Regulation 31 in Kildare
Notification of Incident: 2 non-compliance(s) in the latest reports we read.
An inspection records what inspectors saw on one day; services respond with corrective actions — how to read this.
14 May 2026
Cookies' Early Learning Centre Ltd, Cellbridge · Regulation 31 — Notification of incidents
- (e) The registered provider had not submitted a Notification of Incident form to the Agency following an incident on 11 May 2026 where a child exited the service unsupervised. The person in charge and deputy person in charge stated that they were not aware that a Notification of Incident form was required for this incident
Provider's corrective action:
- (e) Following the inspection, the Registered Provider reviewed the incident that occurred on 11 May 2026 where a child exited the service unsupervised. It was identified that a Notification of Incident should have been submitted to Tusla in accordance with Regulation 31(e). The decision not to submit a notification was reviewed by senior management and corrective action was taken to address the failure to follow reporting requirements. Management responsibilities and reporting obligations were clarified with Person in Charge and Deputy Person in Charge. The incident was reviewed as part of the service's safeguarding and compliance processes to ensure learning was identified and shared. To ensure compliance with Regulation 31(e), the Registered Provider has strengthened incident notification procedures and management oversight arrangements. A review of incident notification procedures was completed with Person in Charge and Deputy Person in Charge to ensure clarity regarding incidents that require notification to Tusla. Additional training has been provided to management teams on incident classification, mandatory notifications, safeguarding responsibilities and regulatory reporting requirements. The Deputy Person in Charge attended further training supported by senior management relating to incident management, safeguarding and reporting procedures. Learning from this training has been shared with staff teams. A Notification of Incident Guidance Document has been developed to support management in determining when a notification to Tusla is required. Any incident involving a child leaving the room unsupervised, leaving the premises, being unaccounted for or any event that may fall within the notification requirements will be escalated immediately to senior management for review. Weekly management meetings are held across all services to review incidents, discuss safeguarding matters, support Persons in Charge and ensure consistent implementation of policies, procedures and regulatory requirements. Incident records and notification requirements will be reviewed during management audits to ensure that reportable incidents are identified and notified within required timeframes. The service has adopted a precautionary reporting approach whereby uncertainty regarding the reportability of an incident will result in immediate escalation to senior management rather than reliance on individual interpretation
13 October 2025
Tiddlywinks and Scallywags, Maynooth · Regulation 31 — Notification of incidents
- (d) The registered providers did not notify the agency of a child who sought medical treatment upon collection from the service on 6 October 2025. The service managers reported they had received the information on 7 October 2025
Provider's corrective action:
- (d) A Notification of Incident form was completed by the registered provider and service manager and submitted to Tusla on 18 November 2025. A thorough review was conducted by management of the service’s policies and procedures in the aftermath of the incident with particular focus on policy 17 (Accident and Incidents). This review served to refresh management on the specific incidents that require submission of a Notification of Incident form to Tusla and that Tusla must be notified of such incidents within three working days