Construction Quality in 2026: Your Quarterly Recap.

Construction quality management is the discipline of planning work, capturing that it was done to standard, and holding onto the evidence that proves it. This quarter at Visibuild moved that discipline in one clear direction: from a record of what was done to a defensible, connected record you can prove, share and question.

That shift matters far more than any single feature. It changes what your quality data is actually worth the moment a dispute lands, an auditor calls, or a client asks a question you cannot answer from a spreadsheet.

Ten releases landed across defects, documents, AI, mobile, and templates and tickets. Read individually, they are useful. Read together, they describe a platform strengthening the quality record at exactly the moments it gets tested.

The rest of this recap follows four of those moments: when work is contested, when the record needs to be complete, when someone needs to question it, and when it has to be captured in the first place.

1. When work gets contested, the record has to hold

Two releases this quarter deal directly with disagreement.

In dispute: contested defects get their own bucket

The new In dispute status for defects gives contested items a home of their own, sitting alongside Open, In review, Closed and Can’t close.

• Assignees dispute from web or mobile, with a reason
• Nominated people are notified early, so nothing gets chased by phone
• The creator or a reviewer resolves it, back to Open or Closed (disputed)
• The full history stays in the activity feed and exports
• Disputes are configured per defect round, including who gets notified

Tickets: know what went wrong, not just who fixed it

For teams running the post-completion Tickets module, every ticket can now be categorised by root cause and responsible party, with a new Resolve status for when a defect is fixed but accountability is still being assigned.

It traces a post-completion defect back to where things actually went wrong, not just the trade that happened to touch it last.

What it means on site

In its 2025 Global Construction Disputes Report, Arcadis put the average value of a US construction dispute at 60.1 million dollars, taking around 12.5 months to resolve in North America. As trade press covering the report noted, the most common root cause is not fraud. It is parties failing to understand or comply with contractual obligations, which almost always comes down to a record no one can produce cleanly when it counts.

For the builder and the quality manager, In dispute means the open defect count clients see reflects what is genuinely outstanding, not what is merely contested.

For the owner and their representative, categorised tickets turn the Defects Liability Period from a shapeless backlog into evidence: a pattern of root causes that tells you which trade, which detail and which decision keeps coming back. In residential and healthcare handovers, where DLP claims are frequent and liability is sharp, that is the difference between settling in a meeting and arguing for a year.

2. A quality record that is complete, not scattered

The biggest release of the quarter closes the gap between your quality data and your documents.

Visibuild Documents: every file, connected to the work

Visibuild Documents gives every project a version-controlled home for every file, connected to the inspections, defects and locations where each document matters.

• Link a drawing, cert or spec to any Visi or location, including on mobile as you complete the work
• A new Document requirement type records the exact revision used at an inspection step as a permanent, point-in-time audit record, even if that document is superseded later
• AI-assisted upload pre-fills document number, revision, title and type, so large packs are not keyed in by hand

Defects, snags & punch lists get their own type, rounds get their own rules

Defect became its own top-level Visi type, promoted from an Issue subtype so it can be created, tracked and reported on independently. Existing defects were reclassified automatically, with nothing to do.

Defect rounds became configurable, each carrying its own viewers, due dates and approval workflow. New defects inherit the round’s rules, and a bulk update brings existing ones in line.

What it means on site

The cost of not having a connected record shows up in the rework research. The Construction Industry Institute puts direct field rework at roughly 5 to 9 percent of total project cost, much of it traced back to information problems rather than bad workmanship. The US National Institute of Standards and Technology once estimated 15.8 billion dollars a year lost to interoperability failures, and research published by the American Society of Civil Engineers continues to underline how documentation quality drives the number.

When quality data lives in Visibuild and documents live on a shared drive, the person doing the work toggles between them mid-task. The moment something goes wrong, the record has to be reconstructed over days. Documents makes it one search away.

For data centre delivery, this is the release that speaks loudest. The main client interface on a data centre project is at commissioning, where the agent is not navigating a building, they are validating a system. A point-in-time record of the exact drawing revision used at each inspection is what turns a commissioning pack from a last-minute assembly job into the natural output of the build.

For healthcare and infrastructure, where staged handovers and multi-package interfaces make version confusion the norm, linking documents to locations and inspections keeps a complex build auditable rather than merely finished.

3. A record you can question, not just store

The third moment is the newest one.

The Visibuild MCP: ask your data in plain English

The Visibuild MCP is a secure connection between your project data and the AI assistant your team already uses, whether that is Claude, Copilot, Gemini or ChatGPT.

• Ask questions in plain English, such as “What’s the health of Capital Towers?”, answered straight from your data
• Semantic search finds defects by meaning, not exact words, so “water ingress”, “leak around window head” and “damp staining behind skirting” surface as one signal
• Ask across your whole portfolio at once, not site by site

What it means on site

This is where the industry’s biggest gap sits, and it is one we went looking for ourselves. Visibuild’s own research into Australian construction leaders found that 73 percent believe AI will define who wins and who doesn’t over the next three years. Only 9 percent have the data foundation to act on it. The gap is not scepticism. It is infrastructure: quality data that is siloed, inconsistent and locked inside individual projects, which is exactly what an AI assistant cannot reason over.

The point that rarely gets made is that an assistant can only answer what your data can express. That is why the MCP and Documents belong in the same quarter. The connected, version-controlled record built by the rest of this release cycle is exactly what makes an AI assistant useful rather than confidently wrong. Visibuild stays a QA-powered platform. The MCP simply means the quality data you have already captured can now be questioned in the tools your team lives in.

For the head of data centres or a VP of delivery running a programme across many sites, the portfolio-wide question was previously impossible without exporting CSVs into a chat window: “Have we seen this before?”

4. None of it matters if it never gets captured

Every point above depends on one thing: the person on site actually logging the work.

Mobile: built for the pace of site

The mobile issue-create flow was rebuilt to be faster in the field, with suggested titles, photos from the camera roll, fields remembered between issues, the ability to switch types mid-flow, and evidence of rectification on by default.

Swipe actions followed. Swipe left on any Visi card to close a defect, request a review or reopen it, right there in the list, built for reviewing long lists at pace.

Templates: review that reaches the whole project

Template review can now be sent to anyone on the project, including clients, consultants and subcontractors, with a one-step “approve and select next reviewer” hand-off and an email alert when a review is cancelled.

And the whole template library now exports to Excel, a ready-made register for reporting, audits and stakeholders outside the platform.

What it means on site

A quality record is only defensible if it exists, and it only exists if the people doing the work will use the platform without being chased. This is the field-first layer, and it is the part generic tools tend to skip.

For the site engineer and the subcontractor, faster capture and one-gesture actions are the difference between a platform that gets fed and one that gets abandoned.

For trade partners following a head contractor onto Visibuild, review that reaches across companies means being part of the record, not emailed a PDF of it. Field adoption is not a nice-to-have. It is the foundation everything else here sits on.