Clinical Operations

Rescheduled Consults: Keep the Original Access Clock

•
November 1, 2026
Behavioral health clinic corridor connecting clinical and administrative workspaces

Measure rescheduled psychiatry consultation access with a fictional timeline, separate waiting clocks, pending cases, and a buyer acceptance exercise.

Rescheduling a psychiatry consultation should preserve the original request clock while recording each offered, booked, changed, and attended date as a separate event.

A report can show a shorter wait simply because a reschedule replaced the original booking date. Another can overstate staff delay by measuring from an old request without explaining a person's chosen later time. Buyers should keep the person's overall elapsed time visible while identifying what each dated event actually establishes.

Psychiatry rescheduled consultation access clock

Choose the start and end events for each measure. Request-to-first-offer, request-to-first-booking, request-to-attended-consultation, and booking-to-attendance answer different questions. Label calendar versus working-day calculations explicitly if both are used. The fictional example uses calendar days and does not establish a clinical access standard or a universal acceptable wait.

Work the fictional consultation timeline

A request arrives November 2. Staff offer November 10 on November 4, and the person books it the same day. On November 8, the clinic moves the visit to November 17. The person attends on the 17th. Request-to-first-offer is two days; request-to-attendance is 15 days; final booking action-to-attendance is nine days. These values are all meaningful if accurately labeled. Replacing the November 2 start with November 8 would erase six days of the person's experience.

Separate the cause of change from the patient's outcome

The clinic's change and a patient-requested change should have different supported explanations. Both can affect the attended date without resetting the receipt clock. Do not infer the reason from who edited the calendar: an employee may enter a change requested by the patient. Record the actual evidence and preserve an unknown category. A later date chosen by the person still belongs in the request cohort, with the choice explained rather than removed.

Keep pending consultations in the selected cohort

At the cutoff, some requests have not yet reached an attended consultation. Show their number and elapsed time separately from completed waits. Reporting only attended cases can make the process appear faster when long-waiting requests remain unresolved. A future booking is progress but does not establish its eventual outcome. Define how requests closed without consultation are represented so they do not vanish from the population.

See this working in Ease.
Book a demo

Use the timeline to diagnose the right constraint

A two-day first offer and a 15-day attended consultation point to different questions from a 15-day delay before any offer. Review actual appointment supply, changes, preferences, and unresolved prerequisites. Clinical prioritization and decisions about appropriate alternatives stay with authorized clinicians. A scheduling metric can guide investigation without determining clinical urgency or proving that software caused the observed delay.

Work through the fictional acceptance exercise

Use a five-event request-to-attendance timeline and a three-clock calculation that preserves the original request date through a clinic-initiated reschedule. All examples below are fictional.

Exercise Starting evidence Required action Failure to expose
Early offer The request arrives November 2 and first offer occurs November 4 Calculate request-to-first-offer as two calendar days The offered visit date becomes the offer-event date
Clinic change The clinic changes the visit on November 8 Preserve the request clock and the change cause The reschedule resets total elapsed time
Patient choice The person chooses a later offered time Retain the request and explain the preference Patient choice removes the case from the cohort
Pending visit A consultation remains booked after the cutoff Report attendance pending and current elapsed time Future care is counted as completed access

Boundary 1: Early offer

The date the option was communicated and the date of the proposed visit are different facts.

Boundary 2: Clinic change

A changed booking creates another event; it does not remove the earlier portion of the person's access experience.

Boundary 3: Patient choice

The explanation adds context without changing which requests were originally selected.

Boundary 4: Pending visit

The cohort should show what is known now while preserving the later outcome as still unresolved.

Want to see it with your own workflows?
Book a demo

A second reschedule lengthens one clock but not another

The request arrives November 2. The first offer is communicated November 4 for a November 10 consultation, which is booked that day. A clinic change on November 8 moves it to November 17. The original specimen would have produced 15 calendar days from request to attendance if the consultation occurred on the 17th.

On November 15, the person requests November 24 because the 17th no longer works. That later time is confirmed, and the consultation occurs November 24. Request-to-first-offer remains two days: nothing about the later changes alters when staff first communicated an option. Request-to-attendance becomes 22 days, from November 2 to November 24. Final booking-action-to-attendance is nine days, from November 15 to November 24.

The timeline now explains one clinic-initiated move and one patient-requested move. It contains one request and one attended consultation, not three completed consultations. At a November 20 cutoff the case would still be pending with 18 days elapsed; its eventual 22-day completed interval was not yet known then.

Resetting the request date to November 15 would report nine days as the whole access experience. Removing the case because the person chose the last date would suppress a legitimate member of the receipt cohort. Preserving the two causes adds context without rewriting the denominator or the earlier elapsed time.

Questions about your setup? Ask them on a demo.
Book a demo

Observe the work before setting a target

AHRQ’s time-and-motion method measures task duration.

AHRQ describes observation in simulated settings.

Give the synthetic timeline to admissions and an analyst without supplying the calculated results. Have them calculate the three named clocks independently, then introduce a second request still pending. They should agree on the event definitions and explain why the pending case has no completed attendance interval. Resolve differences about the date a change was entered versus the date of the actual event before accepting a report.

Questions to settle with the buying committee

Should rescheduling reset the original request clock? Preserve the original request date. Add separate measures for later events rather than erasing earlier elapsed time.

Is first-offer date the date of the offered visit? No. One describes when the offer was communicated; the other describes the proposed appointment time.

Can patient-chosen later appointments be excluded from the cohort? Keep the selected population and explain the preference. Exclusion can hide part of the actual request-to-care experience.

How should uncompleted consultations appear in wait reports? Show pending counts and elapsed time separately. Do not infer attendance from a booking or omit long-waiting unresolved requests.

Bring the specimen to a full-platform review

Bring the three-clock exercise to a scheduling and reporting demonstration. The buyer should be able to reconstruct the displayed access measure from actual events, including the rescheduled and still-pending cases.

Ease offers a unified CRM, EHR, and RCM platform for behavioral health. Use the three-clock timeline across CRM, EHR, and RCM: can reviewers reproduce the original request wait after both clinic- and patient-requested rescheduling?

See this working in Ease.
Book a demo

Related reading

Frequently Asked Questions

Should rescheduling reset the original request clock?

Preserve the original request date. Add separate measures for later events rather than erasing earlier elapsed time.

Is first-offer date the date of the offered visit?

No. One describes when the offer was communicated; the other describes the proposed appointment time.

Can patient-chosen later appointments be excluded from the cohort?

Keep the selected population and explain the preference. Exclusion can hide part of the actual request-to-care experience.

How should uncompleted consultations appear in wait reports?

Show pending counts and elapsed time separately. Do not infer attendance from a booking or omit long-waiting unresolved requests.

Want to see how Ease handles this?