Every hospital enquiry desk has a moment that new staff remember for years: the third time in one morning that a caller asks the same thing, and you realise you cannot explain the answer without reading from a sheet. I hit that moment in my second week at the heart surgery information desk. This post is the write-up I wish someone had handed me then, a plain account of the enquiry desk problem I ran into and the small habit that fixed it. Nothing here is clinical. It is only about how we handle calls, forms and callbacks.
The problem: I could follow the process but not explain it
In the first few days I shadowed a colleague and nodded along. A caller wants to know what to send before an appointment, the coordinator checks the file, a note goes to the right team, and a callback is promised. It all looked simple. Then I took my first calls alone and discovered that nodding is not understanding. A family member asked why we needed a document before we could confirm a date, and I heard myself say, “That is just how it works.”
That sentence is a warning light. If you cannot give the reason behind a step, you probably have only memorised its position in a sequence. Memorised steps survive until a caller asks something slightly sideways, and then they collapse. Worse, a frightened caller can hear the difference between a person who understands the process and a person reading it out.
The diagnosis: confusion is most useful when it is fresh
My supervisor did not give me a longer manual. She asked me to write one page for the next person joining the desk, explaining the process as if they had never seen a hospital. I resisted, because I did not feel qualified. She said that was exactly the point: an expert has forgotten what was confusing, while a newcomer still remembers the exact sentence that made no sense.
Writing the page exposed three holes straight away.
- I could not say why a callback is promised at a specific stage rather than immediately. I had to go and ask, and the answer (the right team has to confirm availability first) made the whole sequence click.
- I used two different words for the same document and had never noticed. Writing for a beginner forced me to pick one.
- I had no idea what happened to a request after I passed it on. I had been treating the handover as the end of the story, when it was the middle.
None of these gaps had shown up while I was only listening. They appeared within twenty minutes of trying to explain the process in plain sentences. That is the quiet power of teaching what you just learned: the explanation is a test, and you are both the examiner and the candidate.
The solution: a one-page write-up in five parts
After that first attempt we settled on a simple shape for these write-ups. You can use it for any desk process, whether it is enquiries, appointment paperwork or travel coordination for out-of-town families.
- Start with the caller’s question, in their words. Not the department’s wording. If a family says “when will someone call me back,” that is the heading, not “post-enquiry follow-up protocol.”
- Give the shortest honest answer. One or two sentences you could say aloud on a call without sounding rehearsed.
- Explain the reason behind each step. Every step gets a “because.” If you cannot write the because, that is your homework for the day.
- List what you got wrong at first. This is the most valuable section for the next reader, because it is the map of where beginners fall.
- Say what you still do not know. Honest gaps tell a reader where to ask a senior colleague instead of guessing.
Notice that the page never tells anyone what a patient should do medically. The desk is not the place for that, and a write-up about process should stay about process. If a caller asks a clinical question, the answer is always to connect them with the clinical team. Knowing where that line sits is itself something worth writing down.
What changed on the desk
The first practical change was that my calls got calmer. When I could explain why a document was needed, callers stopped hearing it as bureaucracy. The explanation took the same few seconds as “that is how it works,” but it carried respect with it. Several families said they felt less like they were being processed and more like they were being walked through something.
The second change was for the colleague who joined after me. She read my page on her first morning and came back with three questions that were better than any I had asked in my first month. The page had not replaced training. It had moved her starting point forward, and her questions pushed my page forward in turn, so it became a living document rather than a souvenir.
The third change was subtler. I started noticing holes in my understanding in real time. Mid-call I would think, “I could not explain this step in writing,” and I would make a note to find out. Teaching, even as an imagined exercise, had become a habit of self-audit.
Where to publish your own write-up
Our one-pagers live in an internal folder, which is right for anything that mentions how our own desk works. But the habit is useful far beyond a hospital. If you are learning anything new, a skill, a tool, a way of organising your week, the same method applies. If you want a public home for a write-up like this, MyBlogPad gives every blog its own subdomain and lets people share a lesson they have just picked up. By its own description it is free, and you sign in with Google. That makes it a sensible place to practise explaining things to strangers, which is a rather good rehearsal for explaining them to callers.
Common mistakes when writing up what you learned
- Holding off until you seem to know it all. By then the useful confusion is gone. Write while you can still remember what was hard.
- Writing for your supervisor instead of a beginner. A beginner needs the “because.” A supervisor needs only the outcome.
- Copying the official wording. If you paste the policy sentence, you have not tested your own understanding at all.
- Never updating it. Processes change. A write-up with a date and a name on it invites the next person to correct it.
Connecting it to the rest of the patient journey
Once I had written my own page, I started reading our other pieces with a different eye. Our explainer on how video follow-ups fit into care after an operation reads very differently when you know how the desk schedules the callbacks around it. And the article describing planning a first remote consultation before surgery makes more sense when you have taken the call that comes before it. Reading your own site as a beginner is a surprisingly good use of an afternoon.
If you are new to a desk like ours, try this tomorrow. Pick one step you currently do without thinking, and write three sentences explaining it to someone who has never set foot in a hospital. Where your sentences stall, you have found your next question. Ask it while you are still new enough that nobody expects you to know, and then write the answer down for whoever arrives after you.