Rebuttal & R&R Response (cps-rebuttal)
An R&R is a contract: address every point from each reviewer and the editor, show what changed, and
point to where. CPS reviewers are comparativists; they care most about comparative leverage, the rival
explanations, measurement across cases, and inference. Treat the letter as a navigable document the
editor can verify against the revised manuscript.
When to trigger
- A decision letter arrives with reviewer reports (R&R, or major/minor revisions)
- Planning the revision and the point-by-point response
- Reviewers disagree with each other and you must reconcile their demands
- A reviewer asks for analyses that would change the paper's identification or scope
Response-letter structure
- Opening synthesis. Thank the editor/reviewers; state the 3–4 biggest changes in a short paragraph
so the editor sees the shape of the revision immediately.
- Point-by-point. Reproduce each comment verbatim, then Response (what you did) and Location
(section/table/page). Number them (R1.1, R1.2, …) for easy cross-reference.
- Show, don't assert. Quote new text, name the new exhibit, give the new estimate — don't just say
"we have addressed this."
- Handle disagreement. Where reviewers conflict, state the trade-off and your principled choice;
ask the editor to adjudicate if needed. Where you decline a change, give a reasoned, evidence-based
defense — politely, without relitigating the decision.
CPS-specific revision priorities
- Comparative leverage / travel. If a reviewer doubts the comparison or generalization, strengthen
the design argument or the scope conditions (
cps-research-design, cps-theory-building) — do not
just add caveats.
- Rival explanations. New robustness or case evidence that adjudicates the rival the reviewer raised;
state the adjudication sentence explicitly.
- Measurement across cases. If asked, show robustness to alternative codings (V-Dem/Polity/etc.) and
defend comparability.
- Inference. Add few-cluster corrections, randomization inference, or multiple-testing adjustments if
challenged; report honest CIs.
- Transparency. Update the replication package and data availability statement to match every new
result (
cps-transparency-and-data).
Reviewer coalition map
Before writing the response, classify comments by reviewer role rather than by report order:
| Reviewer concern |
Typical request |
Revision move |
| Theory/comparative contribution |
Clarify what travels beyond the cases |
Rewrite the contribution paragraph and scope conditions |
| Design/identification |
Explain comparison, timing, or assignment |
Add design schematic, placebo, or rival-specific test |
| Measurement |
Defend cross-national coding or construct validity |
Add alternative coding, measurement appendix, or limitation |
| Area expertise |
Fix case history, regional literature, or institutional detail |
Add precise citations and qualify overgeneralization |
| Transparency |
Make data/code/evidence auditable |
Update Dataverse package, README, appendix, and data statement |
Use the map to reconcile conflicts. If one reviewer wants broader theory and another wants narrower case
precision, the response should say how the revision sharpens the scope condition rather than simply
expanding both sections.
Checklist
Anti-patterns
- Cosmetic edits dressed up as substantive responses ("we have clarified this")
- Ignoring or merging away a reviewer's point without acknowledgment
- Defensive or dismissive tone; relitigating the decision instead of answering it
- Adding caveats where the reviewer asked for design/identification work
- New results in the letter that the deposited code no longer reproduces
- Letting the revision creep over the word limit or re-introduce identifying info
Output format
【Decision】R&R / major / minor
【Major changes】the 3–4 headline revisions
【Reviewer coalition map】theory / design / measurement / area / transparency concerns classified
【Point-by-point】R1.1 … with Response + Location each
【Disagreements】how conflicting reviews were reconciled
【Declined】any requests declined + the evidence-based reason
【Transparency】package + data availability statement updated? [Y/N]
【Then】resubmit via SAGE Track (cps-submission for the preflight)
Supplementary resources
Source: brycewang-stanford/Awesome-Journal-Skills → Comparative-Political-Studies-Skills/skills/cps-rebuttal/SKILL.md
1---2name: cps-rebuttal3description: Use when responding to a Comparative Political Studies (CPS) revise-and-resubmit decision — structuring the response letter to multiple anonymous reviewers and the editor. Plans the revision and response; it does not fabricate results or relitigate the decision.4---5
6
7# Rebuttal & R&R Response (cps-rebuttal)
8
9An R&R is a contract: address **every** point from each reviewer and the editor, show what changed, and
10point to where. CPS reviewers are comparativists; they care most about comparative leverage, the rival
11explanations, measurement across cases, and inference. Treat the letter as a navigable document the
12editor can verify against the revised manuscript.
13
14## When to trigger
15
16- A decision letter arrives with reviewer reports (R&R, or major/minor revisions)
17- Planning the revision and the point-by-point response
18- Reviewers disagree with each other and you must reconcile their demands
19- A reviewer asks for analyses that would change the paper's identification or scope
20
21## Response-letter structure
22
231. **Opening synthesis.** Thank the editor/reviewers; state the 3–4 biggest changes in a short paragraph
24 so the editor sees the shape of the revision immediately.
252. **Point-by-point.** Reproduce each comment verbatim, then **Response** (what you did) and **Location**
26 (section/table/page). Number them (R1.1, R1.2, …) for easy cross-reference.
273. **Show, don't assert.** Quote new text, name the new exhibit, give the new estimate — don't just say
28 "we have addressed this."
294. **Handle disagreement.** Where reviewers conflict, state the trade-off and your principled choice;
30 ask the editor to adjudicate if needed. Where you decline a change, give a reasoned, evidence-based
31 defense — politely, without relitigating the decision.
32
33## CPS-specific revision priorities
34
35- **Comparative leverage / travel.** If a reviewer doubts the comparison or generalization, strengthen
36 the design argument or the scope conditions (`cps-research-design`, `cps-theory-building`) — do not
37 just add caveats.
38- **Rival explanations.** New robustness or case evidence that adjudicates the rival the reviewer raised;
39 state the adjudication sentence explicitly.
40- **Measurement across cases.** If asked, show robustness to alternative codings (V-Dem/Polity/etc.) and
41 defend comparability.
42- **Inference.** Add few-cluster corrections, randomization inference, or multiple-testing adjustments if
43 challenged; report honest CIs.
44- **Transparency.** Update the replication package and data availability statement to match every new
45 result (`cps-transparency-and-data`).
46
47## Reviewer coalition map
48
49Before writing the response, classify comments by reviewer role rather than by report order:
50
51| Reviewer concern | Typical request | Revision move |
52|------------------|-----------------|---------------|
53| Theory/comparative contribution | Clarify what travels beyond the cases | Rewrite the contribution paragraph and scope conditions |
54| Design/identification | Explain comparison, timing, or assignment | Add design schematic, placebo, or rival-specific test |
55| Measurement | Defend cross-national coding or construct validity | Add alternative coding, measurement appendix, or limitation |
56| Area expertise | Fix case history, regional literature, or institutional detail | Add precise citations and qualify overgeneralization |
57| Transparency | Make data/code/evidence auditable | Update Dataverse package, README, appendix, and data statement |
58
59Use the map to reconcile conflicts. If one reviewer wants broader theory and another wants narrower case
60precision, the response should say how the revision sharpens the scope condition rather than simply
61expanding both sections.
62
63## Checklist
64
65- [ ] Every reviewer and editor point has a numbered Response + Location
66- [ ] Opening synthesis lists the major changes up front
67- [ ] New text/exhibits/estimates quoted, not merely described
68- [ ] Reviewer disagreements reconciled with a stated, principled choice
69- [ ] Declined requests answered with evidence, not defensiveness
70- [ ] Comparative leverage / rival / measurement / inference concerns addressed substantively
71- [ ] Replication package and data availability statement updated to match the revision
72- [ ] Revised manuscript still within the word limit and anonymized
73
74## Anti-patterns
75
76- Cosmetic edits dressed up as substantive responses ("we have clarified this")
77- Ignoring or merging away a reviewer's point without acknowledgment
78- Defensive or dismissive tone; relitigating the decision instead of answering it
79- Adding caveats where the reviewer asked for design/identification work
80- New results in the letter that the deposited code no longer reproduces
81- Letting the revision creep over the word limit or re-introduce identifying info
82
83## Output format
84
85```
86【Decision】R&R / major / minor
87【Major changes】the 3–4 headline revisions
88【Reviewer coalition map】theory / design / measurement / area / transparency concerns classified
89【Point-by-point】R1.1 … with Response + Location each
90【Disagreements】how conflicting reviews were reconciled
91【Declined】any requests declined + the evidence-based reason
92【Transparency】package + data availability statement updated? [Y/N]
93【Then】resubmit via SAGE Track (cps-submission for the preflight)
94```
95
96## Supplementary resources
97
98- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — CPS review model and decision categories
99- [`../../resources/exemplars/library.md`](../../resources/exemplars/library.md) — benchmark the revised framing against verified CPS papers
100
101---
102
103**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Comparative-Political-Studies-Skills/skills/cps-rebuttal/SKILL.md`