What the Pretoria team needed
The client was a Pretoria-based operations team working across office hours, planned absences and regular internal activities. Their main issue was not a lack of effort, but the way schedules were being managed in too many places at once. One person had the master roster, another handled reminders, and updates were sometimes sent late or missed altogether.
The brief was to bring daily scheduling into one clear process. They wanted a better way to organise recurring shifts, manage swaps when staff were away, and keep reminders for team activities in one place. They also wanted the roster structure to stay sensible under the Basic Conditions of Employment Act, without turning the process into a legal exercise.
Constraints we had to work around
Pretoria office teams often have a mix of fixed hours, planned meetings and occasional leave changes, so the setup needed to be flexible but orderly. The client also needed a process that managers could follow easily during busy weeks, including month-end, training days and public holidays. We had to keep the system simple enough for day-to-day use, because if it takes too long people stop using it.
- Recurring rosters had to be easy to repeat and adjust
- Shift swaps needed a clear approval flow
- Messages had to reach the right people quickly
- Activity reminders had to sit alongside roster tasks
- Manager handover had to stay clear for leave periods and load-shedding interruptions
What we supplied and set up
We helped the team set up their account structure, import staff details and build a roster template that matched their weekly pattern. The schedule was arranged so that repeating shifts could be copied forward, then adjusted for leave, meetings or special activity days. We also helped them shape the swap process so staff could request changes in a controlled way instead of relying on informal messages scattered across different groups.
For internal communication, we set up message groups and a straightforward activity planning method for reminders, staff sessions and team-building dates. The focus was practical. It needed to be easy to update on a phone or computer, and it had to work well even when people were away from the office or dealing with power cuts. We also checked the roster flow against the team’s internal policy rules so the setup lined up with their working patterns.
- Account setup for managers and staff
- Team import help for existing employee lists
- Roster template setup for recurring weekly work
- Manager training and staff training
- Swap process help for clear approvals
- Message setup and activity planning help
Implementation timeline in weeks
The work took four weeks from first setup to go live support. Week 1 covered planning, staff list checks and roster structure. Week 2 was used for template setup and message groups. Week 3 focused on training, testing the swap process and reviewing the activity reminder flow. Week 4 covered rollout, final corrections and support while the team started using the process in daily work.
That timeline suited the client because they did not want a long changeover period. They wanted the new process to be in place before the next rotation of schedules, and we kept the handover tight so managers could take over without confusion. A few small adjustments were made during rollout, mostly around who approved changes and when reminders were sent.
Results for the Pretoria office
Once the new process was in use, the team had a clearer view of who was working when and what internal activities were due each week. Managers spent less time checking details by message, and staff had one place to look for shifts, reminders and swap requests. The office could plan ahead more easily, which helped during busy periods and leave rotations.
The client also found that the roster was easier to keep aligned with working hours and internal policy requirements. That matters because a good roster is not only about filling slots, it should also fit normal employment rules and business needs. The process is now more predictable, and there is less back and forth when changes come up, even when two people need to swap on short notice.
- Clearer weekly scheduling for office staff
- Fewer missed internal reminders
- Better control over shift swaps
- Less time spent on manual follow ups
- More consistent manager oversight
What we would do again for a similar client
If we were setting this up again for another Pretoria team, we would start with the roster structure before anything else. Getting the weekly pattern right from the beginning saves time later and prevents confusion when the team grows or changes. We would also keep manager training short and practical, with examples based on the client’s own shifts and internal activities, not generic theory.
We would repeat the same approach for check ins after go live, because that is where small issues usually show up. A message sent too early, a swap rule that needs one more step, or a reminder that lands in the wrong group can all be fixed quickly if someone is watching the process in the first few weeks. That kind of follow up keeps the system useful and makes the handover smoother for everyone.
Key facts
| Project | Pretoria Office Team |
|---|---|
| Client type | Operations team in Pretoria |
| Location | Pretoria, Gauteng |
| Timeline | 4 weeks from setup to go live support |
| Core functions | Scheduling, shift swaps, messaging and activity reminders |
| Support scope | Account setup, roster template setup, training, rollout and ongoing check ins |
