What Your CMs Know About Your Projects That You Don’t

If you run a CM consulting firm, you trust your construction managers. You should — that’s why you put them on those projects. But trust isn’t the same as visibility, and over twenty-plus years on the consulting side, I noticed a pattern: there’s a meaningful gap between what’s happening on the project that your Resident Engineer/Construction Managers know, and what makes it back to leadership.

It’s not that CMs are hiding anything. They’re doing their job, but unfortunately, the information is staying where they’re using it — in their heads, in scattered daily reports, in email threads, in a gut sense of how the contractor’s behaving this week versus last week. Most of it never bubbles up until something forces it to: a claim, an audit, a CM leaving, an RFP that needs metrics.

Here are three things your CMs know right now that you probably don’t — and what to do about each.

1. They know if the contractor is setting up for a claim.

Long before a claim lands on your desk, your CM is watching it form. The signals are in the documentation if you know what to look for: a Notice of Delay that’s vague on critical-path impact, a Notice of Changed Conditions on a topic you’ve already responded to, RFIs piling up that all touch the same scope, response times stretching, the tone of meeting minutes shifting.

Your CM sees this. The question is whether anything is being done about it.

The right play, from the CM’s seat, is to make the record. That means responses on time and clear — and if there are too many open items to keep up with, getting the contractor on record prioritizing them themselves based on critical path. Ask the contractor, in writing, when each open item becomes a delay. That’s not adversarial. That’s contract administration. It moves the burden of justification back to where it belongs and protects the agency’s record at the same time.

This is also where most CMs need help and don’t ask for it — usually because they’re heads-down on the project and don’t realize the volume has crossed a line. A firm leader checking in on response times, open-RFI counts, and pattern shifts can step in before it becomes a fire. You don’t need a tool to do that. You need a habit.

2. They know whether your daily reports are useful or just checking a box.

Your CMs read the daily reports their inspectors are submitting. They know which ones could support a claim defense or a change order analysis six months from now and which ones couldn’t. Most don’t say anything about it, because the reports are getting filed, the box is getting checked, and there are bigger fires.

The moment something goes sideways — a differing site conditions claim, a public records request, an audit, a contractor’s working day dispute — that’s when the gap shows up. A daily that says “contractor on site, paving north end” is worthless. A daily that says “contractor placed asphalt at Sta 14+50 to 18+20, two paving crews, weather conditions X, observed deviation from approved mix submittal, notified the contractor” is the difference between defending the agency’s position and scrambling.

A few things firm leaders can require, regardless of software:

• Calibrate inspectors to the project before mobilization. Walk them through the schedule and the spec book. If they can’t tell you what controls the critical path on this job, their reports are going to read the same on a paving day as on a buried utility day — and that’s the problem.
• Require specificity. Stations or structure IDs, not “the north end.” Crew counts and equipment, not “contractor on site.” What controlled progress. Conversations with the contractor and what was said. Deviations from approved submittals.
• Have inspectors read the contractor’s three-week look-ahead before the day starts. They should know what’s supposed to be happening so they can flag what isn’t.
• Run the reconstruction test. Could a CM who wasn’t on the project read two weeks of dailies and tell you what happened? If not, you have a documentation problem dressed up as a reporting routine.
• Recurring critique, not one-time onboarding. Most firms train inspectors on day one and never look at the reports again until something goes wrong. Build it into how the team operates.
  

3. They know the informal cost trajectory — but it’s nowhere on paper.

This is the one I’d push hardest on, because it’s where most firms have the biggest gap and the easiest fix.

Your CMs are running pay requests. They’re tracking quantities. The numbers are accurate enough to support an audit later. That’s contract administration, and most teams do it fine.

What they’re often not doing — and what most firms don’t require — is managing the contract. That’s a different thing.

A CM managing the contract knows that the bid item for asphalt was clearly calculated on theoretical, but it’s paid on tonnage, and the overage is coming. They know there have been four buried manmade objects on force account and the contractor hasn’t priced any of them, so no CCO has been executed for the first two pay requests. They know there’s an RFI sitting open about a foundation detail that’s almost certainly going to land as a change order. None of this is in the formal numbers yet. All of it is real.

Pay requests tell you where the project has been. Managing tells you where it’s going. Most firms only do the first.

When the owner comes asking for a nice-to-have change order, your CM should be able to tell them what’s already eating the contingency — even informally, even as a working estimate. If they can’t, the owner makes that decision in the dark, and your firm gets blamed when reality catches up.

The fix is unglamorous and free: build a running cost estimate practice. Monthly at minimum, weekly on tight projects. Not a formal forecast. A working list. Track items as they happen — overruns you can see coming, force account work without executed CCOs, RFIs that imply a change but haven’t generated one yet, differing site conditions. Make your CMs write these things down on a recurring cadence. Knowing it is better than not knowing it.

The bigger picture for firm leaders

None of this is about your CMs doing better work. They’re doing the work. The gap is between project-level knowledge and firm-level visibility — between what’s happening on a job and what leadership can see across the portfolio.

When that gap is wide, three things happen. You can’t help CMs who need help until it’s already a fire. You can’t compete on RFP responses with real metrics on response times and project performance, because the data is buried in projects. And when a CM leaves, the project knowledge walks with them.

Start with the habits — response-time check-ins on RFIs and submittals, daily report calibration with inspectors, and a running cost estimate practice. They pay back on every project, regardless of what tools you use.

We built BridgeDoc InSite because once those habits exist, the work of seeing across them — across projects, across teams — is still hard.

InSite connects what’s in the meeting minutes, the field reports, the RFIs, and the change orders so firm leadership can see what their CMs are seeing without having to ask. If you’d like to see what we’ve built, take a look.

Better yet, see BridgeDoc InSite in action.

Book your FREE demo with Kelly HERE!

"I’ve managed construction on public works projects for over 25 years, including federally funded infrastructure in California. At BridgeDoc, we’ve built daily report workflows around the documentation practices that hold up under scrutiny — RE review, structured field logging, photo management, working day tracking, and built-in prompts that make thorough reporting achievable in the field. If you’d like to see how it works, I’d be happy to show you."- Kelly Wheeler, BridgeDoc CEO & Founder