Email Asking a Client to Clarify Scope: 9 Templates

A vague brief is not a comprehension problem. You understood it fine — there just isn't enough in it to start billable work without guessing. The guess becomes the scope, the client remembers a different scope, and the disagreement shows up at invoice time instead of at kickoff, where it's cheap to fix.

The templates below ask for what's missing before that happens. Copy the one that fits, fill in the brackets, and send it before you touch the work.

When to send this#

Send a clarification email the moment a brief leaves a decision to you that changes the deliverable, the timeline, or the price. Not every gap needs one — if the client's intent is obvious and the missing detail is cosmetic, ask in a quick call or a Slack message instead. Save the email for anything you'd want on record.

Three signals that a gap is worth an email rather than a shrug:

• The brief uses an adjective where it needs a number — "modern," "clean," "fast turnaround" — and two reasonable readings of that adjective produce different amounts of work.
• The brief is silent on something you can't build around: which pages, which platforms, whose approval, what "done" looks like.
• You've already guessed once on a similar project and the client pushed back on the guess after delivery.

What a good one contains#

A clarification email that actually gets answered has three parts, in this order: what you understood so far, the specific unknowns, and a deadline for the answer. Skip the first part and the client re-explains the whole brief instead of answering your question. Skip the third and the email sits unread for a week.

Numbered questions outperform paragraph questions by a wide margin — not because clients are lazy, but because a paragraph invites a paragraph reply, and a paragraph reply usually answers the easy question and skips the hard one. A numbered list makes the skip visible.

The templates#

Nine formats, from a first-brief question list through a hard escalation for a client who keeps answering in adjectives. Fill in [DELIVERABLE], [ASSUMPTION], and [ANSWER BY] before sending.

1. 1

   1. First-brief numbered questions

   Subject: Quick questions before I start on [DELIVERABLE] Hi [Name], Thanks for sending this over — before I start, a few things I want to confirm so I build the right thing the first time: 1. [Specific unknown #1, e.g., "Which pages need this treatment — all of them, or just the homepage and pricing page?"] 2. [Specific unknown #2] 3. [Specific unknown #3] If I don't hear back by [ANSWER BY], I'll proceed assuming [ASSUMPTION] so we don't lose time — just flag it if that's wrong. Thanks, [Your name]

2. 2

   2. Assumption-list format (when you must start soon)

   Subject: Starting on [DELIVERABLE] — here's what I'm assuming Hi [Name], To keep us on schedule, I'm starting today on the following assumptions. Reply if any of these are off and I'll adjust before it costs rework: - [ASSUMPTION #1] - [ASSUMPTION #2] - [ASSUMPTION #3] If I don't hear otherwise by [ANSWER BY], I'll treat these as confirmed. [Your name]

3. 3

   3. Vague-adjective clarification

   Subject: What "[their word, e.g. modern]" means for this project Hi [Name], You mentioned wanting something [their vague word]. That word covers a lot of ground, and I want to build toward the right version rather than my own guess. Could you send 2–3 examples — sites, brands, or past work — that show what "[word]" looks like to you? Once I have that, I can scope [DELIVERABLE] accurately. [Your name]

4. 4

   4. Missing-deliverable-boundary question

   Subject: Confirming what's included in [DELIVERABLE] Hi [Name], Before I quote/start this, I want to confirm the boundary of the work so there's no gap later: 1. Does this include [adjacent item, e.g., "the mobile version"] or is that separate? 2. Who's providing [asset type, e.g., "final copy / images / API access"] — you, or should I account for producing it? 3. What counts as done — [specific milestone]? [Your name]

5. 5

   5. Approval-chain question

   Subject: Who signs off on [DELIVERABLE]? Hi [Name], One thing I want to nail down before I start: who reviews and approves this — just you, or does it also go to [likely stakeholder, e.g., "your marketing lead"]? I ask because a second reviewer usually means a round of changes I should build time for. [Your name]

6. 6

   6. Written-confirmation summary (after a partial answer)

   Subject: Confirming scope based on your last message Hi [Name], Thanks for the answers. Here's what I now understand the scope to be, so we're both working from the same page: - [Confirmed item #1] - [Confirmed item #2] - [ASSUMPTION] — this one's still unconfirmed, so flag it if it's wrong I'll start on this basis unless I hear otherwise by [ANSWER BY]. [Your name]

7. 7

   7. Timeline-dependency question

   Subject: One dependency before I can commit to a date Hi [Name], I can give you a firm delivery date once I know [dependency, e.g., "when the content will be ready"] — the timeline shifts depending on that. Do you have a date for that, even a rough one? [Your name]

8. 8

   8. Blocking-question escalation (hard version)

   Subject: Need this answered before I can continue Hi [Name], I've asked about [specific unknown] twice now, and I can't move [DELIVERABLE] forward without an answer — continuing on a guess risks rebuilding it. Could you give me a definite answer, even a one-line one, by [ANSWER BY]? If I don't hear back by then, I'll pause this piece and move to [next task] instead. [Your name]

9. 9

   9. Post-kickoff scope-creep clarification

   Subject: Is [new request] part of the original scope or an add-on? Hi [Name], Happy to do [new request] — I just want to confirm whether this falls inside what we scoped for [DELIVERABLE] or whether it's additional, since it wasn't in the original brief. Either is fine, I just want to price and schedule it correctly. [Your name]

The hard version of this situation#

Some clients answer every clarifying question with another adjective. You ask what "clean" means and they say "you know, just clean and professional." This isn't hostility — it's often that they genuinely don't have a sharper answer yet — but it's still a billing risk, because "clean" has no boundary you can build to or bill against.

The fix is to stop asking open questions and start asking them to react to a specific proposal instead. A person who can't define "clean" in the abstract can usually say "no, more like this" when shown two options.

What to do if there's no reply#

Silence after a clarification email is not neutral — it's a decision by default, and it should default in your favor, not theirs. That's what the assumption-list and written-confirmation formats above are for: they put a stated assumption on record with a deadline, so an unanswered email still protects your scope instead of leaving it undefined.

If the deadline passes, don't keep waiting. Send one short follow-up restating the assumption and the date you're proceeding, then start. A client who objects after you've built to a stated, dated assumption is arguing against their own silence — a very different conversation than one where nothing was ever confirmed.

Where AI Emaily fits#

Chasing down which brief still has an open question, and which client hasn't answered by the date you set, is its own small tracking job on top of the actual work. AI Emaily's reply templates hold these nine formats so you send the right one in a couple of clicks instead of retyping brackets each time, and follow-up reminders flag a thread that's gone quiet past the answer-by date you named — so the assumption-and-deadline pattern above actually gets enforced instead of forgotten in a busy week.

We build AI Emaily. It won't write the judgment call about which questions matter for a given brief — that's still yours — but it keeps the templates ready and the follow-up from slipping.