# A conference timer for speakers and sessions Per-speaker countdowns, a session running order, silent wrap-up cues, and screens that prove they are connected — across one stage or several. Conference schedules fail at the podium: one speaker runs seven minutes over, the break shrinks, and the whole afternoon arrives late at the closing keynote. A conference timer fixes the failure where it happens — a countdown each speaker can see, warnings that need no interpretation, and a session order that advances on schedule. MaestroTimer runs this in the browser across as many rooms as the conference has. Here is the setup for a single track, and the pattern that scales it to parallel stages. ## One track: the session as a running order A session maps to a room: one named timer per talk, in order. The setup: 1. Create a room for the track and add a timer per talk — name, speaker, and duration straight from the program. 2. Set wrap-up thresholds to match what speakers were told in their briefing: a first warning to begin landing, a final-minute signal. 3. Link the timers so each talk's countdown starts as the previous ends, and schedule fixed anchors — the 09:00 open, the 14:00 resumption — to start themselves. 4. Open the viewer link fullscreen on the stage-facing confidence monitor. ## What the speaker sees The confidence monitor shows the countdown and nothing else. As the talk approaches its end, the display changes appearance at your thresholds — a peripheral signal the audience never sees and the speaker cannot miss. The classic placement is a wedge monitor flat on the stage floor at the front edge: the speaker checks the time with a glance downward, without ever turning away from the audience. When something specific needs saying — "Q&A cancelled, wrap at time", "mic change after you" — the session chair sends a message from the moderator view and it appears next to the countdown, silently. Remote speakers get the identical experience: the same viewer link, open beside their meeting window. ## Parallel stages: one room per track Conferences rarely stay single-track. The scaling pattern keeps each track independent: one room per stage, each with its own running order, viewer, and controller. Track hosts control their own rooms; the program office keeps every controller link and can step into any track from one laptop. Each room's live connections view lists that stage's screens, so verifying four stages is reading four short lists during the coffee break. ## Keeping the day recoverable The schedule survives on buffers and honesty. Give breaks their own timers — a visible countdown in the foyer brings audiences back on time, and a break is also where a slipped session quietly repays its debt: shorten it from the controller and the day realigns without an announcement. Panels and Q&A blocks run in count-up mode where a hard deadline reads as hostile; the chair watches elapsed time with a planned end in mind. The agenda view's link gives volunteers and speakers the live running order, which kills the "are we on time?" question at the source. ## FAQ ### How do conference speakers see their remaining time? A confidence monitor at the stage edge shows the viewer link fullscreen. Wrap-up thresholds change the display as time runs low, so the warning is visual and automatic. ### How does this work across parallel tracks? One room per track, each with its own running order and screens. The program office keeps every controller link, and each room's live connections view verifies that stage's displays. ### Can remote conference speakers see the same timer? Yes — send them the viewer link to open beside their meeting window. Same countdown, same warnings, nothing installed. ### How do I get a slipped session back on schedule? Absorb the slip in the next break: shorten its timer from the controller. Linked timers keep the rest of the order advancing automatically. **Run every stage on one system** — MaestroTimer runs in the browser: per-talk countdowns, staged wrap-up warnings, silent messages from the chair, and a live list of every connected screen — per track, at any scale. [Try MaestroTimer](https://maestrotimer.com)