5W2H is a framework for turning a decision into executable action: what will be done, why, where, when, by whom, how, and with what resource demand. The method’s name combines five W questions and two H questions in English. The acronym is common in some management contexts, especially in Brazil, but it should not be assumed to be universally recognized. The seven fields must therefore be stated explicitly: What, Why, Where, When, Who, How, and How much.
In industrial maintenance, filling in those seven answers creates value only after the problem has been bounded, causes investigated, and treatment approved. The framework organizes execution. It does not discover the cause of a failure, prioritize risk by itself, or prove that recurrence was prevented.
For engineering, reliability, and maintenance planning teams, the critical point is closing the loop. A technical finding must leave the report, enter a 5W2H action plan with clear dependencies and criteria, become planned work where applicable, and return as evidence. Without that return, “review procedure,” “train team,” or “monitor equipment” remain intentions.
How 5W2H works in maintenance
A public Brazilian Ministry of Health reference on 5W2H describes it as a tool for recording, in an organized and planned way, how identified actions will be implemented. This is a Brazilian public management reference, not an international regulatory requirement. The acronym groups What, Why, Where, When, and Who, followed by How and How much.
The structure is simple, but every field must carry a technical decision:
| Field | Decision that must be explicit | Weak answer | Executable answer |
|---|---|---|---|
| What | Physical, documentary, or operational deliverable that changes the condition | Improve the plan | Revise the EV-204 fan task list to include soft-foot measurement, alignment, and an acceptance report |
| Why | Confirmed cause, controlled risk, or requirement addressed | Avoid problems | Prevent return to service without evidence that the identified misalignment was corrected |
| Where | Asset, location, document, population, or process step affected | At the plant | EV-204 fan, motor base, and equipment task list in SAP PM |
| When | Deadline, start milestone, dependency, and execution window | By Friday | After safety release and coupling availability, before the operational return test |
| Who | One accountable owner, plus required performers and approvers | Maintenance | Engineer accountable for EV-204, named in the plan, with mechanical execution and reliability acceptance |
| How | Sequence, technical standard, resources, controls, and acceptance criterion | Align the unit | Measure soft foot, correct the base, align to the approved procedure, and attach the report before release |
| How much | Hours, materials, services, downtime, and budget needed | Low cost | Planned hours by trade, reserved components, and final cost from confirmations and material issues |
How much does not require an unsupported monetary estimate. If a quotation is unavailable, record hours by trade, materials, external services, downtime duration, and the step that will turn these resources into a budget. The field must not remain empty until scheduling reveals that the approved action does not fit the window or budget.
5W2H, Five Whys, root cause analysis, and GUT answer different questions
A weak investigation produces a precise action plan for the wrong cause. Sequence matters:
- Describe the event and preserve evidence. Equipment, affected function, operating condition, timing, protections, parts, and records bound the investigation.
- Investigate causal relationships. The Five Whys helps construct and test a chain. A broader root cause analysis may require fishbone analysis, fault trees, barrier analysis, tests, and multiple hypotheses.
- Prioritize the problem queue. GUT compares severity, urgency, and trend using predefined criteria. A Brazilian Ministry of Transport reference presents GUT for ranking alternatives. This is a Brazilian management reference, not a universal requirement. A high score indicates where to start but proves neither cause nor technical action.
- Define treatment. Decide what must be contained, corrected, prevented, and verified.
- Structure execution. 5W2H turns each approved treatment into a deliverable, owner, deadline, method, and resource demand.
- Plan, execute, and verify. Route the action through appropriate governance, create a maintenance order when physical work is involved, and close only with implementation and effectiveness evidence.
The Centers for Medicare & Medicaid Services Five Whys material suggests validating a cause by asking whether removing it would probably have prevented the event. That question belongs to investigation. 5W2H comes later to state how the confirmed cause or contributing factor will be controlled.
| Method | Main question | Output | Misuse |
|---|---|---|---|
| Five Whys | Which relationships explain the event? | Evidence-supported causal chain | Stopping at the first convincing narrative |
| Root cause analysis | Which causes and factors contributed, and how were they confirmed? | Tested explanation, extent of condition, and required controls | Confusing correlation, finding, and cause |
| GUT matrix | Which problem receives attention first? | Priority queue under a stated rule | Treating a high score as causal proof |
| 5W2H | How will the approved decision be executed? | Plan with owner, deadline, method, resources, and location | Using the table instead of investigation |
| Maintenance order | How will authorized work be planned, executed, and recorded? | Operations, resources, dates, confirmations, and history | Closing the order and assuming the action was effective |
From finding to a 5W2H action plan
Before opening a spreadsheet, write the finding as a verifiable condition. “Maintenance failure” is too broad. “The EV-204 fan returned to service without an alignment report, and a later inspection found soft foot outside the internal procedure limit” identifies the object, control gap, and available evidence.
Separate four elements that often get combined in one row:
- condition found: observed fact and known extent;
- cause or contributing factor: relationship confirmed by investigation;
- risk or consequence: what may occur if the condition persists;
- expected result: control condition the action must create.
The expected result connects What to the verification criterion. If the issue was accepting a unit without measurement, “provide alignment training” does not ensure change. The deliverable may require a revised task list, mandatory field, attached report, and technical acceptance before release.
Containment, correction, prevention, and verification
Names vary across management systems. This article uses four operational categories and expects each organization to adapt them to its governance.
Containment
Containment limits the immediate effect, stabilizes the condition, or prevents progression while investigation and definitive treatment continue. Isolating equipment, transferring function to validated redundancy, or inspecting an exposed population may be containment. These actions must not be presented as cause elimination.
State the start trigger, operating limit, release authority, and end condition. “Monitor until resolved” defines none of them.
Correction
Correction restores the specific condition found: replacing a damaged component, correcting alignment, repairing the base, updating an approved parameter, or restoring a barrier. It addresses the immediate physical or documentary nonconformity but may not prevent the same mechanism from returning in the next job.
Prevention
Prevention changes the control that allowed the occurrence or extends treatment across the condition’s scope. It may require a task-list revision, design change, acceptance criterion, qualification, functional test, spare-parts control, or inspection of equivalent equipment. “Retrain the team” is inadequate if the process can still accept an order without objective evidence.
Some standards and companies call action on a cause to prevent recurrence a corrective action. The local label does not change the technical requirement. The plan must show which cause is treated and why the proposed control can reduce recurrence.
Verification
Verification has two levels. First, it proves implementation: the list was revised, the base repaired, measurement performed, and report created. Second, it assesses effectiveness: the control produced the expected result under comparable conditions, not only on closure day.
A U.S. Department of Energy corrective-action review guide asks whether actions are clear and executable, have performance measures, can be verified, include an effectiveness mechanism, assign responsibility, and have completion dates. These criteria prevent status-based closure without evidence.
Complete industrial case: recurring failure on EV-204 fan
This is a didactic case. People, dates, hours, equipment, and evidence were created only to demonstrate the method. They are not a client result, benchmark, regulatory limit, or universal recommendation.
Event: exhaust fan EV-204 was removed from service due to high vibration after a planned motor replacement. The coupling was damaged. The alignment report expected by the hypothetical engineering practice was not attached to the closed order.
Investigation evidence: inspection found soft foot above the hypothetical internal procedure limit, unidentified shims, no measurement report, and acceptance based only on motor replacement and a rotation test. The task list said “align unit” without tolerance, method, mandatory record, or acceptance hold point.
Cause treated: the process allowed release without proof of soft-foot correction or an alignment report. The investigation also required reviewing extent of condition across fans using the same task list. The plan does not assume that every coupling failure has the same cause.
In this example, D0 is plan approval. Every deadline states the dependency that authorizes the action to start.
| What | Why | Where | When | Who | How | How much |
|---|---|---|---|---|---|---|
| Containment: keep EV-204 unavailable and operate redundant equipment only after validating required capacity. | Prevent return of the damaged unit and avoid transferring function to redundancy whose condition is unconfirmed. | EV-204, redundant fan EV-204B, and area control room. | At D0, before any start attempt. Ends only after repair acceptance and operating authorization. | Ana Ribeiro, system engineer in this didactic case. Operations performs the transfer and records the condition. | Block EV-204 release, inspect redundancy under the current checklist, confirm capacity with Operations, and record shift acceptance. | Two Operations hours and one supervision hour, with no planned materials. Actual cost is charged to involved cost centers. |
| Correction: replace damaged coupling elements, correct soft foot, and align the unit. | Restore the affected physical condition and remove misalignment confirmed by investigation. | EV-204 base, motor, coupling, and fan. | By D+2, after safety release, kit reservation, and engineering scope approval. | Bruno Costa, mechanical supervisor in the case, accountable for delivery. Mechanical team executes and reliability accepts. | Inspect base and fasteners, measure and correct soft foot, replace damaged parts, align to the internal procedure, test, and attach measurement report. | Twelve mechanical hours, four alignment-specialist hours, coupling kit, and shims. Final amount comes from confirmations and material issues. |
| Prevention: revise the task list used for motor replacement and coupling work. | Prevent release under the vague instruction “align unit” and without measurable evidence. | EV-204 task list and the applicable technical-family template in SAP PM. | By D+5, after engineering approves method, limits, and report. New version applies before the next family order. | Carla Mendes, task-list planner in the case, with reliability-engineer approval. | Add soft-foot measurement, base preparation, alignment method, approved tolerances, mandatory report, and technical acceptance hold point. | Six engineering hours and four planning hours. No purchase expected. Record change to the improvement cost center. |
| Prevention by extent: review recent orders in the family and inspect units lacking an acceptance report. | Determine whether the control gap is limited to EV-204 or exists in other assets using the same instruction. | Fan population linked to the affected task list. | Selection by D+3. Inspections scheduled by D+15 according to criticality, access, and asset window. | Diego Lima, reliability engineer in the case. Planning schedules inspections and area owners release assets. | Extract the linked population, review attachments and confirmations, classify gaps, and create inspection orders only where evidence is insufficient. | Eight analysis hours and two inspection hours per selected asset. Total quantity and cost close after documented selection. |
| Implementation verification: audit the first use of the revised list and the EV-204 repair records. | Prove that method, measurement, report, and acceptance were incorporated, without confusing document editing with control execution. | EV-204 order, revised list, and first subsequent order in the family. | At EV-204 technical completion and on the next order. Depends on completed execution and available attachments. | Elisa Rocha, designated technical auditor in the case, independent from action execution. | Compare every operation with the approved list, check author, measurement, tolerance, report, acceptance, and deviation handling. Reopen the item if evidence is missing. | Three hours per verification, no material. Cost is recorded under maintenance assurance. |
| Effectiveness verification: assess condition and recurrence after return under comparable operating load. | Confirm that the control reduced the chance of the same mechanism returning and that the unit remains acceptable. | EV-204 and a sample of family orders executed with the revised list. | Measurement after stabilization, review at D+30, and final assessment at D+90. Timing depends on operating hours and comparable load, not calendar alone. | Diego Lima, reliability engineer in the case, using Operations and condition-inspection data. | Compare measurements with internal criteria, check recurrence, review order findings, and confirm deviations generated treatment. Close only with approved effectiveness report. | Four analysis hours per review plus route collection hours. No additional investment beyond scheduled resources. |
What makes this 5W2H verifiable
The table does not assign “Maintenance” as owner. Each row has one accountable person in the didactic case, while other teams perform, approve, or supply data. Deadlines are not isolated dates. Correction depends on safety, materials, and scope approval. Task-list revision depends on the technical definition. Effectiveness assessment depends on operating hours and comparable load.
How much records resources before pretending to know an exact monetary value. Final cost comes from confirmed hours, consumed materials, and contracted services. In a real application, planning would replace the didactic estimates with company cost data and record deviations.
Completion and effectiveness remain separate. The repaired order may be technically complete while effectiveness review stays open until the observation period is sufficient.
How to avoid four weaknesses in the plan
Vague action
Verbs such as improve, reinforce, monitor, raise awareness, and review hide the deliverable. Complete the verb with an object, final condition, and evidence. “Review the plan” becomes “revise task list LT-EV-204, add three mandatory measurements, approve the version, and attach the first execution record.”
Can someone outside the investigation execute it and another person verify it without asking what the author meant? If not, What or How is incomplete.
Generic owner
A department is not accountable. “Planning,” “Engineering,” and “Supplier” may be part of the flow, but someone must answer for delivery. Who should identify a person or individual role with suitable authority, separating accountable owner, performer, and approver where needed.
The plan must survive leave and role changes. Associate the name with a formal role and substitution rule, not only a private spreadsheet.
Deadline without dependencies
A date may be impossible before materials, shutdown, permit, design, or analysis. Record the start-enabling milestone, required window, and final deadline. If an external dependency slips, the owner updates impact and decision instead of simply moving the date.
Dependencies must connect to capacity, materials, permits, asset availability, and scheduling. An approved action that never enters an executable window remains open even if a cell is green.
Completion without evidence
“Completed” is not evidence. Define the expected record in 5W2H: report, permitted image, measurement, order number, task-list version, acceptance, test result, or post-implementation trend. The performer should not be the only person assessing effectiveness for a significant action.
Absence of a new failure is insufficient when the equipment has not faced comparable load, time, or conditions. Verification combines control implementation, observed performance, and an observation period coherent with the mechanism.
How to move 5W2H into orders, plans, and scheduling
Not every 5W2H row becomes a maintenance order. Procedure revision follows document control. Design change follows engineering and management of change. Budget decisions follow their governance. Physical work or inspection on an asset, however, must enter maintenance flow with object, scope, operation, resource, material, date, and record.
Official SAP documentation describes the maintenance order as supporting detailed task planning, including type, scope, dates, resources, execution monitoring, costs, and history. 5W2H can provide context and accountability, but the order must translate the action into executable operations.
- One-time asset action: creates an order with operation, resource, material, instruction, and confirmation criterion.
- Approved recurring action: requires engineering decisions about task list, strategy, plan, and interval in SAP PM before future orders.
- Extent inspection: starts with a defined population and creates orders only for approved scope.
- Effectiveness verification: may combine an inspection order, technical document, and history review without closing automatically with correction.
The maintenance work-order guide details fields and operational flow. The maintenance planning and control guide explains how capacity, priority, scheduling, and field feedback sustain the cycle.
PM Run’s role on top of SAP PM
PM Run does not execute 5W2H automatically, determine root cause, or approve technical treatment. Engineering, reliability, and governance remain responsible for method, evidence, strategy, and effectiveness criteria.
After the action is approved and structured in appropriate SAP PM objects, PM Run operates as a planning, execution, and mobility layer on top of SAP. PM Run Planning supports organization of orders, capacity, skills, scheduling, and follow-up. PM Run Mobility takes orders to the field and returns operation confirmations, technical notes, images, PDFs, and measurements where applicable, including offline workflows.
This layer helps preserve the relationship between action, order, and record. It does not turn vague action into sound engineering. If What, How, and acceptance criteria arrive incomplete, digitizing the flow only accelerates ambiguity.
Checklist for approving a 5W2H action plan
- Is the problem bounded by event, asset, function, condition, and evidence?
- Was the cause in Why confirmed or labeled as a pending hypothesis?
- Were containment, correction, prevention, and verification separated?
- Does every What describe an observable deliverable?
- Does Who identify one accountable person, with performer and approver where needed?
- Does When include dependencies, window, and deadline?
- Does How state method, standard, resources, sequence, and acceptance criterion?
- Does How much record hours, materials, services, downtime, and budget or the estimation method?
- Was physical action converted into an order, and recurring action routed through plan governance?
- Do implementation and effectiveness have separate evidence and dates?
Frequently asked questions
What is 5W2H?
It is an action-plan framework based on What, Why, Where, When, Who, How, and How much. Because the acronym is not universal, state all seven fields. In maintenance it organizes execution of a decision already investigated and approved.
Does 5W2H identify root cause?
No. Five Whys and other causal methods investigate the event. 5W2H turns approved causes and treatments into actions with ownership, deadlines, methods, and resources.
What is the difference between 5W2H and GUT?
GUT ranks problems by severity, urgency, and trend. 5W2H details how an action will be executed. Neither confirms cause on its own.
Must every 5W2H action become a maintenance order?
No. Asset work and inspections generally enter orders. Document revision, design change, budgeting, and governance decisions follow their own flows. The plan must identify the correct record for each deliverable.
How do I complete How much without inventing cost?
Record hours by trade, materials, external service, downtime duration, and value source. If a quote is missing, name its owner and deadline. Do not enter “low cost” or an amount without a calculation basis.
When can an action be closed?
When implementation is proven against the defined criterion. For recurrence-prevention actions, effectiveness may close later, after sufficient time, load, and evidence.
Technical references
- Brazilian Ministry of Health, 5W2H, a Brazilian public reference for the seven questions and action implementation.
- Centers for Medicare & Medicaid Services, Five Whys for RCA Tool.
- Brazilian Ministry of Transport, GUT Matrix, a Brazilian public management reference on ranking by severity, urgency, and trend.
- U.S. Department of Energy, corrective-action review criteria.
- SAP Help Portal, Maintenance Order.
A useful 5W2H action plan ends in executed work and reviewable evidence. To organize approved actions into capacity, scheduling, work orders, and field records without replacing SAP PM, learn about PM Run’s planning and mobility layer integrated with SAP.
