Your Coordination Is Only as Good as the Record Behind It

The Day Your Senior Coordinator Quits, the Project History Walks Out Too

Monday after your senior BIM coordinator gives notice. A 40,000 square foot tenant improvement is in coordination and the next package is due Friday. The person who knew which clashes were really open, which trade ignores email and which revision the MEP team is actually working from is gone. That is not a staffing problem. It is a record problem.

Most of what firms lose when key people leave never shows up on a line item. It shows up as a package that goes out against the wrong revision because nobody remembered the structural update. It shows up as a comparison that drags because the shortcuts walked out with their owner. It shows up as rework on an issue the departing coordinator would have caught at a glance. The cost is real and it adds up. Almost nobody traces it back to the departure.

A coordinator's value lives in three places: their shortcuts in the software, their memory of what has been closed and why, and their relationships with the trades. None of it lives in the model. Shortcuts live in a personal toolbar. Open issues live in a personal spreadsheet nobody else can open without a decoder ring. Relationships live in a phone contact list. When the person leaves, all of it goes at once, and you rebuild it from zero while the schedule keeps running.

The fix is not a better handoff document. Those get written in the last week, when the person is already checked out and half the knowledge is gone. The fix is moving the knowledge into the asset that stays, which is the project record. When every export is versioned and every issue is pinned to the element it concerns, the history stops being a person. It becomes a property of the project.

BidLight keeps one live record of the project inside Revit and Navisworks. Every publish is a snapshot with its own files, author and milestone. Issues carry the sheet and revision that raised them, and they close with proof. The incoming coordinator opens the model and sees the same record the last one saw. Not a summary written by someone with one foot out the door. The actual history, in the actual model, in minutes.

What Walks Out the Door

Most firms underestimate what leaves with a departing coordinator, because so much of it is invisible. The shortcut keys are the obvious part. The harder loss is the judgment baked into dozens of small decisions. Why did the team keep that wall type? Why did you stop waiting on that trade's model? Which clash was waived and who agreed? None of that is written down. It is memory, and it is gone.

The trade relationships come next. Your senior coordinator knows which mechanical contractor answers within an hour and which one needs a phone call. They know which model is always a revision behind. A replacement learns those lessons the slow way, one missed update and one clash in the field at a time. That learning period is expensive, and it can last months.

The third loss costs the most and gets talked about the least: knowledge of your own process. Who owns what. What goes in the weekly package and what stays out. How you handle escalation when an issue sits. When that coordinator leaves, the next package is run by someone guessing at your firm's own standards.

Run the math on the field cost. A clash caught in the model costs about $50. The same clash found in the field costs $5,000 to $50,000. If a departure causes even a handful of issues to slip through, the bill arrives on site. And an unresolved one can burn $15K to $50K a week in idle field labour.

You already know the version of this that hurts most. It is not that the answer was wrong. It is that nobody could find it for four extra days, and the crew was already waiting.

Why Spreadsheets and Tribal Knowledge Keep Failing You

The usual recovery plan after a departure is a panic download. Someone sits with the departing coordinator for two days and scribbles notes into a shared drive. Six weeks later nobody can find the file, and the list in it has gone stale against the current model. Firms call that a fragile coordination process. It is not fragile because the people are bad. It is fragile because there is no single record.

Open-issue lists go stale on a schedule nobody controls. A spreadsheet from three revisions ago looks authoritative and is quietly wrong. The next coordinator inherits it, trusts it because it exists, and chases issues that were fixed weeks ago. You can trace that loss straight back to the day the person who kept the list stopped maintaining it.

The other trap is treating the model as a drawing and the issue list as a separate document. Two files, two owners, two update cycles. The model moves when the architect moves. The issue list moves when someone remembers to move it. Rework lives in that gap, and every team we talk to describes it in the same frustrated tone.

The fix is plain. Put the issues where the geometry already lives. When the model changes, the comparison shows it, and the issues attached to those elements show up with it. The person who owns the process becomes less critical, because the process no longer depends on them being in the building.

Teams ask us which projects this helps most, from healthcare to data centers to industrial fabrication. The answer is any team where knowledge sits in too many heads and too few systems. In AEC, that is nearly all of them.

Keep the Record in the Model, Not in the Person

The principle is easy to state and takes real work to put in place. The model is the record. Issues and history are properties of the elements in that record, not a separate document someone maintains by hand. When the design moves, the record moves, and it moves without a meeting.

In practice, every export is a versioned snapshot. Any two revisions compare element by element, grouped by category: structural, MEP, envelope, interior. Do not retype changes into a spreadsheet and hope the two stay in sync. Then pin issues to the elements they concern, carrying the sheet and revision that raised them. You see what changed in about 15 minutes instead of a 90-minute meeting.

For retention, the payoff is that the knowledge stops being personal. The next coordinator opens the same Revit model and sees the same defensible record: who raised an issue, who closed it and the commit that proves it. They can ask why a clash was closed, and the answer sits in the model instead of in someone's memory of a conversation from last spring.

This matters most during the hiring gap, which is when teams get reckless. With the record in the model, a less experienced coordinator has something solid to work from on day one, not a blank page. The 6am digest tells them what each owner holds. You stop losing weeks because the only person who knew the status is gone.

The same logic holds for outside teams. When a trade or consultant joins mid-project, you do not have to walk them through your process. You hand them the model. The history is there, the reasoning is visible, and the record does not fork into two competing versions.

None of this replaces coordinators. It makes the firm's coordination capability something the coordinator adds to and the firm keeps, whatever happens to the org chart.

A Practical Playbook for the Next Departure

Audit what lives outside the model today. Pull the last five coordination packages your team sent and trace every open item back to where it came from. How many came from a personal spreadsheet, a shortcut or a verbal rule of thumb? That count is your exposure, and it is almost always higher than leadership expects.

Next, move the backbone into the record. Publish from Revit so every revision is a versioned snapshot, and pin each open item to its element. Every later step depends on this one. Without it, you are still maintaining two records and hoping they agree.

Then run a test. Pick a project and hand it to someone who is not your senior coordinator. Have them work out the status from the model and its record only. Time them. The first attempt will be slower than you want, and it will show you the gaps. Fill those gaps in the record, not in a handoff doc, and run it again. That is how a team gets to a status check in minutes that anyone can open and trust.

Last, close the loop after each milestone. Track which issues were closed with proof, which drifted and why. The Problem Solver Index makes resolution rates per person visible, so ownership is clear without chasing. That is the gap between a team with a coordination process and a team with a few people who are good at coordinating.

If you want to get there faster, we also do the work for you. Execution plans, 4D sequencing, fabrication detailing and spooling, delivered by a team that does it every week. It is not a shortcut around the work. It is the work.

What You Keep When People Leave

Every firm loses people. Retirement, relocation, a competitor with a better offer. You cannot stop that. You can decide whether their judgment leaves with them or stays in the model where your team can reach it.

When your history lives in the model, a departure becomes a hiring problem. You still have to hire and onboard. But you are not rebuilding your coordination capability from scratch while the job keeps moving. That rebuild is what eats a team's schedule for a quarter after a key person walks.

When the record sits in Revit, your newest coordinator and your most seasoned one look at the same defensible history. On the hyperscale programme, that kind of shared record is what stood behind 18,000+ hours saved and 8,900+ issues resolved. Those results come from knowledge that belongs to the project, not to one person.

Here is the short version. Your coordination is only as good as the team behind it, and your team is only as stable as the systems underneath it. Put the record inside the model. Let it update when the design does. Make one person's departure an HR event, not a schedule event.

You should not have to restart from zero every time someone leaves. Keep your project history where the geometry lives, so the record stays put even when people do not.