How PropertyStellar turns source data into decision context

We assess sources according to the claim being made, not by a single platform-wide label.

• Primary official evidence: Dubai Land Department, RERA and other UAE or Dubai government records and service pages for regulations, registered records and official processes.
• PropertyStellar data layers: normalized transaction, rental, mapping and property records used to compare consistent entities and periods.
• First-party project material: developer and operator material for announced features, plans and timelines, which remain subject to independent confirmation.
• Listings and market context: asking prices, advertised availability and third-party descriptions, which are snapshots rather than completed-transaction evidence.
• Secondary reporting: reputable explanatory sources used for context when a primary source does not answer the full question.

For a transaction, legal or regulatory decision, verify the current position with the Dubai Land Department or the relevant authority.

• Source records are imported or queried with an identifiable refresh period.
• Names, dates, locations and units are normalized so comparable records can be grouped.
• Mapping connects a record to a community, building or project only when the available identifiers support that relationship.
• Aggregates and derived metrics are calculated from the eligible records for the stated window.
• Quality checks look for missing fields, impossible values, duplicate records, mapping gaps and stale snapshots.

Where a page shows its own source, evidence window, sample size, freshness date or confidence note, that page-level disclosure takes precedence over this general description.

• Transaction price or volume refers to eligible recorded transactions in the stated place and period, not every possible deal in the market.
• Listing price is an advertised asking amount at the captured time; it is not proof of final consideration or present availability.
• Price per square foot divides an eligible price by its recorded area. Outliers, inconsistent area definitions and small samples can distort the result.
• Gross rental yield generally compares annualized rent with a property value or price assumption before service charges, vacancy, financing, maintenance, fees and tax effects.
• Trend or change compares defined periods and can be affected by the mix of unit sizes, buildings and property quality sold in each period.
• Score or shortlist rank is a decision-support model based on available inputs, not a forecast of return or a regulated recommendation.

Confidence should rise when the page has recent, directly mapped, sufficiently numerous and internally consistent records. It should fall when evidence is older, sparse, indirectly mapped, supplied only by listings, or missing important fields.

A community-level metric must not be presented as proof of performance for a particular unit or project. When the necessary evidence is unavailable, the correct output is “unavailable” or a clear fallback label—not a plausible-looking substitute.

• Source data can arrive late, contain errors, be revised by its originator or use categories that change over time.
• Project handover, permit, payment-plan, price and availability information can change after capture.
• Automated entity matching can miss a record or associate ambiguous names incorrectly; low-confidence mappings should not drive specific claims.
• Historical patterns do not establish future demand, capital growth, rental income or liquidity.
• Currency, financing, service charge, vacancy and transaction-cost assumptions materially change investor outcomes.

If you find a mismatch, send the URL, exact value and source through our corrections process.