StageClock

How StageClock works

What it measures, how precise it is, and what it cannot see.

Getting started

  1. Connect Notion and, in Notion’s page picker, share the databases you want to track. Share the original database, not a linked view.
  2. Track a database. StageClock proposes its status property and reads the status groups (To-do, In progress, Complete).
  3. Start tracking. StageClock records the current status of every row, then every change from now on.
  4. Open the reports. They fill in as rows move; the cycle time trend needs about 10 completed rows.

1. Property to track

Status or select property
Not startedTo-do
In progressIn progress
ReviewIn progress
Waiting on clientIn progress
DoneComplete
Setup: StageClock proposes the status property and reads its groups from Notion. Sample data.

Definitions

The reports

Median cycle time
6.3 d
▲ 1.1 d vs previous period · 63 rows
Slowest status (median)
Waiting on client
4 d · 18 rows
Open rows
7
2 over their status limit
Completed, last 90 days
63
First entry into a Complete status
Overview: the figures that matter, each with the number of rows behind it. Sample data.
Not started: median 2.1 d (61 rows)Not started2.1 dIn progress: median 3.6 d (63 rows)In progress3.6 dReview: median 2.4 d (58 rows)Review2.4 dWaiting on client: median 4 d (18 rows)Waiting on client4 d
Time in status: median time per status; hover a bar for the average and 85th percentile. Sample data.
Q4 brochure — In progress for 3.9 dQ4 brochure3.9 dLanding page A/B — Review for 3.4 dLanding page A/B3.4 dCase study: Nordwind — Review for 3.1 dCase study: Nordwind3.1 dHomepage redesign — In progress for 1.8 dHomepage redesign1.8 dPricing page copy — Review for 1.3 dPricing page copy1.3 d
Aging work: open rows by time in their current status. The dashed line is the limit you set for alerts. Sample data.
5 d10 dWeek of 10 Aug: median 5.4 d5.4 d10 AugWeek of 17 Aug: median 5.8 dWeek of 24 Aug: median 7.6 d24 AugWeek of 31 Aug: median 6.8 dWeek of 7 Sept: median 9.2 d9.2 d7 SeptWeek of 14 Sept: median 4.3 dWeek of 21 Sept: median 6.9 d21 SeptWeek of 28 Sept: median 6.1 dWeek of 5 Oct: median 5.7 d5 OctWeek of 12 Oct: median 5.8 dWeek of 19 Oct: median 6.4 d19 OctWeek of 26 Oct: median 7 dWeek of 2 Nov: median 7.1 d7.1 d2 Nov
Cycle time trend: weekly median, faded when a week has fewer than five completed rows. Sample data.

Custom metrics

Targets and forecast

Time per assignee

Choose a people property as the assignee: StageClock records who a row is assigned to, like statuses. By default it shows team figures only (time to first assignment, handoffs, unassigned time). Per-person figures can be switched on; they measure individuals, so in some countries employee representatives must be consulted first.

Sharing, exports and embeds

Precision

Not started1.2 dexact
In progress2.5 dexact
Review3.1 dapproximate
In progress0.8 dexact
Row timeline: every stay of one row, with its precision. Sample data.

Limits

Write-back

Optional. StageClock adds Status since, Days in current status (a Notion formula on Status since, so it never needs rewriting), Cycle time (days), Lead time (days) and up to five Time in [status] (days). A Notion filter such as “Days in current status > 5” then shows the same rows as StageClock’s aging report.

Each write is an edit: Last edited by shows StageClock. Writes are silent, but database automations that react to edits can run. Only changed values are written, one request per row, at the pace Notion allows.

Alerts

Set a limit per status. Once a day, at the hour you choose, StageClock emails the rows that went over a limit since the last digest. A row is reported once per stay in a status. Optionally StageClock comments on the Notion page and mentions the assignee.