A clear response to peer review helps an editor see what changed, why it changed, and where to find each revision. This guide provides a practical workflow for categorizing reviewer comments, deciding when to agree or explain a different choice, managing conflicting requests, requesting more time, and building a response letter and revision tracker that can be reused across review rounds.
Overview
A revise-and-resubmit decision is not simply a request to edit the manuscript. It is an invitation to show that you have considered the reviewers’ concerns carefully and responded to them transparently. A strong response letter does not need to accept every suggestion, but it should address every substantive comment respectfully and give the editor enough information to evaluate the revision efficiently.
Before revising, save the decision letter, reviewer reports, submitted manuscript, figures, supplementary files, and journal instructions in a single project folder. Check whether the journal asks for a particular response-letter format, tracked changes, a clean manuscript, line-numbered pages, anonymized files, or a separate document explaining changes. These requirements vary, so the journal’s current author instructions should take priority over a general template.
Use two connected documents throughout the process:
- A response letter that explains your answer to the editor and reviewers.
- A revision tracker that records each comment, its category, the action taken, and the location of the change.
The tracker is your control document; the response letter is the polished explanation you submit.
What to track
1. Separate comments before answering them
Read all reports once without drafting replies. On a second pass, divide comments into categories such as major methodological concerns, analysis or interpretation issues, requests for clarification, presentation and structure, references, language, and administrative requirements. Also mark comments that overlap. Two reviewers may be asking the same underlying question in different language.
Do not assume that a short comment is unimportant. A request to define a term, explain a sampling decision, or clarify a table may reveal a broader problem with reader comprehension. Conversely, not every suggested citation or optional analysis must be added if it does not fit the study’s scope. Record your reasoning either way.
2. Decide whether to implement, explain, or respectfully decline
For each comment, choose one of three initial actions:
- Implement: Make the requested change when it improves accuracy, transparency, analysis, or readability and remains consistent with the study design.
- Explain and adapt: Address the concern in a different but defensible way when the exact request is unsuitable. For example, you might add a limitation, sensitivity analysis, definition, or explanation rather than change the research question.
- Explain and decline: State why you did not make the requested change when it would introduce a methodological problem, exceed the study’s scope, duplicate existing material, or require data that were not collected.
Never answer a disagreement with “the reviewer is wrong.” Describe the constraint, acknowledge the value of the concern, and explain what you did instead. If the issue could affect the editor’s decision, make the rationale especially clear and consider flagging it in the cover note to the editor.
3. Link every response to a manuscript location
After editing, record the exact page, section, paragraph, table, figure, or line range where the change appears. Line numbers may change after formatting, so use the version required by the journal and update locations only after the manuscript is stable. If a response involves a new analysis, identify the method, result, and location of the relevant interpretation rather than merely saying that the analysis was added.
A useful revision-tracking table can use these columns:
| ID | Reviewer comment | Category | Decision | Action taken | Manuscript location | Status |
|---|---|---|---|---|---|---|
| R1-01 | Clarify participant selection. | Methods | Implement | Added eligibility and recruitment details. | Methods, paragraph 3 | Verified |
| R1-02 | Add an analysis outside the study scope. | Analysis | Explain and decline | Explained the design constraint and added a limitation. | Response; Discussion, limitation 2 | Verified |
Assign each comment a stable identifier, such as R1-01 for Reviewer 1’s first comment and R2-03 for Reviewer 2’s third comment. If a comment contains several requests, split it into separate rows. This prevents one completed action from hiding an unresolved sub-question.
Cadence and checkpoints
Use a staged revision workflow
- Day 1: Confirm the decision and deadline. Record the due date, required files, requested format, and any editor-specific instructions. If the decision letter is ambiguous, ask the editorial office a focused question before making assumptions.
- Early review: Build the tracker. Enter every actionable comment, group duplicates, and identify issues that affect the whole manuscript, such as terminology, study aims, or statistical reporting.
- Planning checkpoint: Resolve high-risk issues first. Discuss major methodological or analytical changes with coauthors before editing prose. Confirm whether new work is feasible, necessary, and consistent with the original design.
- Revision pass: Edit the manuscript and tracker together. Do not write the final response letter from memory. Complete an action in the manuscript, record its location, and draft the corresponding response while the change is fresh.
- Verification pass: Check both directions. Starting with the reviewer reports, confirm that every comment has a response. Then start with each response and verify that the claimed change exists in the submitted manuscript.
- Submission checkpoint: Prepare clean and marked files. Confirm that figures, tables, supplements, references, anonymization, declarations, and file names match the journal’s instructions. Remove internal notes and unresolved tracked changes from files that should be clean.
Response-letter structure
A practical response to reviewers template can follow this order:
- Thank the editor and reviewers for their assessment.
- State that the manuscript was revised in response to the reports.
- Summarize the main changes in a short paragraph or bullet list.
- Respond to the editor’s comments first, if applicable.
- Reproduce each reviewer comment, clearly labeled and separated from your response.
- Describe the action taken and provide the exact manuscript location.
- Explain any comment that was not implemented, including the alternative action or limitation.
- Close by identifying any remaining points that require editorial guidance.
For example: “Thank you for noting that the recruitment procedure was unclear. We expanded the Methods section to specify the recruitment setting, eligibility criteria, and sequence of enrollment. The revised text appears in Section 2.3, paragraph 2.”
For a declined request, use language such as: “We appreciate this suggestion. We did not add the proposed comparison because the study was not designed to collect the required measure. To address the underlying concern, we clarified the study’s scope and added this issue to the limitations section.”
When reviewers conflict
First determine whether the conflict is real. One reviewer may request more detail while another asks for brevity; both needs may be met by moving technical material to supplementary files and adding a concise explanation to the main text. If the requests genuinely cannot both be followed, prioritize the study’s validity, the editor’s instructions, and the journal’s scope. Explain the conflict neutrally and ask the editor for direction when the choice would materially affect the manuscript.
Requesting an extension
Contact the editorial office before the deadline, state the manuscript identification details, explain briefly why additional time is needed, and propose a realistic new date. Avoid waiting until the due date unless circumstances leave no alternative. Keep the request professional and do not imply that an extension has been granted until you receive confirmation.
How to interpret changes
The quality of a revision is not measured by the number of visible edits. Look for whether the manuscript is more precise, internally consistent, and transparent. A major comment may require changes in several sections: an amended research question may affect the abstract, introduction, methods, results, discussion, tables, and conclusion. Track those dependencies so that an apparently small edit does not leave contradictory wording elsewhere.
Use the following final checks:
- Does the abstract still match the revised results and conclusion?
- Do methods support every new analysis reported in the results?
- Do tables, figures, captions, and supplementary files use consistent labels and numbers?
- Have new references been checked for relevance, accuracy, and correct formatting?
- Have limitations been expanded where a response relies on an unavoidable constraint?
- Can an editor find each change without searching through the entire manuscript?
Do not promise outcomes. A complete response can lead to another review round, further clarification, or a different editorial decision. Your responsibility is to make the reasoning and revisions auditable.
When to revisit
Use this workflow at every revise-and-resubmit decision, not only when the reviewer reports are extensive. Revisit the tracker when a second review round arrives, when a coauthor proposes a late change, when the journal requests a transferred submission, or when an editor asks for a new file or explanation. A second-round response should not assume that earlier changes were understood; identify what was retained, changed again, or clarified.
Before each submission, check the journal’s current instructions for response letters, anonymization, file preparation, research-integrity disclosures, and revision deadlines. These conventions can change, and a previously correct file structure may not remain appropriate. A monthly or quarterly check is useful for an active research group that manages several submissions, while an individual author can revisit the checklist whenever a new decision arrives.
Action checklist: create the tracker, assign an ID to every comment, categorize each request, decide whether to implement or explain, link each response to a verified manuscript location, resolve conflicts with the editor’s guidance when needed, proofread the response letter, and archive the submitted files with the decision letter. This simple record turns peer review into a controlled revision process rather than a sequence of disconnected edits.