Same deliveries. Two answers.
The difference is a promise someone changed.
Invented records. Inspectable calculations. No client data.
Change the evidence date. Then open a commitment.
9 of 12 confirmed on time
2 approved reschedules
Definition difference,11 of 12 confirmed on time
K-09’s receipt confirms delivery on 20 Oct. The evidence arrived on 23 Oct. The delivery itself hasn’t changed.
A customer-approved reschedule preceded the original deadline. It changes the operating commitment, but it doesn’t erase the first promise.
| Record | First promise | Accepted | Approval | Delivery | Receipt |
|---|---|---|---|---|---|
| K-01 | 2 Oct | 2 Oct | — | 2 Oct | 2 Oct |
| K-02 | 4 Oct | 4 Oct | — | 3 Oct | 3 Oct |
| K-03 | 6 Oct | 6 Oct | — | 6 Oct | 6 Oct |
| K-04 | 8 Oct | 10 Oct | 7 Oct | 9 Oct | 9 Oct |
| K-05 | 10 Oct | 10 Oct | — | 10 Oct | 10 Oct |
| K-06 | 12 Oct | 12 Oct | — | 11 Oct | 11 Oct |
| K-07 | 14 Oct | 14 Oct | — | 14 Oct | 14 Oct |
| K-08 | 16 Oct | 19 Oct | 15 Oct | 18 Oct | 18 Oct |
| K-09 | 20 Oct | 20 Oct | — | 20 Oct | 23 Oct |
| K-10 | 21 Oct | 21 Oct | — | 21 Oct | 21 Oct |
| K-11 | 19 Oct | 19 Oct | — | 21 Oct | 21 Oct |
| K-12 | 22 Oct | 22 Oct | — | 22 Oct | 22 Oct |
An authored example with 12 fictional commitments, each originally due from 2–22 October 2026. One commitment per row; equal weight; no cancellations, partial deliveries, time zones, or contract-specific exceptions. This is a bounded reconciliation, not an estimate of enterprise performance.
Three conversations we’d want to have.
Keep original-promise reliability visible. Acceptance of a new date doesn’t prove the disruption was costless.
Review the reschedule history and customer explanation for K-04 and K-08.
Retain accepted-commitment performance, with dated approval evidence. Don’t treat a legitimate reschedule as a data-quality defect.
Confirm who could approve each amendment and when that authority applied.
Don’t let a reporting release decide an incentive policy by accident. Keep compensation and contractual use outside this release until their owners agree.
Record the intended use, effective date, and the person authorized to resolve exceptions.
“Two approved reschedules explain the gap.”
“Delivery performance improved.”
A definition changed. The deliveries didn’t. An assistant can explain the selected evidence; publishing it or changing a promise needs a separate decision. No AI service is called.
One tells us about the customer’s first promise.
The other tells us about the commitment operations accepted.
Did we keep the first promise?
Same evidence.
Different questions.
Did we meet the accepted date?
Keep both measures, name them for the decisions they support, and publish the reconciliation beside them. Preserve the original promise and the evidence available at each review. A revised date should never silently replace either.
A single headline is easier to govern and explain. That’s a reasonable objection. Here, however, collapsing the measures would either hide the changed customer promise or penalize an operating team for missing a date the customer had already revised. We’d carry the extra measure until the sponsor explicitly resolves that tradeoff.
If the governing agreement defines delivery differently, if reschedule approvals cannot be evidenced, or if partial deliveries matter, this example’s rules aren’t sufficient. Rebuild the definition and rerun the reconciliation before using it.
Open a handoff to see what it has to carry.
Sign off both definitions, the cohort, and the amendment rule. Resolve which measure supports each decision.
Versioned measure contract and decision-use register.
Run both measures on the same bounded cohort. Preserve event dates separately from the dates evidence became available.
Row-level bridge, receipt history, and unresolved exceptions.
Test a late receipt, a withdrawn amendment, and an absent approver. Check that the backup can act within documented authority.
Observed results, defects, and the escalation route used.
Approve the intended uses and explain the change to the people evaluated by it. Retain the previous version for comparison and recovery.
Release decision, effective date, and rollback instructions.
Our call on one page.
The evidence behind it on the next.
Ready to share or print · No account required
Read the brief (PDF, opens in a new tab)That’s one example of how we think.
The interesting part is what the evidence asks of us next.