What causes margin leakage in project-based businesses?
Margin leakage occurs when the economics of a job deteriorate between the original quote and final close. Common causes include scope growth, crew substitutions, overtime, travel changes, late cost capture, unapproved expenses, underbilling, rate mismatches, and disconnected approvals. The best control is to surface the change while the job is still active.
- Margin leakage is usually cumulative rather than one dramatic event
- Late cost capture can hide deterioration
- Committed work should be reflected in the forecast
- Revenue leakage and cost leakage can happen together
- Exception-based review creates earlier intervention
Margin leakage is the gap between the economics a project was expected to produce and the economics it actually produces after operating changes accumulate.
It rarely comes from one dramatic mistake. More often, ten small changes happen after the quote: a role gets upgraded, hours run long, travel changes, an expense is approved informally, a client request expands scope, or a customer charge never makes it onto the final invoice.
The result is a job that still looks busy and successful operationally but finishes below its target margin.
1. Scope grows without an economic reset
A customer request may sound small in isolation: another deliverable, an earlier call time, an additional location, more revisions, another staff role.
The margin problem appears when the operating team treats the change as minor but the cost model never changes.
For fixed-price work, every unpriced addition transfers more delivery cost to the operator.
2. Crew substitutions change the rate mix
Project businesses with rotating crews are especially exposed to late labor changes.
A replacement may have a higher day rate. A specialized role may be required. Overtime may become unavoidable. Travel may be added. The final person filling the role may not match the economic assumptions used when the job was quoted.
Track the expected cost of the actual crew plan, not only the original staffing budget.
3. Overtime and extended hours arrive gradually
One extra hour does not look material. Repeated across ten people, multiple days, or several jobs, it can become the difference between hitting and missing the target margin.
The control is not to eliminate legitimate overtime. It is to make its economic effect visible while decisions are still being made.
4. Costs are recorded after the operating decision
A job can look healthy simply because the data is late.
If contractor work has already been accepted or completed but the cost is not visible until payout, invoice receipt, or month-end reconciliation, the reported margin is temporarily overstated.
For operating purposes, include supported committed or projected exposure in the forecast.
5. Approved expenses bypass the job budget
Travel, rentals, rush fees, supplies, permits, and reimbursements are often individually reasonable. The leakage occurs when they are approved in email, text, or chat but never connected back to the job economics.
Every project-specific approved cost should have a path back to the project.
6. Underbilling creates revenue leakage
Margin can deteriorate on the revenue side too.
Examples include:
- approved customer additions never invoiced,
- reimbursable expenses omitted from billing,
- milestone changes not reflected in the invoice schedule,
- rate changes not carried into the final billing record.
A profitability review should therefore ask whether both expected cost and expected revenue are current.
7. Discounts and credits happen after the quote
A late customer concession can reduce the economic return even when delivery cost is unchanged.
If a discount, credit, or write-off becomes likely, the profitability forecast should reflect it rather than waiting for the final accounting entry.
8. The team reviews actuals but not cost to finish
Actuals answer what has already happened. They do not answer what remains likely to happen.
A job at 60 percent completion can be within budget today and still be heading toward a miss if the remaining staffing plan is more expensive than expected.
Review:
- actual direct cost,
- committed exposure,
- expected remaining cost,
- expected revenue,
- forecast margin.
9. Nobody owns the exception
A dashboard can identify a problem without causing an action.
A useful margin-control workflow should show:
- which job is outside tolerance,
- what changed,
- the financial effect,
- who should review it,
- the next operational decision.
That is the purpose of the margin leakage control page and Kelvaro Margin: move from retrospective explanation to a live exception queue.
Build a margin leakage review around evidence
A practical weekly review can be short.
For each flagged job, ask:
- Is the revenue assumption still valid?
- Has labor or vendor exposure changed?
- Are all approved costs connected to the job?
- Is the cost to finish realistic?
- Is there still time to change staffing, scope, price, or execution?
The goal is not to optimize every decimal point. It is to find material deterioration while options still exist.
Frequently asked questions
What is margin leakage?
Margin leakage is the loss of expected profit between the original job economics and the final result because revenue, cost, or both move unfavorably during execution.
Is margin leakage the same as going over budget?
Not exactly. A job can exceed one cost budget while still protect its margin through higher revenue, or stay within a cost budget while underbilling reduces margin. Margin leakage considers the full job economics.
How often should project margins be reviewed?
The right cadence depends on how quickly jobs change. Fast-moving event, production, tour, and field-service work may need exception monitoring during the job rather than waiting for a monthly close.