Building a Story Bible That Actually Gets Used Most story bibles are graveyards. You build them with good intentions. You name the continents. You map the magic system. You write three paragraphs about the royal succession. And then you open your draft and just... write from memory anyway, because pulling up the bible feels like a context switch that breaks the flow. Six chapters later you've given your protagonist two different eye colors and forgotten the name of the inn from chapter two. A story bible that doesn't get used isn't a bible. It's procrastination formatted nicely. Here's how to build one that actually works during the draft, not just before it. The Two Failure Modes Before the workflow, it helps to name what goes wrong. The Over-Built Bible. You spend three weeks building world lore before a single scene is drafted. The bible has texture and depth and almost zero relevance to the story you're about to tell, because you don't actually know what the story needs yet. By chapter four you're ignoring most of it. The Never-Updated Bible. You build a decent one up front, start drafting, and then never add to it as the story grows. Characters develop details in the draft that never get captured. Plot decisions accumulate. By book two you can't remember what color your protagonist's apartment was. The solution to both is the same: build the bible in layers, during the work, not before it. The Layered Build Layer 1: The Foundation (before drafting) Keep this short. Under three pages if you can manage it. You only need what you can't discover in the draft: The premise in one sentence. The world rules that constrain your plot (magic system limits, technology level, geography if it affects plot). Your main characters, one paragraph each: name, role, want, wound, voice note. The timeline anchor: what happened before chapter one that made chapter one necessary. That's it. Resist the urge to go further. The rest gets built as you need it. Layer 2: The Running Log (during drafting)