Narrative Design Document
Version-controlled story bibles and branching narratives
Narrative content is uniquely difficult to version control. A story bible evolves constantly as writers add lore, rewrite character arcs, and restructure quest lines. Traditional docs lose the history of these changes, making it impossible to understand why a plot point was cut or when a character's motivation shifted.
Gameframe's narrative design template treats story content with the same rigor as code. Every paragraph is diffable. Branch the story bible to explore an alternate plot direction without touching the canonical version. When writers collaborate on dialogue, change prompts document the creative reasoning behind every edit — not just what changed, but why.
What's Inside
This template includes 6 structured sections, each version-controlled and ready to customize.
Story Synopsis
Three-act structure (or equivalent), major plot beats, and thematic pillars. The north star for every narrative decision.
Character Arcs
Per-character emotional journeys, transformation points, and relationship dynamics across the story timeline.
Dialogue Systems
Conversation structure, tone guidelines, branching dialogue rules, and localization notes.
Quest Structure
Main quests, side quests, and emergent objectives. Includes prerequisites, branching paths, and reward structures.
World Lore
History, factions, geography, magic systems, and cultural details. The encyclopedic foundation that keeps the world consistent.
Branching Narrative Map
Visual flow of player choices and consequences. Documents which decisions lock or unlock story paths and how branches reconverge.
How Teams Use This
A narrative team writing a branching RPG story who needs to track which dialogue paths exist, where they diverge, and how they reconnect without losing alternate drafts.
A lead writer revising the main quest line after playtesting, using version diffs to show the team exactly what changed and preserve the original structure for reference.
A localization team referencing the canonical English narrative with full change history so translators know which strings are new or modified between builds.
Frequently Asked Questions
Each narrative branch in your story can be documented in the branching narrative map section. Gameframe versions the entire document, so you can diff any two versions to see how the narrative tree evolved. For experimental story directions, use Gameframe branches to explore changes without modifying the canonical document.
Yes. Writers work on branches or make changes with individual change prompts. Gameframe tracks who changed what, so the narrative lead can review and approve edits before they reach the canonical version.
Gameframe supports role-based permissions. Restrict story-sensitive documents to the narrative team while giving designers read access to quest structure and world lore sections they need for gameplay integration.
Cross-document references let you link character arcs to their character design docs and quest structures to gameplay data. When a referenced document changes, impact analysis alerts you to review the narrative implications.
Start with this template
Create your narrative design document with built-in version control, branching, and team collaboration.