How to Respond to Reviewer Comments Without Tanking Your Resubmission

A "Major Revision" decision is good news that feels like bad news. The editor wants the paper. They also want you to convince them, on paper, that the reviewers' concerns will be answered. The response letter does that work. Editors read it before they reread the manuscript, and many decide acceptance or further review based on the letter alone.

This guide covers the format journal editors expect, three response patterns you can reuse, and the mistakes that turn a fixable revision into a desk rejection.

#Read the Decision Letter First

Before opening the manuscript, sit with the decision letter for an hour. Then leave it overnight.

The editor's note is the part that matters most. A short paragraph from the editor often names the one or two issues that will decide the next round. Authors spend their effort on the longest reviewer comment instead of the one the editor flagged. Do not be that author.

When you come back to the reviewer comments, sort them into four buckets:

• Fix and confirm. Typos, citation errors, small clarifications. Address them, mark them done.
• Substantive but doable. New analyses, restructured sections, added context. Plan the work.
• Substantive and contested. A reviewer wants something you believe is wrong or out of scope. Plan the rebuttal.
• Conflicting between reviewers. Note them, then ask the editor for guidance if the conflict is real.

The bucket determines the response pattern, not your mood about the comment.

#The Format Editors Expect

A response letter has two parts: a short note to the editor, then a numbered point-by-point response to each reviewer.

The opening paragraph thanks the editor and reviewers, names the manuscript ID, and summarizes the major changes in three or four sentences. Editors skim this. Make it count.

The point-by-point section reproduces every reviewer comment verbatim, then your response, then the changed text from the manuscript. Number the comments by reviewer: R1.1, R1.2, R2.1, and so on. Most journals want this format. Some require it.

A clean entry looks like this:

R1.3. Reviewer 1 wrote:
"The sample size of 50 seems low for the claims being made.
Was a power analysis performed?"

Response:
We thank the reviewer for raising this. A priori power analysis
(G*Power 3.1) showed that 48 participants provided 80% power
to detect a medium effect (d = 0.5, alpha = .05). We have added
the calculation to the Methods.

Revised text (Methods, p. 6, lines 142-147):
"Sample size was determined by a priori power analysis..."

Three things matter in that block. The reviewer's words appear unchanged, so they can find them. The response is concrete, not "we have addressed this." The revised text appears in the letter, so the editor does not have to hunt for it.

Refer to reviewers in the third person: "The reviewer is correct that..." rather than "You are correct that..." The letter is addressed to the editor, who will forward your response back to the reviewers. Third person keeps the tone collegial and lets the editor read it cleanly.

#Three Response Patterns You Can Reuse

Almost every reviewer comment falls into one of three response shapes. Knowing them in advance will save you hours of staring at the screen.

#Pattern 1: Agree and Implement

The default for any comment you can act on. Acknowledge, describe the change, and quote the new text.

We agree with the reviewer's point. The original framing
overstated the causal claim. We have softened the language
in the Discussion (p. 14, lines 312-318) and now describe
the relationship as associative.

Revised text:
"Our results suggest that X is associated with Y, though
the cross-sectional design does not permit causal inference."

Two failure modes here. First, claiming changes you did not make. Reviewers check. Second, adding the change to the response letter without updating the manuscript itself. If the reviewer wanted an explanation, the next reader of the paper will want it too.

#Pattern 2: Partial Agreement

You accept the spirit of the comment but need to scope what you can do. Common when reviewers ask for experiments you cannot run.

The reviewer raises an important point about generalizability.
A multi-site replication would strengthen the work, but is
beyond the scope of this revision given our IRB approval is
limited to the original site. We have added a paragraph to
the Limitations (p. 16) naming this constraint and proposing
the multi-site design as future work.

Concede the substance, name the constraint, and convert the comment into a manuscript change. A flat "we cannot do this" leaves the editor to decide whether your refusal is reasonable. A scoped concession does that work for them.

#Pattern 3: Respectful Disagreement

You believe the reviewer is wrong, missed something, or asked for a change that would weaken the paper. This response goes worst when authors get defensive.

The reframe that works: assume the reviewer's confusion is your manuscript's fault, then fix the manuscript so no future reader makes the same mistake.

We thank the reviewer for this comment, which suggests our
original Methods section was unclear. We did not exclude
participants based on outcome scores; the threshold referenced
in the comment applies only to the screening phase. To prevent
this misreading, we have rewritten the relevant paragraph
(Methods, p. 7) to separate the screening and analysis criteria.

That response avoids the phrases that poison rebuttals: "the reviewer is incorrect," "as we clearly stated," and "obviously." Cut them on sight. If the reviewer misread your text, another reader will misread it too. Fix the manuscript and report the fix.

When you cannot agree at all, support the rebuttal with citations:

We respectfully disagree with the suggestion to use a
parametric test for these data. Shapiro-Wilk results
(W = 0.84, p < .001) indicate non-normality, and the
rank-based approach is recommended for this design
(Conover, 1999). We have added this justification to
the Methods (p. 8).

Let the evidence do the disagreeing. Your job is to deliver it without heat.

#The Mistakes That Sink Resubmissions

A short list of patterns that show up in rejected revisions:

"This has been addressed." Vague responses force editors to reread the manuscript to find the change. They will not. Quote the new text.

Cherry-picking comments. Authors sometimes respond to seven of nine comments and hope the other two go unnoticed. Editors notice. Address every comment, even minor ones, with at least a one-line "Corrected, p. 3, line 47."

Story drift. Adding new analyses without updating the abstract, introduction, and discussion to match. The new evidence has to flow through the whole paper, not just the results section.

Long rebuttal, unchanged paper. If the reviewer's confusion is worth a paragraph of explanation in the letter, it is worth a sentence of clarification in the paper.

Tone. "The reviewer clearly misunderstood..." has ended more reviews than weak data ever has. Read your letter aloud before submitting. If it sounds annoyed, rewrite it.

#A Workflow That Ships

Treat the revision as a triage exercise before you treat it as a writing one.

1. Print the decision letter. Read it twice.
2. Make a spreadsheet: comment number, reviewer, severity, response pattern, status.
3. Do the easy fixes first. Crossing off ten typo corrections in an hour builds momentum and shrinks the visible workload.
4. Block calendar time for the substantive comments. Treat them like analysis tasks, not writing tasks.
5. Draft the response letter as you go. Do not save it for the end.
6. Have a co-author read the letter cold before you submit. Anyone who has not been arguing with the reviewers in their head for two weeks will catch the lines that read as defensive.

The response letter is the paper editors read most carefully. Reviewers read it too, looking for whether you took them seriously. Take them seriously, on paper, and the second round usually goes faster than the first.

#How ManuscriptMind Helps

Before you submit the revision, run the revised manuscript through ManuscriptMind. Our analysis flags issues the reviewers raised that your changes did not answer, and surfaces new issues your revision may have introduced. Catching those before resubmission is the difference between an accept and a third round.

Upload your revised manuscript →

---

More on getting through peer review: 5 Common Methodology Issues That Get Manuscripts Rejected.