Who a character is comes out most clearly in how they treat other people — deferential to one, commanding to another, unguarded with exactly one friend. That is why a cast is not just a set of characters but a web of relationships, and why the relationships carry as much story as the characters themselves. They are also a quiet source of continuity errors, because a relationship is canon that lives between two characters rather than inside either one, where neither profile is watching it.
This guide covers how to map the relationships in your cast, what to record about each connection, and how to keep that web consistent as it grows — especially once the cast is large enough that no one can hold every allegiance and grudge in their head. Relationships build on the character fundamentals in how to create a character, and they are most load-bearing in the large ensembles where they multiply fastest.
Relationships reveal character
Much of what readers experience as a character's depth is really refraction: the same person shown through several relationships so that more than one facet is visible. A protagonist who is guarded with a rival, tender with a sibling, and falsely cheerful with a parent reads as a whole person, because no single relationship gives the full picture. Define characters only in isolation and they tend to behave the same way with everyone, which collapses them back into a single note no matter how detailed the individual profile.
This is why relationships are a characterization tool and not just a plot one. The contrast between how a character acts in different bonds is information — it shows what they protect, who they trust, where their contradiction lives. So mapping relationships is not bookkeeping you do after the characters exist; it is part of building characters who feel real, because the relationships are where the realness is most visible.
A relationship is its own canon
The crucial shift is to treat each relationship as a fact in its own right, not merely as a note attached to two separate characters. A relationship has a type — family, rivalry, alliance, romance, mentorship — but more importantly it has a history and a state: who wronged whom, what is owed, what secret one holds about the other, what neither will say out loud. That history is canon, and it is exactly the kind of canon that drifts, because it does not obviously belong to either character's record.
The errors that result are familiar to any reader of long series: a bitter grudge that simply stops being mentioned and is treated as resolved without a scene resolving it; a life-debt established with great weight and then forgotten; two characters who, an installment later, share a backstory they did not have before. None of these are visible on a single character's profile, because the fact lives in the space between two profiles. The only way to catch them is to record the connection itself — its state and its history — as a thing you maintain.
How to map a cast
The most useful way to see a cast's relationships is as a graph: characters as nodes, relationships as the lines between them, labeled with the type of bond. Even a rough version of this immediately reveals things a list of character sheets hides — who is central and who is isolated, which clusters of characters are tightly bound, where a rivalry crosses an alliance, and which connections you have been treating as important without ever actually putting on the page. A cast that looks full in a document often looks thin as a graph, with a few characters carrying every meaningful link.
When you map, distinguish the nature of each connection, not just its existence. An alliance and a rivalry are not the same kind of line, and conflict relationships in particular deserve to be marked, because they are the ones that drive scenes and the ones most likely to be contradicted when a feud is quietly dropped. The goal is a picture of the cast's tensions — who is bound to whom and how — that you can read at a glance and check a new scene against. Keeping that picture current is the hard part, and it gets harder fast as the cast grows.
Where CanonBoard fits
CanonBoard builds this map for you and keeps it live. Characters are connected cards on one canvas, and the relationships between them are first-class links you can see as a graph — every bond drawn, conflict relationships marked distinctly, the whole web of the cast navigable instead of scattered across separate sheets. The relationship stops being an implicit note on two characters and becomes an explicit, shared piece of canon.
Because the connections are real structure, the drift becomes catchable. CanonBoard scans on demand and surfaces relationship contradictions with both sides quoted — a grudge that resolved with no cause, a history that appeared from nowhere, a bond that two scenes describe differently. It never invents your characters' relationships; it just keeps the ones you wrote from quietly falling apart. Start free and see your whole cast as the web it actually is.
Frequently asked questions
- Why map character relationships?
- Because a character is revealed most clearly in relation to others, and because the history between characters is canon that is easy to lose track of. Mapping relationships makes a cast's web of allegiances, grudges, and debts visible, which both deepens characterization — the same person behaves differently with each connection — and prevents the contradictions that live between characters rather than inside one.
- What should a character relationship include?
- The type of bond (family, rivalry, alliance, romance), its current state, and its history — who wronged whom, what is owed, and what is unspoken. The unstated parts matter most for continuity: a grudge, a secret, or a debt that the story establishes and then forgets is the most common relationship error. Record the relationship as its own fact, not just as a note on each character.
- How do you keep relationships consistent across a long story?
- Treat each relationship as canon with its own state over time, and update it when the story changes it. Relationship errors usually look like a grudge evaporating without resolution, a debt being forgotten, or two characters sharing a history they did not have earlier. Because the fact lives between two characters, it is invisible on either character's profile alone — mapping the connection explicitly is what makes the drift catchable.
CanonBoard scans your whole world and tells you where it disagrees with itself.
Start free