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 it finds, StoryHelm watches two states: set up (the promise is planted) and paid off (it is kept). In between, a thread is advanced, fed, complicated, or partly answered, on its way to being kept. A healthy thread is opened and eventually closed. A dropped thread stalls after setup and is never heard from again.

To track that, 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.
• How much weight it carries: whether the setup reads as a major plot point, a significant subplot, or a minor detail, and which characters it involves. A heavy promise left open is the one readers are most likely to remember.
• Whether it was paid off: the scene that resolves the question within the book, or a flag when a setup is still open at the book's end. 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. In the Series Atlas, once two or more books have Foreshadowing results, the Books & order page lists each earlier book's setups that no later book pays off, matched by the setup's name. Setups you marked to carry forward, and setups in the final book, are left off that list.

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 where each was planted, and lets you mark the ones you are carrying forward on purpose, so you can tell the slow burn from the oversight.

Where it lives in StoryHelm

Within a book, thread coverage lives in two places. The first sits beside Plot DNA, which scores each scene for intensity and stakes when you import your manuscript and also tracks beats and filler ratio. On the same Pacing & Emotion page, the Thread Atlas maps where each named character, place, object, faction, and event appears, scene by scene, and flags one that builds up over several scenes and then disappears, or goes quiet for four or more scenes in a row. The second is the Foreshadowing page, which pairs each setup with its payoff within the book and lists the setups that never pay off, with the chapter where each was planted.

A Full read, the same pass that builds your Canon and runs the Coherence Guardian, also runs the Foreshadowing analysis, so continuity of fact and continuity of promise are checked together rather than in two separate read-throughs. You can also run Foreshadowing on its own from its page, on any plan, using credits. The Guardian asks whether your facts agree with themselves; coverage asks whether every thread you opened was eventually closed.