Begin with what was accepted
Choose a safely simulated or consented, redacted scenario. Name the dated acceptance or closure artifact and the person who owns it. Then capture the new request in its designated channel. It may lead to review, deferment, rejection, or a separate request; it does not automatically replace the first record.
Nielsen Norman Group's service-blueprinting template is used only to frame people, actions, support processes, and evidence. The map is representative; it does not record a client, contract, or outcome.
Map the handoffs a status label hides
Use this representative fill-in map to identify the acceptance artifact, request channel, review authority, impact owner, client-contact owner, staff instruction, and escalation route. Do not prefill a row with assumed scope, price, or client consent.
| Stage | Artifact | Named owner | Visible decision or handoff | Exception or recovery |
|---|---|---|---|---|
| Accepted outcome | Dated acceptance or closure record: __________ |
Record owner: __________ |
Baseline remains readable | Missing record goes to: __________ |
| New request | Request and received time: __________ |
Intake owner: __________ |
Record separately from baseline | Clarification route: __________ |
| Review | Baseline plus request: __________ |
Review authority: __________ |
Review, defer, reject, or separate request | Authority-conflict route: __________ |
| Impact handoff | Impact note: __________ |
Operations owner: __________ |
Staff wait for disposition | Dependency route: __________ |
| Client communication | Approved status message: __________ |
Client-contact owner: __________ |
Explain next step without changing baseline | Unclear-message route: __________ |
| Resolution | Decision record: __________ |
Record owner: __________ |
Give reopened work a traceable state | Unknown-outcome route: __________ |
Stop when a handoff has no owner
Pause automation if any of those people, records, or routes are unknown. A manual map can be the smallest useful improvement while the service owner resolves the choices.
For decision delegation, see Transfer Founder Decision Rights to a Service Team. For an intake correction, see Map a Client-Data Intake Exception Before Automation. For another exception, see Map a Client Cancellation Exception Before Automation.
Does this map determine scope or price?
No. It makes records, people, decisions, and recovery handoffs inspectable. Commercial and policy decisions remain with authorised people.