Quality on a capital project is largely decided before the first weld is inspected. By the time fabrication starts, the standards, the acceptance criteria, and the inspection sequence have either been defined clearly or they have not. Project quality management is the discipline that decides which of those two situations a project ends up in, and on EPCM programs with dozens of contractors and vendor shops, it is the difference between a clean handover and a long argument about what conforming work means.
What Project Quality Management Actually Covers
Project quality management is a process that considers how a project should proceed to achieve the desired quality for the project's deliverables. In practical terms it defines quality standards for those deliverables and then builds quality assurance and quality control around the work. Applied to a capital project, it means carrying the project through its four phases, concept, development, execution, and finish, with zero deviations from the project specifications.
The purpose is straightforward: project quality management makes sure project results hit the quality targets and criteria needed. What separates strong programs from weak ones is timing. Managing quality in projects is not only about fixing defects after they appear. Done properly, it is proactive work focused on preventing issues before they happen, using a complete set of methods, tools, and techniques across the project lifecycle to reach the desired quality goals.
Planning, Assurance, and Control: Three Functions That Must Work Together
The three functions below are not sequential stages that finish and stop. They run in parallel for the life of the project, and each one depends on the others being done honestly.
Quality Planning Sets the Acceptance Criteria
Quality planning is where acceptance criteria get defined. Before work starts, the project agrees what conforming output looks like, what will be inspected, what will be tested, and what evidence will demonstrate that the result is acceptable. Those criteria become the reference point for every later decision. When they are vague, or written after fabrication has already begun, the project loses its ability to measure quality objectively and disputes get settled by opinion rather than by specification.
Quality Assurance Builds Quality Into the Method
Quality assurance looks at the process rather than the product. It asks whether the approved methods, procedures, and controls are capable of delivering conforming work consistently. On a program with many contractors, assurance work includes confirming that each party is building to the approved method, that procedures match the governing specification, and that the documented system is genuinely being followed in the field instead of existing only as a manual on a shelf.
Quality Control Verifies the Output
Quality control consists of inspection, measurement, and testing to verify that project outputs meet the acceptance criteria defined during quality planning. It is the verification step, the physical evidence that the work conforms. Systematic processes such as inspection, testing, and corrective actions maintain consistency and reliability across the project. Control without planning leaves inspectors with nothing to measure against. Planning without control produces documentation with no proof behind it.
Why Capital Projects and EPCM Programs Need a Different Approach
Project quality management guides a project toward the desired deliverable quality, with managers measuring quality on an ongoing basis rather than at the end. On a single-contractor job that is already demanding. On an EPCM program it becomes a coordination problem, because engineering, procurement, and construction each generate their own quality questions, and each is often delivered by a different organization with its own forms, definitions, and record systems.
Interface Risk Across Contractors and Vendors
Every interface between parties is a place where a quality requirement can be dropped, duplicated, or quietly translated into a different standard. A vendor shop, a fabrication yard, and a site construction crew may each assume another party holds responsibility for a particular inspection. A program level quality management system closes those gaps by assigning accountability explicitly and by requiring consistent, comparable records from every source feeding the project.
Modular and Skid Fabrication Moves Work Off Site
When work shifts into modular and skid fabrication, verification has to travel with the module. Inspections that would be routine on site become schedule critical in a yard, because once a module ships, access changes and correction costs rise sharply. Programs that define inspection and testing requirements before fabrication begins avoid the familiar problem of a module arriving at site with incomplete quality documentation and no practical way to close it out.
What a Project Quality Management System Should Contain
A useful PQMS for a capital project or EPCM program is more than a procedures manual. It has to tell people what to do on a Tuesday afternoon when a weld fails visual inspection and the schedule is already tight. The components below are the practical minimum.
- Governance and accountability: who owns quality at program level, who owns it inside each contract, and how escalations are handled.
- Quality planning outputs: the standards, acceptance criteria, and inspection and testing requirements that apply to each deliverable.
- Documented procedures covering inspection, measurement, testing, and corrective action.
- Records management: how evidence is captured, indexed, and handed over so it can still be retrieved years after completion.
- Audit and surveillance schedules that confirm the system is being followed in practice, not just written down.
- Nonconformance handling and corrective action tracking carried through to verified closure.
- Interface controls between engineering, procurement, fabrication, and construction.
- Independent verification wherever the owner needs assurance that does not originate from the performing party.
The technical content of the system has to be tailored to the project specification. Code families such as ASME, API, AWS, and ISO are commonly referenced on industrial work, but which clauses apply depends on scope, commodity, and jurisdiction. Those requirements should always be confirmed against the contract documents and the relevant authority before they are written into an inspection plan.
Independent Oversight: Third-Party Inspection, Welding, and NDT
Independent oversight gives owners verification that does not depend on the organizations being verified. Specialist firms provide third-party inspection and quality oversight across fabrication, construction, and vendor shops, along with welding and nondestructive testing services covering methods such as CWI, RT, UT, PT, MT, and PAUT. The value sits in two places. One is finding defects early enough to correct them cheaply. The other is the traceable record showing that qualified personnel examined the work at the correct point in the sequence, using the correct method.
Commissioning as a Quality Discipline
Commissioning is often treated as something that happens after construction, when the real work is done. That framing creates avoidable rework, because systems that were never verified in sequence tend to reveal their problems all at once under load. On data centre projects, commissioning is structured in levels , with levels 1 through 5 aligned to ASHRAE Guideline 0. Planning that verification sequence alongside the build keeps quality measurement continuous instead of concentrated into a final, high-pressure window.
Measuring Quality While the Work Is Still Moving
Measurement continues throughout execution. Managers keep measuring the quality of all the tasks and activities relating to the project as they progress, rather than waiting for a completion review. Useful indicators include inspection pass rates, the number and age of open corrective actions, rework hours, and how complete the turnover documentation is at any given moment. The specific metric matters less than the habit. Ongoing measurement turns quality into a managed variable rather than a verdict delivered at the end.
Common Failure Points on Large Programs
Most quality failures on capital projects trace back to a small set of recurring problems.
- Quality planning compressed to protect the schedule, so acceptance criteria arrive after work has started.
- Systems written to satisfy an audit rather than to be used by field personnel.
- Inspection assigned entirely to the performing contractor with no independent check.
- Corrective actions closed administratively without verifying that the underlying fix worked.
- Handover documentation assembled at the end, when the people who held the records have moved on.
Each of these is cheaper to prevent than to correct, which is the central argument for investing in the quality system during concept and development rather than during execution.
Where to Start
A program level review is usually the right first step: compare the quality requirements in the contract against what each contractor's system actually delivers, confirm the interfaces are assigned, and check whether the records being generated will survive handover. From there, the work is to close the gaps in priority order, starting with the deliverables that are hardest to inspect once they leave the shop. Quality management rewards that kind of early, unglamorous attention, and capital projects rarely regret it.
Questions we get on this topic
What is project quality management?
Project quality management is the process of defining quality standards for a project's deliverables and then measuring, inspecting, and verifying the work against those standards. It combines quality planning, quality assurance, and quality control across the project lifecycle. The goal is to make sure results meet the quality targets and criteria the project requires, with deviations from specification identified and corrected rather than discovered at handover.
How does quality assurance differ from quality control?
Quality assurance focuses on the process , confirming that approved methods and procedures are capable of producing conforming work. Quality control focuses on the output, using inspection, measurement, and testing to verify that deliverables meet the acceptance criteria defined during quality planning. Assurance prevents problems by checking the system; control detects problems by checking the product. Mature programs run both continuously instead of relying on one alone.
Why do EPCM programs need independent quality oversight?
On an EPCM program, engineering, procurement, and construction are frequently delivered by different organizations, each with its own systems and definitions of acceptable work. Interfaces between those parties are where requirements get dropped or duplicated. Independent oversight gives the owner verification that does not come from the party being verified, along with consistent records across contractors, vendor shops, and fabrication yards.
When should quality planning begin on a capital project?
Quality planning should begin during concept and development, well before fabrication or construction starts. Acceptance criteria, inspection and testing requirements, and record formats need to exist while changes are still inexpensive. When planning is compressed to protect an early schedule milestone, criteria tend to arrive after work has begun, and the project loses its ability to measure quality objectively against the specification.
Which codes and standards apply to an industrial project?
Applicable standards depend on scope, commodity, and jurisdiction. Code families such as ASME, API, AWS, and ISO are commonly referenced on industrial work, and commissioning on data centre projects is often structured in levels aligned to ASHRAE Guideline 0. The governing requirements should always be confirmed against the contract documents and the relevant authority rather than assumed from previous projects.
Quality briefs, straight to your inbox
Field-tested guidance on inspection, audits and project quality systems — one issue on the first Tuesday of each month, written for people who have to make them work.
See past issues →- How the Checklist Differs from an ITP and Project Quality PlanA checklist, an ITP and a Project Quality Plan are connected — but they are not interchangeable. See how each document fits into the project quality-management system.
- Project quality plan: what a quality management plan must containThe quality management plan is the document a client reads first and the one most often written to be filed rather than used. Here is the section-by-section outline, and what separates a plan that governs execution from a plan that sits in a folder.
- Manufacturing Record Book (MRB): what goes in a turnover data bookThe MRB is the deliverable that decides whether a fabricated package is accepted or held. Here is what belongs in it, a reusable index, and the rejections that push turnover past the milestone date.
Need independent quality assurance on your project?
Talk to our team about inspection, auditing and QMS support.