Reporter
Identify who submits the account.
Capture the reporter's contact, role, ministry, and whether the account is firsthand.
- Name, role, phone, and email.
- Relationship to the church or event.
- Firsthand or secondhand account.
Describe your property, ministries, and review process. Makeform creates a church incident report form for what happened, where, who was involved, witnesses, actions, photos, and follow-up.
Route incident reports to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a scenario, adjust it, or send the prompt to the Makeform builder.
Audience
Staff documenting a slip, fall, or other accident
Format
Fact-first report with photos and witnesses
Prompt size
248 chars
Example form structure
Fact-first report with photos and witnesses
Reporter name and role
Date, time, building, and exact location
What happened?
Witnesses and contact details
Photos of the area
Suggested routing tags
Needs review
Facilities follow-up
Closed
Ask separately for observed facts and follow-up actions to preserve the initial account.
Step 1
Observe
capture facts, location, time, and people
Step 2
Respond
record assistance, notifications, and safeguards
Step 3
Review
route the report to the responsible leader
Step 4
Follow up
assign actions and document closure
Clear reporting
Capture consistent facts after an accident, property issue, or event incident.
Separate time, location, people, witnesses, and event-sequence fields simplify review.
Conditional sections can show guardian notification, vehicle, property damage, or injury-observation questions only when they apply.
Capture immediate actions, assign the next review, and add a status so an unresolved repair or conversation does not disappear in an inbox.
Built around church activities
Tailor locations, ministries, notifications, and routing in the builder.
Document lobby falls, parking-lot events, damaged fixtures, blocked walkways, and other incidents tied to a specific campus area.
Record supervising adults, guardian contact, the activity underway, observed facts, and when notification occurred.
Capture venue, trip leader, transportation, witnesses, and on-site responses from a phone while details are fresh.
Give ushers, group leaders, and volunteers a shared reporting route with clear escalation and follow-up fields.
Incident workflow
Build a quick report with enough structure for administrative review.
List campuses, rooms, ministries, events, and the kinds of incidents your administrators need to document.
Add your contact options, make core facts required, and use conditional sections for minors, property, vehicles, or attachments.
Give staff and designated volunteers a mobile-friendly link and send new submissions to the people responsible for review.
Use status and owner fields to record facilities work, ministry follow-up, requested information, and closure notes.
Form vs email vs paper
Administrators need consistent fields, supporting files, and a visible next step.
Field guide
Gather an objective account, response details, and context for next steps.
Reporter
Capture the reporter's contact, role, ministry, and whether the account is firsthand.
Time & place
Use structured dates plus a campus, room, parking area, or event venue.
People
Separate involved-person and witness details. For minors, collect guardian notification conditionally.
Account
Ask what happened before, during, and after without requiring blame or diagnosis.
Response
Record assistance, hazard controls, and contacts made. The form does not replace emergency procedures.
Evidence & follow-up
Collect appropriate files, owner, status, due date, and closure notes. Restrict access for sensitive reports.
Related tools
Connect incident intake with general reports, emergency contacts, inspections, facility requests, and volunteer records.
Create a focused report for accidents, people involved, witnesses, and immediate actions.
Open toolBuild a general-purpose incident record for teams that need one shared reporting structure.
Open toolCollect current contacts for participants, volunteers, or ministry members.
Open toolCreate repeatable walkthroughs for rooms, grounds, equipment, and event setups.
Open toolRoute repairs and site needs discovered during incident review to the right team.
Open toolOrganize volunteer contact, availability, role, and onboarding information.
Open toolFAQ
Practical answers for church administrators, ministry leaders, and facilities teams setting up consistent incident intake.
It documents an accident, property issue, conduct concern, or other incident on church property or during an activity. It records essential facts, actions, files, and follow-up.
Include reporter, times, location, activity, involved people, witnesses, chronological description, observed impact, assistance, notifications, attachments, follow-up owner, and status.
Yes. Use common fact questions, then conditional sections for facilities, vehicles, minors, venues, or equipment.
Collect the program, supervising adults, objective sequence of events, and guardian contact and notification details. Limit access to the people responsible for review, and adapt the form and response process to your church's safeguarding procedures and local requirements.
Yes. Add uploads for relevant location or damage photos and documents. Explain what is appropriate and avoid unnecessary sensitive material.
Add review status, owner, target date, action notes, and closure date. Route submissions to a designated administrator.
Yes. Makeform is unlimited free for creating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge.
No. The form documents an incident and supports administrative follow-up. It does not replace urgent assistance, emergency notifications, safeguarding procedures, insurer instructions, or advice from qualified professionals when those are needed.
Give every incident a clear reporting path.