Most contractors believe their margin is decided at tender. The bid is priced, a margin is built in, and the job is then about protecting that margin through delivery. That belief shapes where attention goes: into estimating, into procurement, into productivity on site. It is also why so many UAE contractors finish projects materially below the margin they tendered without being able to point to the moment it was lost. The margin on a typical UAE project is not mostly decided at tender. It is decided afterwards, in the variation lifecycle, and the variation lifecycle is the part of the job most contractors do not instrument as a tracked object at all.
This piece is a perspective on why variations are where construction margin is actually decided, and why that is structurally invisible to most contractors. The argument is opinionated. We are not arguing that tendering does not matter, or that contractors are careless about change. We are arguing that on projects of any complexity the variation account moves margin more than site productivity does; that value leaks at every transition of the variation lifecycle, from identification through to payment; and that contractors who track cost and progress but not the variation as an object through its lifecycle are uninstrumented exactly where their margin is being set. The tender sets the starting margin. The variation lifecycle decides what is left of it.
The audience for this analysis is owners, commercial directors, and senior quantity surveyors of UAE contractors who tender disciplined margins and keep finishing below them without a clear account of where the erosion happened. The useful diagnostic question is not "was the job priced well" but "for every change on this project, can we say what state its variation is in, what it is worth, and how long it has been stuck, or do we only find out at final account".
How Variation Value Leaks Across Its Lifecycle
Below is the variation lifecycle shown as a value bridge: the proportion of a change's value still recoverable at each stage, from the moment it is identified on site to the moment it is paid. The point is not the specific percentages, which are illustrative; it is that value leaks at every transition that is unmanaged, and that the leaks compound, so a contractor that manages none of the transitions banks a fraction of the change value it was entitled to. Tap any stage to see where the margin leaks there and what tracking it changes.
The variation lifecycle as a value bridge
Tap a stage for where margin leaks there and what tracking it changes
Why the Variation Account Decides Margin
The reason the variation account moves margin more than the tender is the nature of change on a construction project. The tendered margin is a single number set once, against a defined scope. The variation account is a stream of events that accumulates throughout the job, each one an entitlement that is either captured cleanly or eroded by the way it is handled. On a project of any complexity the cumulative value moving through that stream is large relative to the tendered margin, which means the quality of variation management, not the quality of the original estimate, determines whether the contractor keeps the margin it priced. A well-tendered job managed loosely on change still finishes poorly.
The leaks are structural because each transition in the lifecycle has its own way of losing value. Work done on a verbal loses the instruction. Pricing submitted outside the contractual window is discounted on process. An agreed variation that is not carried into a certificate is agreement that never becomes cash. Under the FIDIC-family contracts common in the UAE, each of these transitions has a contractual form and a timing, and value that misses the form or the timing is not lost on merit; it is lost on handling. A contractor that does not track the variation as an object cannot see which transition each change is stuck at, so it cannot act before the value is gone.
This is why the failure is invisible rather than obvious. Cost and progress systems show the contractor what it has spent and built; they do not show the population of variations and where each one sits in its lifecycle. The erosion does not appear as a line item; it appears as a final account that is lower than expected, by which point every individual leak is closed. The contractor that is exposed here is not the one that priced badly; it is the one whose change is managed in diaries, emails, and spreadsheets, so the place its margin is decided is the one place it has no instrument pointed at.
The shift in one observation
A contractor that finishes below its tendered margin without knowing where it went usually did not lose it on site. It lost it across a variation lifecycle it never tracked as an object: a stream of entitlements eroded one unmanaged transition at a time. The tender set the margin; the handling of change spent it, invisibly, because nothing was watching the place it was actually being decided.
Where the Tender-Centric Model Breaks
The margin-is-set-at-tender model breaks in four predictable places over the life of a project.
Work done on a verbal
The most common leak is work that proceeds before the instruction is captured. Entitlement that exists in a conversation does not survive the project, and a contractor with no mechanism to open a tracked variation at the point of identification loses value before it is ever priced.
Pricing outside the window
A correct entitlement priced late is discounted or rejected on process rather than merit. Without a prompt tied to the contractual window, pricing slips, and the contractor argues substance while the other side declines on timing.
Variations that stall unagreed
The gap between submitted and agreed is delivered work the contractor finances indefinitely. Unmanaged, stalled variations are negotiated down to close them, and the contractor cannot see the ageing liability because nothing is tracking the agreement state.
Agreement that never becomes cash
An agreed variation not carried cleanly into a certificate, or eroded by retention and contra it cannot trace, is margin recognised and never banked. The handoff from commercial agreement to certified, paid value is the last and least watched leak.
The Numbers
Two Ways to Treat Variations
The difference between contractors who finish near their tendered margin and those who do not is whether the variation is a tracked object through its lifecycle or a thread across diaries and emails.
| Transition | Untracked thread | Tracked object |
|---|---|---|
| Identification | A note in a diary or a verbal. | A variation opened at the point of recognition. |
| Instruction | Work proceeds before it is captured. | Instruction recorded and linked before work proceeds. |
| Pricing | Late, discounted on process. | Prompted within the contractual window, basis attached. |
| Agreement | Stalls unseen, negotiated down to close. | Ageing visible, chased as a financed liability. |
| Certification and payment | Agreement that never becomes cash. | Linked through to certified, paid, retention-tracked value. |
Margin in UAE construction is widely believed to be won at tender and is mostly decided afterwards, one variation transition at a time. A contractor that tracks cost and progress but not the variation as an object is fully instrumented everywhere except the place its margin is actually being set.
What Tracking Variations as Objects Looks Like
The pattern in contractors who finish near their tendered margin is recognisable. Every identified change is opened as a tracked variation at the point of recognition, so nothing recoverable starts life as an untracked note. The instruction is captured and linked before work proceeds. Pricing is prompted within the contractual window with its basis attached. Each variation has a visible agreement state and ageing, so stalled value is chased as the financed liability it is. Agreed variations are linked through to the certificate and tracked to payment against retention and contra. The variation account stops being a final-account surprise and becomes a managed population the contractor can see and act on while the value is still recoverable.
This does not necessarily mean replacing the cost or commercial systems already in place. In many contractors the variation object and its lifecycle can be built around the existing systems, so change management becomes a tracked discipline rather than a reconstruction at final account. Replacement becomes the better option mainly where the existing systems cannot represent a variation as an object with a state and an audit trail. Which applies is specific to the systems in place, and is established in scoping before any build commitment.
How This Sits Alongside the Contractor's Own Responsibilities
The configuration keeps a clear separation. The contractor runs the works, prepares and owns its variations and claims, holds the relationships with the client, engineer, and certifier, makes every commercial and contractual decision, and is responsible for its own contractual compliance. The software is the instrumentation: representing the variation as a tracked object through its lifecycle so value is captured at each transition rather than reconstructed at the end.
This is the role BY BANKS is positioned for. We are an independent software engineering company based in the UAE. We design and build software and hand it over to the contractor who runs it. We do not prepare, price, or certify variations, give quantity-surveying or contractual advice, or act for any client, engineer, or certifier, and we are not affiliated with or endorsed by any of them. The contractor owns its variations, its commercial decisions, and its own compliance; we build the system that tracks the lifecycle the value moves through. The accountable party leads and owns the obligations; we build to their direction.
Where This Analysis Is Useful
The conversations where this perspective is most useful tend to be at three moments: a contractor that tenders disciplined margins and keeps finishing below them; a commercial director who cannot state, mid-project, the state and ageing of the variation account; or an owner reviewing a final account that is lower than expected and finding the erosion was a hundred small handling losses. The honest answer is usually the same: margin is decided in the variation lifecycle, the lifecycle is untracked, and the loss is invisible until it is closed.
For broader related work, see our perspective on the hidden cost of fragmented construction systems and our perspective on tender management in Dubai. The applied work sits across our construction cost tracking software, construction document management, and subcontractor management software capabilities, within the broader construction software practice and our operational platforms work. Get in touch if a 45-minute conversation about a specific variation account would be useful.
Frequently Asked Questions
No. We are an independent software engineering company based in the UAE. We design and build software and hand it over to the contractor who runs it. We do not prepare, price, or certify variations, give quantity-surveying or contractual advice, or act for any client, engineer, or certifier, and we are not affiliated with or endorsed by any of them. On any engagement, the contractor owns its variations, its commercial decisions, and its own contractual compliance. We build the system that tracks the lifecycle; the contractor and its commercial team own the variations themselves.
No. They are an observational illustration of how unmanaged variation value erodes across the lifecycle, not measured statistics, and they describe no specific project, contract, or determination. The point they make is that leaks occur at every unmanaged transition and compound, not that the erosion is any precise figure. Actual outcomes depend on the contract and the specific project.
No, and that is not the intent. Tracking the lifecycle does not create entitlement; it preserves entitlement that already exists by capturing the instruction, the pricing, and the agreement in time and in form. It does not support claiming work not instructed or not done, and it does not change what the contract entitles the contractor to. It changes whether genuine entitlement survives the handling rather than leaking away on process and timing.
Often not. In many contractors the variation object and its lifecycle can be built around the cost and commercial systems already in place, so change management becomes a tracked discipline rather than a final-account reconstruction. Replacement becomes the better option mainly where the existing systems cannot represent a variation as an object with a state and an audit trail. Which applies is specific to the systems in place and is established in scoping before any build commitment.
It is sequenced and does not require pausing the works. The usual starting point is the transition leaking the most on the current project, often instruction capture or the submitted-to-agreed gap, made into a tracked state from the next cycle so live value stops leaking first. The remaining transitions are brought in by order of value at risk. The order is driven by where the current variation account is bleeding most, which scoping establishes for the specific project.
Construction margin in the UAE is widely believed to be set at tender and is in practice mostly decided afterwards, across a variation lifecycle that most contractors never instrument as a tracked object. Value leaks at every unmanaged transition and the leaks compound, so a well-tendered job managed loosely on change still finishes poorly, and the loss is invisible until the final account, when every leak is already closed. The contractors who finish near their tendered margin are the ones who track the variation as an object through its lifecycle and act while value is still recoverable. The build is software work; the variations, the commercial and contractual decisions, and contractual compliance remain entirely the contractor's, and the system simply makes the place margin is decided visible while it can still be protected.
References to FIDIC-family contracts and UAE construction change-management practice are descriptive of publicly known frameworks. This article cites no market figures; the variation lifecycle and the retained percentages are an observational illustration, not measured statistics, and represent no specific project, contract, or determination. Patterns and observations reflect our perspective and are observational estimates rather than measured statistics. BY BANKS is an independent software engineering company; we do not prepare, price, or certify variations, give quantity-surveying or contractual advice, or act for any client, engineer, or certifier, and we are not affiliated with or endorsed by any of them. On any engagement, the contractor owns its variations, its commercial decisions, and responsibility for its own contractual compliance. This article is not contractual, commercial, quantity-surveying, or legal advice; contractors should obtain qualified advice for their specific obligations. Public sources used in this piece are listed on our Sources and Data page.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation