Story Branching: Try a What-If Without Touching Your Manuscript

Every novelist hits the question. What if she refuses the oath? What if the traitor is revealed in Book 2 instead of Book 3? What if the chapter runs from his point of view? You cannot answer it in your head. You have to write the other version and read it.

A story branch is that other version, kept alongside the original rather than on top of it. It starts from a named scene, carries the scenes you rewrite, and leaves the rest of the book alone. When you have read both, you keep one. The term comes from version control in software, where a branch lets a team try a change without disturbing the working copy. For a writer the idea is simpler: the draft you trust stays safe while you try the draft you are curious about.

Most writers branch by hand. The usual methods, and where each one breaks:

• Save As. Book2-final-v3-ALT.docx works for one what-if. By the third, nobody can say which file is the book, and every fix to the original has to be copied into the copy.
• A pasted scene at the bottom of the file. Easy to write, easy to forget, and easy to ship by accident in the upload.
• A separate drafts folder. Keeps things tidy until you want the alternative back in. Then you merge by hand, scene by scene, and hope you caught every one.

The common failure is the same in all three. The alternative and the original drift apart with no record of what changed, so choosing between them means rereading both in full.

In a standalone novel, a branch changes one book. In a series, a branch in Book 2 can reach every book after it. A character who now lives has to be somewhere in Book 3. A secret revealed early changes what the reader knows in every later scene that depends on it. That is why the choice should be made on the page, with both versions in front of you, and why the version you keep has to end up in one place: the main text your series canon is built from.

Story Branches lives in the Story Bible. Each alternative follows the same five steps.

1. Create an alternative. Give it a name, write the question you are exploring (“What if Maren refuses the oath?”), and choose the scene it starts from. Creating it copies nothing into your book and starts nothing. It is an empty place to write.
2. Write it yourself. “Write this alternative” opens the same scene editor you use for the book. Every word in an alternative is yours.
3. See every version on one map. The map shows your main working draft and each alternative as its own lane, with the number of scenes each one has changed. An alternative with no changes says zero.
4. Compare, one scene at a time. Each changed scene sits beside its saved baseline. Under it, “What this changes” lists two plain facts, counted from the text: whether the scene was added, removed or rewritten, and how many words it gained or lost.
5. Adopt it, or let it go. “Review adoption” lists every scene the alternative would replace in your main text. You confirm the full count before anything changes. If you change your mind, “Put it back” restores exactly those scenes.

Two details matter here. The baseline is frozen when you create the alternative, so later edits to the main draft cannot quietly change what you are comparing against. And putting an adoption back undoes only that adoption. Edits you made elsewhere in the book since then, your notes and your other alternatives stay as they are.

A fantasy author is revising Book 2 of a trilogy. In the current draft, Maren swears the oath at Greywater in Chapter 14, and Book 3 is planned around it. A beta reader says the oath feels too easy.

The author reviews the adoption, confirms that three scenes will be replaced, and puts the alternative into the main text. Two weeks later, while drafting Book 3, the old version turns out to set up a payoff the author wants to keep. “Put it back” restores the three original scenes. The unrelated line edits made to Chapter 9 in the meantime stay where they are.

• It does not write the alternative. StoryHelm never writes your prose. Prose generation for branches is switched off in the product, not hidden behind a setting.
• It does not interpret the difference. The comparison reports what changed and by how many words. Which version is better is your call.
• It does not run an analysis on an alternative. Creating, reading or comparing an alternative starts no analysis and spends no credits. An alternative is a place to try something, not a finding.
• It does not restructure the book in one step. Adoption replaces existing scenes. If an alternative adds or removes scenes, the review says so and does not adopt it in one move.