รักษาระยะเวลา latent defects ให้มีผลตลอดห้าปี

Take the certified date of final completion off the certificate itself, store the certificate with the project rather than in a personal folder, and calculate the date five years on that clause 22.1 gives as the end of the latent defects liability period.

เหตุผล: Everything else in this case counts from that one date, and it is not the date of practical completion, the date of the handover meeting or the date the client moved in. Clause 22.3 also runs five years from termination where the agreement was terminated early, so a job that ended badly has a different start date and usually nobody who wrote it down.

Hold the as-built drawings, the specifications, the test and commissioning results, the material approvals and the consolidated health and safety file handed over under regulation 7(1)(e) of the Construction Regulations, 2014, indexed so somebody who was not on the project can find a detail by where it is in the building.

เหตุผล: A latent defect claim turns on showing what was specified, what was actually built and why the difference was not visible at final completion. That is a documents case, and the documents are the ones handed over at the end of the job. A pack that exists but cannot be searched is, four years later, the same as no pack.

Register the subcontractor guarantees and product warranties ceded to the employer at final completion under clauses 21.10 and 21.11, each against the element it covers, the party liable under it and the date it runs out.

เหตุผล: A waterproofing guarantee and the latent defects liability period are two separate routes to the same repair, and they expire on different days against different parties. An owner that registered neither ends up paying for a roof it had two claims for, and the subcontractor whose warranty it was has usually moved on by then.

Load the building and its plant onto the asset register with the warranty and the latent defects end date attached, and set an inspection before that date rather than only routine maintenance after it.

เหตุผล: Latent defects are latent, which means nobody is going to trip over them. The failures that are still recoverable in year four, movement in a slab, a failing membrane, a settled apron, are the ones somebody went looking for. An inspection booked deliberately against the end date is the only mechanism that turns a five year right into five years of use.

When a fault is reported, log it with the date, the location, photographs and any readings before anyone opens anything up, and classify it: wear, an operating fault, a defect covered by a live warranty, or a construction defect that was not discoverable at final completion.

เหตุผล: The most common way a good latent defect claim dies is that maintenance repaired the evidence in the first week. Once the failed detail has been cut out and replaced, what remains is an invoice and an opinion. Recording the condition before the repair costs an hour and is the whole difference between a claim and a complaint.

Put the defect to the contractor in writing with the evidence attached and the contractual basis named, track the claim against the end of the latent defects liability period, and keep the deadline visible to whoever holds the building rather than only to the project team that has moved on.

เหตุผล: Clause 21.12 makes the certificate of final completion conclusive as to the sufficiency of the works other than for latent defects, so the latent defects liability period in clause 22.0 is the only door left open. A claim raised a week after the five years is worth exactly nothing however good the evidence behind it, and the person who would have known the date usually left the company in year two.