At a glance / Do not merge the report with the proposed fix
| Reader reports | Reader proposes | Writer diagnoses |
|---|---|---|
| “The middle dragged.” | Cut the middle | Check whether the section has a visible turn |
| “The middle was my favourite.” | Keep it intact | Preserve its force while testing the transition |
Ask for a reader, not a verdict
A beta reader is most useful when the request identifies the draft’s stage. “Tell me if it works” invites a vague burden. A brief says what the piece is, who it imagines reading it, what version is attached, and two or three questions that revision can answer. It also gives the reader a return date and permission to decline. These details respect both the draft and the unpaid attention it is asking for.
Write four parts
Keep the brief to a page: context; desired response; boundaries; logistics. Context might say, “A 4,000-word essay about a translator’s footnotes for general literary readers.” Desired response might ask, “Where did you understand the claim? Where did the example stop carrying it?” Boundaries can say that line editing is not useful yet. Logistics name the file version, comment format, and date. UW–Madison similarly recommends setting feedback goals and choosing a format that fits both reader and writer.
Make questions observable
Avoid questions that demand reassurance, such as “Is the narrator likeable?” Try: “At what point did you decide what the narrator wants, if you did?” Instead of “Does the ending work?” ask “What possibility did you think the final image left open?” The answer may still surprise you. Specific questions give the reader a task without dictating an interpretation, and they yield evidence a writer can compare across responses.
Process conflicting notes
Put comments into three columns: reported experience, proposed solution, and your diagnosis. If one reader says the middle dragged and another says it was their favorite section, the reports are not mutually cancelling. Locate where each reader’s attention changed and what they expected there. Their proposed fixes may conflict; neither obliges you. Your diagnosis might be that the section needs a clearer turn, not that it must be shorter or longer. Wait a day before responding if the notes land hard.
Close the loop honestly
Thank the reader, name one observation you understood, and do not promise to take every suggestion. Keep the brief and notes with the draft version so future revisions do not turn remembered feedback into folklore. Feedback is not a vote, and several readers are not a representative sample of a future audience. It is a set of encounters with this version. That record makes later editorial conversation more precise. If a reader identifies a concern outside your brief, preserve it separately; unexpected response can matter without displacing the draft’s announced revision question. Return to it after the planned revision pass.
Sources & limits
A useful brief cannot replace sensitivity reading, professional editing, or permission to discuss a confidential manuscript.
- Seeking Feedback from Others
University of Wisconsin–Madison Writing Center · Source undated · Consulted 19 Sept 2026The guide recommends setting revision goals, selecting appropriate reviewers and formats, allowing time to consider feedback, and remaining open to unexpected responses.
Send a correction with the passage and supporting source.
