In Basket · Aging
Why are messages aging in an In Basket pool?
Aging can come from volume, unclear ownership, missing backup coverage, misrouting or an undefined escalation threshold. Measure which categories are aging before asking staff to work faster. The operational fix depends on whether the queue is overloaded or simply unowned.
First checks
Work through the workflow before escalating blindly.
- Break aging down by message category.
- Confirm primary and backup ownership.
- Check whether messages are reaching the correct pool.
- Compare current age with the approved threshold.
- Identify repeat exception categories.
Ownership questions
- Who owns aged items?
- Who covers absences?
- Who reviews recurring misroutes?
- Who decides when an item needs escalation?
Avoid making the problem worse
Common failure patterns
- Treating all aging as a productivity problem.
- Closing or moving work simply to improve metrics.
- Creating unofficial duplicate tracking systems containing protected information.
When to escalate
If aging is driven by suspected routing, access or configuration defects, package the evidence for the authorized application team. Clinical urgency remains a clinical decision.
Related resources
Continue with the closest workflow tool.
In Basket overload guide→Reporting and worklists→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.