Story guide templateA story guide that builds itself from what you already know: the cast, the relationships, the world's rules, the chronology and the things that must not change — compiled into one document as you type.
Free · No account needed · Nothing uploaded

Start a story guide

A story guide is not a document you write once and then maintain. It is the place every later decision is checked against, which is why this one is compiled from the project on every render rather than saved as a second copy that can fall out of step. There is no export to forget, and no version of the story guide that disagrees with the profiles.

A free story guide template for novels and series

A story guide template is only useful if it is the thing later decisions are checked against, so this one compiles itself from the project on every render rather than saving a second copy that can drift. Use it as a free story guide template for one novel, or as a book series guide template when the story guide has to outlive each book: a series guide template with the cast, the relationships, the world and locations, the rules with their limits, a story timeline template and a book glossary template, all in the same compiled document. It serves as a world guide template and a worldbuilding template too, because a fictional world is a set of rules before it is a map.

How to create a story guide, and how to keep a series consistent

People ask what is a story guide, and whether a story guide is the same as an outline. It is not: the story guide holds what is already true, and the outline holds what happens next. The same document answers how to create a story guide and how to create a series guide, and it is where how to keep a series consistent becomes a check rather than a memory: a story continuity pass over what you entered, a glossary that fixes invented spellings, and a timeline that cannot quietly contradict an age. It is a story continuity checker for the story guide, not for your manuscript, because it has not read the manuscript and says so wherever it reports.

The compiled document has eleven sections, in this order:

  • Project facts
  • Protected canon — do not change
  • Cast overview
  • Character profiles
  • Relationships
  • Plot, chapters & scenes
  • World & locations
  • Rules & systems
  • Timeline
  • Glossary
  • Open questions for the collaborator

Each section is numbered the way it is listed, even when a section is empty and left out — so "Cast overview" is section 3 in every story guide the tool produces, and a page number found in one draft still means something in the next.

The first thing in the document is the protected canon: the facts you have marked do-not-change. Each one stores its own wording, so it survives any later edit to the answer it came from, and it outlives the character it names. This is the block a collaborator is meant to read before they write a line.

  1. A continuity check that only reads what you enteredUnanswered fields at the depth you chose, duplicate and near-duplicate names, characters nobody is connected to, glossary spellings that disagree, an age the timeline contradicts, and rules missing a cost or a limit.
  2. Open questions, generated per fieldThe questions your own answers still leave open, asked as questions. Keeping one stores it on the profile, which is how it reaches the story guide's final section.
  3. A one-page brief for the next personThe project facts, the canon, one line per character, the rules that cannot be broken and what is still open — the same document as the story guide, with its own label, so the two can never disagree.

The tool will not tell you your manuscript is consistent, because it has not read it. It checks the story guide you entered — the answers you gave it — and says so plainly wherever it reports anything.

FAQ

Why does the story guide come before the invitation?
A collaborator can only contribute well when they know the characters, the relationships, the world's rules and the continuity you want protected. That context is the thing this tool makes, and it is the thing you can hand over without handing over the book.
Why is the story guide safe to share?
The story guide is the safe artifact. It says who these people are and what must not change, and it says nothing about how the story ends, so sharing it does not mean showing anyone your draft.
How do I invite the role I actually need?
A co-writer needs the cast and the rules. An editor needs the arc and the open questions. A beta reader needs the one-page brief. Because the story guide separates those, each of them can be given the right half.
Why review a response against the same ground?
When two people work from the same protected canon, a disagreement is about the story rather than about which version of the character they each remember.
What do I get on Nexet that this tool cannot do?
The tool builds the context; Nexet is where a story is written against it. A Nexet project holds your scenes and your story guide together: draft in the Manuscript Studio, keep the characters, world, plots and outline in the same project, and let the cast and the do-not-change canon stay visible while you write. It also keeps a revision of every scene, and it tracks the plot threads and the outline. The finished work exports as Word, PDF, EPUB, Markdown, Final Draft and more.
Can I invite a co-writer or an editor to work from my story guide?
Yes, and that is what the story guide is for. On Nexet you invite someone as a role, whether co-writer, editor or beta reader, and they work from the same approved context rather than from a copy that drifts. Each role is given the part of the context its job needs, and a private thread keeps the conversation with the work instead of in an email.
What is the Writers' Audition Arena?
It is where you find someone to write with. You publish a frozen seed: a passage from your own work, held at that exact version. Other writers answer it with continuations, and you read them and choose. Your manuscript is never handed over by publishing a seed: what they see is the seed, and the writer you pick works on from there.
How do I get this story guide into a Nexet project?
Export the JSON file, which is the round-trip format and the one that imports back without loss, then start the project on Nexet and bring it with you. Importing the file directly is coming; until it ships, the JSON export and the one-page brief are what travel, and the brief is what a collaborator reads first.
Does Nexet cost anything?
Nexet needs an account, and it starts free: you can create projects and write in them without paying, with more project slots available if you want them. Nothing on this page is affected either way: the free tool, its exports and its brief stay free, and they never ask for an account.
How do I start writing a book with no experience?
Start before page one. Decide who the story happens to, what they want, and the two or three rules the world cannot break, then write the opening scene against those decisions rather than guessing at them. Experience shows up in the drafting; it is not a prerequisite for deciding what the book is.
What should I decide before I start writing a novel?
Four things: the premise in a line, the cast and how deep each profile needs to go, the world's rules with their costs and limits, and the questions your answers still leave open. Outlining comes after these, because an outline made before the cast is decided tends to be rewritten the moment a character becomes specific.
What should be included in a series guide?
A series guide holds what every book in the series must agree with: the cast and their relationships, the world and its rules, a timeline that covers the gaps between books, a glossary for invented words and their spellings, and the protected canon a later book must not quietly change. The free story guide template compiles all of it into one document and adds a continuity check over what you entered.
How do I keep a character's details consistent across a series?
Put the details somewhere a later book can be checked against, and mark the ones that must not change as protected canon. This tool keeps each character's profile at one depth across the series, fixes spellings in the glossary, and reports the contradictions it can see in the answers you gave it, so remembering is the document's job rather than yours.
Is a story guide the same as an outline?
No. The story guide holds what is already true about the story: who these people are, how they relate, what the world allows. An outline holds what happens next, in order. They are read together, but one is the ground and the other is the route, and mixing them is how a rule gets bent to fit a scene.
Do I need a story guide for one book, or only for a series?
One book needs it too, and needs it earlier than most writers expect: the moment a detail is worth not contradicting, it is worth writing down. A series makes the story guide mandatory, because a reader will remember across years what the writer forgot across months. The tool builds the same document either way.
What does a co-writer need to know before they start?
The cast, the relationships, the world's rules, the protected canon and what is still open. That is the one-page brief this tool produces: enough context to write correctly, and nothing about how the story ends, so sharing it is not sharing the manuscript.
How do I co-write a book without the story drifting?
Agree the ground before the prose, and keep one document of it. The co-written books that drift are the ones where each writer remembers the facts differently, so the fix is a shared story guide: the cast, the world's rules and the protected canon both writers check against, plus a one-page brief at every handoff so the context travels without the manuscript.
Should I outline a novel before or after deciding the characters?
After the cast. An outline is a set of promises about what characters will do, and characters you have not decided yet cannot keep promises, which is why an outline written before the cast tends to be rewritten the moment a character becomes specific. Decide who they are, then outline what that person would do next.

“You shouldn’t have to send your entire book to get useful feedback.”

  • The draft and the story guide in one project. Draft a scene in the Manuscript Studio with the cast, the world and the canon beside it, so the reference sits where the writing happens instead of in another file.
  • Invite the role you actually need. Bring in a co-writer, an editor or a beta reader as a role. Each works from the same approved context, with a private thread for the conversation.
  • Never lose a version of a scene. Revisions keep a copy whenever a scene changes, so an edit is not a one-way door and a collaborator's answer can be read against what it answered.
  • Find a collaborator in the Arena. Publish a frozen seed of your own writing, read the continuations other writers send back, then work with the one that fits. Your manuscript stays private.
  • Take everything with you. Export the project or the finished document as Word, PDF, EPUB, Markdown, Final Draft, Rich Text, OpenDocument, plain text, HTML or JSON. Nothing is locked in.
Start your FREE trial NOW