Assign Review Ownership When a Novel Has Two Editors

Give each editor a clear scope and define how decisions move into the master manuscript. Separate recommendations from author-approved changes, identify who resolves disagreements, and record the version each review covers. A publication checklist should show the evidence and owner for each completed check, not merely collect approval messages for different drafts.

Define the boundary between editorial passes

Write down the work each editor is expected to perform. One may focus on structure, pacing, and character logic while another handles sentence-level consistency and mechanical issues. The boundaries can overlap, but the overlap should be intentional. Without an agreed process, a copyeditor may polish a scene the structural editor is about to remove, or a later structural change may reintroduce wording that already needed correction.

Use a concrete handoff condition for the transition between passes. For example, the author may approve the main scene sequence before the copyedit begins, while a small set of unresolved questions remains explicitly listed. Do not label the manuscript "final" simply to make the schedule appear settled. A visible exception list is more useful than a broad completion label that everyone interprets differently.

Establish one master and identifiable review copies

Choose where approved changes are assembled and who controls that master. Give each review copy a clear version identifier and record when it was issued. Editors should know whether they are reviewing the same draft or successive drafts. If the author continues revising during a review, preserve those changes separately until they can be reconciled instead of quietly replacing the file the editor believes they are assessing.

Consider a scene reordered after one editor has left comments about pacing. Those comments may still be useful, but their original context has changed. Keep the connection to the reviewed version and assess their relevance before applying them. A newer timestamp alone does not establish that one file contains all accepted edits from another. The handoff needs a reliable account of which changes have entered the master and which remain proposals.

Route disagreements to a named decision-maker

Create a short issue record for conflicting recommendations. Include the passage, each recommendation, the reasoning, and the author decision. A disagreement about a character's deliberately unusual phrasing is different from an unambiguous spelling error. Preserve the distinction so one editor does not repeatedly restore a feature another removes. The aim is a coherent editorial choice, not a competition to make every comment disappear.

Assign the final creative decision to the appropriate person, usually the author, while respecting the expertise each editor contributes. If an issue requires a different specialist, such as a specific permissions question, identify that need rather than expecting either editor to certify it outside their scope. A checklist item should name the question being resolved and the evidence available, not imply that any editor's general approval covers every publishing responsibility.

Turn the checklist into evidence of a particular version

For each release check, record the owner, status, reviewed file, and outcome. "Continuity reviewed in draft 12, remaining issue C4 resolved in draft 13" is more informative than "continuity done." Keep unresolved items visible and identify what must happen to close them. This prevents the author from assembling a collection of individually reasonable approvals that refer to incompatible manuscript states.

Separate editorial approval from production approval. A copyedited source file can still produce an incorrect export, and an attractive PDF can still contain an unresolved story problem. Link the formatted candidate to the approved manuscript and inspect the exported files through their own review path. Current KDP requirements belong in that production and submission review; they should not be assumed complete because the prose has been edited professionally.

Reopen only the checks affected by later changes

When a late revision arrives, identify its consequences before sending the whole book back through every stage. A changed character name may require a focused consistency pass across text and artwork. A replaced climax may reopen structural and continuity questions. Record which checks were repeated and which earlier evidence remains applicable. This keeps the process proportionate without treating a small file difference as automatically a small editorial change.

Preserve the final master, resolved issue record, and matching review history with the release package. Thank-you messages and informal conversations can accompany the work, but they should not be the only evidence of what was approved. The finished process should let a future collaborator understand which version became the publication candidate, who reviewed its different aspects, and why outstanding disagreements no longer prevent a coherent handoff.