The main physical format is what I call situation reports. These are working documents with notes on motivations, goals, and plans for factions and NPCs. They serve as a memory aid and a projection of what would unfold if the PCs don’t interfere.
To illustrate this I will use my Nomar campaign set in the Majestic Wilderlands that I ran back in 2012. To provide some context here is the first campaign log I posted.
GURPS Majestic Wilderlands: Campaign Update #1
Here is the first part of what happened.
A Sandbox Campaign, the Nomar Campaign Part 1
The campaign started when the players decided they wanted to be a group of mercenaries. I listed the different places in the Majestic Wilderlands where mercenaries were being employed, and they opted to play in Nomar.
Some background on Nomar if you are interested
Noble Houses of Nomar.
Regional Map of Nomar
I attached the handout the players got to this post. Campaign Starter, Mercernary.
Next I started a local map. I never finished the polished version as the players moved elsewhere before I had it finished.
View attachment 402763
As well as a map of the main settlement
View attachment 402765
Next, I made a situation map. I like do these in poetic style as the graphics helps remember things.
View attachment 402764
There are important locations highlighted there. That I have notes on including who there, what resources there are. Goals, motivations, and plans.
The main set of notes look like this.
What will happens is periodically I will update the situation report above as the campaign unfolds. In the case of Abberset my notes got a minor update when the party returned to Abberset at this.
And after they left the region it didn't matter as I had to focus on the new area they headed too.
How the "Timeline" Emerges
I don’t write out a traditional “event-by-date” timeline in advance. Instead:
The situation report functions as a latent timeline, it describes what factions and NPCs will do if nothing changes.
As players act, I update the notes. New entries are added with in-world dates (e.g., “Portly Pomp 13th, 4460 BCCC”), reflecting what happened or shifted.
When the PCs left the region, I stopped updating it, just as a historian would stop writing a chronicle once the scene moves.
Example of a situation update.
This would be note in a program I use called the Keep by nBos. Or an entry in a notebook if it is a face to face session.
These entries are not scripts. They’re branches of potential action, modified by player intervention, oracles, or rolls.
Memory & Organization
A lot of this is “in my head,” but it's supported by:
- Maps
- Character writeups
- Spatial context
I’ve always linked events to geography, which helps me recall timelines like a mental gazetteer. This technique, which is a variant of the Palace of Memory technique, associates characters and events with geography.
This is why I recommend referees develop a method of organizing info that works for them. It must track people, their motivations, and events across time and geography in a coherent way.
Why I Don’t Use Clocks
I’m not against other folks using clocks. I don’t use them because, in my experience, chains of events don’t progress in neat, measured increments. Too many interconnected factors are in play in my campaigns, and clocks don’t capture those interconnections in a way that works for me.
From what I’ve read, clocks are great when you need visible escalation—they give structure to looming threats or timed developments. But they don’t work as well for causal branching that unfolds across geography or depends on multiple actors with conflicting goals.
So yes, my timelines exist, but they’re not segmented wheels. They’re conditional flows of action—embedded in geography and narrative—updated as the PCs interact with the world. The structure is procedural, just not tied to a particular format.
As for GM fiat, while I get that you're using it to mean "the GM making authorial decisions," I think two things need to be pointed out.
First, like "railroading," GM fiat is often used as a pejorative, even if unintentionally. It implies arbitrariness or unearned authority, and that colors how people receive it, especially when comparing styles.
Second, saying "the GM makes authorial decisions" is fine as far as it goes, but it often skips over how those decisions are made. And that’s critical. There’s a big difference between a referee who decides things on a whim and one who uses structured methods, goals, constraints, causal logic, oracles, even randomness, to shape outcomes. The process behind the decision is what defines the experience at the table, not just the fact that the GM made a call.