Reveal your world’s lore without info-dumping

Forty years ago, someone lowered a harbor chain at night and the lower town burned. You know who gave the order, why the official story blames someone else, and what the town has done every night since. The reader knows none of it, and the pull is to explain all of it before the first conversation ends.

The examples follow an invented harbor town, Vell, and three people in it: Ilsa, an apprentice chain-keeper from inland; Dorran, the senior keeper; and Hesk, a fishing captain whose boat arrives after the chain is up. The method is editorial advice for drafting and revision. Some stories open with history on purpose, and a later section covers when that works.

Sort what you know by when the reader needs it#

List every piece of history and every rule the story touches, then sort each into three groups: needed for the next scene, needed later, and needed only by you. Most of your notes belong in the third group. That is not wasted work. It keeps characters’ behavior consistent even when the reader never sees the reason. If you have not decided those facts yet, worldbuilding questions is a way to settle the ones the next scene will use.

For Vell:

• Next scene: the chain rises at the third bell after sunset and stays up until dawn.
• Later: the night forty years ago that locals call the Burning, and the fact that the keeper on duty, Dorran’s mother Aud, took the blame.
• Only you: how the harbor was founded, the trade treaties, the name of the raiders’ ship.

“Needed” means the scene stops making sense without it. Ilsa can turn the crank without knowing about the Burning. The reader cannot understand why Dorran refuses a sinking boat without at least a hint of it. So the Burning first appears on the night Hesk arrives, not on the opening page.

Give every fact a job in the scene#

A piece of lore earns its place when it does at least one of three things: complicates a choice, starts a disagreement, or raises a question the reader wants answered. “The chain has risen every night for forty years” does none of these on its own. “Dorran will not lower it, even for a boat taking on water” does all three.

Test each paragraph of explanation by deleting it. If the scene still works, the fact was decoration: move it to a scene where it has a job, or leave it in your notes. If the scene breaks, the fact belongs, but ask whether it needs a paragraph or a clause. A rule that will decide the climax needs earlier evidence on the page; building a magic system covers how much of a magical rule the reader should understand before it matters.

Choose who tells it, and why now#

Explanation sounds natural when a character has a reason to say it to this listener at this moment. People rarely tell each other what both already know, so “As you know, the chain rises at the third bell” rings false between two keepers. The same rule sounds right when Dorran says it to Ilsa on her first night, because she does not know it and he needs her to obey it.

Teaching, persuading, accusing, defending and warning are all good reasons to explain, and each shapes what the speaker includes. Dorran warns Ilsa with the rule and none of the history. Hesk, shouting from the water, accuses the town with the history and none of the nuance: “You’d drown us over one bad night forty years gone?” Two partial versions, both in character, and the reader has assembled the outline without a lecture.

A newcomer like Ilsa gives others a reason to explain, but she should not become a machine for questions. Let her guess, get things wrong, and stay quiet when asking would embarrass her. To keep track of who believes which version of an event, the timeline guide separates what happened from what people were told.

Let objects, customs and arguments carry it#

Dialogue is one channel among several. Lore also surfaces in what people own, repeat and fight about, and each channel suits different material:

In Vell, the custom is the third bell and the crank. The object is a bricked-up window in the keepers’ house, where Aud’s name was once carved into the frame. The argument is Hesk’s accusation. The rumor is a children’s rhyme about the keeper who “opened the door for the fire”. None of them explains the Burning, and together they make the reader want the explanation.

Follow the chain through three chapters#

Here is how the reveals might fall across the opening of a novel set in Vell. The third column is what the reader can infer, not what anyone states.

Notice what chapter 2 leaves out: the year, the raiders’ flag, the trial. Hesk does not know those details, and Dorran will not say them. The reader’s question, “What did the keeper do?”, carries the story into chapter 3.

The truth, that the harbor master ordered the chain lowered and let Aud take the blame, waits until it changes a choice. Perhaps on a later night the same office orders Ilsa to lower the chain for a ship it will not name. Dorran tells her then, because the history is now a warning she needs, and the reveal lands as a turn in the plot rather than a footnote.

When a longer explanation works#

Not every block of history is a mistake. A longer telling can hold when the reader is already asking the question, when the teller has something at stake in telling it, and when the listener’s reaction changes something. Dorran’s confession can run a full page: he has kept the secret for half his life, Ilsa can act on it, and both of them know what saying it costs.

Keep such passages anchored. Start inside the scene, let the listener interrupt or doubt, and end on a consequence rather than a summary. A prologue that recounts the Burning before we have met anyone in Vell asks the reader to care about events before they care about people. If you keep one, write it as a scene with its own tension, and keep it short.

Info-dump patterns and how to fix them#

The front-loaded first chapter#

The opening explains the harbor, the curfew and the war before anything happens. Start with the action the most important rule complicates, and cut everything Ilsa does not need to get through her first night.

The convenient expert#

One character exists to answer questions. Spread knowledge across people who each know part of the story and get some of it wrong. The rhyme, Hesk and Dorran each hold a different piece.

The pause at the peak#

The boat is sinking, and the narration stops for three paragraphs of harbor history. Give the fact in a clause during the crisis and the explanation afterwards, when someone has time to ask what just happened.

The repeated reveal#

The same fact arrives in chapter 2 and again in chapter 5, just in case. Reminders are fine, but attach something new to each one. When the Burning comes up again, let it bring the rhyme or Aud’s name with it.

Adjust for point of view and length#

Point of view sets what can be revealed and how. A close narrator can deliver only what the character knows, and only when she would think of it. Ilsa can wonder about the bricked-up window; she cannot explain it. If Dorran narrates, he knows everything and would avoid thinking about the worst of it. That avoidance is honest and builds suspense, as long as the reader can see him steering away. An omniscient narrator can summarize history directly, which saves space, but the summary needs a voice and an attitude or it reads like a report. Locals and outsiders also notice different things; the culture guide covers what each viewpoint tends to see.

Length decides how much can reach the page at all. A short story set in Vell needs the rule and a hint of the Burning; the truth about the order may never appear, and the story can still feel complete. A novel can plan three or four major reveals and spread the smaller ones between them. In a series, keep a record of which facts each book has put on the page. Returning readers need a light reminder, new readers need enough to follow, and one well-placed clause can serve both.

Track what the reader has seen in Yazar.io#

Yazar.io suits a reveal plan well. Give each piece of history or rule its own entry in the Lore section, then keep a note for each reveal and move it through the statuses: Idea while it exists only in your plan, In Progress while you draft the scene that carries it, Used once it is on the page, To Review when a revision moves it (features). Type Dorran’s name in the Burning’s entry and the two link themselves, so when you write his next conversation, his backlink panel lists every piece of lore that mentions him.

Your chapters stay in Word or Google Docs, outside Yazar.io, so a status is only as accurate as your last update. When you move the confession to a later chapter, change its note in the same sitting.

Update, 21 October 2026: Added a link to the worldbuilding questions checklist.