Rebuttal Letter (Response to Reviewers)

A rebuttal letter is a negotiation document. The authors are negotiating with three readers: the editor (who decides whether the manuscript is publishable), the reviewers (who advise the editor), and the future readers of the published article (who will judge the strength of the claims). A successful rebuttal acknowledges the strongest version of each reviewer concern, addresses it with evidence or reframing, and protects the manuscript's central claims. A failed rebuttal either capitulates to every request (and dilutes the manuscript) or fights every comment (and antagonizes the editor). This skill encodes the architecture, the tone discipline, the handling of conflicting reviewers, and the framing of polite disagreement.

When to use

• Responding to a journal's first-round decision (major or minor revision).
• Responding to a rejection-with-invitation-to-resubmit when the editor has signaled that the work is potentially publishable.
• Responding to a transfer-of-review from a previous journal.
• Preparing a re-review package for a revised manuscript at a transferred journal.

When NOT to use

"

• For an outright desk-rejection with no review (use the cover-letter "out of scope" response).
• For comments from a preprint server discussion (use the platform's comment-reply format).
• For internal co-author review of a draft (use a different tone; co-author review is collegial, not negotiated).

Prerequisites

• Received the journal's decision letter with all reviewer comments compiled.
• A clean copy of the revised manuscript (with tracked changes if required).
• A point-by-point response document (see related skill: ors-scientific-writing-response-to-reviewers).
• Co-author agreement on the response to each point, especially the contested points.
• Time and data to address the substantive requests; do not commit in the letter to experiments that have not been run.

Core workflow

1. Read the decision letter twice before drafting

The first read is for emotional decompression. The second read is for structure. The decision letter tells the authors:

• The editor's overall assessment (publishable with revisions, reject, reject with invitation to resubmit).
• The decision category (major revision, minor revision, reject, accept).
• The deadline.
• The list of specific revisions the editor requests.

Authors who draft the rebuttal before the second read often misread the editor's framing and write the wrong letter.

2. Categorize each reviewer comment

Before drafting, tag each comment in one of four categories:

The categories prevent two failure modes: (a) agreeing to every request and diluting the manuscript, and (b) fighting every comment and antagonizing the editor.

3. Draft the response in a point-by-point format

The response document has one section per reviewer, with one subsection per comment. Each subsection has:

• The reviewer comment (verbatim or summarized).
• The author's response.
• The location of the change in the revised manuscript (page, line, figure).

See ors-scientific-writing-response-to-reviewers for the full format.

4. Frame new experiments as additions, not corrections

When a reviewer requests an experiment that the authors have now done, the framing matters. Three patterns:

Pattern A: "We have now done this"

"We thank Reviewer 2 for suggesting this analysis. We have now performed [experiment] on [n=X] additional samples, and the results confirm our original finding. The new data are presented in Figure 3E and discussed on page 14, lines 5-12."

Pattern B: "We agree this strengthens the manuscript; we have added the analysis"

"We agree that this analysis strengthens the manuscript. We have added [analysis] to the Methods (page 9, lines 18-22), the Results (page 13, lines 3-11), and Figure 4."

Pattern C: "We respectfully note that this is outside the scope of the current manuscript"

"We agree this is an interesting future direction. We respectfully note that the requested experiment requires [reason: additional patient cohort / 6-month follow-up / new transgenic line] and is therefore beyond the scope of the current revision. We have added a sentence to the Discussion (page 19, line 23) highlighting this as a priority for future work."

5. Handle conflicting reviewers explicitly

When Reviewer 1 asks for X and Reviewer 2 asks for the opposite, the editor is watching how the authors handle the conflict. The right approach:

• Address both comments separately in the response.
• Explain the decision rule: which evidence supports which change.
• If a third path resolves both, propose it: "We have taken a middle path that addresses both concerns: [explanation]."

Do not pit reviewers against each other. The editor reads the response; the reviewers do not see each other's comments in most journals.

6. Close the letter with a courteous summary

The closing paragraph of the letter is the last thing the editor reads. It should:

• Restate the central claim of the manuscript in one sentence.
• Summarize the major improvements in the revision (new analyses, new figures, restructured discussion).
• Reaffirm the fit with the journal.
• Thank the editor and reviewers.

Code patterns

Response document architecture

Response to Reviewers
Manuscript ID: [ID]
Manuscript title: [Title]
Corresponding author: [Name]

We thank the editor and the reviewers for their thoughtful
comments. We have addressed each comment below. The revised
manuscript uses [tracked changes / redline / clean copy]; the
page and line numbers refer to the clean revised version.

Summary of major changes:
1. New Figure 4E showing [result] on n=X additional samples.
2. Restructured Discussion, with explicit Limitations
   subsection (page 18, lines 12-25).
3. Added [analysis method] to Methods (page 9, lines 4-9).
4. Revised title to [new title] to reflect the new finding.

Reviewer 1
Comment 1: "[verbatim reviewer comment]"
Response: [our response, in two short paragraphs]
Change in manuscript: page X, line Y; Figure Z.

Comment 2: ...

Reviewer 2
Comment 1: ...

Reviewer 3
Comment 1: ...

We thank the editor and reviewers again for their time, and
we look forward to the editor's decision on the revised
manuscript.

Polite disagreement: linguistic repertoire

The response document is a high-stakes rhetorical situation. The following phrasings are useful.

Worked example: "Reviewer is wrong, with evidence"

Reviewer 2, Comment 4: "The authors claim that METTL3 is required for temozolomide resistance, but they only show a knockdown. A rescue experiment with a re-introduced METTL3 would strengthen the claim."

Response: We thank the reviewer for this suggestion. We have now performed a rescue experiment. METTL3 was knocked down using two independent shRNAs in temozolomide-resistant U87-MG cells, and a shRNA-resistant METTL3 cDNA was re-expressed. The re-expression of METTL3 restored temozolomide resistance in the knockdown cells, as shown in the new Figure 3F. The revised text on page 11, lines 14-19 describes the rescue. These data confirm that the temozolomide-resistant phenotype is METTL3-dependent.

Worked example: "Reviewer is wrong, on principle"

Reviewer 3, Comment 1: "The authors claim a novel mechanism, but the m6A modification of MYC has been shown in three previous studies. This is not novel."

Response: We respectfully disagree with the reviewer's assessment. The three previous studies [refs 12, 14, 17] show that MYC mRNA can be m6A-modified in cell lines under specific conditions. Our study is the first, to our knowledge, to (i) show that this modification is enriched specifically in temozolomide-resistant patient-derived xenografts, (ii) demonstrate that the modification is METTL3-dependent in this context, and (iii) show that the modification is required for temozolomide resistance in vivo. The novelty is in the disease context and the functional requirement, not in the modification per se. We have clarified this in the revised Introduction (page 4, lines 18-23) and Discussion (page 17, lines 5-12).

Worked example: "Conflicting reviewers"

Reviewer 1, Comment 3: "The authors should include more patient samples to strengthen the conclusion."

Reviewer 2, Comment 5: "The patient sample size is already at the practical maximum for this rare-disease cohort; further expansion is not feasible and would delay publication."

Response: We thank both reviewers for raising this important point. We agree with Reviewer 2 that the sample size is at the practical maximum for the available cohort. To address Reviewer 1's concern about robustness, we have added a bootstrap analysis (n=10,000 resamples) showing that the METTL3-high vs. METTL3-low survival difference is robust (p<0.001 in 98.4% of bootstrap replicates; new Figure 4B). The bootstrap analysis is now described on page 12, lines 9-15.

Worked example: "We have now done this"

Reviewer 1, Comment 2: "Did the authors check that the m6A effect is METTL3-specific, and not METTL14-dependent?"

Response: We thank the reviewer for raising this important specificity question. We have now performed parallel knockdown experiments with METTL14 shRNAs. As shown in the new Figure 3G, METTL14 knockdown does not phenocopy METTL3 knockdown in temozolomide-resistant cells, confirming that the resistance is METTL3-specific. The new data are described on page 11, lines 22-28.

Worked example: "Experiment not feasible in this revision"

Reviewer 2, Comment 6: "An in vivo experiment with a METTL3 inhibitor in a syngeneic glioblastoma model would be a major advance."

Response: We agree this would be a valuable addition. We respectfully note that an in vivo experiment of this kind requires [reason: 6-month breeding of a new conditional Mettl3-flox × Nestin-Cre line, followed by intracranial implantation and survival follow-up]. The minimum time to generate these data is 9-12 months, which is beyond the revision timeline. We have added this as the first item in the Future Directions paragraph of the Discussion (page 19, lines 5-10).

Common pitfalls

Validation

A rebuttal passes validation when:

• Every numbered comment from every reviewer has a numbered response.
• The response is paired with a manuscript location (page and line, or figure).
• The major changes are summarized in a 4-6 bullet list at the top.
• The tone is respectful throughout, including in cases of substantive disagreement.
• The language discipline ("we respectfully disagree," "we have now done this") is consistent.
• Conflicting reviewers are addressed with a clear decision rule.
• The cover letter is updated to reflect the revised manuscript.
• The clean copy, the marked copy, and the response document are all attached.
• The corresponding author has read the response document end-to-end and signed off on the contested points.

Open alternatives

For commercial reference and language tools, the open alternatives are:

The rebuttal document itself is plain text/Markdown; no commercial tool is required.

References

• ICMJE Recommendations. icmje.org/icmje-recommendations.pdf
• Nature peer-review policy. nature.com/nature-portfolio/editorial-policies/peer-review
• eLife peer-review model. elifesciences.org/peer-review
• COPE discussion documents. publicationethics.org
• PLOS ONE peer-review policy. plos.org/peer-review
• F1000Research open peer-review platform (sample rebuttals in published history).
• BMJ Open peer-review history (sample rebuttals).

Related Skills

• ors-scientific-writing-response-to-reviewers — for the detailed format of the response document.
• ors-scientific-writing-cover-letter — for the cover letter that accompanies a revised submission.
• ors-scientific-writing-manuscript-structure — for the manuscript structure that the rebuttal defends.
• ors-scientific-writing-ai-disclosure-writing — for the AI/LLM usage statement that should be in the manuscript.
• ors-ethics-compliance-authorship-disputes — for handling authorship disagreements that surface during revision.

Changelog

• 1.0.0 (2026-06-10): Initial adaptation by Pradyumna Jayaram. Consolidated public guidance on rebuttal architecture (ICMJE, Nature/eLife/PLOS/BMJ peer-review policies, COPE), point-by-point format, polite-disagreement repertoire, and worked examples for the four common scenarios (fix, reframe, disagree-with-evidence, disagree-on-principle). No specific journal policies are quoted verbatim; all sources are publicly accessible.