The Resubmission Letter: What to Send Back With Your Revision.

A resubmission cover letter is a short note to the handling editor that travels with your revised manuscript. It names the manuscript ID and the decision it answers, states that the revision and the response document are attached, summarizes the major changes in three or four sentences, and lists the files you uploaded. Everything comment-level belongs in the point-by-point response, so the letter stays under a page and costs the editor about thirty seconds.

That thirty seconds is the whole design constraint. Write the letter after the revision and the response document are finished, because its only material is a summary of what those files already contain.

How is a resubmission letter different from a first cover letter?

A first-submission cover letter argues that the paper fits the journal. A resubmission letter drops that argument entirely, because an editor who sent your paper to reviewers has already accepted the premise.

This is the mistake behind most bloated resubmission letters. Authors reuse the original letter as a base, so the new one re-pitches the contribution, restates the findings, and buries the one thing the editor came for: confirmation that the requested work was done. If you catch yourself explaining why the study matters, stop. The first cover letter had that job. This one confirms delivery and points to where the details sit.

At this stage the editor is doing triage, not evaluation. The verdict on the science will come from the reviewers' second read and from the revised text itself. The letter just routes the file.

What does the editor need to see in thirty seconds?

Four things: which manuscript came back, which decision it responds to, whether you engaged with the reports, and where the detailed answers live. A letter that delivers those four has nothing left to do.

Remember what the editor's queue looks like when your revision lands. It sits among new submissions and other returning files, and the editor has to reattach it to a decision made weeks or months ago. Anything that slows identification, a missing ID or a vague "our recent submission," sends them digging through the system before they can open your files.

A useful test: could a colleague who has never seen your paper read the letter and describe the state of the submission correctly? Which round this is, what was asked, what was delivered, what is attached. If yes, the letter works.

How do you summarize changes without repeating the point-by-point?

Report only the changes that affect the paper as a whole, and send the editor to the response document for everything else. Three or four sentences usually cover it: a rerun analysis, a restructured section, new data, a substantial cut.

The failure runs in both directions. Some letters compress too far. "We have revised the manuscript according to the reviewers' comments" tells the editor nothing and reads as evasion. Others expand too far and reproduce half the point-by-point response in paragraph form, which doubles the reading and invites contradictions between the two documents.

The dividing line is scope. A change that answers one reviewer comment lives in the response document. A change that alters what the paper is, a reanalysis, a reframed contribution, a new dataset, earns a sentence in the letter.

Disagreements deserve one honest flag. If you declined a requested change, say so in a single sentence and cite the numbered reply where you make your case. Editors take a clearly flagged disagreement in stride; finding an unflagged one buried in the annex goes down much worse.

Which identifiers and files does the letter need to list?

Five items: the manuscript ID, the paper title, the decision date, the decision type, and every file in the upload. Put the ID in the first sentence, and in the subject line if the journal takes resubmissions by email.

Two details trip authors up. Handling editors change between rounds more often than authors expect, so check the name in the decision letter against the journal's current record before you write the greeting. And the decision date matters because editors process papers in batches; "your decision of 14 April" locates your file faster than the title does.

The file list earns its space because a revision carries more files than a first submission: a clean copy, a marked copy with tracked changes, the response document, sometimes revised supplementary material. Name each file and say which copy the page and line numbers in your response refer to. Whether the decision was a major or minor revision changes how much of this apparatus you need, but even a minor revision travels with at least three files.

A short template you can adapt

For a major revision:

Dear Dr. Okafor,

We are resubmitting our manuscript "Soil salinity and smallholder crop choice in the Nile Delta" (ID AGE-2026-0198) in response to the major revision decision of 14 April.

The revision makes two changes that affect the whole paper. We reran the main model with the 2024 survey wave Reviewer 2 requested, which strengthened the central estimate and replaced Tables 2 through 4. We also restructured Section 5 to separate the policy discussion from the results, as Reviewer 1 suggested. The attached response document replies to all seventeen comments individually, with page and line numbers keyed to the clean copy.

Files uploaded: clean manuscript, marked manuscript with tracked changes, response to reviewers, and revised supplementary material.

Thank you for handling our manuscript.

For a minor revision, cut the middle paragraph to one sentence naming the handful of edits and keep everything else. The structure holds at any scale because the editor's question is the same at any scale: what came back, and where do I look.

One caution before you upload. Revisions break rules the first submission met. An expanded abstract slips past the word cap, new references fall out of the journal's citation style, an added figure lands in the wrong format. Run one pass against the journal's guide for authors before submitting, or hand that pass to Waraq, which checks the revised file against the journal's rule set and returns each fix as a tracked change.

Then send it. The letter is the last thing you write and the first thing the editor reads, so keep it under a page, let the response document carry the argument, and give the editor their thirty seconds back.