Foreshadowing in Writing: How to Plant It and Pay It Off

Foreshadowing in writing is a hint, planted early, about something that happens later. It works when the reader either half notices it and feels the dread build, or misses it and recognizes it at the payoff. Either way, the hint has to be paid off, deliberately misdirect, or come out.

To foreshadow well, plant fewer hints than you think you need, make each one do a second job in its scene, and check every one in revision. The common failure is not a hint that is too obvious. It is a setup the book forgets to pay off.

StoryWith AI is our own product, so weigh what we say about it accordingly.

Key takeaways

• Foreshadowing is a promise. Each hint tells the reader "this will matter." Keep it, break it on purpose, or cut it.
• Chekhov's gun is the rule of thumb. Chekhov wrote in 1889 that a loaded rifle should not go on stage if no one means to fire it.
• A red herring is a planned misdirection, not a dropped setup. It still needs an answer, even a quiet one, if readers will feel owed one.
• Plant in revision. Once the payoff exists, you know what to set up.
• Audit with a two-column ledger: every setup on the left, its payoff scene on the right. Blanks on the right are your list.

What is foreshadowing in writing?

Reedsy defines it this way: "Foreshadowing is a literary device where authors plant hints about future events, creating anticipation and preparing readers for what's to come." (Savannah Cordova, Reedsy, "What is Foreshadowing? Definition, Tips, and Examples", page shows "Last updated on Oct 15, 2025"; read on 4 November 2026.)

The same article splits it in two. "Direct foreshadowing gives readers explicit hints about future events," such as prophecies or narrator statements. "Indirect foreshadowing uses subtle clues through symbolism, weather, or seemingly innocent details that only become significant in hindsight."

In a novel, think of it as setup and payoff. The setup is the line, object, habit or warning you plant. The payoff is the scene where it comes back and matters.

What are the kinds of foreshadowing?

Knowing which kind of hint you are using tells you how loud it can be and what the payoff owes the reader.

A prologue is often one long piece of direct foreshadowing: it shows a later moment so the reader reads the opening chapters waiting for it.

What is Chekhov's gun, and what did Chekhov actually say?

The rule is usually quoted as "if there is a gun on the wall in act one, it must go off by act three." Chekhov's own wording was plainer.

In a letter to the writer Aleksandr Lazarev (the pen name of A. S. Gruzinsky) dated 1 November 1889, Chekhov wrote: "One must not put a loaded rifle on the stage if no one is thinking of firing it." The Isaiah Berlin Virtual Library at Wolfson College, Oxford, gives that translation with the Russian collected-works reference, and also records a fuller version from S. Shchukin's memoirs (1911): "If you say in the first chapter that there is a rifle hanging on the wall, in the second or third chapter it absolutely must go off. If it's not going to be fired, it shouldn't be hanging there." (Isaiah Berlin Virtual Library, "Quotations cited by Isaiah Berlin", page shows "Last updated 15 August 2026"; read on 4 November 2026.)

The rule is about attention, not weapons. Reedsy puts it as: "if you draw a reader's attention to something, you must eventually explain why it was worth noticing." A detail you spotlight is a promise.

Chekhov did not always follow it. Wikipedia's entry notes that Donald Rayfield pointed out two loaded firearms in The Cherry Orchard that are never fired, and ties them to the play's theme of incomplete action (Wikipedia, "Chekhov's gun", no date shown; read on 4 November 2026). An unfired gun can be the point, as long as it is the point on purpose.

How do you plant foreshadowing without giving the ending away?

Steve Hooley at The Kill Zone, summarizing Jodie Renner's 2014 post "Fire Up Your Fiction with Foreshadowing", gives a good rule for quantity: "Use like a strong spice," not too much and not too little (Steve Hooley, The Kill Zone, "Foreshadowing: A Look Back and a Look Forward", dated 23 April 2022). The summary also gives the reason it matters: "Keep your reader curious and worried, and keep them turning pages." In practice:

1. Give every hint a cover job. The key on the hook also tells us the house is old. A hint that only hints is easy to spot.
2. Plant early, pay late, keep the gap. A hint two pages before its payoff is a spoiler. One placed several chapters earlier is a reward.
3. Plant it twice if it carries the climax, in different contexts, so it is remembered without a spotlight.
4. Put the hint where the reader is looking elsewhere, such as the middle of an argument or the end of a list.
5. Write the payoff first. The summary's advice for writers who do not outline is direct: "write the story then add the foreshadowing." Once you know what the climax needs, you know what to plant.

What is the difference between a red herring and a dropped setup?

Both look like a clue that did not lead anywhere. The difference is intent and resolution.

A red herring is planned. Reedsy calls red herrings "deliberate false clues that mislead readers, especially in mystery and detective stories." A dropped setup is an accident: something you spotlighted in an early draft and forgot, or a payoff you cut in revision while the setup stayed.

Kathryn Lilley's advice, collected by Dale Ivan Smith at The Kill Zone, is that red herrings still have to earn their place: "All clues, including red herrings, must serve to move your story forward." She adds: "Red herrings shouldn't scream, 'Hey, I'm a clue!' from the rooftops." (Dale Ivan Smith, The Kill Zone, "Red Herrings, Foreshadows and Creating a Mystery", dated 26 August 2023.)

Not every red herring needs a full explanation. Kris Calvin, writing for Writer's Digest, separates the ones readers will feel owed (a suspect seen fleeing the scene with a gun) from the ones they will let go (a passing remark about where someone was on Thursday). She warns: "When I first started writing mysteries and thrillers I thought all loops had to be closed and all false clues explained, which led to a bloated 'whodunnit' scene at the end." (Kris Calvin, Writer's Digest, "Planting Clues: Red Herrings That Fool but Don't Frustrate Your Readers", dated 15 April 2021.)

The test: if you spotlighted it, the reader feels owed an answer.

How do you audit a draft for setups that never pay off?

Do this on a finished draft, before line editing. It is the ledger from step three of how to analyze your novel's structure, done with foreshadowing in mind.

1. List every setup. Every object, skill, warning, secret or promise the text puts weight on, with its scene.
2. Find each payoff. For each setup, write the scene where it comes back and matters. If you cannot name one, leave it blank.
3. Check the reverse. List every big moment in the last third (a rescue, a reveal, a skill used under pressure) and confirm something earlier set it up. A payoff with no setup feels like a cheat.
4. Sort the blanks. Each blank is one of three things: a red herring you meant (check it resolves or can be let go), a deliberate open thread (fine, if it is one or two and on purpose), or a dropped setup (fix it).
5. Fix in one of three ways. Pay it off, cut the setup, or turn down the spotlight so it reads as background.

A setup with no payoff is the "broken contract" kind of plot hole in how to find plot holes in your novel, and a list shows it far better than a reread.

What does a plant, payoff and risk audit look like?

A hypothetical example, invented for this guide: a thriller where a hydrologist, Ines, is trapped in a flooding dam tunnel in the climax.

Seven rows, six changes, and at most two of them are cuts. The audit finds payoffs you forgot to earn as often as setups you forgot to pay.

Where StoryWith AI fits

StoryWith AI does not write foreshadowing for you. What it has is a Dependency Map, under Diagnostics, which tracks what your manuscript introduces early and where it comes back later.

When you press "Sync with manuscript", an AI model reads your draft and proposes dependencies of five kinds: setup and payoff, clue and reveal, promise, foreshadow, and callback. Each item has a short label, a one-sentence description, the setup scene, the scene it thinks pays it off (or none), and a confidence level of low, medium or high. You see the proposals first and untick anything you don't want before applying them.

Items with a payoff scene are filed as fulfilled, and items without one as pending. You can pick or change the payoff scene yourself, mark a setup broken when the story drops it, or add one by hand. Items you added yourself stay when you sync again. Changes you made to AI-found items, such as marking one broken, are reset by a new sync. It answers in the book's language.

The limits matter for this job:

• It proposes, you judge. A payoff scene is the model's guess. Low-confidence items are worth checking first, and a pending item may be a red herring you meant.
• At most 25 items per sync, chosen by the model as the highest-stakes. A book with more setups than that will have some the map does not list.
• It reads openings, not whole scenes. For each scene it reads the summary and roughly the first 1,800 characters of text, and the scene text sent is capped at 80,000 characters in total. A payoff late in a long scene, or scenes late in a long book, can be missed, so an item can show as pending when the payoff is there.
• It needs at least two scenes, and each sync uses one AI text action.

The Continuity page is the companion check: it tracks the facts your manuscript asserts and flags two that contradict each other across scenes.

When it is the wrong tool: if you want help inventing foreshadowing, it only maps what you already wrote. If your book is long and every setup must be checked, do the ledger by hand, or use the map as a first pass and read the last third yourself. The Author plan lists "Full continuity, coverage, and dependencies scans"; what each plan includes is on the pricing page. Manuscripts are not used to train AI models. StoryWith AI runs in the browser and as an Android app; the site lists no iOS app.

Frequently Asked Questions (FAQ)

What is foreshadowing in writing?

Foreshadowing is a hint planted early in a story about something that happens later. It can be direct, like a narrator saying a character will not return, or indirect, like an object or line of dialogue that only matters in hindsight. In a novel it is the setup half of setup and payoff.

What is an example of foreshadowing?

A hypothetical one: in chapter two a character refuses to swim at a party, and in the climax she has to swim a flooded tunnel to escape. The early scene makes the climax harder for her and more earned for the reader. Chekhov's gun, a weapon shown early and fired later, is the classic version.

What is Chekhov's gun?

Chekhov's gun is the principle that a detail the story puts weight on should matter later. In a letter dated 1 November 1889, Chekhov wrote: "One must not put a loaded rifle on the stage if no one is thinking of firing it." It is about attention, not objects: background detail can stay background, but a spotlighted detail is a promise.

What is the difference between foreshadowing and a red herring?

Foreshadowing points toward something that will happen. A red herring is a deliberate false clue that points the wrong way, mostly used in mysteries. Both are setups. A red herring still has to serve the story, and if readers will feel owed an explanation, it needs one.

How do I find setups that never pay off?

Make a two-column list. On the left, every setup the text puts weight on, with its scene. On the right, the scene where it pays off. Every blank on the right is either a red herring you meant, a deliberate open thread, or a dropped setup to fix. Then check the reverse: every big late moment should have something earlier that set it up.