The first month on an international patient desk teaches more than any induction pack, provided you capture it before it blurs. This list sets out eight things worth writing up once you have handled your first cases. Each is a piece of non-clinical coordination knowledge, such as how records move, who confirms what and how travel details are sequenced. None involves medical judgement, and none should be read as advice about any treatment. The aim is simple: explain what you learned to a new colleague, and let that explanation show you where your own understanding is thin.
Why write it up now
Explaining a process to a beginner is the quickest audit of your own grasp. If you can write a clean paragraph on a step, you understand it. If your sentences wobble, you have found a gap worth closing while somebody senior is still within reach. Writing while the material is fresh also preserves the exact points that confused you, which a more experienced colleague has long forgotten. Those points are what the next beginner most needs.
1. How an enquiry becomes a case file
Describe the journey from a first message to an opened file: what information is collected, who records it and what the sender is told to expect. A beginner should be able to follow the sequence without asking who owns each stage. If you cannot state the owner of a stage, mark it as a question rather than guessing.
2. Which documents travel, and in what form
List the document types a case commonly involves, how they are usually sent, and the practical issues that arise, such as scans that are unreadable or names spelled differently across documents. Keep to the logistics. Do not interpret any content. The value is in recording what a coordinator checks, not what a clinician concludes.
3. Who is allowed to say what
Write down the boundary between coordinator answers and clinical answers. Newcomers often feel pressure to be helpful and drift into territory that belongs to doctors. A short list of phrases that are safe to say, and a short list that should be handed to the clinical team, protects both patients and staff.
4. How time zones shape the day
International work means callbacks that cross working hours. Record how your desk decides when to call, what is promised in terms of response time, and how handovers between shifts are noted. This is the sort of detail that never appears in a manual and is learned by embarrassment, so it deserves a page.
5. The language of estimates and confirmations
Capture the exact words the desk uses when giving cost estimates and confirming dates, and why. Beginners tend to blur “estimated,” “provisional” and “confirmed.” Define each in your team’s usage, with one sentence on who may use it and when it changes.
6. What a travel coordinator needs from you
Document the information your colleagues in travel and accommodation need at handover, and the deadline they work to. Include what you now wish you had sent earlier. This single page tends to prevent more repeat calls than any other.
7. Questions families ask that you could not answer at first
Keep a running list of such questions with the answers you eventually found and the person who supplied them. It becomes a map of the knowledge network on your desk, and it shows a newcomer whom to ask about what. Where the true answer is clinical, record only the route: who it goes to and how quickly.
8. Your own mistakes, honestly stated
Close the write-up with an honest list of early errors. A missed attachment, a callback promised for the wrong window, a name entered twice. Written without drama, these are the most useful lines in the document, because they are exactly where the next person is likely to slip. They also make the page trustworthy: a guide that admits its author’s mistakes is easier to believe.
A short worked example
Suppose you are writing up item five. A weak draft says: “We give estimates and then confirm them.” A stronger draft says: “An estimate is what we tell a family before the hospital has finished its own checks. A confirmation is what we send after the relevant team has agreed in writing. If a family asks which one they have, look at the last message in the file and read out its heading.” The second version names a test the reader can apply, which is the sign that the writer has truly understood the distinction rather than merely repeated it.
Formatting the write-up so people actually read it
- Limit it to a page or two. A longer document will go unread by people between calls.
- Use the same headings every time, so readers learn where to look.
- Put the date and the author’s role on it, and invite corrections.
- Have a senior colleague review it before circulation, especially anything near the boundary between administration and clinical matters.
A note on sharing lessons beyond your desk
Anything specific to your hospital stays internal. General lessons, such as how to explain a process clearly, are worth sharing more widely. Some people publish them on MyBlogPad, a blogging network on which readers can browse community pages and each blog lives at its own subdomain address. It is described by the site as free, and sign-in is through a Google account, so a coordinator could set up a personal notebook of working lessons in a few minutes without spending anything.
How this connects to the rest of our guidance
Families reading our site want clear, honest information about hospital choices, and the desk staff who answer their follow-up questions are the human end of that information. If you are new to the desk, read our guide aimed at international patients to hear the questions families arrive with, and compare it with the step-by-step walkthrough on shortlisting an orthopaedic hospital. Both are general information pieces. Reading them as a beginner, note every term you would have to explain to a friend, and add those terms to your own write-up.
A closing suggestion
You do not need to produce all eight sections in one sitting. Begin with whichever one confused you most last week, write it in plain sentences for a stranger, and let the sentences that stall tell you what to ask next. Over a month you will have a compact handbook in your own voice, and the colleague who arrives after you will begin well ahead of where you did. That head start is the real return on teaching what you just learned.
