Describe the incident, investigation method, and review workflow you use. Makeform turns that brief into a structured root cause analysis form for evidence, contributing conditions, causal reasoning, corrective actions, owners, due dates, and effectiveness checks.
Route investigation submissions to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a complete investigation brief, adapt it to your process, or send it to the Makeform builder. The fields shown are a proposed structure, not a completed investigation.
Prompt ready4 formats
Audience
Quality managers investigating process or product deviations
Format
Evidence-led analysis with 5 Whys and action plan
Prompt size
581 chars
Brief qualitySends to builder
Example form structure
Evidence-led analysis with 5 Whys and action plan
Prompt exampleEditable in builder
Case, process, detection, and containment
Short answerFirst ask
2
Expected result versus observed result
Long answer
3
Evidence, records, and attachments
File upload
4
Why did this happen?
Long answer
5
Action owner, due date, and verification plan
Date & time
Suggested routing tags
Suggested
Investigation open
Actions assigned
Effectiveness review
Separate immediate causes from system conditions. A broken guard may explain contact with a hazard, while inspection frequency, change control, or unclear ownership may explain why the guard stayed broken.
Step 1
Define
state the gap, scope, impact, and containment
Step 2
Investigate
build the timeline and gather reliable evidence
Step 3
Analyze
test causes instead of stopping at symptoms
Step 4
Correct
assign actions and verify the result later
A stronger investigation record
Move from incident description to supported cause.
An incident report records what happened. Root cause analysis connects the event to evidence, system conditions, and owned actions that can be checked after implementation.
A timeline before conclusions
Collect events, task steps, changes, records, and observations in sequence. Investigators can see what is known, what is missing, and where assumptions entered the story.
Evidence beside every cause
Ask what supports each proposed cause, what contradicts it, and which test or record would distinguish it from another explanation. That makes review more useful than a single free-text cause box.
Actions with closure criteria
Capture an owner, due date, priority, deliverable, completion evidence, and effectiveness measure for each action. The investigation stays open until the team can review the result.
Choose an analysis path
Use the method that fits the event and evidence.
The form can guide a lightweight review or a deeper cross-functional investigation. Keep the prompts specific enough that reviewers can follow how the team reached its conclusions.
5 Whys
Use linked why questions for a focused problem, while allowing branches when more than one condition had to be present. Require evidence at the end of each causal chain.
Fishbone categories
Prompt for people, methods, machines, materials, measurements, and environment so the team looks beyond the most visible mistake or failed component.
Barrier analysis
List the controls intended to prevent or reduce the event, then document whether each control was absent, bypassed, unsuitable, unavailable, or ineffective.
Change analysis
Compare normal work with the event conditions: staffing, inputs, settings, schedules, software, suppliers, procedures, and environment. Recent differences often guide the next evidence check.
Investigation workflow
Build a form your review team can actually follow.
Start with the decision the investigation must support, then organize facts, analysis, actions, and review gates in a consistent sequence.
Tell Makeform what your team investigates, who completes each part, which analysis method you use, and what reviewers need before approving causes or actions.
02
Edit the evidence path
Add your categories, rating scales, asset lists, action types, and required attachments. Use conditional questions so an injury, product deviation, or equipment failure opens the relevant detail fields.
03
Route the investigation
Send new cases and action assignments to the appropriate reviewer. Keep notification wording clear about whether the submission is an initial record, a proposed cause, or an approved action plan.
04
Review closure and effectiveness
Record completion evidence, reviewer comments, the effectiveness measure, review date, result, and any follow-up action. Reopening remains possible when evidence shows the problem persists.
Three different records
Incident report, root cause analysis, or action tracker?
These records support different moments. Connecting them is useful, but asking one short report to do every job usually produces thin evidence and vague follow-up.
Record
Primary question
Useful contents
RecordIncident report
Primary questionWhat happened, where, when, and who was involved?
Useful contentsInitial facts, immediate response, impact, witnesses, and attachments.
Record
Root cause analysis form
Primary questionWhy could the event happen, and what evidence supports that conclusion?
Primary questionWho will change what, by when, and how will the result be checked?
Useful contentsOwners, priorities, due dates, status, completion evidence, measures, and effectiveness reviews.
Field guide
What a root cause analysis form should include.
A useful form preserves the path from the original problem to the later effectiveness decision. These six sections give investigators enough structure without deciding the answer for them.
Scope and problem statement
Define the gap without embedding a cause.
Capture what should have happened, what actually happened, where and when it occurred, how it was detected, the known extent, and the consequence or potential consequence. Keep suspected causes in a separate section so the opening statement does not steer the investigation prematurely.
Case ID, category, location, process, asset, product, and relevant dates.
Expected condition compared with the observed condition.
Known scope, impact, initial risk, and immediate containment.
Timeline and context
Reconstruct the work around the event.
A sequence helps separate conditions that existed beforehand from responses that happened afterward. Record task steps, handoffs, decisions, alarms, changes, and discovery points with timestamps or relative order, and mark entries that still need confirmation.
Events before, during, and after the failure or near miss.
Normal process compared with actual work performed.
Recent changes in staffing, materials, settings, schedules, or instructions.
Evidence register
Show where each important fact came from.
List interviews, photographs, logs, work orders, training records, procedures, samples, measurements, and retained parts. Record who gathered each item, the date, its relevance, and any limitation. This makes gaps visible and gives reviewers a way to challenge conclusions constructively.
Source, collector, collection date, attachment, and short finding.
Fact, inference, and unverified statement clearly distinguished.
Missing or conflicting evidence that requires another check.
Causal analysis
Explore conditions, branches, and alternatives.
Use 5 Whys, fishbone categories, barrier analysis, change analysis, or a method your organization already follows. Allow several causal paths when the event required a combination of conditions. Ask what evidence supports and weakens every proposed cause.
Immediate causes, contributing factors, and deeper system conditions.
Controls expected, their actual state, and why gaps were possible.
Alternative explanations considered and tests used to compare them.
Corrective action plan
Turn conclusions into owned, reviewable work.
Connect each action to a supported cause or control gap. Describe the intended change precisely, identify the accountable owner and contributors, set a priority and due date, and define what evidence will demonstrate completion. Separate immediate repair from recurrence prevention when both are needed.
Action type, linked cause, deliverable, owner, approver, and due date.
Dependencies, resources, interim controls, and status updates.
Completion evidence such as a revised workflow, test, photo, or record.
Effectiveness and closure
Decide how the team will know the change worked.
Define the measure, data source, review period, reviewer, and acceptable result before closing the action. At follow-up, capture the observed result and whether the control is used as intended. The reviewer can close, extend, revise, or reopen the action based on that evidence.
Leading check for implementation and later outcome measure.
Review date, sample or observation period, and reviewer decision.
Residual concerns, lessons shared, and additional actions if needed.
Related tools
Connect reporting, observation, audit, and follow-up.
Use separate forms for fast event intake, routine checks, and investigation records, then align their identifiers and ownership fields so teams can trace related work.
Practical answers for quality, safety, maintenance, and operations managers designing an investigation workflow.
What is a root cause analysis form?
A root cause analysis form is a structured investigation record used to define a problem, assemble a timeline and evidence, analyze contributing conditions, document supported causes, and assign corrective actions. It also records how completion and effectiveness will be reviewed. The form guides consistent thinking; the investigation team still evaluates the facts and decides which conclusions the evidence supports.
What is the difference between an incident report and a root cause analysis form?
An incident report is usually the first account of what happened: time, place, people, immediate effects, response, and available attachments. Root cause analysis comes later and asks why the event was possible, which controls failed, what evidence supports each causal path, and what changes should follow. Link the records with a shared case ID, but avoid forcing the initial reporter to reach a cause before the evidence is collected.
Which fields should every root cause analysis form include?
Include a case ID, investigator and reviewers, problem statement, expected and actual condition, scope, impact, containment, timeline, evidence register, people and records consulted, analysis method, contributing factors, proposed root causes, evidence for and against each conclusion, corrective actions, owners, priorities, due dates, approvals, completion evidence, effectiveness measures, review dates, and closure decisions. Add specialized fields only when the selected incident type requires them.
Can I use both 5 Whys and a fishbone analysis?
Yes. A fishbone section can broaden the search across people, process, equipment, material, measurement, and environment. A 5 Whys chain can then examine promising causal paths in more depth. Neither method should force the team into one linear answer. Let investigators add branches, alternative explanations, and evidence so several necessary conditions can be represented when the event is complex.
How should corrective actions be connected to root causes?
Give every action a linked cause, contributing factor, or control gap. Capture the exact change, owner, target date, priority, dependencies, interim controls, approver, and completion evidence. Then define an effectiveness measure and review date. This connection helps reviewers spot actions that merely repair the visible damage without addressing the condition that allowed recurrence.
Can one form support quality incidents, safety events, and equipment failures?
Yes, if the shared opening fields lead to conditional sections. All three may need scope, containment, timeline, evidence, causal analysis, actions, and follow-up. A quality deviation can open product, lot, and specification questions; a safety event can open injury, task, hazard, and barrier questions; an equipment failure can open asset, alarm, component, reading, and maintenance-history questions. Review the resulting branches with each process owner.
How do I keep investigators from choosing a cause too early?
Separate facts from interpretations, require a neutral problem statement, and collect the timeline and evidence before displaying the final cause fields. Add prompts for alternative explanations, contradictory evidence, missing information, and tests still needed. Require reviewers to see the evidence linked to a cause. The form can create these pauses, while the team decides how much investigation is proportionate to the event.
Is the root cause analysis form generator free?
Yes. Makeform is unlimited free, so you can generate, edit, publish, and collect responses for ongoing investigations. The paid tier removes the Makeform badge. You can refine field wording, required questions, conditional sections, and action-routing details before sharing the form with investigators.
Make the reasoning visible.
Generate a root cause analysis form that connects evidence to action.
Unlimited free forms and responsesEvidence-led analysisOwned follow-up actions
