# Workbook Ebook Template — A Complete, Editable Sample
A free original nonfiction workbook example from Scribora · November 20, 2026

**Who this is for:** independent consultants preparing to hand over a small client project.
**What you will make:** a one-page handover manifest with an owner, a decision record, and a verification step.
**What it is not:** a client-specific legal template, a fillable PDF, a promised productivity result, or evidence of customer adoption.

This text is licensed for you to adapt to your own work. All names and situations below are fictional. Do not paste identifying client information into a public book or a third-party writing tool without an appropriate basis and permission.

## How to use this workbook
Set aside about 20 minutes. Complete the three exercises in order. Use the example answers only as illustrations. If an answer depends on a client agreement, follow that agreement rather than this sample. The final checklist tells you when the handover is ready to share.

### Exercise 1 — Define the receiving reader
**Goal:** identify the one decision the recipient must make without another meeting.

1. Who will receive the handover? (Role, not a person's private name): ______________
2. What is the recipient expected to do first? ______________
3. What information would make that action safe and unambiguous? ______________
4. Which information is missing or subject to approval? ______________

**Fictional example**
- Receiver: an internal operations coordinator.
- First action: publish an approved event page.
- Required: approved text, legal sign-off status, asset links, go-live date and rollback contact.
- Missing: final approval of image rights.
- Decision: hold publication until approval is recorded.

**Self-check:** Could someone who missed every project call tell whether to act, wait, or ask for a decision? If not, replace vague instructions with an observable condition.

### Exercise 2 — Make a handover manifest
**Goal:** produce a compact set of fields that can be checked independently.

Copy one row per deliverable:

| Item / version | Where found | Owner role | Approved? / by whom | Recipient action | Due or expiry | Blocker |
| --- | --- | --- | --- | --- | --- | --- |
| Event page copy v3 (fictional) | Approved-documents folder | Editor | Yes / project lead | Paste into draft page | Before launch | None |
| Hero image v2 (fictional) | Assets folder | Designer | Pending rights approval | Do not publish yet | Before launch | Licensing check |
| [Your item] | | | | | | |

If you do not have evidence of approval, write **Pending**. Do not substitute silence for consent. Link only to locations the intended recipient may access.

**Self-check:** For each item, can the recipient locate the correct version and determine the next action without interpreting an ambiguous status label?

### Exercise 3 — Design the escalation and acceptance test
**Goal:** decide what to do when an essential field is missing.

1. A required approval is absent. Default action: **hold the affected task**, record the missing approval, notify the responsible role.
2. The file path returns an access error. Default action: **do not improvise a replacement**; request access or a corrected location.
3. An owner is unavailable. Default action: follow the agreed fallback or escalate to the named decision-maker; do not invent a delegate.
4. The recipient says the handover is complete. Ask for the **acceptance evidence**: a dated acknowledgement or a verified completion in the project system.

**Fictional mini-scenario:** The coordinator can see the approved page copy, but the hero image's rights are pending. A weak handover says: "Everything is ready. Go live tomorrow." The revised instruction says: "Prepare the page as a draft; hold publication until the asset owner records rights approval. The project lead confirms release in the handover log." This is an example of process design, not professional legal advice.

**Your release condition:** _______________________________________________
**Fallback owner role:** _________________________________________________
**Location of acceptance record:** ________________________________________

### Exercise 4 — Final decision
Choose one result:
- **Ready:** every required item has an accessible location, owner, status and executable next action.
- **Ready with an explicit exclusion:** the recipient knows which optional work is not included, and the exclusion is agreed.
- **Blocked:** a required right, approval, file or decision is missing. Record exactly who resolves it.

Why you chose this result: ________________________________________________

### One-page completion checklist
- [ ] The receiver and intended outcome are named by role.
- [ ] The first action is specific enough to execute.
- [ ] Required versions and links are accessible to the receiver.
- [ ] Every required approval is recorded or explicitly pending.
- [ ] No private source material is included without a justified need.
- [ ] Open questions have a named owner and escalation route.
- [ ] The acceptance condition can be checked without another call.
- [ ] At least one person unfamiliar with the project has reviewed the handover.

## Make this a full workbook
This mini-workbook is self-contained. For a longer ebook, repeat the same teaching unit in each chapter: *why the decision matters → concise explanation → a worked case → a reader exercise → a self-check → a reusable result*. Give each chapter a new reader decision; do not multiply near-identical worksheets to increase page count.

### Author's source-and-rights note
Replace all invented examples with material you own or have permission to reuse. Independently verify factual, contractual, financial, medical or legal claims before publication. Where the reader needs a specialized professional decision, refer them to an appropriate expert.

### Format and usability QA
A reflowable EPUB is good for narrative and short prompts, but exact blank lines and wide grids can behave differently across reading systems. Test the output on narrow screens with larger font sizes. For write-in pages or forms, consider a separately tested print-friendly PDF and make clear that the EPUB itself is not a fillable form. Do not promise interactive fields unless you have implemented and tested them.

Source references for the general publication workflow:
- W3C EPUB 3.3: https://www.w3.org/TR/epub-33/
- Amazon KDP — Create a Table of Contents: https://kdp.amazon.com/en_US/help/topic/G201605700
- Amazon KDP — Kindle Create limitations: https://kdp.amazon.com/en_US/help/topic/G93BCLJGZFGK39BT/
- Google Search Central — Helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content

Download is ungated. If you want to build a longer, source-grounded nonfiction book from your own authorized notes, review the free Scribora outline and sample chapters at https://www.scribora.ai/sign-up?start=ebook.

**Attribution:** This file contains no real conversion metrics, endorsements, customers or outcomes.
