How to Track a Cast of 40: A Spreadsheet Schema for Names, Voices and Relationships
Short answer. A cast of 40 needs a structured character spreadsheet with one stable record per character, consistent identifiers, searchable voice notes and a separate relationship table. Keep identity, story status and continuity facts in distinct fields so that changes can be tracked without overwriting earlier information.
- Give every character a permanent ID that survives name changes and aliases.
- Separate character facts from relationships and episode appearances.
- Record voice through observable dialogue habits, not vague personality labels.
- Use dated updates to preserve continuity across a long-running series.
Start with one permanent record per character
A useful story bible template begins with a character catalog that functions as the central index for the series. Create one row for every character, including unnamed figures who later become important. Assign a permanent identifier such as C001 or C040. The identifier should never change, even if a character adopts a new name, uses an alias or is revealed to have a different identity. This prevents duplicate records and makes references between documents reliable.
For a cast of 40, a spreadsheet is often sufficient. Give the main character sheet fields for ID, primary name, aliases, first appearance, current status, affiliation, age or age range, home location and a short identifying description. Keep optional information blank until it becomes relevant. A record should help a writer locate facts quickly, not become an invitation to invent biography that the story never uses.
- Character ID
- Primary name and aliases
- First appearance and current status
- Affiliation and important locations
- One-sentence identifying description
Separate fixed facts from changing story information
A character bible template becomes difficult to maintain when permanent identity and temporary circumstances occupy the same field. Divide information into stable facts and changing facts. A character's birth name may remain constant, while their occupation, residence, alliances and relationship status can change between episodes. Keeping these categories separate makes updates easier and prevents an old description from quietly becoming the current version.
For example, C012 might be introduced as Mara Vale, a courier living in North District. Episode 18 reveals that she has moved to the harbor and joined a political organization. The original identity fields remain intact, while current residence and affiliation receive updated values. Add an effective episode number and a short change note. If the move is later reversed, the record should show when each version was true.
- Stable identity facts
- Current circumstances
- Effective episode number
- Previous value or historical note
Build a separate relationship table
Relationships deserve their own sheet because a cast of 40 can produce hundreds of possible connections. Trying to store every relationship in a character's main row leads to crowded cells, duplicated information and contradictory descriptions. Instead, create one row per relationship. Include the IDs of both characters, the relationship type, its current status, the episode where it begins and the episode of its most recent change.
For example, C003 and C017 may begin as colleagues in Episode 2, become rivals in Episode 11 and cooperate again in Episode 23. Their relationship record can describe the current state while preserving the sequence of changes. Add a short note about what each character believes the relationship to be. This distinction is especially useful when two characters interpret the same interaction differently.
- Character A ID and Character B ID
- Relationship category
- Current status
- Start and change episodes
- Relevant disagreement or unresolved tension
Make voice notes searchable and specific
A voice field should describe how a character speaks, not simply how the writer feels about them. Words such as sarcastic, confident or mysterious provide little practical guidance during revision. Record observable habits: sentence length, preferred vocabulary, formality, interruptions, humor, contractions and subjects the character avoids. A compact voice description should be specific enough to distinguish one speaker from another.
For example, C008 might use short declarative sentences, rarely use contractions and answer personal questions with practical observations. C009 might speak in longer sentences, interrupt frequently and use affectionate nicknames even during arguments. These descriptions offer a useful reference when drafting dialogue. Add an example of an established line from the manuscript and its episode location so the writer can revisit the original context.
Connect the catalog to a series continuity tracker
The character catalog answers who someone is. A series continuity tracker answers when something happened and which facts it affects. Create an appearance sheet with one row per character per episode. Include episode number, scene number, location, physical condition, knowledge gained, promises made and important objects carried or transferred. This makes it easier to identify a character who appears to know information they have not yet received.
Add a separate unresolved-threads field for questions, secrets and commitments that remain active. A character who promises to deliver a letter in Episode 14 creates a continuity obligation. The tracker should record whether the letter was delivered, lost, intercepted or intentionally forgotten. A simple status system such as open, resolved and abandoned helps distinguish unfinished story business from details that have already been addressed.
- Episode and scene reference
- Character knowledge at that point
- Location and physical condition
- Important objects and commitments
- Open continuity threads
Use AI for retrieval, not authority
AI assistance can help locate references, summarize character records and identify possible contradictions when the underlying documents are organized. A writer might ask a tool to list every appearance of C012 or compare a new scene against a documented character description. These tasks are most useful when the source material is clearly identified and the answer can be checked against the original record.
A generated summary is not a replacement for the continuity tracker. Tools may merge characters with similar names, mistake an outdated fact for a current one or interpret an intentional mystery as an inconsistency. Keep the spreadsheet as the authoritative record. When a suggestion affects a character's history, relationship or knowledge, locate the relevant episode before changing the record.
Questions readers ask
Should minor characters receive permanent IDs?
Assign an ID when a character becomes individually relevant to the story. A recurring shopkeeper or unnamed witness can remain a temporary entry until they acquire a name, relationship or meaningful plot function.
How many columns should the main character sheet have?
Start with approximately 10 to 15 useful fields. Additional detail belongs in separate sheets or linked notes. A crowded master sheet becomes harder to search and maintain.
What happens when two characters share a name?
Keep separate IDs and add a disambiguating description, affiliation or location. Never rely on names alone as database identifiers.
When should the spreadsheet be updated?
Update it after a continuity-changing scene is approved. Recording the change at that point is easier than reconstructing character histories after several episodes have been written.