← All field notes
Field Note 004Systems4 min readBy Wilfredo Pasadilla

Why referral follow-up gets lost between inboxes and spreadsheets

An inbox can show that a message arrived. A spreadsheet can show that someone recorded it. Neither automatically establishes who owns the next administrative step.

This note uses fictional administrative examples. It describes a way to investigate workflow design, rather than a completed client engagement or a clinical protocol.

Imagine a specialty practice receives a referral package. An employee records its arrival in a spreadsheet. The package is missing information, so the employee requests it by email. A reply later arrives in a different thread while that employee is away.

Nothing has necessarily disappeared. The message, spreadsheet row, and reply can all exist while the next action remains unclear.

Separate arrival, readiness, and completion

These states answer different questions. Has the practice received the package? Is the information ready for the next authorized step? Has the receiving person accepted the handoff?

Using one checkbox for all three makes it difficult to understand where work is waiting. Define administrative states that match the practice’s process, and give each a clear entry and exit condition.

Clinical triage, urgency, and care decisions remain with authorized clinical staff. An administrative status should not imply that a clinical decision has occurred.

Assign an owner to waiting work

“Waiting for information” still requires ownership. Identify the role responsible for checking the response, the agreed follow-up point, and what happens when that person is unavailable.

The owner does not have to perform every downstream action. They need a clear responsibility for moving the item to the next appropriate step or escalating the exception.

Avoid treating an email sent as evidence that the recipient has received, reviewed, or acted on it. Those are separate events, and the workflow should distinguish the ones that matter.

Define the handoff in both directions

A useful handoff identifies what the sending person provides and what the receiving person needs. That might include an administrative status, a reference in an approved system, and an explicit next action.

Ask the receiving team how they know work is ready. If they routinely reopen an inbox and reconstruct the history, the handoff may be missing context or a completion rule.

Also define how the item comes back when information is incomplete. An exception should return to a known owner rather than become a second untracked message.

Map safely before changing tools

Start with staff descriptions, blank process templates, and fictional examples. Map the path across roles and systems without placing patient details in general-purpose planning tools.

Any proposal involving patient information, practice software, or an integration needs a separately reviewed and authorized scope. A workflow map can identify an opportunity without establishing permission or technical feasibility for a live connection.

Improve one boundary at a time

Choose a specific administrative handoff to improve. Agree on how to assess it: time spent locating status, items waiting without a clear owner, or repeated administrative touches. Establish an appropriate baseline within the authorized environment.

The change might be clearer ownership, a better manual checkpoint, or a supported tool change. Measure the effect before expanding it across the whole workflow.

Make a process map the team can review

Download the blank administrative handoff map (CSV) and open it in your spreadsheet application. Use one row per administrative state or handoff, with role names, entry conditions, the next action, and completion evidence.

This is a process-design worksheet, not a patient tracking register. Use fictional examples and leave patient names, identifiers, documents, and clinical details out. Walk through both an ordinary handoff and an incomplete-information case, including who covers the work when the usual owner is away.

Our referral handoff approach explains the potential scope of an investigation. The generalized system study considers why the apparent automation opportunity may need a different intervention.

To discuss the administrative problem, describe where work gets stuck. Please leave patient information and documents out of the initial inquiry.

Next step

Working through something similar?

Discuss your system