Construction Audits: Are They Really Worth It?

Let me start with a question.

If you were building a $20 million facility, would you spend $20,000 to find out whether your money was being spent the way you thought it was?

Most executives would probably say yes.

Yet mention a construction audit, and suddenly the conversation changes.

Do we really need one?

Isn't the project manager already watching the costs?

Won't an audit slow the project down?

We trust our contractor.

And my personal favorite:

“The project is already over. What are we going to find now?”

Possibly quite a lot.

Because construction audits aren't really about whether you trust your contractor. They're about whether you understand where your money went, whether the contract was followed, whether controls worked, and whether the project delivered what you paid for.

And yes, sometimes they find money.

Sometimes a lot of money.

But that's not the only reason they are worth doing.

First, What Exactly Is a Construction Audit?

When people hear “construction audit,” they sometimes picture an auditor arriving at the jobsite wearing a hard hat, carrying a clipboard, and looking suspiciously at everyone.

Relax.

We're probably not there to count bricks.

A construction audit is a structured review of the financial, contractual, operational, and control aspects of a construction project.

Depending on the project and the timing of the audit, it may examine areas such as:

• Contractor and subcontractor charges

• Change orders

• Labor costs and payroll burdens

• Equipment charges

• Material costs

• Allowances and contingencies

• Insurance

• Markups and fees

• Schedule impacts

• Payment applications

• Contract compliance

• Procurement practices

• Documentation

• Closeout costs

The goal isn't to play “Gotcha!”

The goal is much simpler:

Did we get what we agreed to, at the price we agreed to, under the terms we agreed to?

That sounds like an easy question.

On a large construction project, it rarely is.

“But We Have a Project Manager.”

Good.

You absolutely should.

But a project manager and a construction auditor are looking through different windows.

The project manager is trying to deliver the project. They are juggling contractors, schedules, design issues, permits, meetings, budgets, changes, executives asking when the building will be finished, and probably seventeen emails marked “URGENT” before breakfast.

And then come the excuses. Oh, the excuses. “We trust our contractor.” “The project manager already reviews the invoices.” “We’ve never had a problem before.” “The project is almost finished, so what’s the point?” “An audit might upset the contractor.” “We don’t have the budget for an audit.” And then there is the one I hear far too often: “We don’t have anyone in Internal Audit who is qualified in construction.” Fair enough. Construction auditing does require specialized knowledge, but since when did we don’t know how become therefore we shouldn’t do it? Internal Audit doesn't need to suddenly become a team of architects, engineers, quantity surveyors, and construction managers. Bring in a construction audit specialist, co-source the engagement, partner with technical experts, or use the audit as an opportunity to build your team’s knowledge. On a multimillion-dollar project, there always seems to be money for another change order, another consultant, or another schedule extension, yet checking whether those millions were spent properly is where we suddenly discover our frugal side. And none of this means we distrust the contractor or project team. Trust is wonderful. Trust with evidence is even better.

Their focus is understandably forward:

How do we keep this project moving?

The construction auditor asks different questions.

What does the contract actually allow?

Does this invoice agree with the supporting documentation?

Why did this change cost $180,000?

Was that cost already included somewhere else?

Why are we paying this markup?

Who approved this?

Neither perspective replaces the other.

In fact, the strongest projects often have both.

Change Orders: Where Little Things Become Very Big Things

If there is one area that deserves attention on almost every construction project, it is change orders.

One change order for $12,000 may not raise an eyebrow on a $50 million project.

Neither may the next one.

Or the next one.

But construction costs rarely get into trouble because someone walks into the room and announces:

“Good news, everyone! We accidentally overspent by $4 million!”

Cost creep is usually quieter than that.

A design clarification here.

An unforeseen condition there.

A schedule adjustment.

Some additional labor.

A little extra equipment.

A markup.

Then another markup.

Then a markup sitting on top of someone else's markup like a cherry on a very expensive sundae.

Individually, the changes may seem reasonable.

Collectively?

That's where the story gets interesting.

A good construction audit doesn't merely ask whether a change order was approved. It asks whether the change was necessary, properly priced, supported, authorized, contractually allowable, and not already included in the original scope.

That is a very different question.

Cost not becoming let's look at safety.  What is the price tag on the life of the worker who was injured or killed on a site, simply due to carelessness.  Construction sites are inherently dangerous, multiple moving parts, tools, and sometimes explosives so we have to be careful.  But the project manager is asking us to speed things up and doing things the safe way may take up too much time.  Especially for those things that seem like pointless procedures.  

The Contract Is the Rulebook

Construction contracts can be enormous.

Hundreds of pages. Exhibits. Schedules. Amendments. Insurance requirements. Pricing provisions. Allowances. Definitions.

And somewhere buried on page 147 may be the sentence that determines whether you should have paid an additional 10% markup on a $600,000 change.

That's $60,000 hiding in a paragraph nobody particularly wanted to read.

This is why construction auditing is not simply an invoice review.

The contract is the benchmark.

If the contract says certain costs are reimbursable, we need to understand what qualifies.

If it says certain costs are included in the contractor's fee, we should not pay for them twice.

If it limits markups, those limits matter.

If it requires supporting documentation, the documentation should exist.

If it establishes audit rights, those rights should be understood and exercised appropriately.

If it is ambiguous, better put Legal on alert as surely a dispute can (will) arise.

A beautifully organized invoice can still contain costs that the contract does not permit.  In fact I normally find more mistakes in the beautifully organized invoice than the hand written on, filled out probably in the work truck or van, with a little coffee cup stained ring on top.

So, Do Construction Audits Actually Save Money?

They certainly can.  Is there a guarantee?  Certainly not but why not look.  Even if you find no money you may find improvements for future products or better practices for what you are currently doing.

Construction audits may identify duplicate billings, unsupported charges, excessive markups, incorrect labor rates, inappropriate equipment costs, insurance discrepancies, uncredited allowances, mathematical errors, or costs that should never have been billed to the owner.

But I would argue that focusing only on recoveries misses half the value.

Suppose an audit doesn't recover a spectacular amount of money.

Was it unsuccessful?

Not necessarily.

What if it identifies a weak change-order process before the next five changes occur?

What if it discovers that nobody is reconciling contingency funds?

What if it shows that approval authority is unclear?

What if it identifies poor documentation that could create problems during closeout or a future dispute?

What if it gives management confidence that the project is actually being managed well?

That has value too.

Sometimes the best audit finding is:

Things are working.

That's not boring.

That's assurance.

Timing Matters

One of the biggest mistakes organizations make is waiting until the project is finished before bringing in an auditor.

Can you audit a completed project?

Absolutely.

But imagine discovering two years later that you need detailed documentation supporting a major change order.

The project manager has moved on.

The contractor's employee who prepared it works somewhere else.

The subcontractor can't find the records.

Someone thinks the documents are “probably in the shared drive.”

And the shared drive contains 8,426 files named things like:

FINAL.xlsx

FINAL2.xlsx

FINAL_REAL.xlsx

and my personal favorite,

FINAL_USE_THIS_ONE.xlsx

Suddenly, archaeology sounds easier.

Auditing during the project can identify problems while there is still time to correct them.

It can also create something extremely valuable:

visibility.

Management doesn't have to wait until the ribbon cutting to discover whether the financial controls worked.

“But Won't the Contractor Hate It?”

Maybe.

But probably not.

Experienced contractors have encountered audit provisions before. A professional construction audit should not be adversarial simply for the sake of being adversarial.  Heck I even had project managers help me with writing my first book:  Construction Audit Guide: Overview, Monitoring, and Auditing.

The tone matters.

We're not walking onto the project saying:

“We know you're doing something wrong. We're just here to find it.”

That approach helps nobody.

Instead:

“Let's make sure the contract is being administered consistently and that everyone understands how costs should be supported and billed.”

Clear expectations actually help contractors too.

When documentation requirements, markup rules, approval processes, and billing expectations are understood from the beginning, there are fewer unpleasant conversations later.

Good controls aren't about distrust.

They're about clarity.

The Question Isn't Really “What Does the Audit Cost?”

It's tempting to look at an audit proposal and ask:

How much will this cost us?

Fair question.

But it shouldn't be the only question.

Also ask:

How much could we lose if nobody looks?

If you are managing a major capital project, even a small percentage of billing error, cost leakage, weak controls, or poorly managed changes can become significant very quickly.

On a $1 million project, 1% is $10,000.

On a $50 million project, it's $500,000.

On a $500 million capital program?

You can do the math.

And suddenly the cost of independent assurance starts looking a little different.

So, Is a Construction Audit Worth It?

For many significant construction projects, yes.

But not simply because an auditor might find money buried in the invoices.

A good construction audit can provide something broader.

It can tell you whether your contract is being followed.

Whether your controls are working.

Whether your change orders make sense.

Whether costs are adequately supported.

Whether management is receiving reliable information.

Whether problems are being caught while they are still small enough to fix.

And ultimately, whether the organization is getting what it paid for.

Construction projects are complicated enough.

The financial side shouldn't require crossed fingers, a lucky rabbit's foot, and the hope that someone somewhere checked the spreadsheet.

Trust your project team. Trust your contractors. Build good relationships.

Then verify.

Because when millions of dollars are pouring into concrete, steel, equipment, labor, and change orders, asking a few uncomfortable questions isn't being difficult.

It's good governance.