Work Schedules Overview
Plan who works when: reusable shift slots, a drag-and-drop schedule grid, and publishing that notifies the whole team at once.
How scheduling works
A work schedule covers a date range and a set of employees, with a budget and one or more shift managers. You build it by placing slots — reusable shift templates like "Morning, 6:00 AM – 2:00 PM" with their own pay code and color — onto a grid of employees by days. While you build, the schedule is Pending and only visible to managers. When you Publish, every scheduled employee is notified and the shifts appear on their dashboard.
| Status | Meaning |
|---|---|
| Pending | Being built. Editable; employees don't see it yet. |
| Published | Live. Employees notified; shifts visible on their dashboards. (The status filter on the index calls this "Approved".) |
| Cancelled | Withdrawn. The schedule is locked from further edits. |
Who can do what
| Role | Access |
|---|---|
| HR Admin / Payroll Admin | Create, edit, publish, and cancel any schedule; manage slots and schedule settings. |
| Shift managers (employees or clerks with the shift-manager permission) | Create and manage schedules; non-admin shift managers see only schedules they manage. |
| Employees | See their own published shifts on the dashboard. |
Estimated pay on the schedule grid is visible only to people with salary-handling rights, and only when the Show Estimated Pay? setting is on.
What schedules don't do
Two boundaries worth knowing. Schedules don't feed payroll directly — pay still comes from timesheets and the time clock; the schedule is the plan, not the record. And TriblockHR doesn't block conflicts: an employee assigned to overlapping shifts across two schedules gets no warning, and approved time off shows as an overlay on the grid but doesn't prevent you from scheduling over it. The grid gives you the signals (time-off and holiday markers, leave-highlighted rows); reading them is on the scheduler.
Work Schedules in 3 minutes
Save as: admin-guide__schedules__index__vid1.mp4