An agency book handoff should include approved source files, print and ebook deliverables, cover assets, metadata, rights and disclosure notes, change history, and a clear client upload checklist.
GUIDES · AMAZON KDP
Agency Client Book Delivery Checklist
An agency book handoff should include approved source files, print and ebook deliverables, cover assets, metadata, rights and disclosure notes, change history, and a clear client upload checklist. This page explains the decision, production steps, risks, and final review required for a KDP-ready edition.

Product proof
See it in BookWizard
The direct KDP answer
An agency book handoff should include approved source files, print and ebook deliverables, cover assets, metadata, rights and disclosure notes, change history, and a clear client upload checklist. The decision should be made from the final book specifications rather than a generic web template.
The intended reader or decision context is specific: obtain written approvals for manuscript, cover, pen name, rights, AI use, ISBN, price, and listing copy. That scope keeps the project aligned with the book readers will actually receive.
Inputs to settle first
Before production, obtain written approvals for manuscript, cover, pen name, rights, AI use, ISBN, price, and listing copy. Record these choices in the project brief so drafting, design, and metadata use the same assumptions.
This is especially important for KDP because a late edition change can affect pagination, cover dimensions, identifiers, listing fields, or distribution choices.
A practical Agency Client Book Delivery Checklist workflow
The operational approach is to package versioned deliverables with a manifest and walk the client through the KDP dashboard. Work from one approved source instead of editing disconnected exports.
Use explicit approval points for structure, manuscript, visual assets, edition settings, and metadata. That keeps speed from turning into version confusion.
Mistakes and final checks
A key risk is this: sending unlabeled loose files makes it unclear which version is final or who owns the submission decision. Correct the source decision rather than patching only the final file.
For the final check, archive the exact delivered pack and require client approval before any later revisions. KDP Previewer and the current Amazon help pages remain the authority for the submission surface.
How BookWizard supports this workflow
BookWizard connects Agency Client Book Delivery Checklist to the rest of KDP production: Autobook supports structured drafting, the print editor handles trim-aware pages, Cover Studio builds the wrap, and Export Studio packages PDF, EPUB, manifest.json, and checklist.md. Publish Studio prepares listing fields, while the Chrome extension uses preview-before-apply so you remain in control. Studio is $20/mo with 1M AI tokens, and a typical ~50-page pack can take about 45 minutes. BookWizard does not auto-publish and does not promise royalties.
FAQ
Common questions
Last reviewed: 2026-07-29