Alberta O&G Construction QC: Fragmentation, Turnover, and Why the Office Cannot Carry the Load Alone
#alberta#oil-and-gas#quality-control#construction#aimqc#inspection
A pipeline project in Alberta closes out with thousands of welds, hundreds of inspection records, and a turnover package that is supposed to document all of it. The QC office was busy every day. And yet — three months after mechanical completion, nobody can quickly answer which ITRs are outstanding, which NCRs were closed without root cause, or whether every weld in the spool database has a matching inspection record.
This is not a failure of effort. It is a failure of structure.
The shape of the problem
Alberta oil and gas construction QC runs on a mix of field apps, spreadsheets, email threads, and PDFs. Each discipline has its own forms. Each contractor has its own filing conventions. Data that should be linked — an ITP line item, the inspection record that satisfies it, the NCR that was raised against it, and the ITR that wraps it up at turnover — lives in four different places, managed by four different people, with no enforced relationship between them.
The result is predictable: visibility is expensive. Getting a clear picture of where a package stands requires a QC lead or coordinator to manually chase records, reconcile versions, and stitch together a status report that will be out of date by the time it is read.
Turnover is where the debt comes due
APEGA and AB-83 turnover expectations are not new. The obligation to hand over complete, verifiable inspection and test records has existed for decades. What has changed is the scale and pace of projects, and the expectation of auditability — both from operators and from regulators — that comes with them.
When a project moves fast, shortcuts accumulate quietly. Inspection records get backdated. NCRs get closed administratively. ITRs get signed off against incomplete evidence packages. At turnover, the QC office is left reconciling months of accumulated gaps on a compressed timeline — typically with reduced staff, because the project is in closeout.
This is the turnover crunch, and it is largely a data architecture problem dressed up as a resourcing problem.
Why the office cannot fix this alone
The traditional answer is more QC staff. More coordinators. More reviewers. More checklists.
The problem is that the bottleneck is not attention — it is structure. Without enforced links between inspection events and the objects they are supposed to satisfy, no amount of human review can guarantee completeness. A coordinator reviewing 400 ITRs by hand will miss things. Not because they are careless, but because the information required to be thorough is scattered across systems that were never designed to talk to each other.
The office is being asked to produce system-level guarantees using individual-level effort. That gap does not close by working harder.
What a structural approach looks like
The AIMQC ecosystem is built around closing that gap at the data layer. Inspection records are created against ITP line items. NCRs are raised against specific inspection events. ITRs cannot be completed without satisfying their linked inspection requirements. Every action leaves an audit trail tied to a user, a timestamp, and a specific object in the domain model.
This is not a reporting feature. It is a precondition — the idea that validity should be enforced by the system, not audited after the fact by a person with a spreadsheet.
The office still carries judgment and accountability. But the system carries the structural burden: what links to what, what is missing, what cannot be closed until upstream items are resolved.
That distinction — between human judgment and structural enforcement — is what makes coverage at scale possible. And it is where the role of AI in QC begins, which is the subject of the next post.
David Olsson is CTO at AIMQC. Contact: dolsson@aimqc.com