Run multi-discipline coordination from one workspace

One place for the whole coordination picture

BIM Coordination Workspace treats modeling progress, open clashes, and sheet revisions as one connected loop — not three disconnected trackers — so a change in one is visible in the others and nothing slips between disciplines or spreadsheets.

It runs in your browser and keeps state locally; sign in and your projects sync to your account. Saves are conflict-aware, so two people working at once won't overwrite each other's changes.

Modeling, clashes, and sheeting — one continuous loop

Coordination isn't a checklist you finish — it's a loop you keep turning. Modeling feeds clash detection, resolved clashes reshape both the model and the drawings, and issued sheets send the next round of work back to modeling. The workspace keeps all three visible at once.

Modeling

Track what's modeled

Every discipline logs its packages and models in one shared list — each with its discipline, status, and a progress percentage — so the whole team can see what's been modeled and what's still outstanding without chasing anyone for an update. As models are issued and federated, they become the input for clash detection, which means coordination always runs against the current state of the building rather than a stale snapshot. Keep this list honest and the rest of the loop stays trustworthy.

Clashes

Resolve, with an owner and a due date

Every clash is recorded with a status, priority, assignee, and due date, plus a thread of comments and a full history — so the reasoning behind each decision stays attached to the issue instead of scattering across email and meetings. Filtering and sorting let a coordinator zero in on what's overdue or high-impact first. Resolving a clash rarely ends with the clash itself: it sends rework back to the model and changes what the drawings have to show, which is why clashes sit at the centre of the loop, driving both modeling and sheeting.

Sheeting

Keep sheets in step — then loop

Sheets and revisions are kept in step with the coordinated model, so the documents you issue actually reflect the decisions made during clash resolution rather than lagging a version behind. Each issued set becomes a checkpoint — it shows what's genuinely resolved and what's still open — and that feedback feeds straight back into the next round of modeling. That's what closes the loop: sheeting isn't the end of the line, it's the hand-off that starts the next cycle.

Capture clashes straight from Navisworks

Coordination starts in the model. Our Navisworks desktop plugin connects to your federated model, collects the clashes you run, and pushes them — with screenshots — into the workspace's Clashes view, so you're not re-keying anything by hand.

• Connects to your model. Runs inside Navisworks Manage and reads the federated model you're already coordinating.
• Collects clashes & screenshots. Capture a clash from the live viewpoint, with the snapshot that shows what's actually conflicting.
• Pushes into the workspace. Sends each clash into the Clashes view, ready to be assigned an owner, priority, and due date.
• One coordinated loop. The clashes you capture here feed straight into the dashboard, sheeting, and reports.

Download the plugin For Navisworks Manage · Windows

Built for real coordination work