A response letter that works is not the one that says yes to everything—it is the one that maps every reviewer comment to a specific change, pushes back where the reviewer is wrong, and makes it trivial for the editor to see that the revision was taken seriously. This is the anatomy of that letter.
A revise-and-resubmit decision is not a near-miss. It is the outcome most published papers reach. What separates the papers that get accepted from the ones that get rejected in round two is the quality of the response—not the quality of the original draft.
If you want a deeper analysis of tone and the psychological difficulty of writing rebuttals, read our companion piece on crafting winning rebuttals. This post is the procedural counterpart: how to actually structure and write the letter.
What is the anatomy of a strong response letter?
A response letter has three parts, in this order.
-
A short opening. One paragraph thanking the editor and reviewers, stating that you have addressed all concerns, and listing the major changes at a high level. No fluff.
-
A point-by-point response. This is the body of the letter. Every comment from every reviewer gets its own numbered entry, with the original comment quoted and the response directly below it.
-
A summary of changes (optional but recommended). A short table mapping each major change to its location in the revised manuscript. Editors love this because they can verify your work in minutes instead of hunting.
How do you map reviewer comments to specific changes?
This is the single most important skill in writing rebuttals. The pattern is mechanical.
-
Copy the reviewer’s comment verbatim into the letter. Do not paraphrase. Paraphrasing is where authors accidentally soften or change the meaning of the comment, and editors notice.
-
Quote the comment in a visually distinct block. Indented, italicized, or labeled “Reviewer:”—the format does not matter as long as it is unambiguous.
-
Respond below it, starting with the action you took. “We added a new analysis (Section 3.4, Figure 4) that addresses this concern by…” beats “We agree with the reviewer and have revised the manuscript accordingly.”
-
Quote the revised text. If you changed the paper, show the new sentence or paragraph in the letter. The reviewer should not have to open the manuscript to verify the change.
-
If you did not make the change, explain why. Substantively, not defensively. Editors accept well-reasoned pushback far more often than authors assume.
How do you set the right tone in a response letter?
Tone is where most rebuttals fail. The failure modes are symmetric: too defensive reads as intransigence; too accommodating reads as weakness.
A few rules:
- Thank the reviewer for the comment, then engage with it. Not “We thank the reviewer for this insightful comment” repeated 40 times. Once, sincerely, where the comment genuinely improved the paper.
- Respond to the substance, not the framing. A reviewer who writes harshly may still be right. Ignore the tone of the comment; address the content.
- Use neutral, declarative language. “We have added X to address this” is stronger than “We respectfully disagree” followed by three paragraphs of hedging.
- Never be sarcastic. Even when the reviewer deserves it. Especially then.
When should you push back on a reviewer comment?
Push back when you have substantive reasons grounded in evidence or method. Do not push back because the comment is annoying or asks for more work.
Legitimate reasons to push back:
- The reviewer asked for an experiment that is not feasible, and you can explain why and offer an alternative.
- The reviewer misunderstood something, and the misunderstanding is itself useful feedback—clarify the text, do not just defend it.
- The reviewer asked for a citation or analysis that you believe is incorrect or irrelevant; explain your reasoning and offer the closest reasonable alternative.
- Two reviewers gave contradictory advice, and you cannot satisfy both. Lay out the tradeoff and tell the editor which path you chose and why.
When you push back, the editor is your audience—not the reviewer. Make the editor’s job easy by being specific, evidence-based, and brief.
How do you handle a reviewer who asks for new experiments?
This is the most common high-stakes decision in a revision. The right answer depends on three questions:
- Is the experiment necessary to support the central claim? If yes, do it. The paper will not be accepted without it.
- Is it feasible in the revision window? If yes, do it. If not, explain the constraint and propose a narrower version that addresses the same concern.
- Is there a legitimate substitute? Sometimes a more careful analysis of existing data, or a citation to a published result that already answers the question, addresses the concern without new data.
Editors are realistic about revision windows. They will extend them if you ask, and they will accept a well-argued substitute more often than authors expect.
What should the cover letter to the editor say?
Keep it short. One page maximum. State what kind of decision you are responding to (major revision, minor revision), thank the editor and reviewers, list the three to five most important changes, and note any points where you pushed back so the editor can focus there. Do not relitigate the whole review.
How long should a response letter be?
As long as it needs to be to address every comment substantively, and no longer. For a typical major revision with two or three reviewers and 20–40 comments total, expect 3000–6000 words. A letter that is much shorter probably skipped substance; a letter that is much longer probably has padding.
How do you avoid the most common rebuttal mistakes?
- Do not argue with every comment. Pick your battles. Concede where the reviewer is right; fight where the stakes are high and you have evidence.
- Do not bury major changes. Surface them in the opening paragraph and the summary of changes.
- Do not ignore minor comments. Reviewers notice, and it signals carelessness.
- Do not submit without an outside read. You are too close to the revision to judge whether the tone lands. Get an independent read on your response letter before you submit—run your rebuttal through a structured analysis to catch tone and completeness issues while you can still fix them.
Frequently asked questions
How do I structure a response to peer review comments? Use a point-by-point structure: a short opening that thanks the editor and lists major changes, then a body where every reviewer comment is quoted verbatim and followed immediately by your response, then an optional summary table mapping changes to locations in the revised manuscript. Editors should be able to verify your changes without hunting through the paper.
How do I respond to a reviewer comment I disagree with? Respond substantively, not defensively. Quote the comment, state clearly what you did or did not change, and explain your reasoning with evidence. Push back when you have substantive grounds—a misunderstood method, an infeasible experiment, an irrelevant request—and make the editor your audience, since they decide the outcome.
How long should a response letter be? Most major-revision response letters run 3000–6000 words for two or three reviewers and 20–40 total comments. The right length is whatever it takes to address every comment substantively—much shorter suggests you skipped substance, much longer suggests padding.
Should I quote the revised text in the response letter? Yes. When you make a change in response to a comment, quote the new sentence or paragraph directly in the letter so the reviewer does not have to open the manuscript to verify it. This makes the editor’s job easier and signals that you took the comment seriously.
How do I handle a reviewer asking for new experiments I cannot run? Explain the constraint, propose a narrower feasible alternative, and—where possible—point to existing data or published results that address the same concern. Editors are realistic about revision windows and accept well-argued substitutes more often than authors expect.