# Canceled work in a delivery measurement ledger

Illustrative planning brief; no automatic product import.

Synthetic example: A week closes three records: A accepted, B canceled before acceptance, C superseded by a later request. D remains active.

## Decision

Report one accepted outcome, two closed-without-acceptance records and one open item under the written policy.

## Owned work

- Freeze finish meanings
  - Owner role: Report owner
  - Acceptance evidence: Accepted, canceled, superseded and open are separate dispositions.
- Review closure evidence
  - Owner role: Work owners
  - Acceptance evidence: A has acceptance evidence; B and C have cancellation/supersession reasons.
- Publish the reconciled ledger
  - Owner role: Delivery lead
  - Acceptance evidence: Four records reconcile without calling every closure a delivery.

## Workflow

1. Define accepted finish separately from administrative closure.
2. Classify each record using evidence available at the checkpoint.
3. Report dispositions together so excluded closures remain visible.

## Judgment

A cancellation can be a sound decision without being delivery. Do not erase it or compare closure counts with accepted throughput.


## Worked reporting note

Period note: one accepted delivery; two other records closed with reasons; one item remains open.


## Working artifact

- Observed / Four distinct dispositions / Supports the period reconciliation.
- Unknown / Value saved by canceling work / Do not invent ROI or productivity gains.
- Next check / Inspect one closure reason and one acceptance record / Keep closure and delivery criteria distinct.


## Workflow questions

### Do canceled records vanish from the report?

No. Retain them in a separate disposition count with a concise reason.

### What if a canceled item had partial work?

Preserve the partial artifact and the cancellation boundary; it still lacks final acceptance under this policy.

### Can an item change disposition later?

Record a dated correction and its evidence rather than silently altering a closed period.

## Product connection

Use this manual measurement rule as context when planning or reviewing owned work in TeamBoostAI. Confirm the fields and reports available in your account; the worksheet is not imported automatically.

Confirm account availability before adopting this manual outline.


## Worked measurement study

All example records are synthetic; manual worksheet, no automatic import.

### Inspect the invented records

Record | Disposition | Count treatment
--- | --- | ---
A | Accepted | 1 accepted outcome
B | Canceled | 1 closure without acceptance
C | Superseded | 1 closure without acceptance
D | Active | 1 open item

### Derivation

Four records = 1 accepted + 2 closed without acceptance + 1 still open. Accepted share among these records is 1/4, but this is not a productivity score.

Period note: one accepted delivery; two other records closed with reasons; one item remains open.

### Evidence boundary

Observed / Four distinct dispositions / Supports the period reconciliation.
Unknown / Value saved by canceling work / Do not invent ROI or productivity gains.
Next check / Inspect one closure reason and one acceptance record / Keep closure and delivery criteria distinct.

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