Direct answer
Build a list of setups, promises, mysteries, objects, relationship tensions, and world rules, then check whether each one has a payoff, an intentional deferral, or a clean removal before beta readers see the draft.
Why it matters
Beta readers can tell you a thread disappeared, but it is better to catch obvious dropped promises before they spend attention on them.
A simple way to handle it
- Collect visible promises from early and middle chapters.
- Mark each thread as paid off, deferred, revised, or removed.
- Ask grounded questions about any setup you cannot place.
Look for promises, not just subplots
A plot thread can be a mystery, a vow, a suspicious object, a political rule, a romantic obstacle, or a repeated image that begins to feel meaningful. If the reader is likely to expect a return, it belongs on the thread list.
LoreVia can help surface these patterns because the system is already reading characters, scenes, and recurring story material together.
Decide what each thread deserves
Not every thread needs a large payoff. Some need one sentence of closure. Some should be removed because the book no longer uses them. Others should be deliberately carried into the next book.
The important step is making the decision visible. A thread that is intentionally deferred feels different from one the author forgot.
- Pay off in this draft.
- Clarify as background texture.
- Remove the setup if it no longer serves the book.