Setup Considerations: shift patterns

What this achieves

A shift pattern is a repeating cycle of shifts and rest days that you apply to a group of people over a date range. Getting the cycle right before you generate months of shifts saves unpicking a roster people have already planned around.

Decision 1: the cycle length

A pattern repeats after a set number of days, and each day of the cycle is either a shift template or a rest day.

The cycle length is the decision everything else follows from. A seven-day cycle repeats on the same weekday every week and is easy for people to remember. A cycle that is not a multiple of seven rotates through the week, which spreads unsocial shifts fairly but means nobody can predict next month without looking.

Example: a seven-day cycle at HC Corp UK Ltd puts the same warehouse employee on the same days every week. A longer cycle moves them around the week, sharing weekends across the team.

Fairness and predictability pull against each other here. Decide which one your workforce values more before you build the cycle, because changing it later moves everyone’s days.

Decision 2: how many patterns

One pattern per genuinely different rotation. Resist creating a pattern per person — that is a roster, not a pattern, and the schedule board is the better tool for individual arrangements.

Example: HC Corp UK Ltd’s warehouse runs one pattern for its standard rotation. An employee with a fixed personal arrangement is scheduled directly on the board rather than given a pattern of their own.

Decision 3: the scope you apply it to

A pattern is applied to a scope — team, department, or location — and at least one must be chosen. It reaches everyone matching.

Scope narrowly on the first run. A pattern applied to a whole department generates shifts for everyone in it, including people you may not have had in mind.

Example: applying a pattern to HC Corp UK Ltd’s Operations department covers all 18 people in it. If only a subset works that rotation, scope to their team instead.

Decision 4: what applying does to existing shifts

Applying a pattern generates shifts into a draft schedule for you to review and publish. It is not an immediate change to a live roster.

It also skips rather than overwrites. The result tells you how many holiday days, rest days, and already-present shifts it skipped, so applying over a range that already has shifts in it adds to the gaps rather than replacing what is there.

That makes a second application safe, and it means a pattern cannot be used to wipe and rebuild a period. To replace existing shifts you deal with those shifts.

Decision 5: the date range

Generating a long range in one go produces a lot of shifts to review before publishing. Generating short ranges means repeating the exercise.

Match the range to how far ahead your people need certainty. A workforce that plans childcare needs more notice than one that does not, and the roster is the thing that gives it to them.

What is expensive to change later

Decision	Cost of changing later
Cycle length on a live pattern	High. It moves everyone’s days, and people have planned around them.
Scope of a pattern already applied	Medium. Shifts already generated stay; the change affects the next application.
Which template a cycle day uses	Medium. Generated shifts keep the old template’s times.
Deleting a pattern	Low. Shifts already generated from it are unaffected.
Adding a new pattern	Low.

What happens next

Build the templates first, then the pattern that sequences them, then apply it to a scope and range. The generated draft goes to the schedule board, where you review coverage and publish. Nothing reaches employees until you publish.