Answer every reviewer, and show you missed nothing.

The reviews are in. Now you have to answer all of them.

A revise-and-resubmit is not won by writing more. It is won by covering everything: every reviewer comment mapped to a stance you can defend, a response, a real change, and a place in the manuscript where that change can be found. Miss one buried sub-point, and it is the one the reviewer notices.

The Reviewer Response Builder gives you the finished object: a point-to-point response-to-reviewers letter where every comment is addressed and every change is traceable, and the quiet confidence that you missed nothing.

How it works, in five steps

1. Log every comment. Split the reviews into single comments, one per row. Nothing merged, nothing skipped.
2. Decide your stance. Accept, Partly, Disagree, or Clarify. Three-way honesty carries more weight with an editor than a wall of agreement.
3. Write the three parts. Your response, the exact change you made, and where it lives in the manuscript.
4. Check coverage. A live readout: how many comments addressed, how many still open, and a flag on the two failure modes, a disagreement with no reason and a claim with no change.
5. Assemble the letter. Export the response letter and a one-minute editor summary. Read it once as the editor will, then submit.

The part that makes it defensible: coverage you can show

Most response letters are written from memory and hope. This one produces an auditable object. Every comment maps to a stance, a response, a real change, and a findable location. The tracker rolls it up ("11 of 13 comments addressed, 2 open") and refuses to let a disagreement pass with no reason attached, because a disagreement with no justification is the failure mode that sinks a revision.

What's inside: 7 files

• Quick start PDFThe output first, a submittable response letter, then the five-step workflow, the four-stance guide, and the hard cases: contradictory reviewers, a hostile comment, a limit you cannot meet.
• Response Letter Builder HTMLLog comments, tag stances, see coverage update live, and export a formatted response letter. Offline, private, local-first.
• Reviewer response workbook WordThe fill-in path: the master comment-stance-response-change-location table, the stance guide, a tracked-changes checklist, an editor cover-summary template, and a before-you-submit checklist.
• Response Tracker ExcelThe coverage engine. One row per comment; the first sheet rolls up how many are addressed and flags a disagreement with no reason or a row marked done that is still empty. Opens with a worked example.
• Phrasebank MarkdownPortable phrasings: polite-but-firm disagreement, graceful concession, contradictory reviewers, editor openers, and an AI-assist section with guardrails.
• Worked example PDFOne realistic R&R taken end to end: raw comments, including a contradictory pair and a borderline-hostile remark, to a filled table, an assembled letter, and the editor summary.
• LicensePersonal license; group / facilitation license on request.

Who it's for

Authors facing an R&R, whether it is major or minor revisions. PhD students answering their first review. Clinician-researchers with more comments than time. Anyone who has to respond to reviewers and wants to be able to show they missed nothing.

Pairs with: the reviewer's side

This is the author's half of peer review. The other is the Reviewer's Notebook, which helps a reviewer tell a real methodological demand from a preference and write a review they would sign. Together they are Peer Review, both sides: the coverage you show as an author, and the standard you hold as a reviewer.

What it is not

Questions