Healthcare

Why Wait Times Get Long (and the Fixes That Hold)

Nobody schedules a 70-minute wait. It assembles itself out of four mechanical causes: arrivals that cluster, a front desk that works one person at a time, work done in batches, and two booking systems colliding in one lobby. Here is how each one builds a backlog, and the fixes that hold, ordered by cost.

·9 min read

The strange thing about a long wait is that nobody caused it. The providers were working the whole time. The desk never sat idle. And yet Medimap's Wait Time Index put the average Canadian walk-in clinic wait at 68 minutes in 2023, with Ontario at 59 minutes, more than double the 25 minutes of a year earlier, and Toronto the worst in the province at 72 minutes. Waits that long are not produced by slow people. They are produced by structure, which is good news, because structure can be changed.

This piece is about the why. If you want the cost of the walkaways those waits produce, that is a different article. Here we take the machine apart: where a backlog comes from, why it refuses to clear, and which repairs actually hold once the next rush hits.

Arrivals cluster. Capacity does not.

A clinic that can see six patients an hour and averages five arrivals an hour looks safe on paper. It is not, because that five is an average, and averages arrive in clumps. Nine people walk in between 4:30 and 5:30 when work lets out; nobody comes at two. During the clump, arrivals outrun service and a backlog forms. That much is obvious. The part that surprises people is what happens next: the backlog does not clear when arrivals return to normal, because normal already uses nearly all the capacity. Burning off a queue needs a genuinely quiet stretch, and on a busy day the quiet stretch never comes before close. A wait built in one bad hour is still being paid at eight in the evening.

Capacity is lumpier than the staffing sheet admits, too. Providers take breaks, a procedure runs long, a complex visit eats three ordinary slots. The margin between average demand and real capacity is thinner than it looks, which is why the same clinic can feel fine on Tuesday and drown on Wednesday with identical staffing.

Check-in is serial; arrivals are not

Before anyone waits for a provider, they wait for the desk. Arrivals happen in parallel; a counter works one person at a time. Say the after-work clump delivers five people in four minutes and each registration takes two: the fifth person does not reach the front until minute eight, waiting to be allowed to start waiting. Worse, the desk does double duty. The same person processing new arrivals is fielding how-much-longer questions from everyone who arrived earlier, so the queue's own anxiety slows the queue's intake. And on a paper sign-in sheet the failure compounds quietly: nobody timestamps the walk through the door, so those eight minutes at the counter never appear in any measurement and the clinic cannot see the stage where its wait actually begins.

Batching turns a trickle into lumps

Work done in batches saves the worker and costs the queue. Rooming patients in threes because the walk to the back is annoying. Writing up charts in a block at the top of the hour. Closing intake for a twenty minute break and reopening to a lobby that kept arriving the whole time. Each of these converts smooth flow into a lump, and the arithmetic from the first section says lumps are precisely what create backlogs. The lunchtime closure is the classic: demand does not pause when you do, so the clinic effectively schedules its own rush for 1 p.m. every single day and is then surprised by it.

No-shows and walk-in collisions waste capacity twice

A no-show is capacity wasted in the one way you cannot recover. The reserved slot sits empty while the lobby is full, because by the time the desk is certain the patient is not coming, the window to pull a walk-in forward has mostly closed. Fifteen dead minutes at 3 p.m. is fifteen extra minutes for everyone still waiting at seven.

The collision is the second waste. When appointments live in one book and walk-ins on another list, the front desk becomes the integration layer, reconciling the two by eye. A booked patient arrives on time to a lobby of walk-ins who have waited fifty minutes, and someone has to decide who goes next. Whichever way they decide, somebody feels robbed, and the deciding itself takes time the desk does not have. Two scheduling systems sharing one physical lobby will always fight; the lobby is just where the fight becomes visible.

The wait is also longer in the mind

The clock is only half the wait; the other half happens in the patient's head. David Maister's best-known observation about queues is that an uncertain wait feels longer than a known one, and the traditional lobby manufactures uncertainty by default: no posted position, no estimate, and no way to tell whether the person just called ahead of you jumped the queue or was triaged. Patients sit with nothing to do but audit the room. Forty real minutes are experienced as an hour, and the experienced wait, not the measured one, is what drives the walkout and the review.

The fixes, ordered by cost

Each cause above has a repair, and they conveniently sort by price. Working up from free is also the sensible order in which to reduce wait times without hiring anyone.

Free: measure, then tell people the truth. Time your real service time and your busiest hour instead of guessing at both, and put the current wait where arriving patients can see it. A posted 45-minute estimate is tolerated far better than a mysterious one, and an honest number shifts some arrivals to quieter hours all by itself. Wait-time software produces the measurements as a by-product, because it timestamps every arrival, call and completion.

Cheap: parallelize check-in. A QR code at the door lets ten arrivals register from ten phones at once, so the desk stops being the first queue and handles only exceptions. This kills the serialization problem outright and costs a printed poster.

Moderate: move the wait out of the lobby. A virtual queue with a live position and a text when the turn is near attacks the psychology directly, and it smooths the flow of returns so a provider is not idle while the next patient is found in the parking lot. It does not add capacity; it stops capacity leaking between visits.

Most involved: put appointments and walk-ins in one queue. One ordered list ends the collision, and it converts no-show gaps from dead time into walk-in time, because the next walk-in flows into the space automatically. This is the structural fix for the structural cause, and it is the one that holds when flu season arrives, because it does not depend on anyone at the desk making judgment calls under pressure.

Putting it together with LineMarshal

LineMarshal covers that whole ladder in one tool. Patients check in by QR code from their own phones, wait wherever they like with a live position and estimated wait, and get a text when their turn is near. The estimate is computed from the people actually ahead, the providers on shift and the time already blocked out, and on the Max plan same-day appointments and walk-ins land in one ordered queue so gaps get filled instead of wasted. It starts free for up to fifty customers served, needs no hardware, and goes live in an afternoon. The urgent care use case shows the full clinic setup.

Frequently Asked Questions

Why are wait times long even when a clinic is fully staffed?

Because arrivals cluster and capacity does not. A clinic that averages five arrivals an hour against six slots of capacity looks safe on paper, but the five arrives in clumps: a rush after work lets out, nothing at two. During the clump a backlog forms, and it clears slowly afterwards because the ordinary flow of arrivals uses nearly all the remaining capacity. Add a front desk that processes arrivals one at a time, batched rooming, and no-show gaps that nobody backfills, and a fully staffed clinic can still run an hour-long wait.

What is the biggest cause of long wait times at walk-in clinics?

Variability, not slowness. Arrivals are lumpy and capacity is flat, so any hour in which arrivals outrun service builds a backlog that persists for the rest of the day. The visible symptoms differ: a line at the front desk because check-in is serial, a wall of patients after lunch because intake closed while arrivals kept coming, or booked patients and walk-ins colliding at three in the afternoon. All of them trace back to the same root, which is demand clustering faster than the clinic can absorb it.

Do no-shows make wait times longer for everyone else?

Yes, and in a way that feels unfair: the lobby is full while a reserved slot sits empty. A no-show wastes capacity at the exact moment it cannot be reclaimed, because by the time the desk is sure the patient is not coming, the window to pull a walk-in forward has mostly passed. The fix is structural rather than moral. Put same-day appointments and walk-ins in one ordered queue, so an unused gap is backfilled by the next walk-in automatically instead of expiring while people watch it.

What is the cheapest way to make a long wait feel shorter?

Tell people the number. An uncertain wait feels longer than a known one, so showing each patient a live position and an estimated wait does not shorten the clock, but it changes the decision to walk out, which is the outcome that costs the clinic the visit. Patients who leave without being seen mostly blame the wait itself rather than anything about the care, so the cheapest fix targets exactly the thing driving the loss. It costs a QR poster and a screen, not a hire.

Why do published wait-time averages understate the afternoon peak?

Because an index like Medimap's is a full-day average, and the day is not flat. The published figure blends the dead two o'clock hour with the after-work clump, so it sits well below what a patient arriving at 5 p.m. actually experiences. The clump is also when the walkouts and the one-star reviews are decided, which means the average understates the wait precisely where the wait does its damage. A clinic that measures by hour of day usually finds a two-hour window responsible for most of it, and that window, not the average, is the thing to fix.

Can software fix a wait that is fundamentally a capacity problem?

It cannot mint capacity, but most long waits are not pure capacity problems. Software removes the check-in serialization, backfills no-show gaps with walk-ins, spreads Any Available patients across providers, and shows honest estimates that nudge some arrivals toward quieter hours. Those recover real minutes without new hires. Whatever wait remains after that is a genuine staffing decision, and the same system hands you the busiest-hour and measured service-time data to make it. A wait you can see by hour is a wait you can staff for.

Related solutions

Stop the backlog before it forms

Print one QR code and go live in an afternoon. No hardware, no contract, cancel anytime.