The Visibuild Web App is a browser based application you can access from your browser. It has been designed to support you while in the office as you track the status of your work and progress of the project.

Launch web app

The Visibuild app is accessible on your mobile phone and has been designed to support you while in the field. Your app will work even when you don’t have phone service and changes will be synced once you come back online.

Visis are the building blocks of Visibuild, there are 4 types of Visis that can be created: Inspections, Tasks, Issues or NCRs. Visis represent work that needs to be completed and each type of Visi serves a different purpose.

An Inspection Visi is used for both Templated Inspections or ad-hoc Inspections (site walks). Unlike all other Visi types, an Inspection contains a progress bar and a checklist section where Tasks, Issues or even other Inspections can be nested. An Inspection can only be closed once all the Visis in the checklist have been closed.

Examples:

A Task Visi is an item of work that needs to be completed on the project, this could be a personal task eg. “Check pressure test results match the project spec" or it could be a specific task related to a templated inspection “Check pressure test results match the project spec”. Tasks can be created standalone or nested inside an inspection to detail each check that needs to occur.

An Issue Visi represents an issue that has been observed on the project. Typically issues are related to work that has already occurred whereas Tasks are focused on work that needs to happen. Any project is going to have hundreds of Issues and that’s okay as its part of the construction process. Logging these issues in Visibuild ensures they are resolved quickly before they turn into costly mistakes.

Examples:

An NCR Visi represents a more serious issue where work has not been completed to the correct specifications or fails to meet quality standards. The definition of what constitutes an NCR in your company will determine when this Visi type should be used rather than just an issue. Typically the difference between an Issue and an NCR is that an NCR requires more significant work to resolve and poses more risk to the project if not rectified.

Examples:

Milestones are key project checkpoints that mark significant points within a project’s timeline. They help teams track and compare onsite progress by monitoring the completion of Visis that are lagging behind.

Parent Visis are Visis that have been created to a location. Child Visis are Visis created under an inspection. (This makes the inspection a Parent Visis.)

This concept allows a single inspection to house all the relevant information relating to that piece of work in one place, easily accessible and trackable. 'Child Visis' make up the body of work within a checklist.

Every Visi contains a set of metadata which is essentially just the information to describe what it is, who is assigned and how to close it out. Metadata is useful as it allows anything in Visibuild to be easily searchable for example: every Visi has a location field, this means that anything tagged with that location will be visible on the location page.

On the Web App, every Visi's metadata is located on the right side of the web page, hence the Sidebar. The Sidebar is also used to provide quick contextual information when sifting through multiple Visis, without the need of expanding/clicking into a Visi, to reveal its metadata (who its assigned to, what it is and what is the progress). Additional Visi actions can be done from the Sidebar such as changing the title & description, relocating, reassigning, exporting and archiving.

Completing an inspection in the Visibuild mobile app is easy with our Single Page Inspection Flow (SPIF), allowing you to complete all tasks within an inspection with a single scroll.

In the activity feed of every Visi, it displays an audit log of all the actions and comments that have occurred from creation to approval. You'll see reviews and changes to everything related to a Visi: due date, location, assignee, reviewer, title, and description.

The location tree is the backbone of your project setup in Visibuild and contains every location.

Every visi has a status to reflect its current state.

Open

All Visis begin with the status of “Open”. This means they are either not started yet or being worked on currently.

In progress

This status only applies to Inspections which have checklist items, once any item has been closed within the checklist the Inspection will move into In Progress until everything is complete and the inspection is closed.

Closed

A Visi that has been completed.

In review

If a Visi requires a review, it will first be flagged as “Ready for review” rather than closing it straight away. Once a Visi is set to ready for review the reviewer will be notified and they can check it and if they are happy click “Approve and close”.

N/A

Tasks within templated inspections can be set to N/A when the Task isn’t relevant and doesn’t need to be complete.

Can't Close

Mark Visi as Can't Close if it has not met the requirements necessary to close and provide a clear reason for the action.

The assignee is the person who is responsible for closing the Visi. You can assign yourself or others to Visis. If you create a visi and assign someone else, it will be visible in your “Assigned” tab on your home screen.

The person responsible for checking and approving the Visi before it can be closed out. If you wish to create a Visi and assign it to someone else to complete you can set yourself as the reviewer so that you can check the work and have final approval before it can be closed.

By assigning a company as a Viewer (at the parent inspection level), they will gain view only access to all nested Visis.

By assigning a company as a Viewer (to a task, issue or NCR), they will gain view only access to that single Visi.

A Visi is always Visible To its Creator, Assignee and Reviewer. If Company A gets added as a Viewer to the Visi, the Visi becomes Visible To the Creator, Assignee, Reviewer and Company A but only the Creator, Assignee and Reviewer can carry out actions.

The owning company of the project will also always have visibility to everything.