Common questions
SIL management software — frequently asked
Pulled from real procurement and demo questions covering single vs multi-home operation, ratios, SDA, travel claims, group programs, and BSP encryption.
- Is CareOS SIL software suitable for single-home and multi-home operators?
- Yes. The SIL data model carries from a single shared two-bedroom home through to multi-site SIL operators with cross-home worker pools. Per-home compliance evidence, ratio rules, and SDA payment reconciliation work the same at any scale.
- How does CareOS handle SIL ratio compliance during rostering?
- Daily and overnight ratios are configured per home. The roster engine flags shifts that drop below the funded ratio before publishing, so coordinators correct coverage gaps before they become compliance gaps. Worker hours roll up to SCHADS Award 2010 timesheet calculations including overnight active/inactive splits.
- Can the same record carry SIL plus SDA-funded properties?
- Yes. SIL homes that are also SDA-funded properties carry both data sets — the SIL operations record (residents, ratios, BSPs, claims) and the SDA property register (design category, occupancy, vacancy, payment reconciliation) — without duplicating the property record.
- How are travel claims handled for SIL workers?
- Travel time, mileage, and vehicle allowance roll up against participant plans where the funder allows it. The system honours plan-specific travel rules so coordinators are not deciding eligibility shift-by-shift; SCHADS-compatible travel time enters the worker timesheet for payroll.
- Does CareOS support group programs and centre-based supports alongside SIL?
- Yes. Group programs (community participation, capacity-building groups, day options) carry their own participant ratio rules independent of SIL home ratios. Workers can roster across SIL homes and group programs in the same period; timesheets and claims stay distinct per program.
- Are Behaviour Support Plans encrypted in the SIL module?
- Yes. Behaviour Support Plans live encrypted on the participant record (AES-256), with role-based access — SIL workers see only the plan content their role permits, while quality teams see the full audit trail. Restrictive practices are logged incident-by-incident with the authorisation context.