R&R Response & Rebuttal (ecj-rebuttal)
When to trigger
- An EJ R&R (or reject-with-encouragement-to-resubmit) letter has arrived
- You have referee reports and need a point-by-point response plan
- You are deciding which requests to implement, which to push back on, and how
- The revision is drafted and you need the response letter to accompany it
Do the revisions before writing the letter. The letter documents changes already made; it should never promise work that is not in the revised manuscript.
Reading the decision letter
- The editor's letter is the binding document (at EJ a handling editor coordinates the report; editor-in-chief Francesco Lippi, verified 2026-06-20). Identify which referee points the editor flags as essential vs. optional and prioritize accordingly.
- Separate requests into: (a) must-do for the editor, (b) reasonable and cheap, (c) costly or wrong-headed. Negotiate (c) with evidence, not assertion.
- An EJ editor and referees care most about the economic argument and broad interest: expect demands to strengthen the mechanism, broaden the relevance / bound the generality, or sharpen identification. Treat those as first-order.
- Plan replication readiness now: acceptance triggers the EJ Data Editor's pre-acceptance reproducibility check and a Zenodo deposit (see
ecj-replication-package).
Response-letter structure
- Cover note to the editor: thank them; summarize the 3–4 substantive changes; state how the paper is now stronger economically and more broadly relevant. One page.
- Point-by-point, per referee, in the referee's order:
- Quote (or paraphrase) the comment.
- State the change made, with the new text/exhibit and where it now lives (section, table, page).
- Where you disagree, respond with evidence and economic reasoning — concede what is fair, hold the line where you are right, and never be defensive.
- A summary of changes mapping each major comment to the revised location, so the editor can verify at a glance.
Tone: respectful, concise, confident. Every response is either "done, here it is" or "we respectfully differ, and here is why." Avoid hedging and avoid over-promising future work. Because EJ review is single-blind, you already know the report is read by referees who see your identity — keep the tone collegial.
Handling the EJ-typical demands
- "Broaden the relevance / it reads too narrow" → route to
ecj-topic-selection / ecj-literature-positioning; make the general lesson and external relevance explicit, or bound the claim honestly.
- "Strengthen the mechanism" → route to
ecj-theory-model; add the model result or the discriminating test, then report it.
- "Rule out alternative X" → route to
ecj-robustness; add the discriminating test, summarize in text, table in appendix.
- "Identification is not convincing" → route to
ecj-identification; add diagnostics/falsification or reframe the claim to what the design supports.
- "Improve the exposition" → route to
ecj-writing-style; at EJ this is substantive, not cosmetic — take it seriously.
- Conflicting referees → flag the conflict to the editor and explain the path you chose and why.
Checklist
Anti-patterns
- Writing the response letter before doing the revisions
- Skipping or merging referee points to seem responsive
- Defensive or dismissive tone toward a fair criticism
- Conceding a correct result because a referee pushed hard (defend it with evidence)
- Promising "future work" in place of an analysis the editor asked for now
- Dismissing an exposition request as cosmetic when at EJ it carries weight
- Ignoring the editor's prioritization and treating all comments as equal
Output format
【Decision】R&R / reject-with-encouragement
【Editor's essential points】1... 2... 3...
【Per-referee plan】R1: [done / push-back + evidence] ; R2: ... ; R3: ...
【First-order (broad-interest/mechanism/ID)】how addressed
【Exposition】improvements made? [y/n]
【Revisions complete before letter】[y/n]
【Summary-of-changes table】drafted? [y/n]
【Replication readiness】code ready for EJ Data Editor on accept? [y/n]
【Next】resubmit via Editorial Express (ecj-submission for format re-check)
1---2name: ecj-rebuttal3description: Use when a The Economic Journal (EJ) decision letter (R&R or reject-with-encouragement) has arrived and you need to draft the response-to-referees letter and revision plan. Structures the response and the diff; it does not redo the analysis (route back to ecj-identification / ecj-theory-model / ecj-robustness first).4metadata:5 source: https://skillmd.com/skills/brycewang-stanford/ecj-rebuttal6---78# R&R Response & Rebuttal (ecj-rebuttal)910## When to trigger1112- An EJ R&R (or reject-with-encouragement-to-resubmit) letter has arrived13- You have referee reports and need a point-by-point response plan14- You are deciding which requests to implement, which to push back on, and how15- The revision is drafted and you need the response letter to accompany it1617> Do the revisions *before* writing the letter. The letter documents changes already made; it should never promise work that is not in the revised manuscript.1819## Reading the decision letter2021- The **editor's letter** is the binding document (at EJ a handling editor coordinates the report; editor-in-chief **Francesco Lippi**, verified 2026-06-20). Identify which referee points the editor flags as essential vs. optional and prioritize accordingly.22- Separate requests into: (a) must-do for the editor, (b) reasonable and cheap, (c) costly or wrong-headed. Negotiate (c) with evidence, not assertion.23- An EJ editor and referees care most about the *economic argument* **and broad interest**: expect demands to strengthen the mechanism, broaden the relevance / bound the generality, or sharpen identification. Treat those as first-order.24- Plan replication readiness now: acceptance triggers the **EJ Data Editor's** pre-acceptance reproducibility check and a **Zenodo** deposit (see `ecj-replication-package`).2526## Response-letter structure27281. **Cover note to the editor**: thank them; summarize the 3–4 substantive changes; state how the paper is now stronger economically and more broadly relevant. One page.292. **Point-by-point**, per referee, in the referee's order:30 - Quote (or paraphrase) the comment.31 - State the change made, with the new text/exhibit and where it now lives (section, table, page).32 - Where you disagree, respond with evidence and economic reasoning — concede what is fair, hold the line where you are right, and never be defensive.333. **A summary of changes** mapping each major comment to the revised location, so the editor can verify at a glance.3435Tone: respectful, concise, confident. Every response is either "done, here it is" or "we respectfully differ, and here is why." Avoid hedging and avoid over-promising future work. Because EJ review is **single-blind**, you already know the report is read by referees who see your identity — keep the tone collegial.3637## Handling the EJ-typical demands3839- **"Broaden the relevance / it reads too narrow"** → route to `ecj-topic-selection` / `ecj-literature-positioning`; make the general lesson and external relevance explicit, or bound the claim honestly.40- **"Strengthen the mechanism"** → route to `ecj-theory-model`; add the model result or the discriminating test, then report it.41- **"Rule out alternative X"** → route to `ecj-robustness`; add the discriminating test, summarize in text, table in appendix.42- **"Identification is not convincing"** → route to `ecj-identification`; add diagnostics/falsification or reframe the claim to what the design supports.43- **"Improve the exposition"** → route to `ecj-writing-style`; at EJ this is substantive, not cosmetic — take it seriously.44- **Conflicting referees** → flag the conflict to the editor and explain the path you chose and why.4546## Checklist4748- [ ] Every referee point has an explicit response (none skipped)49- [ ] Each "done" response points to the exact revised location50- [ ] Disagreements backed by evidence/economic reasoning, framed respectfully51- [ ] Editor's essential requests all addressed first52- [ ] Broad-interest / mechanism / identification demands treated as first-order53- [ ] Exposition improvements taken seriously (EJ bar)54- [ ] Replication package on track for the EJ Data Editor if acceptance follows55- [ ] Revisions are actually in the manuscript before the letter is written56- [ ] Summary-of-changes table maps comments → locations57- [ ] No new claim is over-promised without being delivered5859## Anti-patterns6061- Writing the response letter before doing the revisions62- Skipping or merging referee points to seem responsive63- Defensive or dismissive tone toward a fair criticism64- Conceding a correct result because a referee pushed hard (defend it with evidence)65- Promising "future work" in place of an analysis the editor asked for now66- Dismissing an exposition request as cosmetic when at EJ it carries weight67- Ignoring the editor's prioritization and treating all comments as equal6869## Output format7071```72【Decision】R&R / reject-with-encouragement73【Editor's essential points】1... 2... 3...74【Per-referee plan】R1: [done / push-back + evidence] ; R2: ... ; R3: ...75【First-order (broad-interest/mechanism/ID)】how addressed76【Exposition】improvements made? [y/n]77【Revisions complete before letter】[y/n]78【Summary-of-changes table】drafted? [y/n]79【Replication readiness】code ready for EJ Data Editor on accept? [y/n]80【Next】resubmit via Editorial Express (ecj-submission for format re-check)81```