SIL rostering software: shared supports, sleepovers, and roster-of-care review

A shared support shift can look simple on a calendar while still carrying several operational questions: which participants are included, what support line or agreement context applies, what worker ratio was planned, what actually happened, and what needs review before billing or payroll moves.

The NDIS provider guide to SIL describes SIL providers helping participants with day-to-day activities in the home. For software, the practical takeaway is that house context and participant context both need to be visible when the roster is approved. Source: NDIS guide to providing SIL.

A useful roster review should make the shared-support split explicit enough for managers to see whether the planned support, worker evidence, service agreement context, and downstream finance review are aligned. It should not ask finance to reconstruct that story later from notes.

Sleepovers create a common SIL software trap: payroll interpretation and participant support evidence can be treated as the same question. They are connected, but they are not identical. A provider still needs to review worker pay, active work, support evidence, participant context, and claim readiness separately.

The NDIS Commission explains that a sleepover shift is a continuous overnight span where a worker is required to sleep at a participant's premises. Fair Work guidance also says SCHADS sleepover changes took effect from an employee's first full pay period starting on or after 1 June 2026. Sources: NDIS Commission sleepover shifts and Fair Work sleepover changes.

Effica should surface that boundary rather than pretend to make legal, payroll, or claiming decisions. The product job is to keep reviewed evidence, support context, and handoff state visible so the provider can make the right decision with the right source material.

SIL rosters are often recurring, which is exactly why agreement context matters. If participant needs, house arrangements, support lines, funding management, or review owners change, the recurring roster pattern should make that drift visible before it becomes billing cleanup.

The NDIS describes a service agreement as a signed agreement covering how supports are delivered, what they are, how much they cost, how the provider gets paid, and how changes are made. A SIL roster should keep that context close enough for review. Source: NDIS service agreement guidance.

That does not mean every roster user needs to read the full agreement on every shift. It means the software should expose the current period, support context, change flags, and review owner when a roster pattern depends on those records.

A SIL roster tool should handle more than shifts and staff names. Look for house context, participant-level support visibility, shared-support ratio review, sleepover and active-overnight flags, service agreement context, mobile evidence, approval history, payroll handoff state, claim-readiness review, and clear audit trails.

Fair Work record-keeping guidance reinforces the need for accurate employment records and pay slips. For providers, that sits alongside NDIS evidence and participant support records rather than replacing them. Source: Fair Work record-keeping and pay slips.

Effica is being built around that connected review model. If your current SIL workflow depends on spreadsheet rosters, house notes, payroll exports, and separate finance cleanup, the next step is to review the SIL roster workflow against how your team actually approves support.