How to Score a UAE Developer's Track Record: Formula and Numbers

What a Track Record Actually Measures

A developer's track record is not a reputation; it is a set of measurable behaviours across past projects. Did projects finish on or near their contracted dates? How deep were the delays that did occur? Did the delivered product match the brochures, and how did the buildings behave after handover — snagging volumes, defect response, service charge stability? And what happened to buyers who wanted to sell at completion: did early purchasers meet a ready market at or above their contract price, or a discount?

Those questions decompose into five scoreable dimensions: on-time delivery, delay depth, handover quality, payment and registration discipline, and resale behaviour at handover. The market's household names — Emaar, Nakheel, Damac, Sobha, Aldar and the other established masters, alongside a long tail of newer entrants — differ less by whether they score well on every dimension than by which dimensions they score well on, and a fixed scoring model is how you see that instead of feeling it.

One caution frames everything that follows: the numbers in this article are an illustrative worked example, built to show the arithmetic, not a statistic about any real developer. You will collect your own inputs from your own candidate's project history. The formulas are the durable part; the inputs are your homework, and the next sections show exactly how to run both.

Formula One: On-Time Delivery Rate

The formula: on-time delivery rate equals the number of projects delivered on or before their contracted handover date, divided by the total number of delivered projects, multiplied by 100. A contracted date means the date in the sale and purchase agreement, not the date in a marketing update, and delivered means title issued or handover completed — not 'substantially complete' as described in a newsletter.

Worked example, entirely illustrative: a developer has delivered six projects. Two finished on or before contract. The rate is 2 divided by 6, times 100, which is 33 per cent. That number is a fact about the sample; interpreting it is where discipline enters, because a 33 per cent rate across six projects tells you something real, while the same rate across two projects tells you almost nothing.

Sensitivity is the point buyers skip. With five delivered projects, a single delay moves the rate by 20 percentage points, so any developer with fewer than five delivered projects has a rate too unstable to score — read their escrow, registration and contractor quality instead. With ten or more, the rate stabilises enough to compare across developers, and the comparison becomes genuinely informative: the spread between UAE developers' on-time behaviour is wide, and it is visible to anyone who collects the dates.

Formula Two: Delay Depth and the Ugly Tail

Two developers can share the same on-time rate and live different realities: one runs two months late when it runs late at all, the other misses by a year and a half. Delay depth captures that. The formula: average delay in months equals the sum of months beyond contracted handover across all delivered projects, divided by the total number of delivered projects — counting the on-time ones as zero.

Continuing the illustrative example: the six projects finished 0, 0, 3, 7, 12 and 15 months beyond contract. The sum is 37 months, divided by six, which is roughly 6.2 months of average delay. The average alone understates the risk, so read the tail too: the worst project ran 15 months late, and a buyer who planned a mortgage start, a rental expiry or a school year around that project lived the difference between an average and a tail.

The pairing of the two formulas is what makes them useful. On-time rate measures how often the developer's promises hold; delay depth measures how badly they bend when they do not. A developer with a moderate rate and shallow delays is a scheduling risk you can underwrite with buffer; a developer with a similar rate and a 15-month tail is a different proposition entirely, and the formulas separate them in a way that adjectives never will.

Payment Discipline: Escrow, Oqood and Change Orders

Delivery is only half the record; the other half is how the developer handled buyers' money and registrations along the way. Dubai off-plan operates inside a protective framework — escrow accounts are mandatory under Law No. 8 of 2007, tying construction funding to progress, and Oqood interim registration records each buyer's interest with the Dubai Land Department before a title deed exists. A developer's historical behaviour inside that framework — compliance, timeliness, transparency on cancellations and refunds — is among the most predictive facts available about a newer project.

Score it mechanically. Five criteria, each worth two points: escrow compliance on past projects; registration discipline, meaning Oqood or equivalent interim registration issued promptly across the construction period; change-order restraint, meaning specifications honoured rather than reissued; service charge stability at past handovers, because a developer who handed over buildings into charge chaos left evidence; and litigation history with past buyers, read for pattern rather than existence. The maximum is 10, and any zero deserves a written explanation before you proceed.

For the illustrative Developer X: escrow compliant, 2; registrations prompt, 2; change orders — specifications reissued twice mid-construction, 0; service charges stable across handovers, 2; litigation pattern none beyond routine disputes, 2. That is 8 out of 10, and the zero is the interesting cell: change-order behaviour is the dimension buyers feel earliest and weigh least, and a developer who reissued specifications twice may do so again on the project you are considering.

• Escrow compliance on past projects: accounts in place, progress-linked drawdowns, 2 points.
• Registration discipline: Oqood or equivalent interim registration issued promptly through construction, 2 points.
• Change-order restraint: specifications honoured rather than reissued mid-construction, 2 points.
• Service charge stability at past handovers: no chaos or surprise levies in the first years, 2 points.
• Litigation history with past buyers: read for pattern, not existence, 2 points.

Handover Quality: Snagging, Defects and Resale Behaviour

Quality scores from two documents buyers can actually obtain: snagging reports and defect records. Snagging reports from past projects — independent inspectors publish anonymised examples, and buyers of earlier phases share theirs — show typical defect volumes per unit and the categories that repeat. The defect liability period record shows whether the developer closed items within the window or negotiated every fix. Illustratively, a project averaging a dozen or so snag items per unit with around 90 per cent closed inside the liability period is a defensible mid-band score of 6 out of 10.

Resale behaviour completes the quality picture from the market's side. At handover, early off-plan buyers sometimes test the market, and what they achieved against ready comparables is a fact worth collecting: illustratively, if handover-era resales in a developer's past project cleared around 5 per cent below equivalent ready stock, that is a scoreable event — it says the market charged something for the gap between render and reality, and that discount is part of the true cost of buying from this developer.

None of these quality measures requires insider access. Inspection reports circulate, handover-era listings on the major listing portals leave price traces, and owners' groups in delivered communities are forthright about how the first two years went. The buyer who collects quality evidence from a developer's three most recent handovers holds a better picture of the next handover than any brochure can offer — and holds it before the deposit, which is the only time it has any negotiating value.

Weighting the Score: A Worked Composite and Its Sensitivity

Assemble the dimensions into one number with defensible weights. The worked model here uses: on-time delivery 25 per cent, delay depth 15 per cent, handover quality 25 per cent, payment discipline 20 per cent, resale behaviour 15 per cent. Convert each dimension to a 0-10 score — the illustrative mapping scores on-time rate as rate times 10, and delay depth as 10 minus the average months of delay, floored at zero — then run the weighted sum.

Developer X's arithmetic, all illustrative: on-time 33 per cent scores 3; delay depth of 6.2 months scores 4; quality scores 6; payment discipline scored 8; resale behaviour, with that illustrative 5 per cent handover-era discount, scores 5. The composite is 0.25 times 3, plus 0.15 times 4, plus 0.25 times 6, plus 0.20 times 8, plus 0.15 times 5 — which is 0.75 plus 0.60 plus 1.50 plus 1.60 plus 0.75, or 5.2 out of 10. Read as a band, that is mid-table: proceed to deeper diligence rather than walking away.

Now the honesty step most scoring models skip: sensitivity. Move 15 points of weight from payment discipline to on-time delivery — a defensible preference — and the composite drops from 5.2 to roughly 4.45, a swing of three-quarters of a point from judgement alone. That is the proof that the composite ranks investigations rather than issuing verdicts: use it to order which developers deserve the deeper file, and let the underlying evidence — the tail delay, the change orders, the statements — make the final call.

Where to Find the Inputs Without Guessing

Every input in the model has an official or documentary source, and none requires special access. Project registrations, licences and completed-project histories sit with the land departments — the DLD's channels in Dubai and their counterparts in the other emirates — and escrow status for a specific Dubai project is confirmable through official channels rather than sales-lounge assurances. Oqood records confirm registration behaviour across a construction period, and title deed issuance dates for past phases establish the contracted-versus-actual handover gap that Formula One and Two consume.

The behavioural inputs come from the market's own traces. Snagging reports from earlier phases circulate through inspectors and owners' groups; service charge statements from delivered buildings show what handover governance actually looked like; and handover-era asking and achieved prices, visible through the major listing portals and recorded transactions, supply the resale-behaviour input. None of these sources will volunteer itself — but all of them can be requested, and a developer's sales team that obstructs basic documentary questions has answered one of them already.

Rules, fee schedules and registration processes do get revised, so verify the current framework with the Dubai Land Department, RERA or the relevant emirate's authority as part of the same exercise. The diligence hour that produces your scoring inputs is also the hour that confirms the protective framework around the specific project — escrow in place, registration current, approvals live — and those confirmations are worth as much as the score they feed.

Your Developer Diligence Checklist

The model compresses to an afternoon of work per shortlisted developer, and the order matters: assemble the delivery history first, because sample size decides whether scoring is even meaningful; then run the formulas; then collect the behavioural evidence that the numbers alone cannot carry. A developer with two delivered projects is scored on discipline and escrow, not on rates; a developer with ten is scored on everything, and the comparison between them is where your money actually sits.

Interpret with the market's grain. The UAE market spans decades-deep institutions and young entrants racing to build records, and newer projects from newer names sometimes price the difference in — sharper payment plans, lower entry — which is a genuine trade rather than a trap, provided the protective framework is verified rather than assumed. The opposite error is just as real: a familiar name is not a score, and established developers have delivered delays too. Score the record, verify the framework, and let neither the name nor the discount do your thinking.

Run the model on at least two candidates for any serious off-plan purchase, because scores earn their meaning in comparison. The buyer who can put two composites side by side, with the evidence behind each cell, negotiates differently — and exits differently, because the resale-behaviour dimension is a statement about the day they will sell as much as the day they buy.

• Collect the developer's delivered-project list with contracted and actual handover dates; confirm through official land department channels.
• Compute on-time rate and average delay depth; if fewer than five projects, weight discipline and escrow instead.
• Score the five payment-discipline criteria — escrow, registration, change orders, charge stability, litigation — out of 10.
• Gather snagging and defect-liability evidence from the two or three most recent handovers.
• Trace handover-era resale prices on the major listing portals and recorded transactions for the resale-behaviour input.
• Verify escrow status and Oqood or equivalent registration for the specific project before any deposit, and re-verify close to signing.