Workflow Guide

Response to Reviewers

Point-by-point structure. Gracious but firm tone. Color-coded changes. The right response separates papers that get accepted from papers that don't.

The standard structure

Dear [Editor Name / Editor],

Thank you for the opportunity to revise our manuscript "[Title]"
(Manuscript ID: [ID]). We thank both reviewers for their thoughtful
and constructive comments, which have substantially strengthened
the paper.

We have addressed every comment in the point-by-point response below.
Major revisions include: (1) [change 1]; (2) [change 2]; (3) [change 3].
Throughout the revised manuscript, new and substantively modified text
appears in blue.

We respond to each reviewer's comments in turn below.

────────────────────────────────────────────────────────────
Reviewer 1
────────────────────────────────────────────────────────────

R1.1. [Reviewer 1's first comment, quoted verbatim]

Response: We thank the reviewer for this important point...
[Detailed response]

In response, we have revised Section X.Y as follows:

  [color-coded new/changed text]

R1.2. [Reviewer 1's second comment]

Response: ...

[Continue point-by-point]

────────────────────────────────────────────────────────────
Reviewer 2
────────────────────────────────────────────────────────────

R2.1. [Reviewer 2's first comment]

Response: ...

[etc.]

────────────────────────────────────────────────────────────
Summary of changes

We have made the following major changes in response to reviewers:
1. ...
2. ...
3. ...

We hope these revisions address all concerns and that the revised
manuscript is now suitable for publication.

Sincerely,
[Author Names]

Response patterns by comment type

Pattern 1: Accept the comment

"Reviewer X comment." → "We thank the reviewer for this point. In response, we have [specific change]. The revised text now reads: [new text]."

Pattern 2: Partially accept

"Reviewer X comment." → "We agree with the reviewer's underlying concern about [issue]. While we did not implement the specific change requested because [reason], we have addressed the underlying concern by [alternative change]. See Section X for the modified text."

Pattern 3: Respectfully disagree

"Reviewer X comment." → "We respectfully disagree with this characterization. [Evidence and reasoning]. We have, however, clarified the original argument to make this point clearer; see the revised wording in Section X."

Pattern 4: Out of scope

"Reviewer X comment." → "While we agree this would be an interesting direction, we feel it is outside the scope of the present work, which focuses on [specific scope]. We have noted this as future work in the Conclusion section."

Tone rules

  • Always thank the reviewer first. Even for harsh comments. "We thank the reviewer for raising this point..." sets a collaborative tone.
  • Use "we" (the authors), not "I" — even for solo authors.
  • Avoid "you" when addressing reviewers — use "the reviewer" or "Reviewer X."
  • Don't be defensive. "The original wording was unclear; we have rewritten..." is much better than "The reviewer misunderstood; we did mean..."
  • Be specific. "We have addressed this in Section 3.2" beats "We have addressed this throughout."

Common mistakes

  • Doing 100% of what reviewers ask. Looks weak. Some pushback (with reason) shows you understand your own work.
  • Doing 0% and arguing. Reviewers feel ignored. Editor sides with reviewers.
  • Hiding changes. Reviewers re-read your paper looking for changes. If they can't find them, they assume you didn't change anything.
  • Long-winded responses. Reviewers' time is limited. Get to the point. Pad with evidence, not throat-clearing.
  • Ignoring the editor's comments. The editor often has summary comments separate from reviewer comments. Address both.
Response letter template

TypeTeX includes a response-to-reviewers template with the standard structure, color-coded change tracking, and per-reviewer sections. Just paste your reviewer comments and write responses.

Try TypeTeX free

Frequently Asked Questions

How do I structure a response to reviewers?

Point-by-point. Copy each reviewer comment verbatim, then respond directly below it. Group by reviewer (Reviewer 1, Reviewer 2, ...), with each comment numbered. Start with a brief overall thank-you/summary, then dive into the point-by-point. End with a summary of major changes.

What tone should I use?

Gracious but firm. Always thank the reviewer for the comment (even harsh ones). Acknowledge valid points immediately. For points you disagree with, explain your reasoning calmly with evidence — don't dismiss. Reviewers are experts; treat them as such, even when they're wrong. The tone is closer to 'collegial colleague' than 'subordinate employee'.

Should I do everything reviewers ask?

Most things, yes — but not all. If a reviewer asks for something genuinely wrong (mathematically incorrect, outside scope, contradicting your design), explain politely why you didn't change it. Editors generally support authors who pushed back with good reasons. Doing 100% of everything looks weak; doing 0% looks combative; ~80% with thoughtful pushback on the rest is the sweet spot.

How do I show what changed in the manuscript?

Color-code or italicize new text in your response (e.g., 'In response, we have revised Section 3.2 to read: [italic new text]'). For substantial changes, include the relevant before/after side by side. The editor and reviewers shouldn't have to hunt for changes — make them obvious.

What's the standard structure for a response document?

(1) Editor summary letter (1 paragraph thanking + summarizing major revisions). (2) Reviewer 1 comments + responses (point-by-point). (3) Reviewer 2 comments + responses. (4) Reviewer N etc. (5) Summary of changes (1 paragraph at the end). Total length usually 5-15 pages depending on review depth.

How do I push back on a reviewer?

Three patterns. (1) 'We respectfully disagree because...' followed by evidence. (2) 'This is outside the scope of the present work because...' followed by why. (3) 'We have addressed a related concern by...' if their literal request is wrong but their underlying concern is valid. Always provide the underlying reason — never just say no.

How long should a response letter be?

As long as the comments require. Typical: 5-15 pages for a major revision, 2-5 for minor. The response is roughly proportional to review depth — major revision with 30 comments per reviewer needs more space than minor revision with 5. Don't pad; don't be terse. Match comment-by-comment.

Should I include the original comment text in my response?

Yes. Always quote the reviewer's comment verbatim before your response. Reviewers and editors don't want to flip back to the original review — your response should be self-contained. Make the comment text visually distinct (italic or boxed) from your response.

Is there a LaTeX template for response letters?

Yes. Most academic LaTeX distributions include responselatex or respond-to-reviewers packages. TypeTeX includes a response-to-reviewers template with the standard structure (editor letter, point-by-point per reviewer, summary). The template uses color-coded text for changes to highlight revisions.

More workflow guides