The 60% Meeting: Answer What Changed on the Spot

The Question That Decides the Room

The owner just asked, "What changed since the last review?" and the whole room is waiting. Not the answer in three weeks after someone sorts the markups. The answer now, because the design is at 60% and that is the point the decisions turn on. You either answer or you say you will get back to them, and that second answer changes the temperature in the room.

You have been here. The architect has just walked through the plans. The engineer has flagged two beam conflicts. Someone from the owner's side points at an item from four months ago and asks why it is still open. If your answer is "we need to go back through the files," you have handed the room back to whoever can improvise a story first, and that person is almost never the one doing the work.

A coordination review in a large, multi-trade project runs into the same problem, only sharper. Models change daily. Trades work from different versions. A picture from a spreadsheet you exported last month is not one you can defend on a Tuesday. The fix is not a better spreadsheet. It is keeping the record on the model itself, so what you show is never older than the drawing you are looking at.

That is the whole idea behind BidLight. One live record of the project inside Revit and Navisworks. You publish from the model, and every publish becomes a versioned snapshot with its own files, author and milestone. When the design changes, the record moves with it. It is not a separate document you chase. It lives on the same model everyone in the room is pointing at.

At the 60% mark, this is the moment that matters. It is early enough that the owner can still change direction. It is late enough that the shape of the problems is real. It is the coordination meeting where a firm either looks like the one who understands the project or the one who needs another week. BidLight is built for the first version.

Why the Answer Is Never Ready When You Need It

Take an honest look at how most firms prepare for a review. Someone exports views from the model. Someone else drops them into a status deck. A third person checks the issue log against a spreadsheet that was refreshed maybe last month. The log might also carry owners that someone assigned two years ago and nobody has touched since.

By the time those three people finish, the design has moved. A wall shifted. A door type changed. A grid line moved six inches. Now the deck is stale before it is printed, and the only way to find out is to compare the model against the log line by line, which nobody has time to do before the review.

The result is the sentence every owner has heard. "We will have a status for you next week." It sounds careful. It is expensive, because in that week the trades keep building to what they know, and the owner keeps carrying doubts. The firm that answered first has already framed the conversation.

This is not about being fast for its own sake. It is about being current. A comparison that is fifteen minutes old and tied to the model you just showed is more defensible than a deck that is three weeks old and came from a log nobody can trace back to the drawing.

BidLight treats the record as a property of the model, not a downstream document. Any two revisions compare element by element, grouped by structural, MEP, envelope and interior. Issues pin to elements and carry the sheet and revision they came from. The picture on your screen at the 60% review is the picture the model supports, right then.

What Happens When a Door Moves Two Inches

A door moves two inches. That sounds small. It is not, because a door moving changes the wall, the frame, the hardware set, the finishes on both sides and the trades who install them. On a large project, those small moves happen constantly between design phases, and each one quietly invalidates part of a static status report.

With BidLight, those changes show up as element-level differences. When a revision lands, you see what changed element by element, and you see which issues it touches. Not a vague note that the design moved. A specific line: this wall moved, this door type changed from A to B, this trade owns the follow-up. That is the level of answer an owner respects when they ask why the status is not what it was last month.

This also removes a quiet source of friction inside your own team. The coordinator does not need to hunt for what changed. The model already knows. The conversation shifts from "somebody needs to update the log" to "here is what the change did to the schedule." That is the difference between a firm that reacts to design changes and a firm that tracks them as they happen.

Because every export is versioned, you never wonder whether you are showing the latest. That matters more than it sounds. Half the arguments in a project review are really arguments about which version was on the table. When each snapshot carries its author and milestone, that argument goes away.

The practical effect is that the record stops being a deliverable and becomes a running log. You are not producing a status for the coordination meeting. You are maintaining one the coordination meeting can rely on.

## The Answer That Earns Trust on the Call

Most of the work in a coordination review is not tracking. It is positioning. The firm that can answer with specifics on the call is the firm the client calls first next time, because the client learned that this team is not going to disappear for a week after every question.

That calls for the ability to answer quickly without hedging. BidLight gets you the changes in minutes. Where a manual comparison might take a 90-minute meeting, this is closer to fifteen minutes. That gap is not about being impressive. It is about whether you can say what moved while the client is still on the phone, with the model open, and defend it.

The confidence matters as much as the speed. When you answer from the model, you are not guessing. You can say where the finding comes from. You can point to the element, the issue and the revision. An answer you can defend is worth more than one that happens to sound good, because clients remember which status turned out to be real.

This is also where accountability becomes visible. The 6am digest tells every owner what they own, and the project view shows who is behind while there is still schedule to recover. You can tell the owner not just what changed, but who has to act and by when.

That shift is the same one behind the results from the hyperscale programme, where BidLight helped save 18,000+ hours and resolve 8,900+ issues. The client is not buying a status deck. They are buying the feeling that this team knows where the project stands.

From Basics to Enterprise, Sized for How You Work

BidLight plans run from Basics at $260 per licence per year to Max at $590. Custom Enterprise pricing exists for firms that need it. Every plan includes unlimited projects. The point of the low entry is that a small firm can start answering with specifics at the 60% meeting without a procurement process, and the point of the higher tiers is that a larger firm can run the same model across more people and more projects.

Per-licence pricing matches the reality of an AEC firm. You do not adopt a coordination record once and stop. You carry it through every project and every revision. A per-licence annual price keeps the cost visible and keeps the value tied to how many people need the answer at the table.

The tooling is only part of it. BidLight also does done-for-you BIM work: execution plans, 4D sequencing, fabrication detailing and spooling. Some firms want the software and the control that comes with it. Others want the model and the coordination handled by a team that does this every day. Both are valid, and both end in the same place, which is a model with one record riding on it.

If you have ever run a review on a complex project, you know the moving parts. Late design changes, trades working from different versions, and the question of who owns what. BidLight handles the record side inside Revit and Navisworks. Your team keeps working the way it works.

The plain pitch is this. Stop chasing scattered updates. Catch the clash in the model for about $50, not in the field for $5,000 to $50,000. Close issues with proof. That is it. There is nothing clever in it, and that is why it holds up in a design review.