Navisworks Finds the clash. JAED manages what happens next.

From Clash Detection to Coordination.

JAED Collision Suite runs the whole coordination cycle from inside the tools you already use. Publish from Revit, pull every model into Navisworks, push the clashes with their trades, and run the meeting against the model - while the website keeps the record for coordinators, contractors and trade partners alike.

Explore the Platform Explore as Guest

Read-only sample project. No signup, no trial timer.

Project Dashboard · Coordination Health · Live

JAED Collision Suite project dashboard showing coordination health, unresolved and critical clash counts, the coordination progress pipeline, and project data

The Problem

The Clash Isn't the Problem. What happens after it is.

Navisworks already finds the clashes. Everything downstream is where coordination actually breaks down.

Navisworks detects the clash.
A report gets exported.
Screenshots get emailed.
People lose track of ownership.
Issues become outdated.
Meetings require manual preparation.
Nobody knows which version is current.

Old Workflow

Navisworks Export Email Screenshot Spreadsheet Meeting Follow-up Confusion

JAED Workflow

Navisworks JAED Assign Coordinate Resolve Verify Close

JAED keeps the coordination process connected from detection through resolution.

How It Works

One Cycle, Start to Finish.

Eight steps, one connected record. Nothing leaves the system as an attachment.

Publish

Each trade publishes from Revit into the cycle that is open.

Sync

Navisworks pulls every current model into the federated file.

Detect

Clashes are identified in Navisworks.

Push

Clash tests go to the project with their trades already on them.

Meet

Work the agenda in the model. Decision, owner and date recorded as agreed.

Resolve

Trade partners update the issue as coordination progresses.

Verify

Confirm the issue has actually been resolved.

Close

Close the cycle, keep the history, and start the next one.

Revit and Navisworks

The Whole Week, Without Leaving the Model.

Two plugins, one installer. Revit publishes into the open cycle; Navisworks adds a dock pane that keeps the federated file current, pushes the clashes, and runs the meeting against the model itself. No export step, no report to email, no screenshots.

Publish from Revit Update Models Push Clashes Run the Meeting Minutes Published

Publish from Revit

One button exports the active 3D view and uploads it into the open cycle - as the next revision of the model you already had there, with your discipline and company already on it.

Update Models

Every model anyone uploaded this cycle, downloaded beside your .nwf and swapped into the file in one click. Nobody chases anyone for the latest structural.

Push Clashes, With Their Trades

Tick the clash tests to send and choose the disciplines on each one. Every clash arrives already assigned to the trades that own it.

Run the Meeting

Work the agenda item by item with the model isolated on each clash. The decision, the owner and the due date are recorded as they are agreed - the minutes are finished when the meeting is.

Create Issue

Select a clash - or a native Clash Detective group - and create a linked web issue on the spot.

Viewpoints That Stay Behind

Capture the current viewport for an issue, or save the whole agenda as a folder of viewpoints in the .nwf - so the next meeting opens where this one finished.

Group Nearby Clashes

Forty clashes where one duct crosses one wall is one problem. Group them by proximity and write the groups back into Clash Detective.

Linked, Once

Sign in and link the file to its project once. The link lives on your computer, not in the shared .nwf, so it never changes a file your team opens.

Product Tour

Everything Your Coordination Team Needs.

Real screens from the running application.

Dashboard - coordination health, unresolved and critical clashes, overdue counts, coordination progress pipeline, and open clashes by trade

Coordination health Unresolved clashes Critical & overdue Coordination progress Open clashes by trade Recent activity

Click any screen to open it full size

Coordination Issues

Every Clash Becomes an Actionable Issue.

A clash should never become a forgotten screenshot. Every clash pushed into JAED carries the context needed to actually close it out.

Owner Organization Priority Status Due Date Comments Snapshots History Meeting Context

Clash Detail · Assignment & Status

A single clash open in JAED with trade, responsible user, priority, due date and status controls alongside the clash image

Meetings

Run the Meeting in the Model.

The agenda builds itself from what is critical, overdue or reopened. Then work it from the website or from inside Navisworks, where each item isolates in the model as you reach it - and every decision is recorded as it is made.

Critical, overdue, and hand-picked issues on the agenda
Every clash on screen, isolated, as it comes up
Decision, owner and due date agreed in the room, not after it
Attendees recorded by organization, minutes published to all of them

Coordination Meeting · Agenda

Timeline

Connect Coordination to the Project Schedule.

Import an existing construction schedule and track coordination progress alongside the project's own activities.

Model submissions and coordination milestones
Activity status computed from real dates
Week and month zoom on a Gantt-style view
Schedule report export

Coordination Timeline · Gantt

The Timeline tab showing schedule activities and coordination milestones on a Gantt-style view

Project Team

One Coordination Environment for the Entire Team.

Organizations sit above projects. Each firm sees only the projects and information it has actually been assigned.

Owner General Contractor BIM / VDC Architect Structural MEP Trade Contractors

Assigned access

Users belong to organizations, and organizations are assigned to projects. Nobody sees a project they were not put on.

Issues have owners

An issue can be assigned to a company and to a specific person inside it, so accountability is never ambiguous.

No Navisworks required

Trade partners work entirely in the browser. Only the machine running the clash session needs Navisworks.

Why JAED

Coordination That Stays Connected.

Navisworks Connected

Coordination stays attached to the tool where clashes are actually detected, instead of starting again in a spreadsheet.

Centralized

One location for issues, snapshots, meetings, timelines, reports, and files.

Accountability

Every issue has an owner, a status, a priority, and a full history of what changed and when.

No Stale Screenshots

Coordination information stays current instead of being trapped in an email attachment from three weeks ago.

Project Visibility

Project managers and coordination teams can see what is open, overdue, critical, or resolved at a glance.

Team Access

Bring trade partners into the coordination workflow without requiring everyone to run Navisworks.

Current Product

Available Today. Not a Roadmap.

Everything below is built and running in the application right now. Nothing on this page describes a feature that does not exist yet.

Coordination Issues Meetings Timeline Files Snapshots Reports & Exports Admin Console Coordination Matrix Navisworks Plugin Revit Plugin Model Sync Coordination Cycles Meeting Mode in Navisworks

Security

Access Controlled on the Server.

Permissions are enforced by the API, not hidden in the interface.

Server-side authorizationEvery request is authorized by the API. Hiding a control in the UI is never the access check.

Role-based permissionsAdmin, BIM Coordinator, Project Manager, General Contractor, Consultant, and a read-only Guest session.

Organization & project accessAn account only reaches the organizations and projects an Admin has assigned it to.

Audit loggingAccount, project, and data-management actions are recorded with who did what and when.

Secure password hashingPBKDF2 with a per-user salt, plus two-factor authentication.

Self-hosted deploymentRuns on infrastructure you control, with local storage. Nothing goes to a third party.

Who It's For

Built for Everyone at the Coordination Table.

BIM / VDC Coordinators

Run clash detection, push results, assign ownership, and verify that issues were actually resolved.

General Contractors

Monitor coordination progress, accountability, and how each trade is actually performing.

Trade Contractors

See the issues assigned to you and coordinate directly with the project team - no Navisworks seat needed.

Architects & Engineers

Review coordination issues raised against the design and provide direction where it is needed.

Project Managers

Track coordination status and project risk without asking someone to compile a report first.

FAQ

Questions People Actually Ask.

Do I need Navisworks installed to use the web app?

No. The web platform runs entirely in a browser. Navisworks is only needed on whichever machine is actually running the clash session and pushing it to the web.

How does a clash get into JAED?

Two ways. Push it live from the plugin's dock pane - "Push to Website" sends whatever Clash Detective is currently showing straight to the project's Clash Coordination tab. Or export a Clash Detective report from Navisworks and upload the HTML/zip file directly on the web app.

Can I use JAED without the Navisworks plugin?

Yes. The report-upload path needs no plugin at all, and everything downstream - assignment, comments, meetings, timeline, reports - works the same either way. The plugin removes the export/import step; it is not a requirement.

What happens when a clash report is updated?

Re-importing the same test replaces its clashes rather than duplicating them, and everything your team already did - status, assignment, priority, due date, comments, history - carries forward automatically, matched by each clash's own label. It is only lost if that label itself changes between imports.

Can I assign issues to different organizations?

Yes. An issue can be assigned to a responsible organization and to a specific person within it. Organizations sit above projects, so a firm only ever sees the projects it has been assigned to.

Can people access reports without an account?

Yes. Export the full clash list to CSV, generate a weekly HTML coordination report, or print a meeting's minutes - all shareable without giving that person a login.

What roles are available?

Admin, BIM Coordinator, Project Manager, General Contractor, Consultant, and a read-only Guest session. An Admin assigns each real account to the organizations and projects it should see.

How is project access controlled?

Every API request is authorized server-side against the caller's role and their organization/project assignments. Hiding a control in the interface is never what enforces access.

Where is the data stored?

On infrastructure you control - a self-hosted deployment with local storage. Nothing is sent to a third party.

Stop Managing Coordination Through Screenshots.

Connect Navisworks to a coordination workflow built for the entire project team.

Explore as Guest Log In