Inspect the editable source and the exported file for review material that does not belong in the published book. Resolve tracked changes deliberately, remove obsolete comments and placeholders through the proper document controls, and examine the actual output. Current KDP file guidance excludes several kinds of annotations and production artifacts, so a clean editing view alone is not sufficient evidence that the export is ready.
Preserve the review record before cleaning the source
Save the annotated manuscript and relevant editorial decisions as an archive before removing working material. Comments can explain why a passage changed, and unresolved revision marks may identify decisions the author has not made. Cleaning the source should not erase the only record of those questions. Establish which manuscript is the approved basis for publication and which copy preserves the editorial history for later reference.
Give the archive a clear status so it cannot be mistaken for the upload candidate. A file named only with a recent date may still look attractive to someone searching for the latest version. Record the relationship between the annotated source and the publication copy. The goal is to retain useful evidence while making it unambiguous that comments, proposed wording, and abandoned alternatives belong to the working history rather than the reader-facing edition.
Resolve revisions rather than hiding their display
Inspect the document's actual revision state using the controls available in the authoring application. Changing the display so marks are not visible may not resolve the underlying edits. Review additions and deletions against the author's decisions, then accept or reject them deliberately. If the meaning of a proposed change remains uncertain, return it to the editorial issue list instead of treating invisibility as approval.
Pay special attention to passages with overlapping revisions from several contributors. One suggestion may depend on another change that was later rejected. Read the resulting paragraph as continuous prose after resolving the marks. A technically clean revision state does not prove that the final sentence retains the intended meaning or grammar. Keep the approved decision and the actual resulting text connected before moving on to export preparation.
Search for production-only language and placeholders
Review the source for notes such as missing illustration reminders, provisional headings, temporary references, and questions addressed to an editor. Use targeted searches based on the notation your project actually used, but do not rely on one universal placeholder word. A reminder may appear in a caption, a text box, or an appendix rather than in the main narrative. Check those locations according to the structure of the manuscript.
Distinguish genuine book content from working language before deleting anything. A fictional letter containing the word "draft" is not automatically a production note. Similarly, an intentional exercise prompt should not disappear because it resembles an editorial question. Review matches in context and record unresolved cases. Automated searches can locate candidates efficiently, but the author must decide whether each passage belongs to the approved reading experience.
Inspect the export for artifacts the source view can miss
Create a fresh candidate using the intended output settings and open it outside the source application. Inspect pages where comments, special objects, or revision marks previously appeared, then review the rest of the file for unexpected material. Look for visible annotations, placeholder content, unwanted marks, missing text, and layout changes introduced during cleanup. The current KDP submission guidance should be checked for the specific file requirements that apply to the intended format.
Use available document-inspection or preflight information within its stated scope. A report may help identify certain objects, but it does not replace reading the final pages. Keep the file identity and export settings with the findings so the review refers to a particular artifact. If cleanup produces a new export, do not attach an earlier report without checking whether its evidence still applies to the replacement file.
Approve a reproducible clean package
Compare the cleaned source with the approved editorial decisions to ensure that removing review material did not remove intended content. Record the final file names, version identifiers, and checks performed. Keep the annotated archive separate from the delivery folder while preserving a clear link to it. The uploader should receive a defined publication candidate, not a choice between several similarly named copies with different revision states.
If a late correction is made, repeat the affected cleanup and export checks. Review comments can reappear when text is copied from an older file, and a rushed edit can introduce a new placeholder that never receives a final pass. A repeatable process protects the editorial history without exposing production-only material in the book. The finished package should be traceable to an approved source and inspected as the actual file intended for submission.
Frequently asked questions
Clear answers for this publishing decision.
Does hiding tracked changes mean they have been resolved?
Not necessarily. Display settings and the underlying revision state are different. Inspect the actual document controls and accept or reject changes according to the author's decisions before preparing the publication copy.
Should the annotated manuscript be deleted after cleanup?
No. Preserve it as a clearly marked archive if it contains useful editorial history. Keep it separate from upload candidates so retaining the evidence does not create ambiguity about which file is approved.
Can a placeholder search replace a final export review?
No. Searches may miss objects or project-specific notation and can also flag legitimate content. Review matches in context and inspect the actual exported file for unwanted material and layout consequences.
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