Shipping daily
Nov 1DATAAll 646 projects re-verified: 6,419 developer claims tested against registers, courts and pressNov 1DATAMalaysia TEDUH and Philippines DHSUD licence checks: expired licences and approved delays foundNov 1DATAThailand ONEP register: 2 condos found selling before environmental approvalNov 1DATAMexico PROFECO contract register checks: one sales registration belonged to a laundryNov 1DATAAbu Dhabi ADREC inspections and RAK RERA permit list added: % built straight from the regulatorNov 1SHIPPEDNew stage filter: completed but still sellingNov 1SHIPPEDPublic database page: verification levels, disclosure distribution, every marketNov 1DATA+212 projects in one day, round 3: USA, Caribbean, Gulf, Africa, Japan, AustraliaNov 1SHIPPEDStage on every case: off-plan or under constructionOct 31SHIPPEDVerification level per check on every case card: registry, independent, developer, contradicted
Changelog →

Kolaboro / Corrections

Corrections and replies

When we get something wrong, we fix it and record it here. Developers can also reply on any project page.

Accuracy check, November 2026

On 1 November 2026 we drew 50 projects at random from the database (the sample is fixed by a monthly seed, so it cannot be picked afterwards) and re-checked every one of their 485 tested claims against the cited source. The re-check was done by separate AI agents that had not done the original research; it is an automated second check, not a human audit. A human review of the same sample is next.

  • 472 claims: the source, or another credible source for the same fact, supports what we published.
  • 11 claims: the source does not support it. All 11 are corrected below.
  • 2 claims still could not be checked (the page fails to load or sits behind a paywall). They stay as published and go to the human review.

25 claims could not be read on the first pass; a second pass reopened them or found the same fact in another credible source: 22 held up, 1 was wrong and 2 remain unchecked.

Error rate among checkable claims: 11 of 483 (2.3%). Several other claims were confirmed but rated one level too high (for example a portal copying a register counted as the register itself); we are tightening those levels in the next research round.

Corrections log

  1. 1 Nov 2026 · SYD-003: "consent covers residential levels up to Level 54" changed to contradicted. The council consent lists Level 53 as the top residential level; Level 54 is plant.
  2. 1 Nov 2026 · BRA-004: a size conflict (41 vs 410 m²) changed from contradicted to unverified. The cited page no longer shows it.
  3. 1 Nov 2026 · ORL-003: "Phase 1 of 22 units completed" changed from verified to unverified. The cited listing does not mention it; only developer and agent pages do.
  4. 1 Nov 2026 · ORL-003: "construction of Phase 2 started" changed from unverified to contradicted. The developer's own site says Phase 2 is in pre-construction.
  5. 1 Nov 2026 · NBO-002: starting price changed from contradicted to unverified. The cited developer page matches the claim; the higher figure is only on agent pages.
  6. 1 Nov 2026 · BALI-034: "freehold apartments" changed from contradicted to unverified. The cited decree sets minimum prices for foreigners and does not itself rule on freehold.
  7. 1 Nov 2026 · BAH-003: "expected returns up to 7%" changed from verified to unverified. The source is the developer's press release republished unedited, not an independent source.
  8. 1 Nov 2026 · DXB-005: developer identity changed from contradicted to verified. The register lists the project company among the developer's registered entities.
  9. 1 Nov 2026 · CAB-008: "nearby hotel opened August 2026" changed from verified to unverified. The source announced the opening in advance.
  10. 1 Nov 2026 · AUH-014: "under construction" changed from contradicted to verified. The register also labels the project under construction.
  11. 1 Nov 2026 · MIA-001: "completion by about June 2028 per buyer contracts" changed from contradicted to verified (independent). A news report on the buyers' lawsuit confirms the contract date; whether it can be met is a separate question.

The monthly sampling script and the rules for scoring are open: scoring.py. See also how we collect data.

How to request a correction

  1. Write to us with the project page link and what you think is wrong.
  2. Attach the evidence: a document, a registry extract or a dated photo.
  3. We reply within 10 working days. If the evidence holds, we update the page and log the change here.

Removal requests

We remove personal data on request and correct factual errors. We don't remove accurate, evidenced findings because a project or developer would prefer them hidden; you can always add a public reply.

Protect my purchase