Editorial Review and Quality Assurance

Peer Review Feedback Form

Collect specific, prioritized, evidence-aware, actionable feedback from a writing peer while separating reader response, editorial judgment, and required decisions.

Free editable Markdown · Writing teams, editors, and review groups · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Review setup

Draft and version: [File or URL]
Writer: [Name or role]
Reviewer: [Name or role]
Audience and reader task: [From brief]
Review stage: [Concept / Structure / Draft / Line / Final]
Requested focus: [Questions from writer]
Out of scope: [Areas not reviewed]
Decision owner: [Who accepts changes?]

First-read response

My summary: [What the draft says and does]
Main contribution: [What is new or useful]
Expected next action: [What the reader should do]
Strongest element: [Specific passage and why]
First confusion: [Location and reader effect]
Missing context: [What I needed]

This response was recorded before line editing.
Personal preference is labeled as such.

Feedback item

Comment ID and location: [Identifier]
Priority: [Blocking / High value / Optional]
Type: [Purpose / Structure / Evidence / Clarity / Voice / Mechanics]
Observation: [What appears in the draft]
Reader effect or risk: [Why it matters]
Evidence: [Brief, source, style rule, or reviewer experience]
Question or action: [What decision is needed]
Specialist owner: [If outside peer expertise]

Synthesis and handoff

Top revision 1: [Pattern and locations]
Top revision 2: [Pattern and locations]
Revision order: [Dependency]
Strength to preserve: [Specific feature]
Conflicting feedback: [How resolved]
Accepted decision: [Writer or editor response]
Open follow-up: [Owner and date]

How to use this template

Confirm the brief, audience, review stage, confidentiality, feedback scope, and decision owner.
Read once without editing and record an unaided summary, reader experience, and strengths.
Add location-specific comments that describe the issue, effect, evidence, priority, and decision needed.
Group comments into patterns, remove duplication, and order revisions by consequence and dependency.
Discuss questions with the writer, record accepted decisions, and assign any specialist follow-up.

Read once as the intended audience

Before line comments, read the draft without editing and record what you believe its purpose, audience, central contribution, and next action are. Note where you became oriented, confused, convinced, or distracted. This reader response is valuable when labeled as experience rather than universal truth. Compare it with the brief. If the draft solves the wrong problem, sentence corrections are premature. Identify strengths worth preserving so revision does not remove the clearest evidence, example, or voice.

Make comments observable and located

Anchor each comment to a heading, paragraph, sentence, table, or claim. Describe the effect, provide evidence, and state the decision needed. “This is unclear” becomes “I cannot tell whether the deadline applies to submission or approval; name the affected action beside the date.” Ask a question when you lack context. Separate required corrections, high-value revisions, optional ideas, and personal preferences. Too many equal-priority comments shift the burden of diagnosis to the writer.

Synthesize before handoff

After annotating, group issues into a small number of patterns and rank them by reader harm, factual risk, brief alignment, and dependency. Recommend the order of revision: purpose and structure before line polish. Check whether your suggestions conflict with one another or expand scope. In a group review, the review owner should reconcile duplicate or contradictory feedback before handing it to the writer. Invite clarification and record resolved decisions so the same debate does not recur in later passes.

See the fields in context

Fictional example: volunteer welcome guide

Oakpath Kitchen and its guide are invented.

First-read summary: The draft welcomes new volunteers but does not explain how to confirm a shift.
High-priority comment: Under “Your first day,” the reader receives arrival details before confirmation; add the booking action and confirmation signal first.
Evidence: The fictional brief names successful shift confirmation as the primary task.
Strength: Keep the concrete arrival example, which explains an unfamiliar entrance clearly.
Optional note: Shorten two repeated welcome sentences after the task sequence is fixed.

Frequently asked questions

Should peer reviewers rewrite the passage?

Offer a short example when it clarifies the issue, but do not silently replace the writer’s intent or voice. A question and described reader effect may be more useful when context is missing.

How many comments are useful?

Enough to address material patterns and the requested focus. Prioritize rather than marking every possible preference. A synthesis with five consequential actions can be more usable than fifty unrelated comments.

What if reviewers disagree?

Preserve the reasons, compare them with the brief and evidence, and ask the decision owner to resolve material conflicts. Do not make the writer arbitrate an unfiltered pile of contradictory instructions.

Should positive feedback be included?

Yes, when it identifies what works and why. Specific strengths help the writer preserve effective structure, evidence, examples, and voice during revision; generic praise is less actionable.