Reply to a vague request with the questions that pin it down

Write a reply to {{requester}}, who has asked me for something without saying exactly what they need, to send by {{channel}}. I want to confirm what they actually need before I spend time on it, so that I deliver the right thing the first time, without making them feel interrogated or making it look as though I am avoiding the work.

Their request, word for word:
"""
{{request}}
"""

What I think they probably want: {{my_guess}}
What I know about why they are asking (a meeting, a decision, a question from their manager): {{background}}
My other commitments that affect timing: {{my_capacity}}

First work out the few things that would change what I deliver, such as who it is for, what decision it supports, the format, the level of detail, the date and what "done" looks like. Then write a reply that:
1. Says yes, or says what I can do, in the first sentence, so the reply reads as willing.
2. States my best guess at what they need in one or two sentences, so they can simply confirm it.
3. Asks at most three questions, the ones whose answers would change the work most, each answerable in a few words. Offer choices where possible, for example "A one-page summary or the full spreadsheet?". That example shows the form only.
4. Gives a timing based on my capacity, and says what I will start on if I do not hear back by a set time.

Keep it under 120 words for email, or under 60 words for a chat message. The tone should be helpful and brisk, like a colleague who wants to get it right.

Do not ask questions whose answers are already in their request or the background, and do not ask about things that would not change the work. Do not commit to a date my capacity does not support. If the request is so unclear that I cannot form a best guess, say so above the draft, suggest a five-minute call instead of a written list of questions, and write the reply that way.

After the reply, list for me, in two or three bullets, what I will assume and do if they do not answer.