The Rounds Journal · Quality & improvement

How to map a healthcare workflow before improving it

Trace handoffs, decisions and repeated work with a fictional outpatient example.

Written byThe Rounds editorial team
Published
Reading time5 min read

Trace handoffs, decisions and repeated work with a fictional outpatient example.

Set boundaries

Pick a process small enough to observe, such as an administrative request from receipt to confirmation. Agree when it starts and ends. Talk to people who perform each step, including the colleagues who handle incomplete or unusual requests.

Follow a normal case and an exception

A fictional referral office receives a form, checks required fields and forwards it for scheduling. If a field is missing, the form is returned and may re-enter the queue. Mark both the handoff and the return loop so time spent waiting or repeating work is visible.

Choose what to investigate

Ask where delays arise, which information was unavailable and whether the issue affects every case. Validate the map with staff across shifts and label uncertain steps. Follow internal approval and data-access procedures before observing work or piloting a change.

Read the related guide →

Draw it with the people who do the work

Put the requestor, reviewer and scheduler on separate rows. Write one action on each step and connect them in order. Use a decision point for the completeness check and mark who sends a returned request back. Keep the map simple enough for staff to correct during a short discussion.

Distinguish work time from waiting time

A form may take five minutes to review and sit in a queue overnight. Capture these as separate observations. If you only have a handful of timestamps, treat them as clues and ask when the process works differently, such as weekends or peak hours.

Validate before designing a fix

Walk through one normal request and one incomplete request with staff from both sides of the handoff. If people describe different procedures, record both and investigate when each applies. Choose a small approved test only after you can explain which delay or rework the change is intended to address.

Mark the difference between a step and a handoff

Start on paper with one row for each role. If a requester submits a form and a coordinator receives it, draw the handoff between their rows. Ask how the coordinator knows a request has arrived and which system they use to record that it has been reviewed. Put the system or queue name beside the arrow. If staff do not agree on where ownership changes, mark that difference as a question rather than drawing an ideal path that hides it.

Then add the actions performed inside each row. Use concrete labels such as “record missing information” or “send confirmation.” Broad labels like “process request” make it hard to tell which action has changed. For each action, write the input needed to begin and what the next person should receive. If an action produces no visible output, ask how colleagues know it has been completed.

Walk through three different cases

Use a fictional example in which a service receives an administrative request, checks the required fields and sends a confirmation. On a normal day, a complete request is assigned to the next available person. If a date is missing, the reviewer sends it back. If the requester sends the date in a separate message, the reviewer has to match the response to the original item. Draw the return path all the way back to the work queue so you can see where earlier checks may be repeated.

Add a third case where an item reaches the wrong queue. Ask who can redirect it and whether the elapsed time continues to be counted from the original receipt. If the team records this as a new request, its speed figures may exclude the time it spent in the wrong queue. Keep the distinction visible when discussing a baseline. The map can show whether a problem is caused mainly by ambiguous routing, incomplete information or differences in how the work is recorded.

Choose one observation that could change your proposed fix

Pick a point where you suspect work is waiting and agree how to check it. You might compare when several requests were received with when they were first reviewed, using records the team is authorised to use. Log the time between those events separately from the time it takes to do the review. Record what you can substantiate. If a timestamp is generated only when an item is closed, the map needs to show which earlier activity you cannot time from that record.

Bring the draft to the people on each side of the handoff. Ask what differs when demand is high, staff are absent or an unusual case arrives. Note those exceptions. A team can sometimes fix a routine delay while preserving a separate procedure for exceptional work. Agree who owns the updated map and when to revisit it. If you propose a test, identify the affected part of the map and one measure that would show whether the change helped without adding work elsewhere.

After an approved test, mark the steps that actually changed. Keep the original map with its date so the team can tell which findings came from the old process. The quality improvement guide explains how to review the results of a small test.

Explore more resources →