That Email Is Not a Rejection — It’s an Invitation
There is a moment every researcher remembers: opening the decision email, scanning past the word “revise,” and feeling your stomach drop. Your paper was not accepted. It was not rejected either. It landed in the middle ground that most published papers pass through at least once: revise and resubmit — and knowing how to respond to reviewer comments is the skill that turns that decision into an acceptance.
A revise-and-resubmit decision means the editor believes your paper can be published once you address the reviewers’ concerns. That is genuinely good news. The hard part is knowing how to respond to reviewer comments in a way that is thorough, professional, and persuasive — without sounding defensive, and without spending three weeks rewriting a paper that only needed a few careful fixes. This guide gives you a simple seven-step playbook you can use for every revision, plus a worked example, the five most common mistakes, and answers to the questions every first-time author asks.
First, Understand What “Revise and Resubmit” Really Means
When a journal invites you to revise and resubmit, the editor is saying two things at once. First, your paper has a publishable core — the question matters, the method is broadly sound, or the findings are worth sharing. Second, the reviewers found problems that must be fixed before the paper is ready. Those problems might be small (a confusing table, a missing citation) or substantial (an analysis that needs redoing), but the editor has already judged them fixable. Papers that are not fixable get rejected outright.
Keep that in mind: you are not defending your paper against enemies. You are collaborating with experts and an editor who want the same thing you do — a stronger paper.
Step 1: Let It Sit for 24 Hours
Do not reply the day you receive the comments. Reviewer feedback almost always stings on first reading, even when it is fair. A comment like “the theoretical framework is underdeveloped” can feel like an attack on months of work. It is not. It is a reader telling you where they got lost.
Give yourself at least a day before you touch the manuscript. Then read the comments again with fresh eyes. Most authors discover on the second reading that the reviewers were kinder — and more often right — than they first seemed. If a comment still feels unfair after a day, it usually means the reviewer misunderstood something, which means your writing was unclear at exactly that point.
Step 2: Read Every Comment Twice — Then Sort Them
Copy the comments into a document, read them slowly twice, and sort every comment into one of four buckets:
- Agree and fix: the reviewer is right. This is most comments. Plan the change.
- Agree in principle, fix differently: the reviewer spotted a real problem but suggested a solution that does not fit your study. You can solve the same problem another way — and say so.
- Disagree, with reasons: the reviewer misunderstood your method, or asked for something outside your study’s scope. You will need a polite, evidence-based explanation.
- Needs a decision from the editor: two reviewers contradict each other, or a request conflicts with the journal’s own guidelines. Flag these in your cover note to the editor.
Sorting first matters: a typo fix and a request for a new analysis are not the same kind of work, and your response letter should show you understood the difference.
Step 3: Revise the Manuscript Before You Write a Single Reply
Beginners usually do this backwards: they draft replies, then edit the paper to match. Do the opposite. Make every change in the manuscript first — rewrite the paragraph, rerun the analysis, rebuild the table. Only when the paper itself is fixed should you start writing the response letter.
Work from a numbered list of the comments so nothing gets lost, and keep a simple change log as you go — a note of what you changed and where (for example, “p. 8, Methods: added sampling details”). That log becomes the backbone of your response letter, and it protects you from the most embarrassing revision error of all: telling a reviewer you made a change you forgot to make.
Step 4: Write the Response Letter Point by Point
The response letter is the document reviewers actually read first. Its job is simple: prove, comment by comment, that you took the feedback seriously. Follow this format for every single comment:
- Quote the comment in full, numbered exactly as the reviewer wrote it (Reviewer 1, Comment 3). Never paraphrase a comment into something easier to answer.
- Thank the reviewer and acknowledge the point in one sentence.
- State exactly what you did, or explain why you did something different.
- Point to the location — page and section, or a quoted sentence of the new text — so the reviewer does not have to hunt for your change.
A good response looks like this: “Thank you for raising this. We agree the sampling procedure was unclear. We have expanded the description in the Methods section (p. 7), specifying that participants were recruited through stratified random sampling across the three campuses, and we have added the response rate (78%) to Table 1.” That is four sentences, and it answers everything: what was wrong, what changed, and where to find it.
Never write “Done” or “Changed as suggested” on its own. Reviewers cannot verify a one-word reply, and it reads as dismissive. If a change was truly trivial, say what it was: “Corrected — ‘affect’ changed to ‘effect’ on p. 3.”
Step 5: Use the Right Tone — Grateful, Precise, Never Defensive
Tone is where most response letters fail. Reviewers are volunteers who read your work carefully and for free; they remember authors who treat them with respect, and editors notice too. A few rules keep your tone on track:
- Start with gratitude, and mean it. “Thank you for your careful reading and constructive comments” is not empty politeness — it frames the whole exchange as a collaboration.
- Describe, do not argue. “We have clarified this point” beats “The reviewer is wrong about this.” Even when you disagree, frame it as a clarification: “We may not have explained this clearly; we have now added…”
- Never use sarcasm, and never call a comment “unfair.” If a reviewer misunderstood your paper, the misunderstanding is data: something in your writing allowed it. Fix the writing, then explain the fix.
Step 6: How to Disagree Without Burning Bridges
You are allowed to disagree with a reviewer — good editors expect it sometimes. But a disagreement must be argued, not asserted. Use this three-part structure: acknowledge the suggestion, give your reason with evidence, and offer an alternative improvement.
For example, imagine a reviewer asks you to add a control group to a study that is already complete. You cannot run a new experiment, but you can still respond well: “We appreciate this suggestion. A control group would strengthen the design, and we have added this as a limitation and a direction for future research (p. 14). Because data collection is complete, we have instead added a comparison with published norms for the same measure, which we report in Table 3.” You said no — and you made the paper better anyway.
One warning: if two reviewers make the same point independently, they are almost certainly right, and if the editor’s own letter repeats a comment, treat it as a requirement, not a suggestion.
Step 7: Assemble the Resubmission Package
Before you resubmit, check that your package is complete — most resubmissions need all of these:
- The revised manuscript, with changes highlighted (tracked changes or a clean copy, exactly as the journal asks).
- The point-by-point response letter covering every comment from every reviewer, in order.
- A short cover note to the editor summarizing the main changes and flagging any contradictions between reviewers or any comment you could not fully satisfy.
- Any new tables, figures, or supplementary files the revision created.
A Worked Example: Turning a Tough Comment into a Strong Reply
Here is a realistic exchange — the kind of comment that makes a new author’s heart sink — and a reply that handles it well.
Reviewer 2, Comment 4: “The sample size of 86 participants is too small to support the authors’ claims, and no justification is provided. The generalizability of the findings is therefore questionable.”
Weak reply: “We disagree. 86 participants is enough for this type of study.”
Strong reply: “Thank you for raising this important point. We agree the manuscript did not justify the sample size, and we have now added a power analysis to the Methods section (p. 6): with an expected medium effect size, alpha of .05, and power of .80, the required sample was 85 participants, which our sample of 86 meets. We have also added a paragraph to the Limitations section (p. 13) acknowledging that the sample comes from a single university, so the findings should be generalized with caution and replicated in other settings. We have softened the claim in the Discussion accordingly.”
Notice what the strong reply does: it thanks the reviewer, concedes the real problem (no justification), supplies evidence (the power analysis), adds a limitation honestly, and tones down the claim. It never argues that 86 is “enough” in the abstract — it shows the arithmetic and accepts the boundary of what the data can claim. That is the pattern to copy for every difficult comment.
5 Common Mistakes to Avoid
- Replying the same day. Hasty replies are defensive replies. Take 24 hours, minimum.
- Making silent changes. Every change in the manuscript must be announced in the response letter. Reviewers should never discover a change by accident — or worse, never discover it at all.
- Arguing instead of explaining. “You misunderstood” loses reviewers. “We have clarified” wins them.
- Answering the easy comments and dodging the hard ones. Reviewers notice immediately when their biggest criticism gets the shortest reply. Give the hardest comment your longest, most careful answer.
- Forgetting the editor. Your cover note is your chance to explain contradictions between reviewers and to highlight your most important changes. Editors read it first and it shapes how they read everything else.
Frequently Asked Questions
How long should a response letter be?
As long as it needs to be — usually two to six pages. One page is almost always too short (it means you are skimming), and more than ten suggests you are repeating yourself. A good rule: if a reviewer wrote a paragraph, your reply should be at least a paragraph.
What if two reviewers contradict each other?
Say so plainly in your cover note to the editor and explain which approach you chose and why. Never silently pick one reviewer and ignore the other — the ignored reviewer will notice in round two.
Can I disagree with a reviewer?
Yes, when you have a reason and evidence. Acknowledge the suggestion, explain your reasoning briefly, cite evidence or a source where possible, and offer an alternative improvement to the paper. What you cannot do is dismiss a comment without explanation.
How long do I have to resubmit?
Most journals allow 30 to 90 days, and the decision letter states the deadline. If you need more time, email the editor before the deadline and ask — editors almost always grant an extension when asked in advance.
Your Revision Is a Conversation, Not a Trial
Learning how to respond to reviewer comments is really learning to treat peer review as a conversation: reviewers point out where your paper confused them, you fix the paper, and you show your work. Do that patiently and point by point, and a revise-and-resubmit decision becomes what it was always meant to be — the last step before publication. Open the decision letter, take a day, sort the comments, revise the manuscript first, and reply to every point with gratitude and precision.