Head Start Child Health and Safety Incident Report (OHS)
Document a reportable child health or safety incident for Head Start and capture the details OHS expects in one place. This template helps staff record what happened, what was done, and what follow-up is still open.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Head Start Programs · Early Childhood Education · Childcare Centers · Nonprofit Family Services
Overview
This Head Start Child Health and Safety Incident Report (OHS) template is built to document significant incidents involving a child’s health or safety and to support reporting under the program’s Office of Head Start process. It organizes the facts into five sections: what happened, which child was involved, the incident details, who was notified, and what corrective action will follow.
Use it when an incident needs a clear audit trail, when a supervisor must review the event, or when the program needs to show that notification and follow-up happened on time. The fields are structured to support data minimization: child initials instead of full identifiers, specific incident fields instead of open-ended narrative only, and a separate attachment area for photos, logs, or supporting documents.
Do not use this template for routine classroom notes, minor bumps that do not require escalation, or situations where your program already has a separate medical or behavior form that fully covers the event. It is also not the right place to collect unnecessary PII, such as full birth dates or unrelated family details. The best use is a reportable incident that needs accurate timestamps, a concise summary, and a documented response path from initial event through corrective action.
Standards & compliance context
- The template supports documentation and reporting workflows tied to 45 CFR 1302.102 by capturing the facts, notifications, and follow-up needed for a reportable incident.
- Use data minimization under GDPR Article 5 by collecting only the child and incident details needed to document the event and complete required reporting.
- If the incident record includes health-related information, limit access to the minimum necessary staff and avoid collecting unrelated medical details.
- For any public-facing or staff-submitted form, keep required fields clearly marked and ensure the layout is accessible under WCAG 2.1 AA.
- If the form is used for staff reporting, include a clear disclosure about what happens after submission and who can view the record.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Report Overview
This section captures the core facts first so the report has a reliable timeline and a clear reason for submission.
- Date of incident
- Time of incident
- Reported by
- Reporter role
- Incident location
- Is this believed to be a significant child health or safety incident reportable to OHS?
- Why is this being reported?
-
Brief summary of what happened
Describe the event factually and concisely. Avoid speculation.
Child Information
This section identifies the child and program context with the minimum necessary details needed to understand the incident.
-
Child initials
Use initials if your program’s reporting process allows it; otherwise enter the child’s name per local policy.
- Child age
- Program option
- Classroom, home visit group, or service setting
- Was the child in program care or supervision when the incident occurred?
-
Additional child details
Only include details necessary for the incident record and follow-up.
Incident Details
This section records what happened, whether anyone was injured, and what conditions or factors contributed to the event.
- Incident type
- Did an injury occur?
- Describe the injury
- Was medical attention needed?
-
How long was the child missing?
Enter the estimated number of minutes.
- Describe the hazard or unsafe condition
- Contributing factors
Notifications and Response
This section documents who was told, when they were told, and what immediate actions were taken after the incident.
- Immediate actions taken
- Was the parent or guardian notified?
- Time parent or guardian was notified
- External notifications made
-
Notification details
Include who was contacted, when, and by whom. Do not include unnecessary PII.
-
Anonymous submission requested for internal follow-up?
Use only if your internal process allows anonymous intake for follow-up concerns. This does not remove required compliance reporting obligations.
Corrective Actions and Follow-up
This section turns the report into action by assigning fixes, ownership, due dates, and supporting attachments.
- Corrective actions taken or planned
- Was a policy, procedure, or supervision plan updated?
- Follow-up owner
- Follow-up due date
-
Supporting documentation
Attach only documents needed for the audit trail, such as witness statements, photos, or notification logs.
How to use this template
- 1. Set up the form with your program’s incident categories, required notification rules, and any conditional logic for injuries, missing-child events, or hazards.
- 2. Enter the report overview first by recording the incident date and time, the reporter’s name and role, the location, and a brief summary of what happened.
- 3. Complete the child information section with only the details needed to identify the child and understand the program context, using progressive disclosure for any extra details.
- 4. Fill in the incident details with the incident type, whether an injury occurred, what medical attention was needed, and any factors that contributed to the event.
- 5. Document notifications, immediate response actions, and external contacts, then assign a follow-up owner, due date, and corrective actions before closing the report.
Best practices
- Record the incident time and the notification time separately so reviewers can see how quickly the program responded.
- Use child initials and the minimum necessary details unless your internal process requires more information for the reportable event.
- Add conditional logic so staff only see fields that apply to injuries, missing-child incidents, or hazards instead of a long irrelevant form.
- Describe the hazard or injury in plain language and avoid vague entries like 'incident occurred' or 'student was hurt.'
- Capture immediate actions before the narrative fades, including first aid, supervision changes, area closure, or escalation to leadership.
- Attach photos, logs, or witness notes only when they support the report and are permitted by your privacy rules.
- Assign one follow-up owner and one due date so corrective actions do not get lost after the initial report is submitted.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What incidents belong in this Head Start OHS report?
Use this template for significant child health or safety incidents that must be documented and reported under your program’s OHS process. It is designed for events such as injuries, missing-child situations, hazards, or other reportable safety concerns. If the event is minor and handled entirely within classroom documentation, this form may be more than you need.
Who should complete the report?
It is usually completed by the staff member who first learned of the incident, then reviewed by a supervisor, health manager, or program leader. The form captures the reporter’s name and role so the audit trail is clear. If your program uses delegated reporting, keep the same structure and assign one accountable owner.
How soon should this be filled out after the incident?
Complete it as soon as the situation is stable and the facts are fresh, then finalize any missing notification details once parents, guardians, or external agencies have been contacted. The template includes time-based fields so you can record the incident time, notification time, and follow-up due date. Delays usually create gaps in the record and make review harder.
Does this template collect child PII?
It uses child initials and limited context fields rather than full identifiers, which supports data minimization. Only add additional child details if they are necessary for the reportable incident and your internal process. If you do collect sensitive information, include clear disclosure language and limit access to authorized staff.
Can parents or guardians be notified from this form?
The form records whether a parent or guardian was notified and when, but it does not replace your communication process. Use the notification fields to document who was contacted, what was shared, and any follow-up instructions. If your program needs a separate call log or consent record, link or attach it.
How does this handle anonymous submission requests?
The template includes an anonymous submission request field so you can capture concerns without forcing a named reporter in every case. That is useful for staff who need a safer reporting path, but it should not remove the accountability needed for incident review. If anonymity is allowed, define who can see the submission and how follow-up will work.
What should be customized for our program?
Customize the incident types, external notification options, corrective action choices, and any program-specific escalation rules. You can also add conditional logic so only relevant fields appear for injuries, missing-child events, or hazards. Keep the form short enough that staff can complete it during a real incident without skipping required details.
How does this compare with an ad hoc incident email or note?
An ad hoc email often misses key facts, timestamps, and follow-up ownership. This template standardizes the fields needed for a clean audit trail, clearer review, and faster corrective action. It also makes it easier to route the report to the right person and keep attachments with the record.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
Learn how organizations with hourly workers, union contracts, and shift differentials can apply compensation rules consistently and accurately at scale.
-
MangoApps NoCode Workflow Apps let teams build, customize, and deploy employee apps without IT—automating workflows and boosting operational efficiency fast.
Ready to use this template?
Get started with MangoApps and use Head Start Child Health and Safety Incident Report (OHS) with your team — pricing built for small business.
