Meeting Timer

How it works

The Meeting Timer has two views that work together:

The pill — a small floating control that sits on top of whatever page you are on. Everything the running timer needs is on it: rename, pause, reset, next part, stop. Drag it anywhere it is not in the way and it stays there. This is where a quick stopwatch or countdown starts.
Full screen — massive countdown digits, color-coded background, designed to be visible from across the room. Use this when the phone is propped on a podium or table. A planned meeting starts here; anything else opens it only if you ask.

The timer keeps running no matter where you navigate in the app — and it keeps correct time even when you leave the browser entirely. See Leaving the timer running for exactly what happens when you switch apps, lock your phone, or close the tab.

Getting started

Open the timer

Go to Meeting Timer from the Explore menu (under Prepare) or navigate directly to /timer.

Or just start timing

Quick start, at the top of the page, needs no template and no setup. Stopwatch counts up from zero with no limit; Countdown takes a number of minutes — 30s, 1, 3, 5, 10, 15, 30, or anything you type — and counts down from it.

Either one comes up as the pill, beside whatever you were doing, rather than taking the screen. That is the point: you start a stopwatch because someone has begun speaking, and covering the paragraph you were reading is the opposite of helpful.

The same two are on the + button on a phone, so you can start timing from any page in the app.

Pick a starting point

You'll see a card for each starting point: a study group, a team standup, a class session, language practice, a talk with questions, and a quick single timer. Each is a shape to begin from, not a fixed programme, and the one that matches your coaching context is listed first.

Each card shows the parts, their durations, and the total. Tap Start to begin timing immediately, or Clone & edit to make it yours.

Or make your own

Tap Clone & edit on any card, or New template to start from blank. The editor lets you:

Name and describe it — the name is what the timer shows while it runs
Rename parts — tap any part name to change it
Change durations — adjust the minutes for each part
Add or remove parts — use + Add part or the × button
Reorder — use the up/down arrows to rearrange the schedule
Set a start time — enter when the meeting begins and see calculated end times for each part
Pick a coaching context — optional; it tags the template, and the starting point matching your context leads the page

The schedule bar at the top always shows the total duration and predicted end time. As you add, remove, or resize parts, the schedule updates instantly.

Tap Save template to keep it under Your templates, or just tap Start timer to begin without saving. Saving needs an account; starting a timer doesn't.

The full-screen timer

Once started, the timer fills the screen with a large countdown. The background color tells you how the part is going at a glance:

Green — more than half the time remaining. Relax.
Amber glow — between 25% and 50% remaining. Heads up.
Amber solid — less than 25% remaining. Time to wrap up.
Red — overtime. The timer crosses zero and counts up, showing exactly how far over. +0:45 means 45 seconds past the budget.

Controls at the bottom: Pause freezes the clock (tap again to resume). Next records the current part's time and advances to the next one.

The pill

A quick start is already here. From the full screen, tap Minimize (top-left) or press Esc. The pill shows the part name and the countdown, plus the meeting total on a multi-part meeting — "Part 3/10 · Meeting: 58:30".

Its buttons, and none of them expands anything:

✎ Rename — two fields, in place: what are you timing? and which meeting?. The reading is filed the moment you stop, so name it while it runs. Enter commits, Escape abandons.
Pause / Resume
↻ Reset — back to zero, still running
▸▸ Next — multi-part meetings only
■ Stop
⛶ Expand — the full screen

Drag it wherever you like. Take hold of the name or the time — not the buttons — and move it off whatever it is covering. It stays where you put it, and the next timer you start begins there too.

Now you can go anywhere — review your comments, look up a verse, check your outline — and it comes with you, counting.

Stopping, which is not the same as closing

Stop a stopwatch or a countdown and it stays where it is, showing what it said, with Stopped underneath. The reading is already filed in Recorded times — you can walk away from a stopped timer without losing it — and you get four choices:

▸ Play — carry on from where it stopped. The reading that stop filed is taken back out again; you are undoing the stop, so a 0:06 should not sit in the list beside the 0:15 that actually happened.
↻ Reset — start over from zero, running. This one keeps the reading: that measurement happened, and this is the next one beginning.
^ Summary — the full screen, on the summary.
✕ Close — the only button that puts the timer away.

Meeting summary

After the last part (or if you tap End Meeting), you'll see a summary table showing each part's budgeted time, actual time, and the difference. Parts that ran over are flagged.

Tap Save to store the session for future reference, or Done to dismiss.

Leaving the timer running

Meetings do not wait for you to keep the right tab in front. You will switch to your notes, answer a message, let the phone screen lock, or walk away from the laptop for a moment. The timer is built so that none of that costs you accuracy.

Why web timers usually drift — and why this one doesn't

Most timers on the web count seconds as they go by: every second that passes, add one. That works only for as long as the browser keeps ticking. The moment a tab moves to the background, browsers deliberately slow those ticks down — often to roughly one a minute — to save battery, and on iPhones and iPads they stop them altogether when you switch apps or the screen locks. A timer built that way quietly loses every tick it never received. It doesn't pause and it doesn't warn you. It just runs slow, and you find out afterwards that your twelve-minute part was really eighteen.

This timer never counts ticks. It records the clock time your part started and, whenever it needs to show a number, subtracts that from the current clock time. Being backgrounded, throttled, or frozen for twenty minutes changes nothing, because the answer is worked out fresh from the clock rather than added up along the way. The digits refresh four times a second while you are watching, but that is only for the display — the elapsed time is right whether that refresh happened or not.

What survives what

Switching to another app — keeps exact time. The moment you come back the reading is already correct; there is no visible catching-up.
Locking your phone — keeps exact time, including on iPhone and iPad where the browser is fully suspended.
Another window on top of the browser — keeps exact time. This is the case most web timers get wrong, because the tab technically never became "hidden".
Switching tabs — keeps exact time.
Refreshing the page — resumes exactly where it should be, including any time that passed during the reload.
The browser crashing, or the tab being dropped to free memory — resumes when you reopen the page. Phones drop background tabs routinely; that is expected, not a failure.
Several tabs open at once — they stay in sync. Pause in one and the others pause too; you will never have two tabs disagreeing about the same meeting.
Your device's clock correcting itself — the countdown never jumps backwards.

The screen stays awake while the timer runs, so a phone propped on the podium won't dim mid-part. If something else takes that hold away — a call, another app — the timer takes it back as soon as you return.

The one judgment call: long absences

Counting clock time is the right answer for the absences that actually happen during a meeting. It becomes the wrong answer at the extremes. If you close the laptop after a meeting and open it the next morning without ending the timer, strict clock time would greet you with fourteen hours of overtime on a five-minute part — technically accurate, completely useless.

So the timer notices how long the page was actually away, and treats three cases differently:

Up to 30 minutes away — counted in full. You stepped out; the meeting carried on.
30 minutes to 8 hours — the timer comes back paused, holding the last time it can vouch for, and says so plainly: "this page was away for about 2 hours, so that time was not counted." Tap Resume to carry on, or End Meeting for the summary. It will never invent a number it can't stand behind.
More than 8 hours — treated as abandoned and cleared, so yesterday's forgotten meeting doesn't greet you today.

Worth knowing

Nothing alerts you while you are away. The time stays right, but a part going overtime while you are in another app will not buzz, ring, or notify. You see the correct overtime when you come back. If you are chairing, keep the timer in view.
Quitting the browser completely stops the clock. No web page can keep counting once the browser is closed — but the timer's starting point is saved, so reopening the page picks the meeting back up under the rules above.
The timer lives in this browser, on this device. It is not synced to your account, so starting a timer on your phone will not show it on your laptop.
Private browsing still works — but because private windows discard their storage on close, a timer started there won't survive the window closing.

Tips

Keyboard shortcuts in full screen: Space = pause/resume, → = next part, Esc = minimize to pill.
Screen stays on — the timer automatically prevents your phone from sleeping while it's running.
Leave it running — switch apps, lock the phone, refresh the page. The timer reads the clock rather than counting ticks, so the time is right when you come back. See Leaving the timer running.
Prop it up and walk away — because backgrounding is safe, you can start the timer on a second device, minimize it, and still use that phone for something else.
Running the meeting? — clone a starting point once, save it as your own, and adjust it before each session to that day's agenda. Set the start time to see when each part should begin and end.
Speaking? — minimize the timer and review your comment while the pill counts down beside it. Move the pill first if it is sitting on the words.
Timing just one thing? — Quick start. No template, no setup, and it comes up beside what you were doing rather than over it.

Recorded times

Every stopwatch and countdown you stop is filed in a list under Quick start. It exists for one question: how long does this part actually take? — which is the question you need answered before a template is worth building.

By part groups the readings by what you were timing, with a count and an average. Five readings of "Opening prayer" across five weeks is the answer.
Flat is the plain log, newest first.
A countdown's reading carries its budget, so it reads as "4:12 of 5m, 48s under" rather than a bare number. A stopwatch had no target to miss, so it is reported and not graded.

Signed in, readings follow your account. Signed out, they stay on the device. Clear all asks first, in the footer, and cannot be undone.