Response to Reviewers Example: A Full Template With Real Response Language
A worked response to reviewers example, covering the cover paragraph, point-by-point structure, and real response language for agreement, partial agreement, respectful disagreement, and out-of-scope requests.
Readiness scan
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan before you submit. Catch the issues editors reject on first read.
How to use this page well
These pages work best when they behave like tools, not essays. Use the quick structure first, then apply it to the exact journal and manuscript situation.
Question | What to do |
|---|---|
Use this page for | Building a point-by-point response that is easy for reviewers and editors to trust. |
Start with | State the reviewer concern clearly, then pair each response with the exact evidence or revision. |
Common mistake | Sounding defensive or abstract instead of specific about what changed. |
Best next step | Turn the response into a visible checklist or matrix before you finalize the letter. |
Quick answer: A response to reviewers letter has two parts: a short cover paragraph, then a point-by-point section that quotes each comment in full and answers it with what changed and where. The five response types below (agree, partially agree, disagree respectfully, already addressed, out of scope) cover almost every comment you will get.
This page covers the general shape of the letter, for any revision round. If your decision letter specifically says major revision and you want a deeper, field-by-field treatment with a full checklist, use the rebuttal letter template for major revision instead.
The structure every response letter needs
Every response to reviewers letter, regardless of journal, has the same two-part shape.
The cover paragraph goes first. It thanks the editor and reviewers, summarizes the revision at a high level in two or three sentences, and notes anything you changed that was not directly requested (a typo you caught, a citation you updated). Keep it short. The editor reads this in ten seconds before moving to the detail.
The point-by-point section follows. Reviewers are handled one at a time. Under each reviewer, every comment is quoted in full, then answered immediately below it with the exact change and its location in the revised manuscript.
Dear [Editor name],
Thank you for handling our manuscript, and our thanks to the reviewers for
comments that have made the paper stronger. We have revised the manuscript
and respond to each point below. Changes in the manuscript are
marked in [tracked changes / a different color] and referenced by page and
line number.
Reviewer 1
Comment 1: [Quote the reviewer's comment in full.]
Response: We thank the reviewer for this point. [State what changed and why,
or the evidence for a respectful disagreement.] This is now reflected on page
X, lines Y-Z.
Comment 2: [Quote the reviewer's comment in full.]
Response: [Answer.]
Reviewer 2
Comment 1: [Quote the reviewer's comment in full.]
Response: [Answer.]
We believe these revisions have strengthened the manuscript and thank the
editor and reviewers again for their time.The template is a shape, not a script. What makes a response letter work is the response language inside it, which is where most authors get stuck.
Example language by comment type
Most reviewer comments fall into one of five types. Here is real response language for each.
Full agreement. The reviewer is right and the fix is straightforward.
"We agree with the reviewer. We have added the missing effect size and 95% confidence interval to Table 2 and now report it in the Results (page 6, lines 12-15)."
Partial agreement. Part of the comment is valid, part is not, or the full request is not feasible in the time available.
"We agree that a longitudinal follow-up would strengthen the causal claim. A follow-up cohort is outside the scope of the current data collection window, so we have softened the claim in the Discussion to describe the finding as cross-sectional evidence consistent with, rather than proof of, the proposed mechanism (page 9, lines 3-7)."
Respectful disagreement. The science does not support the reviewer's request, and you say so with evidence, not a flat refusal.
"We respectfully disagree that a two-way ANOVA is more appropriate here. Our design has a nested random effect (site within region) that a two-way ANOVA does not account for; the mixed-effects model we used is the standard approach for this structure (Bates et al., 2015). We have added a sentence in the Methods (page 5, lines 20-22) clarifying this choice."
Already addressed. The manuscript already contains what the reviewer is asking for, and the fix is to point to it more clearly, not to add new material.
"This is addressed in the Supplementary Methods (Section S2), which we referenced only once in the main text. We have added a direct pointer to Section S2 at the relevant point in the main Methods (page 4, line 18) so it is easier to find."
Out of scope. The request is reasonable in principle but is a different paper, or requires resources you do not have.
"We agree this is an interesting direction. Testing it properly would require a separate cohort recruited prospectively over a multi-year window, which is beyond the scope of the current manuscript. We have added a sentence to the Discussion noting this as a direction for future work (page 10, lines 8-9)."
The common thread across all five: every response names the exact page and line where the change lives, or explains clearly why there is no change. A reviewer who cannot find what you say you did will assume you did not do it.
Response type | When to use it | Risk if handled wrong |
|---|---|---|
Full agreement | The comment is correct and the fix is direct | Sounds grudging if you skip the "we agree" |
Partial agreement | Some of the request is valid, some is not | Reads as a dodge if you do not name which part |
Respectful disagreement | The science does not support the request | Reads as defensive if you skip the shared premise |
Already addressed | The manuscript already covers it | Reviewer feels dismissed if you do not point to the exact location |
Out of scope | Reasonable request, wrong paper or resources | Reads as evasive without a stated reason |
Source: response-letter patterns compiled from PLOS, APA, and Manusights pre-submission review work.
What we see in pre-submission review work
In our pre-submission review work, the response-letter failure patterns are consistent across fields. The most common one is a response that says "we have clarified this" with no page or line number attached, which forces the reviewer to re-read the whole manuscript to check. The second is a defensive disagreement that opens with "however" or "the reviewer is mistaken" instead of stating the shared premise first, which reads as combative even when the underlying science is correct. The third is a long reviewer paragraph that contains two or three distinct requests, answered as if it were one.
These are the same reviewer-pushback patterns Manusights predicts before submission. Catching a missing effect size, a vague causal claim, or a defensible-but-unstated methods choice before you submit means fewer of these comments show up in the first place. Predict likely reviewer pushback before you submit.
Readiness check
Run the scan to see how your manuscript scores on these criteria.
See score, top issues, and what to fix before you submit.
Common mistakes that weaken a response letter
No location cited. "We have revised this section" tells the reviewer nothing about where to look. Always name the page, paragraph, or line.
Templated answers. The same sentence reused for three different comments reads as dismissive, even when each individual response is technically accurate.
Promising more than the manuscript delivers. If the response says a new analysis was added, the analysis needs to actually be in the revised manuscript, in the location cited. Editors and reviewers check.
Splitting one comment across multiple responses. If a reviewer raises three points in one numbered comment, answer all three, ideally as three sub-bullets, not one blended paragraph that only covers part of it.
Opening a disagreement with "no." Start with what you agree on, then explain the evidence for where you differ. The order changes how the disagreement reads, even when the content is the same.
When to think twice before sending it
Read the letter once as the editor, not as the author. If any response still reads as vague, defensive, or unverifiable against the manuscript, fix it before you resubmit rather than after a reviewer flags it again in the next round.
Who should draft the actual letter
For turning your notes into finished response-letter prose, general language models like ChatGPT and Claude are the better tool: paste the reviewer comment, describe your intended response, and they draft clear, polite language fast. The best AI tools for responding to reviewers guide covers how to use them well and where they go wrong. If you want a second read on a letter you have already drafted, the response to reviewers review service checks whether every comment is answered and whether the tone will land the way you intend.
Tool | Best for | Price |
|---|---|---|
ChatGPT or Claude | Drafting the response letter itself, once you have the comments | Free or existing subscription |
Manusights free scan | Predicting likely reviewer pushback before you submit, so there are fewer comments to answer | Free |
Manusights $39 Full Review | Journal-fit reasoning, citation checks, and named pushback patterns before submission | $39 |
Manusights does not draft response letters; use it upstream, before you submit, to reduce how many hard comments you get.
Frequently asked questions
A short cover paragraph thanking the editor and reviewers and summarizing the revision at a high level, then a point-by-point section that repeats each reviewer comment in full, followed immediately by the author's response and the exact location of the change in the revised manuscript.
As long as it needs to be to answer every comment, and no longer. A response with 15 comments is naturally longer than one with 4. The failure mode is not length, it is an unanswered comment or a response with no location cited.
No. Reviewers are sometimes wrong or working from an outdated version of the field. Disagree when the science supports it, but disagree with evidence and a respectful tone, not with a flat refusal.
General language models like ChatGPT and Claude are genuinely good at drafting a first-pass response once you have the comments. Use them to turn your notes into clear, polite prose, then verify every response against what the revised manuscript actually says.
Not directly. Manusights is a pre-submission review: it predicts likely reviewer pushback by named pattern before you submit, so you have fewer and easier comments to answer later. For drafting the response once comments arrive, a general language model is the better tool.
Sources
Final step
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan. See score, top issues, and journal-fit signals before you submit.
Private API processing. Your manuscript is not used to train models.
See example reportsPut the guidance to work
Move from draft advice to a practical manuscript pass.
Choose the reporting framework first, then use the final checklist when the manuscript and submission files are ready to travel together.