LitMemoCharacter Relationship Maps for Multi-Character Serials: When to Build One, How to Maintain It
TL;DR: Most writers assume a relationship map is a "planning tool" — you work out every character relationship before you write a word. But that's not how people actually use one. The value isn't in planning; it's in looking things up: you're 35 chapters deep and you want to remember exactly how these two characters fell out last time. A relationship map for 2-3 characters is a burden; at 6+ it starts to pay off; at 10+ it's basically mandatory. This post covers when to start one, how to maintain it, and the two classic mistakes to avoid.
The relationship map you imagine vs. the one you actually use
Ask ten writers just starting their first novel, "What's a relationship map for?"
Nine will say, "Planning the story, obviously — you nail down every character relationship first, then start writing."
But I looked at the relationship data from hundreds of writing projects, and reality doesn't work that way. Writers who build the relationships before writing the story are rare — out of five hundred-plus projects, only a dozen or so were "planners" with 5+ relationships but a single chapter or fewer. The overwhelming majority fall into two patterns: filling it in as they write (by far the most common), or not using a relationship map at all (mostly short-form writers).
The vast majority fill it in as they go: ten chapters in, they realize the cast has grown and go back to tidy up; 25 chapters in, they can't remember where A and B last clashed and open the map to check; 40 chapters in, they notice a side character is tangled up in too many relationships and go back to redistribute them.
The core value of a relationship map isn't "planning the story" — it's external memory.
When should you start a relationship map?
| Number of characters | Relationship-map ROI | What to do |
|---|---|---|
| 1-3 | Negative (more burden than benefit) | Just keep it in your head |
| 4-5 | Break-even | Optional; worth it for romance and other genres where the relationships themselves are the subject |
| 6-10 | Positive | Starts paying off, especially for long serials |
| 10+ | Strongly positive | Basically mandatory — your memory won't hold up |
The concrete numbers: across hundreds of projects, over 70% use a relationship map. On average, 17 relationships per project vs. 7.9 characters — more than twice as many relationships as characters.
Two classic mistakes
Mistake 1: Orphan characters (the most common)
Across hundreds of writing projects, about 30% of characters are "orphans" — they have a name and a full profile, but no relationship to any other character at all.
Orphans usually come in two kinds:
- Bit players: the tavern keeper, a passing NPC. No relationships is fine — they shouldn't be woven into the main plot.
- Forgotten key supporting characters: you designed them, gave them a full backstory, but forgot to connect them to your main-plot characters. These are the ones to fix.
Scan periodically: does every fully-developed character have at least one relationship with another character? If not, ask yourself — does this character really need to exist?
Mistake 2: The super-hub (the easiest to overlook)
The other extreme: a handful of central characters connected to 10+ others. The most extreme case I've seen was tangled up in 60+ relationships. Usually this is the protagonist.
Worth thinking about: when one character is connected to too many others, the plot drags them everywhere, and every minor character has to interact with them just to enter the story. Will readers start to feel the whole world revolves around one person?
A healthy relationship web is distributed and layered:
Protagonist ←→ Core support A ←→ Support B
↕ ↕
Core support C ←→ Support D
For every character with 10+ relationships, ask yourself: of those 10, how many are unnecessary? Could you let the supporting characters form relationships with each other and take some of the load off the protagonist?
When to actually use your relationship map
Before starting a new chapter
Look at the current relationship picture: which characters have unresolved conflicts? Which foreshadowing hasn't been paid off yet? The map helps you find the thread most worth developing in the next chapter.
When revising the outline or adjusting the plot
Decided to cut a character or change a relationship line? Open the map and see how many other elements it touches. Sometimes you think it's a small tweak, and the map tells you: that thread moves half your world.
When you're mid-story and starting to suspect "am I making a mess of this?"
This is exactly when you should open the map. If it looks like a mess — too many orphans, a super-hub that dominates, core supporting characters with no cross-connections — your story structure is in trouble. The map tells you before your readers catch it.
When you've finished one book and are starting the sequel
The end of the previous book is the starting point of the sequel. Review the full relationship picture of the earlier work to keep the sequel's setup consistent.
A real comparison: 50 characters vs. 1 character vs. 10 characters stalled
Compare three projects around 50 chapters in:
A: 50 characters, 800+ relationships, 140,000 words, still going
Only 1 orphan out of 50 characters (2%) — against the 30% average, this writer is extraordinarily meticulous. An average of 16 relationships per character. No single super-hub; the relationships are spread across different supporting characters.
B: 1 character, 0 relationships, 60,000 words, stalled since March
Probably a diary or a single-thread account — no use for a relationship map at all.
C: 10 characters, 0 relationships, 8,000 words, stalled for a month after two chapters
The classic "planner" trap — every character built out, but no relationships written and no story to move forward.
The difference between A and C isn't the number of characters — it's writing rhythm. A fills things in while writing; C wants to work out every relationship before putting pen to paper — and ends up never putting pen to paper.
How to maintain a relationship map
1. Start with the main-plot characters and expand outward
Don't add every character at once. Start with the protagonist and 3-5 important supporting characters, and complete their relationships first. Then, with each new chapter, add the characters and relationships that appear in it.
2. Label relationships with the "why," not just the "what"
"A is B's master" is too thin. Change it to "A is B's master, but is hiding that he once killed B's father" — and the relationship instantly becomes plot fuel.
3. Relationships change — remember to update them
In a long serial, enemies become friends and friends become enemies. After each major chapter, spend 5 minutes scanning through and update any relationships that have gone stale. An out-of-date relationship map is worse than none — you'll write the wrong plot off the wrong data.
4. Automatic detection vs. building by hand
Writing tools with automatic detection log each chapter's character "mentions" as a relationship timeline, saving you the manual work. But emotional relationships (love, hatred, jealousy) still have to be added by hand — a tool can't infer those from the text.
Further reading
- How to prevent a character-management meltdown → Why character sheets inevitably fall apart after chapter 30 of a long serial
- The reverse approach to character sheets → How do you write a novel character sheet? A from-scratch guide to building characters
When you're writing a long serial, your memory won't hold the relationship matrix — that's not a flaw, it's physical reality. Use a tool as external memory and save your brainpower for the story itself. LitMemo offers relationship-mapping features, including automatic detection of chapter mentions, cross-series relationship views, and filtering by relationship type.