I’ve known authors who finish their first novel, edit, polish, and then publish it immediately. That’s a completely valid choice. It’s also how you discover, three hundred pages into Book Two, that you locked a character into the wrong location in Chapter Seven of Book One, and the fix requires either a retcon your readers will notice or a structural contortion your plot won’t survive.
The error didn’t happen in Book Two. It was already there, waiting, from the moment you hit publish.
This is the continuity trap for series authors: the mistake is invisible at the point where it’s cheapest to fix, and obvious at the point where it costs the most. The solution isn’t better revision. It’s a tracking system that makes the error impossible to hide before it’s written.
Here is mine.
The Spreadsheet Is Not a Series Bible
A series bible is a reference document. It describes what exists: the world, the rules, the factions, the lore. A tracking spreadsheet is something different. It’s a record of what happened, chapter by chapter, with enough relational structure to catch contradictions across books before they compound.
I track Vampires of Tucson in a single Excel workbook. The series runs eleven books. Three are written, and I’m just now starting to publish Rocket at vampiresoftucson.substack.com. I’m confident enough to begin finalizing the first three because the entire series is already mapped.
The sheet for Rocket (Book 1) is the foundation everything else keys off. Each row is a chapter. Each column answers a question the rest of the series needs to stay consistent with.
What Goes in Each Row
The columns are: Chapter Number, POV, Location, Cast, Timeline, and Summary.
Chapter Number is obvious. The rest earn their place twice over, because each column serves two masters: the author’s continuity and the AI writing partner’s context.
POV defines whose inner voice the reader hears (I write third-person limited), and it tells the AI exactly which entry to pull from the Character Bible. One field, two jobs. Cast does the same thing for the scene: every character present, by canonical name, so the AI knows whose profiles to load before a word gets written. Location references a dedicated location sheet that defines the important features of that place, some that must be named in the prose and some that are pure backstory, relevant only when something that happened there matters to what happens next. Timeline is the in-story date and time, precise enough that events in Rocket can be cross-referenced against events in Babydoll (Book 2) or Blondie (Book 3) that are happening simultaneously or in close sequence.
Summary is where the tracking earns its keep. Not a synopsis. A functional record. What changed, what was revealed, what was established. If a character makes a commitment in Chapter 12, the summary records it in terms specific enough that I can search the sheet for it six months later and find it in thirty seconds.
Here’s the actual row for Rocket’s prologue:
Chapter 0, Prologue POV: Rocket | Location: Managua | Cast: Naida, Mateo, Mateo’s father | Timeline: 12/1/2023
After her parents are killed in gang crossfire and her remaining family refuses to take her in, fifteen-year-old Naida arrives late at night at her boyfriend Mateo’s house, deliberately manipulating his attraction and sense of responsibility in a calculated attempt to secure a hidden place to stay. Her plan collapses when Mateo’s father intervenes, instantly recognizing her tactics and rejecting her not as a victim but as a threat to his son’s future. Stripped of leverage and options, Naida is then coldly “helped” by the same man, who offers to pass her to his criminal associates as trafficked labor under the guise of opportunity in the United States, framing exploitation as rescue and disposal as pragmatism. Faced with homelessness and street violence as the only alternative, Naida accepts, fully aware something is wrong but unable to refuse, and leaves believing she has chosen survival. The father privately sells her as “cargo,” congratulating himself on protecting his family at her expense.
That’s not a summary written for a reader. It’s written for the author six months from now, or for a subsequent book that needs to know exactly what Naida understood, what she didn’t, and what the father’s precise motivation was. Every downstream chapter that references this moment keys off that record. For chapters with dense downstream dependencies, you can break the summary into individual story beats - one line per beat, each one a discrete fact the rest of the series might need to reference.
That prologue wasn’t in the original plan. The idea hit about halfway through writing Blondie. One night it became clear that Rocket needed to exist before the story opens, that opening with her digging out of her own grave wasn’t enough, she needed backstory the reader could feel. Because the spreadsheet was already structured, adding Chapter 0 meant inserting a row, populating each column, and noting what downstream chapters it connected to. The system absorbed a new chapter mid-series without breaking anything. That’s the point of building the infrastructure before you need it.
The Relationships Columns
This is the part most writers don’t build until they need it and no longer have time to build it cleanly.
Every book in Vampires of Tucson gets its own sheet in the workbook, and every book also gets its own column in every other book’s sheet. That happens the moment a book becomes a concept, not when I start writing it. So Rocket’s sheet has a Babydoll column, a Blondie column, a Crimson Cabaret column, and so on across all eleven books. Each column tracks the cross-references between that chapter and that specific book. The architecture exists before any chapters are drafted, because by the time you’re drafting, the relationships are already forming whether you’re recording them or not.
The relationships columns work in both directions. If Chapter 10 of The Crimson Cabaret references something that happened in Chapter 3 of Rocket, or was directly influenced by it, I note that in two places: the Crimson Cabaret sheet on Chapter 10’s row in the Rocket column, and the Rocket sheet on Chapter 3’s row in the Crimson Cabaret column.
Both entries point at each other. When I go back to revise Rocket Chapter 3, the spreadsheet tells me that Crimson Cabaret Chapter 10 is downstream. I check it before I change anything. When I’m writing Crimson Cabaret Chapter 10, I can see exactly which Rocket chapter I’m building off of and verify I’m working from the current version.
There’s also a column for the original draft. Before Rocket, Babydoll, or Blondie existed as individual books, there was a 167-chapter, 400,000-word unfinished series rough draft: the entire arc written out as a single unwieldy whole. Rocket, Babydoll, and Blondie weren’t adaptations of that draft so much as expansions of it, written to fill in the gaps the original never rendered on the page. That draft is the skeleton. The individual books are the flesh. Keeping that lineage visible in the spreadsheet means I can trace any scene or decision back to its structural origin and ask the right question: does this serve the story, or is it a load-bearing remnant I inherited and never questioned?
Why Publish Book One Later
The spreadsheet isn’t the argument for waiting to publish. The eleven books of planning are. I’m publishing Rocket now not because I just finished writing it, but because I’m eleven books deep into knowing exactly what Rocket needs to be.
Once Book One is out and readers have it, it’s locked. Every chapter in every subsequent book that references, builds on, or was shaped by Book One is a constraint you can’t change without breaking a published promise. That’s a reasonable constraint to accept... once you know what the rest of the series actually needs from it.
There’s a second half to this. Rocket didn’t go from first draft to publication. The actual sequence looked like this: write Rocket, then age it by writing Blondie, then review Rocket, then age it again by writing Babydoll, then review Blondie, then review Rocket again, then plan the next book, then review Babydoll, and so on. The aging isn’t passive waiting. It’s active work on the next book, which means every time you return to Rocket, you’re reading it with fresh eyes and with direct knowledge of what the subsequent books actually need from it.
Each pass caught something the previous one missed. That cycle takes time, and that time is not wasted. It’s the difference between a book that’s finished and a book that’s ready.
Most authors don’t know that when they hit publish. They find out later, the expensive way.
By the time you notice the error, you’ve usually already written it into three subsequent chapters across two different books. The fix isn’t a sentence edit. It’s archaeology. You trace the wrong assumption back to its origin and rewrite outward from there. The spreadsheet doesn’t prevent you from making the error. It makes the error impossible to hide before it spreads.
The difference in effort between catching it in the spreadsheet and catching it in revision is roughly the difference between noticing you used the wrong ingredient before you start cooking and noticing it after you’ve served the dish.
You may also like: - Building Believable Characters - Before You Write a Word - Have Some Standards When You Use AI to Write