What this screen is for
This is the decision queue for shift changes. Each row names the employee, the move from the current shift to the requested one, the effective date and any end date, the reason given, and the status. Tabs with counts separate pending requests from those already decided.
Pending requests carry approve and reject buttons. Either decision can take a note, which is then shown against the request. Approving creates a roster assignment, so the new shift takes effect from the requested date without any further step.
When to use it
Work through it whenever the pending count is above zero, and before the effective dates pass. A request left undecided changes nothing — the person stays on their existing shift.
What you see on this screen
- Employee — who the request is for.
- Change — the current shift, an arrow, and the shift being asked for.
- Effective — the date the change would start, and an end date after it where the move is temporary.
- Reason — what the person gave as the reason; hover to read a long one in full.
- Status — the decision so far, with any decision note shown in small type underneath.
- Actions — Approve and Reject on pending rows; a dash on rows already decided.
Filters and actions
- All, Pending, Approved, Rejected — four tabs above the table. Each of the last three carries a count.
- New Request — raise a shift change on someone's behalf.
- Approve — opens a box explaining that approving creates a roster assignment so the new shift takes effect from the requested date. A note is optional.
- Reject — opens the same box, marking the request rejected. A note is optional.
Status values
- Pending — waiting on a decision; the person is still on their existing shift.
- Approved — accepted, and the roster assignment created.
- Rejected — turned down; nothing changes.
Related
- Shifts — where the shifts themselves are defined
- Attendance — where the effect of an approved change shows up