Describe the event and decisions to record. Makeform creates an incident review form connecting evidence, causes, corrective actions, owners, due dates, and effectiveness checks.
Route review records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it to your process, or send it to the builder. The structure is an example, not a completed investigation.
Audience
Safety leads and supervisors reviewing an injury or near miss
Format
Structured review with evidence, cause analysis, and action register
Prompt size
363 chars
Example form structure
Structured review with evidence, cause analysis, and action register
Incident ID, date, location, and review team
What happened, in chronological order?
Evidence reviewed
Immediate, contributing, and root causes
Corrective action, owner, and due date
Suggested routing tags
Review pending
Actions assigned
Effectiveness check
Separate immediate causes from system factors, then assign every action an owner, due date, and verification method.
Step 1
Reconstruct
timeline, impact, response, and evidence
Step 2
Analyze
causes, conditions, and control gaps
Step 3
Assign
actions, owners, priorities, and dates
Step 4
Verify
implementation evidence and effectiveness
Why structure the review
Preserve evidence, distinguish it from assumptions, and carry decisions through verified completion.
Sequence timestamps, observations, records, and attachments so reviewers can test causal claims against evidence.
Prompt for equipment, environment, training, procedures, workload, supervision, and control design.
Require an owner, due date, priority, completion evidence, and effectiveness test for each action.
Adapt the workflow
Keep facts, causes, actions, and verification while tailoring evidence and routing.
Document impact, work conditions, barriers, and stronger controls without assigning blame.
Track detection, escalation, mitigation, recovery, handoffs, and resilience work.
Connect affected scope, containment, measurements, failed controls, and prevention work.
Connect asset history, operating conditions, work orders, repairs, and maintenance changes.
Review workflow
Generate the structure, tailor questions, gather findings, and track corrective actions through follow-up.
Name the event type, reviewers, severity scheme, causal method, evidence sources, and closure authority.
Show injury fields for safety events, asset fields for equipment events, and deeper sections above a severity threshold.
Use required fields and uploads to build a timeline, label unknowns, and support conclusions with evidence.
Route actions to owners, track dates and status, attach evidence, and schedule effectiveness checks.
Review record options
A structured form keeps required evidence and follow-up responsibilities visible after the meeting.
Field guide
Use six sections to connect facts, analysis, decisions, and verification.
Review context
Anchor the review to an incident record. State the scope, participants, and boundaries behind its conclusions.
Timeline & impact
Reconstruct conditions through recovery. Separate facts from estimates and record effects on people, operations, customers, assets, or output.
Evidence
List or upload records, photos, statements, logs, measurements, and procedures. Keep evidence gaps visible.
Causal analysis
Separate immediate causes, contributing conditions, and root causes. Explain failed safeguards with evidence.
Corrective actions
Create one row per action with its linked cause, owner, due date, and implementation evidence.
Verification & learning
Define an effectiveness measure and review date, record residual risk, then capture lessons and closure decisions.
Related tools
Build the upstream incident record and the follow-up safety or audit forms around the same review workflow.
Capture the initial event facts, people, impact, response, and attachments before the review begins.
Open toolGuide a deeper causal analysis when a review needs structured why, factor, and evidence fields.
Open toolCollect first-hand accounts in a consistent format while memories and details are current.
Open toolLet teams report hazardous conditions that emerge from reviews or routine work before another event.
Open toolTurn control changes into repeatable inspection checks and collect evidence from the work area.
Open toolDocument broader process findings and follow-up items across an operational audit.
Open toolFAQ
Practical answers for safety, operations, quality, and facility teams organizing post-incident learning.
An incident review form records what happened, its impact, evidence, response, causes, lessons, and corrective actions. It gives each action an owner, date, and follow-up check.
An incident report captures initial facts and response. A later review assembles evidence, analyzes causes and failed controls, and defines changes to reduce recurrence.
Include the incident ID, scope, reviewers, timeline, impact, evidence, response, causes, control gaps, lessons, and actions. Give each action an owner, priority, due date, status, evidence, and effectiveness check.
Yes. Use a repeating group with one row per action. Link each row to a cause or control gap and collect its owner, priority, due date, status, evidence, and verification plan.
Ask about task design, equipment, environment, procedures, training, workload, communication, supervision, change management, and safeguards. Require evidence and examine why the system allowed individual actions to produce the outcome.
Yes. Keep shared context, timeline, evidence, analysis, action, and verification sections. Use conditional logic for safety, outage, quality, or facility-specific fields.
Define the expected change, baseline, evidence source, reviewer, and check date. Record the result and residual risk, then add follow-up when the action is ineffective.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses with your incident review form. The paid tier removes the Makeform badge; it does not unlock additional response capacity.
Turn the next review into owned follow-up.
