Before uploading a paperback, resolve editorial comments in the working manuscript and produce a clean publication export. Inspect the exported file for both visible review marks and remaining annotations, while retaining the editorial history separately so cleanup does not erase unresolved decisions.
Separate a resolved decision from a hidden comment
Hiding the review pane can make a manuscript look finished while leaving comments or unresolved changes in the document. An editor may have asked whether a number is correct, whether a quotation is complete, or whether an image should be replaced. The absence of a visible balloon does not answer those questions.
Start by classifying the remaining comments according to their editorial state. A correction may be accepted and incorporated, rejected with a reason, or still waiting for a decision. Complete that work before preparing the publication file. Removing comments from an unresolved manuscript makes the uncertainty harder to find without making the text more reliable.
Preserve a review record outside the upload package
Keep a dated working copy containing the editorial history before cleaning the publication version. Record which manuscript revision becomes the basis for export. This allows the author to revisit a decision later without relying on annotations embedded in a file intended for readers or platform processing.
Keep the review archive distinct from the upload folder. Use names that identify purpose and version clearly enough for another person to choose the correct file. A folder containing several nearly identical PDFs called final is an avoidable handoff problem. The release package should point to one current export while the archive preserves the reasoning behind it.
Remove review material in the source application
Use the source application's controls to finish tracked changes and remove publication-inappropriate comments after their decisions are recorded. Check document sections that receive less attention, including front matter, tables, captions, and appendices. Reviewers sometimes leave instructions in ordinary text rather than in the application's comment system.
Search for the project's actual placeholder conventions, such as a distinctive editor tag or a note to insert an image. Interpret each match in context so legitimate manuscript content is not deleted accidentally. A search for the word note, for example, cannot distinguish an editor's instruction from a useful note written for the reader.
Inspect the exported file as a separate artifact
KDP's paperback submission guidance states that submitted files should not contain comments, annotations, placeholder text, and several other nonpublication elements. Consult the current guidance for the full requirements. Check the exported artifact itself rather than assuming that a clean-looking source document guarantees a clean upload file.
Inspect the pages visually and use the export or PDF tool's relevant inspection facilities where available. Record what the check actually covers. A visual page review can find a printed comment balloon, but it does not establish that every nonvisible annotation has been removed. If the tool cannot answer a required question, use a suitable inspection method before approving the file.
Keep reader annotations distinct from review annotations
A scholarly note printed as part of the text is not the same editorial object as a review comment attached to the file. Similarly, a workbook may intentionally contain spaces where readers will add their own notes. Explain this distinction in the review checklist so cleanup does not remove substantive content merely because its label includes the word note.
The decision should follow the element's purpose and implementation. Is it part of the book the reader is meant to receive, or part of the team's discussion about making that book? When a reviewer cannot tell, inspect the source and confirm the author's intent rather than using a broad deletion rule across all similarly named elements.
Recheck after the final correction
A late correction can reintroduce comments when someone exports from a review copy instead of the approved source. After any such change, repeat the relevant cleanup and export checks. Compare the new file with the prior approved version to confirm that the correction was included without restoring old review material.
Record the checked filename and version in the upload handoff. The person uploading should verify that exact artifact rather than selecting the newest-looking attachment from a message thread. Finish by confirming the page content in the platform's available preview process, while keeping the separate file inspection record for questions that a visual preview cannot answer.
Frequently asked questions
Clear answers for this publishing decision.
Is hiding comments enough before export?
No. Resolve their editorial questions and remove the inappropriate review material from the publication version. Then inspect the actual export, because display settings alone do not establish what the file contains.
Should I delete the annotated working manuscript?
Keep an appropriate review archive so decisions remain traceable. Store it separately from the clean release files to reduce the chance that a review copy is uploaded accidentally.
Can I remove every paragraph labeled note?
No. Some notes are intended book content. Identify the purpose of each element and distinguish substantive reader material from production instructions or attached review comments.
How do I get from an idea and a brief to an editable manuscript I can finish?
Write the brief first, generate a structure you can edit, then draft and revise the manuscript in reviewable sections so one change never overwrites work you already approved.
Start a book project from a brief