Written September 2026. Daggerheart Compatible.
The countdown is the thing a Daggerheart GM is actually tracking, and it is the thing most campaign tools have no place to put. A clock that advances toward something happening gives a scene a deadline nobody rolled for, which is how pressure builds across a session instead of inside a single exchange. Run them well and the table makes hard choices without you having to push. Run them badly and they become furniture the table has learned to ignore.
This page is about the practice rather than the procedure: how many to keep live, what to put in front of the players and what to keep to yourself, what should make one move, and the five specific ways a clock stops meaning anything.
Checks are remembered in this browser. Clear all checks
A good default: reach for a clock when you want the pressure to outlive the current exchange.
A roll resolves a moment. A clock holds a situation open across many of them, which is the whole point.
The practical effect at the table is that the party stops being able to solve everything in the order they prefer. A deadline they can see forces a choice about what not to do, and a choice about what not to do is where most of the good play at a Daggerheart table comes from. Without a clock, a group will reliably take the cautious, thorough option every time, because nothing is costing them anything while they deliberate.
It also gives you somewhere to put consequence that is not damage. A situation that got worse is often a better answer to a mixed result than a number going down, and a clock is the place that worsening becomes visible rather than a description the table forgets by next week.
One framing worth keeping: a quest is something the party is trying to do, and a countdown is something happening to them whether or not they engage with it. Tables that track a campaign purely as a list of open quests tend to lose the clocks, and with them most of the pressure.
What tends to work: writing the consequence down first, because that is what stops you softening it later.
A good default: two the table can hold in its head, one you are moving quietly in the background.
The reason the ceiling is low is not bookkeeping, it is decision-making. Two competing deadlines produce an argument about priorities, which is the thing you wanted. Five produce a shrug, because at five the table can no longer tell which one is the expensive one to ignore, so they stop weighing them at all.
Retiring a clock is a normal move and not an admission of anything. A threat the party comprehensively defused should come off the table, visibly, because watching a clock get removed is one of the few ways they find out their work mattered.
A good default: if the clock exists to make them hurry, it has to be where they can see it.
The question is not how secretive you feel. It is what the clock is for.
| Keep it visible when | Keep it hidden when |
|---|---|
| The pressure is the point. A visible clock is the reason the table stops debating and moves. | The players do not know the threat exists yet. A clock on the table is an announcement. |
| You want players spending resources. Nobody spends hard when they cannot see the deadline. | Knowing the exact number would flatten a mystery into arithmetic. |
| It measures something the characters could reasonably estimate: a fire spreading, a ritual building, a patrol returning. | It measures something the characters have no way to perceive, and showing it tells the players what their characters cannot know. |
| You want the table arguing about priorities. Two visible clocks do that better than any speech. | It is a slow background clock that would sit there for three sessions looking like nothing is happening. |
Revealing a hidden clock partway through is one of the strongest moves available, because the table learns the pressure was already real and already moving. The reverse, quietly taking a visible clock off the table when it is going badly for them, costs you the credibility of every clock after it.
A Daggerheart campaign's Live screen carries countdowns and the GM's Fear pool alongside the party's Evasion and damage thresholds, so the clocks sit on the same screen you are already running the table from rather than on a separate sheet. You move them yourself; nothing advances a clock on your behalf.
What the recording does handle is the part that usually goes missing: the session gets written up as a chapter afterwards, so the reason a clock moved is in the record instead of in your memory. That is the note the between-sessions habit above asks you to keep, and it is the one GMs most often skip.
What tends to work: advancing the clock instead of asking for a roll, when the outcome is not in doubt but the cost is.
The last two are the ones that separate a clock that feels like a world from a clock that feels like a scoreboard. If a clock only ever moves in response to something the players did at the table, it is measuring them. If it also moves while they are somewhere else, it is measuring the situation, which is what you wanted.
A good default: if the table has stopped reacting to a clock, one of these five is why.
Four of the five are recoverable by doing the opposite next session. The one that is not is the fourth: once a clock has completed and the table has seen the consequence come in soft, you cannot argue them back into taking the next one seriously. That is the one worth protecting by writing the consequence down before you start.
What tends to work: deciding which hidden clocks moved while the party was not looking, before the next session starts rather than during it.
The background clock is the one that needs deliberate attention, because nothing at the table will remind you it exists. A short habit that works: before each session, read the live clocks, decide whether the background one moved since last time, and write the reason it moved rather than just the new number. The reason is what you will need when a player asks how things got this bad.
It is also worth checking whether any clock has quietly become irrelevant. A situation the campaign has moved past should be retired rather than carried, and a clock carried out of habit is the most common cause of the second failure mode above.
A clock the GM runs that advances toward something happening: a threat arriving, a ritual finishing, a building coming down. It gives a scene a deadline that exists independently of any one roll, which is what lets pressure build across a whole session rather than inside a single exchange.
Most tables hold two live clocks and one slow background one. Beyond that the table stops tracking them individually and they stop creating decisions, which was the reason to run them.
It depends on what the clock is for. A clock that exists to make the table hurry has to be visible or it cannot do its job. A clock measuring something the characters could not perceive should stay hidden, because putting it on the table tells the players something their characters do not know. The table above splits the cases.
The most natural trigger is a roll that succeeds but brings a complication with it: the party got what they wanted and the situation still got worse. Time spent rather than effort spent is the second. The most underused is advancing it instead of calling for a roll at all, when the outcome is not in doubt but the cost is.
A quest is a thing the party is trying to do. A countdown is a thing happening to them whether or not they engage with it. Tracking a Daggerheart campaign as a list of quests tends to miss the clocks entirely, which is where most of the pressure at a Daggerheart table actually comes from.
Whatever you wrote down before you started it. The one rule worth holding to is not softening it at the moment of impact, because a consequence that lands smaller than advertised costs every other clock on the table its weight.
More: Daggerheart session zero · Threadfall for Daggerheart · what makes a good session recap · the campaign tracker template · all Threadfall guides
Daggerheart™ is a trademark of Critical Role, LLC. Threadfall is compatible with Daggerheart™ and is not affiliated with, endorsed by, or sponsored by Critical Role, LLC or Darrington Press.