The patient coordination desk at a mid-sized hospital, the one in this story, is imaginary, but anyone who has worked a hospital front office will recognise its Monday mornings. Four people, one shared phone line, a stack of travel enquiries from families planning a visit, and a veteran coordinator named Kavita who handled the trickiest ones in her head. This is a story about what happened when Kavita was called away for a family emergency, and how the team wrote a front-office runbook that has since kept their visitor-coordination routine steady. Everything here is administrative. It contains no clinical content, and nothing in it is medical advice.
The week the desk wobbled
Kavita left on a Tuesday. By Thursday, three families had received conflicting information about arrival-day arrangements, a request for an airport pickup had gone to the wrong colleague, and a family’s visitor paperwork question sat unanswered for two days. Nobody was careless. The team simply realised that Kavita did not follow a method so much as a feeling for how things worked, built over years.
“We kept asking each other what Kavita would do,” said Arun, the youngest member. “And none of us could answer.”
The conversation that started the runbook
On Friday afternoon, the team lead called a short meeting with one rule: nobody says “it depends” without writing down what it depends on. They picked one recurring task, handling an enquiry from a family planning to travel for an appointment, and listed everything that happened between the first email and the day the family arrived.
It was longer than they expected. Seventeen small actions, from confirming names as they appear on travel documents to noting who meets the family at the entrance. They cut it to eleven by merging small steps, and the first version of the runbook was born.
The first version, in plain words
- Log the enquiry with date, family contact name and phone number.
- Reply within the agreed working-hours window, using the standard first-reply wording.
- Ask for the appointment date and the arrival and departure dates, and confirm all of them in writing.
- Share the standard information sheet on visitor logistics, such as where to arrive, whom to ask for and desk opening hours.
- Ask whether the family needs help with local transport, and record the answer.
- Hand transport requests to the transport contact and write down who accepted the request.
- Send a written summary of every arrangement back to the family.
- Two days before arrival, call the family to reconfirm.
- On arrival day, tell the entrance desk to expect them.
- After the visit, record anything the family found confusing.
- Update the runbook page if a step needed fixing.
Clinical questions, if any came up, were referred to the hospital’s care team using a standard line; the desk never answered them.
Testing it in the wild
The page got its first real test the following Monday, when an enquiry came in from a family in another city. Arun, who had never handled one alone, followed the steps. He got stuck at step five and phoned the transport contact to ask what “local transport help” included. That question became a line in the page: a one-sentence description of what the desk can arrange and what families must organise themselves.
By the third enquiry, the page had grown a short list of standard phrases, and Arun was handling arrivals with the calm of someone twice his experience.
What Kavita thought when she came back
Kavita returned two weeks later, expecting chaos. Instead she found a binder with a dozen pages, several of them rewritten twice. She read the enquiry page standing at the desk, and said she would have added one thing: to ask about a family’s mobility needs for the arrival route, so the entrance desk could prepare a wheelchair if requested. The team added the line. It was a small, warm detail that came from years of experience, and now it belonged to everyone.
It is worth noting how much value comes from experienced people dictating what they already know. If your own team is planning how to explain costs and options to visiting families, the thinking in a plain-language look at what heart surgery costs and how to compare hospitals can feed the standard information sheet. And for the preparation side, the notes on getting ready for a heart checkup so the visit is more useful can help the desk decide what practical reminders to include, always leaving clinical guidance to the care team.
Where the habit comes from
Writing recurring work as runbooks comes from technical operations, where a fix known to one engineer is a risk to everyone. A good place to see data teams discuss this is TheDataOps.org, a blog on running data pipelines dependably. A hospital front office has nothing to do with pipelines, but the lesson carries across: write down the repeatable work.
A few things the team learned along the way
They learned that the best pages came from the most experienced person talking while someone else typed, because experts type slowly and skip steps. They learned that a page with no phone numbers on it was not really a page. And they learned to keep the wording warm: the standard first reply reads like a person wrote it, because a worried family deserves that, even when the words are reused.
What the desk does now
- Every new routine gets a page before it gets a habit.
- Every page has a date and an owner.
- Every Friday, one page is read aloud and corrected.
- Every new starter runs one enquiry from the page, with a colleague watching, in their first week.
The moral, such as it is
Nobody on the desk thinks the runbook replaced Kavita. It protected her. When she next took a few days for a family wedding, nobody phoned. The page said what to do, and the team did it. A hospital front office is a place where kindness and accuracy must work together, and a runbook is simply a way of making the accurate part reliable so the kind part has room to breathe.