IRIS Auto-Approve — Configure and Run the Pending Queue
IRIS Auto-Approve is a paid add-on that automatically approves open shift claims and accepted shift swaps when they pass strict-clean eligibility checks — no compliance warnings, no leave overlap, and within your configured time windows.
Org Admins configure the module; Roster Builders run the pending queue from the Living Roster.
Enable the add-on
- Sidebar → Organizations → your organization → Add-ons tab.
- Platform admins: toggle Available to grant the add-on to the org.
- Org admins: enable Auto-approve open shifts and/or Auto-approve swaps.
- Set Open shift window and Swap window (minimum notice, max horizon, optional date bounds).
- Add Exclusions for specific streams, craft groups, or staff who must always be reviewed manually.
Ongoing vs backlog behaviour
| Mode | When it runs | Open shift outcome |
|---|---|---|
| Real-time | Staff claim or swap is accepted | CONFIRMED or DRAFT (your setting) — staff notified per outcome |
| Backlog run | You click Run IRIS on pending queue | Always DRAFT — silent until you publish the roster |
Backlog runs are designed for clearing a queue before publish: preview first, run, review DRAFT assignments on the grid, then Undo (within the undo window) or Finalise to expire competing claims.
Process the pending queue (Roster Builder)
- Open Living Roster.
- Click IRIS Auto-Approve in the toolbar.
- Filter by stream, craft group, shift dates, and type (open shifts / swaps).
- Click Preview pending queue — review counts, then expand lists for detail.
- Expand Would auto-approve to see rows and uncheck any you want to leave manual.
- Expand Stay manual — grouped by reason with explanations (time window, conflicts, queue order, etc.).
- Click Run IRIS on pending queue — only checked rows are processed (whitelist mode).
- Review Recent runs — Undo reverts DRAFT open shift assignments and future-dated backlog swaps; Finalise expires losing open shift claims on filled vacancies.
Strict-clean rules (all must pass)
- No rest, hours, consecutive-days, craft, scope, or overlap conflicts
- No leave on the shift date
- Within min notice and max horizon windows
- Not excluded by stream, craft group, or staff
- Open shift: normal claim (not linked release)
- Swap: accepted by both parties (direct or open swap with selected offer)
If any check fails, the item stays in your manual Approvals queue.
Queue ordering
Open shift claims on the same vacancy are processed first-in, first-out by request time. If the vacancy has one slot and two eligible claimants, the earlier claim auto-approves and the second shows No open slots remaining — expected behaviour, not a bug.
Roster Builder scope
Roster Builders see only streams and craft groups they are permitted to manage in the preview and run filters. Org Admins see the full org queue. If you cannot find an item, check your Roster Builder Permissions or ask an Org Admin to run the backlog.
Notifications by mode
| Mode | Staff notification |
|---|---|
| Real-time + CONFIRMED | Staff notified immediately when the claim or swap auto-completes |
| Real-time + DRAFT | Assignment created silently — staff see the shift when the roster is published |
| Backlog run | Always DRAFT — no staff emails on run; review on the grid, then publish |
Leave requests are never auto-approved — they always go through Leave Planner.
Publish integration
When you publish the roster, any completed backlog jobs covering that date range are auto-finalised — competing pending claims on fully filled vacancies expire. You can also click Finalise on a recent run before publish.
Backlog job statuses
| Status | Meaning |
|---|---|
| Running | Job in progress |
| Completed | Run finished — review results or Undo |
| Failed | Unexpected error — try preview again or approve manually |
| Undone | Reverted — DRAFT assignments and future backlog swaps rolled back |
| Finalised | Losing claims expired on filled vacancies |
Skip reason reference
When preview shows Stay manual, expand the reason group for detail. Common codes:
| Reason | What it means | What to do |
|---|---|---|
| Auto-approve disabled | Open shifts or swaps toggle is off | Enable under Add-ons → IRIS Auto-Approve |
| Stream, craft group, or staff excluded | On your exclusions list | Remove exclusion or approve manually |
| Outside selected craft group filter | Preview craft filter hides this row | Clear filter or approve manually |
| Outside configured time window | Too soon, too far ahead, or outside date bounds | Adjust windows or approve manually |
| Not a standard claim | Non-normal request type | Review in Shift Deck → Approvals |
| Linked release request | Claim tied to releasing another shift | Always manual — review linked context |
| Compliance or eligibility conflict | Rest, hours, overlap, craft, or scope issue | Check Live Eligibility in Shift Deck |
| Staff on leave | Pending or approved leave on shift date | Approve manually only if overriding leave |
| No open slots remaining | Vacancy full or lower queue priority | Expected queue behaviour |
| Shift already started or passed | Stale queue item | No action needed |
| Request no longer pending | Vacancy or request changed since queued | Refresh Shift Deck |
| Swap not yet accepted | Awaiting staff acceptance | Wait or approve once accepted |
| Swap failed strict-clean validation | Dry-run found conflicts | Review in Shift Deck → Approvals |
| Unexpected error | System error during evaluation | Retry preview or contact support |
Audit trail
- Organization → Logs & Audit → Activity → IRIS Auto-Approvals — filterable history with CSV export
- Assignments and swaps show an IRIS Auto-Approved badge on the Living Roster and Shift Deck
- Reports → Assignment Intelligence includes an IRIS Auto-Approved column
Tips
- Preview before every run. Window rules are evaluated at run time, not when the claim was submitted.
- Expand skip reasons in the preview to understand why items stay manual (time window, conflicts, queue order, linked releases).
- Deselect items you want to leave for manual review — only checked rows are processed on Run.
- Use exclusions for high-risk streams until you trust the filter.
- Backlog + DRAFT is the safest way to bulk-clear before publish — you keep human review on the grid.
- Swap minimum notice in Shift Swaps (Add-ons) applies when staff first request; the Swap window below controls when IRIS may auto-approve accepted swaps.