Start only after the cancellation is final
Choose one consented or safely simulated cancellation. Identify the original request, the authoritative appointment record, and the person who can declare the vacancy. Do not let a message reply, a staff note, or an empty calendar display become proof that the cancellation is final.
A service blueprint is a method for showing the people, actions, and supporting processes behind a service. The map below is a representative scenario, not an observed policy or claim about another team's operations.
Walk the vacancy, not just the message
Use this fill-in map with a second operator. Make the original artifact, authoritative record, decision owner, eligibility rule, hold, and recovery confirmation visible at each stage:
- Confirm the cancellation and its authority.
- Declare one vacancy and name who owns it.
- Select an eligible candidate using a stated rule.
- Send a bounded offer without silently changing the appointment.
- Record acceptance, expiry, or a conflicting result.
- Notify the affected people and recover an unresolved case.
The smallest improvement may be a shared vacancy board or a named handoff, not a portal or automated campaign.
| Stage | Original artifact | Authoritative record | Decision owner | Eligible candidates | Hold or exception | Confirmation / recovery |
|---|---|---|---|---|---|---|
| Confirm cancellation | __________ |
__________ |
__________ |
N/A | __________ |
__________ |
| Declare vacancy | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Select candidate | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Send bounded offer | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Record acceptance or expiry | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Notify and recover | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
Stop at unknown policy
Pause the automation discussion if a cancellation is not final, eligibility is unstated, the offer timing is unknown, the person allowed to accept is unclear, or two people can appear to accept the same slot without a recovery route.
For mapping the cancellation itself, see Map a Client Cancellation Exception Before Automating It. For a request that begins outside a portal, see Map a Client Request That Begins in a Text Message.
Should the first responder offer the slot immediately?
Not by default. The accountable service owner should decide whether the cancellation is final, which candidates are eligible, and who can change the appointment record before an offer creates an expectation.