In Basket & workqueues
Queues only work when ownership is explicit.
When messages or tasks age, start with who owns the pool, what counts as complete and what happens when the normal owner is unavailable.
Check the operating model first.
- Is this a personal In Basket, shared pool or workqueue?
- Who is expected to monitor it?
- What is the expected response or completion time?
- How is coverage handled for PTO, turnover and staffing changes?
- Who reviews aging work?
Common failure points
Shared pool, no named ownerEveryone can see the work, so nobody feels accountable for it.
Coverage gapTasks remain assigned to an unavailable or departed user.
Unclear completion ruleStaff do not agree on what action closes the item.
Aging work is invisibleNo one regularly reviews old or exception items.
Build a queue ownership rule.
Document the primary owner, backup owner, expected review cadence, completion rule and escalation threshold. If staff cannot answer those five items, the workflow is likely to remain fragile.
When to escalate internally
Use your authorized Epic/IT team for access, pool membership changes, security-sensitive routing, configuration changes, production defects or outages.
Need help mapping the queue?
Describe the generic ownership and handoff problem without patient messages, screenshots or identifying information.
Ask HelpEpic