Writing Subplots: The Secondary Stories That Make Your Main Story

A subplot exists to deepen your main story — thematically, emotionally, or structurally. What it doesn't exist for: adding word count, demonstrating additional ideas, or filling time between plot events. The removal test is simple and brutal: take the subplot entirely out of your manuscript. Does the main story weaken? Does any character feel less developed? Does the theme feel less resonant? If the answer to all three is no, the subplot is not earning its place. Every scene in your novel costs the reader time and emotional investment. Subplots that don't pay for that investment with something thematically essential are deficits, not assets. The best subplots are the ones that feel like they couldn't have been in any other book.

The most elegant use of a subplot is as a thematic mirror — a secondary storyline that asks the same question as the main plot but in a different register. If your main plot is about whether trust is worth the risk of betrayal, your subplot might follow a minor character who is also making a trust decision — one who chooses differently than the protagonist, and whose consequences illuminate what the protagonist's choice might cost. This structure turns your entire cast into a thematic argument. Every storyline is asking the same question and arriving at different answers, which enriches the main story's resolution because readers have seen multiple versions of the same choice. The subplot doesn't repeat the main plot — it triangulates it.

Romance subplots appear in almost every genre precisely because they work — they humanize protagonists and add personal stakes to professional or adventure conflicts. But they're also the most abused subplot type. When a romance subplot exists because genre convention expects it rather than because the characters have a thematic reason to be together, it reads as mechanical. The test: does this relationship mirror or complicate the main story's theme? If your protagonist is learning to be vulnerable in the main plot, their romantic arc should also be a vulnerability story, not a coincidental attraction. Integration is everything. A romance subplot that could be transplanted into any book shouldn't be in your book.

Subplot pacing is about timing cuts and returns strategically. Cut to a subplot when the main plot needs a breath — after a high-tension scene, a revelation, or a setback. Return to the main plot before the subplot loses momentum. The error most writers make is cutting to a subplot at the wrong moment — right at the peak of a main-plot scene, which breaks tension instead of building it. Cut between, not during. Also watch the proportion: if your subplot is getting more page time than your main plot, something has gone wrong structurally. A subplot that has grown into a co-equal story needs its own book, or needs to be folded back into the main narrative.

A subplot that goes nowhere is worse than no subplot at all, because it takes up space and promises something it doesn't deliver. The most common failure: a subplot that opens a question but doesn't resolve it within the novel. The second most common: a resolution that's disconnected from the main story's climax — the subplot ties itself up neatly in a side chapter while the main story reaches its peak, rather than converging. Fix the first by asking: what does this subplot's resolution mean for the main story? Fix the second by braiding the resolution into the climax. The best subplots resolve as a consequence of the main climax, or enable it, or are enabled by it. Parallel resolution is a sign of missed integration.

ARC readers are ideal subplot diagnosticians because they experience the novel as a flow. When a subplot isn't working, readers feel it as impatience — they just want to get back to the main story. Ask specifically: Were there storylines you found yourself skimming? Were there secondary characters whose sections you were eager for or dreading? Did every thread feel like it was going somewhere? Was there anything that felt unresolved? The pattern across multiple ARC readers is the real signal — if three out of five found the same thread slow, it's slow. iWrity gives you access to early readers who can give you this kind of structured, comparative feedback before launch.