# Cover Letter Summary of Revisions: Step-by-Step Guide By the end of this article you will be able to write the summary of revisions that goes into a revised-manuscript cover letter, attach it to a complete point-by-point reviewer response letter, and submit a revision that an editor can evaluate quickly. You will need three things on hand before you start: the decision letter from the journal, your revised manuscript with tracked changes or a marked-up version, and a plain text editor or word processor for drafting the letter itself. This guide walks through the whole revision communication package, with the cover letter summary as the centerpiece. The cover letter summary of revisions is a short section, usually one to three paragraphs or a compact list, that tells the editor what changed and why at a glance. The reviewer response letter, sometimes called the point-by-point response, sits behind it and answers every individual comment in full. The two documents do different jobs, and confusing them is one of the most common reasons a revision bounces back for another round. ## What the Summary of Revisions Actually Does ![Five-step flow showing the revision package built from decision letter to point-by-point responses, summary paragraph, cover letter and final upload.](/article-images/illustrations/cover-letter-summary-of-revisions-revision-package.webp) When an editor receives a revised manuscript, they usually face three piles of material: the revised files, the original reviews, and your response letter. Reading all of that carefully takes time. A good summary of revisions shortens that work by answering three questions in the first minute of reading: 1. Did the authors address every comment? 2. What are the substantive changes, in plain terms? 3. Where in the manuscript does each change appear? Editors and reviewers rely on this. The peer review process in scholarly publishing is built on documented, traceable revisions, which is why journals ask for a response letter alongside the revised files rather than a bare upload. The summary is your chance to frame the revision honestly and efficiently before anyone digs into the details. The summary lives in the cover letter, not in the response letter. The cover letter is addressed to the editor. The response letter is addressed to the reviewers. Some journals ask for these as separate uploads, some accept a single combined document, and a few journals use structured online forms where you paste responses into fields. Check the decision letter and the journal's author instructions for the expected format, because practices vary widely between publishers. ## What to Have Ready Before Writing Gather these materials into one working folder: - The decision letter, with every reviewer comment numbered exactly as the editor numbered them. - The revised manuscript, either with tracked changes accepted or as a clean copy with line numbers turned on. - A marked-up version showing every change, if your journal requires one. - Any new figures, tables, supplementary files, or datasets added during revision. - Your notes or drafts from the point-by-point responses, if you have already written them. - The manuscript ID or submission number from the editorial system. If you have not yet written the point-by-point responses, write them first or write them alongside the summary. The summary is a distillation of the responses, so it is much easier to condense something that already exists than to summarize work you have only partially planned. ## Step-by-Step Walkthrough The following walkthrough uses a worked example throughout. Imagine a manuscript titled "Soil Moisture Effects on Root Architecture in Two Grass Species," submitted to an ecology journal, returned with two reviewer reports and a decision of major revision. Substitute your own manuscript details as you go. ### Step 1. Inventory every comment Open the decision letter and build a numbered list of every distinct comment, keeping the editor's numbering. Do not merge comments, even when one reviewer says nearly the same thing twice, because reviewers expect each numbered item to be answered. A short inventory for the example manuscript might look like this: ```text Reviewer 1 R1.1 Add a power analysis or justify the sample size of 12 pots per treatment. R1.2 Figure 2 axis labels are too small. R1.3 Clarify whether "waterlogged" means free-standing water or saturated soil. Reviewer 2 R2.1 The claim of a species-by-moisture interaction is not supported by the current statistical model. Reanalyze with a mixed model. R2.2 Cite recent work on drought responses in C3 grasses. R2.3 Discussion overstates the generality of the findings. Editor E.1 Address both reviews. Provide a marked-up manuscript and a point-by-point response. ``` Expected output of this step: a plain text file, a spreadsheet, or a document section containing every comment in order, each with a stable label such as R1.1 or R2.3. You will reuse these labels in the response letter and in the summary. ### Step 2. Classify each comment Sort the comments into three buckets before you draft anything: - **Major scientific or analytical issues.** These require new analyses, new experiments, or restructured arguments. In the example, R1.1 and R2.1 belong here. - **Clarity and presentation issues.** Rewording, reorganizing, adding citations, fixing figures. R1.2, R1.3, R2.2, and R2.3 belong here. - **Editorial or administrative items.** Formatting requirements, data availability statements, ethics documentation, marked-up copy. The classification determines what appears in the cover letter summary. Major issues get one sentence each in the summary. Clarity issues get grouped into a single sentence. Editorial items usually get one line noting that they are complete. ### Step 3. Decide the summary format ![Decision path asking about revision size and leading to a narrative paragraph, a paragraph plus signpost, or a table mapping changes.](/article-images/illustrations/cover-letter-summary-of-revisions-summary-format.webp) There are four widely used formats for the summary of revisions. Choose based on the number and severity of comments. | Format | Best for | Typical length | Example use | |--|--|--|--| | Narrative paragraph | Minor revisions, few comments | One paragraph, 100 to 200 words | Wording fixes, one added citation | | Short numbered list | Moderate revisions | Five to ten bullets | One new analysis plus several text edits | | Table mapping comments to changes | Major revisions | Rows for each major issue | Multiple analyses or new experiments | | Summary paragraph plus signposted response letter | Any major revision | One paragraph that refers the editor onward | The most common choice for major revisions | For the example manuscript, with two major analytical issues, the table format or the paragraph-plus-signpost format fits best. The walkthrough below uses the paragraph-plus-signpost format, because it works in nearly every editorial system. ### Step 4. Draft the point-by-point responses first Before writing the summary, make sure each comment has a complete response in the reviewer response letter. The standard structure for each item is: ```text Reviewer 1, Comment 1.1 "Add a power analysis or justify the sample size of 12 pots per treatment." Response: We agree that [sample size justification](/knowledge/diagnostics/research-methods/how-to-justify-sample-size-in-grant-proposals-and-manuscripts-a-reviewer-s-perspective) was needed. We added a power analysis as Supplementary Method S2, which shows that 12 replicates per treatment provide 80% power to detect the effect size reported in Figure 3 at alpha = 0.05. We now state this on page 8, lines 14 to 19. The sample size was not changed. Changes made: New Supplementary Method S2. Page 8, lines 14 to 19. ``` Notice three habits that reviewers respond to well. Quote or restate the comment so the response is self-contained. State clearly what you did, including what you did not do and why, if you disagree. Point to the exact location of the change with page and line numbers from the revised manuscript. ### Step 5. Write the summary paragraph Now distill the responses into one paragraph for the cover letter. The paragraph should follow this internal order: 1. One opening sentence thanking the editor and reviewers and stating that all comments were addressed. 2. One sentence per major issue, naming the change and the manuscript location. 3. One sentence grouping the minor and editorial changes. 4. One closing sentence directing the editor to the point-by-point response and the marked-up manuscript. Here is a worked example for the fictional manuscript: ```text Summary of Revisions We thank the editor and the two reviewers for their constructive comments. All comments have been addressed in the revised manuscript. The two major changes are as follows. First, in response to Reviewer 2 (comment R2.1), we reanalyzed the experiment with a linear mixed model that includes block as a random effect, and the species-by-moisture interaction remains significant (page 12, lines 3 to 22, revised Figure 4). Second, in response to Reviewer 1 (comment R1.1), we added a power analysis justifying the sample size (Supplementary Method S2, page 8, lines 14 to 19). We also tightened the Discussion to remove unsupported generalizations (R2.3), clarified the definition of waterlogging (R1.3), enlarged figure labels throughout (R1.2), and added the requested citations (R2.2). A complete point-by-point response follows this letter, and a tracked-changes manuscript is uploaded alongside the clean copy. ``` Read that paragraph against the inventory from Step 1. Every comment label appears exactly once. The two major issues each get a full sentence with a concrete outcome and a location. The four minor issues share one sentence. This density is the goal. ### Step 6. Draft the full cover letter around the summary A revised-manuscript cover letter has a standard skeleton. Fill it in like this: ```text Dear Dr. [Editor's last name], Re: Manuscript ID ECOL-2026-04871, "Soil Moisture Effects on Root Architecture in Two Grass Species" [Paragraph 1] Thank you for the opportunity to revise our manuscript. We appreciate the time and care that you and the reviewers invested in the first round of review. [Paragraph 2] Summary of revisions. (Insert the paragraph from Step 5.) [Paragraph 3] Files uploaded with this letter: 1. Revised manuscript, clean copy 2. Revised manuscript with tracked changes 3. Point-by-point response to reviewers 4. Revised figures and new Supplementary Method S2 [Paragraph 4] We confirm that this manuscript has not been published elsewhere and is not under consideration by another journal. All authors have approved this revision. We declare no competing interests, or list them here if any exist. Sincerely, [Corresponding author name, institution, email] ``` The summary paragraph is the heart of this letter. Everything else is standard professional housekeeping, which still matters, because a cover letter missing a conflict of interest statement or a file list creates administrative delays. ### Step 7. Cross-check the summary against the manuscript Verification is where most revisions succeed or fail. Run these four checks: 1. **Label check.** Every comment label from the decision letter appears in the response letter, and every major label appears in the summary. 2. **Location check.** Every page and line number cited in the summary and the response letter matches the clean revised manuscript, not an older draft. Line numbers shift between versions, so generate the clean PDF last and verify against it. 3. **Claim check.** Read each sentence in the summary and ask whether the manuscript actually contains the change described. If the summary says a figure was revised, open the figure. If it says a model was reanalyzed, confirm the results section reports the new model. 4. **Consistency check.** The outcome described in the summary must match the outcome described in the detailed response. Do not describe the same analysis in contradictory ways across the two documents. A practical way to run these checks is to search the clean manuscript PDF for key phrases. For the example, searching for "mixed model" should land on the revised results paragraph at page 12, lines 3 to 22, exactly as claimed. ### Step 8. Prepare final files and submit Export the cover letter as requested by the journal, usually as a PDF or Word file, and confirm the file list one last time against the editorial system's upload slots. A frequent small error is uploading the tracked-changes version into the slot meant for the clean manuscript, which then propagates through peer review as the file of record. The expected final state before you click submit is: clean manuscript in the manuscript slot, marked-up copy in its own slot, response letter in the response slot, cover letter with its summary in the cover letter slot, and every supplementary file named and versioned. ## Worked Variations for Different Decision Types ### Minor revision For a minor revision with, say, five small comments, the table format from Step 3 is unnecessary. A single narrative paragraph works, and the response letter can be a short list. Keep the same internal order as Step 5, but compress further, and skip detailed signposting because the full response is short. ### Reject and resubmit Some journals close the original submission and ask for a fresh submission with a new ID. In that case the cover letter must do double duty. It reintroduces the work as if new, then summarizes the revisions in a section clearly labeled as responding to the previous decision. Reference the original manuscript ID so the editor can pull the old file and the old reviews, because the new submission may be assigned to the same editor or a new one, and neither will have the history in front of them otherwise. ### Revisions after acceptance Post-acceptance changes, such as proof corrections, do not use this framework. They follow the proofing instructions the production team provides, and a formal summary of revisions would be out of place. ## Summary of Revisions Tips That Carry Weight These are the habits that consistently shorten review rounds: - **Lead with outcomes, not effort.** "We reanalyzed the data with a mixed model and the interaction remains significant" tells the editor more than "we spent considerable effort on the statistics." Editors evaluate outcomes. - **Name locations precisely.** Page and line numbers, figure numbers, and supplementary file names let a reviewer verify your claim in seconds. Vague pointers such as "in the relevant section" force them to hunt. - **Group minor comments.** Ten separate sentences about typos waste the editor's attention. One sentence covering all wording and typographic fixes is standard practice. - **State disagreements with evidence.** When you decline to make a change, explain why in one or two factual sentences and, where possible, point to data or literature. Reviewers accept well-argued disagreements far more often than authors expect, and they resent silent refusals. - **Quote the revised text.** For key changes, paste the new sentence or passage directly into the response letter so the reviewer sees the wording without opening the manuscript. This is standard in reviewer response letters across scientific fields. - **Keep the summary free of new arguments.** New data, new analyses, and new justifications belong in the response letter and the manuscript. The summary only reports that they exist and where they are. - **Version everything.** Name files clearly, for example "Manuscript_clean_rev2.pdf" and "Response_to_reviewers_rev2.docx." Editorial systems handle descriptive names better than "final_final.docx." ## Common Mistakes and Limitations These are the errors that most often trigger a second revision round or annoy an editor. - **Omitting the summary entirely.** Many authors assume the point-by-point response letter makes a summary redundant. The editor often reads the cover letter first, and without a summary they must reconstruct the revision's scope from scratch. - **Writing the summary as a thank-you note.** Gratitude belongs in one sentence. Paragraphs of appreciation with no substantive content read as padding. - **Claiming completeness you cannot support.** Writing "all comments were fully addressed" while quietly skipping one comment is a serious misstep, because reviewers check. If a comment was not addressed, the summary should say so and point to the reasoned disagreement in the response letter. - **Answering comments in a different order or with new numbering.** Reviewers navigate by their own numbering. Renumbering their comments, merging items without saying so, or skipping labels makes verification hard and looks evasive. - **Citing stale locations.** Page and line numbers from the previous version of the manuscript point reviewers to the wrong paragraph. This single error causes more reviewer friction than almost any other, because it makes an accurate response look inaccurate. - **Overloading the summary.** A summary covering twenty individual comments in twenty sentences has failed as a summary. Group the small items and elevate the two or three changes that affect the paper's conclusions. - **Hiding bad news.** If a requested experiment was not feasible, say so plainly in both the summary and the response. Reviewers discover omissions during re-review, and an omission converts a defensible decision into a credibility problem. - **Ignoring the journal's stated format.** Some journals specify separate files for the response letter and cover letter, or provide templates. A correct summary in the wrong file structure still creates work. One limitation to keep in mind: practices differ between journals and publishers, and the decision letter plus the journal's author guidelines are always the controlling documents for format and file requirements. The structure in this guide reflects the most widely used conventions, but where a specific journal specifies something different, follow the journal. And as with any stage of publishing, individual situations vary, so when a decision letter contains ambiguous instructions, a short polite query to the editorial office resolves it faster than guessing. ## Frequently Asked Questions ### What is a cover letter summary of revisions? It is a short section inside the cover letter for a revised manuscript that tells the editor, at a glance, what changed in response to peer review and where those changes appear in the manuscript. It condenses the full point-by-point reviewer response letter rather than replacing it. ### How long should the summary of revisions be? One paragraph of roughly 100 to 250 words suits most revisions, or a short list of five to ten items for major revisions. If it runs longer than half a page, you are probably duplicating the response letter, which should carry the detail. ### Do I need a summary for a minor revision? Yes, but keep it to a few sentences. Even small revisions benefit from a one-paragraph summary listing the changes, because it lets the editor confirm quickly that the requested work was done. ### How do I respond to a peer reviewer I disagree with? Answer the comment directly, state your position in one or two factual sentences, and support it with data, methods, or literature. Then note explicitly in the response letter that you did not make the requested change and why. Respectful, evidence-based disagreement is a normal and accepted part of peer review. ### Should the summary quote the reviewers' comments? Not in the cover letter summary. Quote individual comments in the point-by-point response letter, where each answer sits directly under its comment. The summary stays at the level of what changed, not who said what. ### Should I include page and line numbers in the summary? Yes, at least for major changes. Point the editor to the specific pages, lines, figures, or supplementary files where each substantive change appears, and verify those numbers against the final clean manuscript before submitting. ### Can I use a table in the cover letter to summarize revisions? Yes, and for major revisions with many changes it works well, with one row per major comment showing the reviewer's point, your action, and the manuscript location. Plain-text tables travel safely through editorial systems, and a simple layout is easier for the editor to scan than an elaborate one. ### What if two reviewers contradict each other? Address both comments in the response letter, explain the conflict, and state how you resolved it and why. In the summary, one sentence is enough, for example noting that you adopted the analysis one reviewer preferred and explain the reasoning to the other in the response letter. The editor, not you, arbitrates persistent disagreements between reviewers.