How Additional Work Weakens Margin
Why cost-plus pricing often protects effort but not economics
Additional work often feels commercially positive. More scope appears, more revenue follows. More gross profit dollars may even show up in the forecast. The job looks bigger, busier, and in some respects better than before.
That is where many teams stop reading.
The commercial problem is that additional work can improve revenue and still weaken the job. A project may recover cost, add contribution, and yet dilute the gross margin quality built into the base price. The issue is not whether the extra work is profitable at all. The issue is whether it is being priced in a way that protects the economics of the original deal.
That matters because margin protection does not only fail in execution. It can also fail at the rate table.
In many projects, additional work is still priced through a reflexive cost-plus approach. It feels practical. The work sits outside base scope. The effort has to be covered. The client expects a quick number. A markup is added and the rate is issued. Commercially, that often looks safe enough.
But cost recovery is not the same as margin protection.
If the base job was priced to deliver a certain gross margin standard, and the additional work is priced under a different commercial logic, the combined result can look stronger in revenue and weaker in quality. Leadership sees more turnover and more gross profit dollars. What is less visible is that the overall job has started earning at a lower margin standard than originally intended.
That is not an accounting curiosity.
It is a commercial control issue.
The Misunderstanding Starts With the Rate
A common mistake in additional work pricing is assuming that a percentage markup on cost will somehow preserve the same economic quality as the base scope.
Teams often talk about the extra work as if it is being priced at the same commercial standard simply because a familiar percentage has been added. In practice, the logic is usually different. The base price may have been built around target gross margin, risk allocation, productivity assumptions, asset utilization, and competitive strategy. The additional work, by contrast, is often priced faster, under pressure, and with a much narrower objective: recover the cost, add something on top, and move on.
That is how dilution begins.
The extra work may still be profitable. It may still add contribution. But if it is priced below the margin quality embedded in the base job, the blended commercial position weakens even while the topline grows.
This is one reason margin deterioration gets reported too late in projects. The project appears to be winning more work, the revenue line strengthens, and management takes comfort from visible commercial activity. Meanwhile, the quality of that revenue has already shifted.
Why Cost-Plus Feels Safe
Cost-plus is attractive because it looks defensible.
The work is outside scope. The team can identify labor, equipment, subcontractors, and consumables. A markup is added. The result appears transparent and commercially reasonable. In a live project environment, where decisions often need to be made quickly, that simplicity is useful.
It is also why teams fall back on it so easily.
A cost-plus structure can be entirely appropriate when the priority is speed, recoverability, or provisional commercial treatment. The problem begins when that short-term convenience is mistaken for a margin-protection mechanism.
Cost-plus protects cost recovery first. That can be good discipline as far as it goes. But base pricing is rarely built on cost recovery alone. It is built on a commercial model that includes target margin, risk posture, productivity expectation, asset strategy, and the desired quality of the revenue being booked.
Additional work priced outside that logic may recover the effort and still erode the blended commercial outcome.
That is the trap.
More Revenue Does Not Automatically Mean a Better Project
One of the reasons this issue is under-read is that the visible numbers can still look favorable.
Revenue rises. Gross profit dollars rise. The project team points to recognized additional work. The forecast may even improve in absolute terms. On paper, it can look as though the job is strengthening.
But a larger job is not always a better job.
If the base scope was priced at one margin standard and the additional work is sold at another, lower one, the total gross margin percentage begins to drift. Commercially, that matters for two reasons.
First, it weakens the original economic quality of the project. The job may still produce more money overall, but at a lower standard than the one the business intended to achieve when the contract was won.
Second, it distorts management interpretation. Leadership may see more revenue and more contribution and conclude that the change environment is helping the job. The underlying reality may be narrower: the project is growing, but not on terms that protect its original margin standard.
That is not the same thing.
A project can become more active commercially while becoming less attractive economically.
The Real Issue Is Blended Margin Quality
This is the better management lens.
The question is not simply whether the additional work is profitable on its own. The better question is what that pricing logic is doing to the combined economic profile of the job.
That means looking at the quality of the blended result.
If additional work is priced at a lower commercial standard than the base scope, the project may start carrying more revenue, more absolute gross profit, and a weaker blended gross margin.
That is a much more useful reading than “the variation made money.”
In live projects, where additional scope is often executed under pressure and under different productivity conditions, this matters even more. The work may be harder, more fragmented, less efficient, or more disruptive than the original sequence. If the pricing logic is weaker at the same time, the project does not just carry execution pressure. It carries economic dilution as well.
This is where project controls and commercial discipline need to stay connected. A team can track the change order correctly and still miss what the rate structure is doing to the overall margin profile of the work.
Why This Happens So Often in Projects
There are several reasons teams drift into this.
One is urgency. The project is live, the work cannot wait, Commercial treatment has to keep up with operations, and cost-plus feels faster than rebuilding a proper commercial rate logic.
Another is false comfort. A markup looks like discipline. It creates the impression that the additional work is being handled commercially when the more important question, whether the economics are being protected, is left unasked.
A third is organizational separation. Tendering may have built the base job around one set of commercial assumptions, while the project team handles additional work under another. The original price logic is no longer active in the day-to-day treatment of changes. That gap is where dilution enters.
This is part of a broader project pattern. A deal may be won with one commercial standard, then executed and expanded with a different one. Unless that shift is visible, management keeps reading the project as though the original economic logic still governs all of the revenue.
That is also why project delivery cannot be treated as a simple execution exercise once the work is live. The project team is not only executing scope. It is also making repeated commercial decisions that affect the quality of the job.
Protecting Margin Starts Earlier Than the Change Order Review
The strongest response is not to argue about the dilution later, it is to prevent it at the front end.
If additional work is likely, the project should already have a view on how extra work rates will protect the intended economics of the job. That does not mean every change must be priced through a slow or elaborate tender logic. It means the organization should be clear about the commercial standard it is trying to defend.
That requires a different question when the rate is set.
Not: how do we recover the cost quickly?
Better: how do we price this in a way that protects the margin quality the job was meant to earn?
That one shift changes the discipline considerably.
It pushes the team to think about:
target gross margin, not only markup
whether the added work is being sold under weaker assumptions than the base scope
whether urgency is creating a commercial shortcut
whether the rate reflects the real economic and operational burden of the work
whether management is about to book more revenue at a weaker standard than it realizes
That is where margin protection starts.
At the rate-setting stage.
The Governance Angle
The reason this issue persists is that it often sits between functions.
Commercial teams may understand the pricing distinction. Project teams may focus on getting the work authorized and moving. Finance may see higher revenue and more gross profit dollars. Leadership may not see immediately that the blended gross margin is softening.
That is why the issue belongs inside governance, not only inside commercial working notes.
Someone must ask:
what margin logic governed the base job
what logic is now governing the additional work
whether the two are commercially aligned
and what the combined effect is on the project’s economic quality
Without that, more revenue is too easily mistaken for stronger performance.
This is also where better project intelligence starts to matter. The business does not only need visibility on whether extra work has been priced. It needs visibility on whether that pricing is strengthening the job or quietly diluting it.
Closing View
Additional work does not automatically protect margin.
It may recover cost. It may add revenue. It may even increase gross profit dollars. But if it is priced under a weaker commercial logic than the base scope, the project can still become economically worse while appearing commercially busier.
That is the hidden problem.
The commercial mistake is not failing to price additional work. It is pricing it in a way that recovers effort while quietly diluting the margin standard the job was meant to earn.
That is why margin protection on extra scope starts at the front end.
The rate is not just a recovery mechanism.
It is a decision about the economic quality of the job.
