01
Request Register sheet
One row per request, numbered reviewer, comment, part, with the clause quoted verbatim rather than summarised. A summary is already an interpretation, and the interpretation is what quietly narrows a request into something easier to answer.
02
Conflict and Overlap Map sheet
The register run against itself. Where one change answers two reports, and where satisfying one report means refusing another. In the worked example that is four shared changes and two real conflicts.
03
Disagreement Log sheet
Every decline with a reason class, the evidence behind it, and the reviewer's strongest reply written out. If that reply comes easily, the decline is not finished and it will be back.
04
Response Letter
In the reviewer's numbering, with each part of a multi-part comment answered separately and labelled. Disposition first, then the change, then the location, because the reader is scanning for the disposition and it gets missed under two sentences of thanks.
05
Editor Cover Note
Under a page, and a different document from the letter. What changed, the count, the conflicts that need adjudicating, and the declines in one line each. Nothing about any reviewer.
06
Revised Manuscript Note
What is in the package, how much of the file moved, and any change nobody asked for. An unexplained difference between two versions costs more attention than the correction it hides. If the decision goes the other way and the paper moves journals, the reformatting is a separate job.
07
The pre-resubmission check
Six counts before anything is uploaded: requests, made, made in part, declined, missing locations, missing responses. Line numbers move when text is added above them, so every location gets opened and confirmed in the current file.
08
A numbered comment is not one request
The standing space rule every prompt reads first. Anything a reviewer could later say was not addressed becomes its own row, including a bare question, because an unanswered question reads as an evasion.