What are Visi subtypes?
Visibuild has five core Visi types: Inspections, Tasks, Issues, Defects and Non-conformances. Subtypes let you go a level deeper, categorising work within each type in a way that reflects how your team actually operates. They give you a consistent way to categorise, filter, export and report on your work, and allow you to track more than just QA.
There are two kinds of subtype:
Platform subtypes are provided by Visibuild and available to every company from day one. They're marked with a padlock, and to keep the core Visibuild experience consistent for everyone, they can't be renamed, archived, disabled or converted into custom subtypes.
Custom subtypes are created by a company in its company setup, and are marked with a shared icon. Once created, they flow automatically to every project that company is on. A company can archive its own custom subtypes, and they can also be disabled on individual projects.
Platform subtypes
Visibuild provides a set of default subtypes that are common across the industry, so teams have a sensible starting point without needing to set anything up.
Inspections
ITC (Inspection Test Checklist)
ITP (Inspection Test Plan)
Audit
Site walk
Issues
Incomplete works
Incorrect works
Observation
Corrective action
Custom subtypes
Company Admins can create custom subtypes for any of the five core Visi types. They're defined once at the company level, and from there become available automatically on every project the company is part of.
Some examples of custom subtypes teams have created:
Corrective Action Report (CAR)
Near miss
Health and safety observation
Material inspection request
To create your own, see How to set up custom Visi subtypes as a Company Admin.
How subtypes work across projects and companies
Custom subtypes are always created at company level and flow down to every project that company is part of - they can't be created directly at the project level, since this would undermine the standardisation subtypes are meant to provide.
By default, a subtype is available on a project unless it's been disabled within that project, so Project Admins only need to step in when they want to remove one; there's no setup required to make a subtype appear.
This matters especially when a project involves more than one company. Both project owners and project partners can create their own custom subtypes, and once a company is added to a project, its subtypes become available there alongside everyone else's.
Important: You can disable your own company's subtypes on a project, but you can't disable another company's, whether you're the owner or a partner - if a partner's subtypes aren't relevant to your project, the right move is to raise it with them directly.
Subtypes that have been disabled or archived don't disappear from view entirely. They stay available as a filter for any Visis already created with them, so you never lose access to historical data.
Where you'll use subtypes
On templates - set a default subtype so every Visi created from the template is categorised automatically.
On Visis - choose a subtype when you create a Visi, or add or change one later by editing it.
In filters and reports - filter by subtype on the location page and dashboard, and include subtype in your exports.
What's next
To set up your company's subtypes, see How to set up custom Visi subtypes as a Company Admin. To manage subtypes on a specific project, see Manage Visi subtypes on a project.