Skip to main content

Data governance

Methodology and field policy

How AbuDhaBuy turns official Abu Dhabi property records into comparable, date-stamped commercial intelligence.

Last reviewed 19 August 2026

Normalization pipeline

  • Source snapshots are retained in private runner storage; deployed products contain normalized records or privacy-safe aggregates.
  • Community names are mapped to stable AbuDhaBuy slugs with reviewed aliases. Unmatched areas remain unmatched rather than being forced into a community.
  • Area is published in square metres and square feet; price is AED; price per square foot is derived only when area is valid.
  • Property types, bedroom labels, off-plan status, and procedure types use explicit canonical values while source labels remain traceable in the pipeline.

Aggregates

Counts include records passing each published endpoint filter. Medians are used for prices and PSF to reduce the influence of extreme transfers. YoY compares equivalent trailing periods. Sample sizes, coverage start, coverage end, and generation time are returned wherever they materially affect interpretation.

Derived intelligence

Rental yield divides Tawtheeq median annual rent by ADREC median sale price for comparable bedroom segments. Investability combines yield, forecast growth, liquidity, market temperature, and price stability using versioned weights. Forecasts are scenarios, not valuations or guarantees. Fragility is a downside-screening indicator, not a probability of loss.

Missing data

Null means the metric was unavailable or did not meet the method threshold. AbuDhaBuy does not zero-fill missing periods, impute incomplete inventory runs, or present an unmatched developer/project association as fact.

Versioning

Additive fields may appear within v1. Removing or changing a field’s meaning requires a new version or a documented deprecation window. The OpenAPI document is the machine-readable contract.