Track foreshadowing from plant to interpretation to payoff

Phrase the thread as an expectation, not an object

A note called the red scarf does not explain what the detail promises. Name the underlying question or return: why the witness misidentified the runner, how the scarf moves between characters, or when its color will expose the lie. One prop can support several threads, and each should have its own payoff logic.

Record what a first-time reader can reasonably infer at the setup scene. Effective foreshadowing is present and fair, but it often carries a plausible immediate purpose that prevents it from flashing like an answer key.

• Exact setup scene and the visible detail placed there
• Reader and character interpretations available at that point
• Development scenes that reinforce, redirect, or complicate meaning
• Payoff scene and the consequence the earlier plant enables

Read the isolated sequence at two levels

First, read only the setup, development, and payoff scenes. The chain should be logically sufficient: the ending cannot depend on evidence that never appeared. Then read the setup in full context and ask whether it feels unnaturally emphasized or whether another scene function gives it cover.

Spacing matters less than continued pressure. A plant can wait many chapters if related questions evolve; repeated reminders that add nothing make the machinery obvious and slow the story.

Re-audit after every structural edit

Moving a reveal can place it before its plant. Cutting a quiet scene can remove the only fair clue. Changing viewpoint can expose information that was formerly hidden. Review all attached threads whenever a scene moves, combines, or disappears.

Novelbound stores foreshadowing as a setup-development-payoff thread linked to the manuscript scenes. Unresolved setups remain visible, and the connection makes it possible to inspect the full chain without searching through notes and prose by hand.