Shift planning: staffing needs, rules and fairness

Why shifts create tension

Whoever organizes shifts is always under pressure from two sides. On one side there is the service to guarantee, with opening hours, peaks of activity and skills that have to be on hand. On the other there are the people, with their constraints, their preferences and a very concrete sense of what they perceive as unfair: one weekend too many, an extra night, a change announced at the last minute.

When the schedule is built every week in a spreadsheet, starting from the previous one and adjusting it by hand, the rules stay in the head of whoever fills it in. That works as long as that person is around, but it makes choices hard to explain and makes it almost impossible to check whether everyone has been treated the same way over time.

Start from staffing needs, not from people

The first step is to describe how many people are needed, with which skills, in each time slot and on each day of the week. It sounds obvious, but staffing needs are often not written down anywhere: they are inferred from last year’s schedule, with all its habits and mistakes.

Explicit staffing needs let you think differently. You can see straight away whether one slot is overstaffed and another always stretched, you can anticipate seasonal variations, and you can tell when the problem is not how shifts are organized but how many people are available. It is also the basis of any automatic check: without defined needs, no system can tell you whether a shift is uncovered.

A good starting point is a standard profile for weekdays and one for public holidays, then adjusting it for special periods.

Make rules and constraints explicit

Alongside staffing needs come the rules: minimum rest between shifts, limits on weekly hours, a maximum number of consecutive days, qualifications required for certain stations, and individual arrangements such as reduced hours or not being able to work certain slots. Many derive from the collective agreement and company agreements, others from safety regulations.

Writing them all down, so that they can be checked, is the step that makes the difference. A rule that lives only in the planner’s experience is respected almost always, but that almost is the problem. Distinguishing between hard constraints, which cannot be broken, and preferences, which you try to honor when possible, helps you build realistic schedules instead of chasing a perfect solution that does not exist.

Constraints to check on every schedule

• Minimum rest between shifts
• Maximum weekly hours
• Consecutive days
• Qualifications per station
• Individual arrangements

Fairness is measured over time

No weekly schedule can be perfectly fair: someone will work Saturday, someone will close up. Fairness should be measured over a longer period, a month or a quarter, by counting for each person the least popular shifts, such as nights, weekends and public holidays, and checking that the distribution stays balanced.

Making this count visible changes the atmosphere. Planners have an objective criterion for deciding who takes the next weekend, and those receiving the schedule can check that the load is shared. A stated, verifiable rotation avoids plenty of arguments and makes it easier to ask for availability when it is really needed.

Swaps, the unexpected and the employee app

Even the best schedule changes: an illness, an unexpected peak, a swap requested between colleagues. If changes go through messages and phone calls, the official schedule soon stops matching reality, and at month end the attendance figures do not add up. It is worth setting up a single channel for change requests and checking every swap against the same rules used for the original schedule.

Publishing the schedule with consistent notice, and communicating every change directly to the people affected, is a way of respecting their free time. An app where everyone sees their own shifts, requests a swap and receives confirmation reduces misunderstandings and lightens the planner’s workload.

In People, the schedule starts from staffing needs by time slot, checks rest periods, hours and qualifications, takes approved absences into account and is published to the employee app, where swaps are handled too. The method, however, comes first: written staffing needs, explicit rules and an honest count of the least popular shifts.

Before

• Schedule in a spreadsheet
• Swaps agreed verbally
• Rules in the planner’s head
• Attendance rebuilt at month end

After

• Schedule built on staffing needs
• Swaps requested in the app
• Constraints checked on every change
• Attendance in line with the schedule