| name | wp-rebuttal |
| description | Use when writing the response to a World Politics revise-and-resubmit. World Politics suggests author response memos not exceed about five pages single-spaced, and revised articles may exceed the word limit only when growth results from responding to reviewers; the response must convert each anonymous reviewer while keeping the editors confident. Structures the response; it does not fabricate new results. |
R&R Rebuttal (wp-rebuttal)
A World Politics R&R is a strong signal. But review is triple-blind: you do not know the
reviewers, and your response is read inside an anonymous process. World Politics also suggests author
response memos not exceed five pages, single-spaced, so the letter must be tight, complete, and
persuasive — moving every reviewer toward yes while keeping the editors confident the revision is
convergent.
When to trigger
- An R&R decision arrived and you are planning the revision + response memo
- Reviewers disagree with each other and you must reconcile their demands
- A reviewer requests analyses or cases that would change the paper's claims
- You are at risk of exceeding the ~5-page memo guidance
Strategy
- Read the editors' letter as the rubric. It signals which points are decisive. Solve those first;
the editors adjudicate disagreements among anonymous reviewers.
- One point-by-point response, every comment addressed — but tight. Quote each comment, then
respond. Never skip one. Keep the memo to about five pages single-spaced: be concise, point to
the manuscript for detail rather than re-deriving it in the letter.
- Concede or rebut explicitly, with evidence. For each: did what was asked (say where, with the
new text/table number), or push back respectfully with a reason (theory, design, or evidence).
A well-argued disagreement beats a hollow capitulation that weakens the paper.
- Reconcile conflicting reviewers openly. When one wants the opposite of another, say so, choose a
principled path, and explain the tradeoff to the editors.
- Protect what travels. Add robustness, alternative-source checks, or an extra case to shore up
generalization; resist changes that collapse the argument back to a single-case story or strip its
scope conditions.
- Stay anonymous and reproducible. Keep the revised manuscript triple-blind (no identifying
self-references), and update the World Politics Dataverse package so new tables/figures still
reproduce (see
wp-transparency-and-data-policy). Note that a revision may exceed the 12,500-word
limit only when the growth results from responding to reviewers.
Response-memo format
For each reviewer comment:
> [Quoted reviewer comment]
Response: [What we did / why we respectfully disagree] — concise.
Change: [Section/page/table-figure number where the revision appears].
Open with a short summary of the main changes to the editors; group by reviewer; keep the whole
memo to about five pages single-spaced; end each entry with the location of the change.
Anti-patterns
- A response memo far over the ~5-page guidance (re-deriving the paper in the letter)
- Ignoring or merging away a comment without a visible response
- Capitulating to a request that breaks the paper's cross-case logic just to please a reviewer
- Defensive or dismissive tone toward anonymous reviewers
- Letting the revised manuscript or new exhibits drift out of sync with the deposited package
Reviewer-demand triage (concede / rebut / reconcile)
Because review is triple-blind and the editors adjudicate, sort each demand before writing.
| Demand type | Default move for World Politics |
|---|
| Strengthens generalization (extra case, alternative source) | Concede; it keeps the argument traveling across cases |
| Would collapse the paper to a single-case story | Rebut respectfully with a design reason; protect the cross-case logic |
| Two reviewers want opposites | Reconcile openly; pick a principled path and explain the tradeoff to the editors |
Worked micro-example (illustrative)
A hypothetical R&R on a regime-change paper: Reviewer 1 wants a fourth case; Reviewer 2 calls the
fourth case a distraction and wants more within-case process tracing.
> R1: add a fourth case to show the mechanism generalizes.
> R2: the cases already overreach; deepen the process tracing.
Response: add ONE most-different case (R1) with its detail in the supplement, and deepen within-case
evidence in the two core cases (R2) — serving both the travel concern and the rigor concern.
Change: new case in Sec. 5 + Online Appendix B; expanded process tracing in Sec. 4 (pp. 18–22).
The memo states the conflict, the resolution, and the locations — in well under five pages. (Confirm
current memo-length and word-limit-exception rules against the submission guidelines.)
Output format
【Editors' decisive points】addressed first? [list]
【Coverage】every reviewer comment answered? [Y/N]
【Memo length】≤ ~5 pages single-spaced? [Y/N]
【Concede vs rebut】each tagged with evidence + change location
【Reviewer conflicts】reconciled and explained to editors? [Y/N]
【Travel protected】scope/generalization not diluted? [Y/N]
【Anonymity + Dataverse package updated】[Y/N]
【Next】resubmit via ScholarOne
Supplementary resources
