How to Write a Response to Reviewers Letter (With a Worked Example).

A response to reviewers letter is the document the editor reads before reopening your revised manuscript: a short note that thanks the editor, summarizes the major changes in one paragraph, then answers every reviewer comment point by point, each answer ending with the location of the change. Editors use it to decide how much of the revision to re-read and whether to send the paper back to the reviewers at all. Write it as their reading guide, not as a formality.

Most first-time authors do the opposite. They finish the revision, feel the deadline, and dash off the letter in the last hour before resubmitting. That order is backwards. The letter is the first thing the editor opens, and often the only thing a busy reviewer reads closely, so the hour you save on it is taken from the one reader who decides what happens next.

Who actually reads the response letter?

The handling editor reads all of it, usually before opening the manuscript. Each reviewer tends to read the replies to their own comments and skim the rest. That gives the letter two audiences with different needs.

The editor wants the shape of the revision: did the authors take the reports seriously, what changed at the level of the whole paper, is anything still contested. The reviewers want their own comments quoted back accurately and answered one by one. A letter that answers only one of them fails, and a two-line "we thank the reviewers and have revised accordingly" note answers neither.

Address the letter to the editor by name. The reviewers appear in the third person inside it, as in "Reviewer 1 asked" or "we agree with Reviewer 2 that." You answer their comments in the annex, but the letter itself is a message to the person who signed the decision.

What structure should the letter follow?

Three parts, in a fixed order: brief thanks, a summary of the major changes, and a point-by-point annex. The first two fit on one page. The annex takes as much room as the comments demand.

Keep the thanks to two sentences. Name the manuscript ID and the decision you are responding to, thank the editor and reviewers, and stop. Extended gratitude reads as filler and delays the part the editor came for.

The summary paragraph carries more weight than anything else in the document. Name the few changes that affect the paper as a whole: a reanalysis, a restructured section, new data, a shortened introduction. An editor who has read this paragraph should know what kind of revision this was before scrolling further.

The annex quotes each comment verbatim, numbered, with your reply directly beneath it in a visually distinct format. The conventions that make that section easy to scan are covered in our guide to the point-by-point response format, including what to do when two reviewers pull in opposite directions.

How do you get the tone right?

Confident and specific. You are reporting completed work to a colleague, not pleading a case. State what you changed and where, in the same register you would use in the paper itself.

Two failure modes dominate first letters. One is over-apology: thanking the reviewer for the same comment three times, calling every observation insightful, apologizing for errors nobody accused you of. Editors read that as padding. The other is defensiveness, where a criticism gets a paragraph about why the reviewer misread you. Even when the reviewer did misread you, the productive reply fixes the passage that allowed the misreading and says so plainly.

You do not have to accept every comment. Declining one is normal, provided you decline with evidence and offer something in return: a clarification in the text or an acknowledged limitation. Doing that without souring the file is its own craft, and we walk through it in how to disagree with a reviewer politely.

Anchor every reply to a location

End every reply with where the change lives: section, page, and line numbers in the revised manuscript. "We have revised the discussion" is not an answer the editor can verify. "The new paragraph appears in Section 4.1, page 14, lines 402 to 415" is.

Do this for small edits too, and refresh the numbers last. Line positions shift every time you touch the file, so lock the manuscript first, then check every location in the letter against the final PDF. A reply that points to line 300 when the change sits at line 340 tells the editor the authors never tested their own map. If you submit both a clean copy and a marked copy, say which one the numbers refer to.

A worked example for a major revision

Below is the letter portion for a paper that received a major revision with two reviews. The point-by-point annex would follow in the same document.

Dear Dr. Alvarez,

Thank you for the 12 May decision on our manuscript (ID 2026-0417) and for two reports that improved the paper. We have completed the requested major revision.

Three changes affect the paper as a whole. We reran the main analysis with the covariate Reviewer 1 identified as missing; the effect holds, and the updated results replace Section 3.2 and Tables 2 and 3. We rewrote the discussion to separate findings from interpretation, as Reviewer 2 requested, moving the speculative material into a clearly labeled final paragraph. We also cut the introduction by a third to address the length concern both reviewers raised.

The annex below replies to every comment individually, quoting each one and giving the page and line numbers of the change in the clean copy. A marked copy with tracked changes accompanies this file.

With thanks for your time and for the reviewers' care,

Notice what the example leaves out. It does not summarize the paper again, argue with anyone, or promise future work. It hands the editor a reading plan: two analytical changes, one structural cut, and every detail waiting in the annex with an address.

The checklist before you resubmit

Run six checks before uploading. Every comment has a reply, including the ones buried inside long reviewer paragraphs that hide two questions in one. Every reply names a location, and the locations match the final PDF rather than an earlier draft. The letter greets the correct editor, since handling editors change mid-review more often than authors expect. The summary paragraph claims nothing the annex contradicts. The tone survives a reread the next morning. And the revised manuscript still complies with the journal's formatting rules, because revisions break limits the first submission met: an abstract grows past its cap, a new citation knocks the reference list out of style. That last read against the journal's own rule set is the one Waraq automates, returning each fix as a tracked change in Word with the rule it enforces.

Resubmission usually calls for a brief cover letter as well, separate from the response document. Keep it short and let the response carry the detail; the journal cover letter has its own conventions. Then upload, and let the letter do the job you built it for: walking the editor through the revision before they ever reopen the file.