Reviewer2

Revise and Resubmit: Step-by-Step Strategy for R&R

Revise and Resubmit: Step-by-Step Strategy for Your R&R Decision

An R&R is good news, even when it doesn't feel like it. The editor has decided your paper is worth the journal's continued investment. The question is how to convert that conditional interest into an acceptance — systematically, without losing scope, and without burning weeks on revisions that don't move the needle.

What an R&R Actually Means

Journals distinguish between major revision and minor revision, though practices vary. Understanding the distinction shapes your strategy.

Minor revision generally means the core paper is solid. The requested changes are clarifications, additional analysis, or language corrections. You typically have 4-8 weeks. The expectation is that an acceptance is likely if you comply responsibly.

Major revision is more significant. The paper needs substantial changes: new analyses, restructured arguments, expanded methodology, or additional literature engagement. You typically have 3-6 months. Acceptance is not guaranteed — the revised manuscript may go back to the same reviewers, or new reviewers may be brought in. Some journals allow two rounds of major revision; most do not.

A few journals use "revise and resubmit" to mean something closer to a rejection with an invitation: they would consider a substantially rewritten paper but make no commitment. Read the decision letter carefully for signals.

Step 1: Read the Decision Letter Before the Reviews

The editor's decision letter summarizes what they consider the most important concerns. This matters because: (1) not all reviewer requests carry equal weight, and (2) the editor may explicitly say that one reviewer's concerns are more central than the other's. Some editors list the changes they consider necessary for acceptance.

If the editor identifies specific issues as dealbreakers, those get addressed first, most thoroughly, and most prominently in your response.

Step 2: Triage the Reviews

Create a spreadsheet or document with four columns: Comment ID, Reviewer request, Required action, Priority. Work through every comment and assign it one of three priority levels:

This triage determines your revision schedule. High-priority items get addressed before anything else. If a high-priority item turns out to be impossible to address fully (a new experiment you cannot run), you need to know early so you can plan an alternative and address the limitation honestly.

Step 3: Decide What You Will Not Do — Before You Start

Every major revision involves some reviewer requests you cannot or should not fulfill. Identify them at the triage stage:

For each "no," you need a response. See [how to respond when reviewers ask for more experiments you can't do](/guides/reviewer-asks-more-experiments) for detailed guidance. The key principle: you need an alternative action, not just a refusal.

Step 4: Draft Your Response Letter First

Counterintuitive but effective: write the response letter before you revise the manuscript. Here is why.

When you revise first, you tend to make decisions about scope and substance in isolation, then write a response that describes what you did. When you write responses first, you are forced to articulate what the reviewer's concern actually is, why your planned action addresses it, and what the argument is if you disagree. This often reveals that a planned change is insufficient — or that a simpler intervention would work.

Work through every comment in order. Write a rough draft of each response. Some will be easy; some will require you to work out the logic before you can state it. The manuscript revisions follow from the responses, not vice versa.

Step 5: Revise the Manuscript with Tracking

Make all changes with tracked revisions (or use a versioning system). This matters for two reasons: you can check your work against the response letter more easily, and some journals require you to submit a tracked-changes version alongside the clean manuscript.

As you make each change, note the exact page and line numbers in your response letter. These numbers shift as you edit, so do this pass last — update page/line references after the manuscript is finalized.

Step 6: Write the Response Letter (Final Version)

The opening summary is brief but important. Do not say "we have addressed all reviewer comments." Instead, name the most significant changes:

> "In this revision, we have (1) added a mixed-effects regression analysis to address the repeated-measures concern raised by Reviewer 1 (Section 3.3), (2) restructured the Introduction to engage more directly with the affordance theory literature (pages 2-4), and (3) added a Limitations section addressing potential selection bias (page 20). We believe these changes substantially strengthen the manuscript."

For the full format, see the [response to reviewers template](/guides/response-to-reviewers-template).

Step 7: Write a New Cover Letter

The cover letter for the revised submission is not the same as your original submission cover letter. It should briefly note that this is a revised manuscript, reference the manuscript ID, and mention 1-2 of the most significant improvements. Keep it to a paragraph. The response letter is where the detail lives.

Do not re-argue your case in the cover letter. If an editor had doubts about the paper, reading them again in the cover letter will not help. See [response letter vs cover letter](/guides/response-letter-vs-cover-letter) for what each document is actually for.

Step 8: Internal Review Before Submission

Before submitting, have at least one co-author read the response letter against the original reviews without looking at your manuscript. Their job: identify any comment that appears to be addressed in the response letter but is not visibly addressed in the manuscript, and any manuscript change that does not correspond to a response.

This catches two common errors: (1) promising changes you forgot to make, and (2) making changes that have no corresponding response.

Timeline Management for Major Revisions

A 3-month deadline for major revisions is tight if you have competing obligations. Rough allocation:

Most journals will grant an extension if you ask before the deadline and give a specific new date. Do not let the deadline pass and then ask for an extension.

When the Revised Paper Gets Rejected Anyway

A rejection after R&R is frustrating but informative. Read the new decision letter carefully: did you miss a concern the editor considered essential? Did new reviewers raise entirely different objections? Is there a remaining fundamental issue the reviews have been pointing to across multiple rounds?

If you believe the rejection was based on a misreading of your revision or factually incorrect reviewer claims, you may have grounds for an appeal. See [when and how to appeal a journal rejection](/guides/rebuttal-letter-journal).

Worked Example: Major Revision Triage

Below is a partial triage for a paper in social psychology:

| ID | Comment | Action | Priority |

|----|---------|--------|----------|

| R1.1 | Editor note: primary concern | Rerun analysis with covariates | High |

| R1.2 | Ceiling effects in Exp 2 RT data | Sensitivity analysis excluding high-accuracy participants | High |

| R2.1 | Literature gap: affordance theory | Add 2 paragraphs to Introduction | Medium |

| R2.2 | Sample demographics table missing | Add Table 1 | Low |

| R1.3 | Replicate in US sample | Cannot; add to Limitations and discuss in response | High (must plan alternative) |

The single item marked "cannot" (R1.3) requires the most planning even though it involves no manuscript change — because the response must be substantive.

Using Tools to Move Faster

Working through 30 reviewer comments while also running new analyses and restructuring sections is one of the most time-compressed activities in academic work. [Reviewer2](/#demo) can draft response paragraphs for individual comments, which is useful at the response-drafting stage when you need to generate a first version of each response before refining it. The free demo lets you test it on a single comment before committing.

More guides