A KDP pre-publication checklist should do two jobs: catch predictable production mistakes before you export, then make clear what still needs a human decision. Software is good at finding a bracketed note left in chapter 14, a missing back-matter file, or a keyword field that is too long. It is not good at deciding whether a sentence reads naturally, whether your cover promises the right genre, or whether Amazon will accept every part of a listing.
The practical approach is to run automated checks first, while changes are cheap. Then proof the exported files, review your KDP listing as a reader would, and leave time to fix problems found in preview. Treat the checklist below as a final gate before upload, not as evidence that the book is flawless.
What software can catch in a KDP pre-publication checklist
Automated checks work best when the question has a clear, repeatable answer: does this text exist, is this field filled in, do these versions match, or did this export complete? A writing or publishing system can save you from the most common “I thought I removed that” errors.
Placeholders and production notes
Search the whole manuscript for markers you use while drafting. Common examples include:
- [TK], [TODO], [INSERT], and XX
- “come back to this” or “research this”
- bracketed editorial notes
- temporary chapter titles such as “Chapter name here”
- comments intended for yourself, an editor, or a formatter
Do not rely on memory. Run a book-wide search for every marker in your personal drafting vocabulary. Also search for double spaces, repeated punctuation, and accidental duplicate headings if your editor can identify them.
In Pendrilo, chapter and book find-and-replace makes this kind of final sweep practical, while comments and chapter notes remain separate from the manuscript text. Before exporting, resolve or remove comments that are no longer useful and confirm that no note has been copied into the reader-facing prose.
Missing, excluded, and out-of-order chapters
Software can compare a planned chapter list against the material included in an export. That matters when you have cut scenes, alternate endings, bonus chapters, acknowledgements, a reader magnet invitation, or a preview chapter from the next book.
Check that your front matter, body, and back matter are all present in the intended order. Confirm that deliberately excluded chapters really are excluded, especially if you keep old scenes or research material inside the same project.
A reliable final review asks simple questions: Is chapter 1 the first body chapter? Does the table of contents point to every included chapter? Is the epilogue present? Does the back matter appear only once? Is a “sample chapter” actually the correct sample?
Pendrilo keeps front matter, body, and back matter distinct, and lets you exclude a chapter from exports without deleting it. That is useful, but it also creates one more item to verify: review the export inclusion setting for any chapter that has changed late in the process.
Metadata completeness and consistency
Listing data is not part of your manuscript, but it is part of publication readiness. Software can flag empty fields and compare stored values across versions. Your checklist should include the title, subtitle, series name and number, contributor names, description, categories, keywords, publication date, territories, pricing, and enrollment choices such as KDP Select.
The important check is consistency. Your cover, title page, EPUB metadata, paperback interior, and KDP listing should use the same title and author name. A subtitle added to the Amazon listing but omitted from the title page may not stop publication, but it looks careless and can create confusion in reviews, libraries, or distributor records.
Keep a final metadata record rather than rebuilding the listing from memory. Pendrilo’s KDP listings can retain versioned draft and live keywords, categories, and HTML descriptions, which helps you see what changed between one release and the next. For the seven KDP keyword slots, use Pendrilo’s free KDP tools to check byte length before pasting them into your listing.
Export and file checks
Software can confirm that an EPUB, DOCX, or PDF was generated, but “export completed” is not the same as “file is ready.” Still, automated file checks are valuable for catching missing fonts, invalid markup, unusually small files, blank pages, broken internal links, and missing image alt text where your workflow supports it.
Use the right source file for the job. An EPUB is generally the ebook upload file. A print-ready interior PDF is for paperback or hardcover production. Do not assume a browser printout is interchangeable with a paperback interior designed around trim size, margins, headers, and pagination.
For print, compare the final page count used for your cover calculation with the actual interior PDF. A changed page count can make a previously correct spine width wrong. For ebooks, open the finished EPUB rather than judging only the editor view.
What software cannot proofread for you
Grammar tools, prose checkers, and validation reports are filters. They are not final arbiters. A manuscript can pass every automated check and still contain a continuity error, a misleading claim, or a paragraph that makes readers stop trusting the author.
Meaning, voice, and continuity
Software may identify repeated words, weak verbs, filler phrases, or possible grammar issues. Those flags can speed up a final pass, but they cannot reliably tell whether repetition is intentional, whether a short sentence creates suspense, or whether a character’s speech sounds like that character.
It also cannot fully protect you from story-level errors. If a character drives a blue car in chapter 3 and a black car in chapter 22, a codex or consistency tool may help surface the conflict, but you need to decide which detail is right. The same applies to timeline errors, changing place names, point-of-view slips, and contradictions between books in a series.
Pendrilo’s prose checker can flag weasel words, weak verbs, repetition, and filler phrases. Its Codex can track characters, places, items, and lore. Use both as prompts for review, not as instructions to accept every suggested change.
Reader experience on the page
A validator cannot tell you that a chapter break feels abrupt because the scene should end two paragraphs later. It cannot tell you whether a nonfiction heading hierarchy helps a skimming reader, whether a footnote distracts from the argument, or whether your acknowledgements sound appropriately personal.
Read the book in a different mode from the one you used to write it. Read aloud, use text-to-speech, print a few difficult chapters, or read on an ereader. Changing the format slows your eye down and makes omissions more visible. Pendrilo includes read-aloud and device previews, both useful for this stage, but the judgment still belongs to you.
Cover, blurb, and market fit
Tools can check cover dimensions and calculate a print template. They cannot tell you whether the cover signals cozy mystery when the book is actually romantic suspense, or whether the blurb gives away the twist readers expect to discover. They also cannot judge whether the opening sample delivers on the promise made by your categories and ad copy.
Ask a genre-aware reader to look at the cover, title, blurb, and first pages together. Give them a direct question: “What kind of book do you expect this to be?” If their answer is far from your intended shelf, revise the packaging before launch.
Retailer acceptance is a separate check
KDP makes the final decision about whether a particular book, file, cover, listing, or account activity meets its requirements. No writing app, formatter, or checklist can guarantee retailer acceptance. Amazon can change specifications, interpret content rules case by case, or find an issue that your local tools did not detect.
Before you upload, review the current KDP guidance for your format and book type. Pay particular attention to image rights, public-domain material, low-content classifications where relevant, AI-generated or AI-assisted content disclosures when required, accessibility information, and content that may trigger review.
After upload, use KDP’s own preview and validation messages. Fix every specific issue it identifies, then inspect the preview anyway. A file can pass a technical validation while still showing an unattractive page break, a heading stranded at the bottom of a page, or a blank page you did not intend.
For a paperback, order a proof before a wide launch whenever the budget and schedule allow. Screen previews are useful, but a physical proof reveals trim, contrast, gutter, paper appearance, and cover alignment in a way that no dashboard can fully reproduce.
A final workflow that keeps checks manageable
Run the following sequence after the manuscript is locked. Do not keep editing the text while you are trying to verify files; every late change can invalidate work already completed.
- Freeze the release version. Create a named snapshot or duplicate, and decide which file is the source of truth.
- Clear internal material. Search for placeholders, drafting markers, comments copied into prose, and excluded chapters that should not be published.
- Confirm book structure. Review front matter, chapter order, scene breaks, end matter, links, and samples.
- Review metadata together. Compare the title, author name, subtitle, series details, description, categories, keywords, price, and cover across every location.
- Export format-specific files. Generate the EPUB and the print interior from the locked version. Record the export date and version.
- Inspect the actual files. Test the EPUB on more than one screen size if possible. Review the interior PDF page by page, including the first and last pages.
- Proofread as a reader. Use read-aloud or a fresh device, and focus on missed words, repeated paragraphs, awkward breaks, and factual mistakes.
- Upload early enough to repair. Run KDP Previewer checks, read Amazon’s messages carefully, and leave room in your schedule for a corrected upload or a print proof.
If you want one place to keep the manuscript, chapter status, export files, and listing drafts together, you can try Pendrilo before your next release. Whether you use a single studio or separate tools, the principle is the same: automate the checks that are objective, then reserve human attention for the decisions readers and retailers will actually notice.
Use the checklist as evidence, not a guarantee
A completed checklist means you have reduced avoidable risk. It does not mean the book is immune to typos, reader disappointment, technical changes, or retailer review. That distinction is useful because it keeps you from waiting for impossible certainty.
Software should catch the mechanical problems: missing text, unfinished markers, incomplete metadata, inconsistent versions, and flawed exports. Human review should cover language, meaning, design, market expectations, and the final KDP preview. Put both steps on your release schedule, and you will upload with a far cleaner, more defensible package.
