The Dubai Land Department increased construction-timeline and escrow-account monitoring an estimated 35 percent across 2026, with AED 50,000 fines per violation for fake Trakheesi numbers and immediate license suspension powers escalating to Dubai Police for criminal fraud. The enforcement posture shift reframes pre-acquisition due diligence — buyers no longer need to rely on broker-provided developer reputation summaries when DLD Oqood, Mollak, and RERA registries publish the underlying performance data directly. The Desk's read in 2026 is that the buyer who runs developer track record diligence using public sources arrives at a materially better-calibrated acquisition decision than the buyer relying on developer marketing or broker introductions.

This piece walks through the developer track record audit using only public DLD, Mollak, and RERA data sources. We will state the framing position directly. The diligence framework is not exotic and the data is publicly accessible. The realised buyer-side benefit derives from the procedural discipline of running the lookup before SPA execution rather than from access to privileged information.

The Three Public Data Sources That Anchor Developer Diligence

Dubai property regulatory data centralises across three principal public-access systems, each producing distinct signal across developer track record evaluation.

The first system is Oqood, the off-plan transaction registry maintained by DLD. Oqood records every off-plan project registration, the registered units, the construction milestone progression as reported by the developer, and the payment escrow account linkage. For any developer the buyer is evaluating, Oqood produces the project history — completed projects, projects in progress, projects cancelled or substantially delayed, and the broader project-launch cadence pattern.

The second system is Mollak, the service charge transparency platform managed by RERA. Mollak captures all jointly-owned property service charge filings — apartment towers, townhouse communities, and mixed-use developments. For evaluating a developer, Mollak produces the post-handover operational track record — service charge stability across years, owner-association formation patterns, and the realised maintenance cost evolution that materially affects realised owner net yield.

The third system is the RERA registry, which captures developer license status, broker license validity, project approval status, and the official complaint and enforcement record. RERA registry produces the regulatory standing signal — developers in good standing versus developers under enforcement attention.

The integrated picture across these three systems produces a substantially complete view of developer track record without broker reliance.

What Specifically to Look Up Across Each System

The procedural framework operates with specific lookups across each data source.

In Oqood, the buyer pulls: the developer's complete project list with launch dates, the completion status of each project, the unit count delivered versus registered, the actual handover dates versus marketed handover dates, and the cancellation rate across the developer's portfolio. The pattern that matters is delivery consistency — developers with sustained delivery within 6 to 12 months of marketed handover dates rate substantially higher than developers with systematic 18-plus month delays or with project cancellations.

In Mollak, the buyer pulls: service charge history across the developer's completed buildings, the year-over-year service charge stability pattern, owner-association formation timing, and the documented dispute history. The pattern that matters is operational consistency — buildings where service charges grew within inflation versus buildings where service charges spiked, suggesting underlying operational distress at the building level that may correlate with developer-side handover quality.

In RERA registry, the buyer pulls: the developer license status, license history including suspensions or amendments, the formal complaint record, and the broader enforcement trajectory. Developers in good standing across multi-year periods produce different signal than developers with intermittent enforcement attention.

The Honor Pattern Variance Across Dubai Developers

The Intelligence Desk has tracked the realised developer track record pattern across the available public data and observes substantial developer-by-developer variance. The variance distributes across three principal patterns.

The first pattern is consistent delivery with operational stability. Specific developers demonstrate sustained track records of on-time or near-on-time handover (within 6 months of marketed dates), stable post-handover service charge patterns within inflation bounds, and consistent regulatory standing without enforcement attention. These developers typically operate established corporate infrastructure with strong broader operational reputation, and the realised buyer experience typically aligns with marketing.

The second pattern is mixed delivery with selective operational distress. Specific developers demonstrate variable handover-timing patterns, with some projects delivering on schedule and others experiencing material delay; service charge patterns that show post-handover operational stress in some buildings; and intermittent regulatory attention. Buyers approaching developers in this pattern need calibrated expectations and disciplined SPA review.

The third pattern is systemic delivery distress with documented enforcement attention. Specific developers demonstrate pattern delays across multiple projects, project cancellations during construction, service charge volatility post-handover, and documented RERA enforcement attention. Buyers approaching these developers face materially elevated procedural risk and the diligence findings should weight heavily in acquisition decisions.

The Handover Delay Calibration Across the 2025 Data

The 2025 Dubai handover delivery data shows only 62 percent of anticipated units delivered on schedule, with 2026 estimates suggesting completion rates as low as 48 percent in some segments. The market-wide delay pattern reframes the developer-specific track record evaluation — buyers should not interpret on-schedule delivery as commodity behaviour.

Within the 62 percent delivered-on-time cohort, specific developers cluster at the upper end with sustained on-time records; within the 38 percent delayed cohort, specific developers cluster at the lower end with systematic delays exceeding 12 months. The diligence buyer who maps target acquisitions against the developer-specific pattern within this distribution arrives at materially better-calibrated handover-timing expectations.

The Procedural Compliance Framework for Pre-Acquisition Lookup

For buyers approaching pre-acquisition diligence, the procedural framework operates with specific sequencing.

First, the developer name and project name confirmation through DLD-issued documentation. Buyers should not rely on broker-provided developer names — DLD-registered names sometimes differ subtly and the documentation lookup operates on the registered name.

Second, the Oqood project history lookup using the registered developer name. The lookup produces the complete project portfolio with delivery status across each project. Buyers should evaluate the pattern across the portfolio rather than focusing on a single project.

Third, the Mollak post-handover service charge lookup for buildings where the developer has completed delivery. The 5-year service charge trajectory produces operational signal that complements the delivery-timing signal from Oqood.

Fourth, the RERA registry lookup for license status, enforcement record, and the broader regulatory standing trajectory.

Fifth, the integrated synthesis that maps the data points into the developer-specific track record evaluation.

Where Public Data Cannot Substitute for SPA Review

The public data framework produces strong signal for developer-level evaluation but cannot substitute for SPA-specific clause review. The buyer who completes Oqood, Mollak, and RERA diligence still needs counsel-engaged SPA review for the specific project-level provisions affecting realised buyer rights.

The developer track record evaluation tells the buyer whether the developer is the kind of counterparty worth committing to; the SPA review tells the buyer whether the specific contractual framework supports the realised expectations. Both diligence layers operate complementary rather than substitutionary.

What This Tells Us About Developer Diligence in 2026

First, the public data infrastructure has matured to the point where buyer-side diligence does not require broker introduction or privileged access. Buyers willing to invest the procedural discipline of running the lookups arrive at materially better-calibrated developer evaluation than buyers relying on marketing summaries.

Second, the variance across developers is substantial. The 62 percent on-time delivery aggregate masks developer-specific clusters where on-time delivery rates substantially differ. Buyers who treat developer track record as commodity-equivalent across the market underweight the realised variance and the resulting realised acquisition outcomes.

Third, the integration across Oqood, Mollak, and RERA produces signal that no individual source produces alone. Delivery timing alone, operational service charge alone, or regulatory standing alone produce incomplete views. The integrated framework captures the multi-dimensional developer signal that broker-provided summaries typically compress to a single qualitative claim.

What This Desk Tracks Through Q2-Q3 2026

First, the 2026 handover completion rate aggregate against the 2025 baseline. The directional signal across multi-year delivery patterns informs the broader developer-track-record evaluation framework.

Second, the RERA enforcement action pattern across the developer landscape. The 35 percent monitoring increase produces measurable enforcement output that the buyer-side diligence framework should incorporate as the data accumulates.

Third, the Mollak post-handover service charge stability across recently delivered projects. The first 24 months of post-handover service charge evolution produces operational signal that updates the developer-track-record evaluation.

Honest Limits

The public data framework produces strong directional signal for developer evaluation but does not produce dispositive prediction across individual project outcomes. Even developers with strong aggregate track records can deliver specific projects with material delays or operational distress; even developers with weaker aggregate track records can deliver specific projects on schedule. The framework calibrates buyer expectations rather than guaranteeing outcomes. Realised acquisition decisions should integrate the developer-track-record signal with project-specific SPA review, broader market evaluation, and the buyer's individual investment thesis.

Sources