27/07/2026
SEE CAPA Series
Article 1, Solver in Action
CAPA — The Discipline That Separates Engineers Who Solve from Engineers Who Patch.
There is a moment that every engineer knows. A system fails. A complaint arrives. A test result falls outside its expected range. The instinct — and in many organisations the standing instruction — is to fix it and move on. Replace the component. Adjust the setpoint. Clear the blockage. Close the ticket.
That instinct is not wrong. It is necessary. A failed system must be restored to service. A complaint must be answered. A test must be repeated. But the act of restoring a system to service is not the same as solving the problem that caused it to fail. It is the beginning of the response, not the end of it. And in the gap between those two things — between the correction and the solution — lies the entire discipline of Corrective and Preventive Action, known in quality management practice by its universal acronym: CAPA.
This article is the first in a series published by Shalabi Engineering Establishment (SEE) as part of a forthcoming comprehensive book on CAPA in engineering practice. The series is written for engineers, facility managers, contractors, and consultants who work with built environment systems — HVAC, plumbing, drainage, fire protection, and medical gas — and who want to move beyond reactive maintenance and into the practice of genuine system improvement. Each article stands alone. Together they form a complete framework.
The Problem With Patches
A patch is a response to a symptom. A solution is a response to a cause. The difference sounds simple. In practice it is one of the hardest disciplines in engineering to maintain consistently, because patches are fast, visible, and immediately satisfying, while solutions require investigation, patience, and a willingness to keep asking questions past the point where a plausible answer has already appeared.
Consider a building where the supply air temperature in a specific zone repeatedly drifts above its design setpoint during afternoon hours. The building management system logs the alarm. The maintenance team responds. They check the damper actuator, find it operating correctly, reset the controller, and the temperature returns to setpoint. The ticket is closed. Three weeks later the same alarm appears. The same response follows. The same resolution. The cycle repeats through the summer.
What is happening in that building is not a maintenance problem. It is a CAPA problem. The maintenance team is correcting — restoring the system to setpoint — but no one is performing corrective action, which means no one is investigating why the drift occurs at that time of day in that specific zone and not in others. The root cause may be solar gain through unshaded glazing that was not accounted for in the original load calculation. It may be a duct leakage condition between the air handling unit and the terminal units serving that zone. It may be a control sequence that allows the cooling coil valve to hunt under partial load conditions specific to afternoon occupancy patterns. It may be something else entirely. Without a structured investigation, the cause remains unknown, and the patch remains the only response available.
That organisation is paying for the same problem repeatedly. It is paying in maintenance labour, in energy consumed by a system working harder than it should, in occupant dissatisfaction, and in the accumulated credibility loss that comes from a facility that is never quite right. The cost of one thorough CAPA investigation — identifying and eliminating the root cause — would almost certainly be less than the cumulative cost of the repeated corrections. And once the root cause is eliminated, the cost stops.
What CAPA Actually Is
CAPA stands for Corrective and Preventive Action. It is a structured process, embedded in every major quality management standard in the world, for moving from the identification of a problem to the permanent elimination of its cause.
The corrective side of CAPA addresses problems that have already occurred. It asks:
why did this happen, what is the root cause of the failure, and what must change so that it cannot happen again in this system?
The preventive side asks a different and more demanding question:
where else in our systems does the potential for this type of failure exist, even though it has not yet expressed itself? Preventive action does not wait for a failure to occur. It identifies vulnerability and eliminates it before the failure happens.
Together, corrective and preventive action form a closed loop. The corrective action draws on what was learned from an actual failure. The preventive action applies that learning across the wider system. An organisation that operates this loop consistently does not merely maintain its systems — it improves them. Over time, whole categories of failure become less frequent, then rare, then absent.
This is not a theoretical aspiration. It is the documented outcome of CAPA programmes operated correctly in industries that have been applying quality management principles for decades. The pharmaceutical and medical device sectors — where regulatory frameworks mandate CAPA with particular rigour because the consequences of failure are measured in patient outcomes — have produced extensive evidence that organisations with mature CAPA systems carry significantly lower rates of repeat failures, regulatory observations, and product recalls than organisations without them. The engineering logic is identical in the built environment. The systems are different. The principle is the same.
The Three Things CAPA Is Not.
Understanding CAPA clearly requires distinguishing it from three things it is commonly confused with.
- CAPA is not the same as a correction. A correction is the immediate action taken to address the impact of a nonconformity — clearing the blocked drain, resetting the controller, replacing the failed component. A correction is necessary and often urgent. It is also, by itself, insufficient. A correction without corrective action leaves the root cause in place.
- CAPA is not a paperwork exercise. In organisations that implement CAPA as a documentation requirement rather than an investigative discipline, the forms are completed, the boxes are ticked, and the root cause field contains whatever explanation was most readily available at the time the form was filled in. The result is a record that satisfies an auditor who does not look closely, and a system that continues to fail for reasons that were never genuinely investigated. CAPA done this way is worse than no CAPA, because it creates the illusion of a quality system without providing its substance.
- CAPA is not only for large organisations or regulated industries. The logic of identifying root causes and eliminating them applies to any engineering practice of any size. A two-person consultancy that investigates why a design error reached the client without being caught, identifies the gap in its review process, and changes that process, is practicing CAPA. It may not call it that. The label is less important than the discipline.
Where CAPA Comes From.
The formal CAPA framework emerged from the quality management movement that transformed manufacturing industries in the second half of the twentieth century. The work of Walter Shewhart and W. Edwards Deming established the foundational principle that quality is achieved through the systematic analysis and improvement of organisations and processes, not through inspection of outputs. Joseph Juran's contribution to root cause analysis methodology gave practitioners the investigative tools to act on that principle. The automotive, aerospace, and semiconductor industries adopted and refined these tools across decades of application.
Regulatory frameworks crystallised the requirement. ISO 9001 — the foundational quality management standard applied across commercial and industrial organisations worldwide — includes corrective and preventive action in its core requirements. ISO 13485, which governs quality management for medical devices and clinical systems including medical gas, imposes CAPA with specific procedural rigour. The FDA's regulations for medical device manufacturers under 21 CFR Part 820 and for pharmaceutical manufacturers under 21 CFR Part 211 make CAPA a legal obligation with significant enforcement consequences for organisations that fail to implement it correctly. The WHO's Good Manufacturing Practice guidelines carry the same logic into the global pharmaceutical supply chain.
What all of these frameworks share is a recognition that quality cannot be inspected into a product or a system after the fact. It must be built into the processes that produce the product or operate the system. And when those processes produce a failure, the response must go deeper than the failure itself — all the way to the conditions that made the failure possible.
Why This Matters in MEP Engineering.
The mechanical and electrical engineering disciplines that serve the built environment have developed their technical knowledge to an extraordinary level of sophistication over the past center, which includes:
- The thermodynamic principles that govern HVAC system design,
- The hydraulic principles that govern plumbing and drainage,
- The combustion and suppression chemistry that governs fire protection,
- The purity and pressure requirements that govern medical gas .
These are well understood, well documented, and supported by a mature body of standards, codes, and guidance.
What these disciplines have not developed to the same level is the quality management infrastructure that manufacturing industries built in parallel with their technical knowledge.
The result is an industry where technical capability and quality system maturity are significantly misaligned.
An MEP engineer may be capable of designing a complex central plant serving a major hospital and simultaneously operating without any formal process for investigating why the same category of problem keeps appearing in their designs or their installations.
This misalignment has consequences. Repeated failures that were never investigated at the root cause level accumulate as warranty claims, client disputes, regulatory findings, and reputational damage.
Knowledge that could have been captured from one investigation and applied to prevent the next failure is lost because no systematic mechanism exists to capture and apply it.
The industry as a whole carries a burden of avoidable rework that a mature CAPA culture would substantially reduce.
The pressure to close this gap is growing. Healthcare facility operators, pharmaceutical manufacturers, and data centre operators — three of the most demanding client sectors in the built environment — are imposing quality management requirements on their MEP contractors and consultants that were unheard of a decade ago.
An MEP engineering firm that cannot demonstrate a structured approach to nonconformance investigation and corrective action is increasingly finding itself excluded from the sectors where the most technically demanding and professionally rewarding work is concentrated.
The argument for CAPA in MEP engineering is therefore both principled and practical.
It is principled because every competent engineer has an obligation to understand why their systems fail and to do something about it.
It is practical because the market is beginning to require it, and the firms that build this capability now will be better positioned than those that wait until the requirement is imposed from outside.
What This Series Will Cover.
This is the first article in a series that will move through the CAPA framework systematically, applying each element to the specific context of MEP engineering and built environment systems. The series follows the structure of the forthcoming SEE book on CAPA in engineering practice.
The next article will examine the eight-step CAPA workflow in detail — from the moment a triggering event is identified through to the formal verification of effectiveness and the closure of the investigation. Each step will be examined in the context of real engineering system failures, showing not just what the step requires but why it requires it and what happens when it is skipped.
Subsequent articles will address root cause analysis methodology in depth, the specific CAPA triggers and investigation patterns that apply to HVAC systems, plumbing and drainage systems, fire protection systems, and medical gas systems respectively, the environmental dimensions of CAPA in engineering practice, and the organisational and cultural conditions that determine whether a CAPA programme produces genuine improvement or merely generates documentation.
Throughout the series, the writing will follow what SEE calls the solver format. Every principle will be presented in the context of a problem. The reasoning from the problem to the solution will be shown explicitly. The reader will follow a line of engineering thought, not read a list of definitions.
CAPA is not a quality management requirement imposed on engineers from outside. It is the formalisation of what a good engineer does anyway — ask why, keep asking, and change something that matters. The framework gives that instinct structure, memory, and institutional permanence.
Shalabi Engineering Establishment (SEE)
Solver in Action, SEE site link:
https://sites.google.com/view/shalabi-see/home
| Amman, Jordan | Remote Worldwide
SEE CAPA Series | Article 1 of the forthcoming book:
Corrective and Preventive Action in Engineering Practice
