Describe your reporting process. Makeform creates a critical incident report form for people involved, a time-ordered account, immediate response, notifications, evidence, and follow-up actions.
Route incident submissions to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it into the Makeform builder. Each structure is an example, not a live AI result.
Audience
Employees and supervisors reporting a serious workplace event
Format
Incident intake with timeline and immediate response
Prompt size
314 chars
Example form structure
Incident intake with timeline and immediate response
Reporter, role, and contact details
When and where did the incident happen?
Describe the event in chronological order
Who was notified and when?
Evidence and follow-up actions
Suggested routing tags
Urgent review
Follow-up open
Closed
Separate observed facts from interpretation, and let reporters mark event times as exact or estimated.
Step 1
Report
facts, people, location, and evidence
Step 2
Reconstruct
ordered events with known or estimated times
Step 3
Route
notifications and review based on answers
Step 4
Follow up
actions, owners, dates, and status
A clearer incident record
Preserve observations while giving reviewers a consistent sequence, contact trail, evidence, and action list.
Capture discovery, response, escalation, and resolution separately, with an estimated-time option.
Capture safeguards, stabilization, area controls, and designated contacts before review.
Structure each task with an owner, target date, priority, and status.
Adapt the reporting path
Start with the closest workflow, then add your categories, severity choices, notifications, and owners.
People involved, witnesses, location, immediate response, supervisor notification, evidence, and corrective work.
Participant context, staff observations, designated contacts, escalation details, and program follow-up.
Site details, access or equipment context, area controls, notifications, media uploads, and shift handoff.
Detection, impact, mitigation, communications, recovery milestones, contributing factors, and action tracking.
Reporting workflow
Generate the core fields, apply your escalation procedure, and route submissions for review.
Define critical events, reporters, and the site or service details reviewers need.
Use your categories and reveal specialized questions only when relevant.
Notify reviewers, and keep urgent contact instructions visible outside the form.
Check completeness, label unconfirmed factors, assign work, and update status.
Choose the reporting method
A form requires recurring details and keeps every response in the same order.
Field guide
Use these six sections, then align labels and routing with your incident procedure.
Reporter and context
Collect enough context to contact the reporter and place the event. Offer anonymity only if your process supports it.
Event facts
Ask for observable details first. Structured fields aid sorting; a narrative preserves unexpected detail.
Chronology
Separate detection, developments, response, escalation, and resolution. Mark each time exact or estimated.
Response and notification
Show immediate safeguards and the contact chain. Reveal details for selected response types.
Evidence and impact
Upload photos, documents, or logs. Describe each attachment and label preliminary factors as unconfirmed.
Follow-up and closure
Give each action an owner, priority, date, and status. Retain reviewer notes and the closure decision.
Related tools
Add narrower intake, witness statements, hazard reports, observations, and closure.
Create a general incident intake for events that do not require the full critical workflow.
Open toolCollect a focused first-person account from a witness or person involved.
Open toolLet staff flag a hazardous condition before it develops into a serious event.
Open toolCapture employee-specific details and supervisor follow-up for workplace events.
Open toolDocument observed practices, site conditions, and recommended improvements.
Open toolRecord review outcomes, remaining work, and the decision to close a security incident.
Open toolFAQ
Practical answers for operations leaders and staff designing a consistent serious-event reporting process.
It documents a serious event for organizational review: reporter, people involved, location, timeline, response, notifications, impact, evidence, and follow-up. Define what counts as critical and which urgent channels staff must use.
Include reporter, site, category, internal severity, people and witnesses, times, factual narrative, actions, notifications, impact, attachments, and follow-up owners and dates. Separate observations from unconfirmed explanations.
Ask separately for discovery, start, developments, response, escalation, recovery, and end times. Add an exact-or-estimated choice so uncertainty remains visible.
Yes. Conditional logic can reveal sections by category or answer: access questions for facility events or recovery milestones for disruptions. Keep a common core for comparison.
Yes. Upload photos, logs, statements, or documents. Ask what each attachment shows and provide your own instructions for sensitive information, access, retention, and evidence handling.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect submissions without a response cap. The paid tier removes the Makeform badge.
Send notifications and connect responses to Slack, Google Sheets, or Zapier. Route by category, site, or severity when supported, and test every path first.
No. It is an intake tool, not an emergency channel. Display urgent contact instructions and use your established review, investigation, notification, and record-handling procedures.
Turn serious events into clear, actionable records.
