The Client Just Changed the Whole Layout. Your Coordination Is Already Out of Date.

When the Layout Moves, Every Trade Behind It Goes Stale

You spend nine days coordinating a floor. The client walks in, moves the core, adds two corridors, deletes a stair, and the plan you handed the trades Friday is now fiction. Nobody told you to recheck it. The layout changed, so every element sitting behind that layout changed too, and your coordination is a snapshot of a drawing that no longer exists.

A layout change is not one change. It is a chain. Walls move, so framing and finishes move. A corridor shifts, so the electrical rough-in, the sprinkler heads and the HVAC run all move with it. The plumbing stack that was comfortable against gridline C is now chasing a chase that is not there. One line on the architect's sketch becomes dozens of affected elements, and none of them updated themselves.

Here is the part that stings. You probably know the plan is stale before the client does. The coordinator knows because the model changed. The superintendent knows because the drawing set on the site trailer has revision clouds all over it. What nobody has is a current picture, so the trades keep working from the old layout, and you keep hoping the gap does not show up in the field.

This is the daily headache in AEC right now. Most firms run reviews in one tool, issues in another, and the model somewhere else entirely. The layout moves in the model. The issue list sits in a spreadsheet that still believes in the old drawing. The gap between those two is where schedule dies, and it dies quietly, usually two weeks later, in a meeting where someone asks about a clash you cannot explain.

BidLight keeps one live record of the project inside Revit and Navisworks. You publish from the model and every publish becomes a versioned snapshot. When the design changes, the record changes with it. That is the entire idea. The record rides on the same model the client is changing, so a layout move updates the picture instead of breaking it.

## Rechecking Is Not the Problem. Rechecking From Scratch Is

Coordinators are not slow because they are bad at their jobs. They are slow because a layout change forces a full re-review instead of a delta. You cannot just adjust one issue for the corridor move, because the corridor move also changed the ceiling height, the door count, and the length of the mechanical run feeding the new room. So someone opens the model, exports fresh views, pastes them into a deck, and starts hunting for the differences by hand.

That is the 15 minutes versus 90 problem. A model-driven comparison gives you the changed elements in about 15 minutes. A manual review cycle takes a 90-minute meeting on a good day, and on a bad day it takes a day and a half because two people are arguing about which revision they are working from. Multiply that by every design change between concept and construction, and you can see where the coordination hours go.

There is a second cost nobody puts on the status report. When rechecking takes too long, teams stop doing it. They tell themselves they will catch it in the field. Sometimes they do. Often the problem arrives as rework, and an unresolved clash can burn $15K to $50K a week in idle field labor. That is the quiet schedule leak: not a bad plan, just a plan with no record behind it.

When a client complains about a surprise, the loudest complaints usually trace back to a broken feedback loop, and coordination is no different. The client's complaint is not that the layout changed. It is that nobody told them what the change touched. Giving them the changed elements within the same meeting turns a complaint into a conversation. It also gives your team something to respond to that is not defensiveness. You are responding to a drawing, not an accusation.

If you remember only one thing about how this works, remember the record. One live record of the project inside Revit and Navisworks. A layout change moves geometry, geometry moves elements, elements carry the issues, and you get the new picture out of the same file the architect just edited.

## What a Defensible Answer Looks Like When the Room Is Watching

Walk into the design meeting with the model open and the record live. The architect slides the core 4 feet. You publish, and the comparison refreshes in minutes. The client asks what that move touched, and you have the answer while the marker is still in their hand. That moment does more for your reputation than any brochure.

Defensible does not mean complete. It means every statement traces to an element that traces to a revision you can point at. Any two revisions compare element by element, grouped by structural, MEP, envelope and interior. When a client challenges a line, you do not say the software said so. You show the element, the issue and the revision, then you talk about the scope of work.

That traceability is why coordination can become a service you bill for, not a favor you give away. Firms already do this with BIM: execution plans, 4D sequencing, fabrication detailing and spooling, done for you when the in-house bench is full. When you can hand a client a coordinated model at three design milestones, you are not just delivering work. You are selling the certainty they keep asking for, and you can put a fee on it.

Now think about the pattern underneath all of this. A team that measures progress by meetings held misses whether the project moved. A team that coordinates from a snapshot misses whether the plan still matches the building. In both cases the fix is the same: keep one live source of truth, watch what actually moved, and let the record follow the change instead of trailing it by two weeks. Automation here means watching the source instead of the copy.

The accountability piece closes the loop. The 6am digest tells every owner the issues they own, and the project view shows who is behind while there is still schedule to move work. A layout change stops being a surprise to the plumber on Monday, because he read it at 6am.

BidLight plans run from Basics at $260 per licence per year to Max at $590, with custom Enterprise pricing and unlimited projects on every plan. That is the cost of keeping the record live. The alternative is rechecking from scratch every time the layout moves, defending a picture you no longer believe, and watching a schedule slip in a meeting because the drawing changed and the log did not.

The client will change the layout again. They always do. Your job is not to stop them. Your job is to have the new picture in the same meeting, tied to the same model, and written down. One live record of the project inside Revit and Navisworks turns the change that used to break your coordination into the moment that shows you are ahead of it.