Room operations · no attendee data
Coordinate one room plan across the presentation, in-slot Q&A, and protected turnover. The event brief remains authoritative; every planning template is editable.
These are editable arithmetic templates, not universal conference formats. Replace them with the latest run of show, speaker guide, or chair instruction.
Presentation remaining
Ready — 20:00 presentation, 5:00 Q&A, and 5:00 turnover
“Move now” discards unused phase time and brings the remaining plan and finish forward. Keyboard: Space start/pause · N save · R reset · F fullscreen
Configured boundaries stay fixed unless “move now” deliberately fast-forwards to one.
Total 30:00
Speaker content, demonstrations, and the final sentence must finish before the question reserve.
Moderated audience questions inside the same total slot.
Applause, exit, audience movement, and the next technical setup.
Only numbered runs and timing values stay in this tab; no event, attendee, speaker, topic, or question is collected.
Run or simulate a session, then choose “Save session & reset” to compare another room setup.
The whole room owns the clock
A speaker may think in terms of a 20-minute talk. The room chair may be responsible for a 30-minute cycle: introduction and talk, audience questions, applause, exit, audience movement, and the next technical setup. When the presentation consumes the reserve, the cost moves downstream to the next speaker, captioner, technician, volunteer, and attendee.
This timer keeps those obligations on one room schedule. It counts down the current phase while also showing the total room time remaining. At the talk boundary it changes to Q&A; at the question boundary it changes to turnover; after the hard finish it shows visible overtime instead of silently stopping.
Current examples, not defaults
Current 2026 organizer pages show why a single fixed “conference timer” would be misleading. The same programme can contain regular talks, keynotes, panels, and multi-paper sessions with different timing ownership. Each source below belongs to its named event; your current run of show can override a general presenter page.
| Published example | Total or format | Operational allocation | Source |
|---|---|---|---|
| PyCon US 2026 | Usually 30 or 45 minutes | Most talks are 30 minutes, with a limited number of 45-minute slots. The event groups consecutive talks by topic and room. | Organizer source ↗ |
| EuroPython 2026 | Typically 30 or 45 minutes | The event says many talks include Q&A and separately describes its typical 45-minute keynotes. | Organizer source ↗ |
| AZ Water 2026 | 30-minute room cycle | The moderator instructions specify 20 minutes speaking, 5 minutes Q&A, and 5 minutes changeover to the next speaker. | Organizer source ↗ |
| ASPA 2026 | Up to 75 minutes | Concurrent sessions may be adjusted by staff and many incorporate Q&A. The moderator manages equitable time, engagement, the start, and the finish. | Organizer source ↗ |
| SECAC 2026 | Typically 105 minutes | Published examples combine four or five 15–20 minute presentations with the remaining time for introductions, transitions, and Q&A. | Organizer source ↗ |
Room-slot arithmetic
AZ Water’s current moderator instructions provide a particularly clear example: 20 minutes of speaking, 5 minutes of Q&A, and 5 minutes of changeover. That is a 30-minute room cycle, not a 30-minute speech followed by questions. The default setup mirrors that published arithmetic so the phases are easy to inspect; it is not a recommended default for another event.
For another format, start with the total scheduled interval. Subtract protected changeover and any questions that occur inside the slot. What remains is the maximum presentation budget, including its opening, demonstrations, pauses, and final sentence.
30:00
Total room cycle
− 5:00
In-slot Q&A
− 5:00
Protected changeover
= 20:00
Presentation ceiling
Three-pass operation
A room plan is only useful when the handoffs work under event conditions. Test the same introduction, signals, microphones, slide handover, and exit path that staff will use. Do not collect session content in the timer; keep any names or accessibility notes in the organizer’s approved system.
Confirm the scheduled start and finish, then subtract any Q&A and room-change reserve from the total. Ask the organizer which number is a hard boundary before sharing the setup.
Simulate the introduction, final slide, first audience question, last answer, applause, exit, and next laptop or room change. Adjust reserves before the event, not during a crowded session.
Start at the scheduled room cue and avoid restarting between phases. If staff want an early finish, “move now” discards the unused phase time and deliberately brings every later boundary forward.
Moderator cues
Agree on warning cards, a confidence monitor, a visible timer, or discreet hand signals before the talk. Color alone is not enough: the clock labels presentation, Q&A, turnover, and overtime in text. In fullscreen, keep the device where the responsible operator can still reach pause, phase advance, and reset without blocking the audience’s view.
The “move now” control is intentionally strict. After the room clock starts, it discards the unused part of the active phase, advances schedule position to its planned boundary, and therefore brings the later phases and final finish forward. Use it only when room staff want an early release. Keep ordinary continuous timing when the original finish must stay fixed or the organizer allows reserves to flex.
Panels and multi-speaker sessions
ASPA’s current guidance makes the moderator responsible for equitable shares, audience engagement, and an on-time finish. SECAC publishes several valid ways to divide a 105-minute session among four or five speakers while preserving introductions, transitions, and discussion. Together they illustrate that presenter count changes the arithmetic; it does not erase the shared finish.
Set this timer to the whole session and reserve the common discussion and final turnover. Then create a per-panelist cue plan inside the presentation portion. If a presenter ends early, the moderator can hold the shared schedule, bring questions forward only when allowed, or move deliberately to the next boundary—without silently extending the room.
Intent separation
A keynote is not merely a longer regular session. EuroPython’s 2026 FAQ describes regular conference talks as typically 30 or 45 minutes and its keynotes as typically 45-minute featured talks that set the conference tone. The event still controls the final brief, but the preparation jobs differ.
A speaker rehearsing one featured address against an exact speaking limit can use the keynote speech timer for optional editing maps, overtime, and private run comparison. A chair, stage manager, or organizer protecting a live session should use this page for the room-level talk/Q&A/turnover plan. That separates a speaker clock from room operations without overstating what either tool does.
Conference timing FAQ
There is no universal length. Current published examples on this page include 30- and 45-minute talks, 30-minute talk/Q&A/changeover cycles, 75-minute sessions, and 105-minute multi-presenter sessions. Use the current acceptance email, speaker portal, or run of show for your event.
Sometimes, but the organizer must say. EuroPython notes that many talks include Q&A, while AZ Water publishes a precise 20-minute talk plus 5-minute Q&A inside a 25-minute presentation allocation, followed by 5 minutes of changeover. Never infer the split from the session title alone.
Turnover is protected schedule time after content and questions. It can absorb applause, the speaker leaving, audience movement, microphone transfer, captioner movement, laptop or slide setup, and the next introduction. It is not extra speaking time unless the organizer explicitly reallocates it.
Only when the event plan allows it. This timer’s “move now” action discards the unused part of the current phase and brings every later boundary forward, producing an earlier room finish. Keep the clock running normally if the published run of show keeps the original finish or permits flexible questions.
This page is built for room operations across presentation, questions, and turnover. The keynote page is a speaker-facing rehearsal clock for one featured address, with exact overtime, optional editing maps, and private run comparison; it does not allocate Q&A or room changeover. EuroPython’s current FAQ also describes regular talks and keynotes as separate programme formats.
Yes, at the session level. Put the combined panel content in the presentation budget, reserve the shared Q&A and turnover, and use a separate per-speaker timing plan when panelists need equal individual allocations. The moderator still owns live judgment and the event’s rules.
No. The tool does not ask for an event name, speaker name, session title, topic, attendee, question, slide deck, or recording. Its optional in-tab log contains only numbered sessions and timing values.
Related operating tools
Rehearse one featured address against its exact assigned speaking limit.
Configure general green, yellow, and red speaker signals.
Practice a short event-defined talk with optional in-slot Q&A.
Track an investor pitch and mark live slide changes.
Keep agenda work and decisions inside a meeting limit.
Estimate a draft before measuring it aloud at full pace.
Format statements were checked against the linked 2026 organizer materials from PyCon US, EuroPython, AZ Water, ASPA, and SECAC. They demonstrate current variation and timing responsibilities; they are not universal standards or promises about a future edition. SpeechTimer is an independent utility and is not affiliated with, endorsed by, or an official timer for those organizations or events.