Peer review revision is not a single editing pass. It is a workflow with three distinct jobs: reading reviewer comments as evidence, turning each comment into a documented change or counterargument, and preparing a resubmission package that shows the editor exactly what changed. This guide gives you a diagnostic framework for your current state, a decision table for handling comments, and linked sub-workflows for organizing evidence, checking citations, and preparing the next version. If you draft the response letter carefully and keep your evidence organized from the first read, the revision becomes a headed, finite task instead of an open-ended reset.
What kind of revision are you facing right now?
Before you open the response template, diagnose the state of the manuscript and the comments. Most revision problems come from trying to solve a response-letter problem with a research problem, or a methodology problem with an editing problem. Start with a two-minute self-check.
A useful starting sequence is:
- Read every reviewer comment once without opening the manuscript.
- Sort each comment into one of four categories: claim, method, reporting, or fit.
- Mark whether the comment requires new evidence, a reanalysis, a rewrite, or a justification.
- Check whether comments cluster around one section or one type of evidence.
If most comments are reporting-level, your revision is primarily a documentation and citation task. If most comments demand a new analysis or a different interpretation, the revision is a research task that needs its own evidence plan. The COPE ethical guidelines for peer reviewers describe review as depending on trust and expect constructive assessment, so treat reviewer language about clarity or completeness as a request for better evidence and reporting, not as a reason to restart the project.
How do you turn reviewer comments into a change list?
Work comment by comment, not section by section. A comment that says "the comparison group is unclear" may require a methods edit, a results rephrasing, and a new table note. If you work section by section, you will miss the links between comments.
Build a change list with one row per comment and four columns:
- Comment number and quoted fragment
- Your decision: change, clarify, or rebut with justification
- The location of the change in the manuscript
- The evidence or source that supports the change
For a thesis chapter or course paper receiving supervisor feedback, the same table works at smaller scale. The artifact matters: a written change list is the raw material for your response letter, and it is also the document your supervisor or co-authors can review before resubmission. The ICMJE recommendations tell authors to follow the selected journal's current instructions for article type, format, required statements, and submission materials, so treat the change list as an internal working document while the response letter itself follows the journal's requested format.
Which comments need new evidence, and which need a better explanation?
Use a decision table to sort comments before you act.
| Reviewer statement indicates | Most likely decision | First action |
|---|---|---|
| A factual claim is unsupported or seems incorrect | Add or correct the evidence | Find the primary source in an organized reference set |
| The method or analysis is unclear | Clarify and report transparently | Rewrite the relevant method passage and add reporting detail |
| The interpretation goes beyond the data | Narrow the claim | Revise the sentence-level claim to match the evidence |
| The reviewer misread a section | Clarify and gently point to the text | Rewrite the passage for directness; note the change in the response |
| The comment conflicts with a stated journal requirement | Follow the journal instruction | Cite the instruction in your response, not in the article |
This table prevents the most common revision error: treating an ambiguity as a missing experiment. When the NIH describes scientific rigor as the strict application of the scientific method, including transparent design, methods, analysis, interpretation, and reporting, the practical revision meaning is that many reviewer comments are reporting requests. Fix the reporting first, then assess whether the underlying design still needs work.
How do you build the evidence base before you rewrite?
The rewrite is faster and safer when the evidence is already collected. If you are reworking a thesis chapter or a first manuscript, create a project-specific evidence set before touching the prose. Keep the sources that support each revised claim together with the reviewer comments they address.
A practical order for the evidence pass is:
- Create or reopen a dedicated project for the revision.
- Save the manuscript PDF and the reviewer comments in one place.
- Add the sources you cite in the revision to a single reference set.
- Confirm every reference resolves to a real paper.
- Upload the subset of papers that directly support your revised claims.
- Ask targeted questions against those papers only when a claim needs checking.
You can set up the container for this work in Research Projects and keep the papers you are citing in My Library. Once the papers are saved, Library QA gives you a focused way to check a specific claim against papers already in your library, which helps keep the revision tied to the evidence you actually collected rather than a broad search re-run.
How do you verify the references before you resubmit?
A resubmission with a broken or hallucinated reference wastes the editor's time and signals weak revision discipline. Check the reference list as its own checklist item, not as a formatting afterthought. For each entry, confirm that the paper exists in a real academic database and that the metadata in your BibTeX matches it.
TrueCite is built for this check: it screens BibTeX against academic databases to flag references that do not correspond to a real paper. Run this after you have finalized the reference list but before you generate the final PDF. The result is a fact you can act on, not a vague quality promise: a flagged entry means you find the correct source or correct the metadata before submission.
What does a useful response letter actually contain?
Write the response letter after the manuscript is revised, not before. It should be organized by reviewer and by comment, and it should quote or paraphrase each comment accurately enough for the editor to find the corresponding change. For every comment, state what you changed and where, or why you did not change it and what evidence supports your position.
A working template looks like this:
Reviewer 1, Comment 3
Comment: "The authors should clarify how cases were selected."
Response: We added a sentence to the Methods describing the inclusion criteria and attached the selection flowchart as Figure 1. This follows the materials and reporting information required in the journal's instructions.
Keep the tone factual. COPE's guidelines describe peer review as depending on trust, and a response letter builds trust through precision rather than defensiveness. If you disagreed with a comment, state the disagreement in terms of the evidence and the journal's requirements.
What is the difference between a revise-and-resubmit and a reject-and-resubmit?
Both require a new manuscript, but the revision strategy differs. A revise-and-resubmit usually means the editor wants the paper back in the same journal with the requested changes. A reject-and-resubmit often means the paper did not meet the bar in its current form, but the work might be suitable after substantial change or repositioning.
For a revise-and-resubmit, preserve the paper's core structure unless a reviewer request explicitly requires restructuring. For a reject-and-resubmit, question the framing, the evidence standard, and the target journal before you rewrite. Your change list becomes the basis for deciding whether to revise for the same venue, revise for a different venue, or extract a smaller paper and place the rest in a new project. When the decision is to revise for a new venue, return to the ICMJE point about following the selected journal's current instructions: article type, format, required statements, and submission materials may all change.
How do you organize the resubmission package?
The resubmission package is the manuscript, the response letter, and any required reporting documents or marked-up copies. Before you send it, check each component against the journal's submission instructions. The checklist below is generic; the journal's own instructions are always the controlling document.
- Manuscript with changes visible or tracked as requested
- Response letter organized by reviewer and comment
- Clean and marked-up versions if the journal requests both
- Updated reference list, verified against real databases
- Required statements, data availability notes, and conflict-of-interest forms
- Any supplementary files referenced in the manuscript
The package is ready when every reviewer comment has a matching response, every reference resolves, and every promised change actually appears in the manuscript. This is the end state of the workflow: not "I think it is better," but "I can point to each comment and each change."
What should your first next action be after reading this guide?
Pick the action that matches your diagnosed state. If you have a full set of reviewer comments, build the change list today, before opening the manuscript. If you are preparing a first submission rather than a revision, run the same checklist on your own manuscript: sort your claims into evidence-supported and explanation-needed, verify the reference list, and write a one-page summary of what each section proves. If you are between projects, use the same system to reset: archive the finished project in one place and start the next project with its own evidence set.
A concrete first action for a researcher with reviewer comments in hand is this: create a revision project, open the decision table, and classify the first five comments. That ten-minute pass tells you whether the revision is primarily a reporting fix or an evidence-building task. For a first submission, the first action is to run the reference check before you write the cover letter. For a winter-break cleanup, the first action is to move last term's papers into a single library and archive the finished files, so the next project starts with a clean evidence base.




