IPM Limited All articles
Compliance & Regulation

After the Keys Change Hands: Running Defects Liability as a Managed Workstream

IPM Limited
After the Keys Change Hands: Running Defects Liability as a Managed Workstream

Photo: Stephen Craven , CC BY-SA 2.0, via Wikimedia Commons

Practical completion is often treated as the finish line. The keys are handed over, the site team begins to demobilise and attention moves to the next scheme. Yet for commercial property owners and occupiers, the months that follow can be among the most revealing. Systems are used in earnest, building fabric is tested by real weather and real occupancy, and faults that were not apparent during commissioning begin to surface.

The defects liability period, often twelve months but sometimes longer or shorter depending on the contract, is intended to provide a structured route for those issues to be put right. In practice, it can become an informal exchange of emails, photographs and site visits. The result is predictable: some matters are resolved quickly, others drift, and the evidence needed to support final certification or retention release is incomplete.

A better approach is to treat the defects period as a managed workstream in its own right. That does not require a large team, but it does require clarity about ownership, records and reporting.

Snagging and defects are not the same thing

The first step is definitional discipline. Snagging is generally associated with work that is incomplete or not yet in accordance with the contract at or around practical completion. Defects liability, by contrast, concerns faults that appear or become apparent after handover during the agreed period.

Not every issue reported after occupation is a defect. Some may be wear and tear, misuse, damage by tenants or contractors, a design responsibility held by others, or a maintenance item that sits outside the building contract. The contract definitions and the agreed scope of works should govern how each item is classified. A register that treats every complaint as a contractor defect will quickly lose credibility with all parties.

It is equally important to distinguish between patent defects, which are visible or ought to have been discovered on reasonable inspection, and latent defects, which may not become apparent for some time. The contractual and statutory position can be complex, so classification should be based on the specific agreement and, where necessary, professional advice. The management task is to record the issue accurately, not to make a legal determination in the first instance.

Give the period a named owner and a single register

The most common failure is diffuse responsibility. The project manager has moved on, the facilities team is managing day-to-day operations, and the contractor is focused elsewhere. Reports arrive through different channels and no single person can say which items are open, which are overdue and which have been closed.

A named owner should be appointed for the defects period. This may be a project manager, a property manager or a technical administrator, depending on the size of the asset and the contract. The important point is that the role is explicit and has time allocated to it.

The owner should maintain one register as the single source of truth. A workable entry will include:

A shared spreadsheet can be sufficient for a modest project. Larger or multi-building portfolios may warrant a dedicated defects module within an existing asset management or project system. What matters is that the register is accessible to the relevant parties, updated consistently and not duplicated across inboxes.

Triage by consequence, not by volume

Not every defect carries the same risk. Triage should reflect safety, business continuity, statutory compliance and damage potential. Water ingress, electrical faults, fire safety issues, heating failures in occupied space and problems affecting statutory compliance should be escalated immediately. Cosmetic matters can follow a normal track.

The contract may specify response and rectification periods, or it may require the contractor to attend within a reasonable time. Those obligations should be reflected in the register and monitored. Where the issue is urgent, a telephone call may be appropriate, but it should be followed by written confirmation so that the record is complete.

Triage also helps to manage expectations. A tenant reporting a mark on a wall and a tenant reporting a failed pump should not receive the same response. A clear priority framework allows the owner to explain what will happen, and when, without treating every item as an emergency.

Notices, evidence and the paper trail

Contracts often contain specific notice requirements. These may set out how and when a defect must be notified, to whom, and what information must be provided. Missing a notice deadline can affect the parties' positions, so the contract should be checked at the outset and the requirements built into the register workflow.

Written notification should be factual and unambiguous. It should identify the location, describe the observed condition, attach evidence and state the contractual provision relied upon where appropriate. Photographs should be dated and, where possible, taken from a consistent position. Access records, temperature readings, maintenance logs and tenant reports can all be relevant.

This is a management guide rather than legal advice. Where a dispute is developing, or where the consequences of a notice are significant, specialist legal or consultancy input should be sought early rather than reconstructed after the event.

Track contractor responses and access

The register should record what the contractor has been asked to do, when they intend to attend and what they have done. A closed item should have closure evidence, not merely a verbal assurance. That may be a signed-off work sheet, a completion photograph, a test result or a joint inspection note.

Access is a frequent source of delay. Occupied buildings require coordination with tenants, permits, out-of-hours working and safe systems of work. The owner should track access requests and refusals, because repeated no-access events can obscure whether the contractor or the occupier is causing the delay. Agreed access arrangements should be confirmed in writing.

Where a contractor attends, the visit should be recorded even if the issue is not resolved. A pattern of repeated visits without remedy is useful evidence and should trigger escalation rather than another informal email.

Establish a reporting rhythm

A defects period without a reporting rhythm will drift. A short weekly review of open urgent items and a monthly report to the client and contractor is usually enough for most projects. The monthly report should show the number of items opened, closed and outstanding, overdue items, repeat visits, access issues and any matters approaching the end of the period.

Reporting should be concise and decision-oriented. The question is not simply how many defects exist, but which ones present risk, which are stuck and what decision is required. Escalation should be agreed in advance: who contacts the contractor when a response is overdue, who authorises urgent remedial work and who signs off closure.

Protect the close-out position

The end of the defects period is not an automatic event. The contract may require a final inspection, confirmation that outstanding defects have been remedied, and the provision of warranties, operating manuals, as-built information or training that was outstanding at handover. The final certificate and release of retention or security should follow evidence, not assumption.

Leverage is strongest when the record is complete. A contractor is more likely to return to complete minor items if the request is clear, contractual and supported by a schedule of outstanding works. Conversely, withholding retention without a documented basis can create as many problems as it solves.

Before final sign-off, the owner should reconcile the register, obtain closure evidence, confirm that any agreed remedial works are complete and record any items that remain outstanding or are subject to a separate agreement. The asset register and maintenance plan should then be updated so that the building's operational history reflects what has happened.

The defects liability period is a finite window. Managed well, it protects the value of the completed works and gives the occupier confidence that the building will perform as intended. Managed as an afterthought, it becomes a slow exchange of unresolved emails. The difference lies in deciding, at handover, that the period will be run like a project.

All Articles

Related Articles

Before the SLA Bites: Structuring the First Quarter of an FM Contract

Before the SLA Bites: Structuring the First Quarter of an FM Contract

Consent First, Contractors Second: Untangling the Licence to Alter Process

Consent First, Contractors Second: Untangling the Licence to Alter Process

Counting the Cost of 'Next Year': A Governance Guide to Maintenance Backlogs

Counting the Cost of 'Next Year': A Governance Guide to Maintenance Backlogs