The Losing Job You Won't Stop | Build Better Daily

Construction business owners at $2-10M revenue already know which jobs are losing money. You're not waiting for them to turn around—you're protecting your ego from the conversation you should have had two months ago.

TL;DR — What You Need to Know:

The loss is already real; avoidance just makes it bigger
You're spreading the loss across time hoping it'll hurt less—it won't
Every week you wait steals attention from everything else that could be fixed
Acknowledging the loss doesn't create it; it stops the bleeding
The conversation you're avoiding is the only thing that protects the business

Why do construction owners let losing jobs continue?

Because acknowledging the total loss feels more violent than watching it bleed weekly.

A job losing $20,000 per week doesn't trigger the same gut punch as recognizing you're $160,000 down total. So you attend the meetings. You nod at the recovery plan everyone knows is fantasy. You approve overtime to "get it done faster"—which just bleeds faster.

You're not stupid. You've done the math in your head during the drive home. You see the hours piling up in your Work-in-Progress (WIP) reports. You feel the tension when that project manager gives you the update that sounds fine but isn't.

But you're caught in a loop of justification:

"It's almost done"
"We're too far in to eat the loss now"
"If we just push through the next phase it'll balance out"
"The client will understand when we show them the extras"

None of that is true. And you know it.

What is actually happening when you avoid the loss?

You're spreading the loss across time hoping it'll hurt less—like paying off a credit card in tiny increments while the interest keeps compounding.

According to GAAP (Generally Accepted Accounting Principles), revenue recognition in construction requires percentage-of-completion accounting for contracts. This means losses should be recognized immediately and in full when they become apparent—not spread across future periods.

But here's what actually happens in your business:

Week 1: Job is $20K over budget. "We'll make it up."

Week 4: Job is $80K over. "Too far in to stop now."

Week 8: Job is $160K over. "Let's just finish it."

Meanwhile, you're:

Bidding new work
Talking about growth
Planning equipment purchases
Focusing forward because it feels better than turning around and facing the burning building behind you

The losing job doesn't just cost money. It costs management attention, crew morale, and decision quality across every other part of your business.

What does this avoidance actually cost your business?

The Construction Financial Management Association (CFMA) benchmarks show that gross profit margins in construction average 10-15% for general contractors. A single project losing $160,000 requires $1.1 to $1.6 million in additional revenue at 10-15% margins just to break even.

But the visible loss is only part of the damage:

Attention theft: While you're managing the losing job, you're not fixing the estimating process that bid it wrong, not addressing the PM who can't manage scope, not having the conversation with the client about the change orders you should have submitted months ago.

Crew demoralization: Your best people know the job is a disaster. They watch you pretend it's fine. They stop trusting your judgment on other projects.

Cash flow compression: The job burns working capital every week. According to IRS regulations, you still owe payroll taxes on those hours—even if the job never pays you back.

Decision paralysis: You can't make clear calls on new opportunities because you're hemorrhaging cash on the old one.

Why does acknowledging the loss feel impossible?

Because somewhere in your head, you believe that acknowledging the loss makes it real, makes it your fault, makes it a failure.

The loss is already real. The fault is already distributed. The failure is already baked.

The only thing your avoidance is doing is:

Making the loss bigger
Stealing your attention from fixes that matter
Training your team to ignore problems until they're catastrophic

You're not protecting the business by not looking. You're protecting your ego from a conversation.

Here's the truth most people avoid: the conversation you're scared to have is the only thing that stops the bleeding.

What actually happens when you face the loss?

You call the meeting you've been avoiding. You put the real numbers on the table—not the "it might still work out" numbers, the actual cash out vs. cash in numbers.

You say: "This job is losing $X per week. We're $Y down total. Here's what we're doing about it."

Then you do one of three things:

1. Kill it immediately (if contract terms allow): Negotiate an exit, eat the loss, redeploy the crew to profitable work. Sometimes the fastest way to stop bleeding is to amputate.

2. Stop the bleeding (if you must finish): Cut all overtime, reassign your best PM to something that makes money, put your B-team on finish-out duty. Stop pretending this job deserves A-player attention.

3. Have the scope conversation (if legitimate extras exist): Document every change, submit the change orders you should have submitted weeks ago, and stop working on faith that "the client will understand."

Under GAAP percentage-of-completion accounting, you're required to recognize losses immediately. This isn't just accounting theory—it's forcing function for operator reality. The books should reflect what you already know in your gut.

What will derail you even after you acknowledge the loss?

The same thing that got you here: ego protection dressed up as business strategy.

You'll be tempted to:

Blame the PM (instead of fixing the estimating process that set them up to fail)
Blame the client (instead of acknowledging you agreed to a bad contract)
Blame the crew (instead of recognizing you approved the overtime that accelerated the bleed)

Here's what actually helps: name the real failure point.

Was it:

Estimating that missed scope?
PM who couldn't manage changes?
Sales that agreed to impossible terms?
You, for not calling the meeting two months ago when you first felt the tension?

The answer is probably "all of the above." The point isn't to distribute blame—it's to fix the system that created the problem.

How do you prevent the next losing job?

You don't need ten steps. You need one forcing function.

Institute a weekly WIP review where every job over budget by more than 5% gets a two-minute drill:

Current loss amount (cash basis, not accrual fantasy)
Expected total loss if nothing changes
One action to stop or slow the bleeding
Name attached to that action
Deadline (7 days max)

No explanations. No excuses. No "it's complicated."

If a job shows up on this list three weeks in a row with no improvement, you don't have a job problem—you have a leadership problem. Either the PM can't execute, or you can't make the hard call.

Cash is the truth teller. Everything else is narrative.

Bring This to Your Leadership Meeting

The Question (forces alignment): "Which job are we keeping alive right now that we all know should be killed or radically changed?"

The Prompt (forces clarity): "Go around the table. Everyone names the one project they think is bleeding the most—no explaining, no defending. Just name it. If we hear the same job twice, that's the one we address first."

The Action (forces ownership): "By Friday, [Name of PM or Owner] will calculate the true cash loss on [specific job] and present three options: kill it, stop the bleeding, or submit the change orders. We decide Monday which option we execute."

The job is already losing money. Your avoidance isn't protecting anything—it's just making the loss bigger and stealing your attention from everything else that could actually be fixed.

You don't need courage to acknowledge the loss. You need clarity. The loss is already real. The only question is whether you're going to stop it this week or let it run another month.

Peace comes from facing what's true, not from pretending it might still work out.