“Make it better.” “This section feels off.” “Can you tighten this up?” Each of these is honest, and none of them can be acted on, because the writer still does not know where the problem is, what it is, or why it matters.
To give writers feedback they can act on, make every note point to a specific place in the draft, describe what a reader experiences there, and give the reason it matters for this article. Send the few notes that affect structure first, label which notes must be fixed before publishing, and finish with a short summary of what to change, in order.
That is the method. Below is how each part works on a real publishing team, where the same writer will get your feedback again next week.
Why “make it better” fails
Vague feedback fails for three separate reasons, and fixing one does not fix the others.
It has no location. The writer has to guess which paragraph you meant. They often guess wrong and rewrite the part that was fine.
It has no reason. Without knowing why something is a problem, a writer can only change it, not improve it. The change may well be worse.
It has no priority. Twenty notes of equal weight tell a writer nothing about what matters. They fix the easy ones first, and the draft still does not work.
How to give writers feedback: the anatomy of a usable note
A usable note has up to four parts. The first three are required.
| Part | What it says | Example |
|---|---|---|
| Place | Exactly where | “Second section, third paragraph” |
| Reader effect | What a reader experiences there | “I lost track of which option you were recommending” |
| Reason | Why that matters for this piece | “This is a decision guide, so the reader needs the recommendation to be unmissable” |
| Suggestion (optional) | One way to fix it | “I suggest stating the recommendation in the section’s first sentence” |
Compare a before and after:
- Before: “This section is confusing.”
- After: “Second section, third paragraph: I lost track of which option you were recommending. This is a decision guide, so the recommendation needs to be unmissable. I suggest stating it in the first sentence of the section.”
The second note takes fifteen seconds longer to write and can save a whole revision round.
Describe the effect, not the writer. Miami University’s Howe Center for Writing Excellence, in its guidance on giving feedback to writers (read September 11, 2026), recommends first-person reader statements such as “I’m having trouble following this line of reasoning” over “you’ve lost me here.” The same guidance favors direct suggestions like “I suggest that you add…” over softer phrasing like “you might consider.” Both carry over to editorial work: say what happened to you as a reader, and say plainly what you would like changed.
Tie the reason to something you both share. The strongest reasons point to the brief, the style guide or the reader. The weakest point to your taste. “I would not say it that way” is not a reason.
Label every note before you send it
Every note should carry one of three labels. This single habit does more for a writer than any amount of careful phrasing.
| Label | Meaning | Relationship to publishing |
|---|---|---|
| Must fix | Inaccurate, off-brief, breaks the style guide, or will confuse readers | Blocks publishing until resolved |
| Should fix | Would clearly improve the piece | Expected, but open to discussion |
| Your call | A suggestion the writer can take or leave | Never blocks |
Labels tell a writer where to spend their time. They also keep the editor honest: if you cannot justify a “must fix,” it is a “your call.”
Structure first, sentences last
Send big notes before small ones, ideally in separate rounds.
George Mason University’s Writing Center, in its guidance on providing feedback to writers (read September 11, 2026), advises focusing on “the ‘big picture’ elements of the writing, such as content, organization, logical connections, and audience appropriateness.” Notes about a comma in a paragraph that is about to be cut are wasted on both sides.
In practice:
- First round: does it answer the brief, is the structure right, is anything missing? A few notes at most.
- Second round: accuracy and clarity, section by section.
- Final round: line-level notes and style guide consistency.
Small teams often compress this into a single pass, which is fine for a routine piece. Keep the order within that pass, and put the structural notes at the top of your summary.
How many notes is too many
The Howe Center guidance is blunt about this: “keep comments to a minimum; don’t over comment.” A draft with sixty marks does not look like sixty problems to the writer. It looks like one problem: you did not like it.
Two practical limits help.
- If more than a handful of notes are structural, stop annotating. Send the draft back with a summary of the structural problems. Line notes on a section that is about to change are wasted.
- Cut your “your call” notes hardest. They are the easiest to write and the least useful to receive. Keep the ones that would genuinely improve the piece and drop the rest.
The summary note
Margin notes show the writer where. The summary tells them what to do. Keep it short and put it at the top.
A workable shape:
- What works, specifically. “The opening example is exactly right for this reader; keep it.” Specific praise tells the writer what to protect when they revise.
- Must fix, in order. Usually one to three items.
- Should fix. A short list.
- Everything else is your call.
- When you need it back.
That five-line note turns a page of marks into a plan the writer can work through in one sitting.
Feedback that repeats is a missing standard
Most feedback advice leaves this out, because it is written for a single draft rather than a publishing operation.
If you give the same note to the same writer twice, the problem is not the writer. The rule lives in your head instead of somewhere they can see it.
Keep a short running list of the notes you give more than once. Every few weeks, turn the recurring ones into lines in your style guide or your brief template. A note like “define the term before you use it,” given ten times, is one style guide line that prevents the next ten. Keeping an editorial style guide to one page makes that practical, because a guide short enough to read is one writers will actually check before they submit.
The same logic applies to briefs. If your feedback keeps saying the article went in the wrong direction, the brief did not set the direction clearly enough, and the fix belongs there rather than in the next round of notes.
When the writer disagrees
Sometimes the writer is right. A note is advice from one reader, and the writer may know something about the subject or the audience that you do not.
Handle disagreement by label:
- “Your call” notes: the writer decides. No discussion needed.
- “Should fix” notes: a short conversation. If the writer’s reason is good, drop the note.
- “Must fix” notes: these are tied to accuracy, the brief or the style guide, so the discussion is about the standard, not the sentence. If the standard turns out to be wrong, change it for everyone.
What should not happen is a comment thread that runs for days. Someone on the team has the final say on whether an article is ready, and feedback exists to inform that decision, not to replace it.
Keep feedback next to the text
Keep notes attached to the draft rather than scattered across chat messages and email. Comments in the document, or review comments on a set of changes in a Git-based workflow (see how pull-request review works for content teams), keep every note beside the words it is about, so nobody has to reconstruct what was said. If your platform makes that hard, it is one of the questions worth asking when choosing a CMS for a content team.
FAQ
What makes feedback on writing actionable?
Each note names a specific place, describes what a reader experiences there, and gives the reason it matters for this piece. A label (must fix, should fix, your call) tells the writer what to do first.
Should I start feedback with something positive?
Yes, if it is specific. “The opening example is exactly right; keep it” tells the writer what to protect. Generic praise does not help them revise.
How do I give feedback without rewriting the writer’s work?
Describe the problem and, if useful, suggest one way to fix it, then leave the fixing to the writer. Direct changes are best kept for factual errors and style guide rules.
How much feedback should I give on one draft?
As little as will get the draft where it needs to be. Send structural notes first, and if there are more than a handful, return the draft with a summary instead of marking every line.
Good feedback is not gentler or harsher than bad feedback. It is more specific, better ordered, and tied to a standard the writer can see.
