Preserve lifecycle events
Owner role · Task owner
Evidence: Both acceptance events and the reopen event remain dated.
Reporting decisions / Delivery leads and report reviewers
Drafting workbenchChoose a duration clock for reopened work
Keep the first accepted cycle and the later repair interval visible when deciding how to describe reopened work.
This is a duration policy across lifecycle episodes, distinct from restating a closed-period count or triaging the new defect.
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: An item starts 09:00, is accepted 14:00, reopens 16:00 and is reaccepted 19:00 on one UTC day.
Choose the report’s episode unit
Owner role · Lead
Evidence: The rule distinguishes first cycle, repair episode and whole span.
Write the duration note
Owner role · Reviewer
Evidence: 5h + 3h episodes are not described as 10h of active effort.
Decision to make: Show a 5-hour first cycle and a 3-hour repair interval; name a 10-hour first-start-to-final-acceptance span separately if needed.
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.
Lifecycle note: first accepted cycle 5h; later repair interval 3h; total first-start-to-final-acceptance span 10h includes a 2h gap.
Put the outline to work
- Retain each event and its episode meaning.
- Select the duration definition before aggregating episodes.
- Report excluded gaps and leave effort unmeasured.
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.
Version comparison viewer
Keep the draft and its correction visible
Draft or earlier version · review its limits
Draft: one 10-hour task duration with no episode context.
Revised example · limits retained
Lifecycle note: first accepted cycle 5h; later repair interval 3h; total first-start-to-final-acceptance span 10h includes a 2h gap.
| Review boundary | Draft to review | Revised example |
|---|---|---|
| Duration unit | Single unlabeled span | Separate episodes and whole-span rule |
| History | Earlier acceptance overwritten | Both acceptance events retained |
Wide tables scroll sideways on small screens.
Synthetic example · not customer data
Inspect the records
| Episode | UTC interval | Elapsed time |
|---|---|---|
| First episode | 09:00–14:00 | 5h |
| Gap after acceptance | 14:00–16:00 | 2h |
| Repair episode | 16:00–19:00 | 3h |
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
- Both acceptance events and reopen are known
- Use separately labelled episodes or whole span with its gap explained.
- A lifecycle event is missing
- Hold reconstructed episode durations.
- The question is delivered-unit count
- Use a counted-unit policy; do not derive count from duration.
Questions about this workflow
Why is the whole span 10 hours but episodes sum to 8?
The whole span includes the two-hour accepted-to-reopened gap; the selected episodes do not.
Is repair time a new accepted-delivery count?
That requires a separate counted-unit policy; a duration alone does not determine throughput.
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.