What I Actually Look At in a Construction Operations Audit

← Back to all posts

The word audit gets used loosely, so it is worth saying plainly how BMG uses it. The free first step at BMG is a 30-minute Operating Problem Conversation: one operating problem, a candid read, and a straight answer on whether BMG is the right fit. The deeper assessment is the paid BMG Operations Diagnostic: fixed fee, direct observation of the real work, findings with their economic impact, and a 90-day plan that stands on its own. This note explains the kind of operational looking that belongs inside that Diagnostic for a contractor, and what it is not.

The looking has to happen before anyone recommends anything. You cannot fix a workflow you have not watched, and in my experience it is rare for a construction operation to have been watched end to end by someone whose only job in that window is to see where the time goes. This is what that looks like.

Operations problems tend to hide in the workflow, not the software

In my experience, owners tend to arrive with a guess already formed. The software needs replacing, or the shop is a person short. Sometimes that guess is right, and a good assessment will say so. But more often the friction is not inside any one tool and not inside any one person. It lives in the seams between them, the hand-offs and the waiting and the re-entry, and seams do not show up on a software invoice or a performance review.

That is why the looking does not start with your software list or your org chart. It starts by watching how work actually moves. I have written about where estimating hours go and the gap between the tools that create them. The Diagnostic is simply how you find those things inside one specific shop.

It starts by following one real job, end to end

The first thing I do is not interview people. It is pick one recent bid and trace it from the invitation to the submitted number. Who touched it. What they did with it. What they were waiting on. Where it sat overnight.

One real bid, followed all the way through, teaches more than an hour of anyone describing their process, because in my experience the described process and the real one are never quite the same. The description is how the work is supposed to go. Following the job shows how it actually went, including the parts that go unmentioned because people have stopped noticing them.

Where to look for the friction

After enough of these, you learn where to look. In my experience, a handful of places account for much of it.

Estimating. The point where an estimator stops estimating and starts couriering data: rebuilding the abstract sheet, chasing subcontractor quotes, re-keying numbers between tools that do not talk. The judgment work is what you pay an estimator for. The assessment looks for how much of the week is not that.

Coordination. The small asks. The how-is-it-going message, the where-does-this-stand status check, the email forwarded so someone else can finally act on it. Each one is tiny. Together they are a real tax, and because each is tiny, it is worth checking whether anyone has ever added them up.

Disconnected systems. I do not count this as a number of software tools. Operationally it looks like the same figure typed into three places, a workbook moving around as emailed versions, and one person who is the only one who reliably knows which file is current. Old bid history that sits unsearchable is the same pattern, aged.

Approvals. Where work stops and waits on a yes. A bid waiting on a go or no-go. A change waiting on the owner. The assessment looks for where jobs sit, and who the sign-off is.

Status visibility. Whether anyone can see where a job is without asking. When status lives only in someone's head, every status question interrupts two people instead of none.

What can surprise the owner

Two things have come up again and again in my experience. The first is that the slow part turns out not to be the one thing they expected. They came in certain it was the takeoff, or one particular employee, or a tool that needed replacing. In the operations I have watched, it was spread across many small seams that no one had named.

The second is harder to say, so I will say it plainly. The owner's own desk is often one of the bottlenecks. When every meaningful approval routes through one person, that person becomes the constraint on everything downstream of them, and they can be the last in the building to see it. That is not a criticism. It is just what an outside look tends to surface.

What this looking is not

It is not a sales presentation. It is not a software pitch, and it does not end with a recommendation to go buy AI. It is not a phase-one discovery workshop with frameworks and a maturity score, and it does not need a slide deck.

It is structured looking and asking, by someone whose only task in that window is to see where the time goes, followed by an honest read. That is the whole of it.

The Diagnostic is diagnosis, not a sales document. It is watching how work actually moves through your operation, by someone whose only job in that window is to see where the time leaks. It does not end with buy AI. It ends with where the friction is, and what is worth doing about it.

What happens after

The output is plain language. Here is where your hours are leaking. Here is what is worth fixing. Here is what is not worth touching, because not every rough edge is worth the disruption of changing it.

If there is a workflow worth implementing, that is a separate and properly scoped conversation, with its own number attached. If there is not, I say so. The Diagnostic's job is the findings. It is not a sales document, and treating it as one would ruin the only thing it is good for.

Why the looking has to come first

Every recommendation worth making rests on having watched the real work. A fix proposed without that is a guess wearing a confident voice, and construction has enough of those already.

The looking is unglamorous, it is specific, and it is the step that everything useful depends on. If your operation has never had it, it is worth having, whoever you have it with. At BMG, it starts with a 30-minute Operating Problem Conversation at no charge, and goes deeper inside the paid Operations Diagnostic.

---

Field notes describe how we think about operating problems. They are not client case studies.