Building and publishing a roster - Pacten Guides
The roster is who is working when. Under People → Roster.
BUILDING IT
Shifts, one at a time or from a pattern
Most weeks are not new.
1
Create a shift
A time, a position, and optionally the person doing it. A shift with no one assigned is a real thing — it is an open shift, and it is visible as needing cover.
2
Or create a template
For the shifts that repeat every week. Define the pattern once.
3
Generate from templates
Builds the week from your patterns, leaving you to handle only the exceptions instead of rebuilding the same week each time.
4
Publish it
Until then it is a draft. Publishing is what makes it the roster your team is looking at.
Watch out
An unpublished roster is invisible to the people on it. Building next week and not publishing it is the most common reason somebody does not turn up — from their side, nothing was ever scheduled.
COVER
When somebody cannot work it
Two different situations.
- Open shifts needing cover — nobody is assigned yet. Visible as a group so gaps are obvious before the week starts, not during it.
- Cover requested — somebody assigned has asked to be relieved. The shift is still theirs until it is reassigned.
- Awaiting approval — a change somebody has asked for that has not been decided yet.
AVAILABILITY
People telling you when they cannot work
Better than finding out on the day.
Each person can maintain their own availability, and request changes to it. That gives you the constraint before you build the week rather than after you publish it, which is the whole point — a roster built against real availability needs far fewer swaps.
The screen also shows coverage for the week, so a week that looks full but is not is visible while there is still time to do something.
When they actually arrive
Clocking in, sites, and what the location check does.