Exposition Craft
Agents with full worldbuilding files are prone to dumping them onto the page. This reference is the guardrail: how to deliver necessary information without stopping the story.
The info-dump warning
If a passage exists only to transfer information from the worldbuilding files to the reader, it is an info dump. Test each expository passage:
- Cut test: if you cut the passage, does the scene's action still make sense? If yes, the information belongs somewhere else — or nowhere.
- Knowledge test: does the POV character have a scene reason to think or say this right now? "Because the reader needs it" is not a reason.
Drip-feed
Deliver background information in the smallest useful piece, at the latest possible moment:
- The reader needs the consequence now and the explanation later. Show the sealed gate first; explain the treaty that sealed it three chapters later, when the treaty breaks.
- One new world fact per scene is plenty. Two is crowded. A paragraph of history is a crowd.
- When in doubt, delay: an unexplained detail the reader files away is
foreshadowing; an explained one is exposition. Track planned delayed
reveals in
continuity/questions/so they don't become forgotten setups.
Exposition carried by conflict
Information the characters argue about gets absorbed; information they lecture about gets skipped. Delivery vehicles that carry conflict:
- An argument about the facts — two characters with different stakes disputing what happened (and both may be partly wrong).
- A test or interrogation — the POV character needs the information to survive the scene, not just to know it.
- Withheld leverage — a character who knows something uses it as currency; the exposition arrives when they finally spend it.
Conversely: never deliver exposition as a cooperative lecture between two characters who both already know it ("As you know, Bob..."). If both parties know it, they have no scene reason to say it.
In-world documents as delivery vehicles
When a chunk of information must arrive intact, embed it in a world artifact rather than narration:
- Letters, orders, decrees, newspaper articles, lab reports, contracts, diary entries, inscriptions.
- The document must have a scene reason to exist: someone delivers it, finds it, steals it, or forges it. A document that appears only to inform the reader is narration wearing a costume.
- Keep it short. A three-sentence decree beats a page of minutes.
- For gameable depth: documents can lie, omit, or be misread — the gap
between the document and the truth is a planned
continuity/questions/entry.
Pre-draft exposition audit
For each scene's planned exposition, record in the outline:
- The fact to deliver (one line).
- Why the POV character encounters it now (scene reason).
- Whether it's drip-fed, conflict-carried, or document-delivered.
- If it's a delayed explanation, the question id it was planted under.
A scene whose only answer to (2) is "the reader needs to know" gets its exposition cut or rescheduled.