Sources: 4 · Verified 2026-08-19
Published August 19, 2026. This research brief asks: When one appointment ends late, how much delay reaches later clients and which operating conditions absorb or amplify it? It defines a reproducible unit, reviews relevant external evidence, proposes a local methodology, states limitations, and reaches a bounded conclusion. It does not present a universal benchmark or imply that an observed association proves cause.
Research question and design
| Factor | Details |
|---|---|
| Evidence question | When one appointment ends late, how much delay reaches later clients and which operating conditions absorb or amplify it? |
| Unit of analysis | one provider-day sequence with planned start, actual start, planned end, actual end, and documented interruption times |
| Methodology | Observe consecutive appointments for a fixed set of provider-days. Calculate start delay at each position, then classify recovery through a buffer, shorter transition, unused opening, alternate resource, or client cancellation. Compare like service types and report medians with the full spread rather than one average. |
| Conclusion | The useful result is a propagation map by service sequence, not a blame table. Adjust duration rules, transitions, and notification thresholds where repeated patterns show recoverable delay. |
Evidence question and study frame
Evidence question: When one appointment ends late, how much delay reaches later clients and which operating conditions absorb or amplify it? The population should be bounded before extraction, and the unit of analysis is one provider-day sequence with planned start, actual start, planned end, actual end, and documented interruption times. This framing prevents a dashboard total from mixing requests, appointments, messages, and client outcomes. It also forces the team to state when observation begins and ends. Eligibility rules should include the appointment types, channels, locations, and statuses in scope. Exclusions should be recorded rather than silently removed. A pilot sample is useful for discovering ambiguous fields before the full observation period. The protocol should name who can access records, how identifiers are protected, and how corrections are logged. This study is an operational measurement design. It is not a clinical trial, a forecast, or proof that one scheduling practice causes an outcome.
Evidence collection plan
| Category | Specific Tasks | Time Saved / Week |
|---|---|---|
| Protocol |
| Before collection |
| Collection |
| Observation period |
| Validation |
| Before analysis |
| Reporting |
| At publication |
- Category
- Protocol
- Specific Tasks
- state the question
- define inclusion and exclusion
- freeze the data dictionary
- Time Saved / Week
- Before collection
- Category
- Collection
- Specific Tasks
- retain raw timestamps
- record missing values
- protect identifiers
- Time Saved / Week
- Observation period
- Category
- Validation
- Specific Tasks
- rescore a sample
- inspect impossible sequences
- review unusual records
- Time Saved / Week
- Before analysis
- Category
- Reporting
- Specific Tasks
- show counts and denominators
- state limitations
- separate finding from hypothesis
- Time Saved / Week
- At publication
Descriptive evidence and unsupported inference
| Cost Factor | In-House Research distinction | SchedulingAppointment VA |
|---|---|---|
| Observed record | Timestamped event in the declared scope | Supported evidence |
| Missing field | Unknown unless validated elsewhere | Not a negative event |
| Association | Variables move together in the sample | Does not establish cause |
| Operational pilot | Prospective test with stable definitions | Useful next evidence |
Observed record
- In-house
- Timestamped event in the declared scope
- Our VA
- Supported evidence
Missing field
- In-house
- Unknown unless validated elsewhere
- Our VA
- Not a negative event
Association
- In-house
- Variables move together in the sample
- Our VA
- Does not establish cause
Operational pilot
- In-house
- Prospective test with stable definitions
- Our VA
- Useful next evidence
Evidence synthesis and relevance
Evidence synthesis: The systematic review of missed appointments shows that attendance outcomes vary across populations and settings, which cautions against treating every late start as the same event. AHRQ workflow guidance supports direct observation of handoffs and queues. The BLS occupational profile documents the coordination role of reception staff. Evidence on open access scheduling adds context about how calendar design and lead time interact with operational outcomes. These sources answer different questions and should not be pooled into one invented benchmark. Official workflow and occupational sources describe work, roles, or safety practices. Reviews and trials summarize defined populations and interventions. For this question, they justify careful definitions, direct workflow observation, and explicit communication exposure. They do not provide a universal target for a local calendar. The local evidence should therefore report counts, denominators, time windows, and missingness next to every percentage. Readers should be able to distinguish a measured event from an interpretation and an interpretation from a recommended action.
Methodology and reproducible measurement
Methodology: Observe consecutive appointments for a fixed set of provider-days. Calculate start delay at each position, then classify recovery through a buffer, shorter transition, unused opening, alternate resource, or client cancellation. Compare like service types and report medians with the full spread rather than one average. Preserve the raw event state before recoding so another reviewer can reproduce classifications. Use a written data dictionary with examples for common and borderline cases. Store not observed separately from no, because an absent timestamp is not evidence that an event did not happen. Before analysis, inspect duplicate identifiers, impossible time order, and records that cross the observation boundary. Report channel, service type, location, lead time, and day pattern when sample size permits. Pair the numeric summary with a structured review of a small set of typical and unusual records. That record review can explain process mechanisms without pretending the examples represent the whole population.
Quality checks before a conclusion
| Success Factor | How To Do It | Results You Get |
|---|---|---|
| Reproducible scope | Publish inclusion, exclusion, start, end, and unit rules. | A denominator another reviewer can rebuild. |
| Reliable coding | Rescore a sample with a second reviewer and resolve ambiguous cases. | Visible classification uncertainty. |
| Transparent missingness | Show missing fields by major subgroup and keep unknown separate from no. | Fewer false conclusions. |
| Bounded interpretation | Tie every conclusion to the measured setting and period. | Action without overclaiming. |
- Success Factor
- Reproducible scope
- How To Do It
- Publish inclusion, exclusion, start, end, and unit rules.
- Results You Get
- A denominator another reviewer can rebuild.
- Success Factor
- Reliable coding
- How To Do It
- Rescore a sample with a second reviewer and resolve ambiguous cases.
- Results You Get
- Visible classification uncertainty.
- Success Factor
- Transparent missingness
- How To Do It
- Show missing fields by major subgroup and keep unknown separate from no.
- Results You Get
- Fewer false conclusions.
- Success Factor
- Bounded interpretation
- How To Do It
- Tie every conclusion to the measured setting and period.
- Results You Get
- Action without overclaiming.
Limitations and interpretation boundaries
Limitations: Observed delay does not identify provider fault. Complex visits may appropriately run long, timestamps may be entered late, and clients can arrive after the planned start. A short observation window may overrepresent seasonal demand or one staffing pattern. Results from clinical settings may not transfer to home services. Selection bias can enter when only visible failures are recorded or when staff change behavior during observation. Documentation quality may improve during the study, producing an apparent increase in events even when operations are safer. Confounding remains likely because staffing, demand, season, service mix, and technology can change together. Small subgroups should be shown as counts rather than unstable percentages. Missing data should be reported by field and group. The analysis cannot establish causation without a stronger comparison design. Any local action should be tested prospectively with the same definitions instead of treating an initial descriptive study as a permanent truth.
Conclusion and next evidence
Conclusion: The useful result is a propagation map by service sequence, not a blame table. Adjust duration rules, transitions, and notification thresholds where repeated patterns show recoverable delay. Publish the result with a concise protocol, inclusion rules, denominator, observation dates, and versioned data dictionary. Separate supported findings from operational hypotheses. A finding describes what the records show. A hypothesis proposes why the pattern exists. An action specifies what will change, who owns it, and when it will be reassessed. This separation keeps the research distinct from a general scheduling guide. It also lets leaders revise a workflow without rewriting past evidence. The strongest next step is usually a bounded pilot that changes one control while preserving measurement. If the pattern does not repeat, retain the result as context rather than forcing a broad policy.
Research methodology
Methodology summary. Observe consecutive appointments for a fixed set of provider-days. Calculate start delay at each position, then classify recovery through a buffer, shorter transition, unused opening, alternate resource, or client cancellation. Compare like service types and report medians with the full spread rather than one average. Analysis must retain the numerator, denominator, observation window, exclusions, missing values, and version of every classification rule.
Evidence boundary: Observed delay does not identify provider fault. Complex visits may appropriately run long, timestamps may be entered late, and clients can arrive after the planned start. A short observation window may overrepresent seasonal demand or one staffing pattern. Results from clinical settings may not transfer to home services. Conclusion boundary: The useful result is a propagation map by service sequence, not a blame table. Adjust duration rules, transitions, and notification thresholds where repeated patterns show recoverable delay.
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.
- Dantas et al., No-shows in appointment scheduling: Systematic review showing substantial variation in appointment attendance evidence.
- AHRQ Digital Healthcare Research, Workflow Assessment Toolkit: Methods for understanding tasks, people, and information flow.
- Bureau of Labor Statistics, Receptionists: Description of scheduling and information coordination duties.
- Dantas et al., Open Access Scheduling Review: Systematic review of open access scheduling and outpatient outcomes.
Related content
Research interpretation questions
Does this design establish causation?
Can another organization use the result as its target?
What should accompany every percentage?
Turn the finding into a measured pilot
Choose one control suggested by the evidence, preserve the study definitions, and compare a bounded future period before making a broad operational claim.
Book a Free Consultation →