Pilot job, run as a client job

Private project

A multi-storey building, basement to 7th floor, in three discipline models. The office ran the full chain: model audit, federation, clash detection, quantities, 4D readiness, documents, QA and a client report.

  • Clash detection
  • Root causes
  • Quantities
  • 4D readiness
  • ISO 19650

Names, drawings and locations are withheld. Every figure on this page comes from the delivered files.

Diagram of the clash results by level, not the model itself.
Building
Basement to 7th floor
Disciplines
Architecture · Structure · MEP
Software
Revit · Navisworks Manage
Dates
12 to 16 Nov 2026
Jobs
14 jobs · 7 agents
Type
Pilot job, run as a client job

Human team Engineer's estimate

3 weeks

About 15 working days, office hours only.

Coordify agents Measured

2 h 35 min

24/7The full chain ran on a Sunday night, from 00:04 to 02:06.

Human time is our engineer's estimate for a manual team on the same scope. Agent time is the measured job time: the full chain (2 h 01 min) plus a re-run to save the report (34 min). Both come before the engineer's own review and sign-off.

  • 221raw clashes found
  • 112issue groups
  • 92decisions to make
  • 20critical issues
  • 12root causes
  • 38BOQ lines

Clash detection

221 clashes. 92 decisions.

A list of 221 clashes helps nobody on site. The office filtered the noise, grouped clashes that are the same problem, and folded repeats, so the team gets the number of decisions that really have to be made.

  1. 221
    Raw clashesFive hard clash tests across Structure, Architecture, HVAC and drainage.
  2. 220
    After the noise filterOne result below tolerance was dropped.
  3. 112
    Issue groupsClashes that are the same problem are grouped into one issue.
  4. 92
    DecisionsIssues that repeat on several levels are folded: solve once, apply everywhere.

By priority

  • Critical20issues · 49 clashes
  • High48issues · 72 clashes
  • Medium14issues · 51 clashes
  • Low30issues · 48 clashes

Issues by level

  • 7th floor4
  • 6th floor0
  • 5th floor11
  • 4th floor8
  • 3rd floor8
  • 2nd floor12
  • 1st floor69
  • Mezzanine0
  • Basement0

Most critical issues sit on the same vertical riser strips, repeated from the 1st to the 7th floor.

The catch

36% of the first-round clashes were not real.

The MEP model carried 138 copies of architectural elements with the same Revit IDs as the architecture model. In the first round they caused 126 of 349 clashes. The office scoped every test to its own model, ran it again, and flagged the copies for the MEP author to remove instead of sending noise to site.

The copied floors, 6,858.77 m², were also held out of the quantities, so nothing is priced twice.

36%126 / 349
  • 87walls
  • 34doors
  • 7curtain panels
  • 6floors
  • 4windows

Root causes

Root causes, not just clash lists.

12 root causes explain the results. One of them covers 75 issues and 139 clashes: service penetrations through the slabs are not modelled. That is one action, a penetration schedule sent to the structural engineer before the pour, instead of 139 separate comments.

139clashes, one cause, one action: a penetration schedule

Six work packages, in order

  1. PQ-01 Service penetrations to verify, 6 levels 75 issues · 139 clashes
  2. PQ-02 Structure × HVAC repeated on 6 levels 6 issues · 12 clashes
  3. PQ-03 Architecture × HVAC repeated on 4 levels 5 issues · 9 clashes
  4. PQ-04 Structure × HVAC repeated on 5 levels 5 issues · 5 clashes
  5. PQ-05 Architecture × HVAC repeated on 4 levels 4 issues · 8 clashes
  6. PQ-06 Architecture × HVAC on the 1st floor, one meeting 7 issues · 7 clashes

Who did what

Seven agents. One engineer.

  1. 01Director

    Read the brief, split it into tasks, handed each one to a specialist and collected the files.

  2. 02BIM Coordinator

    Audited the Revit model read-only, federated the three models, ran the clash tests, grouped the results, found the root causes and wrote the clash register.

  3. 03Quantity Surveyor

    Built a 38-line draft BOQ from the model. Flagged 11 floors with a 1.02 m build-up (726.87 m³, 17.6% of the floor volume) for the architect to confirm.

  4. 04Planner

    Checked 4D readiness in TimeLiner: no programme yet, 26 search sets ready to link one, and a list of what is needed.

  5. 05BIM Information Manager

    Proposed an ISO 19650-2 naming pattern, checked 13 files against it and drafted the document register.

  6. 06QA/QC Checker

    Reviewed the work independently. Found three major defects in the first round; all three were fixed and verified. The final register and BOQ passed with comments.

  7. 07Report Writer

    Wrote the client coordination report from the specialists' files, marked DRAFT for the engineer's review and sign-off.

  8. The last word is the engineer's.

Rules held

What the office did not do.

  • The models were not changed.

    Only reading tools touched the models. Results were saved as new files, never over the originals.

  • No price was guessed.

    No price list was supplied, so all 38 BOQ lines wait for real rates. No total was invented.

  • Nothing went out unchecked.

    QA checked the specialists' work before the report was written, and the report waits for the engineer's signature.

Handed over

What the engineer received.

  • Coordination report

    Verdict, key figures, critical issues, root causes and open questions.

  • Clash register

    112 issue groups with level, location, owner and work package (CSV and report).

  • Draft BOQ

    38 lines with quantities from the model, held duplicates and open questions.

  • 4D readiness note

    What TimeLiner holds, what the model offers and what is missing.

  • Document register

    ISO 19650 naming check and suggested names for every file.

  • QA records

    Independent checks of the register and the BOQ, with every comment listed.

  • Federated model

    Navisworks model with the final clash tests, saved as a new file.

  • Model check

    Read-only audit of the Revit model: project information, levels, views, sheets and warnings.

Your project
could be next.

Tell us about the model and the deadline. An engineer reviews the scope, not a bot.

ENGINEER APPROVED • AI AGENTS FOR BIM COORDINATION •