1. Get an account. An administrator either creates one for you or sends an invitation by email. Open the link in the invitation to set your password; invitations expire after 7 days.
2. Sign in with your username, your password and the code from your authenticator app.
3. Set up two-factor authentication. It is required on every account. The first time you sign in you'll be asked to scan a QR code with an authenticator app. Keep the backup codes it gives you somewhere safe — they get you in if you lose your phone.

Forgot your password? Choose Forgot password? in the sign-in window and use Send reset link to get a reset email.

Just looking? Explore as Guest opens a read-only sample project, with no account needed.

Everything is reached from the two bars across the top of the page. Your role decides which items you see, so some of these may not appear for you.

Jumping anywhere. Press Ctrl + K (⌘ + K on a Mac) to jump to any area, switch project, or open a clash test by name.

What you can do depends on your role, and it's enforced by the website itself rather than just hidden from view.

Someone can have a different role inside a particular organization: on the Admin page, open the organization's members and change their role there — it starts as “Same as account role”. An administrator can also limit someone to a single trade, so they see only that trade's clashes, on every project.

The order a project normally follows. Steps marked with a role are for that role; everyone else can follow along.

1. Start a cycle in Files. coordinators Everything from here on — clashes, models, meetings — is stamped with it automatically.
2. Bring the clashes in. Push them from Navisworks with the JAED plugin, or import a Navisworks clash report in Clashes.
3. Triage them in Clashes: assign each to a person and organization, set priority and due dates, and group related clashes.
4. Track them. Every clash is tracked from the moment it arrives. It gets a permanent number, like CLH-0042, that stays with it through every later push. Give it a due date and whoever it's assigned to is reminded as the date approaches and again if it passes.
5. Meet about them. coordinators Create a meeting, generate its agenda from what's outstanding, then run it item by item and publish the minutes.
6. Resolve and verify. Whoever did the work marks it Resolved; a coordinator checks it and marks it Verified, then Closed.
7. Close the cycle coordinators and start the next one. Anything still open carries forward.

The banner at the top shows the latest push or upload; Review new lists the clashes it added. Pick a clash test below it, then work through the table: each row shows the clash number, the two elements and where they meet, who is responsible, priority, status, due date and how many comments it has. Click a column heading to sort.

Finding clashes

Search by number, element, location or owner. Critical & overdue and Assigned to me narrow the list in one click; + Filter picks by status, level, organization, priority, person, due date, trade, grid, area or group. Each filter shows as a pill you can remove.

Changing many at once

Tick clashes, then Assign, Set priority or Add to agenda coordinators; More sets status, due date, trade, area or group. Export CSV exports what you ticked, or every clash if nothing is.

A clash's page

Opening a clash shows its report image (click it to zoom), the Navisworks data, snapshots, and its full history. On the right: who is responsible, priority and due date — click one to change it — the status and Advance status, and the meetings and RFI linked to it. Coordinators raise an RFI from here. The discussion is at the bottom; untick Notify the responsible organization to tell only people already in the thread. The page has its own address, so you can send someone a link to it.

Verifying on site

coordinators Verify on site at the top of Clashes (or V) opens a screen made for a tablet: one Resolved clash at a time, from every clash test, in the order you'd walk the building — level by level, longest waiting first. It shows the clash image, where it is, who fixed it and when. Choose Built as coordinated — close it to verify and close the clash, or Not as coordinated — reopen to send it back; its owner is told. A site photo and a note can go with either: the photo is saved to Snapshots on that clash, and your decision is written into its discussion. Skip for now moves on without changing anything. A clash's own page also has Verify it on site once it is Resolved.

Importing

BIM Coordinators and Admins use Upload report in the banner to import a Navisworks clash report, or grid locations only, which tells the website where each clash sits on the building grid.

Every clash follows the same lifecycle. When someone else changes the status of a clash assigned to you, you're told.

Almost any change of status is allowed. Three are refused, because they would make the record untrue — and the message tells you what to do instead:

• Verified only from Resolved. There has to be a fix to sign off.
• Reopened only from finished work. Something has to have been finished to reopen it.
• Finished work goes back through Reopened. A resolved or closed clash can't jump straight back to In Progress; marking it Reopened first is what keeps the reopen count honest.

Day counts

The website keeps how long each clash has been open, how long it has waited for a response, how long it has waited for sign-off, and how long it took to resolve. Age stops when a clash closes. A blank figure means not tracked yet, which is different from zero.

No separate issues

Every clash is tracked from the moment it arrives, so there is no separate Issues page. Requests for Information are raised from a clash's page and listed under Report.

A cycle is one round of coordination, between one model drop and the next, and it is run from Files. Pick a cycle there, then Details and compare for its figures — counted from the clashes first found while it was open — its history, and a comparison with any other cycle: new work against work carried over, and how quickly things got resolved. The current cycle, and how long until it closes, also shows under the project name at the top of every page.

Coordinators start a cycle with Start cycle and move it through its stages — Planning, Model Collection, Coordination, Review, Closeout — and then close it. Closing freezes the cycle's figures, so later changes can't rewrite what it reported; reopening makes them live again. A cycle started by mistake can be deleted while nothing has been recorded against it.

The Meetings page lists every meeting on the left and opens the next one coming up. The middle shows its agenda: each item's clash, what was decided and the action item with its owner and due date. Attendees and notes are on the right, and the project's action items from every meeting are underneath.

Coordinators start one with New meeting. Generate from clashes shows what it would add before adding it:

• clashes that are overdue, reopened, still being worked at critical or high priority, or due before this meeting
• action items still outstanding from earlier meetings

Running it again only adds what's new; Add item puts any other clash on. Click an item to record its outcome. If two people edit the notes at once, the website tells you someone else saved first rather than overwriting their work.

Running the meeting

Run meeting coordinators shows the agenda one item at a time, in type large enough to read across a room, starting at the first item not yet discussed. Type the decision and action item, pick the owner and due date, and press Record and next (or Ctrl+Enter). Defer moves on without recording. When every item has a decision, Publish minutes tells each attendee. Print minutes opens the printable version.

Your account

Choose your name at the top right, then Account settings: a row each for your picture, profile, email, password, two-factor authentication and notifications — click a row to open it. Turning two-factor off asks for your password, and you'll be asked to set it up again before you can carry on.

Notifications appear under the bell at the top. Choose which you get: My assigned work (anything assigned to you is created, reassigned, changes status, priority or due date, or is coming due or overdue), Comments on things you're involved in, Meetings being scheduled, starting soon or having their minutes published, and Project updates (models uploaded or going stale, new clash tests, verification requests, the weekly report).

Plugin App Password — you don't need this. It's an older way for the plugins to sign in; both now use your normal password and authenticator code. Leave it unset.

• Navisworks Manage 2026. The plugin supports 2026 only, and clash results come from Clash Detective.
• A Collision Suite account — the same one you use on the website.
• An authenticator app set up on that account. Two-factor sign-in is required.
• Access to the project on the website. Ask your coordinator if you can't see it.
• Your coordination file saved as .nwf. Model sync refreshes the models an .nwf references; a published .nwd has them baked in, so it can't be refreshed.
• Clash tests set up in Clash Detective for the file you're coordinating.

1. Download the installer. Sign in to the website and open Downloads. The downloads aren't available to guest sessions.
2. Run the installer. Open jaed-collision-suite.msi. It installs for your own Windows account.
3. If Windows warns you, it may show Windows protected your PC, because the installer isn't code-signed. Choose More info then Run anyway.
4. Start Navisworks. If it was already open, restart it. A Collision Suite tab appears on the ribbon.

The same installer also contains the Collision Suite add-in for Revit 2020 through 2026.

Every ribbon button is a shortcut to something that also lives in the panel. Shortcuts stay quiet when they work; if something goes wrong, they open the panel so you can see why.

The panel opens on the project this file is linked to, with the open cycle beneath it, and six sections across the top.

Two things, once each: sign in, then tell the plugin which project this file belongs to.

1. Sign in. Click Collision Suite on the ribbon and enter:
   • Website — the Collision Suite site address
   • Username and Password — your website account
   • Authenticator code — the current code from your authenticator app
   You only do this once. The plugin keeps your session encrypted on this computer and never stores your password. What you're allowed to do comes from your role on the website: change a role there, and the plugin follows.
2. Link the file to a project. Click the project at the top of the panel — or Project on the ribbon — and choose it. The file must already be saved.

   The link is remembered for that file, so you won't be asked again. It's stored on your computer rather than inside the model, which means linking never changes a file your team shares. If you move or rename the file, just link it again.

1. Update the models. Open the file and the panel says what changed: 3 updated models for Cycle 14. Click Update models. Each changed model is downloaded into a JAED Models folder beside the file, swapped in, and the file refreshed; models that are new to the file are appended. Models nobody has touched are left alone.
2. Save the file if models were added — the panel asks, with a Save file button, because an appended model is only in the file once it's saved.
3. Run your clash tests in Clash Detective as you normally would.
4. Pick the trades, then push. On Push, tick the tests to send and pick which trades each test's clashes belong to — a duct-versus-beam test is Mechanical and Structural. The website assigns every clash in that test to those trades, so nobody has to sort them by hand afterwards. Your choice is remembered per project and test for next week.
5. Run the meeting in the model. When the coordination meeting comes round, open Meeting and work the agenda from here: each clash is isolated on screen as you reach it, and what the room decides is recorded as it's agreed. Section 07 covers it.
6. Coordinate on the website. The team assigns, comments and sets status between meetings. Run the tests again later and push again — each clash keeps its issue number, status, comments and history.

What Update models actually does, and what it never does.

• Each model keeps one file name in JAED Models for the life of the project, so the file's reference to it never changes — even if the model is renamed on the website.
• Downloads resume where they left off, and each one is checked against the website's copy before it's used. A model that fails the check is discarded rather than loaded.
• An interrupted update is safe to run again: what finished is kept, and only what's still behind is fetched.
• Nothing is deleted. A model removed from the website stays in your folder and in your file until you take it out yourself.

The agenda is the website's — the same meeting, the same items, the same record. What happens here is the walkthrough, because this is where the model is. A clash everyone can see is a clash everyone can decide about.

1. Open the meeting. Run Meeting on the ribbon, or the Meeting section of the panel, lists the project's meetings newest first with how many items each has and how many are covered. Click Open on the one being held. Meetings are created and their agendas built on the website; the panel runs them.
2. Work the agenda. The panel opens on the first item nobody has covered yet. Show in model selects the clash, frames the camera on it and — with Isolate ticked — hides everything else, so the room is looking at two elements instead of the whole federated model. Show everything puts it all back.
3. Record what was decided. Type the decision and the action item, pick the owner from the people at the meeting, and set a due date with 1 week, 2 weeks or 1 month. Record and next saves it and moves to the next item nobody has covered — the owner is told, and the action item appears on the website straight away.
4. Publish the minutes when the agenda is covered. Everyone who was recorded as attending is told, except you.

Open Settings from the gear at the top of the panel.

The dot beside the project name is the connection; the line along the bottom is the file.