Skip to content
Corella

For SIL & supported accommodation

Residents, houses, sleepovers — modelled properly.

Supported accommodation breaks software that was built around visits. The roster runs continuously, sleepovers and two-staff ratios are normal rather than exceptional, the house itself has documents and risks of its own, and the people living there are residents. Corella models all four — including the word — so a SIL provider isn't bending a visit-shaped system into a 24-hour one.

Accommodation, without the workarounds

  • Say resident — set once, used across every screen and export
  • Sleepovers and multi-staff ratios as first-class shift types
  • Award checks that understand sleepover length, frequency and rest after
  • Group shifts that split billing across the residents supported
  • Documents and risk assessments that belong to the house, not to one person
  • Restrictive practices register with the Commission's monthly CSV
  • Reportable incidents with 24-hour and five-day countdown timers
  • Continuous rosters with conflict checks, overrides and a full trail

Sleepovers the award actually recognises

Sleepovers are where accommodation rosters and payroll quietly go wrong. Corella treats them as a real shift type, and the SCHADS award checks that run over the draft roster include sleepover length, sleepover frequency and rest after a sleepover alongside the rest of the nine. The checks warn while the week is still a draft; they never block, because sometimes a provider has to wear it knowingly.

The house is a thing, not a field

A fire evacuation plan, a vehicle, an environmental risk assessment and a set of house rules belong to the house rather than to whichever resident's file they were first attached to. Corella keeps program and organisation-level documents and risks separately from personal ones, with expiry alerts and read-and-acknowledge tracking, so the house's paperwork is findable by whoever is on shift.

One roster, several residents, correct billing

A shift supporting three residents at once is one shift, and Corella splits the billing across them rather than making you create three and hope they stay in sync. The same record carries the award check, the timesheet, the invoice lines and the payroll cost — so what the roster promised and what the pay run produces cannot drift apart.

Go deeper

SCHADS award checks Your words Compliance & documents

Fair questions

Asked by teams like yours.

Do you cover residential aged care facilities?
No. Corella is built for in-home and community delivery plus supported accommodation — SIL, community programs and disability supports. Residential aged care facility management is a different product and we would rather do this properly than stretch thin over both.
How are sleepovers paid?
Through the same payroll engine that runs the rest of the pay run — a labelled, simplified SCHADS-style engine, with sleepover-specific award checks flagged on the draft roster before the week is worked. Every figure is arithmetic your finance person can check by hand, which for pay is a stronger promise than anything automated.
Can documents belong to a house rather than a resident?
Yes. Program and organisation-level documents and risk assessments are first-class, with expiry alerts and read-and-acknowledge tracking, so the house's fire plan and environmental risk assessment aren't buried on one resident's file.
Will it say resident everywhere, including reports?
Everywhere your team reads it — nav, headings, table columns, filters, dialogs, report titles and the headers of exported CSVs. The two exceptions are deliberate: web addresses never change, and a document the NDIS requires keeps the scheme's own wording, so a service agreement still says participant. The interface follows your words; documents a scheme requires keep the scheme's.

See your organisation in Corella.

A 30-minute walkthrough with the people who built it — your workflows, your terminology, not a canned demo.

Book a demoor email sales@corellacare.com.au