How To Respond To A Vague Request In Writing
“Can you look into the reporting thing?” “Let’s tighten up the deck.” “We should probably do something about onboarding.” You get a message like this and you have two bad options in front of you: guess what they mean and risk doing the wrong work, or fire back “what do you mean?” and sound like you are stonewalling.
There is a third option, and it is a writing move. You reply in a way that converts the vague request into a specific one, does part of the thinking for them, and leaves them an easy confirmation. Done well, it makes you look sharper, not more difficult.
Reflect Back What You Heard, Then Narrow
The fastest way to expose a vague request is to restate it precisely and watch where your version diverges from theirs. You are not asking them to define their terms. You are proposing a definition and inviting a correction.
Before:
What do you mean by “look into the reporting thing”? I need more information before I can start.
After:
Happy to take the reporting issue. To make sure I spend the time well: I am reading this as “find out why the weekly numbers do not match the dashboard and propose a fix.” Is that the right scope, or did you mean something broader?
The second version does the work of interpretation, so the reply the other person has to send is just “yes” or a small correction. The first version pushes the thinking back to them, which reads as resistance even when it is not.
Offer A Default You Will Run With
A vague request often stays vague because the sender has not decided either. Help them decide by proposing the concrete version and attaching a default action. “Unless you tell me otherwise, I will pull the last four weeks and come back Thursday with what I find.” Now silence means yes, and you are unblocked without a meeting.
This is the same mechanism that makes a follow-up email that gets a reply work: you lower the cost of the response to almost nothing.
Separate The Three Questions Hiding In One
Most vague requests are really three questions tangled together: what is the actual outcome you want, how much of my time should this take, and by when. Pulling them apart on paper is often enough to make the real ask obvious.
State your reading of each. “Outcome: a one-page recommendation. Effort: half a day, not a project. Timing: end of week.” If any of those is wrong, the sender will correct exactly the one that is wrong, which is far more efficient than a general “that is not quite it.”
Do Not Over-Ask
There is a failure mode where clarifying becomes interrogation. Five questions back to a one-line request feels like a form to fill out, and the sender disengages. Ask for the one or two things that actually change what you would do, and make reasonable assumptions about the rest, stated openly so they can be corrected. The goal is to reduce their effort, not relocate it.
A Wrivio Context for replying to a vague ask could say:
Rewrite this reply so it restates the request as a specific scope, proposes a default next step with a date, and asks at most one clarifying question. Keep a collaborative tone. Keep every name, date, and figure exactly as written. Do not add multiple questions or language that sounds like I am refusing the work.
Press Ctrl+Shift+Space, paste your draft, and check the diff. Watch that it did not stack up extra questions or drop the date that unblocks you.
Why This Is A Writing Skill, Not A Personality Trait
People treat “being good with ambiguous requests” as a trait you either have or do not. It is mostly a format. Restate, propose, default, confirm. Once you see the four moves, you can apply them to any murky message, and the clearer your reply, the clearer the next request to you tends to be, because you have shown the sender what a useful brief looks like. The related skill of turning a loose conversation into concrete next steps is covered in how to turn meeting notes into action items.
For the broader principle of writing that reduces a reader’s effort, the US federal plain language guidelines are a good, free reference.
Common Questions
How do I ask for clarification without sounding difficult?
Restate the request as a specific scope and propose a default next step, then ask at most one question. Proposing a reading reads as initiative; firing back “what do you mean” reads as resistance.
What if the sender genuinely does not know what they want?
Decide for them and offer it as a default: “Unless you say otherwise, I will do X by Thursday.” A concrete proposal is easier to react to than an open question, and it unblocks you either way.
How many clarifying questions should I ask?
One or two at most, limited to the things that change what you would actually do. Make stated assumptions about the rest so the sender only has to correct what is wrong.
Should I just start working and ask later?
Only if the cost of guessing wrong is low. If redoing the work would be expensive, spend one message to confirm scope first; a short confirmation is cheaper than a wasted half-day.
Download Wrivio for Windows to turn a defensive “what do you mean” into a reply that pins down the real ask.
Read Next
How To Write A Reply That Closes A Thread
Some email threads will not die. The fix is a reply engineered to end them: a decision, the next step, and no open question for anyone to answer.
How To Write A Correction Without A Long Apology
You sent the wrong figure, date, or file. The fix is a tight correction that leads with the right information, not a paragraph of apology that buries it.
How To Write A Message To Contest A Charge
Disputing a bill or a card charge is won on specifics, not outrage. How to write the message that gets the charge reversed: the facts, the ask, and the paper trail.
How to Respond in Writing When a Colleague Takes Credit for Your Work
A colleague presented your work as theirs. How to correct the record in writing without an accusation, and keep your name attached to what you built.
This article is filed underWorkplace Writing, which has 261 articles.