Request Clarification on an Assignment’s Acceptance Criteria

Choose the right moment to ask

Ask as soon as an ambiguity could affect your approach, workload, or delivery date. For example, a request to “prepare a client update” may mean a short email, a slide deck, or a longer report. Waiting until the work is nearly finished makes a change more disruptive and leaves less time to resolve conflicting expectations.

You do not need to question every detail. Focus on decisions that would materially change what you produce: the intended audience, required content, level of detail, format, review process, or deadline. If one reasonable interpretation seems likely, state it as a proposal rather than silently treating it as settled.

Check the three essentials

Start with scope: what must be included, what can be left out, and whether recommendations, analysis, or supporting materials are expected. Where possible, turn broad language into observable criteria. Instead of asking only what “comprehensive” means, ask whether the deliverable should cover specified topics or answer particular questions.

Then check format. Confirm the file or channel, approximate length or level of detail if it matters, and whether the work should be a working draft or ready for distribution. Finally, confirm the due date, including the relevant time zone when people are working across locations. Ask whether the date refers to a draft for review or the final version.

• Scope: required topics, exclusions, audience, and expected depth.
• Format: file type or channel, structure, and draft versus final.
• Due date: date, time zone if needed, and review or approval timing.

Make the email easy to answer

Use a subject line that connects the question to the assignment. In the message, briefly identify the task, explain the uncertainty without blaming anyone, and group your questions so the recipient can respond point by point. If you have a sensible starting proposal, include it. A proposed interpretation gives the requester something concrete to confirm or adjust.

Keep the tone neutral and the request specific. Avoid a long list of every possible preference. If the recipient is busy, distinguish the decisions you need before starting from details that can be settled during review.

To: [requester@example.com]
From: [your.name@example.com]
Subject: Clarifying acceptance criteria for [assignment]

Hi [Name],

I’m preparing [assignment or deliverable] for [audience or purpose] and want to confirm what you’ll consider complete before I proceed.

Could you clarify:
- Scope: Should I include [specific topic or analysis], or keep this to [narrower scope]?
- Format: Would you prefer [proposed format and level of detail], and should it be a draft for review or a final version?
- Due date: Is [date and time, with time zone if relevant] the deadline for the draft or the final deliverable?

My proposed approach is [brief summary of what you will include and exclude]. Please let me know if that matches your expectations or what you would change. If these details are already documented, could you point me to the relevant brief or example?

Once confirmed, I’ll proceed on that basis. If the timing needs to change, I’ll flag the impact before committing to a revised date.

Thanks,
[Your name]

Adapt the template to the assignment

Replace each bracketed field with details the requester can recognize. Name the actual task rather than writing “the project,” and give a concrete choice where you can. For example, ask whether a summary should include recommendations instead of asking whether the expected depth is “enough.” If you cannot yet suggest a format, ask what the audience needs to do with the deliverable and offer to recommend a format after you understand that purpose.

Keep assumptions visible. If the requester has already provided a brief, refer to the specific point that conflicts or seems incomplete; do not imply that you reviewed a document you have not seen. If there are several independent questions, numbering them can make a reply easier to map back to the work.

Confirm the answer before work moves ahead

When the requester responds, check that the reply resolves scope, format, and timing—not just one of them. If their answer is still broad, restate your understanding in a short follow-up: “I’ll include [items], use [format], and send [draft or final] by [date and time].” Ask them to correct anything that is off. This creates a shared working interpretation without presenting it as a formal approval process.

If the agreed scope cannot fit the available time, say so promptly and offer choices, such as reducing the scope or discussing a different delivery date. Do not quietly remove requested content or promise a deadline you cannot meet. Keep the response with the assignment materials so you can refer back to the criteria during review.

Use a short pre-start check

Before proceeding, read the request and reply together. You should be able to explain what you will deliver, what it will contain, what form it will take, and when it is due. If any answer is missing or contradictory, ask one focused follow-up rather than filling the gap with an assumption.

You can confirm the clarification worked when you and the requester can describe the same deliverable in plain language and identify the same deadline. That does not guarantee there will be no later change, but it gives you a clear baseline. If requirements change after work begins, identify what changed and discuss its effect on scope or timing before revising the deliverable.

• Can you list the required inclusions and any agreed exclusions?
• Do you know the requested format and whether the version is draft or final?
• Is the deadline unambiguous, and does it apply to the right version?
• Can you restate the criteria and get correction before proceeding?