How to Give Feedback on a Colleague's Draft Without Rewriting It

A colleague sends you their draft: a proposal, a report, a policy. “Could you take a look?” You open it, and the temptation arrives immediately: rewrite it the way you would have written it.

That feels helpful. It is usually not. A heavy rewrite takes you hours, teaches them nothing, and replaces their voice with yours. Good feedback is faster, more useful, and leaves the document theirs.

Ask What Kind Of Feedback They Want

Before you start, ask one question: what stage is this, and what do you need from me?

• Early draft: structure and argument. Is the main point clear? Is anything missing?
• Near-final: clarity, accuracy, tone.
• Final check: typos, figures, formatting.

Commenting on comma placement in an early draft wastes both your time. Questioning the whole structure the day before it is due is not helpful either.

Start With The Big Picture

Read the whole thing once without commenting. Then answer, in a few sentences at the top:

• What is the main point, as you understood it?
• Does the structure support it?
• What is the single most important change?

If your summary of the main point does not match what they intended, that is the most valuable feedback you can give.

Comment On The Problem, Not The Wording

Before (a typical review comment):

Rewrite this.

Or worse, a silent rewrite of the whole paragraph.

After:

This paragraph makes two points, cost and timeline, and the timeline point gets lost. Could you split it, or lead with the timeline since that is what the board asked about?

The second comment explains what is not working and why, and offers an option. The author can fix it in their own words. See how to write useful PDF review comments for document review in general.

Separate Must-Fix From Suggestions

Label your comments:

• Must fix: factual errors, wrong figures, legal or compliance issues, things that will confuse the reader.
• Suggestion: improvements you think would help, but the author can decide.
• Nit: tiny preferences. Use sparingly.

This tells the author where to spend their time and makes clear that not every comment is a demand.

Say What Works

Point out what is strong, specifically. “The opening example is great, it makes the problem concrete” is useful, because it tells them what to keep and do more of. It also makes the critical comments easier to hear.

When A Rewrite Is Appropriate

Sometimes a sentence is easier to show than describe. Offer a suggested rewrite of a single sentence in a comment, clearly marked as a suggestion. If you find yourself rewriting whole sections, stop and have a conversation instead.

The Covering Message

Before:

Done, lots of comments, sorry it’s a bit red

After:

I have left comments throughout. Overall it is in good shape: the argument is clear and the cost section is strong. The main thing I would change is the order of sections 2 and 3, so the recommendation comes before the detail. I have marked two must-fix items, a figure on page 4 and a date in the timeline; everything else is a suggestion. Happy to talk it through.

That message tells them the overall state, the one big change, and how to read the comments.

A Wrivio Context for review feedback could say:

Rewrite this as constructive feedback on a colleague’s document. Warm, specific and direct. Start with what works, then the most important change, then other points labelled as must-fix or suggestion. Keep every page number, figure and specific comment exactly as written. Do not add criticism or praise that is not in the original.

Press Ctrl+Shift+Space, paste your rough notes, and check the tone is collegial rather than corrective. For broader guidance on feedback, the Center for Creative Leadership’s Situation-Behavior-Impact model, summarised in Mind Tools’ guide to the SBI feedback tool, is a useful framework. See also how to give critical feedback in writing.

Common Questions

How much feedback is too much?

If the author cannot act on it in the time they have, it is too much. Prioritise the three to five comments that matter most and mark the rest as optional.

Should I use track changes or comments?

Comments for anything that needs explanation; track changes for clear-cut fixes like typos and figures. Heavy track changes can feel like a takeover.

What if the draft is genuinely bad?

Focus on the biggest problem and offer a conversation. A short call to agree the main point and structure helps more than a hundred comments.

How do I give feedback to someone more senior?

The same way, with framing: “You asked for my view, so here is what I noticed.” Be specific and kind; seniority does not make vague feedback more useful.

Download Wrivio for Windows to turn your review notes into clear, kind feedback your colleague can act on.