The record that actually prevents the next accident

A usable accident or incident record captures what happened, when, where, who was involved, the injury or concern, the first aid given, parent contact, any emergency contact made, staff witnesses, and — the step that's easiest to skip — what changed afterward to stop it recurring. A record that stops at "child fell, ice pack applied" hasn't done the second half of its job.

Serious incidents carry their own clock: Tusla notification is required within 3 working days under Regulation 31, and that requirement applies to serious incidents generally, not just accidents specifically — a serious near-miss with no injury still needs the same notification discipline as one with an injury attached.

Individual care or health plans exist for the same underlying reason: a medical condition, allergy, disability, or additional need that requires specific action shouldn't live only in a parent's head or a general note. It needs to say what the risk is, what staff do about it day to day, and what changes if the child's needs or medical advice change — and it needs reviewing when that advice does.

Bloomffy treats accident and incident reports as append-only for exactly the reason that record integrity matters here: a correction is a new, dated entry, never an edit to what was originally written. The signature model reflects how these actually get closed out in a real service — captured digitally in-app, then a physical printout is signed by both the person in charge and the parent, with the scanned signed copy tracked back into the same record — so the report isn't considered closed until both signatures genuinely exist, not just the description of what happened.

Serious incidents also get surfaced directly on the admin dashboard, merging accident and incident reports into one Regulation 31 view, because the failure mode this is designed against isn't "nobody wrote the report" — it's "the report exists somewhere and nobody acted on the 3-day clock."