Rebuttal Strategy (worlddev-rebuttal)

When to trigger

• A WD decision letter arrived: major revision, minor revision, or reject-and-resubmit
• Two referees pull in opposite directions (the methodologist vs. the contextualist split)
• A referee misread the paper and the instinct is to argue rather than to clarify
• The required changes are large and you must triage what to do vs. what to defend
• You are deciding whether to resubmit to WD or redirect to a sibling

Reading a WD decision letter

WD revisions are shaped by double-anonymized, multidisciplinary review, so two patterns recur. First, the editor's letter is the binding contract — referee reports advise, the editor decides; weight the editor's framing above any single referee. Second, because referees come from different evidentiary cultures, you will often face conflicting demands: one wants tighter identification, the other wants thicker context or reflexivity. You cannot satisfy both by capitulating to each; you must find the synthesis the editor will accept, and say so explicitly. Treat a reject-and-resubmit as a genuine second chance — WD uses it as a substantive invitation, not a soft no, but the bar is high and the cover letter must show real movement.

Building the response letter

1. Open with gratitude and a one-paragraph summary of the major changes — let the editor see the shape before the detail.
2. Reproduce every comment verbatim, then respond beneath each, in the referees' order. Number them (R1.1, R1.2, …) so nothing is missed.
3. For each comment, state the action: changed (with location and a quoted snippet of the new text), or respectfully declined (with reasoned evidence). Never silently ignore a point.
4. Show, don't assert. "We have added a Callaway–Sant'Anna estimate (Table 5, p. 18) confirming the result" beats "we addressed this."
5. Handle the referee split openly: state the tension, explain the synthesis, and tell the editor why it serves the paper — e.g., "R1 sought a stronger design and R2 richer context; we strengthened the design (Sec. 4) and added the institutional account R2 requested (Sec. 5), which together make the mechanism more credible."

Triage: concede, strengthen, or defend

Distinctive WD rebuttal traps

• Conceding so much to the methodologist that the development relevance erodes — protect the contribution that made it a WD paper.
• Dismissing the contextualist's reflexivity/ethics points as "not rigorous" — WD takes them seriously.
• Arguing instead of clarifying when a referee misunderstood — that reads as defensive and rarely persuades.
• Forgetting that the revised manuscript stays anonymized if the journal sends it back to the same blinded referees.
• A cover letter that summarizes changes the manuscript does not actually contain.

Checklist

• Editor's letter parsed first; its priorities weighted above any single referee
• Every comment reproduced and answered; none silently dropped
• Each response names the action + exact location of the change
• The referee split is addressed openly with a stated synthesis
• New analyses actually appear in the revised manuscript (no phantom changes)
• The development contribution is protected, not bargained away
• Revised manuscript remains anonymized for re-review
• Declined points are declined with evidence, courteously

Anti-patterns

• "We thank the reviewer and have addressed this" with no specifics or location
• Capitulating to every methodologist demand until the paper is no longer a development paper
• Treating reflexivity/ethics comments as unserious
• Arguing with a referee who simply misread, instead of fixing the exposition
• A response letter that claims changes the manuscript does not contain

Output format

【Journal】World Development (WD)
【Skill】worlddev-rebuttal
【Decision】major / minor / reject-and-resubmit
【Editor's binding priorities】top 2–3 from the letter
【Per-comment plan】[R#.# → concede / strengthen / clarify / defend + location]
【Referee split】tension + stated synthesis
【Contribution guard】how the WD development relevance is protected
【Anonymization】revision still blinded? [Y/N]
【Source status】verified URL / 待核实 / not asserted
【Next step】finalize response letter → re-run worlddev-submission preflight; if redirecting, worlddev-workflow