Freeze the calendar rule
Owner role · Coordinator
Evidence: Weekdays, hours, timezone and holiday treatment are explicitly supplied.
Reporting decisions / Delivery leads and report reviewers
Drafting workbenchElapsed duration and business-window duration
Define a business-window duration separately from elapsed cycle time using a stated calendar and example interval.
A supplied work window can change a descriptive duration; it does not measure person effort or prove a company holiday calendar.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Prepare a brief for human review
Drafting workbenchSynthetic case: Work starts Friday 16:00 and finishes Monday 10:00 UTC. The invented calendar counts Monday–Friday 09:00–17:00 with no holidays in this interval.
Intersect the interval with windows
Owner role · Reviewer
Evidence: Friday 1h + Monday 1h = 2h, with 66 elapsed hours retained.
Label both measures
Owner role · Report owner
Evidence: Neither elapsed nor business-window duration is called hands-on effort.
Decision to make: Report 66 elapsed hours and 2 hours inside the supplied business windows as distinct measures.
Use the downloaded brief as planning input. AI suggestions remain proposals; review scope, owners and acceptance evidence yourself.
Filled review note
Invented planning text. Adapt it to your evidence and confirmed owners.
Clock note: 66 elapsed hours; 2 hours intersect the stated weekday 09:00–17:00 UTC windows. Effort is unknown.
Put the outline to work
- State timezone and calendar rather than assuming a standard workweek.
- Calculate elapsed span separately from overlap with allowed windows.
- Version calendar changes and keep the two units labelled.
From a useful outline to team work
Explore TeamBoostAI for your team
Bring this manual reporting policy and its owned checks into your TeamBoostAI work discussion. Native report/export fields and historical reconstruction depend on your account and implementation; this worksheet does not import or change product records. 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 practical decision workshop
Inspect the example before choosing a rule
Trace an invented case, preserve the evidence limits, then adapt the manual worksheet to your own decision.
Evidence dependency diagram
What must be known first?
Scroll the diagram sideways if needed; every dependency is also written below.
- Observed interval → Two labelled clocks: elapsed span.
- Supplied calendar → Two labelled clocks: window intersections.
Synthetic example · not customer data
Inspect the records
| Segment | Selected window | Included duration |
|---|---|---|
| Friday | 16:00–17:00 | 1 business-window hour |
| Weekend | Outside supplied windows | 0 business-window hours |
| Monday | 09:00–10:00 | 1 business-window hour |
Wide tables scroll sideways on small screens.
Download records (.csv) · Download complete decision kit (.json)
Decision explorer
Choose an evidence situation
This returns a written example explanation. It does not inspect your records or approve a real report.
Read every situation without the interactive tool
- Actual interval and calendar are supplied
- Show both labelled measures using that calendar.
- Calendar exceptions or timezone are missing
- Hold the business-window value until the calendar is known.
- The desired measure is hands-on effort
- Collect effort evidence separately; neither clock supplies it.
Version comparison viewer
Keep the draft and its correction visible
Draft or earlier version · review its limits
Draft: the task took 2 hours.
Revised example · limits retained
Clock note: 66 elapsed hours; 2 hours intersect the stated weekday 09:00–17:00 UTC windows. Effort is unknown.
| Review boundary | Draft to review | Revised example |
|---|---|---|
| Measure | Unlabelled 2 hours | Separate elapsed 66h and business-window 2h |
| Calendar | Assumed standard schedule | Explicit supplied UTC window rule |
Wide tables scroll sideways on small screens.
Questions about this workflow
Why is elapsed time 66 hours?
Friday 16:00 to Monday 10:00 is two full days plus 18 hours. The example uses UTC.
Do two business-window hours mean two hours of work?
No. They measure overlap with a supplied calendar, not observed hands-on effort.
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.