Map records before features
Start with one safely simulated or redacted scenario and name the outcome people need. Then list the original client or intake channel, staff-facing record, client-facing record, and external observation separately. For the external observation, record both its source and when someone observed it. A later timestamp does not by itself settle who may change the work.
Give comparison and communication different owners
The accompanying status-disagreement workflow map asks who compares the records, who may choose a hold, correction, or escalation, and the handoff trigger, sender, recipient, channel, and acknowledgement that turn a decision into staff instruction. It separately records the client communication channel and owner. These may be one person in a small team, but naming each responsibility exposes where a workflow depends on an assumption.
| Assumption | Question to make visible |
|---|---|
| The newest screen is right | Which record and timing rule does the team use? |
| Staff can proceed while records disagree | Who explicitly owns the hold or correction decision? |
| A client only needs a status update | Who confirms the approved message and next contact? |
| Automation can resolve the mismatch | What evidence and recovery route exist when it cannot? |
Stop when the disagreement has no accountable route
Pause the automation when the outcome, records, evidence time, comparison owner, decision authority, staff instruction, client-contact owner, or escalation path is absent. A shared manual decision record is often more coherent than a rule that silently chooses one system.
For an intake that began in a text message, see Map a Client Text Request Before Choosing Software. For a payment and appointment mismatch, see Map Payment Captured While an Appointment Remains Unconfirmed. For repeated requests, see Map Repeated Client Requests Before Automation.
Does this map show how a real service operates?
No. It is a representative blank artifact, not observation or policy. An authorised service owner must complete and review it before any automation or staff procedure relies on it.