Tally Standup Drift Until the Pattern Shows — Free
A fifteen-minute standup that runs twenty is a different meeting. Log planned against actual, count only the minutes over your tolerance, and let the tally make the pattern undeniable.
The proof surface
Meeting cost tools price a meeting before booking it. This audits a meeting you already run: drift minutes beyond a tolerance you set, summed until the creep is visible as a number.
Why the flat version breaks
Netting early finishes against overruns
A short Friday does not refund a long Monday.
Timing the agenda instead of the room
The drift lives in what actually happened.
Logging without a tolerance
Without a line, every row looks acceptable.
How to work the drift chronometer
Start the clock when the standup starts and stop when it truly ends, including the tail of side conversations you count as part of it. Round to whole minutes.
The sample accepts three minutes of drift. Monday ran five over fifteen — two counted, flagged because it passed the tolerance. Exactly three over is tolerated and not flagged.
A meeting that finishes early contributes zero, not negative slack — Friday’s three spare minutes do not cancel Monday’s overrun in the tally. The total is the drift you actually paid.
Eight counted minutes across two flagged standups is a conversation with evidence attached. If drift is deliberate — a hard topic needed the time — say so in the log instead of letting it hide in the total.
What the drift chronometer replaces
| Question | Before | Visible working |
|---|---|---|
| Netting early finishes against overruns | A short Friday does not refund a long Monday. | Set a tolerance you mean |
| Timing the agenda instead of the room | The drift lives in what actually happened. | Sum only the excess |
| Logging without a tolerance | Without a line, every row looks acceptable. | Bring the tally to the retro |
A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.
Run it on the samples, right here
FIRST-LOAD
Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Meeting arithmetic on times you record. Not a productivity judgement or a management mandate; the tolerance and the response belong to the team.
Data note: Everything runs in this browser tab on the drift chronometer: your standup | planned minutes | actual minutes stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Go deeper: the companion app files the same reading as a plotted bar chart sheet
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the drift chronometer reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.
The drift chronometer reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.
Open the tally standup drift until the pattern shows companionBoundary
Meeting arithmetic on times you record. Not a productivity judgement or a management mandate; the tolerance and the response belong to the team.
What this is built on
- Method: A meeting that finishes early contributes zero, not negative slack — Friday’s three spare minutes do not cancel Monday’s overrun in the tally. The total is the drift you actually paid.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-28, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Before: A short Friday does not refund a long Monday. After: the drift chronometer shows the working beside each named row so the reader can change the assumption and inspect the consequence.
Optional AI formatting, not calculation
For this drift chronometer, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a drift chronometer. Return plain rows only: standup | planned minutes | actual minutes. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: standup | planned minutes | actual minutes. No AI response is executed as code.