How to keep track of characters in a novel, scene by scene
To keep track of characters in a novel, record two facts for every scene: who is actually in it, and where it takes place. Then lay those facts out with scenes running across and places running down, so each character becomes a line through the book. Gaps in a line show who has dropped out; crowded rows show where the story keeps returning.
That’s the whole method. The rest of this post is how to do it well, what to look for once you have it, and how ProseSpun builds the same map from your prose.
Why is it so hard to keep track of characters in a long draft?
Because you remember the story you meant, not the one on the page. Twenty scenes into a draft, a simple question gets hard: when did Tom last turn up? You know he was at the depot in chapter one. You think he was at Café Mercer in chapter two. After that, you’d have to page back and look.
Character notes don’t answer it either. A profile tells you who Tom is. It doesn’t tell you that he hasn’t been in a scene since chapter two.
What should a scene-by-scene character tracker record?
Keep it small. For each scene, write down:
- The scene’s number, counted through the whole book. “Scene 14” is easier to scan than “Chapter 3, Scene 2”.
- Where it happens. One place per scene, or “not sure” if the prose never says. That “not sure” is useful too.
- Who is present. Only the people who are in the scene, not everyone it names.
- What happens between them. One line for each thing that changes between two people: a quarrel, a confession, a handoff.
The third point matters most. “Tom’s coat was still on the hook” names Tom, but he isn’t in the room. Neither is he when Lisa says his name aloud on the phone. If you count every mention, a character who left the story in chapter two can look busy until the last page.
How do you turn the notes into a map?
A spreadsheet works. Put scenes across the top and places down the side. In each cell, write the initials of whoever is in that place in that scene.
Then read across a row of initials for one person, and imagine drawing a line through their cells. Where they skip a scene, the line breaks. Where they move from the café to the street, it bends.
Here is a small one, from a story set in a wet October in a harbour city:
| Scene 1 | Scene 2 | Scene 3 | Scene 4 | Scene 5 | |
|---|---|---|---|---|---|
| Café Mercer | Lisa, Tom | Lisa | Lisa | ||
| Mercer Street | Lisa | Lisa | |||
| The depot | Tom |
You don’t have to read the prose to see it: Tom is gone after Scene 2.
What should you look for when you revise?
Once the map exists, four patterns are worth checking.
- A line that stops. A character who disappears partway through. Maybe that’s right. If Tom was meant to matter in the last act, now you know he hasn’t been in a scene since chapter two.
- A place nobody visits. A row that empties out for twenty scenes is a place the story left behind. A row everyone crowds into may be doing too much.
- Meetings that don’t change. If Lisa and Tom are meant to be drifting apart, the scenes where they share a place should thin out. If they don’t, the draft is saying something your plan isn’t.
- A scene with no place. If you couldn’t say where a scene happens, a reader may not be able to either.
A before-and-after example
Before the map, the writer’s plan said: Tom stays at the edge of the story until the depot fire in chapter five.
The map showed that Tom wasn’t at the edge. He was missing. He had no scene between Scene 2 and the fire, so when he arrived at the climax he was nearly a stranger.
After revising, Tom has two short scenes in chapters three and four, one at the depot and one passing Lisa on Mercer Street. His line runs dashed through the middle of the book but never vanishes, and the fire lands on someone the reader remembers.
If you plan your scenes as short notes before writing them, that’s where a missing character gets a beat of their own. (More on that in how to write story beats.)
How does ProseSpun track who is where?
Keeping the spreadsheet above by hand is the part most writers stop doing. In ProseSpun, a writing app for people with more story than sentences, the Threads tab builds the same map from what you’ve already written. It reads the people and places your prose mentions and lays them out across your scenes. You don’t fill anything in.
Places as rows, scenes as columns, people as lines. Any card that isn’t a character can be a row, so Café Mercer, Mercer Street and the depot can be rows, and so can a ferry or a thieves’ guild. A place inside another sits under it. Each person is a line that curves from scene to scene and runs dashed through the scenes they miss, until they turn up again.
Present, not just named. Threads draws a character in a scene only when the prose puts them in it. A possessive like “Tom’s coat” or a name inside quoted speech doesn’t count. A first-person narrator always does.
Scenes with no place. If a scene names people but nobody has said where it happens, they sit in a last row, “Not placed yet”. Threads then asks about the first such scene: “Where is Scene 6?” You pick a place from the story’s cards, or say Not now. Your answer is kept, and ProseSpun never writes over it.
Events where lines meet. A small diamond where two lines meet is an event you’ve accepted. Selecting it shows what happened, who and where, and “Read it in Scene 9 →” takes you to the paragraph it came from. If you rewrite that paragraph, the event is withdrawn the next time the scene is read.
Following one person. Follow someone lists everyone in the order they first appear, each with a strip of bars, one per scene: tall where they’re in it, a stub where they’re not. Pick Tom and his line comes forward in the accent colour, and the header reads like “Character · in 9 of the 12 scenes shown”. You can follow a group, too. Long stories add a Whole story strip with a lens you drag, or move with the arrow keys, through the book.
The list view. Switch to List and the same story reads back as sentences, one section per card: its events with links to their scenes, who it shares scenes with, the ties true of it now, and what it sits inside.
The people and places themselves are the story’s cards, which ProseSpun drafts from your prose and you keep or turn down. (See how to make a story bible that stays up to date.)
Threads changes nothing on your page. While it reads, a line under the tab says so, “ProseSpun is reading · 2 of 3 scenes”, and it waits while you’re typing. If no model server is running, it says that, and the rest of the app keeps working. The same scene-by-scene reading is part of how ProseSpun keeps a long book in mind.
Related reading: How to avoid continuity errors in writing and First person vs third person.
Frequently asked questions
What is the easiest way to keep track of characters in a novel?
Note, for every scene, who is present and where it takes place, then lay it out with scenes across and places down. A spreadsheet is enough. The map shows gaps you won’t see by rereading.
Should I track every time a character is mentioned?
No. Track when a character is in the scene, not when they’re named. Someone remembered, quoted or referred to by a possessive isn’t present, and counting those mentions hides the gaps you’re looking for.
How do I find characters who disappear from my story?
Follow one character across the map and look for long stretches with no appearances. A line that stops partway through the book is either a deliberate exit or a character the draft forgot. Decide which, and give them a scene if they still matter.
Is a character tracker the same as a character profile?
No. A profile records who someone is: their history, habits and relationships. A tracker records where they are, scene by scene. You need both, and they answer different questions.
Write a few scenes, then open Threads and see who is where.