Priority 1 SIRS incidents must be reported within 24 hours under the Aged Care Act 2024. Persistent late reporting by body corporates attracts civil penalties up to $1.65 million.
See the reform timeline →OzlerSIRS™
Capture in 90 seconds. Triage in minutes. Report within 24 hours — every time.
OzlerSIRS walks any staff member through a structured incident capture on their phone, suggests the classification, runs the 24-hour countdown, and prepares the submission your designated officer files through the ACQSC or NDIS Commission portal.
See OzlerSIRS on a worker's phone
Real React component. Demo data. Step through a capture.
OzlerSIRS — Incident Response
Worker capture · AI triage · Designated officer approval
What happened?
Select the category that best describes the incident
AI triage — suggestion for officer review
Serious injury to a person receiving care + awareness time < 3h + fracture suspected → fits Aged Care Act 2024 §68 Priority 1.
Officer submits through the ACQSC portal. AI suggests, humans approve.
Real React component. Worker names are fictional. All data is example-only — a demonstration of how the product looks and behaves, not a live customer environment.
The first hour after an incident is not the hour to learn the system.
A worker finds a resident with a serious injury at 2:47am. What happens in the next 22 hours decides whether your notification is compliant, late, or missed. Your night staff are not trained on SIRS taxonomy. Your admin team is off-shift. Your designated officer is asleep.
SIRS extends to Support at Home providers from 1 November 2025 — many of your workers have never used a SIRS system. Priority 1 incidents (serious harm or death) must be notified within 24 hours.
OzlerSIRS is built for that 2:47am moment. A structured capture any worker can complete. AI triage that suggests the classification. A countdown that escalates if nobody acknowledges.
Priority 1 reporting deadline — serious harm or death
Source: Aged Care Act 2024
Max penalty for persistent body-corporate late reporting
Source: Aged Care Act 2024
Priority 2 reporting deadline — less severe but still reportable
Source: Aged Care Act 2024
How OzlerSIRS works
From incident to compliant submission — in 4 steps.
Structured capture — 90 seconds
A worker opens OzlerSIRS on their phone. A branching question flow captures the facts in about 90 seconds — who, when, where, what happened, who was notified. Voice dictation where typing is slow. Photo upload where useful.
AI triage suggests the classification
Our AI reviews the structured data against the ACQSC's SIRS decision support tool methodology. It suggests Priority 1, Priority 2, or non-reportable — with the reasoning and the precedent cases it drew on. AI suggests, humans approve.
24-hour countdown, managed escalation
For Priority 1, a 24-hour countdown starts the moment anyone in the organisation becomes aware. If the designated officer hasn't approved within configurable thresholds, OzlerSIRS escalates — SMS, email, and on-call rotation — until someone acknowledges.
Portal-ready submission
OzlerSIRS pre-populates the ACQSC or NDIS Commission notification form with every structured data point. Your designated officer reviews, adjusts if needed, and submits through the agency portal. Audit trail archived in your tenant.
Built for the people who run OzlerSIRS™
Care Worker / Support Worker
You find something. You open the app. The questions tell you exactly what to capture. You're done in 90 seconds and the right person is already notified.
- 90-second structured capture
- Voice dictation for hard-to-type moments
- Automatic manager notification
Registered Nurse / Clinical Lead
You review the AI's suggested classification with the facts in one screen. The 24-hour clock and the escalation path are visible. You focus on the clinical decision, not the paperwork.
- AI-suggested Priority 1 / 2 / non-reportable
- One-screen review with source facts
- Auto-escalation if approval is overdue
Quality & Compliance Manager
Every notification carries the evidence of when it was captured, who classified it, who approved it, and when it was submitted. Audit trail by default.
- Timestamped audit trail per incident
- Pattern analysis across incidents
- Direct integration with OzlerReady gap scoring
Designated Officer
Incidents route to you with context already assembled. You submit through the portal. OzlerSIRS keeps the proof.
- Portal-ready pre-populated notification
- Countdown visible from any device
- Full investigation tracker built in
Director of Nursing
Pattern detection across incidents surfaces systemic issues — falls clustering in one wing, medication incidents on the night roster, a specific worker needing support. Root cause, not root symptom.
- Pattern + root-cause analytics
- Clinical governance evidence auto-captured
- Restrictive practices register built in
CEO / Board Director
Your Board pack shows notification compliance rate, time-to-submission, and open investigations — with no manual assembly. Risk exposure is visible, not buried.
- Board-ready incident dashboard
- Time-to-submission SLA tracking
- Open investigations register
Three themes, built deep.
What the product actually does — grouped by outcome, not feature list.
Designed for 2:47am
Most SIRS tools are built for office hours. OzlerSIRS is built for the moment it actually happens.
A support worker finds something at 2:47am on a Sunday. Typing into a web form isn't viable. Calling the designated officer isn't viable. Waiting until morning is not compliant.
OzlerSIRS is a mobile-first capture flow. Structured questions, voice dictation, offline-tolerant. When the worker hits submit, the right people are notified — SMS, push, on-call rotation — with the acknowledgement loop already armed. The rest of the process runs from there.
AI triage — suggests, humans approve
OzlerSIRS's AI has read every public ACQSC guidance note. The designated officer still makes the call.
The Aged Care Act 2024 lists reportable incidents with real legal weight. Mis-classification carries consequences. Our AI doesn't replace the designated officer — it prepares the call.
The AI proposes Priority 1 / Priority 2 / non-reportable with reasoning: which facts in the structured capture triggered the classification, which ACQSC precedents apply, which edge cases to consider. The designated officer reviews, agrees or overrides, and approves. Every classification carries the AI's suggestion alongside the human decision — an audit trail the Commission will ask for.
Portal-ready, not API-pretend
No public ACQSC or NDIS Commission API accepts SIRS submissions. OzlerSIRS doesn't pretend otherwise.
OzlerSIRS generates a pre-populated submission in the exact format the ACQSC or NDIS Commission portal expects — every structured data point, every timestamp, every attachment. Your designated officer opens the agency portal, pastes the prefilled data, reviews, submits.
When agency APIs become available — and the sector is pushing for them — we will integrate. Until then, the right design is honest: we get you 95% of the way there, your designated officer does the final submission.
Concrete numbers, mapped to regulation.
OzlerSIRS captures incidents through a branching, mobile-first flow averaging 90 seconds. An AI engine — trained on publicly available ACQSC SIRS guidance and decision support methodology — suggests the classification for the designated officer to approve. Every step is timestamped and retained. Submissions are generated in ACQSC and NDIS Commission portal formats for the designated officer to file through the official portal.
OzlerSIRS is more powerful with the Ozler platform
One data layer across staffing, training, and compliance. Every product strengthens the others — this is the moat.
Incident Response Loop
A support worker reports a fall via OzlerSIRS. Root cause analysis shows a manual handling training gap. Skill2Care auto-assigns the refresher to every support worker on that roster. OzlerShield tracks completion. OzlerReady's clinical safety score improves next quarter.
Pattern Detection Loop
Three medication incidents in six weeks all involve workers at the same site whose medication training is over 12 months old. OzlerSIRS surfaces the pattern. Skill2Care pushes refreshers. OzlerShield updates credentials. The next incident, the pattern is gone.
Restrictive Practices Loop
Every restrictive practice recorded in OzlerSIRS updates the restrictive practices register. OzlerPolicy ties it to the authorising policy. OzlerReady uses it as evidence for Outcome 5.5. Audit evidence assembles itself.
Plans built around how you work.
Pick the tier closest to your size and compliance load. We'll work out the exact pricing with you once we've looked at your workforce and obligations — no one-size-fits-all quotes.
For sole traders and micro-providers meeting the minimum SIRS obligation.
Talk to us- Up to 10 workers
- Manual incident capture (web form)
- Priority 2 notifications
- Basic audit trail
For small-to-mid providers operating 24/7 care.
Talk to us- Unlimited workers
- Mobile capture + voice dictation
- AI triage with human-approval workflow
- 24-hour countdown + escalation rules
- ACQSC + NDIS Commission portal-ready exports
For mid-to-large providers needing pattern analytics and governance.
Talk to sales- Everything in Essentials
- Pattern + root-cause analytics
- Restrictive practices register
- Board-ready incident dashboard
- Quarterly governance report
White-glove migration included. Dedicated Customer Success Manager.
Ozler is not affiliated with, endorsed by, or certified by the Aged Care Quality and Safety Commission, the NDIS Quality and Safeguards Commission, or the Australian Government Department of Health, Disability and Ageing. OzlerSIRS™ is a tool to help providers meet their regulatory obligations. It does not replace the provider's responsibility to comply with the Aged Care Act 2024, NDIS Act 2013, and associated Rules and Practice Standards.
Ozler is new. We built it because the people running Australian care operations deserve better tools — workforce and compliance as one system, not two. If that resonates, we want to work with you directly.
We're onboarding a small cohort of design partners — aged care and NDIS providers who help shape the product in exchange for early access, direct founder support, and preferential pricing.
Answers to the real buyer objections.
Capture flow
Yes. If the worker loses connection mid-capture, the form saves locally and submits when the device reconnects. The 24-hour clock starts from the moment of awareness — which OzlerSIRS records independent of submission time.
They capture what happened. OzlerSIRS's AI suggests a classification — which may be "non-reportable, log only." The designated officer reviews and approves. Capturing is always safer than not capturing.
AI triage
No. The AI suggests. The designated officer approves. The officer submits through the agency portal. Every step has a human in the loop — we never automate a regulatory decision.
Publicly available ACQSC SIRS guidance, the SIRS decision support tool methodology, and NDIS Commission incident reporting publications. No real customer incident data is used in training without explicit opt-in.
Submission mechanics
No. OzlerSIRS generates a portal-ready, pre-populated submission. The designated officer submits through the ACQSC or NDIS Commission portal. Where agency APIs become available, we will integrate.
ACQSC SIRS notification format (aged care) and NDIS Commission reportable incident format (NDIS). Both generated on demand from the captured structured data.
Security & data
AWS Sydney, Australian region (ap-southeast-2). Encrypted at rest and in transit. Australian Privacy Principles compliant. Retention per your configured policy (default: 7 years for regulatory artefacts).
You can mark an incident as in-error, but the audit trail remains intact with reason and timestamp. Fully deleting regulatory evidence isn't supported — that protects you.
See OzlerSIRS™ working in your facility.
Three ways to take the next step.
No credit card. · Migration included.