An ebook is created twice: first as a useful argument, then as a reliable file.
The editorial build turns a promise and source material into a coherent manuscript. The production build turns that manuscript into a navigable, readable deliverable. Skipping the first produces polished filler. Skipping the second produces good ideas trapped in a frustrating file.
Define “done” before you outline
Write down the intended reader, the result, the approximate scope, the publication channel, and the primary format. These five constraints prevent the project from quietly changing shape halfway through.
Start differently depending on what already exists.
| You have | First action | Do not do yet |
|---|---|---|
| A topic only | Interview potential readers and collect the decisions or tasks they struggle with. | Generate a long chapter list from the topic alone. |
| Notes, talks, or course material | Sort the material by reader problem, evidence, example, and repeated idea. | Paste everything into a draft and preserve its original order. |
| A rough manuscript | Write a one-line job for every existing chapter and identify missing transitions. | Begin sentence polishing before testing the structure. |
| A finished document | Audit rights, navigation, accessibility, links, and destination-specific format behavior. | Assume a successful export is a validated ebook. |
Eight stages from premise to tested ebook.
- Stage 01
Write the reader promise
Name one reader, the situation they are in now, and the change the book should help them make. A useful promise is observable: the reader can make a decision, complete a task, avoid a mistake, or understand a system after reading.
Exit condition: A one-sentence outcome that can reject irrelevant chapters.
- Stage 02
Inventory the source material
Separate what you know from what you need to verify. Gather interviews, notes, original examples, data, citations, permissions, and open questions. Mark anecdotes as anecdotes and claims as claims; they need different editorial treatment.
Exit condition: A source map with evidence, examples, and unresolved questions.
- Stage 03
Choose the destination and working format
Decide whether readers will receive a retail ebook, a direct-download document, or another deliverable. This affects navigation, page-dependent design, image treatment, and the final export. Keep an editable master even when the final book will be EPUB or PDF.
Exit condition: A declared primary output and an editable source file.
- Stage 04
Build an argument, not a pile of chapter names
Give every chapter a job. Write the question it answers, the new understanding it creates, the evidence or example it needs, and the handoff to the next chapter. If two chapters do the same job, combine them before drafting.
Exit condition: A chapter map that shows progression and dependencies.
- Stage 05
Draft in bounded sections
Draft one section against its brief, then compare the result with the source map. Add the author-specific examples while the context is fresh. Leave visible notes where a fact, permission, quote, or demonstration still needs work.
Exit condition: A complete draft with uncertainty exposed, not hidden.
- Stage 06
Revise in separate passes
First test the book-level logic. Then check evidence, usefulness, repetition, voice, transitions, and sentence clarity in distinct passes. Mixing all of these at once encourages cosmetic edits while structural problems survive.
Exit condition: A manuscript whose claims and sequence have been deliberately reviewed.
- Stage 07
Add only visuals that perform a job
Use a diagram when relationships are hard to explain linearly, a screenshot when interface state matters, and a table when exact comparisons matter. Supply captions or text alternatives according to purpose, and keep licensing records for every asset.
Exit condition: A visual plan tied to comprehension, not empty decoration.
- Stage 08
Export, inspect, and correct the artifact
Open the final file outside the writing environment. Use the table of contents, follow links, change text size where the format allows it, inspect page breaks, and test on more than one screen. Fix the source, export again, and repeat until the deliverable—not merely the editor view—works.
Exit condition: A tested release candidate and a reusable master manuscript.
Give each chapter a contract before drafting it.
A chapter title is a label; a chapter brief is a quality-control instrument. Fill in these fields before writing and review them again after the draft:
- Reader question: the question this chapter must answer now.
- Change: what the reader should understand, decide, or be able to do afterward.
- Evidence: the source, demonstration, or reasoning that supports the central claim.
- Concrete example: a scenario that makes the guidance testable rather than abstract.
- Boundary: what the chapter deliberately does not cover.
- Bridge: why the next chapter follows from this one.
This contract also makes AI-assisted drafting safer: the system receives a bounded assignment, while the author retains control over the facts, examples, exclusions, and conclusion. For a deeper workflow, read how to write a book with AI.
Do not export until the manuscript passes these checks.
- The title, subtitle, introduction, chapter sequence, and conclusion all promise the same book.
- Every factual claim that matters has been verified against an appropriate source.
- Quotes, images, and third-party material have documented permission or a valid basis for use.
- Headings are structural—not manually enlarged paragraphs—and the hierarchy does not skip without a reason.
- The table of contents matches the final structure and its links work.
- Examples are specific enough for the reader to recognize a good and bad application.
- Images have an editorial purpose, an appropriate text alternative, and a readable caption where needed.
- Front matter, author information, references, and calls to action point to current destinations.
- A final proofread happened after layout or conversion, because conversion can introduce new defects.
A clean manuscript can still produce a broken ebook.
For a reflowable ebook, enlarge the type, change the viewport, navigate with the table of contents, and look for headings separated from their text, tiny images, or information that depends on a fixed page. For a PDF, inspect small-screen legibility, page boundaries, margins, bookmarks, and link behavior. For an editable handoff, confirm that styles and hierarchy survive when another person opens the source file.
The correct output depends on distribution. Use the EPUB, PDF, and DOCX guide before committing to one file, and use the ebook image guide before adding visual-heavy pages.
Check current rules at the destination.
Retailers and distribution services can change accepted inputs and content requirements. If Amazon KDP is one of your destinations, verify the current supported ebook manuscript formats before upload and review the KDP Content Guidelines. Those official pages—not a static checklist—are the source of truth for current platform rules.
- W3C EPUB 3.3 — the normative specification for the EPUB format.
- Amazon KDP: supported ebook manuscript file formats — current input-format documentation.
- Amazon KDP Content Guidelines — current platform content guidance.
- W3C WAI image tutorials — purpose-based guidance for accessible images.
Turn the reader promise into a chapter path.
Write the promise at the top of a new document, list the five to eight questions a reader must answer to reach it, and arrange those questions in dependency order. That is the beginning of a working outline. You can develop it with the book outline generator or see how the AI ebook generator organizes the broader workflow.