Name the counted identity
Owner role · Report owner
Evidence: The policy uses event ID with task ID, not displayed title.
Reporting decisions / Delivery leads and report reviewers
Drafting workbenchReconcile duplicate rows in a delivery summary
Check whether repeated report rows represent the same accepted event before publishing a delivery count.
The unit is a distinct accepted event; this resolves repeated rows rather than nested parent/child delivery units.
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: The worksheet lists A at acceptance 09:00 twice, B at 10:00 once and A at a later acceptance 15:00 once. Removing every repeated task ID would also lose a different event.
Inspect repeated rows
Owner role · Reviewer
Evidence: The two A/e1 rows are duplicates; A/e3 remains a different event.
Reconcile the ledger
Owner role · Coordinator
Evidence: Four source rows become three distinct events plus one retained duplicate note.
Decision to make: Under the explicit task-ID-plus-event-ID rule, retain three accepted events and record one duplicate row.
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.
Reconciled note: three distinct acceptance events from four rows; one duplicate A/e1 excluded. Unique-task count is a separately named view.
Put the outline to work
- State whether the unit is task or accepted event.
- Compare stable identity and event evidence before removing rows.
- Keep exclusion reasons and reconcile source rows to the final count.
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.
Synthetic example · not customer data
Inspect the records
| Task ID | Acceptance event ID | UTC time |
|---|---|---|
| A | e1 | 09:00 |
| A | e1 | 09:00 |
| B | e2 | 10:00 |
| A | e3 | 15:00 |
Wide tables scroll sideways on small screens.
Download records (.csv) · Download complete decision kit (.json)
Evidence dependency diagram
What must be known first?
Scroll the diagram sideways if needed; every dependency is also written below.
- Four source rows → Event identity check: same event?.
- Event identity check → Three distinct events: retain exclusions.
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
- Stable event identities are present
- Reconcile duplicate event rows and keep other events.
- Only task IDs are available
- Use a task-level measure if justified; do not infer distinct acceptance events.
- Row identity is unclear
- Hold the event count and recover identity evidence.
Version comparison viewer
Keep the draft and its correction visible
Draft or earlier version · review its limits
Draft: four delivered tasks from four source rows.
Revised example · limits retained
Reconciled note: three distinct acceptance events from four rows; one duplicate A/e1 excluded. Unique-task count is a separately named view.
| Review boundary | Draft to review | Revised example |
|---|---|---|
| Counted unit | Raw row | Distinct accepted event |
| Repeat handling | Repeated rows counted without an identity check | Only duplicate event identity removed |
Wide tables scroll sideways on small screens.
Questions about this workflow
Why does A remain twice?
It has two distinct accepted event IDs under this stated event-count policy. A unique-task report would answer a different question.
Why preserve a duplicate note?
It explains how four source rows became three counted events and makes the exclusion inspectable.
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.