The Revise & Resubmit Playbook From Decision Letter to Acceptance

The revise and resubmit decision is the most emotionally complicated outcome in academic publishing. It is not a rejection, but it does not feel like success either. The journal is interested, genuinely interested, and the paper still is not ready. Everything that happens between "not ready" and "accepted" is where researchers either demonstrate that they can engage with hard feedback or reveal that they cannot.

Most R&R failures are scheduling failures and not scientific ones. The reviews sit unopened for three weeks. The new analysis starts in week six. The response letter gets written the night before the deadline, and the editor receives a revision that answers the easy comments thoroughly and the hard ones in one sentence. The timeline below exists to prevent exactly that. It assumes a 25-day working window inside a typical 60-day or 90-day deadline, which leaves slack for the analysis that breaks and the co-author who is at a conference.

The Emotional Arc of a Revise & Resubmit (and Why It Matters)

Before the timeline begins, one honest acknowledgment. Receiving a revise and resubmit decision triggers a predictable emotional sequence that almost every researcher experiences. First, relief that it was not rejected. Then, as you read the reviewer comments, a sinking feeling. Frustration, sometimes anger, at comments that feel unfair. And 24 to 48 hours later, reluctant recognition that several of those comments identify genuine weaknesses you were hoping nobody would notice.

This emotional arc is not a weakness to overcome. It is a normal response to having your work evaluated critically by strangers. What matters is that you do not act on the early-stage emotions. Responses drafted while you are still angry come out defensive and vague, and reviewers read defensiveness accurately. The playbook below builds the cooling-off period directly into the timeline. For the hardest version of this problem, the review that reads as hostile, see our Reviewer 2 survival guide.

Day 1: Read the Reviews. Close the Laptop. Sleep on It.

Read the decision letter and every reviewer comment once from beginning to end. Do not skim, and do not skip ahead to the comments you expect to be kind. Read the entire thing, including the parts that sting.

Then close your laptop and do something else. Go for a walk, cook dinner, call a friend. Anything that creates cognitive distance between you and the reviews will do. You are not being lazy. You are preventing yourself from making decisions about what to change and what to push back on under emotional conditions that distort judgment.

One productive thing is available on day one. Forward the decision letter and reviews to your co-authors with a short note. "Let's discuss this later this week. No rush." That single sentence sets the tempo for everyone else and stops a co-author from firing off a panicked reply at midnight.

Days 2–3: Categorize Every Comment. Build the Battle Plan.

Now read the reviews again. This second reading will feel different. The comments that seemed outrageous yesterday now look mostly like legitimate concerns, and one or two comments you initially accepted turn out to rest on a misreading of your Methods section.

Open a spreadsheet with four columns: Comment Number, Summary, Category, Priority. List every individual comment from every reviewer, including the ones buried mid-paragraph in a reviewer's general remarks. Assign each one a category (must-fix, negotiable, misunderstanding, or out-of-scope) and a priority score from 1 (blocks acceptance) to 3 (cosmetic). The full categorization framework is in our guide to responding to peer review comments.

What the comment table looks like when it is filled in

Here is a fragment from a real-shaped table for an empirical paper that received two reviews and a major revision decision:

• R1.2 Reviewer suspects the 2019 subsample drives the headline effect. Category: must-fix. Priority 1. Plan: rerun the main model excluding 2019, report both estimates in a new Table 4. Estimated 3 days.
• R1.5 Reviewer asks for a power calculation. Category: must-fix. Priority 1. Plan: compute minimum detectable effect, add to Section 3.2 and to the supplement. Estimated half a day.
• R2.1 Reviewer says the contribution "is not clearly differentiated from Petersen (2021)". Category: negotiable. Priority 1. Plan: rewrite the last two paragraphs of the introduction, add an explicit contrast table in Section 2. Estimated 2 days.
• R2.4 Reviewer claims we did not report attrition. Category: misunderstanding. Priority 2. Plan: attrition is in Appendix B, Table B3. Move the numbers into the main text at Section 3.1 and cross-reference the appendix. Estimated 1 hour.
• R2.7 Reviewer wants a second country in the sample. Category: out-of-scope. Priority 3. Plan: decline, explain the data licence covers one country, add to the future work paragraph. Estimated 1 hour.

Two things become visible the moment the table is filled in. The first is that the total estimated time is almost never what you guessed before you built it. The second is that the comments you dreaded are often the cheap ones, while the throwaway sentence in R2.1 is the one that will take a week.

From this table, write a revision plan: one document that states, for each comment, what you intend to do and roughly how long it will take. Send the plan to your co-authors before you start executing. The plan does two jobs. It stops you from spending three weeks on priority-3 changes, and it surfaces strategic disagreements early, when they are cheap to resolve, instead of late, when they are not.

Deciding what to contest

Not every comment deserves compliance. Contest a comment when you can show the reviewer is factually wrong about your paper, when the requested change would weaken the analysis, or when the request lies outside what the data can support. Concede everything else. In practice, most authors contest too much in round one and too little in round two, which is exactly backwards. Round one is where you still have room to argue, and round two is where the editor is looking for closure.

The test is simple. Write your objection in two sentences. If those two sentences need a third sentence of context to make sense, the reviewer probably had a point about clarity even if they were wrong about substance, and the right move is to fix the text and concede the framing.

Days 4–14: Execute Revisions Systematically

Start with the structural changes. If a reviewer asked for a new analysis, begin running it today. Not because it will take the full ten days, but because preliminary results sometimes surprise you, and surprises in week two are manageable while surprises in week eight are not.

Work in priority order:

1. Methodological and analytical changes. New sensitivity checks, revised analyses, additional data processing. These are the gatekeepers.
2. Structural revisions. Section rewrites, a reordered argument, major components added or cut.
3. Framing changes. Adjusted claims, an expanded limitations section, a sharper contribution statement.
4. Line-level edits. Clarity fixes, citations, figure revisions, terminology consistency.

The temptation to start with the easy changes is understandable and strategically wrong. Fixing typos feels productive. It does not move the paper toward acceptance. The hard changes determine the outcome, and they are the ones with a nonzero chance of failing, so they need the calendar slack.

Track every change as you make it. Keep a running document, or annotate the revision plan in place, and note every modification, where it sits in the manuscript, and which reviewer comment it answers. That document becomes the raw material for your response letter. Assembling it retrospectively, from memory and a diff, is dramatically harder than building it in real time, and it is where "we revised the manuscript accordingly" sentences come from.

When the new analysis does not go your way

Sometimes the sensitivity check the reviewer asked for kills your result. This happens more often than the published record suggests, and it is the single hardest moment in a revision.

Report it. Editors and reviewers are far more forgiving of an author who says "the reviewer was right, the effect is not stable outside the 2019 window, and we have rewritten the claim accordingly" than of an author who quietly omits the requested analysis. If you drop the analysis without comment, the reviewer who requested it will notice in round two, and at that point you have a credibility problem on top of a statistical one. Rescope the contribution, present the fragility as a finding, and say what would be needed to settle it.

Days 15–20: Write the Response Letter

The response letter is not a summary of what you did. It is a persuasive document arguing that the paper is now ready for publication. Give it the same care you would give the paper itself.

For each reviewer comment:

Reviewer X, Comment Y. [Quote or paraphrase]

Response: [What you did, why you did it, and what the result shows]

Changes: [Section, page, line numbers]

The response to a must-fix comment should be specific and evidence-rich. The response to a negotiable comment should acknowledge the concern, describe what you did, and explain why your approach addresses the underlying issue even where it differs from what the reviewer proposed. The response to a misunderstanding should clarify without blame and describe the text revision that prevents the same misunderstanding for future readers. The response to an out-of-scope comment should explain why it falls outside the paper's contribution and acknowledge it as future work.

One comment, two responses

Here is the same comment answered badly and well. The comment: "The authors do not justify the choice of a 12-month follow-up window."

The weak response:

Response: We thank the reviewer for this helpful comment. We have revised the manuscript accordingly and added justification for our follow-up window.

Nothing in that paragraph tells the reviewer what changed or where to look for it. The reviewer now has to hunt through the manuscript to verify a claim that the authors could have verified for them in one line.

The strong response:

Response: The 12-month window follows the registry's own reporting cycle: outcomes are certified annually, so any shorter window would mix certified and provisional records. We have added this justification to Section 2.3 (p. 8, lines 145–162) and added a sensitivity analysis at 18 months in Appendix C (Table C2). The point estimate moves from 0.34 to 0.31 and the sign and significance are unchanged.

Changes: Section 2.3, p. 8, lines 145–162, and Appendix C, Table C2.

The second version answers the question, names the location, and pre-empts the obvious follow-up ("does the result survive a different window?") before the reviewer can ask it. That is the whole craft.

For complete templates and formatting, see our rebuttal letter template and our response to reviewer comments template.

Days 21–25: Polish, Proofread, Co-Author Review

These final days serve a quality-control function that is easy to underestimate. The activities, in order:

Alignment check. Read the response letter and the revised manuscript side by side. Every change mentioned in the letter should be verifiable in the manuscript. Every significant change in the manuscript should appear in the letter. Mismatches between the two documents are common and damaging, and the editor will catch them even when you do not.

Consistency check. Verify that line numbers, page numbers, section references, and figure numbers in the response letter match the revised manuscript exactly. If you renumbered sections or moved content during the revision, the letter almost certainly points at stale locations. This is the single most common defect in resubmissions and the cheapest one to fix.

Co-author review. Send both documents to all co-authors with a firm deadline. Co-authors bring fresh eyes and will catch the errors and weak responses that you have gone blind to through proximity. Give them 48 hours and a specific request ("flag anything that reads as defensive"), because an open-ended "any thoughts?" produces nothing.

Final proofread. Read both documents once more and hunt for typos, formatting inconsistencies, and any placeholder text that survived editing. [TODO: check this number] in a submitted response letter is a real thing that happens to real people.

When the Editor Gives You 14 Days Instead of 60

Short deadlines usually accompany minor revisions, but not always. Some journals set a 14-day or 21-day clock even for substantial work. Compress the playbook like this:

• Day 1 (morning). Read everything once. Take two hours instead of two days for the cooling-off period.
• Day 1 (afternoon). Build the comment table. Cut the estimated time for every priority-3 item to zero and do those last or not at all.
• Days 2–8. Execute. If any priority-1 item is estimated at more than five days, email the editor now and ask for an extension with a specific new date and a one-line reason. Editors grant these routinely when asked early and almost never when asked on the deadline.
• Days 9–12. Response letter.
• Days 13–14. Alignment check, co-author sign-off, submit.

The part that gets cut under compression is the polish and not the substance. Never trade a requested analysis for a cleaner letter.

The Revision Checklist: 15 Items to Verify Before Resubmission

Before you click "submit," verify every item on this list:

1. Every reviewer comment has a corresponding entry in the response letter, with no omissions
2. Every response points to a specific manuscript location by section and line number
3. All line and page numbers match the revised manuscript and not the original
4. "No change" decisions include explicit justification
5. Contradictory reviewer suggestions are flagged and addressed in the response
6. The summary of major changes at the top of the response letter is complete and accurate
7. The revised manuscript follows the journal's current formatting guidelines (check them, because they may have changed since your original submission)
8. All new tables and figures are referenced in both the manuscript and the response letter
9. New references have been added to the bibliography
10. Track changes or highlighted revisions are included if the journal requires them
11. The cover letter is updated for resubmission, which is a separate document from the response letter (see our cover letter template)
12. All supplementary materials and new appendices are updated and consistent with the revised manuscript
13. Co-authors have reviewed and approved both documents
14. The manuscript ID from the original submission is referenced correctly
15. All files use the format and naming convention the submission system expects

What Separates a Second-Round Acceptance from a Second-Round Rejection

The second round of review is fundamentally different from the first. Reviewers are not re-reading your paper from scratch. They are checking whether their specific concerns were addressed, and many of them read the response letter before they reopen the manuscript. The letter therefore carries more weight in round two than it did in round one.

Second-round acceptances share common features. The response letter is thorough and specific. It is honest about what could not be done. The revisions are substantive instead of cosmetic. Where the authors disagreed with a reviewer, they supplied evidence and offered an alternative. The overall tone signals intellectual engagement instead of performative compliance.

Second-round rejections share a different set. The response letter is vague ("we revised accordingly"), key concerns are handled superficially, disagreements are asserted instead of argued, and the manuscript shows minimal structural change. The reviewer reads the letter and concludes, correctly or not, that the authors did not take the feedback seriously.

The difference is almost always in the response letter and not the revision. Revisions can be genuinely good and still get rejected when the letter fails to communicate what was done and why. That is why the response letter deserves its own drafting and revision cycle instead of a hasty write-up the night before the deadline.

Need structure for your revision response? ReviewPanel.ai generates a point-by-point rebuttal letter and edit manifest from your manuscript and reviewer comments. You handle the science, and the platform handles the structure. $29/paper.

Frequently asked questions

How long does a revise and resubmit usually take?

Most journals give 60 to 90 days for a major revision and 14 to 30 days for a minor one. The working time inside that window is what this playbook budgets, roughly 25 days of actual effort front-loaded onto the analytical work. Authors who use the full calendar window productively resubmit earlier than authors who wait, because the analysis that breaks in week two still leaves five weeks of recovery. If you cannot finish, ask the editor for an extension before the deadline passes.

Do I have to do everything the reviewers asked?

No. You have to respond to everything the reviewers asked, which is a different obligation. Where you decline a request, say so plainly, give the reason, and say what you did instead. Silent omission is the failure mode that gets revisions rejected, because the reviewer who made the request will look for it first. Editors expect authors to push back on some requests. What they do not accept is a response letter that quietly skips the comment nobody wanted to deal with.

What if a reviewer is factually wrong about my paper?

Correct the record without scoring points. Quote the reviewer's statement, then point to the exact location where the paper already addresses it, and then change the text so the next reader cannot make the same mistake. That last step matters: if a competent reviewer misread your Methods section, the section is unclear, whatever the reviewer got wrong. Framing it as a clarity fix instead of a reviewer error keeps the editor on your side and costs you nothing.

Should I email the editor during the revision?

Email the editor when you need a decision only they can make: an extension, a conflict between two reviewers that you cannot resolve on your own, or a finding that changes the paper's claims substantially. Keep it to a few sentences and propose a specific resolution instead of asking an open question. Do not email to ask whether your planned revisions "sound acceptable," because editors will not pre-approve a revision and the request signals that you are looking for cover.

What happens if the paper is rejected after I revise it?

Second-round rejections are uncommon but not rare, and they usually come with more usable information than a first-round desk reject. The reviewer reports tell you which concerns survived the revision, which means the next submission starts from a much better position. Keep the response letter, because it maps every criticism the paper has ever received. Then work through the recovery steps in our guide to what to do after a rejection before you pick the next journal.