R&R Rebuttal Strategy (jhr-rebuttal)
When to trigger
- A JHR R&R or conditional-acceptance letter arrived
- You need to structure point-by-point responses to referees and the editor
- Referees asked you to reconcile with prior estimates or add sensitivity tests
- You are unsure how much weight to give the handling editor vs. the referees
JHR-specific framing
- No fee for invited revisions — the $175 charge is initial-submission only, so resubmit cleanly without budgeting again.
- Single-anonymous review: referees know who you are; keep the tone collegial and specific, and avoid defensive or status-based appeals.
- The reconciliation requirement carries into revision. If referees ask why your estimates differ from prior published work, the expected response is comparative estimation (re-run under the prior spec/sample) plus sensitivity tests — not prose alone. JHR explicitly may require this.
- The handling editor (coeditor/associate editor) synthesizes the reports; when referees conflict, anchor your plan to the editor's letter and say so.
Response-letter structure
- Cover note to the editor — summarize the 3-5 most substantive changes; state how you handled any conflicting referee requests.
- Per-referee blocks — quote each comment, then respond. Use one of: Done (point to the new table/figure/section), Done differently (justify), or Respectfully push back (rare, evidence-based).
- A reconciliation appendix — a side-by-side of your estimate vs. the prior literature's, with the bridge explained (sample, spec, period, population).
- A change-log — every manuscript change keyed to a comment, with new page/exhibit numbers.
Checklist
Anti-patterns
- Answering prose with prose when a number/comparison was requested
- Silently dropping an inconvenient referee point
- Letting the revision balloon past the page limit
- Picking a fight with one referee instead of letting the editor's letter arbitrate
- Forgetting to refresh the data-availability footnote after adding analyses
Common referee pushback at JHR and the expected fix
| Referee objection |
Weak response |
JHR-calibrated response |
| "Pre-trends look noisy / TWFE biased with staggered timing" |
Cite a methods paper and assert robustness |
Re-estimate with a heterogeneity-robust estimator, show the new event study, add a pre-trend sensitivity bound |
| "Why does your estimate differ from [prior paper]?" |
A paragraph of contextual speculation |
Comparative estimation: prior spec on your sample, your spec on the prior window, bridge table cited |
| "Clustering seems wrong" |
Footnote defending current choice |
Re-cluster at the assignment level, add wild bootstrap if clusters are few, report both |
| "Effect could be sorting at the cutoff" |
Verbal institutional argument only |
Density test, covariate continuity, donut estimate in a new appendix exhibit |
| "Results are a LATE; policy claim is broader" |
Soften one sentence |
Characterize compliers, re-scope the policy paragraph, flag what does not travel |
Worked response excerpt
Comment R2.3: The staggered rollout makes the TWFE estimates hard to interpret.
Response: Done. We now report Callaway-Sant'Anna group-time ATTs as the
preferred estimates (new Table 3) and move TWFE to Appendix Table A7 for
comparison. The event study (new Figure 2) shows pre-period coefficients near
zero; a pre-trend sensitivity exercise (Appendix Table A8) indicates the
headline effect survives violations up to twice the largest pre-period
estimate. Pages 14-16 are rewritten around the new estimates.
Every response of this type names the new exhibit, the new pages, and the
result of the check — referees at this venue reward verifiable specificity.
Triage order for a multi-referee letter
- Editor's letter first: extract the must-do list and any arbitration of
conflicts.
- Empirical asks next (reconciliation, estimators, inference) — these gate
acceptance.
- Framing and exposition asks last; they often resolve themselves once the
new tables exist.
Output format
【Decision】R&R / conditional accept
【Referee map】R1/R2/R3 asks → response type each
【Reconciliation】prior-vs-ours table added? [Y/N]
【Sensitivity】new tests + cross-refs? [Y/N]
【Length】still <=40pp; overflow in appendix? [Y/N]
【Next step】resubmit via msubmit.net (no fee)
Source: brycewang-stanford/Awesome-Journal-Skills → Journal-of-Human-Resources-Skills/skills/jhr-rebuttal/SKILL.md
1---2name: jhr-rebuttal3description: Use when a Journal of Human Resources (JHR) revise-and-resubmit arrives and you must plan the response letter — answering referees and the handling editor, satisfying the reconciliation and sensitivity demands, and confirming no fee applies to invited revisions. Strategy and structure; it does not write your results.4---567# R&R Rebuttal Strategy (jhr-rebuttal)89## When to trigger1011- A JHR R&R or conditional-acceptance letter arrived12- You need to structure point-by-point responses to referees and the editor13- Referees asked you to reconcile with prior estimates or add sensitivity tests14- You are unsure how much weight to give the handling editor vs. the referees1516## JHR-specific framing1718- **No fee for invited revisions** — the $175 charge is initial-submission only, so resubmit cleanly without budgeting again.19- **Single-anonymous review:** referees know who you are; keep the tone collegial and specific, and avoid defensive or status-based appeals.20- **The reconciliation requirement carries into revision.** If referees ask why your estimates differ from prior published work, the expected response is **comparative estimation** (re-run under the prior spec/sample) plus **sensitivity tests** — not prose alone. JHR explicitly may require this.21- The **handling editor (coeditor/associate editor)** synthesizes the reports; when referees conflict, anchor your plan to the editor's letter and say so.2223## Response-letter structure24251. **Cover note to the editor** — summarize the 3-5 most substantive changes; state how you handled any conflicting referee requests.262. **Per-referee blocks** — quote each comment, then respond. Use one of: *Done* (point to the new table/figure/section), *Done differently* (justify), or *Respectfully push back* (rare, evidence-based).273. **A reconciliation appendix** — a side-by-side of your estimate vs. the prior literature's, with the bridge explained (sample, spec, period, population).284. **A change-log** — every manuscript change keyed to a comment, with new page/exhibit numbers.2930## Checklist3132- [ ] Every referee point addressed explicitly (none silently dropped)33- [ ] Reconciliation with prior published estimates shown numerically, not asserted34- [ ] Requested sensitivity/comparative tests added and cross-referenced35- [ ] Editor's synthesis used to resolve conflicting referee asks36- [ ] Revision still within the 40-page limit; new material pushed to the Online Appendix37- [ ] Disclosure statement and data-archive footnote updated if anything changed38- [ ] Tone collegial (single-anonymous — they know you)3940## Anti-patterns4142- Answering prose with prose when a number/comparison was requested43- Silently dropping an inconvenient referee point44- Letting the revision balloon past the page limit45- Picking a fight with one referee instead of letting the editor's letter arbitrate46- Forgetting to refresh the data-availability footnote after adding analyses4748## Common referee pushback at JHR and the expected fix4950| Referee objection | Weak response | JHR-calibrated response |51|---|---|---|52| "Pre-trends look noisy / TWFE biased with staggered timing" | Cite a methods paper and assert robustness | Re-estimate with a heterogeneity-robust estimator, show the new event study, add a pre-trend sensitivity bound |53| "Why does your estimate differ from [prior paper]?" | A paragraph of contextual speculation | Comparative estimation: prior spec on your sample, your spec on the prior window, bridge table cited |54| "Clustering seems wrong" | Footnote defending current choice | Re-cluster at the assignment level, add wild bootstrap if clusters are few, report both |55| "Effect could be sorting at the cutoff" | Verbal institutional argument only | Density test, covariate continuity, donut estimate in a new appendix exhibit |56| "Results are a LATE; policy claim is broader" | Soften one sentence | Characterize compliers, re-scope the policy paragraph, flag what does not travel |5758## Worked response excerpt5960```text61Comment R2.3: The staggered rollout makes the TWFE estimates hard to interpret.6263Response: Done. We now report Callaway-Sant'Anna group-time ATTs as the64preferred estimates (new Table 3) and move TWFE to Appendix Table A7 for65comparison. The event study (new Figure 2) shows pre-period coefficients near66zero; a pre-trend sensitivity exercise (Appendix Table A8) indicates the67headline effect survives violations up to twice the largest pre-period68estimate. Pages 14-16 are rewritten around the new estimates.69```7071Every response of this type names the new exhibit, the new pages, and the72result of the check — referees at this venue reward verifiable specificity.7374## Triage order for a multi-referee letter75761. Editor's letter first: extract the must-do list and any arbitration of77 conflicts.782. Empirical asks next (reconciliation, estimators, inference) — these gate79 acceptance.803. Framing and exposition asks last; they often resolve themselves once the81 new tables exist.8283## Output format8485```86【Decision】R&R / conditional accept87【Referee map】R1/R2/R3 asks → response type each88【Reconciliation】prior-vs-ours table added? [Y/N]89【Sensitivity】new tests + cross-refs? [Y/N]90【Length】still <=40pp; overflow in appendix? [Y/N]91【Next step】resubmit via msubmit.net (no fee)92```9394---9596**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Journal-of-Human-Resources-Skills/skills/jhr-rebuttal/SKILL.md`
thedixitjain