Every series writer hits the same wall eventually. Somewhere around book three, a subplot from book one resurfaces and you genuinely can't remember whether you resolved it, abandoned it, or quietly forgot it existed. Memory alone stops being a reliable system fairly early in a long series, and most writers only realise this once something has already slipped through.
The good news is that you don't need expensive series-bible software to fix this. A few free tools, used the right way, handle subplot tracking better than most people expect.
Why Subplot Tracking Breaks Down in the First Place
The core problem isn't forgetfulness. It's that subplots don't resolve on a predictable schedule. A main plot tends to follow a recognisable arc within a single book, but a subplot might open in book one, go quiet for an entire book, and only resolve in book four. Without a system built specifically to track threads across that kind of gap, even careful writers lose visibility on something that mattered three books ago.
This is also why generic outlining tools often fall short here. Most outlining methods are built around the structure of a single book, not the connective tissue running between several of them. Subplot tracking needs its own layer, separate from your regular outline, and the right free tool depends largely on how your brain prefers to organise information.
Spreadsheets: The Most Underrated Option
A simple spreadsheet, in Google Sheets or any free equivalent, remains one of the most effective subplot tracking tools available, mostly because it's flexible enough to be shaped around exactly what you need rather than forcing you into someone else's template.
A basic structure works well: one row per subplot, with columns for where it opens, its current status, which characters are involved, and which book it needs to resolve by. The real value comes from being able to filter and sort. Sorting by status lets you instantly see every subplot still marked "open" regardless of which book it started in, which is exactly the kind of visibility that memory alone can't provide once a series gets past two or three books.
The downside is that spreadsheets require some discipline to keep updated. They reward writers who are willing to spend a few minutes after each writing session logging changes, and they punish writers who let updates lapse for months at a time.
Notion: Best for Writers Who Think in Linked Pages
Notion's free tier has become a popular choice for series tracking specifically because of how easily it links related information together. A subplot can have its own page, linked directly to the character pages, book pages and timeline entries it touches, which solves a problem spreadsheets handle less elegantly: the fact that subplots rarely exist in isolation from everything else in a series bible.
A simple database of subplots, each with status tags, linked book and character references, and a short running log of developments, tends to work well here. The ability to view that same database as a table, a board sorted by status, or a calendar by resolution date gives more flexibility than a spreadsheet alone, at the cost of a steeper initial setup.
This option suits writers who already keep other series information in Notion and want subplot tracking to live alongside characters, locations and timelines rather than in a separate standalone document.
Trello or Kanban-Style Boards: Best for Visual Thinkers
For writers who think more visually than they do in rows and columns, a free Kanban board, Trello being the most common example, offers a different angle on the same problem. Each subplot becomes a card, moved across columns like "Open," "In Progress," "Dormant," and "Resolved."
The "Dormant" column in particular solves a problem the other tools don't address as directly. A subplot that's deliberately paused for a book or two, rather than abandoned, needs a status that distinguishes intentional pause from accidental neglect. Seeing a card sit in a dormant column is a much clearer visual reminder than a buried row in a spreadsheet that hasn't been opened in months.
The tradeoff is that boards handle long written detail less gracefully than spreadsheets or linked pages. They work best when paired with a card description that's kept genuinely brief, and a separate document for the deeper detail a subplot might need.
Plain Text or Markdown Files: Best for Minimalists
It's worth mentioning the lowest-effort option seriously, because for some writers it's genuinely the most sustainable. A single running markdown or plain text file, one section per subplot, updated chronologically as books are drafted, requires no setup at all and can be searched instantly using a text editor's find function.
This won't offer filtering or sorting, but for series with a more modest number of subplots, often fewer than ten or so threads running at once, the lack of structure is rarely the bottleneck. The bottleneck is usually just remembering to update it, and a plain file removes every excuse not to, since there's no system to learn first.
A Few Practical Habits That Matter More Than the Tool
Whichever tool you choose, a couple of habits tend to matter more than the platform itself. Update the tracker immediately after finishing a draft, not weeks later when details have already blurred. Note not just that a subplot was mentioned, but specifically what changed, since "mentioned again" tells you far less than "revealed she lied about the letter."
It's also worth tagging subplots by intended resolution book as early as possible, even if that plan changes later. A subplot with no intended endpoint is far more likely to be quietly forgotten than one you've already flagged as needing to close by a specific point in the series.
Choosing Based on How You Actually Work
There's no single best tool here, only a best fit for how a particular writer's brain organises information. Spreadsheet-minded writers should default to Sheets. Writers who already think in linked notes will get more out of Notion. Visual thinkers tend to do better with a board. And writers who simply want the lowest possible barrier to consistent updating are often best served by a plain text file they'll actually keep using.
The tool matters far less than the discipline of using it consistently. A simple spreadsheet updated after every writing session will outperform an elaborate Notion setup that gets abandoned after the second book, every time.
