How to Give Feedback on a Draft Without Rewriting It

There is a moment every content manager knows. The draft is not quite right, the deadline is close, and it feels faster to just fix it yourself. So you do, and the piece ships, and you learn nothing, and the writer learns nothing, and the next draft has the same problem in the same place.

Rewriting a draft yourself is not feedback. It is you doing the writer’s job for free while training them to keep missing. Good feedback costs you a few sharp sentences and buys you a better draft this time and a better writer next time. The skill is saying exactly what is wrong in a way the writer can act on without guessing.

Why the Rewrite Is a Trap

Fixing it yourself feels efficient. It is the most expensive thing you can do.

You pay three times. You pay the writer for the draft, you pay yourself in the hours spent rewriting, and you pay again next month when the identical flaw returns, because nothing you did told the writer it was a flaw. The rewrite is a private correction the writer never sees, so it cannot change anything.

Feedback is the opposite trade. A few minutes of precise notes now saves you the rewrite this time and shrinks the editing on every draft after it. The writer who understands what you meant by “this section restates the intro” will not do it again. The one who only ever sees a clean published version has no reason to change.

The rule is simple. If you find yourself rewriting rather than annotating, stop. The moment you are supplying the sentences, you have taken over the job you were paying someone else to do.

Point at the Sentence, Not the Vibe

The single most common failure in feedback is vagueness. “Make it more engaging.” “This needs more punch.” “Can you tighten it up.” Every one of those is a feeling, not an instruction, and the writer has to reverse-engineer what you meant from a mood.

Precise feedback names the location and the reason. Not “the intro is weak” but “the first two sentences restate the title without adding anything, so a reader who clicked already knows this.” Now the writer knows what to cut and why. The why matters as much as the what, because it lets them apply the fix everywhere the same problem appears, not just in the spot you flagged.

The test for a good note is whether the writer could act on it without asking you a follow-up question. “Add more energy” fails the test instantly. “This paragraph lists three benefits but never says why they matter to the reader, can you connect each to a consequence” passes it. One is a mood. The other is a task.

Separate Errors From Preferences

This is the distinction that keeps revision rounds sane, and skipping it is how a single draft turns into four rounds of drift.

An error is objective. A fact is wrong. The piece missed the brief. A section contradicts an earlier one. The direct-answer block does not actually answer the question. These are non-negotiable, you flag them plainly, and the writer fixes them without argument because there is nothing to argue about.

A preference is subjective. You would have opened with the second point. You prefer “however” to “but.” You would have used a different example. These are real, and sometimes worth a note, but they are not errors, and you should mark them as optional so the writer knows the difference. A pile of preferences dressed up as errors makes a competent writer feel like they cannot do anything right, and it is the fastest way to lose a good one.

Before you send a note, ask which kind it is. If it is an error, say so directly. If it is a preference, either let it go or flag it as a preference the writer can take or leave. The draft gets fixed, the relationship survives, and you stop paying for revision rounds that only chase your own taste.

Tie It Back to the Brief

Feedback that invents a new standard is not feedback, it is a moving target, and it is the single thing writers resent most.

If the brief said “for a marketing manager who already knows the basics” and you now want it dumbed down for a beginner, that is not a revision, that is a new brief, and it is not fair to bill it against the writer’s revision round. Say plainly that the brief changed and treat the extra work as new work.

The honest move is to point every request back at something you agreed on before writing started. “The brief asked for one clear argument, and this draft makes three, so which one are we keeping” is a fair note grounded in the original spec. “I’ve decided I want it to feel different now” is not, and a writer who has delivered to spec is right to push back on it.

This is also why a sharp brief is the cheapest editing tool you own. Most of the feedback you would give on a draft is really feedback you could have given on the brief, before anyone wrote a word. The tighter the brief, the shorter the revision round, every time.

A Simple Structure for the Note

You do not need a template, but a consistent shape makes feedback faster to write and easier to act on.

Part of the note	What it does
What is working	One honest line, so the writer keeps the good parts instead of second-guessing everything
The must-fixes	Errors and broken-brief items, each with a location and a reason
The preferences	Optional changes, clearly labeled as take-or-leave
The one priority	If you name a single most important fix, you get it, instead of effort spread thin

Leading with what works is not politeness for its own sake. A writer who does not know which parts to keep will often “fix” the good sections along with the bad ones, and you end up worse off. Two sentences of specific praise protect the parts of the draft that already earned their place.

What to Do When It Is Really Not Working

Sometimes a draft is not a revision problem, it is a mismatch, and no amount of good feedback fixes a writer who does not understand your reader.

The signal is the pattern across rounds. If the same fundamental misunderstanding survives clear, specific feedback twice, more feedback is unlikely to help. That is not a note, that is a hiring signal, and it is better to end the engagement cleanly than to grind through five rounds turning their draft into yours one comment at a time. A paid trial piece exists precisely to surface this before it becomes a standing relationship.

But most drafts are not mismatches. Most are a good writer who needed one thing said clearly and did not get it. Give them the sentence, the reason, and the tie back to the brief, and the second draft usually lands.

Here is the underlying reason feedback is so much work. Commissioning is buying a promise, and a promise needs managing into a product through rounds of notes. Buying something already finished skips the entire loop, because there is no draft to revise when the article already exists and you already read it.

That is how Postdex sidesteps the revision round on the pieces where you want zero risk. Every article in the catalog is complete and readable before you buy, so your judgment happens once, at the point of reading, instead of across three rounds of feedback. Each piece is an edition of one and leaves the shelf permanently once sold. When you do commission, the commissioning desk runs the drafts and a named editor handles the revision loop, so the version that reaches you is already the version you would have edited toward.

Before you rewrite your next draft, stop and write the note instead. It costs you five minutes now and saves you the same fix, forever.