An incident is the dramatic compliance event. A handover is the daily one. A roster sits one layer below both. It is the single document that decides whether a worker is in a fit state to support a participant before the shift even begins — and it is the document the NDIS Commission reaches for when an incident shows the worker was too tired to make the decision they made.

The Fair Work Act and the SCHADS Industry Award (MA000100) set the framework. The NDIS Practice Standards add a participant-safety layer on top. Together they expect SIL providers to have a written fatigue management policy and an enforcement mechanism that catches breaches before the shift runs.

Three thresholds carry most of that weight in practice.

The three numbers

Number 01

10 hours minimum rest between shifts

Worker recovery starts in the gap between shifts. Less than 10 hours and the worker has not slept enough — even if the time-off looks fine on a roster. SCHADS minimum daily break provisions converge here, and the heavy-vehicle and nursing fatigue frameworks both use 10 hours as the floor.

Where it hides

Cross-house rostering. A worker finishes a 10pm shift at house A and is on the 7am roster at house B. The clock between shifts says 9 hours; once travel + sleep prep is taken out, the actual rest is closer to 7. Providers running each house on a separate roster never see the gap.

Number 02

12 hours maximum single shift

Twelve-hour shifts are common in SIL — the operations make sense for sleeping shifts, weekend cover, and short-staffed runs. Past 12 hours, attention degrades faster than self-reported tiredness. Operators often know this and cap shifts at 12 anyway. The trap is the back-to-back exception.

Where it hides

The half-hour break trick. A worker finishes a 10-hour shift, takes a 30-minute break, picks up a 4-hour overflow shift at the same site. The roster shows two shifts; the auditor reads it as a 14.5-hour engagement. If anything goes wrong during the second shift, the finding cites the cumulative hours, not the legal-on-paper structure.

Number 03

76 hours over a rolling fortnight

The 14-day rolling sum is the one that catches operators by surprise. The NES sets ordinary hours at 38 per week — two of those is 76 across a fortnight. The number is not what matters. The distribution is.

Where it hides

Two 38-hour weeks is fine. Two 38-hour weeks compressed into 11 consecutive working days with three days off is not — same total, very different fatigue profile. The rolling-window check catches the second pattern; a flat weekly check does not.

Why this gets missed

Rostering software written for general workforce scheduling does not have NDIS context. The thresholds above are not strictly in any single award clause — they are operating thresholds drawn from the Fair Work Act's reasonable-additional-hours framework, the Heavy Vehicle National Law (which has Australia's most refined fatigue regulations), and the published research on shift-worker injury rates.

Three patterns hide them in practice:

  • Cross-site shifts. When a worker covers houses A and B in the same day, the system looks at each shift in isolation.
  • Casual pickups. Last-minute coverage that bypasses the planner's fatigue check. The shift gets approved by the duty manager, not the rostering tool.
  • Travel time. Between houses, between shifts. Doesn't count as work time, but it eats into rest.

What auditors actually check

NDIS Commission auditors do not run a fatigue scan over the whole roster. They sample. The pattern looks like this:

Step 01
Pull a sample week. Usually the week of an incident or a complaint, or just a randomly-chosen one from the last 90 days.
Step 02
Cross-reference timesheets to the roster. The rostered hours and the worked hours should match. Where they diverge, the auditor asks for an explanation.
Step 03
Check worker statements. Did anyone complain about fatigue, hours, or rest? If yes, was the complaint resolved with a record?
Step 04
Look for incidents on those shifts. Medication errors, falls, missed administrations. If the incident clusters around long shifts or short rest gaps, the finding cites the fatigue policy, not the incident.

If the cross-reference surfaces a violation, the finding cites the fatigue management policy first — not the missed shift specifically. Practice Standards expect a documented policy plus an active enforcement mechanism. A written policy with no enforcement is the most common failure mode.

"A written fatigue policy that the rostering tool doesn't enforce is a policy that exists for the auditor, not for the worker."

What good looks like

Three operating habits separate the SIL providers who pass the fatigue check from the ones who get cited.

Habit 01
Set the three thresholds explicitly in writing. 10-12-76 is a sensible default. You can choose stricter (e.g. 11-hour rest, 11-hour max shift) or looser if your participant cohort tolerates it. Document the choice in the policy. The auditor will read it before the roster.
Habit 02
Bake the check into the rostering tool. A pre-shift creation warning beats a post-hoc finding. The cost of catching a fatigue breach at shift-create time is a 5-second alert; the cost of catching it during an audit is a written corrective action plan.
Habit 03
Track override acknowledgements. Legitimate cases happen — emergency cover, a sleep-shift after a quiet day shift. When a manager overrides a warning, capture the acknowledgement with a written reason. The auditor sees the policy plus the enforcement plus the documented exceptions, and the test passes.

The cross-site point

If you run two or more SIL houses on separate rosters, fatigue across them is invisible until an incident makes it visible. The fix is operational, not technical: one rostering tool, one set of thresholds, one view across every house. The technical part is downstream.

The cost of getting it wrong

Fair Work back-pay claims for inadequate rest periods accumulate at penalty rate over the rolling 12 months — not just the shift itself. A persistent 10-hour-violation pattern across a 4-worker SIL house compounds into meaningful retrospective wage liability if it has been ongoing.

That is before NDIS Commission consequences. A fatigue-related medication error or a fall on a long shift can reframe the audit from compliance review to quality and safeguards investigation, with conditions placed on the registration.

What to do between now and 1 July 2026

Sixty days until mandatory SIL registration takes effect. Treat fatigue as the cheapest pillar to harden — it is the one with the highest sampling rate per audit hour and the lowest fix cost when caught early.

01
Write the policy if you don't have one. Two pages. The three thresholds. The enforcement mechanism. The exception process. Date it. Have a witness sign the review.
02
Run the 90-day backward check. Pull the last 90 days of timesheets. Run a script — or do it manually — that flags every breach of the three thresholds. Triage what you find.
03
Fix the worst pattern first. If 10h rest violations dominate, the fix is a hard floor on shift-create. If the 76h fortnight is the problem, the fix is a rolling check. The two patterns rarely co-occur.
04
Move rostering off spreadsheets. A spreadsheet cannot enforce a fatigue rule before the shift runs. Anything that does the check at shift-create time will surface 90% of breaches before they happen.

Aura OS runs the three checks at shift-create time.

Every shift you create or sign off is scanned against the 10h rest, 12h max, 76h fortnight thresholds. Warnings show up at the moment of action — not in a quarterly report. Override an alert with a reason and the audit-evidence pack records the policy, the alert, and the documented exception. $49 per month AUD, GST inclusive. Seven-day free trial, no card. Australian data.

Start free — 7-day Pro trial See the pricing maths
RP
Richard Patriquin

Richard is the founder of Clearline Health. He talks to SIL operators constantly — in forums, on calls, at conferences — and Aura OS was built out of the compliance gaps they keep running into.