A character bible earns its keep at chapter 80, a long way from the day you invented the character. By then the boxes you actually open have nothing to do with height or eye colour. They are “what does this person know right now” and “who did they say it to, and in which chapter.” Below are six fields that survive a long serial, and the ones you can leave blank on day one.
Most bibles start with the face
The first boxes anyone fills on a new character sheet: height, hair, eyes, favourite food. They fill fast. And when the sheet is full, it feels like you got something done.
Eighty chapters later you will have opened those boxes twice, maybe. Eye colour is the kind of thing your hands remember on their own.
What actually stops your hands mid-paragraph is a different sort of question:
- Did this character already know who the protagonist really was?
- Which chapter did she tell someone, and who was it?
- When did these two meet for the first time?
No appearance field answers any of that. And all three, if you get them wrong, get caught by readers before you catch them yourself. The Royal Road comment section always contains someone who remembers chapter 12 better than the author does.
Six fields that survive
1. What everyone calls them
Write down every form of address in circulation. What the protagonist calls them. What the antagonist calls them. What they call themselves.
The chapter where a name changes is the chapter where a relationship changed. Which is why this field ends up looking more like a timeline of relationships than a profile.
2. Knows / doesn’t know yet
The most important field, and the one missing from nearly every template you can download.
Information reaches each character on its own schedule. Your reader can know something in chapter 20 that the character won’t learn until 37, and that distance is the tension. Manage the distance in your head and it will drift.
Put a chapter number beside every line. “Knows from ch. 37” is worth a hundred of “knows.”
3. Already said out loud
To whom, in which chapter. If your story runs on secrets, this one field is half the bible.
4. The stated want and the real one
The stated want is what the character says at the dinner table. The real one is something they haven’t admitted to themselves yet. Characters come alive in the gap between the two.
You won’t open this field often. But when someone starts reading flat, this is usually where the problem is sitting.
5. What changed, and from when
People change. The trouble is that three chapters after the change you are still writing them in the old register.
Two columns do the job: what changed, and from which chapter.
6. Things you must not write any more
Backstory you retired. A verbal tic you used in the first ten chapters and dropped. A habit that ended up belonging to a different character.
Write “do not use” instead of deleting the line. Delete it and the reason it was retired goes with it, and six months later you reinvent it.
What you can leave blank
- Physical specs to the centimetre. You decided she is 168 cm. That number is never going to appear in the prose.
- MBTI, star sign, enneagram. They look like a summary of a person. They tell you nothing about what this character does in the next scene.
- A complete childhood timeline. Keep the two or three events that will actually reach the page. The rest grows on its own while you draft.
None of that is harmful in itself. It’s just that the hours spent there come back to you later in the shape of an empty field 2.
Serials break differently
Write a standalone novel and you can reread the whole manuscript and fix it before anyone sees it. A serial doesn’t offer that. What’s posted is posted. On KDP you can upload a corrected file, sure; the reader who left a one-star review over the timeline in chapter 40 is not going to re-download it. On a Substack the email has already gone out.
So a serial’s character bible sits closer to a record of settled fact than to a design document. What you haven’t written yet doesn’t need an entry. What you have published has to have one.
One rule covers it. If the reader hasn’t read it, it doesn’t go in the bible.
A template you can copy
Name:
Forms of address
- protagonist calls them:
- antagonist calls them:
- calls themselves:
Knows (from which chapter):
Doesn't know yet:
Said out loud (to whom / which chapter):
Stated want:
Real want:
Changed (what / from which chapter):
Do not write any more:
Eleven lines per character. Longer than that and you stop opening it on the day the next chapter is due.
Worldview material sorts the same way: record what has settled on the page, let the rest wait. The companion list is in Seven Fields: The Worldbuilding Sheet That’s Still Alive at Chapter 30.
Every 30 chapters, spend ten minutes
Don’t try to keep everything correct all the time. Around every thirtieth chapter, take your five main characters and check two things:
- Is anything still sitting under “doesn’t know yet” that the character has in fact already learned?
- Has anything been said out loud in the text that never made it into field 3?
When those two drift, the reader doesn’t read it as a character behaving strangely. They read it as an author who lost track. That’s the sentence where immersion stops.
If the manuscript and the character sheet live inside the same work, you can put both in front of the AI at once. In Slima the bible sits in Notes alongside the chapters, so asking AI Coach “what does this character know as of chapter 37” gets you an answer checked against the actual text. What isn’t written in the bible, the model doesn’t know either. It remembers for you. It doesn’t decide for you.
Where this stops working
The template gets heavy as the cast grows. In an ensemble piece with thirty named characters, keep five at this density and give the rest two fields: forms of address, and what they know.
And a bible does not prevent contradictions. It shortens the distance between making one and finding it. Nobody reaches chapter 80 clean. The whole difference is whether you catch it before you post the next chapter, or a reader catches it in the comments.