The heavy building work finishes months before handover, and yet projects stay open for weeks in a phase that looks minor: a snag list. The reason is that this phase gets managed with tools that do not suit it — messages, photo groups, a spreadsheet per building — while it is the densest phase of the project in number of items and the thinnest in available resources. This is a guide to treating close-out as a managed stage rather than a tail left to chance.
Key takeaways
- A snag is incomplete work found before completion; a defect is a fault appearing after it. Confusing the two confuses who pays and when.
- One list with one reference per item settles most close-out arguments before they start.
- Only whoever raised an item may close it; self-closing empties the list of all its value.
- A self-snagging pass before inviting the consultant cuts the formal list to a third and protects your credibility.
- The handover pack is assembled from day one; assembling it in the final month is what usually delays handover.
Why the final month is where projects stall
At peak, a project has plenty of resources, repetitive work and clear measurement. At the end, all of that inverts: the work is scattered across hundreds of small locations, crews are already moving to other jobs, and access is constrained by finished work nobody is allowed to damage.
| Factor | At peak | At close-out |
|---|---|---|
| Size of an item | Large and repetitive | Small, spread over hundreds of locations |
| Resources | Available and dedicated | Being pulled to other projects |
| Access | Open | Restricted by finished work |
| Approvals | Periodic and orderly | Many, simultaneous and urgent |
| Progress measure | Quantities executed | Items closed and verified |
So the tools from the previous phase stop working. A bill of quantities has no line for "repaint the corner in room 312", and the daily report alone will not tell you how many items were closed this week against how many were opened. Without an explicit closure measure, a project can look stationary for weeks while everybody is working.
A snag is not a defect, and a defect is not a variation
Three labels get mixed up daily on site, and each carries a different payer and a different timing: snag, defect and variation. Confusing them is the source of most argument in close-out meetings.
| Item | Definition | Who carries it |
|---|---|---|
| Snag | Incomplete or non-conforming work found before practical completion | The contractor, within the original scope |
| Defect | A fault appearing after handover during the liability period | The contractor, under the defects obligation |
| Variation | A new requirement that was not on the drawings or in the specification | The client, through a priced variation order |
| Third-party damage | Damage caused by another contractor or by a user after partial handover | Whoever caused it, on dated evidence |
The distinction is not pedantry. An item classified as a snag withholds part of your money until it is closed, while something classified as a variation must be priced and approved before it is built. Logging a new requirement inside the snag list quietly converts it into a free obligation on you.
One list, not five
The normal state of a project with no close-out system: a consultant list, a client list, MEP items in a separate file, photographs in a chat group, and one spreadsheet per building. The result is duplicated items, closed items claimed again, and an argument about how many items remain before any argument about the items themselves.
- A unique reference per item, used in every message and photograph.
- A precise location down to room or grid line — never "third floor".
- The responsible trade: civil, electrical, mechanical, finishes.
- At least one photograph when raised, and one at closure.
- Who raised it and when; who it is assigned to and by when.
- Status: open / in progress / awaiting verification / closed.
- Closure evidence: a photograph, a test report, or a signature.
Raise
The item is raised from site with its photograph and location attached. An item written up in the office that evening has already lost half its detail.
Assign
One named person and a due date per item. An item assigned to "the subcontractor" with no name will not get closed.
Fix
Status is updated from site at the moment of the fix, not in a batched weekly update.
Verify
Whoever raised it, or their representative, inspects and compares photograph against photograph.
Close
Closed with evidence attached. And only whoever raised an item may close it — that single rule is what makes the number mean anything.
The four weeks before practical completion
Successful close-out is not more effort but a different order. The sequence below assumes four weeks — compress or extend it with the size of the project, but the order of the steps does not change.
Week one: self-snagging
Your own teams raise items against themselves before anybody is invited. The goal is that you find 70% of the list, not the consultant.
Week two: close by trade, and commission
Each trade closes its items in one sweep instead of walking between locations, and testing and commissioning are run with results documented.
Week three: joint walk and freeze the list
One walk with the consultant and client produces a signed joint list, agreed in writing as the list of record for handover.
Week four: verify and hand over the pack
Verified closure of the remaining items, the complete handover pack submitted, and the practical completion certificate requested in writing.
When the list is frozen, get that confirmed in writing. Items added after the freeze are not automatically refused, but they are handled as new items with their own classification — and some of them will be variations rather than snags.
The handover pack: what actually gets signed
Plenty of projects finish their snags and then hang on paperwork. The handover pack is not administrative housekeeping; in most contracts it is a condition of issuing the completion certificate, and delaying it delays the start of the liability period and the release of retention with it.
| Item | When it is collected |
|---|---|
| As-built drawings | Updated with every change during construction |
| Operation and maintenance manuals | On approval of each system, not at the end |
| Testing and commissioning reports | As each test is carried out |
| Warranties and manufacturer certificates | On delivery — not after the supplier’s account is closed |
| Material approvals and conformity certificates | With each material approval |
| Spare parts and key register | Two weeks before handover |
| Operator training records | As each system is commissioned |
| Statutory approvals and certificates | Per authority requirements, most of which need lead time |
The liability period and getting retention back
Practical completion is not the end of the relationship but the start of another clock: the defects liability period. During it you remain responsible for rectifying faults arising from workmanship or materials — not from misuse or missing maintenance, a distinction that is settled by documentation rather than by discussion.
- Document the condition of the works on handover day with comprehensive dated photographs — your only reference later in a "was this already there?" argument.
- Give the client one contact point for liability-period reports, and log every report with its date and classification.
- Separate misuse reports and raise them in writing as they occur, rather than arguing them at final settlement.
- A month before the period expires, request the final inspection in writing.
- Once items are closed, claim the certificate of making good and then the release of the second retention tranche.
The link to retention is what makes this stage financial rather than technical: typically half the retention is released at practical completion and half after the liability period ends. A single open item can hold up an entire tranche, which is why closing the last ten items deserves management attention on a par with chasing a full payment application.
A project does not end when the work stops. It ends when the last snag is closed and the last retained riyal comes back.
Frequently asked questions
What is practical completion and who decides it?
It is confirmation that the works are complete enough for the building to be used for its intended purpose, with only minor items outstanding that do not prevent use. It is issued by the consultant or whoever the contract empowers, following the contractor’s request and a joint inspection. Its effects are significant: liquidated damages stop, the defects liability period starts, and the first retention tranche falls due.
Can the client refuse handover over minor snags?
Minor items that do not prevent use do not usually justify refusing practical completion; they go on a list to be closed within an agreed period. Items affecting safety or preventing a core system from operating are a different matter. The practical fix is to agree the "prevents beneficial use" standard in writing early, rather than debating it on the day.
Who carries a snag caused by another contractor?
Whoever caused it — provided you can prove it with dated documentation: photographs of the condition of your work at completion, and an interface handover record between trades. Without that documentation, responsibility falls in practice on whoever worked in the area last. Handing over areas between contractors with a record and photographs is the cheapest insurance available at this stage.
How long is the defects liability period?
One year from practical completion is common; it varies by contract and may be extended for specific elements repaired during the period. Read it from the contract rather than from custom, and note that some systems and equipment carry longer manufacturer warranties which are passed to the client in the handover pack.
What do we do when items keep being added after the freeze?
Accept them, but classify them: a genuine in-scope snag joins the list, a new requirement becomes a priced variation, and later damage from use is documented and reported in writing. Written classification of every new item is what stops the list expanding indefinitely.
One snag list, from site to close-out
Raise items from your phone with photograph and location, assign them with a due date, close them with evidence, and track the weekly closure rate — in Arabic and English.