Describe your incident process. Makeform creates a staff form for student details, factual observations, immediate actions, witnesses, attachments, and follow-up routing.
Route incident submissions to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a scenario, adapt the prompt, or send it to the builder. Each example suggests a structure, not a completed report.
Audience
Teachers and support staff documenting classroom or campus behavior
Format
Conditional report with actions and referrals
Prompt size
277 chars
Example form structure
Conditional report with actions and referrals
Reporter, student, date, time, and location
What did you directly observe?
Incident category
Immediate actions taken
Who owns the follow-up?
Suggested routing tags
Administrator review
Health office follow-up
Family contact needed
Ask reporters to separate what they directly observed from what another person told them. That distinction makes later review clearer.
Step 1
Record
who, when, where, and what was observed
Step 2
Respond
immediate safety, care, and supervision steps
Step 3
Route
administrator, health office, counselor, or facilities
Step 4
Follow up
owner, notifications, actions, and closure notes
Clearer incident records
A school incident report form gives staff a consistent factual sequence, while conditional questions keep each report relevant.
Separate direct observations, received statements, witnesses, and attachments so reviewers can understand where each detail came from.
Show injury response fields for an injury and property photos for damage, without making staff work through unrelated sections.
Capture the follow-up owner, notification status, and target date so submission is the start of the workflow rather than its endpoint.
One intake, several routes
Start with shared fields, then reveal relevant questions and recipients.
Document observed conduct, statements, antecedents, interventions, student disposition, and administrator or counselor referral.
Record the activity, apparent affected area, immediate response, health office contact, and family notification details.
Capture the precise location, equipment affected, temporary controls, photos, and facilities assignment.
Keep witness details structured and record who contacted a parent or guardian, when, and by which method.
Build the reporting workflow
Describe required details, then refine the branches and routing for your school's process.
List reportable events, shared facts, and category-specific details.
Add locations, roles, notification choices, and urgent-action instructions.
Branch by category so each report asks relevant follow-up questions.
Send reports to the right team and record ownership, status, and closure.
Reporting approaches
Email and paper can capture a story, but a structured form prompts for the location, source, response, notifications, and follow-up details that are often missed.
Field guide
Use these six sections as a practical starting point, then align the labels, response choices, recipients, and retention process with your school's own procedures.
People and reporter
Identify the reporter, students named, and each person's relationship to the event. Student IDs can distinguish similar names.
Time and place
Use structured date, time, and location fields. Add the activity or class period when useful.
Factual account
Ask for observable actions in order. Separate direct observation from statements by others.
Immediate response
Record the student's disposition and remaining needs, including supervision, first aid, referrals, or area controls.
Notifications
Record who contacted whom, when, by which method, and whether another attempt is needed.
Follow-up and closure
Assign a reviewer, target date, and status. Use a closure note without rewriting the original report.
Related tools
Connect incident intake with focused behavior, bullying, statement, attendance, and family communication forms.
Create a focused behavior report with observed actions, interventions, and next steps.
Open toolOffer a dedicated path for reporting bullying concerns and sharing relevant details.
Open toolCollect a structured first-person statement connected to an event review.
Open toolGive students a clear intake route for concerns that need staff review.
Open toolTrack attendance events and the follow-up details that belong outside an incident report.
Open toolCollect family feedback through a separate, purpose-built survey workflow.
Open toolFAQ
Practical answers for administrators and staff building a consistent incident intake process.
Staff use it to document behavior, injuries, safety concerns, conflicts, or property issues. It records participants, time, location, observations, immediate actions, notifications, and follow-up.
Include the reporter, student, date, location, category, factual sequence, source of each account, witnesses, immediate response, notifications, attachments, follow-up owner, and target date.
Ask for observable events in order and exact words when relevant. Separate direct observation from others' statements. Avoid labels, motives, diagnoses, and unsupported conclusions.
Yes. Use shared fields, then reveal category-specific sections. Behavior can ask about conduct and interventions; injury can ask about activity, affected area, response, health office contact, and family notification.
No form should replace the school's immediate response process. Tell staff how to get urgent help, then use the form to document events and actions.
Yes. Route by category, site, or need: behavior to an administrator, injury to the designated health-office workflow, and hazards to facilities. Confirm recipients before publishing.
Yes. Makeform offers unlimited free forms and responses for generating, editing, publishing, and collecting reports. The paid tier removes the Makeform badge.
Require an owner, target date, notification status, and initial action. Use separate status and closure fields for updates, preserving the original report.
Give staff one clear reporting path.
