Meera joined the front office of a cardiac hospital as a coordinator, and before long she was the one every family asked for by name. She knew where the admission forms lived, which relative had called twice already, and how to calm someone who had not slept. She also stopped taking lunch breaks. This how-to follows what happened next, and it shows how a hospital enquiry desk rotation can spread the least-loved non-clinical jobs around a team. Everything here concerns office administration only. Medical questions are left entirely to clinicians.
Step 1: Name the jobs nobody volunteers for
Meera began by writing down the administrative tasks that kept landing on her. The list was not glamorous: answering the first call from an anxious family, tracking which documents were still missing, updating the visitor information sheet, and handling the end-of-day handover note. Each task mattered, and each one drained energy because it never ended.
If you try this, keep the list short and honest. Only include non-clinical duties. A good test is whether a trained administrator could do the task without any medical judgement. If the answer is yes, it can go on the rota.
Step 2: Notice who is carrying the load
Next, she marked beside each job the name of the person who actually did it. One name appeared almost everywhere, and it was hers. That is how heavy duties tend to behave in a busy office: they drift toward the dependable person, and the dependable person rarely complains. The risk is quiet. When she is away, nobody else knows which family was promised a call back.
Step 3: Build a visible hospital enquiry desk rotation
The team agreed on a simple weekly rotation. One person takes the enquiry desk, another takes document follow-up, a third takes the information sheet and the handover note. Next week, everyone moves one position. The schedule was pinned where the whole team could see it, because a rotation that lives in somebody’s head is just another hidden duty.
- Keep the cycle short enough that nobody dreads their turn.
- Pair a newer colleague with an experienced one for the first round.
- Let people swap a shift openly, with a note, rather than quietly disappearing from it.
Step 4: Share the knowledge while you share the work
The first rotation was clumsy. A colleague who had never run the enquiry desk asked Meera five questions in an hour. She was tempted to say “I’ll just do it myself.” Instead she turned the questions into a few lines at the top of the shared notes: how to greet a worried caller, which department handles which request, and a kind way to admit an answer is still pending. Over a few weeks the questions shrank. The skill had left her head and entered the team.
Reading material helps here. Families often arrive after reading about recovery at home, so it is worth knowing how your own hospital describes the pathway. A page such as the explanation of remote follow-up after cardiac procedures shows the kind of question callers bring, and it helps the person on the desk know where to point people without improvising medical answers.
Step 5: Look after the people doing the hard turns
A rotation is only fair if the heavy parts are shared, not just relabelled. Meera noticed that the Monday enquiry desk was busiest, so the team stopped giving it to the same junior colleague. They also agreed that the person on the desk gets a proper break, covered by a named colleague. Ask the group after each cycle what felt hardest, and change the plan when the answer repeats.
People who handle upset callers all day need recovery time too. That is not indulgence. A calm, rested voice on the phone is part of the service a hospital offers to families who are already frightened.
Step 6: Borrow an idea from technical operations
The pattern is not new. Technology teams that run systems around the clock learned the same lesson long ago: when one engineer always carries the pager, the knowledge and the fatigue both pile up on that person, so many teams share it on a visible rota. Consulting and support companies such as DevOpsSupport, a consultancy offering cloud and DevOps operations support, help engineering teams set up that kind of sharing. The same principle works in a hospital front office, with very different tasks.
Step 7: Review it together after a month
Four weeks in, Meera sat down with the team for twenty relaxed minutes. They asked three plain questions. Which job was the most draining? Which job did people discover they were good at? What did we learn that we would have missed if only one person had been doing it? Several colleagues said they now understood why families called repeatedly, and one found she liked the documents job more than the desk.
Write the answers down and adjust the rota. Keep it light. Perfection is not the goal; the goal is a team where no single person holds all the knowledge about how the front office really works.
What changed for Meera
She took her lunch breaks again. More importantly, when she took a week of leave, the enquiry desk did not fall apart. Colleagues knew the routine, the handover notes were readable, and families still heard back on time. The hospital’s clinicians, who had always relied on the front office without thinking about it, noticed that the office had become steadier.
If your own team is relying on one person for the hardest non-clinical jobs, start small. Pick one duty this week, share it between two people, and write down what you learn. Families who need heart care often spend long periods dealing with hospital logistics as well as worry, so material like a patient-facing overview of bypass recovery and rehabilitation can also be useful reading for new desk staff who want to understand the setting they work in.
A short checklist to finish
- List the non-clinical jobs that drain people most.
- Write beside each one who really does it today.
- Draw up a weekly rotation and pin it up where everyone sees it.
- Pair newcomers with experienced colleagues for the first round.
- Turn repeated questions into shared notes.
- Review after a month and change what is not working.
None of this requires new software or a large budget. It needs a pencil, a pinboard and a team willing to take turns on the jobs that nobody ever asked for.