Name the snapshot boundary
Owner role · Delivery lead
Evidence: Active start and accepted finish are written beside the noon checkpoint.
Work measurement / Team leads and delivery coordinators
Task boardWork in progress: define the snapshot boundary
Count started-but-unfinished work at a fixed checkpoint without mixing backlog, active work and accepted outcomes.
A state-by-state ledger makes stock at one instant distinguishable from throughput over a period.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Turn the situation into owned work
Illustrative task boardSynthetic example: At noon a board has five unstarted items, two active, one blocked, one awaiting review and two accepted items.
Reconcile state counts
Owner role · Coordinator
Evidence: 2 active + 1 blocked + 1 in review = 4; backlog and accepted records are excluded.
Review the control decision
Owner role · Work owners
Evidence: Owners inspect the blocked/review inputs before deciding whether to start additional work.
Decision to make: Under the agreed start-to-acceptance boundary, report four work-in-progress items and preserve their state breakdown.
Worked reporting note
Invented planning text. Adapt it to your evidence and confirmed owners.
Noon snapshot: four started-but-unfinished items, including one blocked and one awaiting review. No finish forecast is made.
Put the outline to work
- Freeze one observation time and the start/finish meanings.
- Classify started-but-unfinished records, including waits inside the boundary.
- Use the state breakdown to review new-start decisions, without deriving a delivery rate.
A worked measurement study
Inspect the data. Trace the decision.
Every record here is synthetic. Use the rule to review your own evidence before taking action.
Keep evidence and inference separate
Observed
Counts and states at noon
Supports a four-item stock snapshot.
Unknown
Future completed volume
Do not infer a daily completion rate.
Next check
Verify one started-but-unfinished record per state
Repair inconsistent state meaning before trend comparisons.
Invented records · inspect every count
| State | Records | WIP treatment |
|---|---|---|
| Unstarted backlog | 5 | Excluded |
| Active | 2 | Included |
| Blocked | 1 | Included |
| Awaiting review | 1 | Included |
| Accepted | 2 | Excluded |
On small screens, scroll a wide table sideways to see all columns.
Download example data (.csv) · Download method worksheet (.json)
Read units and denominators with the source table. These are invented example records.
Work through the rule
WIP at noon = active 2 + blocked 1 + awaiting review 1 = 4 records. Neither backlog 5 nor accepted 2 is added.
Noon snapshot: four started-but-unfinished items, including one blocked and one awaiting review. No finish forecast is made.
Questions about this workflow
Is the backlog part of WIP here?
No. These five items have not crossed the defined active-start boundary.
Does a blocked record still count?
Yes, when it started and has not reached accepted finish under this policy.
Does four WIP mean four items will finish today?
No. The count contains no future completion evidence.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.
From a useful outline to team work
Explore TeamBoostAI for your team
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.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.