R&R Rebuttal (jbf-rebuttal)
When to trigger
- JBF returns a major or minor revision decision
- Referees request more identification, robustness, data detail, or mechanism evidence
- You need a response letter that is firm, empirical, and concise
Triage first
Classify every comment:
- Must-do: editor requests, identification threats, data errors, missing
robustness, unclear contribution.
- Should-do: additional heterogeneity, mechanism tests, clearer exposition,
appendix reorganization.
- Negotiate: infeasible data, out-of-scope extensions, tests that would
answer a different paper.
- Clarify: misunderstandings caused by your writing.
JBF-style response strategy
- Put the editor's main concern first.
- For identification comments, add the strongest feasible test and explain what
it does and does not rule out.
- For robustness comments, add a table or appendix panel with exact line/table
references.
- For data comments, document sources, merge rules, sample attrition, and
proprietary-data limits.
- For scope comments, tie revisions back to banking/finance implications.
Response paragraph pattern
We thank the referee for raising this point. We now [change made]. The new
analysis appears in Table X / Appendix Table Y and shows [result]. We also revised
page Z to clarify [interpretation]. This addresses the concern because [logic].
Anti-patterns
- Arguing instead of adding evidence where evidence is feasible
- Saying "space constraints" when the appendix can carry the work
- Hiding null or weaker robustness checks
- Changing the design without updating the contribution claim
JBF comment-to-fix map
| Typical JBF referee ask |
Standard fix |
Where it goes |
| "Plain TWFE is biased under staggered adoption" |
Re-estimate with a heterogeneity-robust DID estimator; show both side by side |
main table + event-study figure |
| "Results may be a crisis artifact" |
Re-run excluding 2007–09 (and 2020 if in sample); report stability |
appendix panel cited in the text |
| "Cluster at the policy level, not the bank" |
Re-cluster; wild-cluster bootstrap if clusters are few |
table notes + one robustness column |
| "Economic significance is unclear" |
Convert to basis points / % of assets / capital-ratio points against a stated benchmark |
results text + abstract |
| "The policy conclusion overreaches" |
Bound the claim to the identified margin and treated population |
conclusion rewrite, flagged in the letter |
Worked response pass (illustrative)
Referee: "Your staggered-deregulation DID relies on TWFE, which recent econometrics shows can be badly weighted."
- Action: re-estimate with a robust estimator; suppose TWFE gives −1.8% and the robust estimator −2.4% (illustrative), with flat pre-event coefficients.
- Letter: report both numbers, note the conclusion is unchanged or strengthened, and point to the new event-study figure plus an estimator note.
- Manuscript: promote the robust estimate to the baseline; keep TWFE as a comparison column rather than deleting it.
Negotiation lines that hold up at JBF
- Infeasible supervisory data: offer aggregate moments plus full code, citing the confidentiality regime, rather than a flat refusal.
- Out-of-scope structural-model request: offer a stylized mechanism subsection and bound the empirical claim instead.
- Sample extension beyond the data license: state vendor coverage limits and show stability on the overlapping window.
Letter skeleton
Dear Editor,
[1] One paragraph on what the revision does, led by the editor's own concern.
[2] Summary table: comment -> change -> location (table/page).
Referee 1
R1.1 [restate the point fairly] / Response: [evidence, exact table and page]
...
Referee 2 ...
[Closing] remaining limitations stated plainly; no new unflagged claims.
Evidence ledger
For the response letter, maintain a ledger:
Comment | New evidence | Location | Effect on claim | Remaining limitation
Every must-do comment should have a new evidence row or a clearly justified infeasibility row. If a new
test weakens the headline result, state the narrower finance interpretation and update the introduction.
JBF rebuttals are strongest when the response letter, manuscript text, and appendix all tell the same
story about identification, data limits, and economic magnitude.
Output format
[Decision type] major / minor / conditional
[Editor priority] ...
[Comment matrix] must-do / should-do / negotiate / clarify
[New analyses] ...
[Response tone] grateful, precise, evidence-led
[Next step] revise manuscript + response letter
Source: brycewang-stanford/Awesome-Journal-Skills → Journal-of-Banking-and-Finance-Skills/skills/jbf-rebuttal/SKILL.md
1---2name: jbf-rebuttal3description: Use when responding to a Journal of Banking & Finance revise-and-resubmit, including triaging referee reports, strengthening identification, adding robustness, preserving anonymity where needed, and drafting a point-by-point response letter.4---5
6
7# R&R Rebuttal (jbf-rebuttal)
8
9## When to trigger
10
11- JBF returns a major or minor revision decision
12- Referees request more identification, robustness, data detail, or mechanism evidence
13- You need a response letter that is firm, empirical, and concise
14
15## Triage first
16
17Classify every comment:
18
191. **Must-do**: editor requests, identification threats, data errors, missing
20 robustness, unclear contribution.
212. **Should-do**: additional heterogeneity, mechanism tests, clearer exposition,
22 appendix reorganization.
233. **Negotiate**: infeasible data, out-of-scope extensions, tests that would
24 answer a different paper.
254. **Clarify**: misunderstandings caused by your writing.
26
27## JBF-style response strategy
28
29- Put the editor's main concern first.
30- For identification comments, add the strongest feasible test and explain what
31 it does and does not rule out.
32- For robustness comments, add a table or appendix panel with exact line/table
33 references.
34- For data comments, document sources, merge rules, sample attrition, and
35 proprietary-data limits.
36- For scope comments, tie revisions back to banking/finance implications.
37
38## Response paragraph pattern
39
40```text
41We thank the referee for raising this point. We now [change made]. The new
42analysis appears in Table X / Appendix Table Y and shows [result]. We also revised
43page Z to clarify [interpretation]. This addresses the concern because [logic].
44```
45
46## Anti-patterns
47
48- Arguing instead of adding evidence where evidence is feasible
49- Saying "space constraints" when the appendix can carry the work
50- Hiding null or weaker robustness checks
51- Changing the design without updating the contribution claim
52
53## JBF comment-to-fix map
54
55| Typical JBF referee ask | Standard fix | Where it goes |
56| --- | --- | --- |
57| "Plain TWFE is biased under staggered adoption" | Re-estimate with a heterogeneity-robust DID estimator; show both side by side | main table + event-study figure |
58| "Results may be a crisis artifact" | Re-run excluding 2007–09 (and 2020 if in sample); report stability | appendix panel cited in the text |
59| "Cluster at the policy level, not the bank" | Re-cluster; wild-cluster bootstrap if clusters are few | table notes + one robustness column |
60| "Economic significance is unclear" | Convert to basis points / % of assets / capital-ratio points against a stated benchmark | results text + abstract |
61| "The policy conclusion overreaches" | Bound the claim to the identified margin and treated population | conclusion rewrite, flagged in the letter |
62
63## Worked response pass (illustrative)
64
65Referee: "Your staggered-deregulation DID relies on TWFE, which recent econometrics shows can be badly weighted."
66
67- Action: re-estimate with a robust estimator; suppose TWFE gives −1.8% and the robust estimator −2.4% (illustrative), with flat pre-event coefficients.
68- Letter: report both numbers, note the conclusion is unchanged or strengthened, and point to the new event-study figure plus an estimator note.
69- Manuscript: promote the robust estimate to the baseline; keep TWFE as a comparison column rather than deleting it.
70
71## Negotiation lines that hold up at JBF
72
73- Infeasible supervisory data: offer aggregate moments plus full code, citing the confidentiality regime, rather than a flat refusal.
74- Out-of-scope structural-model request: offer a stylized mechanism subsection and bound the empirical claim instead.
75- Sample extension beyond the data license: state vendor coverage limits and show stability on the overlapping window.
76
77## Letter skeleton
78
79```text
80Dear Editor,
81[1] One paragraph on what the revision does, led by the editor's own concern.
82[2] Summary table: comment -> change -> location (table/page).
83Referee 1
84 R1.1 [restate the point fairly] / Response: [evidence, exact table and page]
85 ...
86Referee 2 ...
87[Closing] remaining limitations stated plainly; no new unflagged claims.
88```
89
90## Evidence ledger
91
92For the response letter, maintain a ledger:
93
94```text
95Comment | New evidence | Location | Effect on claim | Remaining limitation
96```
97
98Every must-do comment should have a new evidence row or a clearly justified infeasibility row. If a new
99test weakens the headline result, state the narrower finance interpretation and update the introduction.
100JBF rebuttals are strongest when the response letter, manuscript text, and appendix all tell the same
101story about identification, data limits, and economic magnitude.
102
103## Output format
104
105```text
106[Decision type] major / minor / conditional
107[Editor priority] ...
108[Comment matrix] must-do / should-do / negotiate / clarify
109[New analyses] ...
110[Response tone] grateful, precise, evidence-led
111[Next step] revise manuscript + response letter
112```
113
114---
115
116**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Journal-of-Banking-and-Finance-Skills/skills/jbf-rebuttal/SKILL.md`
thedixitjain