# Report duration coverage when starts are missing

Illustrative planning brief; no automatic product import.

Synthetic case: Four items were accepted; A and B have ordered starts and finishes, C lacks a start and D has a start after its finish.

## Decision

Report two usable durations out of four accepted records and disclose both excluded cases; do not assign zero to missing or reversed starts.

## Owned work

- Reconcile accepted records
  - Owner role: Report owner
  - Acceptance evidence: All four accepted IDs remain in the coverage ledger.
- Review the duration eligibility rule
  - Owner role: Reviewer
  - Acceptance evidence: Ordered known timestamps qualify; missing/reversed pairs are separate exceptions.
- Publish the coverage note
  - Owner role: Lead
  - Acceptance evidence: Two-of-four coverage accompanies any duration summary.

## Workflow

1. Start with all records in the stated acceptance cohort.
2. Apply one documented eligibility rule to event pairs.
3. Keep coverage and exclusion reasons beside the duration result.

## Judgment

Missingness may be systematic. The two usable records cannot establish the duration distribution of all accepted work.


## Filled review note

Coverage note: two ordered event pairs among four accepted items (50% coverage). C is unknown; D has conflicting timestamps. The usable mean is three hours, not an all-item mean.


## Workflow questions

### Should a missing start become zero duration?

No. It is unknown duration in this policy, not instantaneous delivery.

### Can I show the average of usable records?

You may label it as the usable subset, retain two-of-four coverage and avoid generalizing to all work.

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

Item | Start UTC | Finish UTC | Duration treatment
--- | --- | --- | ---
A | 10:00 | 12:00 | 2h usable
B | 09:00 | 13:00 | 4h usable
C | Missing | 14:00 | Unknown duration
D | 15:00 | 14:00 | Ordering conflict

### Version changes

Boundary | Draft | Revised
--- | --- | ---
Coverage | Four accepted records assumed usable | Two usable; two explicit exceptions
Interpretation | All-item duration claim | Subset-only summary with missingness limits

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

Draft: a duration summary for four accepted items.

### Revised example

Coverage note: two ordered event pairs among four accepted items (50% coverage). C is unknown; D has conflicting timestamps. The usable mean is three hours, not an all-item mean.

### Decision situations

- Eligibility and exclusion counts are known: Publish the subset summary with its coverage and exceptions.
- Excluded records are not tracked: Hold the all-item claim and reconcile the accepted cohort.
- The event-pair rule is unspecified: Define timestamp eligibility before summarizing.

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