A 7.15 am call about an absent support worker should not send the whole day sideways. Yet for many providers, one change can trigger a chain of phone calls, text messages, spreadsheet edits and unanswered questions: who is available, who is suitable, who has been told, and has the participant’s service actually been protected?
This NDIS coordination case study follows a mid-sized provider facing exactly that pressure. It is a composite scenario based on common workforce problems in disability support, rather than the story of one named organisation. The operational lessons are real: reliable coordination comes from making the roster, staff communication and attendance records work together.
The problem was not just a messy roster
The provider supported participants across several service areas, with a mix of regular supports, community access shifts and short-notice changes. Its team cared deeply about continuity and participant preferences. The system around them, however, made good coordination harder than it needed to be.
Rosters were prepared in one place, while staff availability sat in emails, messages or a coordinator’s memory. Last-minute requests were sent through group chats. Staff could see messages intended for broader teams, and coordinators had no single view of whether a replacement had received and accepted a shift.
That created four costly issues:
- A coordinator could spend an hour chasing a replacement for a single changed shift.
- Workers were occasionally allocated before key matching details had been checked.
- Staff arrived without seeing an updated instruction or participant note.
- Timesheet and attendance questions surfaced days later, when the details were harder to verify.
None of these problems meant the team was not working hard. They meant the team was relying on disconnected processes during the most time-sensitive part of the job.
What good NDIS coordination needed to look like
The service manager set a practical goal: when a shift changed, the right person needed to be identified, informed and confirmed quickly, without sacrificing participant fit or creating an audit trail that had to be rebuilt later.
That meant more than digitising a roster. The provider needed a clear operational workflow. Coordinators needed to see current availability before allocating work. Workers needed shift notifications on their mobile, with relevant information available in one private place. Managers needed confidence that actual attendance could be checked against planned work.
There was also a trade-off to manage. Speed matters when a participant is waiting, but simply filling every vacant shift with the first available worker is not a service standard. The workflow had to support fast decisions while keeping matching, qualifications, location and participant preferences visible to the person making the allocation.
Step one: make availability usable before a shift changes
The first improvement was to set clear expectations for staff availability. Rather than asking coordinators to search old messages or make multiple calls, workers kept their availability current through the workforce platform.
This did not remove the need for human judgement. A worker may be technically available but not be the right person for a particular participant or support type. What changed was the starting point. Coordinators began with a more accurate pool of potential workers, then applied the knowledge that matters in disability support: skills, compatibility, travel time, continuity and individual requirements.
The provider also set a cut-off for routine availability updates and gave team leaders a simple exception process. That reduced the familiar problem of a staff member saying they were unavailable after a roster had already been published.
Step two: send changes through one private channel
When a worker called in sick, the coordinator no longer had to copy details into several systems and then send a broad text message. The changed shift could be offered and communicated through the same system used for rostering.
Private business messaging was particularly useful here. Participant-related instructions should not be scattered across personal text threads, where context is easily lost and access is difficult to manage. Keeping operational communication connected to the shift gave staff a clearer source of truth.
The provider was careful about what it included. Shift messages contained the information a worker needed to do their job safely and professionally, while sensitive participant information remained subject to the provider’s policies and access controls. Technology supports sound practice, but it does not replace privacy obligations or thoughtful communication.
Step three: close the gap between planned and actual work
A published roster tells a manager what should happen. It does not, by itself, confirm what did happen.
The provider introduced mobile clocking with GPS information for relevant shift-based work. Coordinators could see when staff clocked on and off, helping them resolve attendance questions much earlier. For managers, this was less about watching people and more about reducing uncertainty.
The rollout mattered. Staff were told clearly why clocking was being used, when it applied and how to report a legitimate exception, such as poor reception or a participant-requested change. A workforce tool earns adoption when people understand the purpose and the process is easy to follow.
The NDIS coordination case study results
After the new workflow settled in, the provider did not claim that roster changes disappeared. They never do. What changed was the amount of manual chasing required to manage them.
Coordinators had a live starting point for availability, and staff received clearer updates. Fewer changes depended on someone remembering to update a spreadsheet after sending a message. Team leaders could see emerging issues sooner, including repeated late clock-ons, unfilled shifts or workers whose availability patterns had changed.
The service manager reported four noticeable improvements:
- Faster response to routine shift changes, with less back-and-forth between coordinators and workers.
- Better visibility of whether staff had received the information connected to their shifts.
- More consistent attendance records for payroll checks, service review and operational follow-up.
- Less coordinator time spent reconstructing what happened after a change.
The strongest outcome was not simply admin time saved. It was greater confidence that participants would receive the planned support, or that the provider could respond quickly and clearly if a change was unavoidable.
What the provider learned during implementation
The technology was only one part of the result. The provider learned that process discipline makes the platform useful.
First, participant-worker matching rules needed to be agreed before configuring the roster. If coordinators use different criteria, the system cannot create consistency on its own. The team documented what must be checked before a replacement is allocated and what information should be visible at the shift level.
Second, staff adoption depended on simplicity. Workers were more likely to keep availability current and clock correctly when the mobile experience was straightforward. Long training manuals were less effective than short, practical sessions based on everyday situations: accepting a changed shift, checking instructions and reporting an issue.
Third, the provider avoided trying to fix every process at once. It began with roster visibility, notifications and attendance, then refined reporting and exceptions after staff had built confidence. This staged approach reduced disruption and gave managers time to address genuine questions from the team.
A configured platform such as Tommy can support this approach by bringing scheduling, availability, notifications, private messaging and time clocking into one operational system. The value is not in adding another screen for staff to manage. It is in reducing the number of places they need to look when the day changes quickly.
Questions to ask before changing your coordination process
If your team is feeling roster pressure, start with the moments where work breaks down rather than the features you think you need. Ask whether coordinators can see real availability before they call people. Ask whether staff receive one clear version of every changed shift. Ask whether your attendance information is available when an issue occurs, not a week later.
Also consider scale. A process that works with 10 support workers can become fragile with 50, particularly across multiple locations and participant schedules. The right system should give managers visibility without forcing staff through complicated steps for ordinary tasks.
The best coordination process will still rely on capable people making good decisions. It should simply give them less chasing, less guesswork and more time to protect the support experience that participants rely on. Happy Staff – Happy Life starts with a roster that holds together when real life does not.