NDIS Rostering: Why Spreadsheets Break at 15 Workers

Most NDIS providers don't realise their rostering is broken until they cross ~15 support workers. Below that threshold, a Google Sheet with conditional formatting works fine — you can see the whole week at a glance, manually catch conflicts, remember who's matched to which participant, and the worst case of a missed shift is one phone call.

Above 15 workers, three things fail at once. None of them are dramatic. All of them are expensive.

This post is about what changes — what the cost shows up as, and what NDIS rostering software actually needs to do once you outgrow the spreadsheet.

The 15-worker threshold

The threshold isn't a number we made up — it's the number we keep hearing from NDIS provider operations managers in research conversations. It's not strictly about headcount. It's about the shape of the roster:

• Worker count above ~15 means more permutations than a human can hold in working memory while building the schedule
• Participant count above ~25 means you can't remember every participant's preferences, supports, and management type
• Service mix beyond just core supports + community access (SIL with high-acuity cover, group programs, support coordination on top) means the shift types stop fitting in one spreadsheet view
• Shift frequency above ~80 shifts per fortnight is where copy-paste roster building starts breaking down

Hit any two of those four and you're in the territory where the spreadsheet starts costing more than the software would.

What fails at 15+ workers

1. The fortnight roster takes a full day to build

At 10 workers and 20 participants, you can build a 2-week roster in ~2 hours on Friday afternoon: open last fortnight's sheet, copy forward, swap in changes, send the WhatsApp.

At 25 workers and 60 participants, the same process takes 6–8 hours and you're losing Friday afternoons routinely. Worse, the conflicts you'd have caught visually at 10 workers (worker double-booked, participant assigned to a worker they've requested not to see, shift overlapping with worker's hard cap) are now hidden in the volume.

What ends up happening: the operations manager builds the draft, sends it to the team, and the workers spot the conflicts — usually 24 hours before the shift, often via a worker message saying "I can't do Tuesday after all." Then the fortnight reshuffles last-minute, and someone else picks up the cancelled shift without proper notice.

2. Worker certifications quietly expire under the surface

Every NDIS support worker must hold a current NDIS Worker Screening Check [NDIS-CHECK: confirmed at https://www.ndiscommission.gov.au/providers/worker-screening — required for all NDIS workers in risk-assessed roles]. Most providers also track:

• First Aid certificates (typically 3-year renewal)
• Manual handling training
• Medication administration competency (where relevant)
• Driver's licence + vehicle insurance (where transport is part of the role)
• NDIS Worker Orientation Module completion [NDIS-CHECK: confirmed required at https://www.ndiscommission.gov.au/workers/training/worker-orientation-module]
• Any participant-specific training the support plan calls for

The pattern that bites every provider above ~15 workers: a certificate quietly expires, the worker keeps working, and nobody notices for 2 or 3 weeks. By the time HR realises, the worker has billed for shifts they weren't legally authorised to deliver — and those claims are at risk if the worker's expired certification surfaces in an audit.

The cost: at the auditor level, this is one of the five most common non-conformities cited in audit findings. At the operational level, it's the claim revenue you can't safely recover.

3. Short-notice cancellations cascade

In NDIS rostering, "short-notice cancellation" has a regulatory meaning [NDIS-CHECK: the NDIS Pricing Arrangements 2025-26 define short-notice cancellation rules — providers can claim up to a specified threshold per participant per period when participants cancel inside the notice window. Confirm latest threshold at ndis.gov.au/providers/pricing-arrangements before quoting it externally.]. Operationally, it's the moment everything goes sideways.

A participant cancels at 7am for a 9am shift. Your worker is already in their car. You need to:

1. Decide whether to claim the cancellation against the participant's plan
2. Reassign the worker to another participant if possible (so you're not paying them to drive home)
3. Update the roster everywhere it shows
4. Make sure the worker's shift notes don't reflect a service that didn't happen
5. Track the cancellation count against the per-participant threshold so you know whether to claim or absorb

Below 15 workers, this is a 5-minute phone call. Above 15 workers, the operations manager is fielding 4–5 of these a week, and the per-participant cancellation count is impossible to track in your head.

What providers usually do: lose track of the cancellation thresholds, under-claim out of caution, over-claim and get pulled up in an audit, or just stop offering services to participants who cancel a lot — which goes against the principle of choice and control.

Where the cost actually shows up

It's not in one big number. It's in three places, each easy to dismiss individually:

Lost claim revenue. Shifts billed where the worker's certification had quietly expired. Cancellations under-claimed because the threshold wasn't tracked. Service item codes pulled from a stale spreadsheet instead of the live Pricing Arrangements. For a $400k/year provider, this is typically 3–7% of revenue — enough to fund a part-time admin role, gone.

Worker churn. When the roster process is slow and reactive, the workers who get the worst shifts (last-minute reassignments, broken fortnights, no-notice cancellations passed onto them) are the ones who leave first. Replacing a support worker costs ~$3,000–$5,000 in onboarding, training, and lost productivity during ramp-up [NDIS-CHECK: figure is a research-conversation estimate, not a formally published NDIS-sector benchmark; cite carefully]. Lose 3 workers a year to roster friction and you've spent $10k+ on recruitment that didn't have to happen.

Participant complaints. The soft kind that don't get logged formally but show up in the next quality review: "the rostering's been all over the place," "we never know who's coming," "we asked not to have [X] worker and they keep getting assigned." None of these are conformity findings in themselves, but they accumulate, and they affect what auditors call "evidence of participant satisfaction."

What NDIS rostering software actually needs to do

The category of "rostering software" is wide — from generic timesheet apps to enterprise workforce management platforms. For NDIS-specific operations, the functional requirements are narrow:

Validate before scheduling. When you draft a shift between worker X and participant Y, the system should warn you if worker X's screening expires before the shift date, if worker X has a documented preference conflict with participant Y, if the shift creates a fatigue-management breach with the worker's previous shift, or if the service item code you've picked doesn't match the participant's plan management type.

Track certifications with expiry alerts. 30-day, 14-day, and 7-day alerts to the certificate owner (HR / ops manager). A worker whose check expires on a Friday should not be rostered for Saturday's shifts — the system should make that impossible, not optional.

Handle the cancellation flow end-to-end. Participant cancellation triggers a workflow: claim/no-claim decision, worker reassignment, shift state update, cancellation-count-against-threshold tracking. One workflow, not five separate updates across five tabs.

Connect to the claim pipeline. The roster isn't a separate system from billing — every shift is a future claim. The validation that catches a wrong service item code or an expired worker certification should fire at roster-draft time, not at PACE submission time.

Mobile-first for the worker side. Workers need to clock in, write progress notes, and capture incident reports on a phone, offline, in real-world conditions [see our earlier piece on why we built mobile for 4am with no signal — the audit checklist post covers the documentation discipline this supports].

If your current rostering tool meets fewer than three of those five, you're paying the cost of the spreadsheet era inside a slightly nicer interface.

When to switch — and what comes with the migration

The honest answer on when to switch isn't a worker count. It's the first Friday afternoon you spend 4 hours building the roster and notice you missed something obvious only because a worker spotted it. That's the signal.

The migration isn't trivial. Moving an NDIS provider's roster from a spreadsheet (or from a legacy tool like ShiftCare or SupportAbility) into a connected workflow involves:

• Importing the participant master list with plan management types and budgets
• Importing the worker master list with current certification expiry dates
• Mapping your service item codes against the current Pricing Arrangements
• Backfilling 30+ days of historical shifts so the audit pack works on history, not just future state
• Re-training the operations team on the workflow (the spreadsheet muscle memory is hard to break)

Done well, the migration is a 2-week project for a small-to-mid NDIS provider. Done badly, it's a 3-month nightmare that ends with everyone back on the spreadsheet.

The single piece of advice from providers who've made the switch successfully: don't run the new system in parallel with the spreadsheet for more than 2 weeks. Either commit, or the old habits win and you've spent the implementation budget without changing operations.

What we built into Tendaroo

Tendaroo is rostering + claims + audit prep + compliance for Australian NDIS providers, designed around the case where the operations manager can't hold the whole fortnight in working memory anymore. The five points above — pre-flight validation, certification tracking, cancellation workflow, claim pipeline integration, mobile-first worker app — are the ones we obsessed over for the first product release.

If you're in the territory where the spreadsheet has started costing more than it saves, try Tendaroo free for 30 days. No credit card, no demo call. We're founder-led right now — if you get stuck on setup, the founder reads every reply.

If you'd rather see the comparison against the two tools you've probably already shortlisted: ShiftCare vs Tendaroo and SupportAbility vs Tendaroo. Both written with the honest answer about when each one wins — including the cases where they beat us.