Biting Incident Documentation Form (Infant/Toddler)
A biting incident documentation form for infant and toddler classrooms that records what happened, who was involved, injuries, parent notification, and follow-up. Use it to create a clear childcare record and support consistent response.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Childcare Centers · Early Learning Programs · Preschools · Montessori Schools
Overview
This form captures the core facts of a biting incident in an infant or toddler classroom: when it happened, where it happened, who was involved, what was happening right before the bite, whether any injury was observed, what first aid or comfort measures were provided, and how parents were notified. It is meant for childcare recordkeeping, staff follow-up, and consistent communication with families.
Use this template when a bite occurs and you need a clear, factual record that can be completed quickly after the incident. It works well for single events, repeated biting patterns, and situations where the staff member needs to document witnesses or note a possible trigger. The anonymous submission option can be useful for internal reporting workflows, but child-specific fields still need to be completed when the incident involves a named child.
Do not use this form as a disciplinary report or as a place to speculate about intent, diagnosis, or blame. It is not the right template for older-child behavior incidents, major injuries requiring emergency response, or medical documentation beyond immediate observation and first response. Keep the entries specific, observable, and brief so the record is useful later and easy for staff to complete in real time.
Standards & compliance context
- Keep the form aligned with GDPR data minimization by collecting only the child, witness, and notification details needed for the incident record.
- If the form is public-facing or parent-accessible, follow WCAG 2.1 AA practices with clear labels, keyboard access, and readable error messages.
- Use anonymous submission only for internal reporting workflows where child-identifying details are not required, and do not use it to replace mandatory incident documentation.
- Avoid collecting unnecessary sensitive information in the notes field, and limit health-related details to the minimum necessary for the bite 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
Incident Overview
This section anchors the record with the date, time, classroom, and incident type so the event can be filed and searched later.
- Date of incident
- Time of incident
- Classroom / room
- Incident type
-
Submit anonymously
Select this only if your program allows anonymous submission for internal reporting. Do not include names or other PII if submitting anonymously.
Children Involved
This section identifies the children and any witnesses so the report is tied to the correct people without adding unnecessary detail.
- Child who was bitten
- Child who bit
- Were there witnesses?
-
Witness names
List staff witnesses only if needed for follow-up.
Circumstances and Behavior
This section captures what was happening before the bite so staff can document context, triggers, and repeated patterns.
- What activity was happening?
-
What happened immediately before the bite?
Describe observable events only. Avoid speculation or blame.
- Possible trigger or contributing factor
- Has this child shown similar biting behavior before?
Injury and Immediate Response
This section records what was observed and what staff did right away, which is essential for safety follow-up and parent communication.
- Was an injury observed?
-
Describe the injury
Include visible marks, redness, swelling, or broken skin if observed.
- First aid provided
-
Immediate staff response
Describe what staff did immediately after the incident.
Parent Notification and Follow-Up
This section shows when families were informed and what happens next, turning the incident record into an actionable follow-up log.
- Parent or guardian notified?
- Notification method
- Time parent or guardian was notified
- Follow-up actions
- Additional notes
How to use this template
- Set up the form with the incident date, time, classroom name, and anonymous submission option so staff can start the record immediately after the bite.
- Enter the children involved and any witnesses, using the witness names field only when a witness was actually present and relevant to the report.
- Describe the activity at the time, the events that led up to the bite, and any possible trigger using observable facts rather than assumptions.
- Record whether an injury was observed, describe the injury if present, and note the first aid or comfort measures provided by staff.
- Document when and how the parent or guardian was notified, then list any follow-up actions such as monitoring, behavior tracking, or director review.
- Review the completed form for accuracy, save it in your childcare recordkeeping system, and use it to guide any required classroom or family follow-up.
Best practices
- Write the incident while details are fresh so the activity, timing, and response are based on direct observation.
- Use field types that match the data, such as a date picker for the incident date and a time field for the incident time.
- Keep the language factual and avoid guessing about motive, intent, or developmental causes unless your policy requires a separate review.
- Use progressive disclosure for follow-up fields so staff only see extra questions when an injury, repeated behavior, or parent notification applies.
- Mark required versus optional fields clearly so the form stays fast to complete during a busy classroom day.
- Document the immediate response in enough detail that another staff member can understand what was done without asking follow-up questions.
- Include a clear note about what happens after submission so staff know who reviews the record and how parents are informed.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What age group is this form for?
This template is designed for infant and toddler rooms where biting incidents are more likely to occur and need quick documentation. It focuses on the immediate facts a caregiver can observe, rather than a disciplinary record. If you serve older children, you may want a broader incident report template instead. The fields are written to support age-appropriate, non-punitive follow-up.
How often should this form be used?
Use it every time a biting incident occurs, even if the injury seems minor or the bite did not break skin. Consistent logging helps staff spot patterns such as time of day, transitions, or repeated triggers. It also creates a reliable record for parent communication and internal review. If your center has an escalation policy, this form can feed that process.
Who should complete the form?
The staff member who witnessed the incident or responded first should complete it, with a supervisor reviewing if needed. That person is usually best positioned to capture the activity at the time, immediate response, and notification details. If multiple staff observed the event, one person should consolidate the facts to avoid duplicate or conflicting entries. Keep witness names in a separate field only when they are relevant to the record.
Does this form need to collect child names and other PII?
Yes, but only the minimum necessary information needed for childcare recordkeeping and follow-up. Avoid adding extra identifiers that are not needed for the incident record, and keep any notes factual rather than speculative. If your workflow allows anonymous submission for internal reporting, that can be useful for staff safety or escalation concerns, but it should not replace required child-specific documentation. Make sure parent notification language is clear about what will be shared and why.
What are the most common mistakes when using a biting incident form?
Common mistakes include writing vague summaries, skipping the time of the incident, and failing to document the immediate response. Another frequent issue is recording opinions about intent instead of observable behavior, which makes the record less useful. Staff also sometimes forget to note whether parents were notified and by what method. This template is built to reduce those gaps with separate fields for facts, response, and follow-up.
Can this template be customized for our center's policy?
Yes, and it should be. You can add fields for classroom ratio, director review, incident severity, or behavior plan follow-up if those are part of your process. You can also adjust the witness section, parent notification options, and additional notes to match your documentation standards. Keep the form short enough that staff can complete it immediately after the incident.
How does this compare with an ad-hoc note or message to parents?
An ad-hoc note is easy to forget, hard to standardize, and often misses details that matter later. This template gives staff a repeatable structure so every incident captures the same core facts: what happened, who was involved, what care was provided, and how parents were informed. That consistency helps with internal review and reduces confusion when incidents recur. It also makes it easier to spot patterns across classrooms.
Can this form connect to other childcare workflows?
Yes. It can be paired with attendance records, daily classroom logs, parent communication tools, or behavior tracking forms. If your system supports conditional logic, you can show follow-up fields only when an injury occurred or when the incident was repeated. That keeps the form shorter while still capturing the details you need. It also helps staff move from documentation to action without re-entering the same information.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
Ready to use this template?
Get started with MangoApps and use Biting Incident Documentation Form (Infant/Toddler) with your team — pricing built for small business.