Freeze the checkpoint
Owner role · Coordinator
Evidence: The snapshot names the date, 16:00 UTC and the open-item rule.
Work measurement / Team leads and delivery coordinators
Drafting workbenchMeasure the age of still-open work at a fixed checkpoint and separate it from completed-item cycle time.
An open-item snapshot exposes unfinished work that a completed-only report omits; it does not select review priority automatically.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Synthetic example: At a 16:00 UTC checkpoint, item A started at 09:00 and is still active; item B started at 12:00 and is still blocked. A completed item is excluded from the open snapshot.
Owner role · Coordinator
Evidence: The snapshot names the date, 16:00 UTC and the open-item rule.
Owner role · Work owners
Evidence: A and B have known starts; completed item C is excluded.
Owner role · Delivery lead
Evidence: B’s required input is owned; A’s acceptance boundary is checked separately.
Decision to make: Keep A at seven elapsed hours and B at four; investigate B’s blocking condition without pretending either item has a completed cycle time.
Use the downloaded brief as planning input. AI suggestions remain proposals; review scope, owners and acceptance evidence yourself.
Invented planning text. Adapt it to your evidence and confirmed owners.
Open snapshot: A 7 hours, B 4 hours. Investigate the blocked input for B and retain both unfinished items in the report.
From a useful outline to team work
Use this manual measurement rule as context when planning or reviewing owned work in TeamBoostAI. Confirm the fields and reports available in your account; the worksheet is not imported automatically. Confirm the workflows available in your account before adopting this outline.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
A worked measurement study
Every record here is synthetic. Use the rule to review your own evidence before taking action.
Read units and denominators with the source table. These are invented example records.
At 16:00, A age = 16 − 9 = 7 hours; B age = 16 − 12 = 4 hours. Neither has a finish event.
Open snapshot: A 7 hours, B 4 hours. Investigate the blocked input for B and retain both unfinished items in the report.
Invented records · inspect every count
| Item | Start UTC | Checkpoint state | Age in hours |
|---|---|---|---|
| A | 09:00 | Active | 7 |
| B | 12:00 | Blocked | 4 |
On small screens, scroll a wide table sideways to see all columns.
Download example data (.csv) · Download method worksheet (.json)
Open status and start events at 16:00
Supports two ages, not two completion times.
Future finish events
Do not forecast a finish solely from current age.
Repeat the snapshot and inspect blocking inputs
Keep the same boundary while work progresses.
No. It stops at the observation checkpoint because the item is unfinished.
Not under this started-but-unfinished rule. Keep their state visible rather than erasing their waiting.
Show unknown age and repair the event evidence. Do not substitute creation time silently.
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.