The Coordination Tax Killing Construction Operations

briq Research · April 22, 2026

Ops leaders describe their week as chasing exceptions, not running the business. The calendar gets hijacked by coordination because nothing else is doing it.

You coordinate the chaos. Every day. The work your title says you do gets whatever time is left over.

Ask any VP of Operations at a construction firm to describe an average week and the description won't sound like operations leadership. It will sound like a dispatcher's job. Phone calls about a subcontractor who didn't show. Emails about a material delivery that got pushed. A PM asking for a sign-off on a change order. A controller asking why a cost code is wrong. An owner asking when the next pay app is coming. A superintendent asking whether to pull the second crew off Project A to help Project B.

None of this is operations. It's exception handling. And it's every day.

The role most ops leaders were hired for, the strategic one, is what happens after 6 p.m. or on weekends. Capacity planning, process improvement, margin analysis, vendor strategy, talent pipeline. The work that actually moves the business forward gets whatever hours are left after the coordination is handled. In a busy quarter, that's zero hours.

Here's why this happens, and why it gets worse as the company grows.

Every construction company runs on a web of handoffs. Project wins a bid. Job gets set up in the ERP, the PM system, the billing system. Estimator hands it to the PM. PM hands the schedule to the super. Super coordinates with subs. Subs send invoices. AP codes them. Controller reconciles. PM approves pay apps. Owner pays. Each of those handoffs has a standard version and a dozen exceptions. The standard version has a defined owner. The exceptions do not. They route themselves to whoever is senior enough to resolve them, which in most firms is the ops leader.

Two things happen as the firm grows. First, the number of handoffs increases linearly with the number of projects. Twice the projects, twice the handoffs. Second, the number of exceptions grows non-linearly. Twice the projects, roughly three times the exceptions, because complexity compounds. More project types, more clients, more subcontractors, more systems, more edge cases. The ops leader's calendar fills up faster than the org chart can expand.

Most firms try to solve this by hiring. Another project controls person. Another AP clerk. Another operations manager. The hires help for a quarter. Then the coordination load catches back up, because the new headcount added their own handoffs to the web. Hiring scales the amount of work the company can absorb. It doesn't scale the coordination layer that holds it together.

Some firms try to solve it with software. New PM system. New ERP module. New dashboard. The software helps with the parts of the work that are inside its domain. It does nothing for the coordination work, because coordination happens between systems, not within them. You now have five well-run systems and the same ops leader on the phone at 7 p.m. figuring out why a change order approved in one system didn't make it to the other.

The real shape of the problem is this. Coordination is work. It's human middleware. And the org chart doesn't reflect it. Nobody's title says "spend 30 hours a week keeping the systems in sync." But that's what ops leaders, senior project accountants, and controllers actually do. The cost is hidden because it's absorbed into overhead. The effect is visible in what those people don't get to do.

A healthier model puts the coordination work into a layer that can actually carry it. Exceptions get flagged automatically when the systems disagree. Handoffs get tracked as a thing in their own right, not as a side effect of someone's inbox. Routine cross-system reconciliation happens continuously instead of at the end of the month. When an ops leader gets pulled in, it's because a decision is needed, not because something fell through the cracks.

The firms that have made this shift don't have smaller ops teams. They have ops teams doing different work. The VP of Operations spends the quarter on capacity planning, not on the phone about a delivery. The project controls team closes out projects instead of chasing documentation. The senior accountants do variance analysis instead of variance cleanup.

It takes a different way of thinking about where the work actually lives. If coordination is what's eating your ops team's week, automating individual tasks won't fix it. The coordination is the task.