Rebuttals and revisions that change minds
Reading reviews without despair, writing rebuttals that work, and surviving revision cycles.
Rebuttals and revisions that change minds
Reviews arrive. Some are thoughtful. Some are harsh. At least one seems to describe a different paper entirely. What you do next matters more than most people realize: rebuttals and revisions genuinely change outcomes, but only when written a certain way.
Read the reviews cold, then wait 24 hours
Read everything once, feel whatever you feel, and close the tab. Do not draft responses. Do not message co-authors in all caps. Come back the next day.
On the second read, reviews shrink. The “devastating” objection is often one fixable experiment. The reviewer who “missed the point” is usually reacting to a paragraph that really is unclear. If a smart, tired person misread your paper, the fix is in the paper. If this is your first rodeo, peer review, explained covers what reviewers are actually asked to do.
Rebuttal structure: thank, clarify, evidence, commit
A rebuttal that works has four moves, usually in this order for each point:
- Thank, briefly and once. Not groveling, just professional.
- Clarify misunderstandings by pointing to specific lines, or admitting the text was unclear.
- Evidence: new numbers, an added ablation, a citation that answers the question. Concrete beats rhetorical every time.
- Commit: state exactly what will change in the revision. “We will add this experiment to Section 5” is a promise reviewers can hold you to, and they respect it.
Address every numbered point
Skipping a point reads as evasion. Within the word limit (often 500 to 1000 words for all reviewers combined), respond to everything:
- Number your responses to match the reviews (R1.2, R3.1)
- Spend words proportional to severity, not to how annoyed you are
- Group duplicate concerns across reviewers into one answer, then reference it
- Cut pleasantries ruthlessly. The word budget belongs to evidence.
What actually flips scores
Data from area chairs and long experience agree: scores move when a rebuttal delivers new evidence that directly answers a stated objection. “Reviewer asked for comparison X, here is comparison X, we win” flips scores. Restating your contributions does not. Arguing the reviewer is wrong, without new material, never does. Also honest concessions help: admitting a limitation and scoping the claims down can turn a hostile reviewer into an advocate.
Journals: major vs minor revision
Journal timelines differ from conference rebuttals. Minor revision means the editor expects to accept once you fix specifics. Major revision means real work, often new experiments, and re-review, but it is a genuine invitation: most major revisions that come back carefully done get accepted eventually.
Your response letter is a document in its own right: quote each reviewer comment, respond below it, and state what changed and where. Many authors color the changed text in the revised manuscript. In a Git-backed workspace like Oleafly, the diff between your submitted checkpoint and the revision writes most of this letter for you.
The resubmission cycle
Rejection is a routing event, not a verdict. Fold in every fixable criticism, then pick the next venue (revisit choosing your venue). Many well-cited papers were rejected at least once first. The reviewers at the next venue will notice the paper got stronger, even if they never know why.