You create a shift pattern as a record, then add shift pattern entries that map templates to day positions. Build your shift templates first, since the pattern references them. Then apply the finished pattern from the Shifts list view to generate shifts.
- Open Shift Patterns
From the App Launcher, enter Shift Patterns and open the list view. Click New to start a pattern.
- Set the pattern details
Give the pattern a clear name and description, set the length in days (7 for a weekly cycle), and mark it active so it can be applied.
- Add shift pattern entries
For each working day, add an entry that links the pattern to a shift template and sets the day position (1 to 7 for a week). Leave a day with no entry to make it a day off, and add two entries to one day for a double shift.
- Apply the pattern to create shifts
Go to the Shifts list view and choose New from Pattern. Select the pattern, set a start date, choose a service resource or leave it blank for open shifts, then enter an end date or number of repetitions.
A descriptive label for the pattern, like Standard Weekday Mornings, so schedulers can find and reuse it.
The number of days in one cycle. A weekly pattern is 7; a monthly pattern is roughly 28 to 31.
Marks the pattern as usable. An inactive pattern cannot be applied to generate shifts.
The template each shift pattern entry references, which supplies the start time, end time, and time slot type for that day.
Where in the cycle the entry falls, from 1 to 7 for a weekly pattern, placing the template on a specific day.
- Build shift templates before the pattern. Pattern entries cannot reference a template that does not exist yet.
- Length is always in days, not weeks. A weekly pattern is 7, so a four-week schedule is generated by repeating a 7-day pattern four times, not by setting length to 4.
- Leave a day empty to make it a day off. There is no separate off-day record; an absent entry is what creates the gap.
- Leaving the service resource blank at apply time creates unassigned shifts for demand planning, which still need a worker assigned later.
- A long date range over a short cycle can generate a large volume of shift records fast, so generate a few cycles, review, then extend.