November 16, 2026

How to Write a Point-by-Point Response to Reviewers

A point-by-point response to reviewers is the document that turns a mixed set of referee comments into a clear path back to acceptance. Editors use it to check that every concern received an answer, and reviewers use it

Written byWisPaper TeamAI Research Workflow Team
Editorial illustration for How to Write a Point-by-Point Response to Reviewers

A point-by-point response to reviewers is the document that turns a mixed set of referee comments into a clear path back to acceptance. Editors use it to check that every concern received an answer, and reviewers use it to see whether their objections were understood. The response letter therefore works best when it is organized as a traceable ledger: each reviewer comment appears verbatim, followed by a short, specific answer and an exact pointer to where the manuscript changed.

This guide walks through the full sequence, from diagnosing where your revision stands to verifying that the response file is ready to submit. It includes a worked example drawn from a revised results section, a reusable checklist, and explicit completion criteria you can check before uploading. Along the way, it shows where a research workspace such as WisPaper helps keep the supporting evidence and citation changes auditable rather than buried in email threads.

What state is your manuscript actually in?

Before writing responses, separate the revision states. A helpful diagnostic is to read each reviewer comment and classify it into one of three groups: accepted and revised, addressed with a counterargument, or out of scope for this manuscript. Misclassifying a request is the most common reason a revised submission returns with the same concerns repeated.

Group 1 covers comments where you agree and have already changed the manuscript. Group 2 covers comments where you disagree and will explain the reasoning with evidence. Group 3 covers requests that belong to a different article, a future study, or a different journal format. For Group 3, the response still needs a sentence explaining why the request sits outside the current scope, but it should not pretend that a limitation does not exist.

This classification becomes the skeleton of the response letter. A column or colored tag next to each comment makes it easy for the editor to see that every item was categorized rather than skipped.

Which reviewer comments should you answer, and in what order?

Answer every numbered or bulleted comment in the order the reviewer wrote it. Do not group similar comments under one answer unless the reviewer did so; an editor checking completeness will scan down the original list and look for a response beside each item. If two reviewers raised the same point, answer each one in place and add a short cross-reference such as "see also our response to Reviewer 1, Comment 4."

For the ordering, keep the reviewer structure rather than a thematic structure. A thematic reorganization can make the revision read more smoothly, but it forces the editor to reconstruct which concern each response addresses. The response letter is a compliance document first and a narrative second. Within each reviewer's section, preserve the original comment numbers and quote the comment before responding.

If the journal combines editor comments and reviewer comments in one file, begin with the editor's summary. Editors sometimes add revision requests that reviewers did not mention, and those carry the same weight.

How do you format a response without losing information?

A standard format is a table or a repeated block with four parts: the reviewer comment, the author response, the manuscript location, and the revised text where relevant. The comment should appear word for word. The response should state the decision first, then the action, then the evidence. The location should give section, paragraph, and line or page numbers from the tracked-changes manuscript.

Where the journal author guidelines specify a response structure, follow it. Guidance such as the ICMJE recommendations reminds authors to use the selected journal's current instructions for submission materials, and a response letter is part of that package. If the journal asks for tracked changes plus a clean copy, provide both; if it asks for responses inserted directly beneath each comment, do not substitute a separate table.

Keep quotations accurate. A response that paraphrases a reviewer comment before answering can reshape the concern. Use copy-and-paste from the decision letter and preserve the original numbering.

What should a strong response actually say?

A strong response uses a consistent sentence pattern: what you changed, where you changed it, and why the change resolves the concern. Avoid thanking the reviewer more than once, and avoid starting every response with "We agree" when the comment requires disagreement or a partial change.

For an accepted comment, a useful response reads: "We revised the Methods section to report the image acquisition settings. The new sentence is in the 'Microscopy' paragraph on page 7, lines 189–193." The revision itself should appear in the response letter only when the journal requests it; otherwise the location pointer is enough.

For a disputed comment, state the disagreement plainly, provide the evidence, and show the manuscript adjustment if one was made. A response such as "We did not add a second time point because the original study protocol limited data collection to baseline; we added this constraint to the Limitations section" resolves the concern without overreaching. The reviewer may still disagree, but the editor can see that the disagreement is reasoned and documented.

Peer review operates on trust, as COPE's guidelines for reviewers describe, and the response letter is where an author earns that trust by showing the work behind each answer. A claim that a reference was added is stronger when the reference and its role in the revised argument are visible.

How do you keep the evidence trail auditable while revising?

The response letter fails when it points to changes that cannot be found. Before writing the final version, each answer should resolve to one of three sources: a tracked change in the manuscript, an added or revised reference, or a documented decision with rationale. If a response says "we clarified this point" without a location, add one.

A working paper library helps keep the reference trail intact. Save the revised manuscript and the papers you used to answer reviewer concerns in one place, such as My Library, so the response references and the manuscript citations stay consistent. When the reviewer asks for additional citations, confirm that each new reference is real and correctly formatted before it enters the revised bibliography.

How do you verify every cited reference in the response?

A revised manuscript often adds citations under time pressure, and a response letter that attaches a fabricated or misformatted reference can damage the whole submission. Before finalizing, run the bibliography through a screening step that checks each BibTeX entry against real academic databases. TrueCite performs this check and flags references that cannot be located, which is useful right after the coauthor round and again before upload.

Do this before the coauthors sign off, not after. A reference that fails screening may require changing the manuscript text, and that change then needs its own tracked edit and response line.

How do you align the response with a revised results section?

Use a worked example to see the full pattern. Suppose Reviewer 2, Comment 3 states: "The authors do not report the number of excluded participants or the reasons for exclusion."

A weak response might say: "We agree; this was a good point." It answers nothing and adds no location.

A complete response would be:

Reviewer 2, Comment 3: The authors do not report the number of excluded participants or the reasons for exclusion.

Response: We added a participant flow description in the Results section. We now report that 214 participants were screened, 37 were excluded, and the exclusion reasons were prior enrollment in a related study, incomplete baseline measures, and withdrawal before the first session.

Revision: Results, "Participant flow" paragraph, page 12, lines 301–315.

This one example shows the classification, the action, the location, and enough detail for the reviewer to check the change without reopening the original concern.

How do you keep track of every response across long revisions?

Long revisions generate dozens of comments, and the main risk is losing one during coauthor edits. A project space that holds the decision letter, the response draft, and the assigned owners keeps the status visible. In Research Projects, you can create a project for the revision and keep the response ledger separate from the manuscript files, which makes the handoff to a coauthor or graduate student less prone to missing comments.

Use a three-column status during revision: Comment ID, Decision, Location added. Only when every Comment ID has both a Decision and a Location does the response move to the verification stage. If a coauthor adds a paper to the library during the revision, keep that paper linked to the project so the source of each new citation remains findable.

What does a reusable response checklist look like?

The following table is a working checklist, not a final format. Adapt the Location column to your journal's tracked-changes file.

#CheckPass when
1Comment captureEvery numbered comment from every reviewer and the editor appears verbatim in the response file.
2ClassificationEach comment is tagged as revised, disputed, or out of scope.
3No orphaned commentsNo comment lacks a response block below it.
4Action statedEach response says what changed or why no change occurred.
5Location statedEach revised or disputed response points to section, page, and line or paragraph.
6Revised text included where requiredWhen the journal asks for quoted revised text, it matches the tracked-changes manuscript exactly.
7Citation auditEvery new or edited reference exists and matches the in-text citation.
8Cross-references resolvedEach cross-reference to another response uses the correct reviewer and comment number.
9Coauthor sign-offEvery coauthor has reviewed the responses to their assigned comments.
10Journal format checkLine spacing, file type, and placement match the journal's current instructions.

How do you know the response is ready to submit?

Use concrete completion criteria rather than a feeling of completeness. The response is ready when all five of these statements are true:

  1. Every comment in the decision letter appears in the response file, verbatim and numbered.
  2. Every response contains either a tracked revision with a location or a documented rationale for not revising.
  3. Every new reference added during revision passed the citation check.
  4. No response points to a location that does not exist in the revised manuscript.
  5. The response file matches the journal's requested format and includes all required coauthor sign-offs.

Check the last criterion just before upload, because a coauthor edit can happen after the main response review. A final read-through that follows the reviewer's original numbering, rather than reading the response as a narrative, will catch the gaps editors also look for.

When the revised manuscript and response letter together form a traceable record of every decision, the editor can verify the revision without asking for clarification. That is the outcome a point-by-point response is intended to produce.

FAQs

Length follows the number and complexity of comments, not a fixed target. A response is long enough when every comment has an answer with a specific action and location, and short enough that no courtesy paragraphs or repeated descriptions add bulk. If the journal sets a page limit, compress the quoted revised text rather than merging comments.