Work measurement / Team leads and delivery coordinators

Task board

Cycle time: define the start and finish clock

Choose reproducible cycle-time boundaries before comparing task durations. Work through a timestamp example and record the rule in a manual worksheet.

Distinguish creation, active start and accepted finish; specify elapsed hours and retain waiting time in this example.

Request TeamBoostAI access Get the work brief Task table (.csv)

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 board

Synthetic example: An item is created at 08:00, started at 10:00 and accepted at 18:00 on the same UTC day. A report currently subtracts creation time.

Agree the boundary

Owner role · Delivery lead

Evidence: The rule identifies active start, accepted finish, UTC timestamps and included waits.

Reconcile the event pair

Owner role · Task owner

Evidence: The original record contains 10:00 and 18:00, with no guessed start.

Review the reported duration

Owner role · Acceptance reviewer

Evidence: The report shows eight elapsed hours and names its clock policy.

Decision to make: Publish eight elapsed hours under an active-start-to-acceptance rule; keep ten hours as a separately named creation-to-acceptance duration.

Worked reporting note

Invented planning text. Adapt it to your evidence and confirmed owners.

Report: 8 elapsed hours from active start to accepted finish. Preserve the separate 10-hour creation-to-acceptance observation.

Put the outline to work

Write event meanings before subtracting timestamps.
Check ordering and timezone, then calculate elapsed time under one rule.
Version a changed clock rule rather than silently rewriting prior comparisons.

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.

Invented records · inspect every count

Inspect the invented records
Event	Observed time	Treatment
Created	08:00 UTC	Not this clock’s start
Active start	10:00 UTC	Included boundary
Accepted finish	18:00 UTC	Included boundary

On small screens, scroll a wide table sideways to see all columns.

Download example data (.csv) · Download method worksheet (.json)

Try the arithmetic

Local calculation sandbox

Change the invented inputs to explore the rule. Inputs stay in this browser; nothing is sent or saved.

Start hour (same UTC day)Finish hour (same UTC day)8 elapsed hours

The written example remains below if JavaScript is unavailable. A calculation does not validate a sample, instrument or forecast.

Follow the example events

08:00
Created
Outside the selected clock
10:00
Started
Clock begins
18:00
Accepted
Clock ends

Work through the rule

Same-day elapsed hours = finish hour − start hour = 18 − 10 = 8. Creation-to-acceptance = 18 − 8 = 10; these answer different questions.

Report: 8 elapsed hours from active start to accepted finish. Preserve the separate 10-hour creation-to-acceptance observation.

Keep evidence and inference separate

Observed

Two ordered same-day timestamps

Supports an eight-hour elapsed duration.

Unknown

Hands-on effort during those hours

Do not label eight hours as engineering effort.

Next check

Audit the next record against the written events

Investigate missing starts before comparing durations.

Questions about this workflow

Does task creation start this clock?

No. This worked policy starts at active work. A creation-based clock is useful only when separately labelled.

Do waits disappear from cycle time?

Not under this elapsed policy. If you also report active effort, maintain a separate measure and its evidence.

What if acceptance happens the next day?

Use complete timestamps in one timezone. The same-day hours sandbox cannot model a date rollover.

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