How to Track Subplots in a Novel
Subplots get dropped when they run beside the main story instead of into it. Here is how to track every subplot, connect setups to payoffs, and stop threads tangling.
By Scyn Team
Key takeaways
- A subplot only works if it connects to the main plot. A thread that runs alongside the story without ever touching it reads as a digression, no matter how good the writing is.
- Most dropped subplots are not forgotten; they are unresolved. The setup is there and the payoff is missing, which is why the reader feels a loose end without being able to name it.
- The two checks that catch almost every subplot problem are: does each setup have a payoff, and does each subplot change the main plot at least once?
- Color and weight matter. A subplot with more scenes than the main plot is usually competing with it rather than supporting it.
- A list of chapters cannot show whether a subplot connects. A map can, because a disconnected thread is literally a cluster of nodes with no edges into the main spine.
If subplots in your novel keep getting dropped, picked up late, or quietly forgotten, the problem is rarely memory. It is connection. A subplot you can track is one that touches the main story at specific points: a setup, a complication, a payoff. This guide shows you how to give each subplot a clear job, how to connect every setup to the scene that pays it off, and how to map the whole web so a thread that never connects becomes impossible to miss.
What is a subplot, really?
A subplot is a secondary story thread that runs through the novel beneath the main plot. A romance beside the heist. A family conflict beside the murder investigation. A mentor relationship beside the coming-of-age arc. The useful definition is not "a smaller story." It is "a thread that changes how the main plot lands."
That last part is the whole game. A subplot that does not change the main plot is not a subplot. It is a parallel story that happens to share a book. The reader can feel the difference even when they cannot articulate it, because a true subplot creates setups and payoffs that the main plot then depends on.
Why do subplots get dropped?
Three reasons, and they compound.
They run beside the story, not into it. The subplot has its own beginning, middle, and end, but none of those beats touch the main plot. It is structurally optional, so when revision pressure hits, it falls out and nobody notices a hole.
The setup has no payoff. You plant something early, a secret, a grudge, a promise, and then the draft moves on. The reader is holding a question the book never answers. This is the single most common subplot failure, and it produces that vague "something was left hanging" feeling.
There are too many threads to hold in your head. Past two or three subplots, tracking them mentally stops working. You remember the threads you wrote most recently and lose the ones from two hundred pages ago. This is not a discipline problem. It is a working-memory limit, and the fix is external: get the threads out of your head and onto something you can see.
How do you track subplots without losing the thread?
Give each subplot one sentence
Before anything else, write each subplot as a single sentence that states who wants what and how it pressures the main plot. "Maya's debt to her sister forces her to take the job that puts her in the killer's path." If you cannot write that sentence, the subplot does not yet have a reason to exist. The sentence is your test for every thread.
Connect every setup to a payoff
Go through the draft and pair them. Every subplot setup (a planted secret, an unfulfilled promise, a simmering conflict) should have a later scene that pays it off. List the setups in one column and the payoffs in another. The orphans, setups with no payoff and payoffs with no setup, are your subplot bugs. Fix them by adding the missing half or cutting the lonely one.
Mark the convergence points
The strongest subplots converge with the main plot at least once before the climax, and ideally feed directly into it. Find the moments where a subplot and the main plot collide and change each other. If a subplot never converges, it is running in its own lane. Either route it into the main story or ask whether the book needs it.
Watch the weight
Count the scenes in each thread. A subplot is support, not a rival. When a subplot starts carrying more scenes than the main plot, one of two things is true: it has quietly become the main plot (in which case restructure around it), or it is stealing momentum (in which case trim it). Either way, you want to see the imbalance, and you can only see it once the threads are laid out side by side.
A worked example: two subplots in a murder mystery
Say the main plot is a detective hunting a killer. Subplot A is the detective's failing marriage. Subplot B is her rookie partner hiding a personal connection to the victim.
Run each through the one-sentence test. Subplot A: "The detective's wife issues an ultimatum, forcing her to choose between the case and the marriage at the worst possible moment." Subplot B: "The rookie's hidden connection to the victim contaminates the evidence the conviction depends on." Both sentences name a want and a pressure on the main plot, so both threads earn their place.
Now pair setups with payoffs. The ultimatum in chapter 3 pays off in chapter 24 when the detective misses the anniversary dinner to follow a lead, and the marriage ends. The rookie's flinch at the crime scene in chapter 2 pays off in chapter 21 when the defense discovers the connection and the case nearly collapses. Each early beat has a later scene that answers it.
Finally, mark the convergence points. Subplot A converges when the divorce papers arrive mid-interrogation and the detective, rattled, misses a lie she would normally catch. Subplot B converges when the contaminated evidence forces the detective to find a second path to the killer, which becomes the climax. Neither subplot is decoration. Remove either one and the main plot resolves differently, which is exactly the test they need to pass.
If your threads work separately but fall apart when you combine them, the worked plot outline example shows the full merge into one scene-by-scene plan.
What tools can you use to track subplots?
Most writers reach for one of four methods.
| Method | What it shows | Where it breaks down |
|---|---|---|
| Spreadsheet or subplot grid | Which chapters each thread appears in | Shows presence, not connection. The romance appearing in chapters 4 and 19 says nothing about whether 19 pays off 4. |
| Index cards on a corkboard | Scene order, easy to rearrange | The connections live in your head. Past forty cards the wall stops being readable. |
| Writing-app labels (Scrivener keywords, tags) | Which scenes belong to which thread | Labels mark membership, not consequence. You can filter to every romance scene and still not know if the thread resolves. |
| Visual plot map | Each thread as a colored line with explicit setup-to-payoff connections | Needs an upfront hour to lay the threads out. |
The first three share one gap: they record where a subplot appears, not what it connects to. And connection is the thing that fails when a subplot gets dropped. A grid can tell you the romance thread has not appeared in eight chapters. It cannot tell you the romance thread never touches the investigation at all.
How many subplots can a novel hold?
There is no fixed number, but there is a useful rule: every subplot should earn its thread by changing the main plot at least once. A tightly plotted thriller might run two. A sprawling epic fantasy might run six, especially if it is also a multi-POV novel where each viewpoint carries its own thread. The limit is not a count. It is whether you can still trace how each thread feeds the spine. When you lose that thread, you have one subplot too many, regardless of the total.
How do you track subplots as a map instead of a list?
A chapter list puts everything in one column and hides the relationships. You can see that the romance subplot appears in Chapter 4 and again in Chapter 19, but you cannot see whether Chapter 19 pays off what Chapter 4 set up, or whether the romance ever touches the main investigation at all.
A map shows it directly. Lay each subplot out as its own colored thread, place the main plot as the spine, and draw edges where a subplot creates setup, complication, or payoff. A dropped subplot becomes a cluster of nodes with no edges into the spine. An unpaid setup becomes a node with nothing flowing out of it. The problems you were trying to hold in your head become things you can point at.
Tracking subplots in Scyn
Scyn is built around this way of working. Each story event is a node on a canvas, and you give every subplot its own color from a fixed palette, the way you would use highlighters. The main plot stays neutral, the romance is amber, the rookie's secret is blue. One glance at the canvas tells you how much space each thread takes up, which is the weight check from earlier without any counting.
Connections are drawn as arrows with optional labels, so "plants the secret" in chapter 2 gets a literal line to "secret exposed" in chapter 21. An unpaid setup is a node with no arrow leaving it. A subplot that never touches the main plot is a colored cluster floating free of the spine. Both problems are visible before a reader ever finds them.
The filters do the isolation work. Filter by color and the canvas shows one subplot on its own, start to finish, so you can check its arc without the noise of everything else. Filter by chapter or act and you see which threads are active in any stretch of the book, which catches the subplot that vanishes for a hundred pages.
Scyn's subplot tracker template sets this up for you: a main spine with each subplot as a connected thread, so setups, payoffs, and convergence points are visible at a glance. If your subplots are tied to different viewpoint characters, the multi-POV novel template maps each viewpoint as its own line and marks where they intersect.
For the larger outlining process these threads sit inside, how to outline a novel covers the full method, and visual plot mapping for writers explains why a map catches what a list cannot.
Subplots are not hard to track once you stop trying to remember them. Give each one a sentence, connect every setup to a payoff, route each thread into the main story, and put the whole web somewhere you can see it. The threads that matter will hold. The ones that do not will show themselves.