Building Your First Countdown Clock: A Practical Guide for Game Masters

A countdown clock can be one of the smallest pieces of game prep you make, and many GMs find it one of the most useful. It is a way to represent a plan that is moving forward whether or not the players are watching. This guide is a practical walkthrough: how to build a clock from nothing, how to decide when it advances, how to write the consequences attached to it, and how to keep it fair.

If you want the underlying idea first, see the earlier articles in this week's series. This article assumes you have the general idea and want to sit down and make one.

What a Countdown Clock Actually Is

A countdown clock is a visible or private tracker that represents progress toward an event. Blades in the Dark, for example, describes its progress clock as a circle divided into segments. When a segment fills, something in the world changes. When the last segment fills, the event happens.

Segmented progress trackers appear in several games, most visibly Blades in the Dark, and many GMs have adapted the idea for other systems. It helps to be honest about the lineage rather than claim one inventor, and the idea of a threat that advances on its own is familiar from the long history of GM advice about keeping a world alive between scenes. For related thinking about prepping situations instead of fixed plots, see Alexander (2009), who argues against prepping a predetermined plot and in favor of preparing situations the players can act upon.

The key properties of a good clock are simple:

• It represents one specific thing, not a general mood.
• It has a defined number of segments.
• It has clear rules for when it advances.
• Each segment, or at least some segments, corresponds to something the players can notice.
• It can be slowed, stopped, or reversed by player action.

That last property matters most. A clock that cannot be stopped is a railroad with a timer on it. A clock that players can influence is a source of stakes.

Before You Draw Anything: Decide What the Clock Is For

A frequent stumbling block is starting with the drawing. Start with the question instead: what is moving, and who is moving it?

Write one sentence that fits this pattern:

[Someone or something] is working toward [a specific outcome], and if nobody interferes, it happens.

Examples of well-formed sentences:

• A merchant consortium is buying up a town's debts so it can seize the mills.
• A cult is gathering the three relics it needs to open the sealed vault.
• A besieging army is starving the keep and will force a surrender.

Examples of weak sentences:

• Bad things are happening in the region. (Too vague, no actor, no outcome.)
• The villain is evil. (A trait, not a plan.)
• The world is in danger. (Not specific enough to produce steps.)

If you cannot write the sentence, you do not yet have a clock. You have a vibe, and vibes are fine for atmosphere but cannot be advanced one segment at a time.

Step One: Choose the Size

Blades in the Dark uses 4-segment clocks for complex obstacles, 6 for more complicated ones, and 8 for daunting ones, though nothing prevents you from using other numbers. The right size depends on how long you want the threat to take and how many distinct beats you want to show the players.

No size standard applies across all games, though Blades in the Dark offers one (4, 6, or 8 segments by difficulty). Treat the following as table-craft guidance, not a rule:

• Four segments suit a fast threat, a single-session complication, or a plan with only a few clear stages.
• Six segments suit a medium-length threat that should take several sessions to resolve if players engage.
• Eight or more segments suit a slow campaign-level pressure, though very large clocks can become hard to track and tend to feel abstract.

A practical rule of thumb: pick the smallest number of segments that lets you describe a distinct, noticeable change at each one. If you find yourself writing segment descriptions that are nearly identical, the clock is too big. If you find yourself cramming two major events into one segment, it is too small.

Step Two: Write the Steps

Each segment should correspond to something that has actually happened in the fiction. This is what separates a clock from a vague countdown. Write the steps as events, in order, using concrete nouns.

Here is a template:

1. Segment 1: a quiet, early sign that something is wrong.
2. Segment 2: a visible consequence the players could discover.
3. Segment 3: an escalation that forces a reaction.
4. Final segment: the outcome the clock was counting toward.

Notice that the early segments are quiet. This is deliberate. If the first segment is already a disaster, there is no room for the players to notice, investigate, and respond before it is too late. Early segments are the part of the clock that rewards attention.

A useful test for each step: could a player discover this through play? If the answer is no, because the step happens entirely off-screen with no trace, it is not doing any work for the table. Either add a clue the players could find, or merge it with a step that does leave a trace. The three clue rule is a well-known piece of GM advice about making sure important information can be reached more than one way (Alexander, 2008), and the same instinct applies here: a step that leaves no discoverable evidence is a step the players cannot react to.

Step Three: Write the Triggers

The triggers are the rules for when the clock advances. This is where fairness lives, so it deserves the most care.

Three useful kinds of trigger are failure, time, and specific events, and many GMs combine them.

Trigger on failure. The clock advances when the players fail a relevant roll or action. For instance, a failed attempt to follow an agent unseen ticks the clock because the agent is now alerted.

Trigger on time. The clock advances when a set amount of time passes without the players acting on the threat. This might be a full session, a number of in-game days, or a number of scenes.

Trigger on a specific event. The clock advances when something particular occurs, such as a named character being killed or a location being reached.

Write triggers down before play, and be willing to tell the players the general shape of them. Players who understand that ignoring the problem will let it grow are making informed choices. Players who feel the clock is advancing at the GM's whim can reasonably suspect the game is rigged.

A few guidelines for trigger design:

• Prefer triggers the players can predict. "A full session passes without anyone looking into the debts" is predictable. "Whenever the GM feels like it" is not.
• Avoid triggering on every failure. If every missed roll in the campaign ticks the same clock, it will fill almost immediately and feel punitive. Tie it to rolls that are actually relevant to the threat.
• Include at least one way to slow or reverse it. If the only direction is forward, the clock is a doom meter, not a tool for play.

Step Four: Write the Counterplay

For every clock, write down at least two ways the players could interfere. This is not about forcing a solution. It is about making sure the clock is a problem the players can engage, not a countdown they can only watch.

Counterplay can look like:

• Removing a step (destroying a relic before the cult collects it).
• Winning back a segment (rallying the millers to pool their debts).
• Changing the trigger (securing the treasurer so bribery is no longer an option).
• Exposing the actor (making the threat public so its method stops working).

You do not need to decide in advance which counterplay will work. You only need to know that several options exist, so that when the players come up with their own approach, you are ready to say yes, and here is what that changes. This fits with a long-standing view in GM craft that good prep gives you material to respond to rather than a script to enforce (Alexander, 2009; Shea, 2023).

Step Five: Decide How Visible the Clock Is

Whether to show the players the clock is a matter of table preference, and both approaches have supporters.

A visible clock tells players that a threat exists and roughly how close it is. This turns the clock into an explicit pressure and lets players weigh trade-offs openly. It also reduces the chance that a player feels blindsided.

A hidden clock keeps the mystery intact and lets you reveal progress through fiction: a rumor, a changed landmark, a suspicious visitor. This tends to feel more organic but gives players less information to plan around.

One middle path some tables like: keep the clock hidden but announce its movement. When a segment fills, tell the players what changed in the world, without necessarily saying which clock it belongs to. They get the consequence and the information, and you keep the mechanism private.

Whichever you choose, discuss it with your group. Expectations about transparency and consequences are the kind of thing that fits naturally into a session zero conversation (Shea, 2021; Haeck, 2024).

Step Six: Set the Pace

A clock that fills too fast frustrates players. A clock that never moves is decoration. The pacing question is: how many segments should a typical session add if the players largely ignore the threat?

A reasonable starting assumption is one segment per session of neglect, but adjust to your table. If your sessions are short or infrequent, you might advance on a slower schedule. If your campaign moves quickly, you might advance faster. There is no single correct number.

Two helpful checks:

• The runway check. Count how many sessions the clock would take to fill if the players ignored it completely. Make sure that is a number you are comfortable with. If the answer is two sessions and you wanted a slow-burn threat, resize the clock.
• The attention check. If the players are actively working against the clock, it should advance more slowly or even retreat. If it fills at the same pace regardless of what they do, it is not responding to play.

For broader thinking about session and campaign rhythm, see Alexander (2013) on pacing, and Shea (2022) for practical suggestions on keeping a game moving.

A Worked Build, Start to Finish

Here is the whole process on a small scale, using a generic threat so you can see the steps in order.

The sentence: A smuggling ring is moving stolen relics through a harbor town and will bribe the harbormaster to look away permanently if nobody stops it.

Size: Four segments, because the plan has four distinct beats.

Steps:

1. A crate of relics is moved through the docks at night.
2. A dockworker who saw something goes missing.
3. The harbormaster is seen dining with strangers.
4. The harbormaster signs a standing order exempting the ring's ships from inspection.

Triggers:

• Advance one segment when the party fails a roll to investigate the docks.
• Advance one segment if a full session passes without anyone looking into the harbor.

Counterplay:

• Find the missing dockworker.
• Intercept a shipment.
• Expose or protect the harbormaster.

Visibility: Hidden, but each filled segment is announced through a change the players can notice.

That is about a dozen short lines of prep. It gives the harbor town a life of its own, creates several ready-made hooks, and leaves every outcome open.

Common Mistakes When Building Clocks

Making the clock a plot. If the clock leads to one pre-written scene that must happen, you have built a railroad with a progress bar. Keep the final segment as a change in the situation, not a mandatory cutscene.

Writing steps the players cannot perceive. Every segment should leave a trace somewhere in the world.

Running too many clocks at once. Each clock is something you must remember and advance. Start with one or two. A small number of active threats is usually easier to track and can give each one more weight, though this is a matter of how much you want to juggle.

Punishing players for doing other things. A clock is not a penalty for ignoring the GM's favorite storyline. The players are allowed to hunt wolves. The consequence is simply that the world moves while they do, and they decide whether that cost is acceptable.

Never letting the clock fill. If you always rescue the players at the last segment, the clock is theater. Part of what makes a countdown meaningful is that it can actually complete, and the story continues from that new reality. This is also a matter of table preference, and some groups prefer softer consequences, so agree on the approach in advance.

Forgetting to pay it off. When a segment fills, show it in the next scene. A clock that advances silently teaches players to ignore it.

Tracking Your Clocks

You do not need special tools. An index card per clock is enough, with the sentence, the steps, the triggers, and the counterplay written on it. Index-card prep is a familiar approach; Index Card RPG: Master Edition (Runehammer Games, 2022) even takes its name from it.

If you prefer digital tools, any note-taking app or campaign manager can hold the same information. The format matters less than being able to glance at it during play and update it in a few seconds. For a broader look at what is actually worth having at the table, see The Dungeon Trainer (2026), Essential Dungeon Master Tools: What You Actually Need at the Table.

Two habits help:

• Update the clock immediately when a trigger fires, not at the end of the session. It is easy to forget otherwise.
• Keep a short log of what each filled segment looked like in the fiction, so you can remind players of the thread next session.

Example: The Millbrook Reckoning

Here is an illustrative scenario showing the build in motion. It is a hypothetical, not a record of a real game.

A party arrives at the river town of Millbrook, where the mill owners' guild controls grain, and a quiet rival, the Ashen Ledger, wants to buy the guild out through debt. A Game Master wants to turn that idea into a clock, so they follow the steps above.

The sentence. The Ashen Ledger is lending coin to struggling millers so it can call the loans in all at once and seize the mills without a fight.

Size. The plan has four natural beats, so the Game Master draws a four-segment clock labeled with the Ledger's name.

Steps. Writing the steps as events, in order:

1. Miller Dovane takes a loan he cannot repay.
2. Two mills change hands quietly.
3. The guild's treasurer is bribed.
4. The loans are called in.

Each filled segment also needs a trace the players could find. The Game Master notes two: after the first segment fills, a mill has changed owners and the miller's family is in the street; at two of four segments, the treasurer is seen with unfamiliar company.

Triggers. The Game Master writes two. The clock advances when the party fails a roll to investigate the lending, or when a full session passes without anyone looking into the millers' debts. Both are predictable, and the Game Master mentions the general shape of them to the players when play begins, so the pressure is fair.

Counterplay. Before play, the Game Master jots three options without deciding which will work: protect the treasurer, expose the Ledger's agent, or rally the millers to pool their debts.

In the first session, the party hunts wolves in the hills and never touches the lending question. The full-session trigger fires, the first segment fills, and the Game Master shows it through the fiction: a mill has changed owners and the miller's family is in the street. The players notice and ask questions. In the second session, the party tracks the lender's agent but fails a roll to follow him unseen. The clock ticks again. The agent is alerted and more careful, and at two of four segments the treasurer is spotted with unfamiliar company.

Nothing here required a plot. It required one index card, a handful of lines, and a willingness to let the board change while the players were busy. The party is still free to intervene, and every option they take changes the clock instead of ending the story.

A Short Checklist

Before a clock goes into your campaign, run through these questions:

• Can I state the threat in one sentence with an actor, a method, and an outcome?
• Is the number of segments small enough that each one means something?
• Does each step leave a trace the players could find?
• Are the triggers written down and predictable?
• Is there at least one way for players to slow, stop, or reverse it?
• Have I decided how visible the clock is, and does my group agree?
• Do I know what the world looks like if it fills?

If the answer to all of them is yes, the clock is ready.

Where to Go From Here

Once you are comfortable with one clock, you can experiment: pair two clocks that interact, use a clock for a good thing the players want to build toward, or let a clock become public knowledge and see how the table responds. Treat each as an experiment and adjust based on what your group enjoys.

If you want a place to keep campaign information, character sheets, and notes organized alongside the people you play with, The Dungeon Trainer lets groups run campaigns with a human Game Master; AI support is optional. A clock on an index card works just as well.

Sources and Further Reading

• Alexander, J. (2008, May 8). The Three Clue Rule. The Alexandrian. https://thealexandrian.net/wordpress/1118/roleplaying-games/three-clue-rule
• Alexander, J. (2009, March 23). Don't Prep Plots. The Alexandrian. https://thealexandrian.net/wordpress/4147/roleplaying-games/dont-prep-plots
• Alexander, J. (2013). The Art of Pacing. The Alexandrian. https://thealexandrian.net/wordpress/31509/roleplaying-games/the-art-of-pacing
• Haeck, J. (2024, March 11). How to run a Session 0 for your D&D game. D&D Beyond. Original work published January 8, 2021.
• Runehammer Games. (2022). Index Card RPG: Master Edition. Runehammer Games.
• Shea, M. E. (2021, April 5). Running session zeros. Sly Flourish. https://slyflourish.com/runningsessionzeros.html
• Shea, M. E. (2022). Improving Pacing. Sly Flourish. https://slyflourish.com/pacing.html
• Shea, M. E. (2023, October 23). The Eight Steps of the Lazy DM: 2023 Review. Sly Flourish.
• The Dungeon Trainer. (2026). Essential Dungeon Master Tools: What You Actually Need at the Table. https://thedungeontrainer.com/blog/essential-dungeon-master-tools-what-you-actually-need-at-the-table