Every written reading starts with a question, and the quality of the reading is limited by the quality of the question. This isn’t a formality — it’s the single biggest factor in whether a reading actually helps you. A vague question gets a vague answer, no matter how skilled the reader is, because a vague question doesn’t give them anything specific to work with. Here’s how to phrase yours so it can actually be answered.
Why “will it work out?” doesn’t work
“Will things work out?” feels like a real question, but it isn’t specific enough to answer usefully. Work out how? Between whom? By when? A reader can respond to a question like that, but the response has to fill in all the blanks you left open — which means it ends up describing a general situation rather than answering yours. The more open a question is, the more room there is for the answer to be generic. Specificity is what lets a reader actually engage with your situation instead of a placeholder version of it.
This isn’t about being clever or writing a perfect sentence. It’s about closing the gaps that would otherwise force the reader to guess at what you actually mean. Part of the reason vague questions are so common is that a specific question can also get a specific answer you don’t want. “Should I leave my job” risks a direct yes or no; “will things get better at work” doesn’t, because it’s vague enough to interpret however you like afterward. If you want a reading that’s actually useful, that trade is worth making — a direct answer you can act on is worth more than a soft one you can’t.
Start with the decision, not the feeling
Most questions start as a feeling: anxious about a relationship, unsettled about work, unsure about a move. That feeling is real, but it’s not yet a question a reader can answer. The useful step is converting the feeling into the decision sitting underneath it. “I’m anxious about my relationship” becomes “should I bring up moving in together before the lease renews.” The feeling explains why you’re asking. The decision is what the reading actually needs to be about.
The “should I” test
A quick way to check whether your question is specific enough: try rephrasing it as “should I” or “is it likely that.” If you can’t fit your question into either shape without adding more detail, it’s probably still too broad. “Will I find love” doesn’t fit into either shape without more information — love with whom, on what timeline. “Is it likely that reaching out to this specific person now will go anywhere” fits cleanly, because it names a person, an action, and a timeframe.
Give context, but don’t over-explain
Context helps — but only the parts that actually change the answer. Three things are usually worth including: the timeline (is there a deadline, and when), who else is involved, and what you’ve already tried. Everything past that tends to be backstory that doesn’t move the answer one way or the other. If you’re not sure whether a detail matters, a short version that includes it costs you nothing; a long version that buries it in unrelated history makes it harder for your reader to find. A question with three well-chosen facts attached is more useful than one with fifteen facts and no clear priority among them.
One question at a time
It’s tempting to fold three concerns into one submission — the job, the relationship, and the move, all in one question. Resist it. A reading answering three questions at once has to split its attention three ways, and each answer ends up thinner than if you’d asked one question properly. If you have more than one thing weighing on you, pick the one that matters most right now. The Deep-Dive tier’s included follow-up question exists for exactly this situation — ask the first question, sit with the answer, then use the follow-up for whatever’s still open.
What happens if your question is still too broad
If you submit a question and it turns out to still be too open for your reader to answer directly, they won’t simply guess. On Full Reading and Deep-Dive orders, a reader who needs a specific detail before they can answer properly will email you to ask for it before writing anything — you won’t be penalized for an imperfect first attempt, and it won’t cost you anything extra. It does add a small amount of time to your turnaround, though, so a narrower question up front is still worth the effort.
Examples: vague vs. specific
Vague: “Does he still think about me?”
Specific: “Is it worth reaching out to him again, given that the last time we spoke was six months ago and he hasn’t contacted me since?”
Vague: “Will I ever get out of this job?”
Specific: “Should I start applying elsewhere now, or wait until after the review I’ve been told is coming in the spring?”
Vague: “What does the future hold for my family?”
Specific: “Should I bring up my father’s health with my siblings directly, or wait for him to raise it himself?”
Each specific version gives a reader something to actually work with: a timeline, a decision, a real stake. That’s the whole difference between a reading that feels generic and one that feels like it was actually about you.
Once your question is narrowed down, you’re ready to ask it.