What is a federated model, and why as-built checks need one

A federated model is what you get when the separate discipline models, architectural, structural, mechanical, electrical, plumbing, get linked into one coordinated file without merging into a single master. Each trade keeps authoring in its own software: Revit for architecture, Tekla for steel, whatever the MEP team runs. The federated version is a live-linked assembly, usually opened in Navisworks or a similar viewer, where every discipline's geometry sits in the same coordinate space at the same time.
That's where most clash detection happens. A structural engineer checking a beam-to-duct conflict doesn't open the mechanical model directly. Someone opens the federated model and runs the clash test across all linked models at once. It's the closest thing the project has to "here's everything, together," even though no single file actually contains everything.
Model coordination vs as-built verification
These two activities get talked about like they're the same discipline. They're not.
Coordination happens before anything gets built. It catches design conflicts, a sprinkler main routed through a beam, a duct that clips a structural column, while the fix is still a model edit. That work lives entirely inside the federated model. Nothing physical exists yet to check against.
As-built verification happens after work is in the ground, in the walls, or on the roof. It checks whether the site matches the design, a question coordination never answers, because nothing physical exists yet when coordination runs. A slab can be poured exactly where the structural model says it should be and still conflict with where the MEP model routed a duct through that same zone. Coordination caught that clash on paper months earlier. Whether the field crew built to the coordinated version, or to an older structural issue without the latest MEP changes, is the question as-built checks exist to answer.
Why check against the federated model instead of one discipline's model
If an as-built comparison only checks captured site geometry against, say, the structural model, it can confirm a column line is right and still miss that a wall was framed a foot off from where the coordinated MEP routing needed it. Checking against the federated model means the comparison is measured against the full coordinated design intent, the version every trade was supposed to build to, not just one discipline's slice of it.
Timing matters here too. A federated model is a snapshot. If a trade pushed a change through late and the federated model didn't get rebuilt before the next site capture, the comparison is checking against stale coordination, not current intent. Keeping that reference current is part of why checking monthly works better than waiting for one survey at closeout: a deviation caught against last month's federated model, while the wall is still open, is a punch-list item. The same deviation found after drywall and finishes go up is a demo-and-rebuild.
What this means for a QA or owner's rep team
If your team is relying on a formal as-built survey at project close to catch a deviation, that survey is checking the finished building against the federated model as it existed at that moment, long after the trade that caused the gap has demobilized and the rework cost has gone way up. A monthly comparison against the same federated reference catches it while the crew responsible is still on site.
As-Built Compare registers a reconstructed site surface, built from monthly drone capture, against your design model and flags elements that have drifted out of tolerance, early enough that fixing it is still a change order and not a tear-out.
If your project runs on a coordinated federated model already, that's the reference worth checking the built site against before the next trade closes it up.