Use this KDP first book checklist to decide whether the files, product description and actual reading experience agree before promotion. A successful upload is only one check. You also need a reader to navigate the book, complete its useful exercises and encounter the edition you intended to release.
This checklist produces a proof-review log and a release decision. Have your editable manuscript, cover source, contributor permissions, current metadata and a separate review copy available. Allow time for a physical proof if you are publishing print. Delivery and platform review depend on the project; do not book a launch around an assumed approval date.
1. Freeze an identifiable version for review
Give each manuscript, cover and exported file a version and date. Record the format, trim size where applicable, intended marketplace and the person responsible for each file. Keep the editable source as well as the uploaded export. If a formatter leaves, a PDF alone may not be enough to make efficient corrections.
Create a review folder containing the files under test, a copy of the description and a blank issue log. Avoid filenames such as “final-final-new” that conceal which version reached KDP. A simple release identifier, such as BALCONY-01-R3, can connect the manuscript, exported interior and proof order.
Read the book-project planning guide first if the reader result or contributor rights remain unclear. Proofing cannot resolve an undefined proposition or a missing permission. Mark those as release blockers rather than hiding them among punctuation corrections.
2. Check the promise against the actual contents
Read the title, subtitle, description and contents page together. Make a list of every concrete promise: beginner suitability, included worksheets, illustrations, coverage or outcomes. Find where the book delivers each one. Remove unsupported promises or complete the missing material before launch.
For a hypothetical balcony-gardening workbook, “plan your first container garden” should lead to a completed planning exercise. If the book advertises a printable shopping list, ensure that list exists and is usable. If a chapter depends on plant-care expertise, have an appropriately qualified reviewer check the advice rather than relying on a spellchecker.
Check the order of instructions. A novice should not have to choose containers before learning how to observe the space that constrains them. Read each task from the reader's starting point and mark any missing definitions, unexplained tools or prerequisites. These are content defects, even when the page looks polished.
Ask a sample reader to follow one representative exercise without coaching. Record where they stop and what they expected next. Do not describe that small check as proof of market demand or comprehensive usability testing; its purpose is to expose preventable confusion.
3. Review the digital reading experience
Use the preview tools applicable to the format you are producing. Inspect navigation, chapter starts, headings, tables, captions and image placement. Try the reading conditions your audience is likely to use, including narrower screens and changed text size where the format permits it.
A table that looks attractive on a large monitor may be unreadable on a phone. A manually constructed contents page may display correctly yet fail to navigate. A diagram's labels may become too small after conversion. Log the actual symptom and location so the person repairing the file can reproduce it.
Check links intentionally. A reference should lead to the promised resource, and any external download should have clear access conditions. Do not imply that the reader must join a mailing list to receive something sold as included without making that condition clear before purchase.
Amazon's content guidance makes the publisher responsible for rights and the customer experience. Review it against the files you are actually uploading, including the workflow used for AI-generated elements if applicable. KDP content guidelines.
4. Use a print proof for physical defects
If you are publishing print, inspect a physical proof for trim, margins, gutter, cover alignment, spine legibility, image clarity and usable writing space. Screen review and print review answer different questions. A clean PDF cannot demonstrate whether a worksheet is comfortable to write in after binding.
KDP distinguishes proofs from author copies. Proofs are prepublication review copies with identifying markings; author copies concern the live edition and do not include unpublished draft changes. Neither purchase generates royalties or appears as customer sales in KDP Reports. KDP proof and author copies.
Record which file version the proof represents. If you correct a diagram after ordering, that physical copy cannot validate the correction. Decide whether the change can be checked reliably in the applicable preview or warrants another physical proof. A changed trim specification or a major layout revision usually needs more than a verbal assurance that “the text is the same.”
Budget proofs and shipping as production expenses. Keep their receipts separate from royalties and promotional purchases. A box of author copies can be useful for events or distribution, but it is not evidence that independent readers chose the book.
5. Turn observations into a repair log
Give each defect an identifier, location, severity, owner, proposed repair and retest result. Use release-blocking for rights problems, missing promised material or unusable files; use major for substantial reading friction; use minor for cosmetic defects that do not alter meaning.
Here is a completed hypothetical log:
| ID | Observation | Decision | Retest evidence |
|---|---|---|---|
| Q01 | Worksheet instructions refer to a missing table | Block release; add the table and check references | Sample reader completes the sequence in R4 |
| Q02 | Light-level diagram labels disappear on a narrow screen | Replace layout and enlarge labels | Reviewer checks the converted R4 file |
| Q03 | Cover subtitle differs from description | Reconcile intended wording across files | Cover and metadata compared side by side |
| Q04 | One paragraph has inconsistent punctuation | Correct during copy pass | Second reviewer checks the marked paragraph |
Avoid vague closures such as “fixed.” Name the new file and the check performed. A designer may repair the cover but accidentally export the old interior; the release log should make that mismatch visible.
6. Perform a clean second pass
After repairs, review the corrected export from the beginning. Do not inspect only the marked pages. Pagination, contents entries and cross-references can change when text moves, and fixing a table can introduce a blank page or a new overflow.
Separate the passes to preserve attention: first reader logic and factual meaning, then navigation and layout, then language consistency, then metadata and rights. Assign another reviewer where possible. If you work alone, leave a gap between passes and use a checklist so familiarity does not replace examination.
Check every contributor credit and attribution against the actual permission record. Verify that the files required for later updates are present and accessible. A rights register should identify unresolved scope issues; proof approval should not silently convert them into assumed permission.
Keep a rollback copy of the previously reviewed files. If a late change breaks the export, return to a known state rather than reconstructing the book under launch pressure. A small delay is easier to manage than promoting an edition you already know is defective.
Check that the exercise survives the reading format
Choose one exercise from the checked manuscript and complete it using the intended reading format. Record the manuscript version, device or print proof and the supporting files used. Do not judge only the editor preview.
Check heading order, table navigation, link destinations, image descriptions and whether the reader can obtain or reproduce the worksheet. A page reference that works in print may fail in a reflowable eBook. A graphic containing the only copy of the instructions can exclude readers who need accessible text.
For a hypothetical “compare two supplier quotes” lesson, confirm that both quotes use the same units and that a reader can enter and check their result. Log an inaccessible table as a task-blocking defect; a punctuation correction belongs in a different severity class. Repair and replay the same exercise before approving that version.
KDP's preview tools support format inspection. They do not establish learning effectiveness, legal clearance or market demand. The learning-evidence guide provides a separate method for observing whether instruction enabled the promised task.
7. Match the public listing to the release
Before submitting or promoting, compare the title, subtitle, contributor names, description and format details with the final files. Check that illustrations, worksheets and other advertised features are actually included. Use accurate reader language rather than claims of superiority or artificial urgency.
The reader-discovery guide explains how to plan a bounded metadata experiment after the quality check. Keep those activities separate: changing a keyword cannot repair a missing chapter, and a launch discount cannot make unclear instructions usable.
Make a final decision record with the release identifier, reviewer names or roles, remaining issues, accepted limitations and approval responsibility. This is your operating record, not a claim that Amazon has accepted the book. Platform review remains separate, and your own acceptance standard can be stricter than a successful upload.
A practical release worksheet
For the balcony example, the release note might read: “R4 interior and R3 cover reviewed together. The planting-plan exercise was completed by a sample reader. Digital navigation checked. Print proof matches current trim and cover. Two minor style corrections remain documented; no rights or reader-function blockers remain.” That note tells a future editor what was examined and what was not.
Use these sign-off fields for each format, marking a check not applicable only with a reason:
- Release identifier, interior version and cover version match the reviewed exports.
- Description promises have a matching page, exercise or included resource.
- Navigation, links, diagrams and tables work in the converted edition.
- Print proof represents the current files, or remaining physical checks are explicitly unresolved.
- Rights, credits and any applicable AI-content declarations have been checked.
- Every blocker and major defect has a documented repair and retest; minor accepted issues have an owner.
- A responsible reviewer records the date, decision and next maintenance trigger.
Keep the decision on hold when a consequential check remains unresolved.
Attach the issue log, proof order details, current exports, editable sources and contributor records. Add a maintenance trigger: review broken links or dated references when notified, and schedule substantive specialist review when the advice changes. A first edition should be maintainable without depending on the original formatter's memory.
If a blocker remains, write the next action precisely. “Await photo license from illustrator by Friday; substitute original diagram if unavailable” is executable. “Improve quality” is not. Do not launch while the plan depends on a permission that nobody has obtained.
Can I skip the physical proof?
A digital-only edition does not need a print-copy check. For print, skipping a physical inspection leaves binding, paper and physical usability untested. Record that limitation explicitly and weigh it against the cost and timing of a proof.
How much feedback is enough?
Enough to resolve the specific defects you are checking, with clear limits. One reader completing an exercise is useful evidence about that exercise; it does not certify every chapter or predict purchases. Test the most consequential tasks first and expand when failures suggest a wider problem.
What should I keep after release?
Retain the exact released files, editable sources, permissions, repair log and metadata record. These records support updates and a future catalog evaluation. They do not themselves establish permission to transfer a KDP account or individual titles.

