A Low DLER Doesn’t Tell You Why

You pull the rolling twelve. You divide gross margin (for DLER this is revenue less material and subcontractor costs) by direct labor wages (for DLER this does not include fringe benefits or payroll taxes). The number comes back under your target, say you’re aiming for 3.5 and you landed at 2.9.

The instinct, almost every time, is to go to the field.

Crew’s too slow. Too much standing around. Somebody’s not pulling their weight. You start thinking about who to blame, and about what you’re going to say at the next production meeting.

Hold on.

That instinct is right maybe half the time. The other half, walking onto the jobsite to fix a low DLER is the worst thing you can do. The problem was never on the jobsite, and the people standing there know it.

I wrote a full piece on what DLER is and how to calculate it back in November, Labor Efficiency Ratios Define Profitability. If you’ve never run the number, start there. This post assumes you have it.

The short version: DLER is the gross margin remaining after material and subcontractor costs divided by the wages you pay the people doing the field work, before burden. It’s a multiplier, not a percentage. Higher means more gross profit per labor dollar. Your target comes out of your budget; overhead plus profit, divided back down into a number every labor dollar has to carry. That’s the number you set on the way in. The rolling twelve is the number you actually got.

This post is about what to do when those two numbers don’t match.

Here’s the thing almost nobody says about DLER. It’s a ratio. Gross margin on top, direct wages on the bottom. When the number is low, it can be low for two completely different reasons, and the ratio will not tell you which.

The top can be too small — you didn’t generate enough gross margin.

Or the bottom can be too big — you spent too much in wages for the output you got.

Same low number. Opposite problems. Opposite fixes. And the default assumption that a low DLER means the crew was slow only addresses one of them.

When I sit with a soft DLER, it’s almost always pointing at one of three things.

Sometimes it’s genuine field inefficiency. The margin was in the estimate and it leaked out during the build through rework, travel, waiting on a decision, cleaning up after a sequencing mistake, two trades in the same room tripping over each other. The hours went in and the output didn’t come out. This is the one everybody assumes. It’s real, and when it’s the cause, the fix is in production: sequencing, handoffs, decisions made before the crew shows up.

Sometimes it’s a pricing and mix problem. The margin was never in the estimate to begin with. You sold a labor-heavy job at a blanket margin that didn’t account for how much direct labor it would eat. The crew built it fine, efficiently even, and the number still comes back low, because there was never enough gross profit in the job to clear your labor. Going to the field here isn’t just useless. It’s corrosive. You’re putting a desk decision on the backs of the people who had nothing to do with it.

And sometimes it’s structural. The crew’s fine, the pricing’s fine, but the labor load has grown out of proportion to what you’re producing. You hired ahead of the work. You’re carrying a bench. Management time crept into direct labor without anyone deciding it should. More wage, same gross margin, ratio erodes.

Three causes. The first lives in the field, the second at the estimating desk, the third on the org chart. A low DLER looks identical in all three cases.

So before you act, you diagnose. And the question that sorts it is simple.

Was the gross profit there in the estimate?

Pull a job that came in light and compare its estimated DLER to its actual DLER. (If you don’t estimate DLER on the way in, that’s a separate fix and an easy but important one. You can’t tell erosion from underpricing if you never set a mark.)

If the estimate showed a healthy DLER and the actual came in low, your margin eroded during the build. That’s a field and production conversation.

If the estimate itself showed a low DLER because the job never had the margin in it, then no crew on earth was going to save it. That’s an estimating and pricing conversation, and the field is the wrong room to have it in.

And if it’s neither, if job after job estimates fine and builds fine and the company number is still soft, then it’s structural. You’re looking at capacity and head count, not any single job.

This matters more than a spreadsheet correction, because the cost of misreading the number isn’t just wasted time.

Walk onto a jobsite and start squeezing a crew over a number that a pricing decision caused, and you’ll fix nothing and lose trust doing it. The people in the field can feel the difference between we have a production problem to solve together and I’m blaming you for something that happened at a desk. Get that wrong enough times and your best people start updating their resumes.

DLER tells you the engine is underpowered. That’s all it tells you. It does not tell you whether the problem is the fuel you put in, the load you’re asking it to pull, or the machine itself. Finding that out is the actual work, and it’s worth doing before you say a word to anyone.

Run it, by all means. Run it on the rolling twelve so the seasonal noise washes out.

But when it comes back low, resist the reflex to go find someone to blame. Ask the quieter question first, where did the margin actually go, and was it ever there at all. The answer tells you which of the three problems you have.

And the three problems don’t share a fix.

This is my 42nd post on Nails to Numbers. The best part of writing it hasn’t been the writing. It’s been the people. Builders who read a post about GP/Day, or about a low DLER, and wrote back to say that’s me, that’s exactly where I am.

I know where they are because I’ve been there. I spent years running my own shop without really knowing whether it worked. I learned what I know about financials after a business of my own came apart, by going back and understanding the things I’d spent years avoiding. I didn’t come to these numbers as an accountant. I came to them as a tradesman who got buried by what he didn’t understand, and decided never to be there again.

That’s the work I want to help other people do. I’m opening up time to advise a small number of companies — owners who came up in the trades and can feel that the business is busy but can’t yet see where the money is or isn’t. Not to run your numbers for you. To help you build the systems and the habit of reading them, so that you own them and they don’t walk out the door with me when we’re done.

If that’s where you are and you’d like to talk about whether I can help, reply to this email or message me in the Substack app.

Thank you for being part of Nails to Numbers.

Ian