The pending queue
Clear the queue that should never have needed a 23:00 login.
Strict-clean open-shift claims and accepted swaps can clear without sitting in an after-hours pile. Leave is never auto-approved. You still publish.


Strict-clean gating only
Rest, hours, craft, scope, overlap, and leave must all pass. Conflicts, window violations, and exclusions stay in the manual queue.
Real-time and backlog
Instant approval when a claim or accepted swap is clean — or preview the pending queue on the Living Roster, whitelist what to run, undo, and finalise before publish.
Separate toggles and windows
Open shifts, swaps, and swap-with-open-shift are independent. Minimum notice, horizon, date bounds, and exclusions by stream or craft group are yours to set.
What you keep
- Whether the module is on, and for which claim types
- Time windows and exclusions
- Preview, whitelist, undo, and finalise on backlog runs
- Publication of the Living Roster
- Leave approval — always manual
Questions services ask
- Is Auto-Approve the same as IRIS Generate?
- No. Generate and Fill Gaps create assignments from your structure. Auto-Approve only approves existing open-shift claims and accepted swaps that are already strict-clean.
- Will it auto-approve leave?
- Never. Leave stays a human decision with coverage impact visible before approval.
- Is it included in my tier?
- No. It is an optional module on any tier. Contact us to grant it; your admin then sets windows and exclusions under Organizations → Add-ons.
See how an ED-first roster platform works.
From emergency departments to whole health services — and the ED-like teams beyond them.