Skip to content
Project QualityPublished Nov 11, 2026 · 6 min read

Quality Risk Register for Critical Projects

Build a quality risk register that exposes failure modes, assigns accountable owners, and drives verified action across critical capital projects today.

Share
Executive summary

A quality risk register is not a spreadsheet maintained for an audit. On a critical project, it is the working record of what can fail, where that failure can enter the work, who must control it, and what evidence proves the control worked. If it does not change inspection priorities, supplier decisions, release points, or management action, it is documenting exposure rather than controlling it.

For owners, EPC firms, and quality leaders, that distinction carries material consequences. A missed hold point, unqualified welding procedure, substituted material, or incomplete turnover record can become months of recovery work, a delayed startup, a rejected asset, or a safety event. The register must therefore operate as part of project governance, not as a static line item in a quality plan.

What a Quality Risk Register Must Do

A quality risk register identifies threats to conformity, fitness for purpose, and verifiable acceptance before those threats become nonconformances. It should connect the requirements in contracts, drawings, codes, specifications, inspection and test plans, and regulatory obligations to the activities where defects are most likely to arise.

The register is not the same as a general project risk log. Schedule and commercial risks may belong in a broader enterprise register, but quality risks require technical detail: the applicable requirement, failure mechanism, inspection method, acceptance criteria, and objective evidence needed for release. A risk statement such as “poor vendor quality” is too vague to direct action. “Pressure vessel material traceability is lost during cutting and fit-up, preventing verification against the approved material certificate” is actionable.

It is also not a nonconformance log. A risk is a credible future failure that requires preventive control. A nonconformance is evidence that a requirement has already not been met. The two must inform each other. Repeated nonconformances , audit findings, supplier escapes, and late documentation gaps should trigger updates to the register, including stronger controls or higher residual risk ratings.

Build the Register Around Failure Paths

The most useful starting point is not a generic risk library. Start with the deliverable, the governing requirements, and the points where evidence can be lost or defects can be concealed. For a fabricated system, that may include material receipt, traceability transfer, fit-up, welding, nondestructive examination, coating, pressure testing, preservation, final inspection, and data-book compilation. For a civil scope, the failure path may run through subgrade preparation, reinforcing placement, concrete batch records, curing, testing, and as-built verification.

Bring the people who understand the work into the assessment: engineering, procurement, construction, supplier quality, commissioning, and the discipline inspector. Senior participation matters. A register built only from workshop assumptions tends to identify obvious hazards while missing the interfaces where critical defects occur - for example, design changes not reaching the shop floor, inspection records not matching serial numbers, or temporary protection being removed before final acceptance.

Each entry should answer six operational questions:

  • What requirement, asset function, or acceptance criterion is at risk?
  • What specific failure could occur, and at what stage?
  • What conditions make that failure more likely?
  • What is the consequence if the defect reaches the next stage or the completed asset?
  • Which preventive and detective controls are required?
  • Who owns the action, and what evidence closes it?

This level of definition makes the register usable by the field team. It also makes independent verification possible. An auditor or owner representative should be able to review an entry and determine whether the stated control occurred, whether it met the standard, and whether the risk remains within the approved tolerance.

Use a Scoring Method That Drives Decisions

Likelihood and consequence scoring are useful only when they lead to different treatment. A five-by-five matrix can work well, provided the organization defines each score in terms relevant to the project. Consequence should not mean only cost. Rate impacts across safety, regulatory compliance, asset performance, rework, schedule, documentation acceptance, and reputation.

A low-frequency failure can still warrant immediate senior attention where the consequence includes loss of containment, code noncompliance, or inability to certify the asset. Conversely, a moderately likely minor documentation error may be tolerable if it is quickly detectable and correctable before release. The decision depends on the work scope and acceptance regime.

Record both inherent and residual risk. Inherent risk reflects the exposure before planned controls. Residual risk reflects the exposure after the controls are implemented and verified. If the residual rating remains high, do not simply accept the number. Escalate the matter for a decision: add inspection coverage, revise the process, require a qualified specialist, change the supplier, or formally accept the exposure at the appropriate authority level.

Define Controls as Verifiable Work

Weak controls use vague language: “monitor supplier,” “ensure compliance,” or “conduct inspections.” These phrases do not establish frequency, responsibility, acceptance criteria, or records. A defensible control states exactly what will happen and how it will be proven.

For example, instead of “inspect welds,” define the control as: review approved welding procedures and welder qualifications before production; witness first-article fit-up; verify traceability at designated stages; perform surveillance against the inspection and test plan; review NDE reports against weld maps; and release only when the complete record package meets contract requirements. The right level of control depends on code, criticality, supplier capability, and past performance. It should never be copied without regard to the actual failure mechanism.

The register should identify the evidence required for closure . That evidence may include a signed hold-point release, geo-tagged photo record, calibrated test certificate, material test report, surveillance report, NCR disposition, CAPA effectiveness check, or approved turnover document. A statement that an action is “complete” is not evidence.

Assign One Accountable Owner

Every risk needs a named owner with authority to act. Shared ownership often means no ownership, particularly when a risk crosses engineering, procurement, and construction. The owner may coordinate several contributors, but one accountable person must maintain status, secure evidence, and escalate when controls are late or ineffective.

Set due dates around the point of no return. A supplier qualification risk must be closed before award or production release, not before final inspection. A design-interface risk must be resolved before fabrication begins. A commissioning documentation risk must be addressed before systems are handed over, not after the asset is energized.

Risk reviews should be linked to project gates and field activity. Review high-rated entries before procurement release, fabrication start, shipment, installation, pressure testing, mechanical completion, and turnover. This prevents a common failure: a register reviewed monthly while irreversible work advances weekly.

Keep the Register Connected to the Quality System

A quality risk register has value when it drives other quality artifacts. High-risk entries should be reflected in inspection and test plans, supplier surveillance plans, audit agendas, resource assignments, and management review reporting. Where risks concern recurring process breakdowns, they should also feed CAPA programs and lessons learned.

Consider a supplier with acceptable historical performance that receives a late engineering revision affecting critical dimensions. The supplier may not require full-time surveillance across all work, but the change creates a concentrated risk. The register should trigger targeted verification of revision control, first-off inspection, dimensional records, and downstream assembly compatibility. This is more effective than increasing inspection everywhere without a stated basis.

Independence matters at this point. When verification is performed by a party with no fabrication, installation, or equipment-sales interest, findings can be reported against the governing standard and the owner’s acceptance requirements. Jags Assurance applies this approach through qualified discipline specialists, formal surveillance records, and evidence that tracks actions to closure.

Review for Change, Not Just for Status

The register must change when the work changes. Update it after design revisions, supplier substitutions, failed tests, repeated NCRs, scope transfers, schedule compression, staffing changes, audit findings, or commissioning discoveries. Each event can alter likelihood, consequence, or the adequacy of existing controls.

Do not close an entry solely because the planned action was performed. Close it when the required evidence confirms the control was effective and the residual risk is accepted or reduced to the defined threshold. If a corrective action addresses the immediate defect but does not prevent recurrence, the risk remains open.

A well-run register gives leadership a clear view of where quality exposure is accumulating before it becomes visible in the field. Keep it specific, assign it to people who can act, and require evidence at every release point. That discipline turns quality risk management from a reporting exercise into a practical defense of the asset, the schedule, and the people who depend on both.

Get in touch

Need independent quality assurance on your project?

Talk to our team about inspection, auditing and QMS support.