Relationship and Rank Drift: Family Trees and Chains of Command in a Series
Relationship and rank drift is the continuity error in which an uncle becomes a father’s cousin, a captain outranks the colonel she answered to a book ago, or strangers in Book 1 share a childhood by Book 4. Family trees and chains of command do not bend; record them per book and check every reference against the record.
Check 10 of the 12-check Series Continuity Self-Audit →
What drifts
Three things. Kinship: the exact relation (uncle, father’s cousin, foster-brother) and the generation it implies. Rank: who gives orders to whom, and the title that goes with it, in an army, a guild, a court or a crew. Address: the form one character uses for another (“my lord”, “Captain”, a first name), which readers hear as a statement of relation even when you meant it as texture. Drift happens when a draft needed a scene to work: the sergeant gives the order because the lieutenant was not in the scene, and now he outranks her.
A kinship and rank table, per book
In your series bible, keep two small tables and copy them forward with each book. Kinship: one row per pair that matters (A is B’s what), with the chapter where it was first stated. Rank: one row per hierarchy (the army, the house, the ship), listing who answers to whom and each character’s title, with the chapter of the last change on the page. Promotions, demotions and revealed parentage are plot events; write them in the Events section with their consequences, and update the table the same day. The Series Bible Template has an “Aliases, titles and how others address them” field on every character card for the third kind of drift.
Checking forms of address
Search each new book for every title and honorific your world uses and read the hits in context: a “Captain” addressed as “Commander” is either a promotion you wrote or the error. Do the same for kinship words (uncle, aunt, cousin, ward, heir). This is the fastest check in the Self-Audit and the one most authors skip.
Each book’s canon records the relationships its read found, and in a Full read (the Author, Series and Studio plans, and the free trial at public launch) the Coherence Guardian can flag a relationship that contradicts itself inside that book. In our test manuscript (read on October 13, 2026), a sergeant giving orders to the lieutenant who outranked him was not flagged, so treat rank inside a book as your check too. An “uncle” who became a “father’s cousin” within the same book was flagged in the read’s findings in the same test. Across books, relationships and ranks are never compared: the cross-book check you start compares the appearance and distinguishing marks of same-named characters, their voice when each book holds enough of their dialogue, and the same event’s dates in two fully read books, and nothing else. The uncle who becomes a cousin between Book 1 and Book 3 stays with you and your table.
Questions authors ask
Military, naval and court fiction readers notice it first and write about it most; in any genre, the reader who noticed the chain of command is the reader who cares about your world.
One tree per family, drawn once and copied forward, with every revealed relation dated to its chapter. How to build a character bible covers the cards the tree hangs from; how to keep track of characters in a book series covers the rest of the record.
No. Relationships are recorded per book and never compared across books. Inside one book, in a Full read, a relationship that contradicts itself can be flagged.
StoryHelm is an AI manuscript-intelligence platform for indie series authors. It reads and analyzes an entire fiction series, catches continuity errors before readers do, and never writes or rewrites the author’s prose. You write every word of your book yourself, in StoryHelm’s built-in editor or in files you import. Two disclosed features produce text that isn’t your manuscript: Ship Dock drafts pitch material about the book (a query letter, synopsis, logline or back-cover blurb) for you to review and edit, and Translation Studio produces machine-generated translated editions of a finished book.
Keep reading
POV and Tense Leaks: Head-Hopping in a Series
Head-hopping, a chapter in the villain's head, a slip into present tense: how to log every scene's POV and hold the line across a series.
ReadBuild a Character Bible That Scales Across a Series
A character bible that scales across a long series is a structured record of every character, extracted from the books you wrote and kept tethered...
ReadHow to Keep Track of Characters in a Book Series
Keep every character consistent from Book 1 on: names, fixed traits, voice, relationships and what they know. A tracking method, and what...
ReadCousins stay cousins. The captain still answers to the colonel.
In a Full read, StoryHelm checks each book against its own canon and can flag a relationship that contradicts itself. Across books, the table, and the decision, stay yours. It never writes your prose.
Get the free Self-Audit