Quick answer
What to do
Choose one visit type and watch it from the client’s first request through the final follow-up. For each step, write down who acts, what starts the task, what information they need, which tool they use, what they produce, where work waits, and what can go wrong. Ask the staff who do the work to correct the map, then improve one point where information is lost, re-entered, or delayed instead of trying to redesign the whole clinic at once.
Start with one visit type and two clear boundaries
“Map the clinic” is too broad. Choose one kind of work, such as a new-client wellness visit, same-day sick visit, procedure drop-off, refill request, or post-visit recheck. State exactly where the map starts and ends.
A sick-visit map might begin when the clinic receives the request and end when staff complete the documented follow-up. List related work outside those endpoints separately and map it later if needed.
Watch staff do the work
With clinic approval, observe several examples at different times. Record what staff actually do, not what the written policy says they should do. Leave out client or patient details that the map does not need. Record paper, boards, inboxes, and hallway conversations, along with repeated entry, searching, and waiting.
Ask each staff member what starts the task, what information they need, how they know it is complete, and what happens when something is missing. Make clear that the team is examining the process, not grading the person doing the work.
Give every action and wait state an owner
Use one swimlane per role or working group: client, front desk, assistant or technician, veterinarian, checkout, and outside service where relevant. Put software and paper artifacts on the step, not in separate lanes. This makes duplicate entry and tool switching visible without making the diagram unreadable.
Put waiting on the map as its own step. “Waiting for a room,” “awaiting veterinarian review,” “pending result,” and “client reply needed” all consume time. Name who watches each wait and what tells that person to resume the work.
Write down what the next person needs
Whenever responsibility moves to another role, list the information that person needs. A technician rooming a patient may need the patient’s identity, reason for the visit, safety alerts, current status, and the next task. Checkout staff may need completed services, anything still pending, client instructions, and the name of the person responsible for follow-up.
Record where each detail lives and how the next person knows it is ready. If the chart contains one detail, chat contains another, and a hallway conversation is the only signal to begin, show all three on the map. Otherwise the diagram will hide the searching and interruptions staff deal with.
Map what happens when the visit does not go as planned
Add branches for late arrival, wrong contact detail, urgent change, unavailable clinician, missing consent, declined estimate, pending result, and incomplete note only when they occur in the chosen flow. Name who decides what happens next and where the exception waits.
Avoid a box labeled “handle issue.” Name the person who decides what happens and the event that lets work resume. If neither is clear, the map has exposed a specific process to fix. Put rare cases in a separate table so the main map remains easy to read.
Fix one staff-to-staff transfer and test it
Choose one problem staff can recognize: a repeated question, duplicate entry, delayed rooming, an unassigned callback, or a charge missing at checkout. Decide what information must move, who sends it, how the next person is notified, and what happens if the usual method fails. Test the change during one visit type or one shift first.
Watch the visit again and ask whether the next person received the right information at the right time. Update the map to show what actually happened. Assign someone to maintain it when the process changes.
Reusable template
One-row visit observation template
Create one row for each action, transfer between staff, or period of waiting. Fill it in while observing, then check it with the person who performs the step.
STEP — What happened, using a verb and object?
OWNER — Which role performed it or watched the queue?
TRIGGER — What event, status, or message started the step?
INPUT — What information was required, and where did it come from?
TOOLS — Which system, paper form, board, inbox, or conversation was used?
OUTPUT — What changed, and how did the next person know?
WAIT — How long or under what condition did work pause?
EXCEPTION — What commonly goes wrong, who owns it, and how does work resume?
Sources and scope
How this guide was prepared
This observation method does not define clinical care or promise faster visits. Get clinic approval before observing, protect client and patient information, and have the staff who perform each task confirm the map before changing their work. The source pages below were checked July 12, 2026.
- 1Flowchart: Workflow Assessment for Health IT ToolkitAgency for Healthcare Research and Quality / checked July 12, 2026
- 2What Is Workflow?Agency for Healthcare Research and Quality / checked July 12, 2026