Closing out snag lists: how it works

What does closing out a snag list actually mean?

The project owner declares works reception with or without reservations. Closeout tracking then organises verification of reported repairs, item by item.

A snag is not closed because the contractor says it is fixed. It is closed when the architect re-inspects the exact location, confirms the work matches the requirement, and records dated evidence. The original observation, corrective work, and verification should remain linked in the project history.

Illustrative example: of 80 snags, 60 may be verified and closed while 20 remain open. The report should distinguish these two lists.

How long do you have to close out a snag list?

Article 1792-6 of the French Civil Code provides for repair deadlines agreed between the project owner and the contractor concerned.

Record the agreed date, responsible party and next action. If work is overdue, retain the follow-up history and check the appropriate contractual steps with the parties. Do not infer retention or payment from a snag status alone.

What proof do you need to close out each snag?

A useful record connects the original finding, location, available photos, remedial work and inspection outcome. Identify who recorded each step and when. Appropriate evidence depends on the defect and the inspection needed.

Keep rejected items and items requiring further checks, with reasons. A photo alone may be insufficient to verify a repair; the record should explain the inspection performed.

This chain is kept automatically. Every reserve logged on-site carries its location, trade, photo, and deadline. When the architect lifts it, the verification photo and timestamp attach to the same record, so the closeout is audit-trailed end to end.

What is the PV de levée des réserves?

The closeout report identifies the inspected snags, references, dates, evidence and outcomes. The relevant parties agree the formal record appropriate to the project.

It supplements the works reception record and preserves still-open items. Preparing it does not automatically release retention or extinguish all warranties.

In Builddar, the PV de levée des réserves is generated from the live snag data, not retyped. Every lifted reserve, its date, and its verification photo flow straight into the document, so the proof you captured on-site is the proof in the signed PV.

What should you check before closing a snag?

Find the original observation, location and before-work photos. Ask the contractor for the repair date and evidence attached to the same item identifier.

Compare the evidence with the reported defect. If it is inconclusive, keep the item open and arrange the necessary inspection. Record who checked it, when and on what basis.

Share the list of closed and still-open snags. Keep the evidence with the project file instead of replacing the original observation with a photo without context.

Annotated example: a joint requiring repair

Illustrative example: item R-017 concerns a discontinuous joint in the bathroom of home A-204. The initial photo locates the defect. The trade and contractor identify the assignee; a deadline records the expected repair.

An after-work photo is added. Tracking distinguishes a reported repair from a verified repair. If the photo does not show the entire joint, further inspection is needed before validation.

The PDF below illustrates a document format. Names, identifiers and data are examples; no customer outcome or time saving has been measured.

What framework applies to reception and repairs?

Article 1792-6 of the Code civil distinguishes reception by the project owner, with or without reservations, from repairs under the completion warranty. Repair deadlines are agreed with the contractor concerned. Software records these steps without replacing the parties’ agreements and decisions.