Start with the record boundary
Choose one representative exception, not an entire intake process. Identify the original client submission, the request ID, the current canonical record, and the person who may correct each. Do not silently replace the original artifact with a staff interpretation; preserve a reference between them.
A service blueprint is one method for showing the relationships among people, artifacts, and process steps. The map here is a representative scenario, not evidence that another team's process or product will work the same way.
Make interpretation an explicit handoff
Intake staff may be able to mark information unclear without being allowed to infer the intended value. Name the client-clarification role, correction decision authority, record-writing owner, and client-confirmation requirement separately. A team can then distinguish “waiting for clarification” from “staff changed a record” and from “the client confirmed a correction.”
If a client does not respond, record a hold, fallback, or escalation rather than routing the ambiguity into automation. That missing decision is often the smallest coherent improvement to make before building a feature.
Walk a single map with a second operator
Use this fill-in map with a second person for ten recent, consented, or safely simulated exceptions. It makes no claim about response time, privacy, compliance, or client outcome.
| Stage | Client clarification role | Correction authority | Record-writing owner | Client confirmation requirement | Artifact or recovery |
|---|---|---|---|---|---|
| Receive | __________ |
__________ |
__________ |
__________ |
__________ |
| Detect | __________ |
__________ |
__________ |
__________ |
__________ |
| Clarify | __________ |
__________ |
__________ |
__________ |
__________ |
| Record | __________ |
__________ |
__________ |
__________ |
__________ |
| Confirm or recover | __________ |
__________ |
__________ |
__________ |
__________ |
For a missing-item workflow, see Map a Missing-Document Workflow Before Choosing a Client Portal. For text-led requests, see Map a Client Request That Begins in a Text Message.
Should every typo block a workflow?
No. The accountable service owner should define which values are consequential. The map is useful because it exposes that threshold and its recovery route before a tool turns it into an invisible rule.