My 7-factor due-diligence framework sets out what to assess in a developer — handover quality, timeline certainty, rental demand, exit liquidity, and the rest. This page is narrower and more mechanical: it is about how you check the two factors that decide whether everything else in the framework is worth trusting — delivery record and build quality — and it names the actual places to look.
Why a track record has to be verified, not read
A developer's own marketing is not evidence — it is a claim made by the party with the most incentive to make it look good. That does not make it false. It makes it unverified. The distinction matters because the gap between a brochure and a handover is exactly where off-plan returns are won or lost: a project that delivers on time with the finish it promised behaves completely differently, commercially, from one that slips and disappoints — even if the sales deck for both once looked identical.
My developer tier framework already makes this point structurally: tiers describe risk character, and any developer's claims inside a tier still need checking against transfer records and completed-building evidence before you rely on them. This page is that check, laid out as a repeatable method.
The two records that actually matter
- Delivery record — did previous projects complete on the timeline the developer originally communicated, across more than one flagship? A single well-executed hero project tells you less than a spread of projects delivered consistently.
- Build quality — does the handover match what was sold, on inspection of the finished building, not the show unit? This is the factor buyers most often skip because it requires visiting something that already exists rather than admiring something that doesn't yet.
Both are covered in more depth — including how a poor handover suppresses rental and resale pricing from day one — in the handover quality section of the full framework.
The checkable sources, named
None of these require insider access. They are things any buyer, agent or advisor can look at before money moves:
- Completed-building evidence. Walk the finished buildings a developer has already handed over. Compare finishing, common areas and amenity operation against same-price competitors — not against that developer's own sales office.
- Owner and resident evidence. Building-specific forums, resident photos and snagging reports form a real evidence trail on whether promised amenities were operational at handover and how fast punch-list items were resolved.
- Agents who attended the handover. A second-hand account from someone who was physically present at completion is worth more than a sales deck produced before a single unit existed.
- Public disclosure, where it exists. A publicly listed developer publishes audited accounts and is subject to analyst scrutiny — a due-diligence advantage almost no private developer offers, and one you can verify yourself rather than trust on faith.
- Independently recorded price and delivery data. Where a third party has tracked price history and on-time performance across a developer's full portfolio of completed buildings — not one flagship — that spread tells you far more than an average ever will.
- Public land registry disclosure. The Dubai Land Department and RERA publish registered transaction and project data. Treat this as one input alongside the others above — a public record worth cross-referencing, not a substitute for walking the building yourself.
A verification ledger — claim, source, and what “good” looks like
Here is the method laid flat, using the names I have reviewed in detail as the worked examples. This is not a ranking — it is a demonstration of what checking a claim looks like against what merely reading one looks like. Where a figure below is independently recorded, it is marked as such; where it is the developer's own stated position, it is marked as that instead.