Sources: 3 · Verified 2026-10-22
A waitlist can look busy and still fail to fill slots. The team calls many patients, but the offer order, response window, and fill outcome are not recorded. Yield is the share of opened slots that become confirmed visits through the waitlist.
Workflow at a glance
| Factor | Details |
|---|---|
| Unit | Open slot offered to the waitlist |
| Yield | Confirmed fill divided by offers |
| Window | Fixed response deadline |
| Control | No duplicate promises |
Research question and scope
The question is how to measure whether a waitlist recovers capacity. Scope covers open appointment slots offered to a waitlist in a defined period. The unit is the slot offer. The plan counts offers, responses, confirmed fills, declines, expirations, and duplicate promises, and reports the result by slot type and response window. The scope also defines when a slot counts as opened. A slot becomes open when a cancellation, a reschedule, or a schedule change releases booked time that the clinic intends to refill. A slot held for a specific follow-up is not part of the waitlist population, and neither is time the clinic never intended to offer. Each offer records the slot, the patient, the channel, the time sent, the deadline, and the outcome. A declined offer and a non-response are different outcomes, because one is a decision and the other may be a contact failure. A duplicate promise is recorded when two patients are told they have the same slot, even if one is later moved. The reporting period follows the slot's opening date, so a slow fill is visible in the period where the capacity was lost. These definitions make the yield calculable and keep the offer log auditable.
Required scheduling checkpoints
| Category | Specific Tasks | Planning Estimate / Note |
|---|---|---|
| Count offers |
| Per event |
| Set window |
| Per offer |
| Fill |
| Before deadline |
| Review |
| Weekly |
- Category
- Count offers
- Specific Tasks
- Record each open slot
- Record each patient offer
- Log the channel
- Planning Estimate / Note
- Per event
- Category
- Set window
- Specific Tasks
- State the deadline
- Record the response
- Close on time
- Planning Estimate / Note
- Per offer
- Category
- Fill
- Specific Tasks
- Confirm the visit
- Update the schedule
- Notify the team
- Planning Estimate / Note
- Before deadline
- Category
- Review
- Specific Tasks
- Calculate yield
- Inspect expired offers
- Fix the rule
- Planning Estimate / Note
- Weekly
Evidence and decision controls
| Decision factor | Manual process | Documented workflow |
|---|---|---|
| Unit | Calls made | Open slots and offers |
| Outcome | Message sent | Confirmed fill |
| Window | Open-ended | Fixed deadline |
| Control | Multiple promises | One offer at a time |
Unit
- Manual process
- Calls made
- Documented workflow
- Open slots and offers
Outcome
- Manual process
- Message sent
- Documented workflow
- Confirmed fill
Window
- Manual process
- Open-ended
- Documented workflow
- Fixed deadline
Control
- Manual process
- Multiple promises
- Documented workflow
- One offer at a time
Why call counts mislead
A team can make forty calls and fill two slots. Another can make ten offers and fill eight. Call volume measures effort, not recovery. A slot-level denominator shows whether the waitlist is converting available capacity into visits, and the expiration reasons show where the process loses. Yield and slot recovery answer different questions and should both appear. Yield describes how well the offer process converts a patient contact into a confirmed visit. Slot recovery describes how much opened capacity the waitlist actually restored, including slots that were never offered. A high yield on a small number of offers can coexist with poor recovery if most slots were never presented to anyone. A high recovery with low yield may mean the team is making many offers per fill, which is effort the clinic may want to reduce. The report should also show the share of offers that expired without a response and the time from slot opening to first offer. A slot offered late may fill, but the capacity was still at risk for most of the day. Neither number proves that the waitlist caused the fill, because a slot may have been taken outside the waitlist.
A yield report
Report open slots, offers, confirmed fills, declines, expirations, and duplicate-promise events. Add the median response time and the share of offers closed at the deadline. Stratify by slot type and time of day. A weekly review can choose one fix, such as a shorter window or a different offer order. The weekly review starts with the count of opened slots and the share that were offered at all. Then it reads the offer outcomes, the median time to first offer, and the reasons offers expired. A pattern by slot type or time of day is more useful than a single overall yield, because a waitlist may work well for short follow-ups and poorly for long new-patient visits. The team chooses one fix, such as a shorter deadline, a second contact channel, or a rule that offers the slot to the best-matched patient first. The fix is recorded with a date and compared over the next period using the same definitions. Offers that were never sent are reviewed as a demand-matching problem rather than a conversion problem. The review ends with the next question, not with a score.
Quality controls
| Success Factor | How To Do It | Results You Get |
|---|---|---|
| Offer log | One row per slot and patient | Yield is calculable |
| Deadline | Close and reoffer | No aging offers |
| Duplicate check | One promise per slot | No double booking |
| Reason review | Why offers expire | The rule improves |
- Success Factor
- Offer log
- How To Do It
- One row per slot and patient
- Results You Get
- Yield is calculable
- Success Factor
- Deadline
- How To Do It
- Close and reoffer
- Results You Get
- No aging offers
- Success Factor
- Duplicate check
- How To Do It
- One promise per slot
- Results You Get
- No double booking
- Success Factor
- Reason review
- How To Do It
- Why offers expire
- Results You Get
- The rule improves
Limits and controls
The measure depends on accurate offer and confirmation records. It does not measure patient preference or clinical appropriateness. It can be gamed by offering only the easiest slots, so report the slot mix. Duplicate promises should be counted as a control defect, not hidden in the fill rate. The measure also cannot show whether the patient who filled the slot was clinically appropriate for it. A visit type may match on paper while the patient needs a different length or provider. That judgment belongs to the clinical team and should not be inferred from a fill count. The yield can also be distorted by a small denominator, so a week with few opened slots should be reported as counts and treated cautiously. Offers sent outside the patient's stated contact preference may fail for reasons the measure records as non-response. Privacy rules apply to the offer log, which should carry only the details needed to confirm the fill and the contact attempt. The measure is a capacity signal, and it should be paired with a review of whether the right slots are being opened at all.
What this means for a scheduling team
A waitlist is a capacity tool, not a call list. Measuring yield at the slot level tells the team whether the tool works. SchedulingAppointment keeps the offer, deadline, and outcome together so the measure is possible. A call list records effort. A slot record records what happened to capacity. Keeping the offer, the deadline, the response, and the confirmed fill in one place lets the team see where a slot was lost and who was responsible for the next step. It also makes a fair review possible, because a coordinator who followed the rule is not blamed for a patient who could not be reached. The team can then change the rule rather than the person. SchedulingAppointment treats the waitlist as part of the schedule, so a filled slot and an expired offer refer to the same appointment record. That connection keeps the report honest and keeps the patient from being promised a time that was already taken. The result is a small, repeatable review that improves the rule over time. A simple review beats a polished dashboard that nobody uses.
Research methodology
This paper defines a slot-level measurement plan. It specifies the offer unit, the response window, outcome categories, and duplicate-promise controls. It does not estimate a yield rate for any clinic.
This is a measurement design. It does not report a yield rate or claim a universal offer window.
Data sources and methodology
This brief reports published findings as stated by each source. It does not combine study populations into a new benchmark; local operators should treat the figures as context and measure their own workflow.
- AHRQ: Access and scheduling: Capacity context
- CMS: Coverage: Coverage context
- NIST Privacy Framework: Data handling
Related content
Frequently asked questions
Is yield the same as fill rate?
Should declined offers count?
Can we offer a slot to two patients?
Measure whether the waitlist actually fills
If the team is busy but slots still expire, start counting offers and confirmed fills, not calls.
Book a Free Consultation →



