All required documentation is in place: approved Method Statements, completed and signed ITPs, material certificates, test reports, inspection records, and a properly maintained construction site diary.
Everything indicates that the work was performed in accordance with the project requirements.
However, after completion or during operation, a defect appears – for example, water leakage through a waterproofing system, a leaking roof, or a leaking pipe connection.
How can this happen?
Does it indicate a failure in Quality Assurance, Quality Control, the inspection process, or a gap between documented compliance and actual construction quality?
Saving Changes...
Sort By:
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Aleksandar, thank you for raising this important question.
Yes, a construction project can have all the required documentation properly completed and approved, yet experience defects after completion. But before concluding that Quality Assurance, Quality Control or inspection failed, we need to establish what the available evidence actually demonstrates and what caused the defect.
I would distinguish three dimensions.
First, documentary compliance is not necessarily evidence of complete construction compliance.
Approved Method Statements, signed Inspection and Test Plans (ITPs), material certificates and inspection records provide important evidence, but their conclusions are limited by the requirements assessed, the methods applied and the conditions verified.
A signed inspection record demonstrates that an inspection was documented and accepted within a defined scope. It does not, by itself, establish that every relevant condition was examined or that the system will perform correctly under all future circumstances.
Second, a defect does not automatically establish a failure in QA, QC or inspection.
Consider a leaking roof. The cause might involve defective installation, an inadequate design detail, an interface between construction elements, subsequent damage or operating conditions outside those originally specified.
These possibilities require different investigations.
The essential starting point is to characterise the defect, identify plausible failure mechanisms and examine the evidence needed to distinguish between them.
Only then can we determine whether a requirement was not met, a control was inadequate, an inspection failed to detect a relevant condition or the failure arose from circumstances outside the original verification scope.
Third, compliance must also be examined through the relationships between documents, decisions and actual execution.
This is where relational analysis can provide additional value.
A Method Statement, Risk Assessment, ITP, construction schedule and design documentation may each appear acceptable when reviewed individually, while inconsistencies emerge from their interdependencies.
For example, suppose an approved waterproofing methodology is changed during execution because of site constraints.
That change may affect the installation sequence, interface details, identified risks or required inspections.
If the relevant documents and controls are not reviewed accordingly, the records may remain formally complete while no longer adequately representing the work performed or the conditions requiring verification.
This is a hypothetical example, not an explanation of any particular defect.
Importantly, relational analysis is not a substitute for technical investigation, inspection or testing. It can help identify inconsistencies and missing connections, but it cannot establish the cause of every failure.
We must also consider the opposite possibility: the documentation was accurate, the work complied with the approved requirements, and the inspections were properly performed, yet the system subsequently failed.
In that situation, the investigation may need to examine the adequacy of the design, the acceptance criteria, deterioration or conditions encountered during operation.
Compliance must therefore be assessed against defined requirements, supported by evidence appropriate to the conclusions being drawn, and understood in relation to the conditions and time of verification.
For me, the practical implication extends beyond document control.
When methodologies, designs, sequences or site conditions change, the responsible parties need to determine which assumptions, risks, inspection requirements and previous approvals must be reassessed.
Otherwise, formal approval may persist even when the conditions supporting it have changed.
Ultimately, the objective is not simply to demonstrate that the required documentation exists. It is to establish whether the requirements were appropriate, the work was executed accordingly, the relevant interfaces were controlled and the evidence supports the conclusions reached.
I would therefore add one question to yours:
Are we verifying only that individual documents and activities satisfy their respective requirements, or are we also verifying that the relationships between design, methodology, risk controls, inspections and actual execution remain coherent as the project evolves?
That distinction may be essential to understanding why a project can appear compliant on paper while a defect remains undetected or emerges later. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Aleksandar, I would like to add one further dimension to my previous comment: the effectiveness and accountability of the verification system itself.
Who verifies that those responsible for checking compliance are actually performing their responsibilities effectively?
A completed inspection is not necessarily an effective inspection. Likewise, a completed audit does not, by itself, demonstrate that the quality management system is effective.
However, we need to distinguish responsibilities.
Inspectors verify specified characteristics of the work against applicable requirements, within their assigned scope. Auditors evaluate evidence against defined audit criteria, which may include the effectiveness of processes and controls. Neither function can guarantee that every defect will be detected.
Now consider a situation in which a defect existed during construction, was reasonably detectable through a required control, yet remained unidentified.
The investigation should not stop at the technical defect. It should also establish whether the control was adequately designed, correctly performed and capable of detecting the relevant condition.
These are different questions, with potentially different responsibilities.
Was the inspection requirement appropriate? Was the verification properly executed? Was relevant evidence overlooked? Were identified deficiencies escalated and addressed?
We should also examine the organisational conditions under which verification takes place.
Do those responsible have sufficient competence, independence, time, information and authority? Are their findings acted upon? Could schedule, cost or contractual pressures compromise the integrity of verification?
These are matters for investigation, not assumptions about any particular project.
Crucially, responsibility for the effectiveness of the quality management system cannot be transferred entirely to inspectors or auditors.
Within their respective authority, management must ensure that appropriate controls are established, adequately resourced, evaluated and improved. Individual verification responsibilities and management accountability are related, but they are not interchangeable.
This raises a further governance question:
Who evaluates whether the verification system is achieving its intended purpose, and who has the authority and responsibility to correct weaknesses when it is not?
The answer should not simply be to introduce more inspections or audits. Additional controls are only valuable when they address an identified need and their effectiveness can itself be evaluated.
If a reasonably detectable defect passes through a control intended to identify it, the evidence may reveal an individual verification failure, an inadequately designed control, a broader weakness in quality governance, or a combination of these.
The appropriate conclusion depends on the evidence, not on the number of approvals or signatures.
Correcting a defect restores the affected work. Correcting the weaknesses that allowed it to remain undetected strengthens the system.
And that, for me, is the essential distinction between completing quality verification activities and demonstrating that the verification system is effective. Saving Changes...
