How do we set up a roster that fits our workplace
We do not give legal advice, but rosters should always be checked against the Basic Conditions of Employment Act and your own workplace policies. That matters for overtime, rest periods and public holidays, especially where teams work late, weekends or split shifts.
A simple setup is often best for first time users. Keep the template plain, use clear names for each shift and avoid too many special cases at the start. Once the team is comfortable, you can add more detail without making the roster hard to read.
- Keep public holiday handling separate from normal shifts
- Record approval steps for overtime and changes
- Use the same format for every branch or site
- Review the roster before it is published each week
Can staff swap shifts without creating confusion
Yes, shift swaps can be managed in a simple and controlled way. The aim is to let staff ask for a swap, let a manager review it, and then record the final change clearly so everyone knows what has changed.
Good swap process help reduces missed shifts and last minute confusion. A manager should always be able to see who requested the swap, who accepted it, and whether the replacement still fits the role, location and working hours. If the original shift covered a specialist task, that should be checked as well.
- Staff submit a swap request instead of making informal arrangements
- Managers approve or decline before the roster is updated
- Changes are visible to the people affected
- Swap rules can be linked to your internal policy
This is particularly useful for larger teams where one change can affect several people. It also helps during load shedding periods or peak trading times, when a missed handover can slow everything down.
What should we use team messaging for
Team messaging is useful for routine updates that need to reach the right people quickly. That could be a roster change, a site reminder, a shift start time update or a note about an activity for the team.
Keep messages short and specific. If you need people to read something before their next shift, say so clearly. If the message applies only to one branch, one department or one group of employees, keep it targeted. That avoids unnecessary noise and helps managers stay organised.
In practice, many businesses use messaging for three things: confirming a roster change, sending reminders before a shift, and sharing notes about team activities or staff engagement sessions. It is a simple way to keep communication in one place instead of across several channels.
What happens during onboarding and go live support
Onboarding usually begins with account setup and a review of your current scheduling process. From there, we help with team import help, roster template setup and policy alignment so the system reflects how your business actually works.
Before go live, it is worth checking the basics with managers and supervisors. They should know how to view the roster, approve changes, send messages and handle team activities. Staff also need a brief introduction so they know where to check shifts and what to do if they cannot make a scheduled time.
- Confirm your teams, sites and user access
- Check the roster template before publishing
- Train managers first, then staff
- Test the swap process and messaging before launch
Our support team can stay involved during the first few roster cycles, which helps catch small issues early. It is easier to fix a reporting or process issue in week one than after a month of manual work.
How do we keep policies and rosters aligned
Policy alignment means your roster rules should match your own workplace policies, not work against them. If you have rules for overtime, late arrival, weekend work, or approval levels, those should be reflected in how the roster is planned and managed.
This is also where manager training helps. A manager needs to know when to approve a change, when to escalate a request and when to leave the roster as it stands. The cleaner the process, the less back and forth for staff and supervisors.
Businesses often ask for support when there are several branches or sites with slightly different processes. In that case, the answer is usually not more complexity. It is a clear template for each group, plus one simple rule set that everyone can follow.
When should we ask for ongoing check ins
Ongoing check ins are useful once the system is live and your team has started using it regularly. They give you space to review what is working, tidy up any loose ends and improve the way rosters, swaps and messages are handled.
We usually suggest check ins after the first few shifts, then again after a full roster cycle. That gives enough time to spot patterns such as repeated swap requests, unclear shift notes or messages that are not reaching the right group. Small changes at that stage can save a lot of admin later.
If your business grows, adds new branches or changes operating hours, check ins become even more helpful. A roster process that worked for one site in Rosebank may need a few adjustments when it is used across Johannesburg and other centres too.
