Labor Productivity and Earned Hours: The Early Warning Signal Many Contractors Miss

Labor Productivity and Earned Hours: The Early Warning Signal Many Contractors Miss

Why labor productivity deserves a seat in the Monthly Job Review

For labor‑intensive scopes, few things affect margin faster than labor productivity. And yet many teams still review labor primarily through a backward‑looking question: how many hours did we spend?

That matters, but it is not enough. A stronger question is: how many hours did we earn?

Earned hours and productivity variance help a team understand not just how much labor was spent, but whether that labor is producing at the level the job requires.

Earned hours in plain English

In simple terms, earned hours are the number of labor hours the team should have consumed based on the amount of work actually completed.

A simple version is:
Earned Hours = Budget Hours × % Complete

That allows the team to compare earned hours (what the work should have taken) to actual hours (what it actually took). The difference is the productivity variance.

Why this matters

A labor‑driven margin problem rarely appears all at once. It often starts with:

    • Lower‑than‑planned production
    • Crew inefficiency or poor sequencing
    • Rework or coordination issues
    • Access constraints or schedule pressure
    • Changes in crew mix

Those issues often show up in productivity before they fully hit the forecast. That is why earned hours can be such a valuable early‑warning tool.

What leadership should want to know
    • What were the budget hours?
    • How many hours have actually been spent?
    • How many hours have been earned?
    • What is the productivity variance?
    • Has the remaining forecast changed?
    • What action is required now—and who owns it?
What a useful productivity view should include
    • Phase/cost code
    • Budget hours
    • % complete or progress measure
    • Earned hours
    • Actual hours to date
    • Productivity variance
    • Forecast hours to complete
    • Notes on key constraints/drivers
Red flags to watch
    • Actual hours climb, but progress does not.
    • Productivity variance worsens month after month.
    • Forecast hours‑to‑complete stay flat despite poor performance.
    • The team talks about labor generally, but not quantitatively.

Take the next step

Labor productivity is not just a field issue. For labor‑intensive work, earned hours and productivity variance are some of the clearest management signals available—and that is why they deserve a consistent place in the Monthly Job Review packet.

Download the Monthly Job Review Toolkit to accelerate implementation.

If you would like a second set of eyes on your current packet, request a 15‑minute Job Review Packet Review.

  • A minimum viable packet definition (and meeting flow)
  • Templates that match the packet pages
  • Facilitator checklist and meeting form