Why fairness starts with the rules, not the roster
Most complaints about rostering are not really about one late shift or one early start. They come from people feeling the process is unclear, uneven, or changed without warning. If your team does not understand how shifts are assigned, swapped, and approved, even a sensible roster can feel unfair.
That is why the first step is to set out the rules in plain language. Keep them short, make them visible, and apply them the same way every week. In South Africa, rosters should also sit within the Basic Conditions of Employment Act in general terms, so working hours, rest periods, overtime and notice are handled properly. That is not about legal jargon, just basic discipline.
Make scheduling visible enough for everyone to follow
People trust a roster more when they can see how it was built. That does not mean sharing every private detail, but it does mean showing the important parts clearly: who is working, when the shift changes, and what the process is for requests and swaps. If the logic is buried in one manager's notebook, staff will fill the gaps themselves.
- Use one clear roster view for the team, not several versions in circulation.
- Set cut-off times for swap requests and late changes.
- State who approves changes and how the approval is confirmed.
- Keep notes on why exceptions were made so the same rule can be used next time.
When rules are visible, the conversation changes. Instead of asking why one person got a better shift, staff can see the pattern for themselves.
Shift swaps work better when the process is consistent
Shift swaps are often where fairness breaks down. One person gets an easy approval, another is told to wait, and the whole team starts comparing treatment. A clear swap process helps prevent that. It should say what can be swapped, who can swap with whom, and what needs manager sign-off.
A fair process also protects service levels. If a swap leaves a floor short-staffed or puts the wrong skill mix on site, then the issue is not fairness it is planning. The aim is not to approve every request, but to apply the same standard every time and avoid last-minute surprises.
- Allow swaps only when both employees agree.
- Check that the replacement is suitable for the role and site.
- Record the change immediately so the roster stays current.
- Keep the same approval steps for every department or branch.
Messages should reduce confusion, not add to it
A roster can look fair and still cause frustration if people miss updates. A short message at the right time can save hours of back-and-forth. The key is to keep messages practical and direct, especially when shifts change at short notice because of absenteeism, load shedding, a delayed delivery, or a sudden client demand.
Good team messaging should answer three things: what changed, who is affected, and what the team should do next. If the message is too vague, staff will ask the same question again and again. If it is too long, they may ignore it. Short, specific messages work best and help managers avoid repeat explanations.
Local example: a Johannesburg team with mixed shift needs
A service team in Rosebank with staff rotating between office hours and site visits had regular complaints about fairness. The issue was not the number of shifts alone, but the fact that the rules changed depending on who was on duty. Some staff were told about swaps by word of mouth, while others only saw the final roster the next morning.
Once the manager set a fixed process for schedule changes, the mood shifted. Swap requests were captured in one place, approval rules were explained to the whole team, and every roster was released at the same time each week. Staff still did not get every shift they wanted, but they could see why decisions were made. That made the system feel fairer, which matters just as much as the final roster.
Simple activity planning can support team buy-in
Team activities are often treated as a separate item from rostering, but they can help people feel included when done properly. A short quarterly session, a site huddle, or a practical team exercise gives managers a chance to explain how shifts are planned, hear concerns, and reset expectations before small issues grow. It also helps in larger businesses where teams are spread across Johannesburg, Cape Town, Durban, Pretoria, Bloemfontein, Midrand and Sandton.
Use activities to reinforce the same fairness rules, not to replace them. People remember what is repeated in a simple way. If the message is consistent, they are more likely to accept the roster even when it is not perfect for them personally.
- Use team sessions to explain the roster cycle for the next period.
- Repeat the swap rules and approval steps at the same time.
- Invite questions before the new roster starts, not after it starts.
- Keep the tone practical so staff know the process is there to help them, not police them.
Fairness is easier to maintain when the admin stays tidy
Rosters become messy when the admin is spread across notes, chats and memory. A tidy process helps managers keep changes under control, train new supervisors faster, and support different sites with less confusion. That matters whether you are running one branch or several across South Africa.
At OurTeam, the focus is on practical rostering support for scheduling, shift swaps, messaging and team activities. Our setup support, training and ongoing check-ins are there to help businesses keep rules clear and visible. That way, fairness is not left to chance, and the team knows what to expect week after week.
