When a Trade's Model Doesn't Match the Design Model

You have been there. The design model is current, the trades have been working for weeks, and then a trade's model lands in the federated set with geometry that makes you squint. Columns in the wrong grid cell. A duct run that ignores the new ceiling height. It is not usually carelessness. More often it is a scope gap, a stale reference or a different read of the drawings. Whatever the cause, you need to catch it before anyone fabricates.

The trouble is, you have no quick way to prove it. Comparing the two models by eye is slow and just as prone to error. Running it again takes days. Meanwhile, the fabrication deadline looms and the trade is calling. So you accept the model, hoping the gap sorts itself out. It will not. It becomes rework, and rework on site is the expensive kind.

Say a trade's steel model shows one set of columns and the design model shows another. If you do not catch it, the shop drawings go out wrong, the steel arrives and a crew stands around. That is not a story about a careless trade. It is about a mismatch that takes weeks to surface.

The real issue is not anyone's intent. It is the lack of a quick, reliable comparison. You need a record that reads straight from the model, one you can trust enough to challenge a trade's submission on the spot. That is the baseline you have been missing.

BidLight gives you that baseline. It runs inside Revit and Navisworks, publishes each export as a versioned snapshot, and compares any two revisions element by element. When a trade's model does not align with the design model, you see exactly where, not after the shop drawings are issued.

Why Models Drift, and What It Costs You

Models drift apart for a few reasons. Sometimes a trade works from an outdated set of drawings. Other times they interpret a detail differently, say, a wall assembly two inches thinner than the one specified, so their layout shifts. Or they miss an entire element, like fireproofing on steel beams, because it is not obvious in the 2D plan.

Each drift carries a cost. A misplaced run means a clash in the field. A missing element means a change order later, and you pay a premium because the work is already in place. Either way, the schedule goes wrong. An unresolved clash can burn $15K to $50K a week in idle field labour.

A concrete example: a trade's steel model came in with 54 columns and 90 beams while the design model had 62 columns and 110 beams. The difference was 8 columns and 20 beams. The trade had worked from a memo from the architect's office that had been superseded three weeks earlier. They did not know. You would not either, unless you can compare quickly.

Checking is what BidLight automates. Compare the trade's revision against the design model's, and you see exactly where they diverge. Which elements are missing? Which moved? You ask pointed questions, not vague ones. That is the value.

And it is not just about the trade. It is about protecting your reputation. Deliver on schedule and clients remember. Do not, and they do not care whose fault it was. Your record needs to be bulletproof. BidLight gives you one you can defend.

How an Element-Level Check Gives You the Upper Hand

BidLight keeps every export as a versioned snapshot with its own files, author and milestone. The diff is grouped by category: structural, MEP, envelope, interior. So when a trade submits, you can compare not just the total but each element. Did the run move? Is a member missing? You see the nuances.

Here is how it works day to day. An electrical trade submits a model. You publish it and compare it against the last revision. You do not reject it outright. You dig into the differences. Maybe the trade added a backup generator you did not expect. Or they routed conduit through a space the structure no longer allows. You catch it and pin an issue on the element.

That process takes minutes, not days. About 15 minutes instead of a 90-minute meeting. If the design changed since the trade last updated, maybe you moved a wall or added outlets, the next publish shows it. You can notify the trade with an exact list of elements.

This shifts the power dynamic. You are no longer accepting a submission at face value. You are working from a detailed, current comparison that matches the actual models. That is the kind of confidence that keeps rework out of the field.

Turning a Headache into a Routine

Once the comparison is routine, you stop checking trade models one at a time in a panic. Pin an issue on the element, tag the trade, and the 6am digest puts it in front of them every morning until it is dealt with. You do not need a separate email thread.

Imagine telling a trade, "These twelve elements do not match, here is the sheet and revision each came from, and here is who owns each." You are not just coordinating; you are running a clean process. That is a different conversation, and it earns respect.

Beyond keeping the job on track, this saves you from the daily grind of chasing submissions. You spend fewer hours reconciling files. Teams lose about 11 hours a week working out which model version is current. That is time you can put back into the project.

The mistake some teams make is treating every submission as gospel because they lack the time to challenge it. BidLight removes that excuse. You get a record that is always current, so you act on a discrepancy the moment you see it.

And since BidLight lives inside Revit, it is not an extra step. Publish your model, and the comparison follows. You do not leave your design environment to get a check. That is what makes it practical enough to use on every submission.

When the Record Doesn't Lie: A Walkthrough

Consider a coordinator who received a masonry trade's model. The design model specified certain block courses and lintel sizes, but the trade's model showed a different lintel depth and extra block in one corner. The coordinator published both and compared them.

Instead of accepting the submission, the coordinator called the trade and walked through the differences. The trade had used a default lintel size two inches deeper than the drawings called for. The corner condition had been modeled twice. Each difference was pinned to its element and assigned.

The fixes went in as a new commit. Each issue closed with a screenshot, a tagged user and the model commit that delivered it. Nothing was ripped out on site. That builds trust, not just in the trade relationship but in the record itself.

This is not about being adversarial. It is about being informed. Most trades are competent; they just use different data. When you speak to specifics, elements, sheets, revisions, you lift the conversation from gut feel to precision.

And when the GC asks whether it is really fixed, you do not need a long answer. You point to the commit. A clash caught in the model costs about $50. The same clash found in the field costs $5,000 to $50,000.

Start Catching Mismatches Before They Cost You

The next time a trade model lands, do not just glance at it. Compare it against the design model. If you do not have a reliable way to compare, that is the gap BidLight fills.

BidLight is priced per licence, billed annually or monthly, starting with Basics at $260 a year ($30/month), and AIA members get discounts of up to 29%. Every plan includes unlimited projects. It is an affordable way to avoid rework and scope gaps.

You can also use done-for-you BIM services if you would rather have someone else run the model work. BidLight offers execution plans, 4D sequencing and fabrication detailing and spooling. That is a way to get the checks without building the in-house capability.

Ultimately, the goal is to own your record. When you can defend every closed issue, you stop worrying about whether a trade is building to the wrong version. You know, because you have the comparison.

So the next time a trade model does not match the design model, you can act. Question it, get it corrected and sign off with confidence. That is the difference between hoping something works out and knowing it will.