Patient-travel coordination is full of hand-offs: one coordinator starts a trip plan, another takes the evening shift, a third covers the weekend. Yet the way these changeovers are done is wrapped in comfortable myths. This article takes six of them apart. It is about the non-clinical side only, meaning enquiries, documents, bookings, transport and accommodation. A medical travel coordinator handover never concerns anyone’s treatment, and nothing here is medical advice. If it sounds blunt, that is deliberate: these myths cost real time and goodwill every week.
Myth 1: “I’ll just tell them when I see them”
Reality: spoken briefings fade. The coordinator arriving for the next shift hears ten things at the door and retains four. Worse, the busiest changeovers are the ones where the outgoing person is already late for the exit. A spoken word is a nice addition, not a record. Write the open items down in one shared place, date them and let the speech add emphasis only.
Do this: keep one standing page, newest entry on top, and require the reader to confirm they have read it before the writer leaves.
Myth 2: “It’s all in the system”
Booking tools hold bookings. They do not hold the promise you made on the phone, the caller who asked not to be rung before noon, or the fact that the pickup vendor tends to confirm drivers late. The system is where facts live, and the handover is where the context lives. Coordinators who rely only on the first are surprised again and again by the second.
Do this: add a “watch out for” line to every handover, containing what the system cannot tell the next person.
Myth 3: “Names are enough to know who to ask”
“Ask Ravi” works until Ravi is on leave. The next coordinator, who has met Ravi once, is stuck. Names also go out of date as teams change. Roles are sturdier: the accounts desk, the records room, the airport transfer vendor’s dispatcher. A role keeps pointing to the right place even after the person in it changes.
Do this: list contacts by role and department, and update the role list monthly.
Myth 4: “A longer note is a better note”
Many coordinators respond to the fear of missing something by writing everything. The result is three pages nobody reads. Quality depends on structure, not length: finished, open, where kept, cautions, who to ask. Every unfinished item closes with one concrete step for the reader to take. If a line does not help the reader act, it goes.
Do this: cap the entry at about one screen and put anything with a deadline at the top, with the time.
Myth 5: “Travel details stay true once confirmed”
Flights change, rooms are reassigned, drivers swap. A line that was accurate on Tuesday can be wrong on Thursday, and the next coordinator has no way to know. The fix is tiny and effective: record when each line was last checked. The reader then knows which items to trust and which to reconfirm.
For an idea of how many details one overseas trip generates, see our overview of the practical questions people raise before travelling for a procedure. Each of those questions can become a line a coordinator must carry across a shift change.
Do this: add a “last checked” time to every travel and accommodation row.
Myth 6: “Handover is the outgoing person’s problem”
The writer carries most of the work, but the reader shapes the quality. An incoming coordinator who skims the page, or who is shy about saying “this line is unclear”, lets gaps slide. The best teams treat the handover as a two-way exchange: the writer provides, the reader tests, and anything unclear is fixed on the spot.
Do this: ask the incoming person to name the first action they will take from the page. If they cannot, the note needs work.
Why the myths persist
Few of these ideas are held out of laziness; they are held out of habit, and habit is hard to see from inside a busy shift. They are comfortable. They let busy people skip a ten-minute task, and the cost is paid later by someone else. That deferred cost is invisible on any given day, which is why teams rarely connect an irritated caller on Wednesday to the careless changeover on Tuesday. Making the cost visible is the first step. Keep a simple tally for a fortnight of repeated questions, late callbacks and “where is that kept?” moments and let the numbers speak, whatever they turn out to be.
A changeover, step by step
To show how these corrections fit together, here is an ordinary changeover on a travel desk. At a quarter to six, the outgoing coordinator stops taking new calls and spends ten minutes finishing the page. She moves two closed items to the archive, updates the three open ones with their next actions, and adds a caution about a transfer vendor that has been slow to confirm. She puts the one item with a same-evening deadline at the top and writes the time beside it.
At six, the incoming coordinator reads the page while she is still in the room. He says aloud what he will do first, which is to chase the vendor, and points out one line that says “documents sent” without saying to whom. She clarifies it and updates the line. They spend perhaps four minutes talking, and nothing important lives only in the conversation.
At five past six she leaves. By ten past, he has made the first call. No family is told to wait while somebody works out what happened earlier in the day.
Bad habits to retire this month
- Leaving notes on personal phones or in private message threads where colleagues cannot see them.
- Using “as discussed” or “the usual way” as if the reader had been there.
- Saving the note for the last thirty seconds of the shift, when the day’s detail has already blurred.
- Recording opinions about callers instead of simple, respectful preferences.
- Letting old, closed items pile up until the page is too long to scan.
Each of these is easy to drop once a team agrees on it together. The agreement, not the tool, is what makes a handover reliable, and it costs nothing but a short conversation.
The technical-world parallel
Short engagements elsewhere suffer from the same myths. A specialist hired for a defined period often assumes the work “is all in the repository”, then leaves, and the next team spends weeks re-discovering the context. Organisations seeking such help sometimes browse the DevOps FreeLancers site, a portal grouping freelancers under each country, a setting of short assignments, and the lesson applies in the same way: the engagement is only complete when the successor can carry on.
A starter template that busts all six
- Finished: what is closed, with dates.
- Open: each item, its state and its blocker, ending in a next action.
- Where kept: real folder and register names.
- Watch out for: what the system cannot tell you.
- Who to ask: roles, not just names.
- Last checked: time stamps on anything travel-related.
If your team also helps families compare options, our guides on what accreditation can and cannot tell you about a hospital overseas and why side-by-side hospital comparison matters show how many separate threads sit around one journey, and why a tidy transfer between coordinators keeps them together.
The practical bottom line
It also helps to say the quiet part out loud: a clean exit is a courtesy to the family as much as to the colleague, because the family is the one who feels every dropped thread. None of this needs new software. It needs a fixed format, ten minutes at the end of each shift and a habit of leaving things in the state you would want to inherit. Drop the myths, adopt the six-line template, and the next time the desk changes hands the family on the other end of the phone will not notice, which is exactly the goal.