A few colleagues recently asked me how BIM coordination works.

It’s a straightforward question, at least on the surface. I could have explained clash detection, coordination meetings, issue tracking, model reviews, and the processes involved in getting multidisciplinary models ready for submission.

Instead, I found myself talking about the project I’d been working on for most of the year.

Only afterwards did I notice the date. It was almost exactly a year since I started in BIM coordination.

Where It Started

The project was one I inherited: fragmented coordination history, incomplete information, questionable modelling decisions, and responsibilities that weren’t always clear.

I told my colleagues how difficult it was at the beginning. How I would encounter an issue and spend hours investigating something that initially appeared to be a simple modelling error. How one drawing would lead to another, then to an RFI, an old coordination comment, a revised shop drawing, or a scope clarification that hadn’t reached everyone involved.

Sometimes the answer was in the model. Sometimes it was buried in correspondence. Sometimes there was no answer, and the correct course of action was to ask another question.

I explained how I investigated clashes, not simply how I detected them. With 24 assets to coordinate, the clash reports could contain hundreds or thousands of results, and I made a point of investigating each clash individually, regardless of how many there were.

It was exhausting at times. But something changed between those early reports and the later ones.

I became better at knowing where to look.

I started recognizing patterns in the inherited models, understanding which references were authoritative, identifying when an apparent modelling error was actually a discrepancy between disciplines, and distinguishing technical problems from missing decisions.

At five months, I wrote that the model is not always the truth and that a clash is the beginning of an investigation, not the end of one. Most of that still holds. What I hadn’t seen then was how much those investigations were quietly changing the way I work.

The Television in the Staff Lounge

During that conversation, I walked my colleagues through one investigation in particular.

In a staff lounge, a television modelled by the previous contractor appeared to conflict with a mirrored wall feature. In a coordination meeting, the interior contractor maintained that the television’s location reflected actual site conditions, while the BIM model appeared to match the IFC elevation.

Initially, I agreed with the drawings.

But after the meeting, I recreated the perspective of the contractor’s site photograph in Navisworks and began comparing the surroundings: the ceiling, the walls, even the natural light entering from an adjacent façade. Everything indicated that we were looking at the same space.

I went through additional drawings, consulted other contractors, and examined inspection records to understand what had actually been built.

Eventually, I returned to the IFC drawings and noticed something I’d overlooked. The outline I had read as part of the television unit was the wall’s own geometry. The inherited model seems to have been built on the same misreading.

We requested more site photographs, and they confirmed it: the wall was there in the staff lounge, exactly as the contractor had said. The model was corrected. The contractor had been right all along.

The site photo aligned with the model. The outline read as part of the television was the wall itself.

What had looked like a disagreement between a site photograph and an approved drawing turned out to be a question about how the drawing had been read in the first place.

I Hadn’t Noticed How Much My Approach Had Changed

Somewhere in that explanation, it occurred to me.

I hadn’t noticed how much my approach had changed.

There was no single moment when I suddenly understood coordination. No particular meeting, clash report, or submission that marked a turning point.

It happened gradually, through repetition. Every investigation added something. Every incorrect assumption taught me to ask a better question. Every missing piece of information forced me to look beyond the model. And every subsequent asset gave me another opportunity to apply what I’d learned.

That’s what made this project so valuable to me. It wasn’t an ideal environment in which to learn coordination. In many ways, it was the opposite.

But because the information wasn’t always reliable, I couldn’t afford to take things at face value. I had to understand why something was modelled the way it was, where the instruction originated, whether the information remained valid, and who was responsible for making a decision.

The difficulty forced me to develop an investigative approach rather than rely entirely on established procedures.

Coordination Isn’t Something I Do Alone

I also learned that coordination isn’t something I can do entirely on my own.

There are situations where I need another discipline’s expertise, a site engineer’s confirmation, or another reading of the available information. Sometimes I work through an unfamiliar technical detail with an AI collaborator, or ask it to challenge my reading of a clash.

That doesn’t replace verification. It gives me another way to question what I’m looking at.

Thorough Is Not the Same as Efficient

There is a distinction between being thorough and being efficient. Investigating thousands of clashes individually isn’t how the process should operate indefinitely.

As my understanding improved, I began looking for ways to automate repetitive work while keeping responsibility for the technical conclusions. Some of that thinking has since become the Coordination Operating System.

The objective was never to investigate everything manually forever. It was to understand the work well enough to know what could safely be delegated, automated, or standardized.

What a Year Taught Me

Looking back, the most important thing this year taught me is that BIM coordination isn’t fundamentally about finding clashes.

It’s about establishing what is true, what remains uncertain, and what needs to happen next.

The model is one source of information. The drawings are another. Site conditions, correspondence, decisions, and people’s expertise all contribute to the picture. The coordinator’s responsibility is to connect those pieces without pretending the picture is complete when it isn’t. That’s the thread I’ve been trying to keep with b1m.solutions.

When my colleagues asked me how coordination works, I didn’t give them a perfect methodology. I gave them the experience of someone who had struggled to develop one.

Perhaps that’s why the conversation stayed with me.

I’d spent months concentrating on the next issue, the next asset, and the next submission. I rarely stopped to consider the accumulated effect of all those investigations. It took explaining the process to someone else to recognize it.

Sometimes you don’t realize how much you’ve learned because you’re too busy applying it.