The blank worksheet.
Use one row per milestone. Start with the accountable workflow owner and the decision to be made. Record the configured workflow, review date, observation cutoff, correlation method and authoritative sources alongside the sheet.
A completed worksheet may contain unresolved questions. Its value is making those questions precise and assignable. Keep observed facts, unknowns and expected conditions in their own columns.
| Milestone | Expected condition | Evidence reference | Observed fact | Unknown | Responsible role | Next confirmation | Decision affected |
|---|---|---|---|---|---|---|---|
| ________________ | ________________ | ________________ | ________________ | ________________ | ________________ | ________________ | ________________ |
Use the downloaded CSV in your approved workspace. No upload or account is required. Evidence references should point to records your team is permitted to review.
- Milestone
- Name the event or business state, such as receiving-team acceptance.
- Expected condition
- State what must be true and who agreed it. Mark an unconfirmed expectation as provisional.
- Evidence reference
- Identify the source, record, time and same-request link. State when a source is missing.
- Observed fact
- Write what the supplied evidence actually says or shows. Keep causal explanations out.
- Unknown
- Name the specific missing information; do not turn absence of evidence into proof of absence.
- Responsible role
- Name the role that can provide the confirmation. The workflow owner coordinates cross-team questions.
- Next confirmation
- Ask for the particular fact, source or interpretation needed. Track a due date with the owner.
- Decision affected
- Explain which acceptance, ownership, recovery or scope decision depends on that answer.
The completed fictional version.
FICTIONAL EXAMPLE · SYN-CANCEL-041 · observation cutoff 15 September 2026, 10:05 UTC
Read the six-artifact packet and manifest first. Expected conditions below are review criteria, not assertions about an unknown production configuration. The service obligation is explicitly unresolved.
| Milestone | Expected condition | Evidence reference | Observed fact | Unknown | Responsible role | Next confirmation | Decision affected |
|---|---|---|---|---|---|---|---|
| Service outcome | Direct cancellation or staff follow-up is explicitly agreed | SYN-CANCEL-041 manifest; 15 September 2026; cutoff 10:05 UTC; scope definition not supplied | Caller requested cancellation | Configured service obligation and allowed action | Accountable workflow owner; access-policy owner | Is the service supposed to cancel directly or request staff follow-up? Which permission rules apply? | Acceptance criteria and authorized service scope |
| Call ended | Call event meaning is documented | A1 · CALL-SYN-041 · 10:03 UTC | Call connected and ended normally | Whether this event says anything about fulfillment or receiving acceptance | Contact-center administration | What does this configured call event establish? | Whether call status supports an outcome claim |
| Caller confirmation | Completion statement matches a confirmed milestone | A2 · CONV-SYN-041 · 10:02 UTC; A5 · 10:05 UTC | AI said cancelled; appointment still scheduled at observation time | Which confirmed milestone supported that statement | AI application owner | Which confirmed milestone supported the statement to the caller? | Whether to accept the cancellation confirmation |
| Submission acknowledged | Acknowledgment meaning is established | A3 · MSG-SYN-041 · 10:02 UTC | Callback request accepted for processing | Whether acknowledgment establishes receipt, processing or business completion | Integration owner | What did the acknowledgment establish? | Whether submission evidence can support fulfillment |
| Case closed | Closure meaning is confirmed | A4 · CASE-SYN-041 · 10:03 UTC | Case closed because sent to another queue | Local closure semantics and responsibility after transfer | CRM owner | What does this closure reason mean? | Whether the closed case counts as fulfilled |
| Appointment state | Authoritative state supports cancellation by observation cutoff | A5 · APPT-SYN-041 · 10:05 UTC | Appointment remained scheduled | Record authority/freshness in a real review; any later recovery | EHR/scheduling owner | Which record establishes the appointment state, at what time? | Whether cancellation is supported at the observed time |
| Receiving acceptance | A receiving role accepts responsibility and a due window | A6 · RECEIVE-SYN-041 · 10:05 UTC | Receiving-team acceptance not established in supplied packet | Who owns the request pending acceptance; any later acceptance | Receiving-team owner; accountable workflow owner | Who owns the request until someone accepts it? | Recovery assignment, due window and escalation |
The judgments behind the rows.
- Scope comes first. The caller requested cancellation, but the packet does not define the configured service obligation. The operational owner must settle direct cancellation versus staff follow-up.
- Correlation is supplied, not guessed. The fictional manifest ties A1–A6 to one request. In your own review, document how that link was established.
- Criteria are distinct from observations. “An authoritative state supports cancellation” is an expected condition. “Appointment remained scheduled” is the observed A5 fact. Neither identifies the component responsible.
- Different closures stay different. A1 ends a call; A4 closes a case by transfer. Neither proves that the receiving team accepted the work or that the appointment was cancelled.
- Missing evidence remains unknown. A6 leaves acceptance unconfirmed. Assign the question without claiming no acceptance ever occurred.
- Time bounds the result. A5 supports the appointment state at 10:05 UTC. No later recovery or final patient outcome is established.
- Owners resolve questions, not presumed blame. The role in each row is asked for evidence or meaning. It is not a finding of fault.
The supplied evidence does not support the cancellation confirmation at the observed time. It shows a callback submission and administrative case closure while the appointment remains scheduled. Receiving-team acceptance remains unconfirmed. The packet does not establish which component caused the discrepancy or whether later recovery occurred.
Start with the accountable workflow owner.
Agree the requested outcome, observation window and decision first. Involve the contributors needed for that scope; one person may hold several roles. Record names in your own approved workspace.
- Contact-center administration: call events, queue definitions and caller communication.
- AI application ownership: the milestone used to generate a completion statement.
- CRM ownership: case states, closure reasons and transfer behavior.
- Integration ownership: message correlation and acknowledgment semantics.
- EHR/scheduling ownership: the authoritative appointment record and its observation time.
- Receiving operations: acceptance, due windows, recovery and closure outcomes.
- Access-policy ownership: who may request and perform the action, and under which conditions.
The accountable workflow owner coordinates unresolved questions across these roles. A named team is not evidence that someone accepted a particular request.