Tally Standup Drift Until the Pattern Shows
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.
1 · standup | planned minutes | actual minutes
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.
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.
Perspective: 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.
2 · Read the drift chronometer
Meeting arithmetic on times you record. Not a productivity judgement or a management mandate; the tolerance and the response belong to the team.
Paid layer: drift chronometer print and history
one-time step · the free reading above stays complete
Free tier
- one complete drift chronometer run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the drift chronometer with its row workings
- CSV of minutes over and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the drift chronometer, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
Meeting arithmetic on times you record. Not a productivity judgement or a management mandate; the tolerance and the response belong to the team.
- 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.
Mechanism: competence-autonomy-loop
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.