I sat in on a VR design review last month at a mid-size architecture firm in Melbourne. Five people wearing Quest 3 headsets, walking through a building that doesn’t exist yet, pointing at ceiling heights and asking whether the corridor felt too narrow. The senior architect reached up and literally moved a wall, then asked the client to walk through again.

That’s the promise, and increasingly it’s the reality. But it’s not as simple as “throw your BIM model into VR and you’re done.”

Why Architecture Firms Are Making the Switch

The traditional design review involves printed plans, maybe a 3D rendering on a big screen, and if the budget allows, a physical model made from cardboard, foam, or 3D-printed components. These have worked for decades. They still work. But they have a fundamental limitation: clients can’t experience space.

A floor plan tells you a room is 4 metres by 5 metres. A VR walkthrough lets you stand in that room and feel whether it’s generous or cramped. That’s a different kind of information, and it leads to better decisions earlier in the design process.

Autodesk’s research on VR in AEC workflows suggests that firms using immersive design reviews catch spatial issues 60% earlier than those relying on traditional methods. That sounds like marketing, but the underlying point rings true—you notice things at 1:1 scale that disappear on a screen.

The cost argument has shifted too. A decent physical model for a commercial project runs $5,000 to $20,000 depending on complexity. A VR setup with a few headsets and the right software costs roughly the same upfront but works for every project afterward. The per-project cost drops fast.

The Practical Setup

Most firms I’ve spoken with use one of three pipelines:

Revit to Enscape/Twinmotion to headset. This is the simplest path. You design in Revit (or ArchiCAD), export to a real-time rendering engine, and view in VR. The quality is good enough for spatial review, though materials and lighting won’t look photorealistic.

Unreal Engine pipeline. Higher quality output but more technical work. Firms with dedicated visualisation teams use this for important client presentations. The results look stunning, but building the VR scene takes days, not hours.

Web-based viewers. Tools like Shapespark and Modelo let you share VR-ready models via a link. The client doesn’t need software installed—just a browser and optionally a headset. Quality is lower, but accessibility is high.

The Melbourne firm I visited uses the Enscape route for internal reviews and shifts to Unreal for final client presentations on large projects. They told me the internal reviews are where VR adds the most value, because that’s when changes are cheap.

What Clients Actually Think

Here’s something I didn’t expect: clients generally love it, but they need guidance.

First-time VR users in a design review spend the first five minutes distracted by the technology itself. They’re looking at the controllers, testing what happens if they walk through a wall, marvelling at the headset. A good architect running a VR review accounts for this—they build in a warm-up period in a simple space before moving to the actual design.

Clients consistently notice things in VR that they miss on plans. The most common one? Window placement. People are surprisingly bad at imagining where windows will be relative to their eye height when they’re looking at a 2D elevation drawing. In VR, they look out a window and immediately say, “Can we make this bigger?” or “This faces the neighbour’s fence—can we move it?”

The firms seeing the best results from Team400 and similar AI-driven consultancies are starting to combine VR reviews with AI-generated design variations. Instead of showing the client one option, you show three, and they walk through each. The feedback loop tightens significantly.

The Hesitation

Not every firm is jumping in, and some of the reasons are legitimate.

Learning curve. Someone has to manage the VR setup, troubleshoot headsets, and ensure the model exports correctly. That’s a role that didn’t exist before.

Client demographics. If your typical client is a 65-year-old property developer who’s never worn a headset, the technology can be a barrier rather than a bridge. Several firms told me they keep physical models available as a fallback.

File management. VR-ready models are large. They need to be maintained alongside the working BIM model, and keeping them in sync as the design evolves requires discipline.

Motion comfort. Some people get uncomfortable in VR within minutes. A design review that makes the client queasy isn’t a good design review. Teleportation-based movement helps, but it’s not perfect.

Where This Is Heading

The direction is clear even if the timeline isn’t. IrisVR (now part of The Wild) and similar platforms are making the Revit-to-VR pipeline smoother every quarter. Apple’s push into spatial computing with Vision Pro is adding mainstream awareness. And as headset displays improve—particularly with passthrough mixed reality—the “put on a headset and look at your house” experience will keep getting more convincing.

The firms that adopted VR reviews early aren’t going back to cardboard. But they’ll also tell you it took six months to work out the right process, and they still print drawings for construction documentation. VR is a design tool, not a replacement for everything else.

The question for most architecture practices isn’t whether to adopt VR—it’s when, and which projects justify the overhead. For anything involving spatial decisions that affect user experience, it’s increasingly hard to argue against it.