Your Best Coordinator Quit Last Friday. The Work Didn't Stop.

Friday's Resignation, Thursday's Meeting

The email lands at 4:40 on a Friday. Two weeks' notice, thanks for everything, I have accepted another position. You read it twice. Then you open the calendar and see Thursday circled. The GC coordination meeting. That is the whole problem in one glance. The work did not resign with them.

You know the picture has to be right, because you have watched a missed clash turn into a hard conversation in a conference room six months later. You also know you have not looked at what changed in the model since the last meeting. It lives somewhere in a folder, geometry and metadata sitting there, fully aware of every wall and duct and beam, and completely disconnected from the issue list you are about to rebuild by hand.

Here is what most firms do in this moment. They call the coordinator who left, politely, and ask for one favor. They dig up last month's markups and stretch them to fit this project. They assemble three people around a screen and spend six days reconciling a list nobody fully trusts. That is how you end up running a meeting about a building that changed since you last measured it.

BidLight starts from a different place. You keep one live record of the project inside Revit and Navisworks. Every publish is a versioned snapshot with its own files, author and milestone. When the design changes, the next snapshot shows it. No tribal knowledge required. Just the geometry, the history and the owners.

The Thursday meeting is still Thursday. What changes is how you spend the days before it.

What You Lose When the Coordinator Walks Out

Everyone tallies the salary and the recruiting fee. The real loss is quieter. Your departed coordinator held a private map of the project in their head, and that map included which issues were really closed, which trade always misses the first call, and which level always clashes at the ceiling. None of that was written down anywhere you can open.

That hidden layer is why departing-coordinator articles usually end with advice about documenting your processes. Fine advice, hard to execute under deadline. If you have ever tried to get into BIM coordination from the outside, you know the job is less about software and more about judgment calls made from repetition. Judgment does not transfer through a shared drive.

So when the person leaves, the judgment leaves with them, and the next person inherits a log with no memory. They inherit a folder with files named Final_v3_REAL_final. They inherit a meeting on Thursday. And sooner or later 47 versions of the same markup are all they have to go on.

The question is not which tool looks best. The right question is where the status comes from and whether it can explain itself. A record that traces back to model elements you can click is a different animal than a cell someone typed in 2023 and everyone has trusted since.

BidLight puts that trace on the record. Issues are pinned to the elements they concern and carry the sheet and revision they came from. Closing one needs proof: a screenshot, a tagged user and the model commit that fixed it. When someone asks why a clash is marked closed, you have an answer that is not a shrug.

Open One View. Get a Picture You Can Defend.

The scene is real, and it is unglamorous. You are not going to become a senior coordinator over a weekend. You are going to open one view and check what it shows, which is a genuinely different job. You will not rebuild their log. The model already knows which elements changed.

Compare the latest publish to the one before the last meeting, and BidLight returns the changed elements, grouped by structural, MEP, envelope and interior. A review that used to take a 90-minute meeting comes back in about 15 minutes, and you spend the saved hour on the parts that deserve a human: scope gaps, trade coverage, the issues you want to push on deliberately rather than accidentally.

Defensibility is the whole point of Thursday. When the GC pushes back on a status, you click it and land on the model element behind it. When your own team questions an issue, you show the geometry. When the architect sends a revision Wednesday afternoon, you publish and watch the changes appear instead of guessing how much moved.

That last part is the piece most coordination workflows cannot do at all. Chasing scattered updates and redoing comparisons is the routine cost of manual coordination, and it never shows up on a budget line. It shows up as the Thursday you spent reconciling instead of solving clashes.

If you have been looking at coordination platforms, this is the test to run: change something in the model and see whether the record follows. If it does not, you have a digitized spreadsheet, not a live record. If it does, you have a picture you can defend in a room full of people who are paid to find holes in it.

## The Model Holds the History. You Do the Thinking.

A comparison is not a claim that software replaces your judgment. BidLight does not run automated clash detection. It tracks model changes and clashes between revisions, pinned to the elements, and clears the busywork so your judgment arrives somewhere useful. You still review the changes, catch the odd element and decide who acts. What you stop doing is hunting for differences with two windows and a mouse.

Think about what changes when the history is a read of the model rather than a manual pass. Status stays consistent across disciplines because it comes from one source. Changes ripple instead of getting patched in one tab and forgotten in another. The record and the model stop drifting apart, which is the quiet failure mode in most firms, and the one that costs the most.

For a firm choosing a coordination platform, the honest criterion is whether it lives where the design lives. A tool that asks you to re-enter the building is asking you to introduce errors on purpose. One live record inside Revit and Navisworks means the record is never a translation. It is the same building, tracked.

This also changes the hiring math. When the history is handled, a coordinator can spend their day on trade strategy, scope review and the conversations that keep the job on schedule. That is a better job, and better jobs are easier to fill. Coordinator retention, as it turns out, is often a tooling problem wearing a people problem's clothes.

You also stop being the bottleneck. Anyone on the team can open the record and read the status, which means the project is not hostage to one person's calendar or one person's memory of a job they left behind.

The Meeting Is Thursday. What Does It Cost?

BidLight Basics runs $260 per licence per year. Max is $590. Enterprise pricing is custom, and for firms with real volume, that conversation is worth having. Compare any of those to the cost of one clash that reaches the field, $5,000 to $50,000, or one week of three people chasing a deadline, and the arithmetic stops being interesting.

There is a second side to this that most firms miss. The record you now keep in the model is not just an internal tool. It is a service you can show clients. When you can turn a design change into a clear list of elements and owners in minutes, you can sell that capability instead of giving it away.

BidLight also does done-for-you BIM work when you would rather hand off the execution plans or the detailing. Some firms want the software. Some want the outcome. Both are on the table, and neither one asks you to rebuild a departed coordinator's log from scratch on a Tuesday night.

The broader pitch is plain, so here it is plainly. Stop chasing scattered updates. Close issues with proof. Know who is behind while there is still time. If you remember only one thing about how BidLight works, remember this: you keep one live record of the project inside Revit and Navisworks, and every change rides on the same model.

That is what you have on Thursday. Not tribal knowledge, not a stretched old spreadsheet, not a favor from someone who left. The geometry, the history, the owners and a 6am digest that tells each of them what they own. The work did not stop when your coordinator did, and now neither does the record.