How to give writing feedback a writer can use

---

title: "How to give writing feedback a writer can use" date: "2026-09-24T11:24:18-07:00" description: "Replace vague draft comments with clear writing feedback. Use practical examples, a review order, and a reusable note to explain what needs changing without rewriting every sentence." tags: [ "how to give writing feedback", "writing feedback examples", "constructive writing feedback", "how to review a draft", "editorial feedback", "content review process", "feedback on copywriting", "client feedback for writers", "editing comments", "peer review writing", "reviewing blog posts", "website copy review", "working with freelance writers", "revision requests", "content editing", "business writing", "clear communication", "writing collaboration", "editing checklist", "better writing", ] image: "" status: "published"

A writer sends a draft. You read it, sense that something is wrong, and leave a comment that says "Make this stronger." The next version has shorter sentences and a louder headline. It still misses the point you wanted to make.

The problem started in the feedback. "Stronger" describes your reaction, but it gives the writer no clear problem to solve. Useful writing feedback names the passage, explains what a reader needs, and sets a direction for the revision.

You do not need to be an editor to do this well. Whether you are reviewing a blog post, a team email, or website copy from a freelancer, you can turn an uncertain reaction into a practical request. The examples below use invented drafts and review situations so you can see how that works without treating sample claims as real results.

Agree on the job of the draft before marking it up

A draft can be clear and still do the wrong job. A welcome email that explains the company history may read well, yet fail to tell a new customer how to start. Before you comment on words, write down what the reader should understand or do after reading.

For example, imagine a small repair business has asked for an article about preparing a bicycle for a first visit to the shop. The goal is to help a new customer bring the right information and know what happens at drop off. It is not a full guide to fixing a bicycle at home.

That distinction gives you a fair reason to question a long section on replacing brake cables. Without an agreed purpose, cutting that section may seem like a matter of taste. With one, you can explain that the section asks the reader to do work the shop will handle.

Before reviewing, confirm these details with the brief or project notes:

• Who will read the piece, and what do they already know?
• What question should the draft answer?
• Where will it appear?
• What should the reader do next, if anything?
• Which facts, tone choices, or length limits are required?

If the brief left something open, name the new decision in your feedback. Say "We have decided this email should focus on booking the first visit" instead of suggesting the writer ignored a rule that never existed. A change in direction may also change the amount of work needed.

Read once without editing every sentence

Use the first read to understand the whole piece. Keep a short note of places where you lose the thread, need evidence, or have a question. Resist fixing small word choices before you know which sections belong in the next draft.

On the bicycle article, you might notice that the draft spends four paragraphs on tools, never explains whether a customer needs a booking, and puts the drop off steps near the end. Those are more useful findings than spotting two repeated words in the introduction. The writer may remove that introduction once the structure changes.

A simple way to test the draft is to finish this sentence after reading it: "The reader now knows how to..." If your answer differs from the brief, review the focus before the line edits. If you cannot finish the sentence, point to the missing explanation rather than calling the whole draft confusing.

This first read also helps you avoid contradictory comments. You may want an example in the opening, then discover the exact example later. In that case, suggest moving it rather than asking the writer to create another one.

Turn a reaction into a clear revision request

Most useful comments have a location, a reason, and a requested change. The location tells the writer where to look. The reason connects your concern to the reader or the brief, and the request explains what a better version needs to achieve.

Consider the comment "This section feels weak." It leaves the writer to guess whether the problem is tone, detail, evidence, or order. A more useful comment would be:

In the section on drop off, a new customer still cannot tell what to bring. Please add a short list with the bicycle, any removed parts, and a note about when the problem happens. Confirm the list with the shop before including it.

The revised comment does not supply every sentence. It gives the writer a specific gap to close and identifies a fact check. That is enough direction to make the next version meaningfully different.

You can use this pattern even when you are unsure how to fix a passage. Explain the question you had as a reader, then ask the writer to propose a solution. "I cannot tell whether the price includes parts. Can you make that clear after we confirm the policy?" is useful feedback without an instant rewrite.

Separate required changes from personal preferences

Not every comment deserves the same weight. An incorrect price must change. A missing step needs attention. Your preference for one opening sentence over another may be optional, especially if both versions meet the brief.

Use plain labels when the distinction could be unclear. "Required before publishing" tells the writer that a fact or decision blocks approval. "Suggestion" leaves room for another approach, while "Question" signals that you need information before choosing a change.

Be honest about those labels. If you write "Could we perhaps remove this paragraph?" but will reject any draft that keeps it, make the request direct. Polite wording should not hide a firm decision.

Personal taste still has a place in a review. A business owner may choose a warmer voice or prefer a particular phrase. Explain it as a choice rather than presenting it as a universal writing rule, and connect repeated choices to a shared brand voice guide so the writer can apply them consistently.

Put the biggest changes in one review note

A draft with twenty comments can be hard to act on when each comment looks equally urgent. Give the writer a short overview before the detailed notes. Explain what works, which changes matter most, and what you expect in the next version.

For the bicycle article, the review note could read:

The section explaining how to describe a noise is useful and should stay. For the next draft, focus on preparing for a shop visit. Move the booking and drop off steps above the repair advice, and remove the cable replacement instructions. The shop manager still needs to confirm what customers should bring, so please leave that list marked for review. Sentence edits can wait until we approve the new order.

This note gives the writer an order of work. It also protects a successful section that might otherwise disappear during a large revision. The specific praise has a practical purpose because it tells the writer what to preserve.

Keep the overview consistent with the comments in the document. If the overview says to shorten the article but six comments request new sections, decide what should come out. The writer should not have to resolve a conflict you could have caught before sending the review.

Explain tone with examples instead of labels

Words such as "friendly," "professional," and "bold" can mean different things to different people. One reviewer may call a joke friendly while another finds it careless. Give the writer a short example of the tone you mean and explain the choice behind it.

Suppose a draft says, "Our team will undertake a detailed assessment of your bicycle upon arrival." You want the business to sound approachable. A possible revision is, "When you bring in your bicycle, we will check it and explain the repair options."

The lesson is specific. Use everyday verbs, speak to the reader, and show what will happen. The feedback becomes something the writer can use across the draft instead of a request to imitate one sentence.

If you suggest wording, mark whether it is required copy or an example. "Possible wording" gives the writer freedom to improve it. Save exact wording requests for text that truly needs to stay fixed, such as a confirmed product name or an approved statement.

For more help describing sentence problems, the readability guide offers ways to spot long sentences and unclear structure. Keep the comment tied to the passage you are reviewing instead of asking for a better score without explaining why.

Ask for evidence without inventing the missing claim

A reviewer can make a draft less accurate by suggesting a stronger claim without checking it. "Say we are the fastest shop in town" may sound like a copy improvement, but it creates a statement the writer may have no basis to support.

When a claim seems too broad, ask what evidence is available. If the business has a confirmed service time for a defined repair, the writer can describe that service accurately. If no evidence exists, remove the comparison and explain the actual process.

The same rule applies to customer stories. Do not turn "The client found the new page easier to use" into "The new page doubled sales" because the second sentence sounds more persuasive. Ask for approved details or keep the narrower statement.

Make fact checks easy to resolve by naming who can answer them. A comment such as "Maya to confirm whether Saturday drop off needs a booking" creates a clear task. "Check this" leaves the writer searching for both the answer and the person who owns it.

Keep several reviewers from sending mixed directions

When several people review a draft, ask one person to collect the final direction. Individual reviewers can still comment on their areas, but the writer should receive one agreed set of requests. Otherwise, a round of edits can become a contest between competing preferences.

Imagine the sales lead asks for a longer explanation of the repair service while the owner asks to cut the page in half. Both may have a valid concern. The review owner needs to decide whether a short summary with a link to a separate service page meets both needs before passing the request to the writer.

Set the review scope for each person where possible. The shop manager can confirm the process, the owner can approve the offer, and the editor can check the flow. This does not prevent people from raising other issues, but it makes missing decisions easier to spot.

Also keep comments attached to one agreed draft. If someone sends feedback on an older copy, compare it with the current version before adding new work. A writer should not have to restore a sentence that another reviewer already asked them to remove.

Use a feedback note you can adapt

A reusable note can help you cover the essentials without sounding mechanical. Replace the bracketed text with real details and remove any line that has no purpose. A short draft may need only a few sentences.

This draft needs to help [reader] understand [question] and take [next step]. The section on [specific passage] works because [reason], so please keep that part.

For the next version, please address [main issue] by [requested direction]. This matters because [reader need or brief requirement]. Also resolve [second issue, if needed].

[Person] will confirm [fact or open decision] by [agreed date]. The comments marked as suggestions are optional. Please send the revised draft by [agreed date], with a short note about any question that remains open.

Do not use the template to create false certainty. If a date is not agreed, propose one. If you cannot explain why a change matters, reconsider whether it belongs in the review at all.

Before sending the note, scan the document for repeated comments. One clear instruction to replace formal wording is often enough if you include two examples. Marking every instance can make a small issue look like the main problem with the piece.

Review the revision against the requests you made

When the next draft arrives, start with your previous review note. Check whether the writer solved the stated problems before searching for fresh improvements. This keeps the review fair and helps you see whether the feedback itself was clear enough.

If a requested change still misses the point, explain the remaining gap with a concrete example. "The new list covers what to bring, but it still does not say whether a booking is needed" gives the writer a smaller, clearer task. Repeating "Needs work" does not.

Sometimes a revision reveals a new problem. Name it as new rather than treating it as an ignored request. If it changes the scope, agree on the added work before asking for another full rewrite.

Once the main issues are resolved, handle the final sentence edits and approve the piece. A useful review has an end point. The draft is ready when it meets the agreed purpose, contains the required information, and has no unresolved publishing issues.

For your next review, begin with one comment you would normally write as "Make this better." Replace it with the exact passage, the reader question it leaves unanswered, and the change you need. That gives the writer a real task and gives you a clear way to judge the next draft.