Shared prep time pool: why most debate timers get it wrong
TL;DR
In Lincoln-Douglas, Policy, and Public Forum, prep time is a pool — each side (or each team) draws from a single allocation across the entire round. Most mobile timers treat it as a per-speech countdown, which doesn't match how the format actually works and puts the tracking burden on the judge. Tracking it properly takes a timer that stops and resumes the pool, not one that resets on every speech.
If you've ever judged a Lincoln-Douglas round and found yourself whispering "that's about 45 seconds" into a phone timer while a debater flips through flow sheets, you already know the problem. The prep in LD isn't a countdown that starts over at each speech. It's a single 4-minute pool per debater that carries forward through the whole round. The affirmative might take 15 seconds before the 1AR, two full minutes before the 2AR, and the math has to balance by the end.
That's hard to do on the fly. And most of the tools built for debate timing don't help — they present prep as yet another countdown with a start and stop button, but they don't retain state between speeches. So judges end up tracking it manually, on paper, or in their head, which is exactly what the timer was supposed to prevent.
What a prep pool actually is
A prep pool is a single allocation of prep time that a debater (LD) or team (Policy, PF) can use across the entire round, at their discretion. It's called "shared" for two reasons:
- Shared across speeches — the pool doesn't reset per speech. Time saved early is available later.
- Shared across partners (in Policy and PF only) — either debater on a team can request prep from the same pool.
The standard amounts under NSDA rules as of the 2025-26 season:
- Lincoln-Douglas: 4 minutes per debater
- Policy (CX): 8 minutes per team
- Public Forum: 3 minutes per team
- Parliamentary: no in-round prep (pre-round only)
Each of those numbers is a ceiling, not a per-speech allotment. The debater decides how to spend it.
Why per-speech timers fail
A per-speech timer looks like this: countdown to zero, then reset. When prep starts, the display shows a 4:00 countdown. When the debater stops prep, the timer resets to 4:00 for the next speech. The judge has to remember that "actually they already used 1:15 before the 1AR, so we only have 2:45 left" — and hold that number in their head, round after round, through an entire day of judging.
The consequences show up predictably:
- Overage by accident. A debater takes 2 minutes before a rebuttal that should have used their last 45 seconds. Neither the judge nor the debater noticed.
- Conservative play. Good debaters under-use their pool to avoid running out, which wastes a competitive resource.
- Disputes at the ballot. Post-round, someone checks the math and finds the prep arithmetic doesn't add up. The judge has to adjudicate something they were supposed to have tracked in real time.
None of this is the debater's fault. They're running a debate. The timer is supposed to track the pool.
What a pool-aware timer does differently
A timer that understands pool-based prep does three things a countdown timer doesn't:
1. It persists pool state across speeches
When prep stops, the remaining time saves. When prep resumes, it picks up where it left off. The display for the affirmative debater might read 3:17 at the start of the round, 2:45 after some pre-1AR prep, and 0:58 by the final focus — one continuous accounting.
2. It auto-pauses active prep when a speech starts
This sounds obvious but most timers don't do it. When the 1NC begins, any active prep from the negative needs to stop automatically. Otherwise the pool drains while the debater is already speaking. A pool-aware timer does the bookkeeping: speech running → prep paused → prep pool saves its remaining time.
3. It surfaces the pool on the debater's display
The debater needs to know how much they have left without asking the judge mid-round. A proper setup shows the pool on whatever screen the debater is already watching — their laptop, their tablet — with the remaining time visible at a glance.
Tracking manually vs. tracking automatically
The workaround most judges use is a physical stopwatch plus a piece of flow paper with "Aff prep used" and "Neg prep used" columns. Tick marks after each use. It works. It also splits the judge's attention at the exact moments they need to be listening hardest — usually right before a rebuttal, when the debater is signaling "I'm taking prep" and the judge has two hands full of notes.
Automating it is the higher-leverage move. If the timer does the pool math, the judge can give the actual content of the debate their full attention. That's the job.
How DebateClock handles it
This is the feature DebateClock was built around. Each format's prep pool is preloaded — 4 minutes per debater in LD, 8 minutes per team in Policy, 3 minutes per team in PF, none in Parliamentary. The judge taps Start Prep — Aff or Start Prep — Neg when a debater requests it. The pool counts down on both the judge's phone and the debater's display. Tap again to stop; remaining time saves.
The two behaviors that matter most:
- Auto-pause on speech start. Hit Start on the next speech and any active prep stops itself. No double-drain.
- Pool persists across speeches. The pool state follows the round. When the aff has 58 seconds left going into the 2AR, that's what the display shows.
It works on any device the judge already has — phone, laptop, tablet — and the debater sees a full-screen countdown on a separate device, synchronized in real time. No signup, no install.
Try a pool-aware timer for your next round
Free forever. No signup. Opens in any browser.
A quick FAQ
What happens if a debater runs out of prep?
Most formats don't allow further prep once the pool is exhausted — the debater has to proceed without it. DebateClock disables the prep button when the pool hits zero, so there's no ambiguity.
Can the judge add time back if they made an accounting mistake?
Yes. The prep reset button restores the full pool for both sides. The speech timer has +30s and -30s buttons for adjusting on the fly, and prep can be started and stopped manually to fine-tune consumption.
What about flex-prep and other variants?
DebateClock uses the standard NSDA allocations as defaults (4 / 8 / 3 minutes). For flex-prep or local variants with different pools, the judge can use the same start/stop/reset controls — the underlying pool logic doesn't care about the number. Future versions will include a format editor for leagues running non-standard timings.
Does this work if I only have one device?
Yes. The same interface runs as a single-device timer, too. The debater can watch the same screen as the judge, or the judge can tilt the screen toward them before each speech. Two-device sync is the recommended setup but it's optional.