What do you like best about Revizto?
More than anything else, Revizto succeeds at being a digital collaboration hub. Centered on the model as the basis for collecting communication in one platform, Revizto succeeds at gamifying issue tracking, model review, clash coordination, constructability review, and general collaborative workflows in a visual-forward, lightweight platform. From early integration with the Revizto team, client needs were their primary focus and added feature/tool implementation was lightning fast compared to more pedestrian competitors in the same space. They are driven to compete in an AI-heavy world, as well as stay relevant in a world of open-source vibe-coded custom tools that seem to be around every corner. They stick to a confidently proclaimed purpose of tying different information together across 3D tools, 2D drawing storage tools, for integrations that just work--staying out of weeds where they know their time may be wasted or ineffectual. The tool being lightweight allows for hosting projects of various sizes from small K-12 education renovations, complex mission critical mega projects, and intricate new-build hospital towers while remaining accessible to project field staff and superintendents that aren't always running the most capable hardware on their construction trailer wifi. Our unique relationship with Revizto makes the pricing and ROI a no-brainer, allowing us to cover licensing for trade partners, design teams, clients, vendors, and beyond to make sure everyone can take part in a centralized collaboration workflow to successfully deliver our projects. Review collected by and hosted on G2.com.
What do you dislike about Revizto?
All of the following should be taken with a grain of salt, because Revizto is still one of the most consistent tools out there: it’s simple, has a low barrier to entry, and works across desktop, web, and mobile. That said, in a world where vibe-coding and enterprise-specific or internal tools seem to be on the verge of taking over, it doesn’t feel like Revizto is moving quickly enough.
Their 2D tools fall significantly behind the competition, and the roadmap for rolling out features feels long—mostly just to catch up to where others were two years ago. I also see a gap in how Revizto is building out the data analytics side: it looks like it will rely heavily on our team creating custom integrations and dashboards. Some of that is clearly by design, since it allows teams to manipulate and use data as needed, but it still leaves a lot on the customer.
I can see Revizto becoming more capable as a Solibri-type tool with powerful analysis capabilities if it were pushed in the right places. The industry needs that from any tool that claims to support constructability reviews and model clash coordination.
Since the Premium User Group in 2024, I’ve been pushing the Revizto team to permission out their tool so certain users—likely by company—can view or edit specific portions without affecting others. The current project-wide roles don’t work for mega-projects trying to establish collaborative workflows. More often than not, someone ends up spending too much time QC-ing project appearance and search set settings just to make sure they aren’t edited or removed by others. The seemingly easy answer to those accidentally changing things is to edit the project roles available on your license, but that doesn’t work when you’re trying to maintain standards across an entire company operating across North America and across a variety of project types. At that point, project-specific permissions by company or role becomes the next step. More carefully permissioned and folder-capable tools are now on the roadmap, but again, it feels like it’s taking a long time to get there.
Allowing for non-hosted issues also seems like a no-brainer for action items from meetings, or for higher-level project issues that don’t belong on a specific drawing sheet or in a particular area of the model.
The web browser experience has become what I’ll bluntly describe as a sandbox for only certain features, and it doesn’t function smoothly or quickly enough to send partners to for reviewing issues (outside of very important license/user/project administrative tools). Again, in an age of vibe-coding, having a lightweight 3D Viewer in the web browser that’s also capable of 2D sheet viewing isn’t just a nice-to-have—it’s necessary to compete. It’s astonishing to me that we’re still forced to have people download the desktop app when it should be possible for project leads to create specific model presets for quick coordination and viewing in the web browser. Because other commonly used tools in the industry have mastered this, we often run into project partners wrongfully using those other tools for coordination, when Revizto needs to be the place where we make decisions based on the model and 2D drawings.
More generally, things feel too manual inside Revizto. For folks used to BIM/VDC software, this has never been a major issue, but there should be more in-tool help functionality and more ability to follow and/or prescribe certain workflows or “Preferences” selections depending on which user is in the tool. There are too many items that require constant explanation and training—for example, the Load/Unload Models tool (to make sure people are seeing the right models), making sure your appearance template is locked in the issue tracker to prevent constant load times when moving from issue to issue in 3D, and issues with IFC model element property continuity, to name a few.
Lastly, there is little to no oversight for project management to clearly report which version of the model we’re seeing and what workflows are built for clash. Custom company/project-specific matrices built in Excel have become a standard way for us to wrap our heads around clash setup, when it seems like a no-brainer to have a clash-structure matrix that tells you exactly what was included in your latest clash test and from which model (this was reported to Revizto for feedback in 2022 by our team). Overall, the tool leaves these kinds of project standards and visuals up to project leads, when I would hope that standards built in Revizto (Appearances, Search Sets, Clashes) could show quick visuals of what data they’re using for their individual processes—for example, which models are feeding into search sets, which models/elements/search sets feed into a clash, and which search sets/models feed into an appearance template. Review collected by and hosted on G2.com.
