Practical completion triggers half your contract obligations. Here's what it actually means, the common arguments, and how to manage the process properly.
Practical completion is the most important milestone on any construction project. It's the point that triggers the release of half the retention, ends your liability for liquidated damages, starts the defects liability period, transfers insurance risk, and — for most contractors — marks the point where you can finally invoice your last interim application and start closing the job down.
Given all that, you'd think the industry would have a clear, universally agreed definition of what practical completion actually means. It doesn't.
JCT contracts don't define practical completion. They refer to it extensively — it triggers obligations throughout the contract — but they never say what it is. That deliberate ambiguity has been the subject of decades of case law, and the position that's emerged is essentially this:
Practical completion means the works are complete for all practical purposes. That doesn't mean perfect — it means the client can use the building for its intended purpose, and any remaining items are so minor that they don't prevent that use.
The classic formulation comes from the case of Emson Eastern v EME Developments, where Judge Newey stated that practical completion means completion for all practical purposes — that is, free from patent defects other than ones that are very minor.
What constitutes "very minor" is, predictably, where the arguments happen.
Snag lists. The most common battleground. The architect or employer's agent carries out an inspection, produces a snag list with 150 items, and refuses to certify practical completion until they're all resolved. Is that reasonable? It depends on the items. If 140 of them are paint touch-ups and 10 are leaking valves, the answer is probably different from a list where most items are incomplete works or significant defects.
The general principle is that practical completion should not be withheld because of minor snagging items that don't prevent the building being used. Those are defects matters — they should be recorded and dealt with during the defects liability period. Withholding practical completion to use it as leverage for snagging is technically a misuse of the certificate, but it happens routinely.
Outstanding works. If there are areas of work that simply haven't been completed — a plant room that hasn't been fitted out, a section of floor that hasn't been laid — that's not snagging, that's incomplete work. And practical completion shouldn't be certified while significant work remains incomplete.
The grey area is where a minor element is physically incomplete but functionally irrelevant — a cupboard door that's on order but the room is otherwise complete and usable, for example. Reasonable people can disagree about whether that prevents practical completion.
Commissioning and testing. On projects with significant M&E content, the question of whether systems have been properly commissioned and tested is often the most contentious element. You can argue that the physical works are complete, but if the heating system hasn't been balanced or the fire alarm hasn't been commissioned to the satisfaction of the building control officer, is the building practically complete?
Generally, if commissioning is required under the contract, it needs to be done before practical completion. The building needs to be safe and functional.
Here's how to manage the practical completion process properly:
Carry out your own inspection first. Before the architect or employer's agent sets foot on site for the PC inspection, walk the building yourself. Create your own snag list. Fix what you can. You want the formal inspection to be a formality, not a discovery exercise.
Give adequate notice. Tell the contract administrator you'll be ready for a PC inspection at least two weeks in advance. This gives them time to arrange it, gives you time to finish off, and avoids the argument about availability.
Be present at the inspection. Walk around with the inspector. If they raise items, you can often clarify on the spot — "that's the specified finish, not a defect" or "that valve is awaiting the part which arrives Thursday." Being present turns a one-way inspection into a two-way conversation.
Agree the snag list. Not every item on a snag list is necessarily your responsibility. Client damage after partial possession, design issues, items that are actually as specified — challenge where appropriate. But do it constructively and with reference to the contract and specification.
Prepare your documentation. At practical completion, you typically need to hand over operation and maintenance manuals, as-built drawings, commissioning records, guarantees and warranties, health and safety file information, and any other documents required by the contract. Having these ready avoids the very common situation where practical completion is delayed because the contractor hasn't assembled the handover documentation.
Get the certificate. Practical completion should be certified in writing. Don't accept a verbal statement that "we're treating the building as practically complete." The certificate triggers contractual obligations on both sides — it needs to be formal.
Once practical completion is certified:
Half the retention is released. Submit a request immediately. Don't let it drift.
The defects liability period starts. Typically 12 months under JCT. During this period, you're obliged to return to site and remedy any defects that become apparent. Schedule this into your resource planning — defects callbacks are inevitable and need to be managed proactively.
Liquidated damages liability ends. If you're in delay, the employer's right to deduct liquidated damages crystallises at practical completion. If you achieved PC on time or early, this is a non-issue. If you were late and no extension of time was granted, the employer can deduct LDs for the period between the contract completion date and the actual PC date.
The final account clock starts ticking. Under most JCT contracts, the contractor should submit their final account documentation within a specified period of practical completion. Don't leave this until the last minute — getting the final account agreed quickly frees up your QS and closes out the commercial risk.
Not pushing for the certificate. If the works are practically complete and the architect is dragging their feet on the certificate, write to them formally. Every day without a PC certificate is a day your retention isn't being released and your defects period isn't running.
Accepting partial possession when PC would be more appropriate. Partial possession has different contractual consequences — make sure you understand the difference and are agreeing to the right thing.
Neglecting the handover documentation. I've seen projects where the works were physically complete for weeks but practical completion was delayed because the contractor hadn't assembled the O&M manuals. This is entirely avoidable with proper planning.
Forgetting about defects management. Practical completion isn't the end — it's the start of a 12-month obligation. Budget time and resources for defects callbacks, track what's reported and what's been resolved, and manage the process systematically through to the certificate of making good.
The PC process — snag lists, documentation handover, defects tracking — is one of the areas where having a proper system pays dividends. At Construction AI, our site management inspection and snag list tools are designed specifically for this workflow: capture items on site with photos, assign responsibility, track resolution, and maintain a clear record through to close-out.
But system or no system, the fundamentals don't change. Prepare thoroughly, manage the inspection professionally, get the certificate, and follow through on defects.
Stephen Mckenna MCIOB
30+ years in UK commercial construction, from site management to director level. Now building the project management tools he wished he'd had.
Tier-one contractor processes shouldn't only be available to tier-one contractors. Drawing registers, document control, RFIs, programmes, financial tracking — built for how you actually run projects, priced so any construction business can access them. Get started today.
By subscribing, you agree to our Privacy Policy.
NEC4 is gaining ground where JCT has dominated. Here's what's actually different, when each contract framework makes sense, and what your software must handle.
A delay that isn't notified is a delay you'll pay for. Here's how to identify delay events, notify properly, and build EOT claims that actually succeed.
Choosing the wrong JCT contract costs thousands. A practical guide to when Minor Works is right, when you need Intermediate, and the grey area in between.
Tier-one processes, priced for any size business. Get started today.