Start With One Team And A Clear Purpose
Pick one team that is steady enough to give useful feedback, but not so small that you miss the usual roster pressure. A store in Sandton, a head office team in Rosebank, or a branch group in Pretoria can all work well if the manager is willing to follow the process properly.
Set one clear purpose for the pilot. It might be cleaner shift planning, faster swap handling, better message use, or simply fewer last minute changes. Keep the scope tight so you can tell whether the pilot is helping or not.
- Choose one manager to own the pilot.
- Use one roster template only.
- Keep the pilot period short enough to review properly, usually 2 to 6 weeks.
- Tell staff this is a test, not a permanent change on day one.
Check The Rules Before You Load The First Roster
Before you start, make sure the roster approach lines up with your internal policies and the Basic Conditions of Employment Act in general terms. That includes working hours, breaks, notice for changes, overtime handling where relevant, and any rules you already use for weekends or public holidays.
This is also the point to tidy up the basics. If your team works split shifts, night shifts or rotating weekends, write those rules down in plain language so everyone sees the same version. A pilot goes smoother when people know what is expected and who approves changes.
- Confirm normal shift lengths and rest breaks.
- Set a rule for swap requests and approval.
- Decide how much notice is needed for roster changes.
- Check that public holiday cover is planned in advance.
Set Up Scheduling, Messaging And Swap Handling Properly
Use the pilot to test the full day to day flow, not just the roster itself. Load the schedule, show the team how messages will be used, and agree how shift swaps should be requested and approved. If staff are used to WhatsApp groups or handwritten notices, this step matters even more because the new habit needs a clear routine.
Keep the instructions simple. One place for the roster, one place for work messages, one process for swaps. That makes it easier for teams in Durban, Bloemfontein or Cape Town to follow the same routine even when they are working different hours or different sites.
- Show staff where to find their shifts.
- Explain how a swap request should be sent.
- Set a message rule for urgent updates and reminders.
- Keep activity planning separate from shift changes, so the roster stays easy to read.
Train The Manager First, Then The Team
Do not launch the pilot without training the manager who will use it every day. They need to know how to add shifts, handle changes, approve swaps and check whether the roster is up to date before payday or a busy weekend. If the manager gets stuck, the team will lose confidence fast.
After that, run a short team session. Keep it practical and use real examples from their actual work pattern. For a retail team in Midrand or a service crew in Johannesburg, 20 to 30 minutes is often enough if the steps are shown clearly. Make space for questions and repeat the basics twice if needed, because roster habits take a little time to change.
- Manager training first.
- Use the real roster pattern for the demo.
- Show one swap, one message and one activity example.
- Give staff a simple contact route for support during the pilot.
Watch The First Week Closely And Fix Small Problems Fast
The first week tells you the most. Look for missed shifts, confusion about start times, swap requests that arrive too late and messages that are being read but not acted on. Small problems can turn into bigger ones if nobody responds early, especially when rosters are changing around load-shedding, client bookings or weekend trading.
Keep a short log of what went wrong and what was corrected. If a message was unclear, rewrite it. If the roster template was confusing, simplify it. If staff are unsure who approves changes, state it plainly. A pilot is supposed to surface these issues while the risk is still low.
- Check attendance against the roster each day.
- Note repeated errors or missed steps.
- Review whether messages are being seen in time.
- Correct the process the same week, not next month.
Review Results Before You Roll It Out Wider
At the end of the pilot, sit down with the manager and a few staff members to review the process. Ask what saved time, what caused friction and what should change before the next site joins. Keep the review factual rather than emotional. You want honest comments, even if they point to gaps in the setup.
If the pilot worked well, capture the final version of the roster template, the swap process, the message rules and the activity planning routine. If it needs more work, fix the weak points first and test again with the same team. That is better than pushing ahead and creating avoidable confusion across all branches at once. A careful pilot can save hours every week and help the whole group settle into a better pattern.
- Compare the pilot roster with the actual shifts worked.
- List the top 3 improvements before rollout.
- Confirm who will support the next team.
- Agree the date for wider rollout only after the review is done.
