Daycare Incident Report Template: How to Write One That Protects You

A daycare incident report records what happened — child, time, place, staff present — in objective language, plus the care given, the child’s condition, and the parent notification, with signatures on both ends. The form is simple; the wording discipline is what makes it protective.

This guide covers the eight sections of a complete report, the language rules that keep it factual, and the special handling biting incidents need. One principle governs all of it: this document may eventually be read by someone who wasn’t there — a licensor, an upset parent, an insurance adjuster — and it must stand on its own.

The Eight Sections of a Complete Report

Whether your form says “incident” or “accident” at the top matters less than covering all eight. Most programs run one form for injuries and behavior events alike, which keeps staff trained on a single habit.

The Objective-Language Rules

The description section is where reports succeed or fail. Three rules keep it a record instead of an editorial:

Write what a camera could have seen. “Mia tripped on the playground edge and scraped her left knee” is observable. “Mia wasn’t paying attention” is an interpretation — and an admission of a supervision opinion you don’t want in a file.

No motive, no labels, no history. “He bit because he was frustrated” assigns a cause nobody can verify. “Aggressive,” “always,” and “again” attach a character to a child and a pattern to your program. The event is enough: what, where on the body, what was done.

Specifics over reassurance. “Probably fine” and “nothing serious” are conclusions that age badly if the evening brings a swollen ankle. “Ice applied for 10 minutes; walking normally; parent shown the area at pickup” documents care without predicting outcomes.

In our experience building the wording engine for our own incident tool, nearly every problematic report breaks one of these three — usually the first.

Biting Incidents: The Special Case

Biting is the incident type with two families attached, and the rule is strict: each family’s copy names only their own child. The bitten child’s report says “another child” — never the biter’s name — because the report documents your program’s response, not a referral between families.

Both reports stay factual: location of the bite, whether skin was broken, the care given, the context (time, activity, transition). If biting is recurring, the response lives in your biting policy and a separate behavior communication with the biting child’s family — the incident report is not the place to work the problem.

Notification and Signatures

The parent conversation happens the same day — a call for anything involving the head, broken skin, or real distress; at pickup for minor scrapes. The signature at pickup closes the loop: the parent read the account and was informed. Their copy goes home; the original goes in the child’s file alongside the emergency contact form it may have activated.

Every state also defines reportable incidents — the serious events that require notifying licensing itself, on the state’s timeline. That list and clock live in your state’s regulations in the National Database of Child Care Licensing Regulations; know your state’s version before you need it, because the timelines are short.

Make the Wording Automatic

Staff write incident reports at the worst possible moment — right after the incident, with a room to run. That’s the argument for a template that carries the discipline for them: labeled sections, prompts for specifics, and no free-form space that invites editorializing. Our editable version does exactly that, and the Customizer’s incident engine goes one further — staff describe what happened in plain words, and it returns the report in clean, objective language with every section covered.