Snag List and Defect Follow-Up Automation for Building Projects

What this service does

A snag list is the record of small defects and unfinished items found before a building is handed over. In the UK, the list is usually issued by the contract administrator, the person named in the building contract to certify works. In Australia the same role often sits with a superintendent or project manager. Whatever the title, the list only protects anyone if each item is clear, located, assigned and closed with evidence.

Most projects still run this on photos in phones, spreadsheets and emails. Items get copied by hand, photos lose their location, and a subcontractor says a fix was done without a record. AiStaffo sets up AI workers that take over that routine chain. They log each defect from site photos and inspection forms, attach it to a location and trade, assign it to the right subcontractor, send reminders until the item is closed, and produce a handover status report. A site manager signs off every closed item.

Why open items become expensive

The cost of unresolved defects is measurable. A 2000 study by Love and Li, based on two Australian building projects, put the cost of rework at 2.40% and 3.15% of contract value. Those figures are older and drawn from a small sample, so treat them as an indication rather than a benchmark for your job. The pattern they show still matters: work that has to be redone after the fact is paid for twice.

Timing adds pressure. In a UK project management guide published around 2024, the defects liability period after practical completion was described as usually running from a few months up to a year. During that window, every unresolved item is a live obligation. A list that cannot show which trade owns which fix, and when it was closed, makes disputes harder to settle.

Who this is for

The service fits any organisation that manages building or fit-out work with several subcontractors and repeated site inspections. That includes a five-person builder with two trades on one job, a developer handing over several blocks at once, and a facilities or property team running fit-outs across multiple sites. The size of the team matters less than the number of trades and the number of defects per handover.

It suits project managers, site managers, quantity surveyors and operations heads who currently spend days each week chasing subcontractors for status updates. It also suits owners who want a clear written trail of what was raised, what was agreed and what was closed.

What is included

• A defect log built from site photos, voice notes and completed inspection forms, with each item tied to a location and trade
• Assignment of each item to a named subcontractor, with a due date and the instruction the site manager wrote
• Automatic reminders to the assigned party until the item is marked closed or escalated
• A closure step where the subcontractor attaches evidence, and a site manager signs off before the item is counted as closed
• A handover status report listing open, closed and disputed items by trade, location and age
• A record of every change in status, kept for the defects liability period
• A written process map of your current snagging steps, so you can see where items stall

How the work runs

The service follows five stages. Each stage ends with something you can review before the next one starts.

The sign-off step is deliberate. The AI worker can propose that an item is complete when a subcontractor uploads evidence, but a site manager confirms the closure. That keeps a named person accountable for every item the handover report calls closed.

Typical timeline

For a single site with a manageable number of trades, the audit and process map usually take about two weeks. The build and parallel run typically take four to six weeks more. Multi-site groups or projects with many trades take longer, because each trade needs its own assignment rules and reminder sequence. These are planning ranges, not guarantees. The audit sets the final plan for your project.

What you provide

You provide the access and the material the workers need to do the job correctly. That means your current inspection forms, sample snag lists from past handovers, a list of subcontractors with their trades and contact routes, the building contract clauses that define practical completion and the defects period, and floor plans or site maps with room or zone names. You also name the site managers who sign off, and agree the severity categories that decide which items block handover.

Someone on your side must also decide the escalation path. If a subcontractor ignores three reminders, who calls them? If a dispute appears, who speaks to the other party? The system records these events. It does not make the decision.

What this does not cover

The service does not inspect the building. It cannot tell from a photo whether a finish meets specification, whether a wall is out of plumb to a tolerance, or whether a fire barrier was installed correctly. A qualified person still makes those judgements. The AI worker logs what is recorded and flags missing information, but the severity and the decision to accept or reject remain with your inspector.

The service does not certify practical completion, does not replace the contract administrator or the building certifier, and does not give legal advice on defect claims. The rules on defect notices, retention and time limits come from your building contract and local law. This explains the workflow in general terms; it is not legal or tax advice for your case.

It also needs a steady data connection or offline capture in the field tool you choose, and it depends on photos and forms being filled in on site. If site teams do not record defects at all, the system has nothing to route. A project with very few defects and one trade may not justify the setup effort. The audit tells you whether it does.