# Budgeted vs actual productivity: why there is always a gap

> Budgeted productivity is an average under standard conditions. The actual figure almost never matches. How much of a gap is normal, and when it stops being normal.

- Author: Carlos Pérez (Comandos) — CEO of Paladio
- Published: 2026-08-10
- Original: https://usepaladio.com/en/blog/rendimiento-presupuestado-vs-real/
- Productivity

---

Budgeted productivity is the output figure assumed when the unit price of a line item was calculated. It is an average built from historical data, cost manuals or experience, under conditions considered normal. Actual productivity is what your crew really produces on your project. They are almost never equal, and that gap is the margin of the line item.

There is a scene that repeats on every project. The site engineer reports the crew is doing fine. The technical office reviews the month-end cut and the line item comes in 20 % over budget. Nobody lied: the two are looking at different numbers.

## Where the unit-price figure comes from

That productivity is not a measurement of your project. It comes from one of three sources, and each has its bias.

1. **Cost manuals and databases.** Broad averages that assume standard conditions. Useful as a starting point, blind to your specific context.
2. **Company history.** Much better, if it is genuinely being measured. In most contractors, "history" is what someone remembers about a similar project three years ago.
3. **The estimator's judgement.** A number that reflects real experience — and also the pressure that the bid has to win. Optimistic productivity lowers the price and improves the odds of award. It is a structural bias and it is worth naming.

In all three cases, budgeted productivity describes an average project. Yours is not one.

## The seven reasons for the gap

1. **Learning curve.** The first weeks of any line item yield less. The crew settles in, finds its rhythm, sorts out access and hauling. The analysis assumes steady state; the project starts at start-up.
2. **Repetitiveness.** A hundred metres of identical wall in one run yields far more than the same hundred metres spread across six fronts with different geometries. The analysis does not distinguish.
3. **Height and hauling.** The same line item at ground level and on level 8 does not cost the same. If the schedule of rates does not separate by level, productivity degrades as the building rises and the budget never allowed for it.
4. **Interference.** Another crew occupying the front, a service that arrives late, scaffolding that has to be moved. The analysis assumes a clear front. The real project almost never has one.
5. **Material quality and availability.** Chipped block, mortar with irregular mix, partial deliveries. All of it is paid for in labour time.
6. **Crew composition and experience.** The analysis assumes a standard crew. If your mason has two years of experience and the budget assumed ten, the difference is real and it is predictable.
7. **Weather and working hours.** Extreme heat, rain, short shifts due to restricted access hours. All of it cuts effective hours inside a nominal working day.

## How much of a gap is normal

No standard sets it, but as a working frame:

| Deviation vs budget | Reading |
|---|---|
| 0 to 10 % | Normal noise. No action required. |
| 10 to 20 % | Expected, especially at start-up. Watch the trend. |
| 20 to 30 % | A signal. There is an identifiable cause and it is worth finding. |
| Over 30 %, sustained | Either the analysis was wrong, or there is a real execution problem. |

The key word is **sustained**. One week at 35 % may be a bad week. Four weeks at 35 % is a structural deviation, and the difference between catching it in week 2 or week 8 is the whole difference between fixing it and explaining it.

## What to do when the gap appears

1. **Check you are comparing like with like.** It is surprisingly common for the field unit of measure not to match the schedule of rates, or for the executed quantity to include work the line item does not cover. Before concluding the crew is underperforming, confirm that numerator and denominator correspond.
2. **Separate productivity from interference.** If the crew performs well on the days it works but loses two days in every ten waiting for material, the problem is not the crew. It is a logistics problem and it is solved elsewhere.
3. **Decide whether you are fixing execution or fixing the forecast.** They are two different paths and the choice has to be deliberate. If the cause is removable — access, supply, sequence — you fix it and productivity rises. If it is structural — the analysis assumed conditions this project will never have — the honest move is to update the schedule and cost forecast with actual productivity, and to raise it early. A delay announced in week 3 is a scheduling problem. The same delay discovered in week 12 is a crisis.
4. **Keep the data.** The actual productivity measured on this project is the best possible input for pricing the next one. Most contractors waste this information because it is never recorded in a way anyone can query. It is the cheapest cumulative advantage in this business and almost nobody takes it.

## Frequently asked questions

**Should I update the unit-price analysis mid-project if actual productivity differs?**

The contractual analysis is normally not amended: it is the basis of the agreed price. What you do have to update is your internal cost and schedule forecast. They are two different documents and confusing them is an expensive mistake: one is what you will bill, the other is what it will cost you.

**Is actual productivity better than budgeted good news?**

Almost always yes — it is margin. But it is worth checking that speed is not being won at the expense of quality, because rework shows up later and is paid in full.

**How do I justify a productivity deviation to the client?**

With a dated record. Lost days with their cause, front conditions, late material deliveries — all documented at the moment it happened. A deviation explained with contemporaneous evidence is a conversation; explained from memory three months later it is an argument you lose.

**Is it worth measuring productivity on small line items?**

If they account for less than 2 or 3 % of the budget, the measuring effort does not pay for itself. Concentrate measurement on the line items that concentrate the cost. The Pareto rule applies with fair accuracy.