Begin with the observation, not a feature

Choose a safely simulated or consented, redacted scenario. Name the attendance authority and the recovery-policy owner. Then trace the work from the report through record verification, policy classification, capacity treatment, customer contact, staff action, and escalation.

Nielsen Norman Group's service-blueprint definition is used only to frame people, actions, and supporting processes. The map is representative; it does not record a real customer's attendance, charge, or business outcome.

Keep five decisions distinct

Use the reusable map to separate five questions that can otherwise disappear inside “no show”:

  1. Which record is authoritative for the attendance observation?
  2. Which named policy classifies the exception?
  3. Who makes the capacity decision, and where is it recorded?
  4. Who owns customer communication and the staff handoff?
  5. Where does a conflicting record or exception go next?

Do not prefill these cells with an assumed fee, a vendor behavior, or a result. The completed map should let another operator find the owner and next state without guessing.

Stop where ownership breaks

Pause automation if the team cannot name the attendance authority, policy, capacity decision, contact owner, staff instruction, or escalation route. A manual map can still be the smallest useful improvement while those choices are resolved.

For a cancellation exception, see Map a Client Cancellation Exception Before Automation. For cancellation-to-waitlist work, see Map a Cancellation-to-Waitlist Replacement Before Automation. For a different record mismatch, see Map Payment Captured While an Appointment Remains Unconfirmed.

Does this map recommend a no-show fee or automated follow-up?

No. It makes the people, records, decisions, and recovery handoffs inspectable before a service owner chooses a policy or tool.