Ask a Colleague for Feedback on a Draft by a Clear Date

Start with a reviewable request

A useful feedback email answers three questions near the top: What is the draft? What should the colleague focus on? When would a response help? If any answer is missing, the recipient may need to ask for clarification or spend time reviewing parts you do not need reviewed.

Use a recognizable draft name, such as “April client update” or “Project handoff guide,” rather than “the document.” If the draft has a version label or date, include it. For example, “Draft 2, updated Tuesday” is more informative than “latest version,” which can become ambiguous after another edit.

Set a scope the colleague can act on

Ask for the kind of feedback you need, not every kind of feedback at once. You might want a check on whether the main point is clear, whether the order makes sense, or whether a specific section leaves questions unanswered. If you want proofreading, say so; if you want high-level comments rather than line edits, say that instead.

A short scope helps the colleague decide where to spend attention. It also helps you interpret the response: a review of clarity is not necessarily a full fact-check or approval. If there are areas that are still in progress, name them so the reviewer does not spend time polishing text you expect to replace.

Make the deadline specific and reasonable

Give a calendar date rather than “soon” or “when you can.” Add a time and time zone if the timing is important or the colleague may be working elsewhere. Choose a date that leaves them a realistic opportunity to read the draft, and explain briefly if you have a next step that depends on the feedback.

If the date is flexible, say so plainly and offer a fallback, such as asking them to tell you if the requested timing will not work. Avoid making a request sound optional when you genuinely need a response by a certain point. Clear timing lets the colleague accept, decline, or propose another date.

Check the version and review boundaries

Before sending, open the file or reference you plan to include. Confirm that it is the intended draft, that its name or version matches your email, and that the colleague can access it. If you attach a file, make sure you selected the right one; if you refer to a shared document, check that the reference leads to the intended item and not an older copy.

Then compare the request with the document itself. Are there unfinished sections, sensitive details, or sections outside the review scope that should be called out? Do not assume the recipient knows which edits are current. If you made changes after preparing the message, recheck the file and update any version label before sending.

A concise template to adapt

Replace the bracketed fields with details the recipient can act on. Keep the request focused; add only enough context to explain why the feedback matters.

• The example addresses a colleague at a fictional example.com address; replace it with the intended recipient.
• If you only need one kind of feedback, remove the second question rather than broadening the request.

Subject: Feedback by [day, date] — [draft name], [version/date]

Hi [colleague name],

Could you review [draft name], [version/date]? I’m looking for feedback on [specific question or section] and whether [second focused point] is clear. Please focus on [review scope]; [area or task] is still in progress, so you can skip it.

Could you send comments by [day, date, time, time zone]? I’m using them to [brief next step]. If that timing does not work, please let me know what would be manageable.

The draft is attached / available at [file reference]. Please use this version rather than [older version identifier].

Thanks,
[Your name]

From: [your name] <[sender@example.com]>
To: [colleague name] <[colleague@example.com]>

Confirm the handoff and close the loop

Before sending, check the recipient, subject, deadline, and file reference together. Make sure the promised response date is consistent throughout the message and that the requested review is within the colleague’s role or knowledge. If another person must approve the draft, distinguish feedback from approval so your request does not imply authority the reviewer may not have.

After sending, confirm that the message appears in your Sent folder and that its attachment or file reference is the intended one. That confirms your side of the handoff, not that the colleague has read or received it. If the deadline passes without a response, send a brief, courteous follow-up that restates the draft and asks whether they can still review it. When feedback arrives, acknowledge it and clarify any comment whose meaning is uncertain.