How to Respond to Reviewer Comments (Without Losing Your Mind)

Decision cue: If you need a yes/no submission call today, compare your draft with 3 recent accepted papers from this journal and only submit when scope, methods depth, and claim strength line up.

Related: How to choose a journal • How to avoid desk rejection • Pre-submission checklist

You got the decision email. Major revisions. Or maybe minor. Either way, there's a document attached with reviewer comments, and now you have to respond to every single one of them.

This part trips up a lot of people. The science might be solid. The revisions might be straightforward. But the response letter? That's where papers go to die.

I've seen authors tank their own acceptances with defensive responses, miss obvious signals from reviewers, or bury good revisions under walls of text that no editor wants to read. I've also seen papers with serious problems get accepted because the authors handled the response well.

Your response letter matters as much as your revisions. Maybe more.

The Structure That Works

Every successful response letter uses the same format. It doesn't vary by discipline, journal tier, or how many reviewers you have. Here's the structure:

Preamble (one short paragraph): Thank the editor and reviewers for their time, summarize that you've addressed all comments, and note that the manuscript has been revised accordingly.

Reviewer sections (one per reviewer): Label them clearly , "Response to Reviewer 1", "Response to Reviewer 2", etc. Within each section, address every single comment in numbered order.

Each response follows this pattern:

1. Quote the reviewer comment verbatim
2. State what you did in response
3. Show the revised text (or explain why no change was needed)

That's the whole thing. Editors don't need literary craft here. They need to be able to verify, in under five minutes, that every comment got a real response. Make that easy for them.

The Format for Each Response Item

Here's what a good individual response looks like:

Reviewer 2, Comment 3: The authors should verify that the control group received the same vehicle concentration as the treatment group.

Response: The reviewer is correct that this wasn't explicitly stated. We apologize for the ambiguity. Both groups received identical vehicle concentrations (0.1% DMSO). We have added the following sentence to the Methods section (line 142): "Vehicle controls received 0.1% DMSO, matching the highest concentration used in treatment conditions."

That response does everything it needs to: acknowledges the comment, states the clarification, shows exactly where the change appears in the manuscript.

What it doesn't do: argue, apologize excessively, or pad the response with context the reviewer didn't ask for.

When You Agree With the Reviewer

This is the easy case. Quote the comment, say "We agree" or "The reviewer raises a valid point," explain what you changed, and cite the line number where the change appears. Keep it brief.

Don't thank reviewers for every single comment. One genuine expression of appreciation in the preamble covers it. Thanking them repeatedly within the response reads as sycophantic and slows down the editor trying to process your letter.

When You Disagree With the Reviewer

This is where most authors go wrong. They either cave completely (making changes they don't think are scientifically warranted) or push back defensively in ways that irritate editors.

The approach that works: address the underlying concern even if you disagree with the proposed solution. Almost every reviewer request has a legitimate concern underneath it. Find that concern, address it, and offer an alternative if you're declining the specific request.

Here's the language that works:

"We appreciate the reviewer's concern about [X]. On reflection, we believe the issue is that [framing problem in our original text] may have created ambiguity about [Y]. Rather than [requested change], we have [alternative change] because [reason]. We believe this directly addresses the reviewer's concern while maintaining [scientific principle you're protecting]. See revised [section] at line [N]."

This approach does three things: it shows you understood the concern, it offers a genuine alternative, and it points the editor to where the change is. Editors can almost always get behind this framing even if the specific change differs from what the reviewer asked for.

Declining a Reviewer Request

You can decline a reviewer request. You should decline requests that would make your paper scientifically weaker, that ask for experiments outside the scope of the current study, or that would require years of additional work for a marginal improvement.

When declining, always do two things:

1. Explain your reasoning clearly and without condescension
2. Offer something in return , a limitation paragraph, a clarifying sentence, a footnote acknowledging the gap

Here's an example of a refusal that works:

"The reviewer suggests including additional validation in a second animal model. While we agree this would strengthen the generalizability of the findings, this experiment would require approximately 12 months of additional work and is beyond the scope of the current paper. We have added the following to the Limitations section (line 287): 'The current findings are limited to one preclinical model; validation in additional systems remains an important direction for future work.' We believe this acknowledges the concern explicitly without delaying publication of the primary finding."

Handling Conflicting Reviewer Comments

If Reviewer 1 asks you to shorten the introduction and Reviewer 2 asks you to expand it, you can't satisfy both. Here's how to handle it:

Acknowledge the conflict explicitly. Don't silently favor one reviewer over the other , the editor will notice.

"Reviewers 1 and 2 offered conflicting guidance on the introduction length. Reviewer 1 requested condensing (Comment 4), while Reviewer 2 requested additional context (Comment 2). In response, we have [choice you made] because [reason]. We believe this approach addresses Reviewer 2's concern about [X] while respecting Reviewer 1's point about [Y]. See revised introduction at lines 18-47."

Editors deal with conflicting reviewer comments constantly. They don't expect you to satisfy mutually exclusive requests. They expect you to acknowledge the conflict, explain your reasoning, and make a defensible call.

The Hostile Reviewer

Occasionally a reviewer's tone is dismissive, condescending, or unfair. It happens. Here's what to do:

Separate the tone from the substance. Read through the hostile phrasing and ask: what is the actual scientific concern? Is there one? Address the scientific concern if there is one. If the comment is pure tone with no scientific substance, acknowledge it briefly and move on.

If the review contains factual errors, correct them politely. Frame the correction as a presentation ambiguity, not a reviewer mistake , even when the reviewer is clearly wrong.

"This comment may reflect ambiguity in our original description. To clarify: [correct information]. We have revised [section] to make this explicit (lines 156-159)."

Never attack the reviewer in your response letter. The editor chose that reviewer, and questioning their judgment doesn't help your case.

In genuinely abusive cases , personal attacks, clear bias, or reviews that appear designed to prevent publication for competitive reasons , contact the editor directly, separately from your formal response letter. Be measured and factual. Flag the specific language, explain why it's problematic, and let the editor decide. Don't make accusations.

What the Editor Is Actually Looking For

The editor reads your response letter with one question in mind: did the authors take this seriously?

Taking it seriously means addressing every comment, including the minor ones. It means explaining your reasoning when you make a different call than the reviewer requested. It means not dismissing concerns with a sentence when a paragraph is warranted.

Editors are experienced at spotting responses that look thorough but aren't. A letter that runs 40 pages with two-sentence responses to every comment is less convincing than a 10-page letter that engages substantively with the six comments that actually matter.

The response letter doesn't need to be long. It needs to be complete and intellectually honest.

The Timeline

Most journals give 60-90 days for major revisions and 2-4 weeks for minor revisions. These are real deadlines , if you miss them without requesting an extension, your paper may be treated as a new submission.

If you need more time, ask early. Most editorial offices are flexible if you contact them before the deadline and explain the situation. Asking for 30 extra days two weeks before a deadline is easy to grant. Asking for an extension the day after your deadline has passed is awkward for everyone.

Don't rush a major revision to submit in three days. Editors know how long additional experiments take, and a three-day turnaround on a major revision raises questions about whether you actually did the work.

Common Mistakes That Kill Acceptances

Skipping minor comments: Reviewers remember what they asked. If you respond to 8 of 10 comments and skip two, the editor will notice , especially if one of the skipped comments was the reviewer's main concern.

Wall-of-text responses: Long responses that bury the actual answer are hard for editors to process. Lead with what you did, then explain your reasoning. Don't make the editor read 300 words before finding out whether you made the change.

Generic thanks for every comment: "Thank you for this insightful comment" repeated 15 times reads as filler. One genuine expression of appreciation in the opening paragraph is sufficient.

Changing things without noting it: If you made a change in response to a comment, say so explicitly and cite the line number. Don't make the editor hunt for it.

Not tracking changes in the manuscript: Submit a clean version and a tracked-changes version. Editors use the tracked version to verify that responses match actual manuscript changes. If you describe a change but it doesn't show up in tracked changes, that's a problem.

The Covering Letter to the Editor

Your response letter goes to reviewers. Your cover letter to the editor is a short separate document , typically one paragraph , that summarizes the revision at a high level.

The editor's cover letter should:

• Confirm that all reviewer comments have been addressed
• Flag any major changes made to the paper
• Note anything the editor should be aware of (one declined request, a substantial new analysis, etc.)

Keep it under 200 words. The detailed justification is in the response letter. The editor's cover letter is a navigation aid, not a second argument for your paper.

The Bottom Line

A revision is not a second chance to impress. It's a logistical task: show the editor and reviewers that you took their concerns seriously, made defensible choices, and addressed every single comment. The papers that fail at the revision stage usually fail not because the science is wrong, but because the response letter was incomplete, defensive, or hard to follow.

The format is simple. The execution requires care and patience. Both are within reach on every paper.

See also

• Major vs. minor revision: what each actually means
• How to write a rebuttal letter to journal reviewers
• Pre-submission checklist

Sources

• International Committee of Medical Journal Editors (ICMJE) , author responsibilities during revision
• Published editorial guidance from Nature, Cell, and PLOS journals on revision expectations
• Pre-Submission Checklist , 25-point audit before your first submission