Jf Rebuttal

---
name: jf-rebuttal
description: Use when drafting the response to a The Journal of Finance (JF) revise-and-resubmit (or addressing a reject-with-comments). Structures the response letter and revision plan after the manuscript is revised.
---

# Rebuttal & Response Letter (jf-rebuttal)

## When to trigger

- A JF **revise-and-resubmit (R&R)** has arrived and you must respond
- You are deciding whether/how to answer a reject-with-encouragement
- The revision is drafted and you need to map every editor/referee point to a change

## A JF R&R is rare — treat it accordingly

With **~5% acceptance** and **~33–45% desk rejection** (afajof.org editor reports, accessed 2026-05-30), an R&R from JF is precious. The path to acceptance runs through the **handling editor** (currently the team led by **Antoinette Schoar (MIT)** — verify the masthead): the **editor's letter, not any single referee, defines what acceptance requires**. Address the editor's framing first and most fully.

## Structure

- **To the editor**: summarize the main changes and how you met the editor's synthesis of the decision.
- **Per-referee, per-point**: restate each point, then state exactly what changed and **where** (section/table/Internet Appendix), quoting revised text where useful.
- **Disagreements**: handle respectfully with evidence; never ignore a point — explain if you chose not to change something.

## JF-specific moves

- Route substantial new robustness to the **Internet Appendix** (bundled at the end of the same PDF; does not count toward 60 pages; see `jf-internet-appendix`) and say so explicitly — this matches JF norms and keeps the body lean.
- Keep the body within the **60-page limit** after revisions.
- Update **disclosure** and ensure **replication code** is ready for the Data Editor under JF's Data and Code Sharing Policy (see `jf-submission`); near acceptance the code is verified before publication.
- Use the cover-letter channel only for specifics (e.g., a code-exemption request) — JF does not want a generic letter.

## Checklist

- [ ] Editor's points ranked and addressed first
- [ ] Every referee point tabulated with response + location of change
- [ ] New robustness placed in the Internet Appendix and cross-referenced
- [ ] Body still ≤60 pages after revision
- [ ] Disagreements handled with evidence, none ignored
- [ ] Replication code / disclosure updated for the Data Editor

## Anti-patterns

- Optimizing for one referee while missing the editor's central concern
- Burying or ignoring a referee point
- Adding robustness without telling referees it lives in the Internet Appendix
- Letting the revision push the body past 60 pages
- Forgetting the code-sharing obligation surfaces at acceptance

## Output format

```
【Editor's central concern + how met】...
【All referee points tabulated?】yes / no
【New robustness → Internet Appendix + cited?】yes / no
【Body ≤60 pp?】yes / no
【Code/disclosure ready for Data Editor?】yes / no
【Next step】resubmit via the AFA portal
```