Practice Operations
Waitlist Offer Order: Who Gets the Open Slot First
First come, first served is the wrong rule for a surgery center block. Waitlist offer order has to weigh readiness and yield, not just how long someone waited.
When a case falls off a surgery center block, someone has to decide who gets offered the slot. Most centers answer that question with whoever has waited longest, and waitlist offer order turns out to be one of the few scheduling decisions where the fair-sounding rule and the workable rule are not the same.
A freed slot at an ambulatory surgery center is not an appointment. It is a block of room time with an anesthesia requirement, a surgeon attached, equipment implications, and a set of things that must already be true about the patient before they can occupy it.
So offering it strictly by wait time produces a predictable sequence of failures. The longest-waiting patient is offered a slot on Thursday, and their pre-operative evaluation has expired, or their clearance never came back, or the surgeon on that block does not perform their procedure. Each attempt burns part of a recovery window that was already short, and the slot goes empty while three people were technically offered it.
Readiness is a regulatory fact, not a preference
The first filter on offer order is not a judgment call, and it is worth being precise about where it comes from.
Federal requirements for ambulatory surgical centers at 42 CFR 416.52 set out what has to be in place before surgery. A physician must document a comprehensive medical history and physical assessment no more than 30 days before the scheduled surgery, and the patient must have a pre-surgical assessment that includes documentation of allergies to drugs and biologicals. There is a defined window, and it either covers the offered date or it does not.
That single rule reorders the waitlist immediately. A patient who has waited four months but whose history and physical is 29 days old cannot take a slot three weeks out, while a patient who has waited three weeks with fresh documentation can take it today. Offering by wait time alone means offering slots to people who are not eligible to use them.
The useful reframe is that the waitlist has two dimensions. There is how long someone has waited, which is a fairness input, and whether they can actually occupy this specific slot, which is a gate. Gates come first, and treating fairness as a gate is what produces the empty room.
The complication: the block belongs to a surgeon, not the center
This is the constraint that makes ASC backfill different from clinic backfill, and it is the one generic waitlist logic misses entirely.
Block time is allocated to a surgeon or a practice, and a slot freed inside that block is usually not open to the whole waitlist. It is open to that surgeon’s cases. A center that offers a freed orthopedic block slot to the next general surgery patient on the list has not recovered anything, it has created a conversation about whose time that was.
The release rules are where centers differ, and they are real policy rather than convention. Some release unused block time to the general pool at a fixed interval before the date, commonly a week or two out. Some require the surgeon’s office to release it explicitly. Which rule applies, and how many days out you currently are, determines the candidate pool for that specific slot.
So offer order is really pool selection followed by ranking. GET /appointments/waitlist/{waitlistid} retrieves the entry detail needed to test a candidate against the slot’s surgeon, procedure type, and anesthesia requirement, and DELETE /appointments/waitlist/{waitlistid} clears the entry once a case is placed so the same patient is not offered a second slot the following week.
The handoff sits exactly here. When a slot is inside a block whose release window has not been reached, the automation does not reassign it. It notifies the block owner’s office that time is going unused, with the date and the candidates who could fill it, and a person decides whether to release. That is a business relationship, and no scheduling rule should make that decision silently.
Rank on what makes the case actually happen
Once the eligible pool is identified, the ranking should reflect probability of the case proceeding rather than seniority on a list.
Documentation currency comes first, because it is binary. Patients whose history and physical, clearance, and any required testing all cover the offered date go to the top. Patients whose paperwork is close to complete form a second tier worth contacting, but not worth holding the slot for.
Authorization status is the next filter and it behaves in one direction only. A case whose authorization has already returned can move to almost any date. A case whose authorization is still pending can be pushed later but not pulled earlier, which removes it from short-notice backfill entirely. Rescheduling also breaks the link between an appointment and an existing authorization, so a case moved into a freed slot needs that link re-established rather than assumed.
Then reachability, which sounds trivial and decides most outcomes. A patient who answered the last two calls within the hour is a better candidate for a Thursday slot on Tuesday than one who has never returned a call, regardless of who has waited longer. Wait time then breaks ties among candidates who are equally ready, which is where fairness genuinely belongs and where it costs nothing.
Offer in parallel, and be honest about what an offer is
Sequential offers do not fit the timescales an ASC works on, and the arithmetic is unforgiving.
A case that cancels 48 hours out leaves a window in which each sequential attempt costs a callback cycle. Three attempts can consume the entire window while the room stays booked and unused. Offering to several ranked-eligible candidates at once and taking the first confirmation is the only approach that fits.
The wording carries the weight. An offer presented as an available date, first to confirm, works and patients understand it. An offer presented as a scheduled surgery that is later withdrawn does real damage, and it damages the surgeon’s relationship with the patient rather than the center’s, which is how backfill programs get shut down from the clinical side.
One detail matters more at an ASC than in a clinic. Surgery has preparation that starts before the date: fasting instructions, medication holds, arranging a ride home, sometimes time off work. So the confirmation has to close the loop immediately with the specific instructions for that procedure and date, and the case has to be firmly booked before the patient begins preparing. An offer that stays ambiguous for a day produces a patient who fasted for a surgery that was given to someone else.
What to count, and the number that changes the conversation
Most surgery centers can state their block utilization and cannot state how much freed time was recoverable and went unrecovered. Those are different numbers and the second one is the actionable one.
Start by separating unused block time into time released to the pool and time that expired unreleased. The second category is a governance problem rather than a scheduling one, and it usually turns out to be larger than anyone assumed. No amount of waitlist automation touches it, which is exactly why measuring it separately matters.
For the released portion, track fill rate by notice window and offers per fill. Offers per fill rising over time is the signal that the waitlist has gone stale, that entries no longer reflect who still wants surgery, or that documentation currency is not being maintained on the list.
Missed appointments are moving in the wrong direction generally. In a 2025 MGMA Stat poll, 27% of practices said no-show rates had increased that year. At an ASC the cost per occurrence is far higher than in a clinic because of the committed room, staff, and anesthesia time, which is what makes recovery worth building properly rather than leaving to whoever has a free half hour.
Key Takeaways
- Apply eligibility gates before fairness. A patient who cannot legally or practically occupy the slot should never be offered it, however long they have waited.
- Check documentation currency against the offered date. The required history and physical has a defined window, and a long wait does not extend it.
- Identify the candidate pool before ranking. A freed slot inside a surgeon’s block is usually open to that surgeon’s cases, not the whole list.
- Notify the block owner when unused time is approaching release rather than reassigning it silently. That is a relationship decision, not a scheduling rule.
- Exclude cases with pending authorization from short-notice backfill. They can be pushed later but not pulled earlier, and rescheduling breaks the existing authorization link.
- Rank on reachability alongside readiness. A patient who answers calls is a better short-notice candidate than one who does not, and wait time should break ties rather than lead.
- Offer to several eligible candidates in parallel and confirm firmly before the patient starts preparing. Surgical prep begins days out and cannot be un-started.
- Split unused block time into released and expired-unreleased. The second category is usually large and no scheduling automation will touch it.
Waitlist offer order at a surgery center is a ranking problem wrapped in a governance problem. The ranking needs documentation currency, authorization status, and reachability, all of which live in different places and all of which change daily. The governance sits above it in the block release rules, and that part belongs to people. An AI team working freed slots inside athenaOne can hold the eligibility gates, rank the candidates who can genuinely take the date, offer in parallel while the window is still open, and surface the unreleased block time to the office that owns the decision.
Related reading
- what the waitlist has to know to be workable
- recovering a cancelled high-value slot
- pre-operative patient communication at a surgery center
Sources
Ready to See It in Action?
See how PGA ranks and offers freed surgical slots inside athenaOne
Schedule a Demo →Written by Kevin Henrikson