TeamBoostWORKFLOW LIBRARY

Work measurement / Team leads and delivery coordinators

Drafting workbench

Blocked time: avoid double-counting overlapping waits

Calculate the union of blocked intervals before reporting total waiting time. Preserve each cause without adding overlapping hours twice.

Separate elapsed blocked time from the number of concurrent causes; this ledger resolves overlap arithmetic rather than retry decisions.

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Prepare a brief for human review

Drafting workbench

Synthetic example: A missing input blocks work from hour 10 to 14. A permission issue also blocks it from 12 to 15 on the same day.

01

Check the interval log

Owner role · Task owner

Evidence: Both start/end pairs use one day and timezone; ends follow starts.

02

Merge overlapping coverage

Owner role · Coordinator

Evidence: The union is [10,15), five hours, with both cause labels preserved.

03

Confirm each recorded end

Owner role · Receiving owners

Evidence: Each cause owner confirms its recorded end condition and retains the evidence for the retrospective log.

Decision to make: Report five elapsed blocked hours, while preserving two blocking causes and their receiving owners.

Use the downloaded brief as planning input. AI suggestions remain proposals; review scope, owners and acceptance evidence yourself.

Worked reporting note

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

Blocked coverage: five elapsed hours. Missing-input and permission causes remain separately owned records.

Put the outline to work

  1. Write blocking starts and ends as half-open intervals.
  2. Sort and merge overlapping intervals before adding lengths.
  3. Retain causes and owners separately from the elapsed total.

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.

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
Cause or unionStart hourEnd hourElapsed hours
Missing input10144
Permission issue12153
Merged coverage10155

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.

5 elapsed hours

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

Work through the rule

Individual lengths are 4 and 3; overlap is 2. Union = 4 + 3 − 2 = 5 elapsed hours, not 7.

Blocked coverage: five elapsed hours. Missing-input and permission causes remain separately owned records.

Keep evidence and inference separate

Observed

Two closed intervals on one clock

Supports their five-hour union.

Unknown

Active effort or financial impact

Do not multiply the coverage into a cost claim.

Next check

Confirm the end condition with each receiving owner

Do not close a cause because a different cause cleared.

Questions about this workflow

Why not add four and three hours?

The two intervals overlap for two hours. Adding their lengths would count that period twice.

What does half-open mean here?

Include the start and stop at the end; touching intervals do not create extra duration.

What if both causes have different owners?

Keep both cause records. Merging time coverage does not merge responsibility.

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.