A systematic process for responding to peer review comments — from reading the decision letter to submitting a revision that gets accepted.
You just received peer review comments on your manuscript, and your stomach dropped. This is normal. The mix of dread, indignation, and (if you are being honest with yourself) the uncomfortable recognition that some of the comments have a point — every researcher knows this sequence. What separates the papers that survive revision from the ones that don't is not the quality of the science; it is how you respond to peer review comments in the document that accompanies your resubmission.
Here is the uncomfortable truth most guides avoid stating directly: a strong revision with a weak response letter gets rejected more often than a decent revision with an excellent response letter. The response letter is the argument that the paper is ready. It needs to be systematic, specific, and strategically aware.
This guide walks you through every step, from the moment you open the decision letter to the moment you click "submit."
What Do Reviewers Actually Want When They Read Your Response?
Before you write a single word, it is worth understanding the psychology on the other side of the transaction. Reviewers are researchers too — usually overworked, almost certainly unpaid for the review itself, and (in most cases) genuinely trying to improve the paper even when their tone suggests otherwise.
When a reviewer opens your response letter, they are looking for four things:
- Evidence of engagement. Not agreement with everything, but engagement with the substance. They want to see that you read their comment, understood its intent, and took it seriously.
- Specificity. "We revised the manuscript" is not a response. "We added a subsection (3.2) with a sensitivity analysis across three parameter ranges, reported in new Table 4" is a response.
- Intellectual honesty. If you cannot do what they asked, they would rather you say so and explain why than watch you perform a hollow gesture that does not actually address the concern.
- Easy navigation. They want to locate their comment, read your response, and find the corresponding change in the manuscript without hunting through 40 pages.
Most peer review frustration (on both sides) comes from a mismatch in these expectations. Reviewers expect substantive engagement; authors provide deflection dressed as compliance. Understanding this asymmetry is half the battle. For the formatting dimension, see our response to reviewer comments template.
Step 1: Read the Reviews. Then Close Your Laptop.
This is not performative advice. Read the decision letter and all reviewer comments once, beginning to end. Do not open your manuscript. Do not start revising. Do not compose draft responses in your head (you will do this anyway, but recognize it for what it is: emotional processing, not strategy).
The first read is for absorbing the blow and letting the sting dissipate. Give yourself 24–48 hours before you begin working. Every senior researcher will tell you this, and every early-career researcher ignores it at least once — usually to their regret.
After the cooling period, read the reviews again. This second read is different. The comment you initially found outrageous now looks like it identifies a genuine weakness. The comment you initially agreed with turns out to rest on a misreading of your method. The emotional distance changes the signal-to-noise ratio dramatically.
Step 2: Categorize Every Single Comment
Open a spreadsheet or document and list every individual comment from every reviewer. Assign each one to a category. This categorization is the foundation of your entire revision strategy — skip it and you will spend the next three weeks reacting instead of executing.
Must-fix: The reviewer is right, and the change will make the paper better. Failing to address these is the fastest path to rejection. Examples include statistical errors, missing references to directly relevant work, and unclear method descriptions that leave readers guessing about what you actually did.
Negotiable: The reviewer has a legitimate underlying concern, but the specific fix they suggest is not the only (or best) option. You can address the concern without doing precisely what was asked. The classic case: "You should run a new experiment." Maybe a reanalysis of existing data addresses the same worry.
Misunderstanding: The reviewer misread or misunderstood something. This is still your problem — if an expert reader in your field misinterpreted the text, so will others. Correct the misunderstanding in your response and fix the writing that caused it. Never respond to a misunderstanding without also revising the manuscript to prevent it.
Out of scope: The reviewer is asking you to write a different paper. This happens, and it is more common than it should be. You can decline these requests, but the declination must be justified — explain why the requested change falls outside the paper's stated contribution, and acknowledge it as a direction for future work.
For a printable version of this categorization framework integrated into a full revision checklist, see our revise and resubmit guide.
Step 3: Prioritize by Impact on the Accept/Reject Decision
Not all reviewer comments carry equal weight. Some are gatekeepers — if you do not address them, the paper is dead regardless of everything else you do. Others are cosmetic suggestions that an editor would not reject the paper over. Your revision time is finite (usually 60–90 days for major revisions), and spending it on the wrong priorities is a common and avoidable failure mode.
Prioritize in this order:
- Structural and methodological concerns — these take the most time and carry the most weight in the acceptance decision. If a reviewer questions your sample selection, your statistical approach, or your experimental design, this is where your first week goes.
- Requests for new analyses or evidence — start these immediately, because they may involve running computations, re-analyzing data, or producing new figures. Waiting until week three to begin these guarantees a last-minute crisis.
- Framing and argumentation — how you position your contribution, what you claim and do not claim, how you discuss limitations. These changes are intellectually demanding but not time-consuming to execute.
- Clarity and writing quality — sentence-level edits, paragraph reorganization, improved figures and tables. Important, but lower priority than the structural issues above.
- Minor corrections — typos, formatting, missing references. Do these last.
The error to avoid is working bottom-up. If you spend week one polishing prose and fixing citations, then discover in week three that the new robustness analysis the reviewer requested produces unexpected results, you have left yourself no room to think.
Step 4: Write the Point-by-Point Response
The standard format for responding to peer review comments is not optional in most fields. For each reviewer comment, the entry looks like this:
Reviewer 1, Comment 3: [Quote or faithful paraphrase]
Response: [What you did and why]
Changes in manuscript: [Section, page, line numbers]
Three principles govern the quality of each response:
Be specific. The sentence "We agree and have revised accordingly" is a failure of communication, not an act of concision. Write instead: "We agree that the sample size justification was insufficient. We added a formal power analysis (Section 3.1, lines 112–118) showing that n=340 provides 80% power to detect a medium effect size (d=0.5) at α=0.05, confirming that the study is adequately powered for our primary hypothesis."
Lead with agreement when possible. Even when you are about to disagree, opening with an acknowledgment of what is valid in the comment costs nothing and signals good faith. "The reviewer raises an important point about external validity" is true even if you then explain why external validation data are unavailable.
Provide evidence, not assertions. "We believe our approach is correct" is an assertion — and a weak one. "Our approach follows the recommendation of [Smith et al., 2023], who demonstrated that method Y outperforms method X for datasets with these characteristics (see their Table 3)" is evidence. Evidence persuades; assertions irritate.
For ready-to-use templates that you can drop your individual responses into, see our rebuttal letter template.
How to Handle Contradictory Reviewers
Reviewer 1 says your paper is too long. Reviewer 2 says you need more detail. Reviewer 1 praises your theoretical framework. Reviewer 3 wants it deleted. This situation is stressful, but it is not unusual — and editors expect it.
Flag the contradiction explicitly. Write it out: "We note that Reviewer 1 and Reviewer 3 offer opposing suggestions regarding the theoretical framework (Reviewer 1: retain and expand; Reviewer 3: remove entirely). We have attempted to balance both perspectives by…" Pretending the contradiction does not exist insults everyone's intelligence.
Look to the editor's letter for prioritization signals. The editor often tips their hand. If the decision letter says "please pay particular attention to Reviewer 1's methodological concerns," that is a hierarchy, not a suggestion. Follow it.
Find the underlying convergence. In many cases, contradictory surface-level suggestions point to the same underlying problem. "Too long" from Reviewer 1 and "needs more detail" from Reviewer 2 might both be solved by cutting the weakest sections and strengthening the most important ones. The reviewers diagnosed the same issue (uneven depth) from opposite directions.
Be transparent about the trade-off. When no synthesis is possible, say so: "Given the opposing recommendations, we chose to [action], because [reason]. We are happy to adjust this if the editor prefers a different approach." This puts the decision where it belongs — with the editor who has read all the reviews.
How to Disagree with a Reviewer Without Getting Rejected
You are allowed to disagree. Editors expect it, and a response that agrees with everything (including mutually contradictory comments) actually signals a lack of critical engagement. But how you disagree determines whether the disagreement is received as confidence or as arrogance.
The Formula That Works
- Acknowledge the comment and the concern beneath it
- Explain your reasoning, backed by evidence (citations, data, logical argument)
- Offer something — a clarification in the text, a partial analysis, a new sentence that addresses the concern even if you did not make the requested change
- Defer when appropriate: "We are happy to make this change if the editor feels it is warranted"
Before/After: Disagreeing with a Methodological Suggestion
Reviewer comment: "The authors should use method Z instead of method Y. Method Y has known biases."
Weak response:
We disagree. Method Y is widely used and appropriate for our data.
This is an assertion without evidence. "Widely used" is an appeal to popularity, not a defense. The reviewer will not be persuaded, and the editor has no basis for siding with you.
Strong response:
We appreciate the reviewer's concern about potential biases in method Y. We selected method Y over method Z for two reasons: (1) method Z requires stationarity assumptions that do not hold for our dataset (see diagnostic tests in new Appendix C), and (2) recent work by [Chen & Park, 2024] demonstrated that method Y's bias is negligible for sample sizes above n=200, which applies here. To address the concern directly, we added a robustness check using method Z in Appendix D — the results are qualitatively identical (new Table D1), which supports the validity of our primary analysis. We added a note in Section 3.2 (line 134) referencing this robustness check.
Before/After: Handling a Request You Cannot Fulfill
Reviewer comment: "The authors should validate their model on a second dataset from a different geographic region."
Weak response:
We do not have access to another dataset.
Factually true, strategically disastrous. This reads as an unwillingness to engage with a legitimate concern about generalizability.
Strong response:
This is an excellent suggestion that would strengthen the paper's generalizability claims. Unfortunately, datasets with comparable variables for a different geographic region are not currently available in the public domain, and new data collection falls outside the scope of this revision. We addressed this concern in three ways: (1) we added a cross-validation analysis using a held-out 30% subset of our data (new Section 4.4, lines 245–260), (2) we expanded the Limitations section (lines 312–320) to discuss geographic generalizability explicitly as a direction for future work, and (3) we compared our coefficient estimates with those reported by [Rivera et al., 2023] for a European sample (new Table 5), finding broadly consistent patterns.
Before/After: Reviewer Wants Something Removed
Reviewer comment: "The literature review is too extensive and detracts from the paper's contribution."
Weak response:
We believe the literature review is necessary to contextualize our work.
Strong response:
We take this point seriously and have shortened the literature review from 2,400 words to 1,600 words. Specifically, we removed the review of tangentially related work on [topic] and condensed the discussion of [second topic] into a single summary paragraph. The material that remains directly supports the development of our hypotheses in Section 3. We retained the subsection on [core topic] because it introduces the theoretical gap that our study addresses — without it, the research question in Section 3.1 would lack sufficient motivation.
Managing the Revision Timeline
For major revisions, you typically have 60–90 days. This feels generous until you realize that new analyses can take weeks, co-author feedback cycles are unpredictable, and the response letter alone requires substantial focused time. A realistic timeline for a major revision looks something like this:
- Days 1–3: Read reviews, process emotions, begin categorization
- Days 4–7: Complete categorization, build revision plan, identify new analyses needed
- Days 8–30: Execute major revisions (structural changes, new analyses, rewritten sections)
- Days 31–45: Draft the point-by-point response letter
- Days 46–55: Revise response letter, align with manuscript changes, check for consistency
- Days 56–60: Co-author review of both documents, final proofreading, submission
The mistake that derails the most revisions is underestimating the time the response letter requires. It is not a summary of what you did — it is a persuasive document that requires its own drafting, revision, and polishing cycle. Budget at least 10–15 days for it.
For a detailed checklist organized around this timeline, see our revise and resubmit guide.
What Happens When You Submit: The Second Round
After resubmission, one of several things happens. The editor may accept without further review (common for minor revisions). The editor may send the paper back to the original reviewers (standard for major revisions). Or, in some cases, the editor may invite a new reviewer — which can feel like starting over but usually indicates the editor needs a tiebreaker opinion.
In the second round, reviewers are evaluating one thing above all: did you take their comments seriously and respond with substance? They are not re-reviewing the paper from scratch (usually). They are checking whether their concerns were addressed. This is why the response letter matters so much — it is the document they read first, and it sets the frame for their evaluation of the revised manuscript.
A well-structured, specific, evidence-based response to peer review comments — written with the kind of care you would put into the paper itself — is the single highest-leverage investment you can make in the revision process.
Facing 30+ reviewer comments and a 60-day deadline? ReviewPanel.ai analyzes your manuscript alongside every reviewer comment and generates a structured, point-by-point response with specific edit suggestions. One paper, one price — $29.