Describe how your daycare documents an accident, injury, behavior event, or unusual occurrence. Makeform turns your process into a clear staff form with child details, an objective incident narrative, witnesses, immediate actions, parent notification, and follow-up fields in one consistent record.
Route completed reports to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose the situation closest to your center, revise the wording, or send the prompt into the Makeform builder. Each structure is a practical starting point, not a completed incident record.
Audience
Teachers documenting a fall, collision, or equipment-related event
Format
Staff report with body-area selection and parent notification
Prompt size
389 chars
Example form structure
Staff report with body-area selection and parent notification
Child, classroom, incident date, time, and location
What did staff directly observe?
Body area and visible signs
Immediate actions taken
Parent notification and acknowledgment
Suggested routing tags
Parent notified
Director review
Follow-up due
Separate what staff directly observed from what the child or witnesses said. This makes the report easier for a parent and director to understand without turning assumptions into facts.
Step 1
Observe
record the time, place, people, and facts
Step 2
Respond
document care, comfort, and immediate safety steps
Step 3
Notify
log family contact and director review
Step 4
Follow up
assign prevention tasks and close the record
Why a structured incident form
When staff are caring for children and speaking with families, a blank page is easy to postpone or fill with vague recollections. A structured daycare incident report form prompts for the same essential facts every time and leaves room for a human, objective account.
Dedicated fields for the setting, activity, sequence, witnesses, and visible signs help staff write what they saw and heard. Separate fields for a child's statement or a witness account keep reported words distinct from direct observation.
Capture who contacted the parent or guardian, the method, each attempt, the time reached, information shared, and the pickup decision. A required notification block prevents the communication step from disappearing into a hallway conversation.
Turn a loose suggestion such as check the climbing area into an assigned action with an owner, due date, status, and closure note. Directors can distinguish a completed report from an unresolved safety task.
One form, several incident paths
A scraped knee, a biting event, and a near miss share basic identifying details but need different follow-up. Conditional sections keep the form short for staff while preserving the details each event type requires.
Show body-area, visible-sign, first-aid, activity outcome, and family-contact fields only when an injury is selected. Allow a photo when center policy calls for one, without making uploads mandatory for every minor event.
Record observable actions, what came before, staff response, support for each child, and prevention planning. Keep another child's identifying information in an internal section rather than repeating it in the family-facing report.
Document the hazard, who noticed it, who could have been affected, how staff secured the area, and what correction remains. No-injury events can bypass care fields and move directly to corrective action.
Use an adaptable path for supervision concerns, missing belongings, unauthorized access, facility disruptions, or other events your center tracks. Add a custom category while keeping the shared timeline and review fields.
Incident reporting workflow
Start with your center's rooms, incident types, contact expectations, and review path. Makeform creates the structure, then you refine the language and route completed submissions to the right people.
Tell the builder which events staff report, which rooms or locations belong in dropdowns, what parent-contact details matter, and who reviews each submission. Include separate paths for injuries, behavior events, and near misses.
Replace generic options with your classroom names, define required fields, and split internal notes from the parent-facing summary. Phrase narrative prompts around observation: where everyone was, what occurred in sequence, and what staff did next.
Send the completed report to the director or designated reviewer and log the family notification within the same submission. Use conditional routing to flag records that still need contact, review, or a corrective action owner.
Run a fictional incident through the form on a phone before launch. Confirm staff can find it quickly, required questions make sense under pressure, signatures appear in the intended path, and a reviewer can understand the event without asking for missing basics.
Online form vs paper record
The useful record is more than a narrative. It connects the staff member's account, immediate response, parent communication, director review, and any remaining prevention work.
Field guide
Use these six sections to capture an understandable timeline, document the response, communicate with families, and make unfinished safety work visible. Adapt the fields to your own center policy and review process.
Record identity
Start with information that lets a director place the event without searching another system. Use structured classroom and location options wherever possible, and record who completed the report separately from who supervised or witnessed the event.
Objective narrative
Ask what staff directly saw and heard before requesting interpretations or prevention ideas. A useful narrative names the setting, the activity immediately before the event, the sequence of observable actions, and where each adult was positioned. Give statements their own labeled fields.
Condition & response
When an injury path is selected, collect the affected body area, visible signs, the child's immediate response, and the actions staff took. Use a checklist for common actions plus a narrative field for exact details. The form records the response; it does not decide care.
Family notification
A single parent notified checkbox hides too much. Collect the guardian contacted, phone or in-person method, time of each attempt, whether contact succeeded, the staff member who communicated, and any agreed pickup or observation plan. Keep a space for acknowledgment without implying that it changes the factual record.
Privacy-aware details
An event may involve several children, but each family's communication should stay focused on their child. Build an internal section for names, witness coordination, staff coaching, or sensitive operational notes, then create a parent-facing summary that avoids identifying another child.
Review & prevention
Director review should confirm that essential details and notification steps are present, then create follow-up when the environment, routine, staffing, or equipment needs attention. Assign each task to a person and give it a due date so closure is more than a signature.
Related tools
Use a focused report for the event itself, then support enrollment, emergency contacts, classroom safety checks, behavior documentation, and broader accident workflows with related Makeform tools.
Build a general incident workflow for facilities, visitors, staff, or events outside the child-specific daycare process.
Open toolCapture a detailed accident timeline, witnesses, immediate action, and review when the workflow extends beyond childcare.
Open toolCollect family, child, pickup, schedule, and enrollment information before the child's first day at the center.
Open toolKeep guardian and emergency contact details organized so staff know whom to reach when an incident occurs.
Open toolTurn room inspections into a repeatable checklist and assign corrections before a hazard leads to an incident.
Open toolUse a behavior-centered report for observable actions, staff response, impact, and a structured follow-up plan.
Open toolFAQ
Practical answers for childcare owners, directors, teachers, and administrators designing a consistent reporting workflow.
A daycare incident report form is a structured record staff complete after an accident, injury, behavior event, near miss, or unusual occurrence involving a child. It identifies the child, time, place, people present, observable sequence, visible signs, immediate response, parent notification, review, and follow-up. It gives staff and families a clear account and makes unfinished action visible. Your center decides which events require a report and how records are reviewed, shared, and retained.
Include the child's name or identifier, classroom, incident date and exact time, location, activity before the incident, reporting and supervising staff, witnesses, objective description, affected body area or impact when relevant, visible signs, immediate actions, activity or pickup outcome, parent contact attempts, successful notification time, director review, and follow-up owner. Add conditional fields for first aid, equipment, another child, behavior context, photos, acknowledgments, or corrective action instead of showing every question in every report.
Prompt staff to write in time order and use observable details: where the child was, what activity was underway, what the staff member saw or heard, what happened next, and how staff responded. Avoid labels such as careless, aggressive, or fine when the report can state a specific action or visible sign. Put a child's words and witness statements in separate fields marked as statements. If a cause is unknown, the form should allow staff to say that instead of requiring a guess.
Yes. Start with an incident-type question and use conditional sections. An injury path can ask about body area, visible signs, response, and activity outcome. A behavior path can ask what occurred before the event, observable behavior, staff response, and prevention planning. A near-miss path can skip injury questions and focus on the hazard, who could have been affected, how the area was secured, and the owner and due date for correction. Shared identity, timeline, notification, and review fields remain consistent.
Create separate internal and parent-facing sections. The internal record can identify participants and witnesses for director follow-up, while the family summary focuses on the named child's experience, observed sequence, response, and next steps without naming another child. Route internal fields only to designated staff and use a distinct parent copy or view. Review the form with your center's own privacy and record-handling policies before publishing it.
A center may use a signature or acknowledgment field to record that a parent or guardian received or reviewed the report. Label the field precisely, include the date, and offer space for a comment. An acknowledgment should not be described as agreement with every detail, a waiver, or proof of legal effect. If your organization has specific signature or notice requirements, use wording and a process approved for your setting rather than relying on generated copy.
Yes. Makeform supports unlimited free forms and responses, so a daycare can generate, edit, publish, and use its incident report without a response cap. The paid tier removes the Makeform badge. You can begin with one of the sample prompts, replace the generic classroom and incident options with your center's own terms, test the complete staff-to-parent workflow, and revise the form before sharing it with the team.
Submit fictional scenarios from the devices staff use: a playground injury, a behavior event, a failed parent contact attempt, and a near miss. Confirm conditional sections appear correctly, required fields do not block a report, internal details stay out of the family path, notifications reach the reviewer, and follow-up tasks have owners. Ask a staff member who did not build the form to retell the event from the submission; missing context will reveal questions to improve.
Give staff a clear path from event to follow-up.
