Somewhere around book four, a reader emails to point out that the character you killed off in book two just showed up for dinner in book four with no explanation. You didn't resurrect him on purpose. You just forgot. This is one of the most common and most embarrassing continuity errors in long-running series, and it's entirely preventable with a system built for series continuity instead of your memory alone.
Fantasy and mystery authors run into this constantly because both genres kill people for a living. Mystery has a body count by design. Fantasy has wars, plagues, and betrayals spanning a dozen POV characters across five books written over five years. By the time you're drafting book five, you can't hold every death, every survivor, and every "presumed dead but actually not" in your head. You need a record that outlives your memory.
Why character deaths are the easiest continuity error to make
Deaths are quiet in your files. Unlike a plot thread, a death isn't something you're actively tracking scene by scene — it happens once, in one chapter, and then you move on. Six months later when you're outlining the next book and need a name for a minor scene, your brain reaches for a familiar character without checking whether that character is still breathing.
The problem compounds in shared universes. If you write a trilogy plus two spin-off series set in the same world, a death that happens in the main trilogy needs to be respected in every spin-off character list, every family tree, every "who's who" reference page, forever. A single missed detail — a supposedly dead character mentioned in present tense in a spin-off's back matter, or invited to a wedding in book three of a companion series — breaks trust with readers who've been paying closer attention than you have.
Build a single source of truth for series continuity
The fix isn't a better memory. It's one authoritative record per character that every book in the series pulls from, instead of five separate documents that can drift out of sync. Whether you're using a spreadsheet, a binder of index cards, or dedicated story-bible software, the principle is the same: one entry per character, updated in place, referenced rather than duplicated.
What to log for every character
- Full name, aliases, and any name changes across the series
- Status: alive, deceased, missing, or unknown to other characters
- The book and chapter where death (or presumed death) occurs
- Cause of death and whether other characters witnessed it firsthand or only heard about it secondhand
- Relationships that are affected — spouses, rivals, mentees, anyone whose arc changes because this person is gone
- Notes on whether the death is reversible in your world's rules (necromancy, time travel, faked death) so you don't accidentally write yourself into a plot hole later
The witnessed-versus-secondhand distinction matters more than it looks. If only one unreliable character saw the death, your other characters should keep acting like the missing person might return — and your codex should flag that ambiguity so you don't accidentally write everyone else as fully certain.
The Deceased flag: mark it once, respect it everywhere (characters only)
Pendrilo's codex includes a Deceased checkbox for characters — a feature that marks when and how a character died. Once you flag a character as deceased, that status carries forward from that point in your series. Since v2.41, the deceased flag is available for characters only, paired with a "when and how" note you write to explain the death's context.
The flag matters most in a shared universe. If your series lives across multiple books in the same Pendrilo shelf, codex entries can be shared universe-wide instead of copied and pasted into each new project. Mark a character deceased in the book where it happens, and that status is visible from every other book in the universe that references the same entry — spin-offs, prequels, companion novellas, all of it. You're not maintaining five copies of the same character sheet and hoping they stay in sync. There's one entry, and the flag propagates with it.
Each entry can also generate a printable one-page profile sheet, which is genuinely useful when you're deep in drafting book six and need a fast reference without opening the whole codex: name, relationships, status, and notes on one page you can keep next to your keyboard or print for a critique partner who's helping you track the timeline.
Handling resurrections, fake deaths, and unreliable narrators
Not every death stays dead, and that's fine — as long as it's intentional and tracked, not accidental. A few patterns worth planning for:
- Faked deaths. If a character's death is staged for other characters but not for the reader, log the real status separately from what other characters believe. A note field on the entry ("world believes deceased; actually alive, hiding in Port Callow") keeps you from slipping and having someone react to the fake death as though it were real in a scene from another character's POV.
- Resurrection magic or tech. If your world allows characters to come back, decide the rules once and write them into the entry's notes, not just your head. Readers will forgive resurrection if it follows established rules. They won't forgive it if it feels like you needed the character back and invented a loophole on the spot.
- Presumed dead. Missing-in-action characters need their own status distinct from confirmed deceased. Don't flag someone deceased just because they haven't appeared in two books — that's a different kind of loose end, and conflating the two will trip you up when you eventually bring them back.
Whatever the mechanism, write it down where future-you will actually see it before drafting the scene that depends on it.
A pre-launch continuity checklist
Before you send book four (or book twelve) to your editor or beta readers, run a deliberate pass focused only on continuity, separate from your regular revision pass:
- Pull up every character who has died anywhere in the series and confirm they don't appear in present tense anywhere in the new manuscript, including back matter like character lists or "previously in the series" recaps.
- Check any family tree, dramatis personae, or relationship map you include in front or back matter — these are the places dead characters sneak back in because they were written once, early, and never revisited.
- Verify secondhand knowledge is consistent: does every character who should know about a death actually reference it, and does nobody who shouldn't know act like they do?
- If you write in a shared universe, check spin-off and companion titles too, not just the main series line. A death in book three of the main series needs to be respected in a novella you published between books two and three, if it's set after the death chronologically.
If you're also polishing KDP metadata or double-checking cover dimensions while you're in launch-prep mode, Pendrilo's free tools cover the calculator-and-checklist side of things — royalty math, cover sizing, keyword byte counts — so continuity checking doesn't have to compete for your attention with formatting math.
Continuity tracking isn't glamorous work, but it's the difference between a series readers trust and one they start fact-checking against a spreadsheet of their own. If you're planning a long series or a shared universe and want the character status to live in one place instead of five documents, Pendrilo's codex and its deceased flag for characters are worth exploring — you can register and start building your series bible from book one.
