What the team needed in Nelspruit
This project was for a site security team in Nelspruit working across day and night shifts, with supervisors needing faster updates when someone called in sick or had transport trouble. The old process relied on calls and messages passed around one by one, which caused confusion when a change happened after the roster had already been shared.
The brief was straightforward: make rostering easier to manage, keep shift changes visible and give the team one place to handle communication. The client also wanted a simple setup that supervisors could use quickly, without turning roster admin into a full time job. Because the site operated in a practical, rules-led environment, the team also wanted rosters and swap steps to follow the Basic Conditions of Employment Act in general terms, without getting into legal advice.
- Client type: security team at a single site in Nelspruit
- Core need: late roster changes and shift swaps handled more clearly
- Main pressure point: communication between supervisors and guards on different shifts
- Working environment: early starts, night shifts and occasional load-shedding disruptions
Constraints on a busy local site
The site had a few practical limits. Internet coverage was not always perfect in every corner of the property, so the process had to stay simple and easy to pick up. Some team members were more comfortable with short messages than long instructions, so we kept the workflow direct. The supervisors also needed a way to see who was available before approving any change, because a late swap can create gaps fast if it is not checked properly.
We also had to keep the setup aligned to the way a South African work site runs in practice. That meant clear shift times, a defined approval path for changes and a record of who messaged what and when. It also meant making sure the roster approach could support fair working hours and rest periods in line with the Basic Conditions of Employment Act, in general terms, so the team was not left guessing. Small detail matters on these sites, and even a missed handover can affect the whole shift.
- Late changes had to be visible quickly to the right supervisor
- Swap requests needed a clear approval step
- Messages had to be short enough for quick reading on shift
- The roster structure had to support fair scheduling and rest periods
What we set up and how it worked
We set up the account, helped with team import, and built a roster template suited to the site’s shift pattern. That included standard shift blocks, supervisor oversight and a basic process for marking who was on duty, who was off and where a swap had been requested. We also helped the client shape a message setup that kept shift updates in one place instead of scattering them across calls and informal chats.
On top of the roster structure, we guided them through swap process help and activity planning help for team building days and staff engagement sessions. The aim was not to add unnecessary steps. It was to give the team a clean process they could follow on busy mornings, during load-shedding and on weekends when cover was tighter. We also provided manager training and staff training so the process was understood by both supervisors and guards, not just by one person in the office.
- Account setup and team import help
- Roster template setup for a security shift pattern
- Message setup for updates and acknowledgements
- Swap process help with a clear approval flow
- Manager training, staff training and go live support
The rollout over three weeks
The rollout took three weeks from initial setup to go live support. In week one, we mapped the roster pattern, the main shift changes and the places where communication was breaking down. In week two, we built the template, tested the message flow and reviewed the swap process with the supervisors. In week three, we trained the team, checked the first roster cycle and stayed close while the new process settled in.
Because this was a working site, we kept the rollout practical. We did not try to change everything at once. The focus was on making the core routines easier first, then tightening the process after the team had used it for a few days. That approach kept the handover smooth and avoided confusion for guards who were coming on duty at different times.
- Week 1: process review and roster mapping
- Week 2: template setup and message testing
- Week 3: training, go live support and first cycle checks
What changed after the first roster cycle
After the first roster cycle, the supervisors had a clearer view of who was covering each shift and which changes still needed approval. The team did not have to rely on memory or long message threads. Late changes were easier to track, and the roster no longer felt like a moving target by the end of the day.
The client told us the biggest improvement was communication. Guards could see updates sooner, supervisors had fewer follow up calls, and roster changes were less likely to be missed after a shift started. It also became easier to plan around leave, sick calls and short notice cover without scrambling at the last minute. For a security team, that kind of order matters because the site has to stay covered, even when people are off sick or transport runs late.
- Clearer visibility of late changes
- Fewer repeat calls between supervisors and guards
- Better control over shift swaps and cover
- Cleaner handovers between day and night teams
What we would do again on a similar site
We would use the same method again on another security site in Nelspruit, White River, Mbombela or any other South African town with mixed shift patterns. Start with the real roster pain points, keep the template simple and make sure supervisors are trained before the first live cycle. That approach works better than trying to force a complicated process onto a team that needs speed and clarity.
We would also keep the policy side plain. If a site needs rostering that follows the Basic Conditions of Employment Act in general terms, the process should be clear enough for managers to use without extra confusion. Once the roster, messaging and swap steps are understood, the rest of the team usually settles into it quickly. That is especially true on sites where late changes are common and time is tight.
- Begin with one site and one clear shift pattern
- Train supervisors before full rollout
- Keep message rules short and practical
- Review the first cycle, then adjust the process
Key facts
| Project | Nelspruit Security Team |
|---|---|
| Client type | Security team at a site in Nelspruit, Mpumalanga |
| Timeline | 3 weeks from setup to go live support |
| Main issue | Late roster changes and shift swaps were hard to track |
| What was supplied | Account setup, team import help, roster template setup, manager training, staff training, go live support |
| Key process | Scheduling, shift swaps, messaging and activity planning support |
