Scheduling · Handoffs
What should I check when scheduling is waiting on another team?
Identify the exact readiness event scheduling is waiting for. Then identify which team owns that prerequisite, how readiness is communicated, and the exception path when the expected handoff does not arrive. Avoid treating referral readiness, authorization readiness and appointment capacity as the same problem.
First checks
Work through the workflow before escalating blindly.
- Name the readiness requirement.
- Identify the team that owns it.
- Confirm how readiness is communicated to scheduling.
- Check the aging threshold.
- Use the approved exception route.
Ownership questions
- Who owns the prerequisite?
- Who confirms readiness?
- Which scheduling pool or location owns the request next?
- Who handles aged exceptions?
Avoid making the problem worse
Common failure patterns
- Duplicating appointment requests.
- Bypassing required authorization or referral steps.
- Assuming capacity and readiness are the same issue.
When to escalate
If the approved trigger should move work to scheduling but does not, send the no-PHI workflow evidence to the authorized application team.
Related resources
Continue with the closest workflow tool.
Scheduling handoff guide→Scheduling workflows→Ownership worksheet→Boundary: Your organization’s approved policy, configuration, security controls and escalation process always control. HelpEpic is independent workflow guidance, not clinical advice or official Epic support. Never send HelpEpic patient names, DOBs, MRNs, screenshots, records, passwords, tokens or confidential internal information.