Writing Incident Reports: The Mistakes That Draw Citations
An incident report is a legal record, not a note home. These are the writing habits and timing errors that turn a routine playground scrape into a finding, and what to write instead.
Writing what you concluded instead of what you actually saw
When you fill out an incident report, the difference between an observation and an assumption is the difference between a clear record and a liability. Reports that say, "Ava was pushed by Marcus because he was angry," turn a factual document into guesswork. Licensing reviewers and parents both need to know what happened, not what you think happened.
The requirement is to record exactly what you witnessed or what the child and others present reported, using direct quotes when possible. This means writing, "I saw Ava fall near the play kitchen. Marcus was standing nearby. Both children were holding dolls," instead of speculating on intent or blame. If you did not see the moment, state, "I did not see the incident, but Ava told me, 'Marcus pushed me and I fell.'" Avoid language that assigns motive, such as "on purpose," unless the child states it and you quote it directly.
Making assumptions leads to corrective actions that may not fit the situation, and can create unnecessary tension among families. More importantly, licensing officials can cite your program for not sticking to facts. If you are not sure, say so. Record the behaviors, the sequence, and the statements made. Let the documentation stand on the observable and the verifiable.
Keep reading: Family Home, Group Home, or Small Center: How the Rules Differ
Naming the other child in a biting or hitting report
One of the most common mistakes is naming the child who did the biting, hitting, or pushing when writing the report for the injured child. This can violate confidentiality rules that exist in most states and expose your program to complaints from the families of both children. Parents do not have the right to detailed information about other children's identities or behaviors.
A correct report for the family of the child who was bitten should read, "During free play, your child was bitten by another child. First aid was given. The other child's parent was notified." If you are required to record both children in your internal records, keep that copy in your administrative file, not in the folder shared with families.
When state licensing reviews your records, they look for this separation. If reports sent home include another child's name, this can lead to a citation. Only use names in documentation that stays internal, and redact or generalize when sharing with parents. This protects privacy and meets regulatory standards.
Missing time stamps, vague body location, and no description of the surface involved
Leaving Out the Time
Time matters in incident reports for three reasons: medical follow-up, child supervision review, and regulatory compliance. Some injuries have symptoms that develop over hours, especially with possible head injuries. If the report does not say when the incident happened, you leave both parents and licensing without a critical detail.
Always write the time you discovered the injury, as well as the time you first observed symptoms, if different. If you learned about the incident from another child or staff member, record when you were told and estimate the time of the event if possible, noting the uncertainty.
Location, Location, Location
Simply writing "hurt his arm" or "bumped her head" is not enough. Precise documentation means describing exactly where on the body the injury is: "small red mark, left forearm, about one inch below the elbow" or "raised bump, top right side of forehead." This helps medical professionals if the child needs care, and gives licensing a clear picture of the event.
The Surface Makes a Difference
Surface details are often overlooked, but they matter for injury investigation and prevention. Was the child on the poured rubber under the climber or the concrete walkway? Did the fall happen on carpet, tile, or grass? These details help licensing evaluate hazards and show that you are aware of your environment. In most states, failing to document the surface can be cited as an incomplete report.
Keep reading: Subsidy Payment Reform: Enrollment Based Pay and the Copay Cap
Waiting until pickup to tell a parent about a head injury
Every state has rules about parental notification for injuries that involve the head, face, or neck, and many require immediate notification for head injuries. Waiting until pickup to inform a parent that their child banged their head can result in citations and damages trust. Some symptoms of concussion or serious injury develop hours after the event, so parents need to know as soon as possible to watch for signs at home.
Best practice is to call the parent or guardian as soon as the child is stable and first aid has been given. Document the time of the call or attempted call in the incident report. If you cannot reach the parent directly, note all attempts (call, voicemail, text) and continue trying until contact is made. If your center uses written or electronic daily reports, do not rely on those alone for serious injuries. Licensing reviewers will check for prompt notification, and parents expect transparency when it comes to head injuries.
In some states, there are specific time windows for notification, and failing to meet them is a common reason for corrective action plans. Even if the injury seems minor, err on the side of caution and prioritize a real-time phone call or direct message, followed by written confirmation.
Blowing past your state's window for reporting a serious injury to licensing
State regulations set strict time frames for reporting serious injuries, hospitalizations, or allegations of abuse to the licensing agency. These windows vary but often require notification within the same business day or within 24 hours. Missing this deadline, even by a few hours, can result in significant citations and investigations.
Common mistakes include waiting to "see how the child does," assuming the injury is minor, or thinking someone else on staff will handle the reporting. If you are not sure whether an injury meets the threshold for reporting, it is always safer to contact licensing and document the call. Reporting does not mean you are admitting wrongdoing; it means you are following the law and protecting children.
Establish a clear internal protocol: who calls licensing, what information is provided, and how you document that the call was made. Keep a written record with the date, time, the name of the licensing representative, and a summary of the conversation. This protects your program and shows regulators that you take compliance seriously.
See how NapLog handles this for childcare
Treating a near miss as nothing worth documenting
Near misses, incidents where a child could have been injured but was not, are often overlooked. However, many licensing bodies expect providers to document these events, especially if they reveal a hazard or a gap in supervision. Examples include a child slipping on a wet floor but catching themselves, or almost running out the door before staff intervened.
Failing to document near misses can be seen as ignoring potential risks. It also means you miss the chance to analyze patterns and prevent future accidents. For instance, if several children nearly trip over the same threshold in a week, you have evidence to consider fixing it. Licensing reviewers may ask about your system for tracking and responding to near misses, and lack of documentation can lead to findings of insufficient safety practices.
Keep a running log of near misses, separate from injury reports if needed. Include the date, time, location, and a brief description of what almost happened. Use this log to review safety protocols and make changes when you see a pattern. This kind of documentation shows a proactive approach to safety and can be a positive point in licensing inspections.
Filing the copy and never changing the condition that caused it
The final, and perhaps most harmful, mistake is treating incident reports as paperwork to be filed, rather than as tools for improvement. Licensing agencies look for a pattern of recurring incidents in the same area or involving the same equipment. If your files show three reports of children tripping on the same rug, but the rug is still there, that is a red flag.
Every incident report should prompt some kind of review. Ask: What needs to be fixed? Does the environment need to change? Do staff need more training? Did supervision fall short? Document the follow-up action on the same report or in a central log. This could be as simple as "Moved rug to reduce tripping hazard on June 10th," or "Staff meeting held to review playground safety on March 5th."
Licensing reviewers expect to see not just documentation of injuries, but evidence that you use the reports to improve safety. Programs that file and forget are likely to face repeat citations. Make incident reviews a regular agenda item at staff meetings and track changes made as a result.
Modern recordkeeping tools can help with this process by organizing incident data, making it easier to spot trends, and linking follow-up actions to each report. Solutions that allow for quick, detailed, licensing-ready documentation, daily child reports, and incident logging support compliance and help you use every report as a step toward a safer program.
