Multi-choice requirements can now accept more than one answer. When a single option isn't the whole story, you no longer have to choose.

When you build a multi-choice requirement — in a template or directly on a Visi — you can now set whether it's answered with one option or many. Single-choice requirements show "Select one"; multi-select shows "Select one or many".

Out on site, people tick every option that applies instead of being boxed into a single answer. It works the same on web and mobile, and selected answers flow through to your CSV and PDF exports and the API like any other requirement data.

Until now a multi-choice requirement only captured one answer. When more than one applied, people picked the closest option and lost the rest, left the field blank, or built a duplicate requirement for each answer. Now a single requirement holds the full picture, and your reporting reflects what actually happened on site.

📱 Update to the latest version of the mobile app to fulfil multi-select requirements on site (6.7.0).

Defects now have a dedicated status, sitting alongside Open, In Review, Closed and Can't Close — so contested items get their own bucket instead of sitting in your open list or hiding in "can't close".

When an assignee disagrees with a defect — wrong trade, out of scope, not their job — they can mark it from web or mobile, with an optional comment explaining why. The people you nominate get an email, so the right person can step in early instead of chasing the disagreement over phone and text with no record.

The defect's creator or a reviewer then resolves it: send it back to Open, or close it as . The full history stays in the activity feed, and disputed defects show up across your list, filters, dashboards and exports.

Until now, a disputed defect either sat in Open — inflating the count your clients see — or got dumped in Can't Close, where it was impossible to tell apart from a genuine blocker. Now there's one clear, reportable way to handle a disagreement, and your defect numbers reflect what's actually contested.

Disputes are configured per defect round, where you choose who gets notified and whether a comment is required to raise one.

Note: "Require comment" is off by default

Visibuild Documents is live. A version-controlled home for every document on a project, connected to the inspections, defects, and locations where each document actually matters.

Until now, your quality data lived in Visibuild and your documents lived somewhere else — a shared drive, an inbox, a separate system — and the people doing the work toggled between them mid-task. When something goes wrong (a dispute, a DLP claim, an audit), the record you need is now one search away instead of days of reconstruction.

The Visibuild MCP is a secure connection between Visibuild and the AI assistant your team already uses — Claude, Copilot, Gemini, ChatGPT, or any tool that supports the Model Context Protocol. Once it's switched on for your company, your team can ask questions of their project data in plain language, without leaving the assistant they're already in.

The MCP gives your AI assistant a direct line to your Visibuild data. Out of the box it can:

Answer questions in plain English — " or The assistant pulls the answer straight from Visibuild and explains it back to you.

Find issues by meaning, not exact wording — the same defect logged as "water ingress," "leak around window head," and "damp staining behind skirting" finally surfaces as one signal. Semantic search catches the variants that keyword search misses. Work across your whole portfolio — questions like "have we seen this before?" run across every project at once, not site by site.

Your team is probably already using AI — and probably doing it the hard way, exporting CSVs and pasting lists into a chat window. The MCP removes that step. The data comes straight from Visibuild, the search understands what you mean rather than just matching words, and each tool is built to answer a real question in a call or two. Fewer turns, better answers, and trends that used to sit buried across project logs finally show up as one signal.

Note: This feature is specific to companies with the Tickets module enabled. Contact our sales team if you'd like to learn more about managing post completion defects.

Every ticket can now be categorised by root cause and responsible party, so accountability data is captured from the start.

Two new fields are live on tickets: Root cause and Responsible party. Your team defines the root cause options, and the responsible party is picked from companies on the project, or added on the spot. There's also a new Resolve option for when a defect is fixed but you still need time to assign accountability, separate from Closed.

This traces tickets back to where things actually went wrong, not just the trade that did the work. It turns post-completion from a record of work done into something that helps teams improve, with real insights and early warnings off the back of categorised data.

1️⃣ Go to Company setup > Tickets > Categorisation

2️⃣ Toggle Root cause or Responsible party on as mandatory

3️⃣ Create your root cause options and responsible party list

Here's the full guide.

Every defect round can now be configured to carry its own viewers, due dates, and approval workflow.

Existing defects keep their current settings — use a bulk update to bring them in line with the new round config.

Visit project setup to access.

Defect has been promoted from an Issue subtype to its own top-level Visi type. You can now create, track, and report on Defects independently across web and mobile.

Issues and Defects behave differently in Visibuild, and bundling them under a single category was causing confusion when creating, filtering, and reporting on them. Splitting them out makes it clearer which workflow you're using and sets us up for a much bigger release coming soon — support for custom Visi types.

No action is required — all existing Defect Visis have been automatically reclassified.

The API is unchanged in this release. A V2 of the core API is coming in the next month or two that will reflect these category changes (plus some new capabilities we're building). The current API version will keep working after V2 ships, with a deprecation window to give you time to migrate. Read more →

We've shipped a few updates to make the template review process smoother and more flexible.

Template reviewers can now choose "Approve and select next reviewer" instead of (or in addition to) "Approve and publish." This lets a reviewer complete their step and immediately hand the template off to another reviewer — without needing to publish first, then go back in to manually change the reviewer and re-request review. It's a lightweight way to run templates through multiple reviewers sequentially.

Previously, only head contractor project admins could be selected as a template reviewer. Now, any partner admin from any company in the project can be assigned — clients, consultants, subcontractors. If someone is marked as the reviewer, they automatically get visibility of that template. Head contractors project admins are still able to specify whether or they need to provide final sign-off before a template is published.

When a template review is cancelled, both the person who originally requested the review and the person who cancelled it will now receive an email notification. This closes a gap where templates could silently fall back to draft state without the original requester knowing — meaning templates were getting stuck in limbo without anyone realising.

Closing a Visi from the location screen used to mean tapping into it, finding the action button, confirming, and backing out again. Repetitive for reviewing a long list.

Now you can swipe left on any Visi card to reveal its primary action, right there in the list. Close a defect. Request a review. Reopen something that was mistakenly shut. For Visis with a checklist, you'll see that as a second action too.

Update to the latest version to get access (6.2.1)

Creating issues on site should be fast. This release rebuilds the issue create experience from the ground up on mobile, and it's now live for all projects.

This update requires the latest version of the app (6.0.2)