Research Series · Daily Briefing

How to Write an R-and-R Response Letter That Recovers the Paper Without Surrendering It

Dr. Debasis Pahi  |  Ph.D. (IIT Kharagpur)  |  DrDPKlass
14 September 2026  ·  drdpklass.com
PhD · Post-Doc · Faculty India & Emerging Economies Revise & Resubmit

A revise-and-resubmit is not a compliment and it is not a verdict. It is a conditional invitation: the editor will look again if you can show, in writing, that every material objection has been heard, classified, and either fixed in the manuscript or refused with a reason a second reviewer can live with. Most lost R&Rs are not lost in the tables. They are lost in the letter.

This Research Series briefing is for doctoral candidates, post-docs and early faculty—especially those working from Indian and other emerging-economy institutions—who have a first R&R in hand and six to sixteen weeks on the clock. It is a playbook for the letter, not a second lecture on identification. The letter is the only document the editor is guaranteed to read in full on the return trip.

1. Decode the decision before you touch a sentence

Read the decision letter twice before you open the manuscript. The first read is emotional. The second is operational. Circle three things only: the editor’s own paragraph, any comment the editor flags as “must address,” and the deadline. Everything else is material for a map, not a mood.

Editors write in a dialect. “We would be willing to consider a revision” is weaker than “please revise along the following lines.” “Major revision” at many field journals still means the contribution is salvageable. “The paper would need substantial new analysis” may mean a new design, or it may mean one robustness table that the associate editor already has in mind. Do not invent a harsher reading than the text supports. Do not invent a softer one either.

Separate Reviewer 1, Reviewer 2, and the editor into three voices. When they conflict, the editor’s voice wins. When two reviewers ask for opposite framings, the letter must name the conflict and state which path you took and why. Silence on a conflict is read as evasion.

Working rule. If you cannot write, in one sentence, what the editor still needs to believe in order to accept, you are not ready to revise. You are only ready to tinker.

2. Build a comment map the editor can audit

Do not start by rewriting the introduction. Start with a spreadsheet or a two-column document that no one else will see. One row per discrete request. Columns: source (R1, R2, AE, EIC), quote or tight paraphrase, type, action, location in the new manuscript, status.

Type the comments into five bins only:

Parked items still appear in the letter, briefly, so the reviewer does not think you missed them. Refused items get the longest careful prose. Added-evidence items get a pointer to a table and a one-line result. Clarifications get a page-and-paragraph cite and almost no argument.

BinLetter lengthManuscript change
ClarifyShort. Quote the new sentence.Usually a paragraph, a label, or a footnote.
Add evidenceMedium. State the test and the kernel result.Table, appendix, or new subsection.
ReframeMedium-long. Show old claim versus new claim.Introduction and discussion, not only a footnote.
RefuseLongest. Reason, alternative, what you did instead.Often a limitations paragraph that is specific, not generic.
ParkOne or two sentences.None, or a one-line “beyond scope” note.
Audit test. An associate editor should be able to tick every numbered comment against a paragraph in your letter without hunting. If they have to search the manuscript to discover whether you answered, you have already spent goodwill.

3. Tone: neither apology nor combat

The letter is professional correspondence among people who will meet again. “We thank the reviewer for this insightful comment” is fine once. It is noise the twelfth time. Prefer verbs that describe work: we relocated, we estimated, we cut, we cannot implement because.

Do not prosecute the reviewer. Even when a comment misreads a table, the productive move is “We see how Table 3 could be read that way; we have relabelled the columns and added a sentence at p. 17.” The reader of the letter is the editor, not the reviewer you wish you had had.

Do not collapse into gratitude theatre. Indian academic training sometimes teaches excessive deference in letters to seniors. Editors of international field journals read that as uncertainty about the contribution. Equally, do not import seminar-combat language—“the reviewer is simply wrong”—into a document that will sit in an editorial file.

Thank once. Then show the work. Then stop writing atmosphere.

First person plural is the default for coauthored papers. First person singular is acceptable for a solo dissertation chapter. Mix them and the letter looks unfinished.

4. Anatomy of one comment–response unit

Each unit has four beats. Keep them in this order so a tired editor can scan.

4.1 Restate the request in the reviewer’s language

One or two sentences. Do not improve the reviewer’s English. If they asked for “a test of reverse causality,” use that phrase even if you privately think they meant selection.

4.2 State what you did

Past tense, concrete artefact: new paragraph in Section 2.2; Appendix C; Column 5 of Table 4; a footnote on page 12. Vague “we have strengthened the discussion” is not an action.

4.3 Give the kernel

One result or one clarified claim. Not the whole robustness section. The letter points; the paper argues.

4.4 Close the loop

If you implemented: “We hope this addresses the concern.” If you refused: “We therefore kept the original design and added a limitation at p. 29 that names the missing test.” Do not leave the unit hanging.

Weak unit

“Thank you for this excellent point. We have revised the paper accordingly and believe it is now much stronger.”

Usable unit

“R2 asked whether the BRSR shock is anticipated. We added a pre-trend plot (Figure A2) and a lead-coefficient test (Table 4, col. 6). Leads are small and insignificant. Text at pp. 14–15.”

5. Hard comments: new data, new theory, new paper

Some comments are really invitations to write a second article. Treat them as such. A request for a new country sample, a new instrument, or a full theory rewrite may be beyond the R&R if the original contribution was already identified. The letter should say so without sulking.

When the request is feasible but costly—fresh hand collection, a survey wave, a freedom-of-information wait—give a dated plan or a partial substitute. Editors would rather see a clean partial than a promised dataset that does not arrive. If institutional review board timelines at your campus will overrun the resubmission window, say so early and ask, in one short paragraph to the editor only, whether a staged return is acceptable. Do not bury that question inside a reviewer response.

When two reviewers want opposite contribution paragraphs, pick one conversation and write the choice into the letter. “We followed Reviewer 1’s framing because it matches the journal’s last three accepted papers on disclosure; we retained Reviewer 2’s mechanism test as Appendix B.” That sentence does more work than six pages of both-sides prose.

Do not. Change the research question to please the loudest comment. A recovered paper with a muddled question is harder to accept than a focused paper that refused one request with a reason.

If a comment exposes a real error—wrong clustering, a leaked future variable, a mistranslated regulatory date—say so plainly, show the corrected estimate, and state whether the qualitative claim survives. Concealment here is career-level risk, not style.

6. Constraints that shape R&R work from Indian campuses

Emerging-economy authors often face three frictions that the letter must handle without sounding like a plea.

Data that cannot be re-downloaded. Prowess extracts, CMIE vintages, bank supervisory files, and some ministry microdata are vintage-specific. If a reviewer asks you to “extend the sample through 2025” and the licensed vintage ends earlier, name the licence and the last observable year. Offer a public-data robustness slice if one exists. Do not promise a merge you cannot legally perform.

Institutional clocks. Teaching load, examination duty, and delayed ethics clearance are real. They are not, by themselves, reasons to skip a feasible test. They are reasons to sequence work: high-leverage comments first, polishing last. Put the sequence in your private map, not in the letter.

Setting treated as exotic. Reviewers sometimes ask you to “explain India” at a length that would be odd for a US or UK sample. Give the institutional minimum that identification requires—who is regulated, what changed on which date, who is omitted from the frame—and refuse a country tour. Point to a short institutional appendix rather than inflating Section 2.

Use the setting as you would in the contribution paragraph: as a source of variation or a boundary condition, not as an apology. A fourth friction is coauthor geography. Many India-based papers have a coauthor abroad who can meet house style quickly and a coauthor on campus who holds the data licence. On day one of the R&R, name who owns the letter and who owns each table. Split that ownership late and the packet reads like two papers stapled together. Earlier Research Series notes on contribution paragraphs and identification sections are the right companions when a reviewer is really asking you to restabilise the claim.

7. What to send back, and in what order

The return packet is a small archive. Typical contents:

  1. A short cover note to the editor (half a page): decision date, manuscript ID, what changed at the level of the claim, any remaining disagreement you want the editor to referee.
  2. The point-by-point letter, numbered to match reviewers, with page cites to the revised manuscript.
  3. The revised paper, clean.
  4. A marked copy if the journal asks for one. If they do not ask, do not send a rainbow of tracked changes unless house style requires it.
  5. Replication materials the journal’s policy already demanded, updated to the new tables.

Number comments the way the reviews number them. If a reviewer wrote in paragraphs, number the paragraphs yourself and say that you have done so. Consistency beats clever structure.

Keep the letter shorter than the paper. A forty-page response to a twenty-eight-page manuscript signals that the authors cannot prioritise. If you need space for extra tables, put them in an appendix to the paper, not in the letter.

Before you upload, print the letter and the introduction and read them in one sitting. The contribution sentence in the new introduction must match the contribution sentence in the letter. Drift between those two pages is a common reason an AE comes back cold.

Deadline hygiene. If you will miss the posted window by more than a few days, write the editor once, early, with a date you will keep. A silent late upload reads as process risk. A dated request is ordinary professional practice.

8. Field checklist and closing brief

Run this list the morning you submit, not the week you start.

An R&R is a second chance at a conversation you already started. The letter is how you prove you were listening. Recover the paper. Do not surrender the question that made the paper worth writing.

Dr. Debasis Pahi
Ph.D. (IIT Kharagpur) · DrDPKlass · drdpklass.com
Research Series · 14 September 2026