Your Campaign Has a Ticking Clock. You Just Haven't Drawn It Yet.

A borrowed TTRPG technique for tracking offscreen threats and countdowns without relying on memory, and why "the ritual finishes eventually" is the sentence that gets GMs in trouble.

There's a specific kind of threat that never quite lands right: the cult working toward a ritual, the rival crew chasing the same prize, the town slowly running out of patience. It lives in your notes as pressure without a deadline. Then comes the session that needs a big beat, the ritual finishes right on cue, and the players clock it immediately, because it means nothing they did along the way actually mattered. The problem isn't that you forgot. It's that "eventually" was never a number.

The fix is one TTRPG design already solved, just not in the game most tables are playing. Blades in the Dark popularized progress clocks. You draw a circle, cut it into segments (four, six, or eight, depending on how complex or how close the threat is), and fill it in one bite at a time as things happen at the table. Nothing about it is specific to Blades' own rules. It's a GM bookkeeping trick you can run in any system, D&D included, because all it needs is a circle and a pen.

How the segments actually fill

The rule that matters is deciding how many segments something costs at the moment it costs them, rather than deciding in advance exactly when the clock finishes. A minor complication ticks one segment. A real setback ticks two or three. A full clock means the thing happens: the ritual completes, the rival crew gets there first, the town's patience runs out and the mob shows up at your door. You're not tracking a countdown of sessions. You're tracking a countdown of consequences, which means the players' own choices are what move the clock, not your session-count math.

A cult ritual is the obvious use: eight segments, ticking whenever the party chases the wrong lead or lets a cultist escape. The same trick covers a rival adventuring party racing you to the same dungeon, where two clocks run side by side and whoever fills first gets there. It covers a town's suspicion of a party that's been a little too effective at solving problems with violence. None of these need a full quest log. They need one circle and an honest answer to "did that cost them anything?"

Where the clock actually lives

A clock that lives only in your head has the exact same failure mode as "eventually." You'll forget to tick it for three sessions, then panic-fill it to make something happen on cue. The fix is the same one that works for every other GM tracking problem. It needs to live somewhere you'll actually open between sessions, not somewhere you're relying on memory to check. GameMasterCraft's campaign and faction notes are a fine home for it. Attach the clock to whichever faction or NPC owns the threat, tick it the same night the session ends while the consequence is still fresh, and it's waiting for you next time instead of getting reconstructed from memory a month later.

The real value of a clock isn't dread, even though that's the effect players usually feel. It's that the clock forces you to make a call in the moment, instead of freezing on "I'll figure out when this happens later" or overcorrecting by ending it exactly when the story wants a climax. A circle with three segments filled in is a promise you already made to yourself about how the world moves. The only job left is keeping it.

Your Campaign Has a Ticking Clock. You Just Haven't Drawn It Yet.