Naviate Builders Work Openings June release news 2026

This release news includes Naviate Builders Work Openings Beta version 2025 and 2026 v 26.0.0.

This release introduces the first beta of Naviate Builders Work Openings (Naviate BWO). This new collaborative solution helps multidisciplinary design teams define, plan and coordinate Builders Work Openings across the entire design lifecycle.

The solution replaces fragmented opening coordination typically handled through PDFs, email threads and isolated Revit files with a structured digital workflow shared between MEP, structural and architectural disciplines.

What is Naviate Bulders work openings

Naviate BWO provides a single, structured workflow for coordinating builders' work openings. MEP designers create openings in Revit, package them into deliveries, and publish them to a shared project space. Structural engineers, architects, and other consumers retrieve those deliveries, review each opening, set a status, add comments, and sync the results back — with full traceability of every decision.

The solution has two coordinated environments that share the same project data:

A Revit add-in (Naviate BWO) for authoring, consuming and managing openings inside your model.
A web application for project oversight, status visibility and user management.

The first beta release covers the complete round-trip workflow:

Connect an active Revit file to a BWO project.
Create and publish deliveries from PFV and Magicad opening data.
Consume deliveries from another discipline's perspective.
Set status, attach comments and record edits per opening request.
Sync changes back to the shared project space with full history.

Revit add-in (Naviate BWO)

The workflow for managing openings from Revit add-in contains the following function.

Connected Project - connect your Revit project with a web-based BWO project

Before any other Naviate BWO action, the active Revit file must be connected to a BWO project. Click Select Project in the ribbon and choose the project. The connected project name then appears in the read-only Connected Project field.

Create Delivery — the producer-side tool. Used to assemble openings from your model and publish them as a named delivery.

Once connected, use Create Delivery to start packaging openings. The tool scans the active model and surfaces all supported opening data — PFV families (Provision For Voids) and Magicad openings. Pick the openings you want to include, give the delivery a clear name and publish. The delivery becomes visible to other disciplines in the project's common space.

Delivery Manager — used by both producers and consumers. Lists every delivery in the connected project, lets you import a delivery (openings), review opening requests, set statuses, attach comments, record edits and sync back.

Every delivery in the connected project is shown with its name, owner, creation timestamp, and overall status. The Import button brings the selected delivery's openings into your active Revit model.

Openings — every opening request inside the selected delivery. Each row shows the IFC GUID, family, type, current status (as a colored badge) and a comment count. Single-click to select a request; double-click to zoom to it in the Revit view.
Changes — a date-sorted change log for the selected opening request, listing every edit (family type, position, dimension, …) with author and timestamp.
Sync — Sync pushes all your local status changes, comments and edits back to the shared database. The original delivery owner can then see the updated state of every opening request — in their own Revit add-in and in the web application.
A delivery is not a one-way export. It is a structured exchange between disciplines, persisted as data with a full history.

Four statuses for opening requests

Each opening request carries a status that reflects where it is in the review:

Pending — the default state when a delivery is first published; no consumer decision has been recorded yet.
Accepted — the opening is acceptable as proposed.
Conditional — approved, but only subject to specific conditions. A comment should describe what's required before full acceptance.
Rejected — the opening cannot be approved in its current form; the producer needs to redesign and republish.

There is also a fifth state: Orphan. This state is available only to the producer (the user who created the delivery) and is used when an opening request has been deleted. When the status is changed to orphan, the corresponding opening is removed from the Revit project.

The web BWO application

The Naviate BWO web application complements the Revit add-in by providing project-wide visibility for non-modeling stakeholders, including project managers, coordinators and reviewers.

The web application supports:

Creating new projects and inviting users:

Listing every delivery in a project with its status and ownership.
Open any opening request to view its basic information, current status, and comment thread.