# Elapsed duration and business-window duration

Illustrative planning brief; no automatic product import.

Synthetic 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.

## Decision

Report 66 elapsed hours and 2 hours inside the supplied business windows as distinct measures.

## Owned work

- Freeze the calendar rule
  - Owner role: Coordinator
  - Acceptance evidence: Weekdays, hours, timezone and holiday treatment are explicitly supplied.
- Intersect the interval with windows
  - Owner role: Reviewer
  - Acceptance evidence: Friday 1h + Monday 1h = 2h, with 66 elapsed hours retained.
- Label both measures
  - Owner role: Report owner
  - Acceptance evidence: Neither elapsed nor business-window duration is called hands-on effort.

## Workflow

1. State timezone and calendar rather than assuming a standard workweek.
2. Calculate elapsed span separately from overlap with allowed windows.
3. Version calendar changes and keep the two units labelled.

## Judgment

Calendar time is not engineer effort. Real holidays, daylight-saving transitions or irregular schedules require their actual calendar rules.


## Filled review note

Clock note: 66 elapsed hours; 2 hours intersect the stated weekday 09:00–17:00 UTC windows. Effort is unknown.


## Workflow questions

### 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.

## Product connection

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 account availability before adopting this manual outline.

## Decision workshop

Synthetic examples only. Manual worksheet; no automatic import or product writes.

### Synthetic reporting 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

### Version changes

Boundary | Draft | Revised
--- | --- | ---
Measure | Unlabelled 2 hours | Separate elapsed 66h and business-window 2h
Calendar | Assumed standard schedule | Explicit supplied UTC window rule

### Draft or earlier version (review its limits)

Draft: the task took 2 hours.

### Revised example

Clock note: 66 elapsed hours; 2 hours intersect the stated weekday 09:00–17:00 UTC windows. Effort is unknown.

### Decision situations

- 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.

### Evidence dependencies

- Observed interval → Two labelled clocks: elapsed span
- Supplied calendar → Two labelled clocks: window intersections

### Method references

- The Kanban Guide, May 2025: https://kanbanguides.org/the-kanban-guide/2025.5/ — Clock and work-item definitions; examples and local rules are our own.