Track a Running Example Across a Practical Manuscript

Keep an editable record of the starting facts and each approved change in a running example. Connect every chapter’s version to that record, then check that later steps use the results actually produced earlier. A recurring name or setting does not create continuity if the example’s numbers, assumptions, or decisions drift.

Define why the example continues across chapters

A running example can help readers see how several lessons combine into one process. Decide what it should demonstrate that separate examples would not. A guide to preparing a community workshop might follow the same organizer from choosing an audience through designing an agenda and reviewing feedback. The continuity should reveal how one decision affects the next.

Write a short description of the example’s purpose and limits. Identify which facts are fictional, which claims require evidence, and which details are merely background. Keep the scenario focused enough to maintain. Adding many characters or incidental events can create continuity work without helping readers understand the method. The example should support the book’s instruction rather than becoming a second project competing with it.

Record the starting state and allowed changes

Create an editable working record of the initial inputs: participants, objectives, constraints, resources, and any other details the lessons depend on. Include units and definitions where they matter. This is the example’s starting state, not a list of facts that must remain frozen forever. Some changes may be the very decisions the book is teaching readers to make.

For each planned stage, identify what can change and why. If the organizer narrows the workshop objective in one chapter, later chapters should use the revised objective. If the participant count changes because new information arrives, show that event explicitly. The record helps distinguish an intentional development from an accidental inconsistency introduced by drafting different chapters at different times.

Connect each chapter to an approved result

After drafting a stage, record the result it produces and the assumptions it used. The next stage should start from that accepted result. Do not let a generated continuation invent missing decisions simply to keep the narrative moving. If a required input has not been established, revise the earlier lesson or explain where the new information comes from.

Suppose the first chapter selects a ninety-minute session, but a later agenda example allocates two hours without explanation. The arithmetic may be correct within the later table while contradicting the project’s established constraint. Check the dependency, decide which duration serves the lesson, and update all affected locations deliberately. A single shared record makes that repair easier to trace than a search for isolated numbers alone.

Review local edits for downstream effects

When a chapter changes, identify which later stages depend on its result. A revised objective can affect the activity choice, materials, timing, and evaluation example. Review those dependencies before accepting the change as complete. Not every wording edit needs a full chain review, but changes to inputs or decisions should be assessed for their effect beyond the local paragraph.

Keep the explanatory text, tables, figures, and exercises aligned. A corrected table can still be accompanied by an old caption, and a new illustration can preserve a superseded participant count. Inspect the complete example unit at each stage. If different collaborators own different parts, provide the revised state and the reason for the change rather than sending only a vague request to “make it consistent.”

Test the example from beginning to end

Read the running example in sequence, extracting its inputs, decisions, and outputs at each stage. Confirm that every transition is understandable and that readers can reproduce the reasoning with the information supplied. Then read the surrounding chapters normally to check that the example remains useful where it appears. A perfectly consistent scenario can still distract from a lesson if too much explanation is devoted to maintaining its story.

Save the final working record with the manuscript and review the example again in the publication export, including figures and references. Preserve origin information for generated text or artwork and apply current KDP guidance during publication review. The record is a maintenance tool: it allows a later edition to change one part of the example while identifying the other passages that need deliberate attention.