Track the Estimate From Start to Finish

Estimate tracked against actual job cost, split into labor, material, equipment, subcontract and other

Your estimate is the job's budget. Who reads it after the contract is signed?

In a lot of companies, nobody. The estimator moves on to the next bid. The project manager runs the job from memory. The estimate retires the day the contract is signed.

The estimate is the job's budget

One ROOI exam item reads: Each job has an estimate we track from start to finish.

The estimate says how many hours, how much material and how much equipment the job should take. That's a budget. Tracked weekly, it tells the project manager where the job is heading while there's time to steer.

Without it, the project manager only knows the job is going badly when the money runs out.

It closes the loop

Tracking the estimate also closes the loop.

When the job ends, the estimators see what the field actually did. The next bid is better because the last job taught them something.

Without that loop, every estimate is built from memory. And memory is generous. It remembers the good jobs and forgets the overruns.

When I ran my concrete company, the biggest improvement in our bids came from measuring what the crews actually produced and feeding it back to estimating. The rates got real.

$50,000 over. Over where?

Here's the second half of the problem. "The job came in $50,000 over." That sentence doesn't tell you what to fix.

Another exam item reads: Job cost is split into labor, material, equipment, subcontract, and other.

Here's an example. Split the same job five ways. Labor is $62,000 over. Material is $12,000 under. The rest is on budget.

Now the problem has a name. It's a labor problem, not a pricing problem, and it's a different conversation with a different person.

Lumped together, problems hide

Lumped together, the material savings hid part of the labor overrun. Split, you can see both.

That matters for the next job too. If you only knew the job was $50,000 over, you might raise the whole price. But material was fine. The labor rate was the problem. Raising the material number would make the next bid less competitive without fixing anything.

Cost codes that follow the estimate

Cost codes that follow the estimate make this automatic.

If the estimate is built by cost code, and the field reports by the same codes, the comparison is built in. Every week, each code shows estimate versus actual. Labor by code. Material by code. No one has to rebuild the report.

The key is keeping the codes simple enough for the field to get right. Too many codes and the data gets worse.

Weekly, not at closeout

Tracking weekly is what makes the estimate useful. A job that's 40 percent complete and over on labor still has 60 percent left to fix. A job at closeout has nothing left to fix. Read labor hours against the estimate, every week.

Bring the numbers to a monthly job status meeting so the project managers, the controller and the owners see the same thing.

Make it a habit

The hardest part isn't the report. It's the habit. Someone has to look at it every week, and someone has to ask why when a cost code drifts.

Start tracking

Pick your next job. Build the estimate by cost code. Split the costs five ways. Compare weekly. When it closes, sit down with the estimator and look at what the field really did.

The ROOI exam asks about estimate tracking, job cost splits and 18 other systems. You'll see your score against same-size firms, the pretax profit at stake each year and the first step to close each gap.

Take the free ROOI exam

LinkedIn Facebook X

More on this