The end of a defects liability period does not mean the asset has become incapable of having defects, nor does it necessarily mean every legal exposure has expired.
The supplied Defects.docx describes the Defects Liability Period (DLP), also called in the source a maintenance period, as a fixed contractual period commencing at practical completion. During it, the contractor may be required to complete minor outstanding work and rectify defects identified at practical completion or discovered during the period.
The source also notes that some security or retention may remain during the DLP and that defective work can sometimes be accepted subject to a price adjustment under the relevant contract.
Those mechanisms are historical and contract-specific. [FACT CHECK REQUIRED]
The enduring management lesson is that the DLP is a structured post-completion rectification window.
The Strategic Context
Practical completion is deliberately not the same as perfect completion.
An asset may be ready for use while minor defects remain.
Some defects only become visible after operation begins.
The DLP gives the project a defined period in which the contractor remains engaged to rectify qualifying issues.
This benefits both parties.
The owner gains a clear rectification mechanism.
The contractor gains the opportunity to correct work before the owner uses other remedies.
But the DLP must be understood correctly.
It is not a universal warranty period.
It is not automatically a limitation period.
It does not necessarily determine every statutory or tortious obligation.
What Leaders Commonly Misread
The first mistake is saying, “The DLP has expired, therefore the contractor has no further defect responsibility.”
That conclusion is too broad and requires legal analysis.
The second is holding security automatically without linking the amount to residual risk.
The third is allowing all outstanding work to migrate into a vague defects list at practical completion.
Major incomplete work should not necessarily be treated as a minor defect simply to achieve a milestone.
The fourth is failing to distinguish defect rectification from new scope.
The fifth is treating the DLP as passive observation rather than an active assurance period.
Reframing the Issue
The DLP should be managed as a residual performance program.
At practical completion, the project should know:
- what defects are already identified;
- what incomplete work remains;
- which tests or performance monitoring continue;
- what access the contractor requires;
- how defects are notified;
- how rectification is verified;
- what security remains;
- what happens at DLP expiry.
The objective is not to keep the contractor around.
It is to retire residual delivery risk systematically.
Strategic Analysis: The DLP Is a Transition Between Project and Operations
A hypothetical industrial facility illustrates the issue.
The plant achieves practical completion and operations take control.
During the next six months, several minor leaks, sensor calibration issues and finish defects appear.
Operations wants immediate fixes.
The contractor needs planned access to avoid disrupting production.
The project team is demobilising.
If no clear DLP governance exists, the owner becomes a coordination bottleneck.
The right approach is to define:
- defect logging;
- severity;
- response time;
- access windows;
- acceptance evidence;
- escalation;
- final close-out.
This is where Week 11's practical-completion architecture and Week 12's defects material connect.
Security During the DLP
The source states that an owner may retain a proportion of security or retention during the DLP as assurance of rectification.
That is conceptually sensible, but any typical percentage or release mechanism depends on the contract and jurisdiction. [FACT CHECK REQUIRED]
The strategic rule is that retained security should follow residual exposure.
If material defects remain, release may need careful assessment.
If all obligations are complete, indefinite retention can become commercially inefficient.
Strategic Analysis: Defect Data Should Influence Future Procurement
The defects register is not only a close-out tool.
It is supplier-performance and design-performance evidence.
If one contractor repeatedly produces the same workmanship defect, future sourcing decisions should know that.
If several contractors produce the same defect under one design standard, the issue may be design rather than supplier capability.
If defects cluster around commissioning interfaces, acceptance criteria may be weak.
This makes DLP data valuable at portfolio level.
A mature organisation should classify defects by cause, severity, recurrence and responsible interface. That evidence can improve specifications, inspection plans, evaluation criteria and supplier reviews.
The goal is to reduce the number of defects that need a DLP, not merely manage them efficiently once they appear.
Decision Framework
Use a DLP Governance Review.
At practical completion
Confirm the defect list, outstanding work, retained security and operating interfaces.
During the DLP
Track defects by severity, cause, due date and rectification evidence.
Before expiry
Inspect unresolved issues and determine what contractual notices or directions are required.
At close-out
Confirm completion, residual latent-risk records and any security release.
The exact legal effect of DLP expiry must be verified under the governing contract and law. [FACT CHECK REQUIRED]
From Strategy to Execution
Immediate action: create one controlled defects register shared between project and operations.
Medium-term capability building: define DLP ownership before the project team demobilises.
Long-term strategic positioning: analyse defect patterns across projects to improve design standards, supplier selection and acceptance criteria.
A defect should become learning, not only rectification.
Signals to Monitor
Watch for practical completion with a large unresolved defect list, project staff leaving before DLP ownership transfers, defects tracked through email rather than a register, repeated contractor access problems, security release disconnected from defect status, or teams treating every post-completion issue as automatically outside the contract.
Questions for the Leadership Team
- What does our actual contract require during the DLP?
- Which outstanding items are defects and which are incomplete scope?
- Who owns defect management after handover?
- What evidence proves rectification?
- Is retained security proportionate to residual risk?
- What obligations may survive DLP expiry?
- What defect patterns should change future designs or supplier decisions?
Closing Perspective
The DLP is not a magic legal boundary.
It is a practical governance period that helps transition an asset from project delivery into reliable operation.
Used well, it closes visible defects while preserving the evidence needed to manage what may emerge later.
Related article: Practical Completion Is a Transfer Point, Not the Finish Line
Related article: Latent Defects Outlive Handover: Governing Residual Liability After Completion
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.