
The issues that survive clash detection and still cause field problems are usually the ones that only register at eye level: a tight equipment corridor, a maintenance clearance that looks fine on a flat screen. Reviewing those conditions spatially and logging them directly into your Revizto issue tracker, without any manual re-entry, is what this workflow makes possible.
TLDR:
- Revizto's built-in VR feature requires a PC tether and has not been updated in roughly a decade.
- Field rework costs 5% to 15% of total project costs; catching issues in the model before they reach the field is what Revizto's issue tracking targets.
- Two-way sync between VR and Revizto pushes annotations with spatial pins and screenshots, pulling existing issues back into the session with no manual re-entry.
- Conditions that pass automated clash detection, tight maintenance clearances, congested corridors, blocked access panels, only register as problems when reviewed at human scale.
- Resolve connects Revizto's issue log to wireless, untethered VR review on standalone headsets, with the same issue list accessible to browser and iPad participants in the same session.
What Revizto Does in BIM Coordination
Revizto sits at the coordination layer of most complex construction projects, giving VDC teams a shared environment to review models, log issues, and track resolution across disciplines. Teams use it to manage clash coordination and issue workflows without bouncing between disconnected spreadsheets, emails, and PDFs.
That issue log matters more than it might seem. According to Construction Industry Institute research, field rework can represent 5% to 15% of total project costs. On a large data center or hospital project, that range covers a substantial volume of rework that starts as a missed coordination issue sitting unresolved in someone's inbox. Catching problems in the model, before they reach the field, is what Revizto's issue-tracking workflow is designed to support.
Where Revizto's Built-In VR Feature Stands
Revizto does include a VR feature, but it has not seen meaningful updates in recent years. The experience requires a PC tether, which limits where and how teams can use it. Running a headset through a gaming PC means setting up hardware in a conference room, managing cable routing, and keeping non-technical stakeholders from tripping over the cord. That friction kills adoption before a review even starts.
The feature does not fit serious immersive review workflows, so teams that need them pair Revizto with purpose-built tools. It cannot carry the load of a full federated model walkthrough on wireless standalone hardware.
For teams already invested in Revizto's issue tracking, that creates a real problem. Coordination data lives in Revizto. Immersive review happens somewhere else. Without a connection between those two environments, issues found in VR get re-entered manually, a breakdown in BIM coordination, or they disappear from the coordination record entirely.
Why Issue Tracking and Immersive Review Belong Together
A spreadsheet issue number tells you something is wrong. It rarely tells you why, where, or what the surrounding conditions look like at installation height. Spatial context is what turns a record into something actionable, and traditional issue tracking strips that context out the moment the model closes.
The reverse problem is just as real. Immersive review without a connected issue log means findings exist only in someone's memory or a separate notes file. By the time those observations reach the coordination record, they are paraphrased, decontextualized, or gone.
When issue tracking and immersive review share the same data, the gap closes. An issue logged at the exact location in a federated model carries its spatial pin, the surrounding geometry, and a screenshot. Anyone who opens it later can go directly to that spot and see what the reviewer saw. That is a different class of coordination record than a text field with a grid coordinate attached.
For teams running a complex MEP coordination process, this matters most in the spaces hardest to read on a flat screen. Equipment access corridors, ceiling plenum configurations, maintenance clearances: these are the conditions that pass automated clash detection and still create field surprises. Reviewing them at human scale and logging findings in the same system the whole project team uses is how those surprises get caught before concrete is poured.
How Two-Way Issue Sync Works Between VR and Revizto
The sync runs in both directions. Issues found in VR get pushed into Revizto as stamp issues. Existing Revizto issues get pulled back into the VR session for in-context review. No manual re-entry required in either direction.
When you create an annotation in Resolve during a VR walkthrough, one click pushes it to Revizto. The record carries the issue text, a spatial pin at the exact model location, and a screenshot captured automatically at the moment of logging, all core to any solid BIM coordination clash detection workflow. The Revizto issue number cross-references back in Resolve so both records stay linked.
Pulling works the same way. Your existing Revizto issue log appears inside the VR app under its own tab in the Annotations panel. Click any issue and you teleport directly to its location in the model. No coordinates to look up, no hunting through geometry.
Project-level configuration takes a few minutes: select the target Revizto project, set a default issue type, and the sync is live. Standard licenses may not, so confirm with your Revizto admin before connecting the accounts. Once linked, project-level configuration takes a few minutes: select the target Revizto project, set a default issue type, and the sync is live.
What Gets Reviewed: Issues in Spatial Context
Clicking an issue in the Revizto tab teleports you to its exact coordinates in the federated model. You land at human scale, looking at the problem in context: the ductwork above, the adjacent conduit runs, the corridor width on either side. A grid reference on a flat screen cannot give you that.
The issues worth reviewing this way are rarely the ones automated detection catches. A maintenance panel that is technically clash-free but surrounded by installed equipment on three sides. A corridor that measures code-compliant on paper but feels impassable at eye level: exactly the scenarios where BIM review in VR coordination adds the most value. Clearances around electrical gear that only register as dangerously tight when someone is standing in front of them. These conditions survive a coordination log without a flag, then surface during installation.
With Revizto issues loaded into the session, reviewers work through a punch list spatially. A superintendent in a headset and a trade partner on a browser can look at the same issue together, in place, without either needing to describe what they are seeing.
Setting Up the Revizto and VR Integration
Getting connected takes a few minutes once the prerequisites are confirmed.
Start by verifying that your Revizto license includes API access. Standard licenses sometimes exclude it, so check with your Revizto admin before anything else. Without API access, the sync will not function.
Once confirmed, the steps are:
- Generate an access code from the Resolve Integrations page and link your Revizto account
- At the project level, open Annotation panel settings and turn on the Revizto issue integration
- Select the target Revizto project from the dropdown
- Set a default issue type, such as "Standard"
The user connecting the accounts also needs "create and view issues" permission inside the target Revizto project. Without that, pushes will fail silently on the Revizto side.
After setup, Revizto issues appear in the VR app under the Annotations panel, and any annotation pushed from Resolve lands in Revizto with its spatial pin and screenshot attached.
Who Participates in a Revizto VR Review
VR headset, web browser, iPad. All three connect to the same live session, with the active Revizto issue log visible alongside the federated model, a practical application of BIM virtual reality review.
| Access Point | Typical Participant | Hardware Required | BIM Training Required | Can Teleport to Issue Location |
|---|---|---|---|---|
| VR Headset | VDC coordinator, superintendent | Standalone Meta Quest (no PC tether) | No | Yes |
| Web Browser | Trade partners, project managers | Any computer, no download required | No | Yes |
| iPad | Field lead | iPad | No | Yes |
The VDC coordinator or superintendent typically leads from the headset, moving through the model and calling out issues spatially. Trade partners and project managers join on a browser with no download required. A field lead on an iPad can follow the headset user's perspective in real time or break off to review a separate area independently.
That access model matters because the most useful feedback in a Revizto issue review often comes from people outside BIM. A superintendent recognizes an access problem because they have built spaces like it before. A facilities manager flags a maintenance concern because they will eventually own it. Getting those people into the session, without asking them to install software or learn a coordination tool, keeps participation rates high enough for the review to be worth running.
Resolve's Role in the Revizto VR Workflow
Resolve is the piece that makes wireless, untethered VR review work alongside Revizto's issue log. The Wellington Engine runs full federated models on standalone Meta Quest headsets with no PC tether and no model downsizing. That is the hardware gap Revizto's built-in VR feature never closed.
The Revizto integration runs through two access points: the VR app and the browser-based Lightning Viewer. Issues appear in the same tabbed Annotations panel in both, with teleport-to-location navigation in each. A superintendent in a headset and a project manager on a browser are reviewing projects together in real time, looking at the same Revizto issue list, in the same model, at the same time.
Resolve has supported over $50 billion in construction projects and more than 6 GW in data center portfolios. Those review sessions include VDC coordinators, trade partners, superintendents, and facilities staff, all connected without needing BIM expertise to participate. Revizto holds the issue record. Resolve puts everyone inside it.
Final Thoughts on Making Revizto VR Work for Your Team
Revizto's issue tracking does its job well. The VR piece just never caught up, and for years that left a real gap in how teams could review coordination spatially. Connecting a wireless VR workflow back to your Revizto issues closes that gap without adding a separate system to manage. Book a demo to walk through the setup.
FAQ
Can I review Revizto issues in VR without re-entering them manually in a separate system?
Yes. The Resolve and Revizto integration syncs in both directions, so issues found during a VR walkthrough push directly into Revizto as stamp issues, and your existing Revizto issue log pulls into the VR session for in-context review. No manual re-entry in either direction. The one prerequisite: your Revizto license must include API access, so confirm that with your Revizto admin before connecting the accounts.
What software should my construction team use to review 3D models on iPad, web, and VR together?
Resolve connects all three access points to the same live session. A superintendent leads from a Meta Quest headset, trade partners join on a browser with no download required, and a field lead follows on iPad. All three see the same federated model and the same active issue log at the same time. No BIM training required to participate from any device.
How does Resolve handle large federated models on wireless VR headsets without a PC tether?
Resolve runs full federated models on standalone Meta Quest headsets using the Wellington Engine, a proprietary display system built in C++ that uses virtualized geometry and custom occlusion culling. No gaming PC, no cable routing, no downsized model files. That is the hardware gap Revizto's built-in VR feature never closed; it still requires a PC tether.
What kinds of construction issues does Revizto VR review catch that automated clash detection misses?
Clash detection answers whether two objects intersect. It does not flag a valve on a congested catwalk that is clear on plan but unreachable once adjacent equipment is installed. Reviewing those conditions at human scale, with Revizto issues loaded into the session, is how those problems get caught before installation. A superintendent in a headset recognizes access and sequencing problems because they have built spaces like it before. That judgment does not show up in a clash report.
How do I set up the Revizto integration in Resolve?
Confirm your Revizto license includes API access, then generate an access code from the Resolve Integrations page and link your Revizto account. At the project level, open Annotation panel settings, turn on the Revizto issue integration, select the target Revizto project, and set a default issue type. The user connecting the accounts also needs "create and view issues" permission inside the target Revizto project. After that, Revizto issues appear in the Annotations panel in both the VR app and the browser viewer, with teleport-to-location navigation in each.
