School support team in Bloemfontein
This project involved a support team at a school in Bloemfontein that needed better control over daily duties, term activities and planned leave. The team was handling a lot of moving parts, from morning coverage and after school tasks to ad hoc changes when staff were off site or needed to swap a shift.
The brief was straightforward: make the roster easier to build, easier to share, and easier to update when something changed. The school also wanted a cleaner process for staff messages and activity planning so that everyone could see what was happening without chasing paper copies or relying on memory.
- Client type: school support team
- Town: Bloemfontein
- Scope: duty rosters, leave coordination, shift swaps, messaging and team activities
- Delivery: setup, training and go live support
What the school needed the roster to do
The school was not looking for a complicated system. They needed a roster that matched the way a real campus runs, with term dates, event days, exam periods and staff leave all changing the week ahead. A good roster had to make sense at a glance and still leave room for quick changes.
We also had to keep the setup aligned with general employment practice and roster planning under the Basic Conditions of Employment Act, especially where working time, rest periods and fair scheduling are concerned. This was not legal advice, just a practical check so the process started in the right place. The team wanted clear rules for swaps and updates, plus a simple way to message the group when a change landed after hours or early in the morning.
- Key need: simple roster visibility for all staff
- Key need: quick shift swaps with manager approval
- Key need: clear messaging for duty changes and notices
- Key need: activity planning for school events and term programmes
Constraints around term time and leave
Like many schools, the biggest challenge was timing. Term schedules move quickly, leave can stack up, and events often need extra hands at short notice. The support team also needed a method that worked for both office hours and the busy edges of the day, when staff are arriving, leaving or covering another area.
Another consideration was consistency. When rosters are built by different people on different days, the result can be uneven and hard to follow. We set things up so the school could keep one clear structure, then make changes in a controlled way. That cut down on confusion and reduced the number of times staff needed to ask who was meant to be where. Load-shedding was also part of the real world picture, so the team wanted a process that did not depend on someone being at one computer at one time.
- Term activity pressure
- Leave planning during exam and event periods
- Need for a consistent process across the team
- Practical use during power cuts and busy changeovers
What we supplied and set up
We handled the initial account setup and helped the school import staff details so the roster structure could be built from the actual team list. From there, we assisted with roster template setup, manager training and staff training so everyone understood how the process worked before the first live week.
We also helped with swap process guidance, message setup and activity planning support. The school wanted a system that could support ordinary school work as well as special days, so we paid attention to how activities were named, how notices were shared and who needed to see them. The final setup was practical rather than fancy, and it matched the way the team already worked. A few things took time to tidy, but that was expected when you are sorting out real schedules with real people.
- Account setup and team import help
- Roster template setup for school duties
- Manager training and staff training
- Swap process help and message setup
- Activity planning help and go live support
Rollout over four weeks
The rollout ran over four weeks. In week one we confirmed the structure, the main duty groups and the rules for leave and swaps. In week two we built the first roster templates and checked the wording on messages and activity notices. Week three focused on training and testing with the school team, then week four was used for go live support and the first round of check ins.
That timeline gave the school enough time to adjust without rushing the process. It also gave the managers space to ask practical questions like how to handle a late change, who approves a swap, and how to keep the roster readable when term events stack up. The result was a cleaner start and a calmer handover for the people doing the actual scheduling day by day.
- Week 1: planning and structure
- Week 2: templates and message setup
- Week 3: training and testing
- Week 4: go live support and check ins
Results and what we would do again
After the rollout, the school had a more reliable way to manage duty cover around term activities and leave. Managers could make changes faster, staff had clearer notice of what was expected, and the team spent less time correcting mixed-up rosters. Communication also improved because routine messages and activity notices were easier to send in one place.
If we were doing this again, we would follow the same approach: keep the setup simple, train the people who actually handle the roster, and agree on the swap rules before the first week starts. That is especially important for schools where the calendar shifts often and where a missed duty can affect the whole day. The best outcome came from matching the setup to the school’s normal routine, not trying to force a new one onto it.
- Clearer duty cover during busy term periods
- Fewer last minute roster mix ups
- Better staff visibility for swaps and notices
- More practical planning for school activities
Key facts
| Project | Bloemfontein school support team roster setup |
|---|---|
| Town | Bloemfontein |
| Timeline | 4 weeks |
| Core functions | Scheduling, shift swaps, messaging, team activities |
| Services used | Account Setup, Roster Template Setup, Manager Training, Staff Training, Go Live Support |
| Company base | Rosebank, Johannesburg |
