# Free KDP Book Description Template Pack

**Use:** Copy the source of an example into the **Description → Source** field on Amazon KDP only after replacing it with truthful facts about your own book. The books, authors and contents below are **FICTIONAL EDUCATIONAL EXAMPLES**, not Scribora customer books or testimonials. This is not a KDP publishing or conversion guarantee.

**Verified references, 2026-11-18:**
- [Amazon KDP — Write a Book Description](https://kdp.amazon.com/en_US/help/topic/G201189630)
- [Amazon KDP — Fixing description formatting](https://kdp.amazon.com/en_US/help/topic/GC4VASCGNQP6LQ7L)
- [Amazon KDP — Metadata Guidelines](https://kdp.amazon.com/en_US/help/topic/G201097560)

Amazon limits the book description to **4,000 characters including HTML tags** and suggests concise copy around 150 words. Supported tags: br, p, b, em, i, u, h4–h6, ol, ul, li. Do not paste reviews, testimonials, contact information, URLs, prices, availability, time-sensitive offers, Unicode emojis, keyword lists or off-platform ordering instructions. Rules may change: check the linked KDP guidance before publishing. The snippets below are plain, supported HTML, not complete KDP listings.

## Reusable five-part framework

1. **Reader situation:** Name a recognizable obstacle or decision.
2. **Specific promise:** What can a reader learn or make with this *actual* manuscript?
3. **Proven contents:** Identify two or three deliverables present in the book.
4. **Fit:** Who is this for? Who should choose something else?
5. **Expectation:** What is the reading experience, and what does it *not* replace?

Draft around 150 words; count the actual HTML source in KDP, not just the rendered words. Do not insert empty marketing claims merely to hit a length target.

## Example 1 — Process guide: Better Client Handovers

**FICTIONAL EXAMPLE.** Assumed interior: four chapters, a handover inventory, a six-step review sequence and two annotated delivery notes. No actual book or sales outcome is claimed.

~~~html
<p><b>What should a client receive when the project ends?</b></p>
<p>A finished deliverable can still leave a client wondering where the files live, what decisions were made, and who owns the next step. <i>Better Client Handovers</i> shows independent consultants how to organize a clear final package before the last call.</p>
<p>Work through a handover inventory, a six-step review sequence, and two annotated delivery notes. The examples show how to record decisions, identify unresolved items, and make a project easier to pick up later.</p>
<p>Written for solo consultants and small service teams handling client projects. This is a practical documentation guide, not a contract template or a substitute for professional legal advice.</p>
~~~

**Evidence to verify in a real manuscript:** the inventory exists; there are six review steps; there are two actual annotated notes; the guide targets consultants; the legal boundary is appropriate.

## Example 2 — Planning workbook: Your First Community Workshop

**FICTIONAL EXAMPLE.** Assumed interior: a sample two-hour agenda, role assignment sheet, venue checklist and three editable planning exercises. Not an actual event or tested operational plan.

~~~html
<p><b>How do you turn an idea for a community workshop into a plan people can follow?</b></p>
<p><i>Your First Community Workshop</i> walks first-time volunteer organizers through the questions to settle before an event: purpose, participant roles, room setup, and a realistic running order.</p>
<p>Inside are a sample two-hour agenda, a role assignment sheet, a venue preparation checklist, and three short planning exercises. Each example shows what to write down and what still needs a local decision.</p>
<p>Designed for small, informal educational workshops, not large public events or specialized activities. The book helps organize the planning conversation; it does not replace venue policies, accessibility review, safeguarding or safety requirements.</p>
~~~

**Evidence to verify:** agenda, checklist, sheet, exercises and scope are in the final book; no false claim that an EPUB is interactive; event safety is not guaranteed.

## Example 3 — Evidence-led explainer: Reading Research Before You Buy

**FICTIONAL EXAMPLE.** Assumed interior: a guide to recognizing study design, sample selection and claims; two worked hypothetical examples; a one-page question checklist. No research or purchasing results claimed.

~~~html
<p><b>A confident headline is not the same as convincing evidence.</b></p>
<p><i>Reading Research Before You Buy</i> is a short introduction to evaluating the evidence behind product and service claims. It shows how to ask what was actually measured, who was included, and whether the conclusion goes further than the data.</p>
<p>Using two clearly hypothetical examples and a one-page reading checklist, the guide separates observations from interpretation, explores common limitations, and gives readers questions to take into their own research.</p>
<p>For curious nonspecialists who want a more careful way to read promotional claims. This is a method for asking better questions, not a catalogue of endorsed products or individualized professional advice.</p>
~~~

**Evidence to verify:** two hypothetical examples and checklist exist; no implied product endorsements; cited claims are supported; audience matches reading level.

## Description fact-check card (duplicate for your book)

| Claim made in description | Source page or chapter | Verified in final file? | Revision needed? |
| --- | --- | --- | --- |
| Specific outcome or method | | | |
| Named worksheet or example | | | |
| Number of chapters, steps or exercises | | | |
| Audience and stated limits | | | |
| Other measurable claim | | | |

**Rule:** Blank means unverified, not approved. If a claimed exercise disappears during editing, remove it from the description before publication.

## KDP release check

- [ ] Title, subtitle, author, edition and actual cover are consistent with the listing.
- [ ] Every listed deliverable exists in the exported book or explicitly delivered supplementary asset.
- [ ] No testimonials, reviews, review requests, URLs, contacts, prices, urgency claims or keyword lists.
- [ ] All HTML tags are in KDP's supported set and properly closed.
- [ ] The full Source field is under 4,000 characters including tags.
- [ ] No hidden markup from copying styled text; preview the published-looking result in KDP.
- [ ] Recheck policies on publication day; do not assume approval is automatic.

## Version and observation log

| Version | Date | Actual Amazon listing URL | What changed | Verified store observations, if available | Confounders or unknowns | Decision |
| --- | --- | --- | --- | --- | --- | --- |
| Draft 1 | | | | unknown | | |
| Draft 2 | | | | unknown | | |

**Measurement discipline:** A rewrite is not evidence of more sales. Unless you can establish comparable traffic and outcomes, record *unknown*, not an estimated lift. Avoid changing description, price and cover at the same time if you intend to compare them.

**Next step:** If your manuscript is still unfinished, use [Scribora](https://www.scribora.ai/sign-up?start=ebook) to organize rights-cleared source notes into an outline and draft chapters. Scribora is not Amazon KDP and does not publish listings for you.
