When reviewing a publication preview, distinguish a file or layout issue from a decision about the book's content. Record both against the actual file, assign the appropriate review, and track any dependencies between them. Passing a technical preview does not resolve an editorial question, and a content correction may require another technical check.
Describe the observation before assigning its cause
A line may appear missing, a paragraph may seem incomplete, or a diagram may be difficult to read. Record what you observed and where before deciding why it happened. The cause could be an export problem, a source-layout choice, or wording that never supplied the necessary explanation.
Use the actual file version and a stable section reference alongside the preview location. This helps the responsible person reproduce the finding even if later pagination changes. A screenshot without a version or context can document an appearance while leaving the correction attached to the wrong manuscript.
Distinguish technical behavior from content meaning
A clipped caption is a layout problem; a complete caption describing the wrong image is an editorial problem. Both can be found during the same preview session, but they require different evidence for resolution. Label the concern according to what must be established, not merely according to the tool in which it was noticed.
Some findings involve both. A chart label may be unreadable and also use the wrong term. Preserve those as separate checks so fixing the font size does not silently close the terminology issue. The checklist should make the full problem visible without forcing every observation into one broad category.
Assign the review to the appropriate person or record
Technical questions may require examination of the source settings and the exported file. Editorial questions may require the manuscript brief, source evidence, or author judgment. Identify what information is needed and who is responsible for reaching the conclusion.
Do not treat an automated preview result as a substitute for a decision it does not evaluate. A file can render successfully while containing an unsupported claim or a confusing instruction. Conversely, an approved paragraph may still need production repair if it does not survive correctly in the reader-facing output.
Connect the correction to its dependent checks
If the wording changes, determine whether the revised length affects layout. If the layout changes, determine whether a caption, cross-reference, or figure relationship needs another editorial look. Record these dependencies so the checklist follows the consequence of the correction rather than ending at the first repaired symptom.
For example, adding a missing explanation can move an illustration to another page. The editorial gap may be closed, but the placement and navigation now need review. Keep both conclusions attached to the revised file rather than carrying the old preview approval forward without examination.
Close findings with specific evidence
A technical finding can be closed with the inspected corrected output and the relevant check result. An editorial finding needs the approved content decision and supporting evidence where applicable. Avoid a universal done status that gives no indication of what was actually verified.
If a finding is determined not to be an error, record the reason and the scope of that conclusion. An intentional blank page or an unusual narrative device may be valid, but the next reviewer should not have to reconstruct that judgment from silence. Preserve the explanation outside the publication file where appropriate.
Reconcile the checklist before the release handoff
Review unresolved findings across both categories and identify any corrections that still await a new export. Confirm that the final preview belongs to the file named in the release inventory. A clean result from an earlier candidate cannot establish the state of a later replacement.
Use current KDP formatting and submission guidance for the technical requirements, while retaining the authorial and factual review that the book needs. The resulting checklist should show what the file checks established and what the editorial review established. Publication preparation becomes more reliable when those conclusions support each other without being mistaken for the same kind of evidence.
Frequently asked questions
Clear answers for this publishing decision.
Can one preview finding create two checklist items?
Yes. A figure can have both a rendering issue and a content error. Separate the conclusions when they require different evidence, while keeping their relationship visible in the correction record.
Does a successful preview establish editorial accuracy?
No. It does not prove the truth of claims, the clarity of instructions, or the coherence of the narrative. Those questions need the appropriate content review.
What should be checked after an editorial correction?
Assess its production effects, including pagination, figure placement, and references. Export the revised file where needed and attach the resulting technical approval to that actual version.
Which trim size, page count, margins, and bleed setting work together for my paperback?
Check the complete combination first: a trim size, ink and paper type, and page count must be a supported KDP set, and the page count then fixes the minimum inside margin and whether the interior needs a bleed page size.
Set the format in a book project