Why the Centurion depot asked for help
The team was dealing with the kind of pressure many South African logistics sites know well: early starts, last-minute call-ins, and different groups of staff arriving at different times. When a driver or warehouse hand could not make a shift, the office often had to phone around, update paper notes and send repeat messages before the first loads left the yard.
The brief was simple enough, but the detail mattered. They wanted a practical way to manage rosters, handle shift swaps, share messages and keep track of team activities without adding more admin for supervisors. They also wanted the process to sit comfortably with basic working-time rules under the Basic Conditions of Employment Act, while keeping the setup straightforward for day-to-day use.
What made the roster tricky
The branch runs early mornings, which means cover requests often come in before 6am. That left very little time to rework a roster, and if one message was missed the whole handover could slip. In a logistics setting, a late update can affect loading bays, vehicle departures and receiving schedules all at once.
- Multiple shift start times across the week
- Short-notice change requests from staff
- Managers needing one clear place for messages
- Rosters needing to stay aligned to working-time basics
- Teams spread across warehouse and transport functions
Coastal humidity was not the issue here, but the team did mention load-shedding and early phone traffic as regular interruptions. They needed a way to keep the roster visible and current even when the morning got busy and the office was under pressure.
What we set up with the team
We supported the Centurion team with account setup, roster template setup and manager training first, then moved on to staff training and go live support. The core setup was kept plain: shift planning, swap requests, internal messaging and activity planning in a single workflow. No extra layers, just a clear process that supervisors could follow before the day started.
Our work also included policy alignment so the team could shape their roster and swap process around their own rules and normal employment practices. We helped them define who approves changes, how notice is given, and what happens when a shift needs cover at short notice. The aim was not to add admin, but to make the rules easier to follow in practice.
- Account Setup and roster template setup
- Manager Training for supervisors and team leads
- Staff Training for quick uptake on the floor
- Swap Process Help for common cover requests
- Message Setup for shift notices and reminders
- Activity Planning Help for team engagement items
Delivery timeline and rollout
The rollout took 3 weeks in total. Week one covered the setup work and roster structure, week two focused on training and process adjustments, and week three covered go live support and check-ins while the team settled in. That pace gave the branch enough time to test the routine without dragging the process out for months.
We kept the schedule practical for a working depot. Sessions were short, the roster rules were kept clear, and the staff were shown the exact steps they would use when a shift needed swapping or when a supervisor needed to send a message. A few small changes were made after the first round of use, which is normal when a busy site starts using a new process.
What changed after go live
Once the team was live, early-morning cover requests became easier to handle. Supervisors had one place to check the roster, send messages and manage swaps, so they were not chasing information across calls and chat threads. That meant fewer gaps at handover and less time spent sorting out who was meant to be on site.
The staff also adapted quickly because the process was easy to explain. They knew where to send a request, how to check updates and what to expect when a change was approved. The branch reported smoother morning coordination and better visibility across the day, especially when someone was off sick or running late.
- Faster response to early cover requests
- Clearer handover for supervisors and staff
- Less repeat calling and message confusion
- More consistent use of the same roster process
- Better visibility for daily team activity
What we would do again for a similar site
For another logistics site in Centurion, Midrand or Pretoria, we would take the same approach again: keep the roster structure simple, train the supervisors first and then bring the staff in with clear examples. If a site works early mornings, the priority is always speed and clarity, not adding more layers to the process.
We would also keep checking that the roster rules match the business's own policy and working-time requirements under the Basic Conditions of Employment Act. Not legal advice, just practical alignment so the team has a sensible process to follow. That approach worked well here, and it would suit other depots that need stronger day-to-day control without making the admin heavier.
Key facts
| Project type | Team-building and staff rostering rollout for a Centurion logistics team |
|---|---|
| Location | Centurion, Gauteng |
| Timeline | 3 weeks |
| Core functions | Scheduling, shift swaps, messaging and team activities |
| Support included | Account setup, roster template setup, manager training and go live support |
| Key compliance note | Roster and swap process aligned to basic working-time rules under the Basic Conditions of Employment Act |
