Thread Coverage

What it means

A thread is any open question a story raises and promises to answer. A prophecy that names a child not yet born. A locked room nobody has the key to. A grudge between two captains that has not yet come to blows. A coat with a hidden pocket the reader is shown but the character is not. Each of these is a small contract with the reader: you noticed this, and it will matter.

Thread coverage is the record of how each of those promises is doing. For every thread, there are three states StoryHelm watches: set up (the promise is planted), advanced (it is fed, complicated, or partly answered), and paid off (it is kept). A healthy thread moves through all three. A dropped thread stalls after setup and is never heard from again.

To track that movement, StoryHelm records three things for each thread:

• Where it was planted: the scene and chapter where the question first opens. A debt sworn over a deathbed in Book One, promised but not yet repaid. The reader files that away.
• Where it was touched again: every later scene that picks the thread back up, raises the stakes, or reminds the reader it is still live. A thread that is planted and never touched is the one most likely to be forgotten.
• Whether it was paid off: the scene that resolves the question, and whether that payoff lands in the same book or a later one. Some payoffs are meant to wait. The danger is the ones that wait forever.

Coverage is a series problem, not just a book problem

Inside one novel, a dropped thread is annoying but findable: you reread, you notice the gun on the mantel never went off, you cut it or you fire it. Across a series written over years, that same gun is hundreds of thousands of words behind you, planted in a book you finished and shipped long ago and have not reread since. Setups quietly accumulate faster than payoffs, and the gap between them stretches across volumes you can no longer hold in your head at once. StoryHelm holds the whole series in view through the Series Atlas and reports which early-book promises are still hanging when you reach the finale.

The dropped-thread problem

The failure thread coverage is built to catch has one shape: a setup the reader remembers and the author forgot. The example below is invented to show how it reads on the page.

Not every unresolved thread is a mistake. A series can keep a promise open on purpose, holding a payoff for a later book or leaving one mystery deliberately unanswered. The point of thread coverage is not to force every thread closed. The whole difficulty is that a deliberate slow burn and a forgotten setup look identical on any single page: both are just a question left open. The difference only shows up when you can see the early setup and the missing payoff side by side, which is precisely what no single read-through gives you. Thread coverage reports which threads are still open and how long each has been waiting, so you can tell the slow burn from the oversight.

Where it lives in StoryHelm

Thread coverage is one layer of Plot DNA, the per-scene read StoryHelm builds when it analyzes your manuscript. Plot DNA also tracks intensity, stakes, beats, and filler ratio; the coverage layer is specifically the map of threads: what each scene opens, what it advances, and what it closes. Across a series, those per-scene maps roll up into a single view of every promise the series has made and the state each one is in.

The same pass that builds your Canon and runs the Coherence Guardian also charts your threads, so continuity of fact and continuity of promise are caught together rather than in two separate read-throughs. The Guardian asks whether your facts agree with themselves; coverage asks whether every thread you opened was eventually closed.