Custom software development for businesses across Dubai, Abu Dhabi & Sharjah — book a free consultation →
← All posts

Bidding · January 2026 · 5 min read

LDs, escalation and advances: the fine print that eats margins

Two tenders with the same value can have very different economics. The difference is in payment schedules and penalty rules.

Put two tenders side by side, each with the same headline value — say AED 100 million — and most bid meetings will treat them as the same size of opportunity. They almost never are. One pays on time, shares inflation risk and funds your mobilisation. The other holds your money, penalises every slip and leaves you carrying years of price movement alone.

The difference is not visible on the cover page. It sits in the fine print — liquidated damages, escalation formulas, advance rules and payment schedules — applied month after month over a multi-year project. That fine print, not the contract value, decides what a tender is actually worth to the company that wins it.

Reading it is not the problem; every serious contractor reads it. The problem is arithmetic. These clauses interact, over years, and their combined effect on margin is not something intuition can hold. It has to be modelled.

Liquidated damages: pricing your own delay

Every EPC contract carries an LD clause, and every bid team has read one. Far fewer bids actually price it. LDs accrue for each period of delay up to a cap, which means the honest question at bid stage is not whether the project might slip, but by how much, where, and what that costs under this contract's particular numbers.

Suppose a clause deducts a small fraction of contract value for every week beyond a milestone, up to a capped total — survivable on paper. Modelled against a realistic schedule, with summer midday-break months, site handover delays and authority approval cycles where they usually fall, the likely deduction can be a large share of the margin you think you are bidding with.

That is not a reason to avoid the tender. It is a number you need before you sign, not after — because it may change your price, your schedule contingency, or your decision to bid at all.

Escalation: who carries the inflation

A multi-year project is a position on prices — steel, cement, fuel, labour. Escalation clauses decide who holds that position. Some contracts adjust your payments through an indexed formula as input costs move; others fix your price on the day you bid and leave every dirham of movement with you.

Two tenders of identical value can sit on opposite sides of that line. On one, a price rise is substantially the client's problem; on the other, it is entirely yours for the duration. Bidding both at the same margin is not consistency — it is not knowing which contract you are signing.

The formula's details matter as much as its existence: which indices, which base month, which components of the work it covers and which it quietly excludes. Those details are exactly the kind of thing a crowded bid week skips.

Advances and payment schedules: cash has a price

A mobilisation advance is not free money — it is recovered — but its presence changes the economics of the first year completely. With an advance, the client funds your start. Without one, you fund it yourself, with borrowed money at your own cost of funds, before the first payment arrives.

Payment schedules do the same quiet work across the whole project. Milestone payments, measurement and certification cycles, retention held to completion — each rule sets how long your money stays inside the project before it comes back to you.

Two contracts can pay an identical total and demand very different amounts of working capital along the way. Working capital is never free, so the difference lands, invisibly, on margin — unless the schedule is modelled as cash over time rather than skimmed as a table on page forty.

The clauses work on each other

The reason intuition fails here is that the clauses interact. A slipped milestone does not just trigger LDs — it stretches your escalation exposure into another price year, pushes payments further out, and lengthens the period your working capital sits inside the project.

So the true cost of one month of delay is not one line of the contract; it is the sum of what that month does across all of them. A bid that prices each clause separately, in isolation, will still miss the number that matters — the combined effect on margin when the project goes the way projects actually go.

This is why modelling beats checking. A checklist confirms every clause was read. A model shows what the clauses do to each other over three or four years, under the schedule you honestly expect rather than the one on the bar chart.

Each sector writes its own fine print

These rules are not random, and that is the useful part. They follow sector patterns. Roads, utilities, buildings and marine tenders each have their own habits — how LDs are framed, how escalation is indexed, what advances are offered, how payments are staged and retained.

A contractor bidding across sectors cannot carry one mental model between them. The clause that was standard in your last road project may be missing from the water tender on your desk, and the absence is worth real margin. Sector-wise modelling is not sophistication for its own sake — it is simply reading each contract in its own language, with the patterns of that sector as the starting point.

Know the real number before the bid meeting

None of this arithmetic is exotic. It is just long — many interacting rules projected over the life of a project — which is why it rarely gets done properly in the crowded week before a submission deadline. So the bid meeting falls back on headline value, a standard margin and experience, and the fine print gets priced by hope.

This is the problem a bid-economics engine exists to answer: modelling payment schedules, LDs, escalation and advance rules per sector, across roads, utilities, buildings and marine works, for UAE government and private tenders. The intent is exactly what this article argues for — see the real margin before you commit to it, while the decision is still yours to make.

It is the same approach we bring to every sector we build for: find the rules the business actually runs on, put them into working software, and let your people make the judgement calls with the arithmetic already done. Winning work is straightforward. The discipline is making sure you are not winning losses.

Know your real margin before you bid.