Prepare your manuscript for Amazon KDP: pre-publish checklist

Self-publishing on Amazon KDP saves time — not rigor. Readers expect the same quality as traditional publishing. Here's a narrative + technical checklist before upload, with SagaScope's role in the chain and errors that cost negative reviews.

For tool positioning, see KDP / long-form writing software on our site.

In brief

• Coherence first: names, dates, promises, relationships.
• AI committee + human beta before final polish.
• SagaScope aligns the manuscript; Vellum/Atticus format.
• Prepare metadata and blurb before upload.
• Order a proof copy and test Look Inside.

1. Narrative coherence

Before any export, verify the substance holds:

• Fixed facts (names, ages, recurring objects) checked
• Timeline: durations and event order
• Narrative threads: promises paid or cut
• Relationship graph: no « forgotten » character
• Style analysis: no involuntary drift at the end

See the DOCX/EPUB/PDF export guide for the full technical chain.

Narrative errors that kill KDP reviews

2. Human and AI proofreading

• Spelling / typography: Grammarly, ProWritingAid, Antidote depending on language
• Beta readers on at least one full act — targeted questions, not « what do you think? »
• Simulated reading committee as pre-filter (AI committee): consensus on boredom, credibility, pacing
• Final pass: you alone, reading dialogue aloud

Recommended order: narrative threads → AI committee → revision → human beta → polish → export.

3. KDP metadata (prepare before upload)

Look Inside (free preview) uses your opening chapters: ensure your opening hooks work without external context.

4. Technical export

• Chapters with consistent titles (e-reader navigation)
• No weird tabs inherited from Word
• Clickable table of contents in EPUB
• Clean page breaks between chapters
• Cover at KDP dimensions (ebook + paperback separate)

SagaScope → formatter workflow

1. SagaScope: coherence, threads, timeline, style
2. DOCX export from SagaScope (or structured copy)
3. Vellum / Atticus / Reedsy: layout, TOC, typography
4. EPUB from formatter → KDP upload
5. KDP preview: check on phone and e-reader

SagaScope doesn't format your final ebook — it aligns the manuscript so export doesn't propagate narrative errors.

KDP paperback: specific points

Ebook and paperback share the manuscript but not the constraints:

A manuscript narratively aligned in SagaScope avoids discovering at the paperback proof that a character changes name in chapter 40 — costly to fix after printing.

5. Post-upload

• Order a proof copy if paperback (margins, trim, cover)
• Test on Kindle: table of contents, links, mobile rendering
• Check Look Inside as a new reader would
• Watch early reviews for patterns (pacing, ending, coherence)
• Fix glaring typos quickly (KDP allows ebook updates)

Common post-upload errors

• Broken EPUB TOC: chapters not navigable → « badly formatted » reviews
• Pixelated cover: unreadable Amazon thumbnail
• Misleading blurb: marketing promise ≠ book → 2-star « disappointed » reviews
• Unseen inconsistencies: names, dates — flagged in comments week 1

Where SagaScope fits

If you import an existing manuscript, start with magic ingestion then follow this checklist.

Use case 1 — Pre-export: orphan mystery avoided

Before DOCX export to Vellum, you walk narrative threads: one thread « the killer's identity » is set up in ch.5, never resolved. You write the payoff in ch.38 or cut the setup — before 200 KDP readers flag it in reviews. SagaScope did what a linear re-read would have missed.

Use case 2 — Paperback proof: name inconsistency

The proof arrives: a character is « Élise » until ch.20 then « Elise » for no reason. Codex pass + name search in SagaScope: a variant left from an old draft. Fix, re-export, re-upload — far cheaper than reprinting after « inconsistent » reviews.

FAQ

Which format for KDP ebook?

EPUB is the recommended standard; DOCX also goes through Amazon conversion. Check table of contents and chapter breaks.

Do you need a coherence pass before upload?

Yes. KDP readers are ruthless on name, date and relationship inconsistencies. A facts + timeline + threads pass avoids « sloppy » reviews.

Does SagaScope replace an ebook formatter?

No for final layout (Vellum, Atticus…). Yes for preparing a coherent manuscript before export.

Which KDP metadata to prepare upfront?

Title, subtitle, description (blurb), keywords (7), BISAC categories, author name and series if applicable. Write the blurb before upload to test the hook.

When should you run the AI reading committee?

After consolidating narrative threads and before final polish — see our AI reading committee article. Human beta remains essential before KDP.

Conclusion

KDP rewards manuscripts that are clean narratively and technically. Use SagaScope for coherence and structural revision, a formatter for layout, and real readers for emotion. The checklist isn't bureaucracy: it's what separates a « published » book from a book read to the end.