Loading...
compliance

Head Start Child Health and Safety Incident Report (OHS)

Document and report significant Head Start child health and safety incidents to OHS with the right details, notifications, and follow-up in one place.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Head Start Programs · Early Childhood Education · Nonprofit Child Services

Overview

This template is a structured incident report for Head Start programs that need to document significant child health and safety events and determine whether Office of Head Start notification is required. It captures the report overview, child information, incident details, health or safety impact, immediate response, external and internal notifications, and follow-up actions in a single audit-ready record.

Use it when an incident involves injury, illness, unsafe supervision, environmental hazards, emergency medical response, or any event that may trigger reporting under 45 CFR 1302.102. The form is especially useful when multiple staff members respond and you need one consistent record of what happened, who was notified, and what corrective action is assigned. It also supports a clear audit trail with submitter signature and PII disclosure acknowledgement.

Do not use this template for routine classroom notes, minor bumps that are fully handled in standard daily communication, or broad program complaints that do not involve a child health or safety incident. It is also not the right form if you need a general parent communication log, staff injury report, or anonymous whistleblower channel. Keep the report focused on facts, use conditional logic for fields that only apply in certain cases, and avoid collecting unnecessary PII. The goal is a complete, defensible incident record that staff can submit quickly and compliance teams can review without rework.

Standards & compliance context

  • This template supports documentation needed for Head Start incident reporting under 45 CFR 1302.102 when an event may require notification to the Office of Head Start.
  • The child information fields should follow data minimization principles by collecting only the PII needed to identify the incident and complete required reporting.
  • The PII disclosure acknowledgement and submitter signature help establish an audit trail for internal review and retention.
  • If the form is used in a public-facing intake or portal, it should meet WCAG 2.1 AA accessibility expectations for labels, validation, and keyboard navigation.
  • For health-related incidents, keep the record aligned with the minimum-necessary principle by limiting medical details to what is needed for response and reporting.

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 basic facts of the report so reviewers can identify the event, the reporter, and the program site without searching through narrative notes.

  • Date of report (required)
  • Time of report (required)
  • Reporter name (required)
  • Reporter role (required)
  • Program or grantee name (required)
  • Center, home-based site, or location name (required)
  • Incident type (required)

    Select all that apply. Additional fields will appear based on your selections.

  • Brief incident summary (required)

    Describe what happened in plain language. Do not include unnecessary PII.

Child Information

This section identifies the child and notification status while keeping PII limited to what is needed for the incident record.

  • Child identifier (required)

    Use the child ID or internal identifier rather than full name when possible.

  • Child age

    Enter age in years if needed for the report.

  • Child enrollment option (required)
  • Specify other enrollment option (required)
  • Was the parent or guardian notified? (required)
  • Time parent or guardian was notified

Incident Details

This section records when, where, and under what conditions the incident happened so the timeline and context are clear.

  • Date of incident (required)
  • Time of incident (required)
  • Incident location (required)
  • Specify other incident location (required)
  • Supervision status at the time of incident (required)
  • Environmental or contributing factors
  • Specify other contributing factor (required)

Health or Safety Impact

This section shows the outcome of the incident, including whether injury or illness occurred and what medical response was needed.

  • Did the child experience an injury or illness? (required)
  • Severity
  • Immediate medical response
  • Specify other medical response (required)
  • Was hospitalization required?

Immediate Response and Notifications

This section documents who was told, when they were told, and whether OHS notification is required so deadlines are not missed.

  • Internal notifications completed (required)
  • Specify other internal notification (required)
  • External notifications completed
  • Specify other external notification (required)
  • Is Office of Head Start notification required? (required)
  • Notification deadline

    Enter the deadline if a report to OHS is required.

Follow-up, Consent, and Audit Trail

This section assigns corrective action, confirms disclosure acknowledgement, and preserves the signature trail for review and retention.

  • Follow-up actions taken or planned (required)
  • Corrective action owner
  • Target completion date
  • PII disclosure acknowledgement (required)

    I understand this form collects only the minimum necessary PII for compliance reporting and follow-up, and the information will be used for audit trail, notification, and corrective action purposes.

  • Submitter signature (required)

How to use this template

  1. 1. Set up the report by entering the report date, time, reporter details, program name, site name, and a clear incident type before the record is routed for review.
  2. 2. Identify the child using the least amount of PII needed, record the child program option, and note whether the parent or guardian was notified and when.
  3. 3. Document the incident facts with the date, time, location, supervision status, and environmental factors, using the other fields only when the standard options do not fit.
  4. 4. Record the health or safety impact by selecting whether injury or illness occurred, the severity, the medical response, and whether hospitalization was required.
  5. 5. Capture all internal and external notifications, confirm whether OHS notification is required, assign corrective action ownership, and set a target completion date.
  6. 6. Review the completed form for accuracy, confirm the PII disclosure acknowledgement, and submit with a signature so the record is ready for audit trail retention.

Best practices

  • Use conditional logic so staff only see the fields that apply to the specific incident, which reduces errors and speeds submission.
  • Mark required and optional fields clearly, and keep free-text fields limited to facts that cannot be captured with structured choices.
  • Record the incident as close to the event time as possible so the timeline, notifications, and supervision details stay accurate.
  • Use a child identifier instead of unnecessary personal details unless a specific disclosure is required for the report.
  • Capture the parent or guardian notification time separately from the incident time so reviewers can verify response timing.
  • Assign one corrective action owner per follow-up item to prevent duplicated work and unclear accountability.
  • Keep environmental factors specific, such as broken equipment, unsecured access, or staffing gaps, rather than writing a vague summary.
  • Review the final record for consistency before submission so the audit trail matches the narrative and the selected fields.

What this template typically catches

Issues teams running this template most often surface in practice:

The incident summary is too vague to show what actually happened or why the event was reportable.
Parent or guardian notification is left blank, making it impossible to confirm whether contact occurred and when.
Supervision status is not documented, which weakens the review of how the incident happened.
Staff choose the wrong incident location or use the other field without enough detail to identify the setting.
Medical response is described in general terms but does not show whether emergency care, first aid, or hospitalization was involved.
Corrective actions are listed without an owner or target completion date, so follow-up stalls.
The form collects more child PII than necessary instead of using the child identifier field.
Notification deadlines are not tracked, which creates risk when OHS reporting may be time-sensitive.

Common use cases

Head Start Center Director
A center director uses the form after a child injury on the playground to document the timeline, parent notification, and whether OHS reporting is required. The report becomes the official record for leadership review and corrective action assignment.
Health and Safety Manager
A health manager completes the template after a medication-related incident to capture the response, any medical escalation, and follow-up steps. The structured fields help the team compare the event against internal reporting thresholds.
Family Services Coordinator
A family services coordinator records the parent or guardian notification details and any communication barriers after an incident. This keeps the contact history tied to the incident record without adding unrelated personal data.
Program Compliance Lead
A compliance lead reviews the completed report for completeness, confirms the OHS notification deadline, and checks that the audit trail is intact. The form supports consistent review across sites and reduces missing documentation.

Frequently asked questions

What incidents should be recorded in this template?

Use this template for significant child health and safety incidents that require internal review, parent or guardian notification, or reporting to the Office of Head Start. It is meant for events where the program needs a clear incident summary, response record, and follow-up plan. If the event is minor and handled entirely within routine classroom documentation, this form may be more than you need. When in doubt, use the template to capture the facts and route the report for review.

Who should complete the report?

The report is usually completed by the staff member who first learned of the incident, then reviewed by a supervisor, health manager, or compliance lead. The template includes fields for reporter name, role, and submitter signature so the audit trail shows who entered the information. Programs can assign ownership differently, but the form should always make clear who is responsible for submission and follow-up. That helps avoid gaps when multiple staff respond to the same event.

How often is this form used?

It is used whenever a reportable incident occurs, not on a fixed schedule. Some programs may also use it as part of a same-day escalation process so leadership can decide whether OHS notification is required. The notification deadline field helps teams track time-sensitive reporting obligations. If your program has an internal incident log, this template can serve as the formal record for the cases that rise to the compliance level.

Does this template support privacy and minimum-necessary data collection?

Yes. The structure is designed to collect only the fields needed to document the incident, notify the right parties, and complete follow-up. Use the child identifier field instead of unnecessary personal details, and keep PII disclosure acknowledgement tied to the actual report workflow. If your program does not need a specific data point, leave it out rather than adding extra free-text fields. That supports GDPR data minimization and the minimum-necessary principle.

What should we do if the child’s parent or guardian could not be reached right away?

Record the notification attempt, the time it was made, and any follow-up attempts in the parent or guardian notification fields and internal notes. If contact was not possible, the form should still show what the program did next and who was informed internally. This helps create a complete audit trail and avoids ambiguity later. Programs should also follow their own escalation policy for delayed contact.

How does this template help with OHS reporting requirements?

The template includes fields for incident type, severity, medical response, hospitalization, external notifications, and the OHS notification deadline. That structure helps staff capture the facts needed to decide whether the incident meets the threshold for reporting under 45 CFR 1302.102. It also keeps the report focused on what happened, what was done, and what remains open. That reduces the risk of missing a required notification or follow-up action.

Can we customize the fields for our program option or site setup?

Yes. The template already includes program name, site name, child program option, and an optional other field for cases that do not fit standard categories. You can add conditional logic for your specific site roles, internal notification chain, or corrective action workflow. Keep the form lean and avoid adding fields that do not support a real reporting or compliance need.

What integrations are useful with this form?

Common integrations include task assignment for corrective actions, email or workflow alerts for notification deadlines, and document storage for the final audit trail. Some programs also connect the form to incident logs or case management systems so follow-up stays linked to the original report. If you use automation, make sure the submitter still reviews the final record before it is sent. That helps prevent incomplete or inaccurate submissions.

What are the most common mistakes when using this template?

Common mistakes include leaving the incident timeline vague, skipping the supervision status, and using free text where a structured field would be clearer. Another frequent issue is failing to record whether parent or guardian notification happened and when. Programs also sometimes over-collect personal details instead of using the child identifier field. The best results come from capturing the facts quickly, then completing follow-up after the immediate response is documented.

Go deeper on the topic

Related concepts
  • 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...
Related guides

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.

Get Started