Practical story guide models

Story guide examples that stay small enough to use

The best story guide is shaped by the continuity risks of the book. A domestic novel may need relationships and chronology; a mystery needs clue knowledge and promises; a fantasy series needs shared world rules. These examples show the structure, not invented story content.

01

A compact guide for a standalone novel

Use four sections: characters, locations, chronology, and open threads. Each character record holds want, need, role, important relationships, voice notes, and linked appearances. Each location stores only details likely to recur. The chronology records dated or ordered events that scenes could contradict.

The open-thread list is the revision engine. Phrase each thread as a reader expectation, then connect the scene that creates it, the scenes that change it, and the scene that resolves or intentionally transforms it. This compact model covers most continuity risk without becoming a second manuscript.

  • Standalone: characters, places, chronology, and open promises
  • Mystery: add clues, suspects, knowledge, alibis, and reveal order
  • Series: add shared canon, book-specific changes, and carryover threads
  • Nonlinear novel: compare story chronology with reader-facing scene order
02

A mystery guide built around information

Track the true event sequence, the clue sequence shown to the reader, and what every major character knows after each revelation. Separate evidence from interpretation: a fingerprint is a fact, while the detective's theory about it can be wrong.

Create a thread for each central question and a record for every clue that matters. Link planted evidence, red herrings, reinterpretations, and the final proof to scenes. This exposes reveals that depend on missing support and suspects who react to knowledge they should not have.

03

A series guide with shared and local layers

Keep stable world canon, recurring characters, institutions, naming rules, and long-range chronology at series level. Inside each book, store the manuscript's active cast, scene appearances, local timeline, structural beats, and promises. Promote a fact to the shared layer only when later books truly need it.

Novelbound connects these records to the draft. Instead of copying a template into an isolated document, you can navigate from the guide entry to the manuscript scene that makes the entry true and review what changed after revision.

A practical workflow

Put the method into the manuscript

1

Name the continuity risks

Choose the contradictions readers are most likely to notice in this particular book.

2

Select the smallest model

Start with characters, places, chronology, and threads; add a category only when the story needs it.

3

Define every field's job

Remove fields that never affect a decision, scene, reveal, or later book.

4

Connect the manuscript

Link records to the scenes that establish, complicate, or overturn them.

Questions, answered

Frequently asked questions

Is there one correct story guide format?

No. The useful format follows the book's continuity risks. Start with a compact core and add specialized records for mysteries, nonlinear chronology, invented rules, or series canon.

What should a mystery story guide include?

Include the true chronology, clues, red herrings, suspects, alibis, knowledge by character, reader-facing reveal order, and setup-development-payoff links for the central questions.

How is a series guide different?

A series guide holds facts reused across books and long-range changes. Each individual book should still keep its own scene evidence, viewpoint limits, structure, and active promises.

Can I adapt these examples in Novelbound?

Yes. Use character, location, timeline, thread, outline, note, and shared-world records to build the version your manuscript requires.

Your words stay yours

Keep the draft, the decisions, and the finish line together.

Bring the book you have, including the messy version.

Start writing with Novelbound