The reviews are back, the email says major revisions, and somewhere in the attached comments a stranger has called your favorite paragraph unconvincing. Learning to respond to peer review comments well, without caving on everything or bristling at anything, is a skill nobody formally teaches, yet it decides the fate of more manuscripts than the original writing does. Editors routinely see strong papers die because the response was defensive, and middling papers succeed because the response was thorough, organized, and gracious.
This guide gives you the working machinery: a cooling-off rule, the standard structure of a response document, a point-by-point template with worked examples, language for disagreeing without self-destructing, and what to do when reviewers contradict each other.
Before You Respond to Peer Review Comments: The Cooling-Off Rule
Read the reviews once, close the file, and do not touch it for 48 hours. First readings reliably distort: criticism reads harsher than intended, and the mind fixates on the one dismissive sentence while skating past the four compliments. Two days later, the same comments look like what they usually are, a mixed but workable to-do list from people who read the paper closely for free.
On the second reading, sort every comment into four buckets: easy fixes, substantive requests requiring real work, requests you intend to push back on, and misunderstandings. That last bucket deserves special attention. When a competent reviewer misreads your paper, the practical lesson is almost never that the reviewer was careless; it is that the text allowed the misreading. Reviewers are a proxy for your future readers, and confusion is data. Under double-blind review, remember, none of it is personal in either direction; the comments were aimed at the work, not at you.
The Anatomy of a Strong Response Document
Editors and reviewers process revisions faster, and more favorably, when the response follows the conventional shape:
- A brief opening paragraph thanking the reviewers and editor and summarizing the two or three largest changes in the revision. Two to four sentences; gratitude, not groveling.
- A point-by-point section that restates or quotes every single comment, numbered by reviewer (R1.1, R1.2, R2.1), each followed by your response. Nothing gets silently skipped, including the compliments, which earn a simple thank-you.
- Locations for every change, by page or section number, so no one has to hunt. Where a change is short, paste the revised sentence directly into the response.
- Visible formatting conventions, stated up front: reviewer comments in italics, responses in plain text, quoted revisions indented. Consistency here signals care everywhere else.
The document is often longer than authors expect, and that is normal. A thorough response to a full set of reviews can run several pages, because its job is to make the editor’s decision easy: every concern raised, every concern addressed, nothing left to check by hand.
The Point-by-Point Template, With Worked Examples
Nearly every response you will ever write is a variation on four moves. The table shows the pattern; the phrasings are starting points to adapt, not scripts to paste.
| Situation | The Move | Sample Opening |
|---|---|---|
| You agree and made the change | Accept, describe the change, give its location | We agree. We have revised Section 3 to state the sampling frame explicitly (p. 8). |
| You agree in part | Accept the valid core, explain the boundary | We agree that the claim was too strong and have qualified it; we have retained the comparison itself because it grounds the discussion in Section 5. |
| The reviewer misread the text | Take responsibility for clarity, then clarify | We see how this passage invited that reading. We have rewritten it to make clear that the analysis excludes the pilot data (p. 6). |
| You disagree | Acknowledge, give evidence, offer an accommodation | We considered this carefully but have kept the original model, for two reasons detailed below; we now note the alternative approach and its trade-offs in the limitations section. |
A worked example, invented for illustration: a reviewer writes that the interview sample seems too small to support the conclusions. A weak response argues that qualitative work is simply different. A strong response makes three moves in four sentences: it acknowledges the concern is reasonable, explains the sampling logic the paper follows and where the revision now states it, and adjusts the language of the conclusions from claims about prevalence to claims about mechanism. The reviewer’s underlying worry, overreach, has been answered even though the sample never changed.
A Mini Response Document, Start to Finish
To see the parts working together, here is a condensed, invented example for a paper with two comments from one reviewer.
Opening. We thank the reviewer and the editor for their careful reading. The two largest changes in this revision are a reorganized literature review (Section 2) and a new paragraph clarifying the scope of our claims (Section 6). Reviewer comments appear in italics below; page numbers refer to the revised manuscript.
R1.1: The literature review reads as a list rather than an argument. We agree. Section 2 is now organized around the two competing explanations our study tests, rather than chronologically. Each subsection ends by stating what the prior work leaves unresolved (pp. 3 to 5).
R1.2: The conclusion overstates what a single-site study can show. We agree in part. We have reworded the strongest sentence and now frame the findings as evidence of a mechanism worth testing across sites (p. 14). We have retained the practical recommendations, now explicitly labeled as provisional, because practitioner readers of this journal expect them.
Notice the rhythm: agreement where agreement is due, a located change for every point, and one small, reasoned boundary. Multiply that rhythm by the full comment list and the response is done.
How to Respond to Peer Review Comments You Disagree With
You are allowed to say no. Editors do not expect capitulation on every point; they expect every point to be engaged seriously. Effective disagreement has a consistent architecture: name what is legitimate in the concern, give your evidence or reasoning plainly, and where possible offer a partial accommodation, a new caveat, an added citation, a clarified sentence, so the reviewer’s effort visibly improved the paper even where you held your ground.
Three rules keep disagreement survivable. First, never be sarcastic, and never question the reviewer’s competence; the editor reads every word, and tone problems outlive technical ones. Second, disagree on a small number of points, not a dozen; a response that fights everything convinces the editor the authors cannot hear feedback. Third, when a requested change is genuinely impossible, such as new data collection the study design cannot support, say so directly, explain why, and state what the revision does instead. Honest constraints, clearly explained, are accepted far more often than authors fear.
A useful self-test before submitting: read only your disagreements, in sequence, imagining you are the editor. If the cumulative tone sounds like a colleague reasoning in good faith, send it. If it sounds like a rebuttal brief, soften two of them or concede one.
When Reviewers Contradict Each Other
Sooner or later, Reviewer 1 will demand more theory and Reviewer 2 will demand less. Contradictions are not a trap; they are a delegation of judgment back to you. State the conflict neutrally in your response, choose a direction, and justify it in terms of the paper’s purpose: we have followed R1’s suggestion here because the added framework directly supports the central claim, while keeping the section concise in view of R2’s concern about length. If the decision letter came with editor guidance, follow it; if the conflict is deep and the stakes are high, a short question to the editor before revising is entirely acceptable and often welcomed.
Deadlines, Logistics, and the Conference Version of All This
Practicalities decide outcomes more often than eloquence. Note the revision deadline the day the decision arrives, and ask for an extension early rather than late; editors grant reasonable requests routinely and resent silent lateness. Keep strict version control, one master file, dated copies at each milestone, so the response document and the manuscript never drift apart. Before resubmitting, have a colleague read the response cold, checking one thing only: does every numbered comment have an answer and a location?
The same craft transfers directly to conference publishing, where timelines are compressed. Papers accepted to conference proceedings often go through a lighter revision round on a fixed production schedule, so the sorting discipline and the point-by-point format matter even more when you have two weeks instead of three months. And journals attached to scholarly organizations, including the NIVA journals, run the full cycle described here, which makes a proceedings revision an ideal rehearsal for the article that follows.
Frequently Asked Questions
As long as thoroughness requires, often several pages for a full revision. Restate every comment, respond to each one, and give the location of every change. Length signals diligence; what editors penalize is skipped comments, not detailed answers.
Yes. Editors expect engagement, not capitulation. Acknowledge the legitimate part of the concern, present your evidence or reasoning respectfully, and offer a partial accommodation such as a caveat or clarification. Keep disagreements few, focused, and free of sarcasm.
No. You must address every comment, which is different from adopting every suggestion. Make the changes you agree with, explain your reasoning where you decline, and flag genuinely impossible requests honestly with an account of what the revision does instead.
Name the conflict neutrally in your response, follow any guidance from the editor, and otherwise choose the direction that best serves the paper’s argument, explaining why. If the contradiction is fundamental, asking the editor before revising is acceptable practice.
The best way to get comfortable with peer review is to go through it with real work and low stakes. Submit your research to NIVA’s next virtual conference and experience the full double-blind cycle, from reviewer comments to published proceedings, with free membership and registration of $150 for faculty and $70 for students.