Hospitals are complicated organisations, and much of what keeps them running is administrative: scheduling, records handling, billing queries, bed and room coordination, supply requests and the daily flow of messages between departments. This article looks at the non-clinical side only. It surveys a trend that has been gathering attention in health-system operations: treating interruptions and the cost of switching tasks as a design problem for the organisation, and not simply a matter of individual discipline. Nothing here is medical guidance, and no clinical practice is discussed.
Where the conversation stands
For years, advice about attention in busy workplaces focused on the individual: manage your time, avoid distractions, try harder. In recent years, operations writing across many sectors has moved toward a different view. If a role is structured so that a person must answer a phone, serve a counter and watch an inbox at the same moment, then willpower is not the main lever. The structure is.
Healthcare administration has taken an interest in this shift for obvious reasons. Administrative teams there manage high volumes of time-sensitive requests, and the work involves detail that is easy to get wrong if a task is dropped halfway. Researchers who study interruptions in complex work settings, including health-system operations, have consistently reported that interrupted tasks take longer to resume and are more prone to omissions. The size of the effect varies by task, which is why careful teams measure their own patterns before drawing conclusions.
Trend one: measuring switches before redesigning work
A growing number of operations teams begin with observation. Staff keep simple tallies of how often they move between tasks and what caused each move. The data is rough, but it turns a vague sense of being overloaded into a picture: which hours are most fragmented, which channels cause the most hops and which request types are scattered across the day.
The better versions of this exercise are lightweight and anonymous, with the focus on the process. When staff sense that the tally is about spotting pattern problems, they engage with it; when it feels like surveillance, they do not.
Trend two: grouping similar administrative requests
A second trend is organising work by request type. Rather than each person handling whatever arrives next, teams assign blocks for scheduling changes, document requests, billing questions and similar categories. Moving between similar items costs less attention than moving between unlike ones, so grouping reduces the mental reload. Teams still need a fast path for urgent items, and the most thoughtful designs spell out what counts as urgent so that the exception does not swallow the rule.
Role splitting accompanies this. One person covers live contact, such as the phone and the counter, while another works a protected block on written requests, and the roles swap at set times. This turns an all-day fragmentation problem into a rotation.
Trend three: windows for messages and a single queue
Internal messaging has multiplied the number of channels a person watches. The response, increasingly, is to define windows for checking messages and to funnel requests into a single queue with a named owner. This does not mean slower service. Many teams find that a predictable reply window of a few minutes for non-urgent items is acceptable to colleagues, and it gives staff long uninterrupted stretches for detailed work.
Clear urgency flags matter here. If everything is marked urgent, nothing is, and the window approach breaks down. Agreeing on a short list of genuinely time-critical categories keeps the system honest.
Trend four: better handovers and stopping notes
Shift handovers have long been a focus of hospital operations, and the same thinking is being applied to the smaller handovers inside a day. A one-line stopping note when a task is left unfinished, saying where it stands and what comes next, lowers the cost for whoever resumes it, whether that is the same person an hour later or a colleague on the next shift.
The format is deliberately plain. The value is in consistency, because a handover that looks the same each time is easy to read quickly. Teams that adopt it report fewer follow-up calls asking what has been done, though the accuracy of such reports depends on how each team measures.
Trend five: fewer tools, not more
Technology investment in hospitals is a constant theme, and a quieter lesson from operations is that every added system can add another place to look. Pieces on technology in care settings, such as an overview of heart-monitoring technology in hospitals, illustrate how much the field values tools; the operations point is that the surrounding workflow must keep the number of windows and queues to a manageable level. Consolidating where requests arrive often helps more than adding another dashboard.
Outside healthcare, even business-facing sites such as BHASO, which presents web, cloud and AI services for companies, speak in terms of keeping related digital work together. The common thread is that integration is useful when it reduces the number of places a person has to hold in mind.
Why hospitals are a useful test case
Few workplaces combine so many request types, so many channels and so many people relying on timely answers. A scheduling change may involve a department, a records team and a person waiting for confirmation. A single administrative thread can touch three desks. Because the volume is high and the details matter, even modest reductions in avoidable switching are noticeable, and the organisation has plenty of data points against which to compare.
That same complexity is also a caution. Interventions that work on a small outpatient desk may not suit a large central scheduling office, and the other way round. Pilots, in the sense of trying a change in one team for a few weeks, are the usual sensible route.
Staff experience as a measure
Alongside counts of switches, some teams close the week by asking staff how often they felt they had lost their place. Subjective measures are imperfect, yet they pick up something the tally misses, namely how fragmented the day felt. Where the two measures move together, a team can be more confident that a change is working. Where they diverge, the difference is itself a useful prompt for discussion.
How strong is the evidence?
Limits deserve a plain mention. The body of work on interruptions is wide, and the direction of its findings is fairly consistent, but results from one workplace do not transfer automatically to another. Few published studies measure administrative desks specifically, and many available accounts are case descriptions instead of controlled trials. A responsible team treats any practice as a hypothesis, tests it on a small scale and checks whether its own measures improve.
Equally, the trend does not promise that switching can be removed. Some interruptions are essential, particularly where timing matters, and well-designed processes keep a clear route for them. The objective is to make necessary interruptions deliberate and to remove the avoidable ones.
What this means for operations managers
- Start with a short, anonymous baseline of switches and their causes.
- Group routine requests by type and assign blocks where the work allows.
- Split live contact from written work, and rotate the roles.
- Set message windows and define a short urgent list.
- Standardise stopping notes and handovers.
- Keep tools and queues to a minimum, and review the count periodically.
Material about safety culture in specialised units, such as a guidelines article for families of patients in a cardiac ICU, is a reminder that structure, clear roles and predictable communication are valued across hospital settings. The same instincts apply to the administrative side, where they take the form of clear queues and clean handovers.
Costs and trade-offs to expect
Nothing here is free. Block-based working can lengthen the wait for a non-urgent reply, role rotation takes planning, and a tidy single queue needs someone to keep it tidy. Teams that go in expecting those trade-offs tend to handle them calmly, by agreeing in advance on acceptable reply times and by reviewing the arrangement after a few weeks. Those that expect an instant, painless gain are more likely to abandon the effort at the first awkward day.
Looking ahead
Expect more attention to attention itself. As hospitals continue to digitise administration, the number of channels that compete for staff focus is unlikely to shrink on its own, so deliberate design will matter. The teams most likely to benefit are those that measure first, change one thing at a time and treat the cost of switching tasks as a feature of their processes that can be improved.