Session 8 · Day 31
The bell answers from the empty tower
- What changed
- The tower rang after forty silent years.
- Who / where
- Ilyra, Orin · Drowned Chapel
- What it set in motion
- Something beneath the chapel now knows the party is there.
D&D campaign timeline template
Build a readable history of what actually changed during the campaign—decisions, discoveries, consequences, and threads that still have somewhere to go.
This is a campaign chronology. Future deadlines and fantasy holidays belong in a calendar; scene-by-scene detail belongs in session notes.
Worked campaign chronology
Select an event to follow its consequence.
What changed
The party proves the harbour office has been selling routes to smugglers.
What it set in motion
Blackwake recruits inside the watch.
The compression pass
Raw session account
The party reached Mireport, asked three dockworkers about missing boats, followed a clerk, argued at the harbour office, searched the ledgers, and accused the harbourmaster.
One lasting event
Day 18 — The party exposed the harbourmaster.
Smugglers lose port access. Blackwake begins recruiting inside the watch.
A template worth taking
Add the optional links and private context only when they help you find or run the event later.
Session 8 · Day 31
The campaign history in Multiloop
Timeline lives inside World. The same events can be read as Feed, Chapters, Journal, Browser, or Storyboard, with structured links back to sessions, locations, and characters.
Chapter II · Beneath Mireport
The party proves the harbour office has been selling routes to smugglers.
The party trusts Mara and leaves Factor Madric's offer unanswered.
Mireport's ferrymen agree to move the party beyond the flooded road.
This worked example uses the Timeline record. DM Notes remain private; suggestions from Analysis require review before new events are created.
Timeline inside World
World Timeline adds Feed, Chapters, Journal, Browser, and Storyboard views, with structured links to sessions, locations, characters, eras, and private DM Notes.
A free Multiloop account and campaign are required. Events from this guide must still be added deliberately.
Keep it simple while one person can maintain a short chronology. A connected timeline becomes useful when events need chapters, different views, private context, and links to the people, places, and sessions around them.
Planning a campaign timeline
Record changes that will matter later: decisions, revelations, arrivals, departures, victories, losses, and consequences. Routine travel and scene-by-scene action usually belong in session notes instead.
Use whichever you can maintain. Session numbers are dependable; an in-world date is useful when time itself affects play. You can keep both without inventing a full calendar.
No. This template is a history of changes that happened. A calendar or schedule is better for future deadlines, holidays, travel time, and hidden upcoming events.
A chronology with campaign context