content-left-bg.png
content-right-bg.png

National Decision Tree—new guidance on when to lodge a notification

 
WebPartZone1_1
PublishingPageContent

​​a bandage being placed on a child's finger

​Would you like support to understand when you need to notify your regulatory authority of an incident, complaint or change of information?

The Australian Children's Education and Care Quality Authority (ACECQA) website now features an interactive notifications National Decision Tree, designed to help approved providers and their staff identify whether a notification must be made to the regulatory authority (and in what timeframe).

Approved providers must notify the regulatory authority of certain incidents, complaints and changes to information under the Education and Care Services National Law. Notifications provide transparency and accountability. They also enable serious incidents, complaints and breaches of the National Law and National Regulations to be effectively monitored, tracked and resolved.

The National Decision Tree provides guidance and information about all notifications that must be made to the regulatory authority under the National Law and National Regulations.

If you need to lodge a notification, the National Decision Tree will provide you with information about how long you have and the next step to take. Users will be directed to log in and lodge the relevant online form via the National Quality Agenda IT System.

You should remember to fill in all relevant form fields and include any relevant documentation so the regulatory authority can assess whether it must take any action.

The National Decision Tree includes guidance and explanations of key terms, including ‘trauma’, ‘missing from the service’, ‘not accounted for’, ‘physical abuse’, ‘sexual abuse’, ‘complaint’ and more.

It also includes useful examples of scenarios that must be notified, including serious injuries, serious illnesses and circumstances that pose a risk to the health, safety or wellbeing of children.​

WebPartZone1_2
WebPartZone2_1
WebPartZone2_2
WebPartZone2_3
WebPartZone3_1
WebPartZone3_2
WebPartZone3_3
WebPartZone3_4
WebPartZone4_1
WebPartZone5_1
WebPartZone5_2
WebPartZone6_1
WebPartZone6_2
WebPartZone7_1
WebPartZone7_2
WebPartZone8_1
WebPartZone8_2
WebPartZone9_1
Back to news feed
Last updated 12 July 2024