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 / Standard

Version 1.0 · 1 November 2026 · CC BY 4.0

The Off-Plan Disclosure Standard

What every off-plan project should publish so a buyer can check it before paying. Six core items, eight recommended ones, each with what to publish, why it matters, and how we check it. Free to cite, copy and adapt.

Score your project Free templates Cite this standard

…projects tracked today
…publish all six core items
…data last updated

The standard at a glance

A project meets the standard when it publishes all six core items in a place any buyer can reach without signing up, and keeps them current. The live figure next to each item is the share of projects Kolaboro tracks that publish it today.

Figures are computed in your browser from our open data. Projects are anonymous. A published item is not proof it is genuine: that is what the checks below are for.

Core items

  1. D1 Building permit or licence number…
  2. D2 Deposit protection…
  3. D3 Construction progress…
  4. D4 Plans and specification…
  5. D5 Developer track record…
  6. D6 No guaranteed returns language…

Recommended items

  1. R1 Land title and who holds it
  2. R2 Title type for foreign buyers
  3. R3 Completion date and delay penalty
  4. R4 Payment plan tied to milestones
  5. R5 Service charges
  6. R6 Sales contract template
  7. R7 Complaint route
  8. R8 Data on unit counts

Part 1

Six core items

These are the six checks Kolaboro runs on every project. A buyer should be able to verify each one without asking the sales team.

D1

Core item

Building permit or licence number

#

… of tracked projects publish this today (…)

Counts as published only when a number and the issuing authority are given.

What to publish

The permit or licence number exactly as issued, the name of the issuing authority, the date of issue, the plot or address it covers and the number of units approved. Link to the official register entry when one exists.

Why it matters to a buyer

A number turns "approved" into something you can check in minutes. It shows whether the building is approved at all, for this plot, for this use and for this many units. Without it you are relying on the seller's word.

Good example

Building approval no. [reference], issued by [City Planning Office] on [date] for plot [lot reference], [12] residential villas. Look it up yourself: [link to the official register].

Bad example

"Fully licensed and approved." Or: "Permits in process, construction starting soon." No number, no authority, nothing to look up.

How Kolaboro checks it
Registry
The number is found in an official permit or licence register and matches the plot, use and unit count.
Independent
A regulator notice, court record or official gazette confirms the permit.
Developer only
Only the developer or its agents state a number; no official source found yet.
Contradicted
The register shows a different plot, use, holder or status (for example expired or revoked).
None
No number is published. "Licensed" without a number counts as none.
D2

Core item

Deposit protection

#

… of tracked projects publish this today (…)

Counts as published only when an escrow, trust account or guarantee is described.

What to publish

How buyer payments are protected: the bank that holds the escrow or trust account and the type of account holder (a licensed escrow agent, a notary or a trustee), or the issuer of a bank guarantee and what it covers. Never publish the account number: buyers receive it in the signed contract, and public account numbers invite payment fraud.

Why it matters to a buyer

If a developer runs out of money, protected deposits can be returned to buyers. Unprotected deposits join the queue of creditors, and buyers often recover little or nothing.

Good example

All buyer payments go into a project escrow account at [Bank name], held by [licensed escrow agent], and are released only against certified construction milestones. Account details are given in your sales contract, never by email or chat.

Bad example

"Your money is completely safe with us." Or a full account number posted on the website. Or: "Pay the booking fee to our director for faster processing."

How Kolaboro checks it
Registry
The escrow account or guarantee appears in a regulator's escrow or project register.
Independent
The bank, a regulator or another independent source confirms the arrangement.
Developer only
Only the developer describes the arrangement.
Contradicted
A regulator lists no escrow for the project, or the named bank or agent denies it.
None
No deposit protection is described.
D3

Core item

Construction progress

#

… of tracked projects publish this today (…)

Counts as published whenever any progress figure or regular update exists.

What to publish

A dated percentage complete, or dated photos taken from the same fixed viewpoints, updated at least every month. Ideally certified by an independent engineer or taken from the regulator's own inspection system.

Why it matters to a buyer

Payment plans follow construction. Dated progress lets a buyer compare the site with the schedule before paying the next instalment, and spot a stalled site early.

Good example

Progress report, [date]: structure [x]%, roof [y]%, overall [z]%. Certified by [engineering firm]. [12] photos from the same four viewpoints as last month, each with its date.

Bad example

"Construction is going great!" with undated renders. Or a single drone video from many months ago with no date on it.

How Kolaboro checks it
Registry
The percentage comes from a regulator's inspection or escrow system.
Independent
Satellite imagery or an independent report confirms the stage of work.
Developer only
Only the developer's own updates or photos.
Contradicted
Imagery or the regulator shows less work than the developer claims.
None
No progress information is published.
D4

Core item

Plans and specification

#

… of tracked projects publish this today (…)

Counts as published when floor or site plans are available to buyers.

What to publish

A site plan, floor plans with areas and how they are measured, and a specification list of materials, finishes and included fittings. The same documents should be attached to the sales contract.

Why it matters to a buyer

What you are buying is defined by these documents. Without them, "premium finishes" means whatever is delivered, and a smaller unit is hard to dispute.

Good example

Unit [B2]: [x] m2 internal, measured to the inside face of walls, plus [y] m2 terrace. Floor plan, site plan and specification version [3], dated [date], which forms Annex [2] of the sales contract.

Bad example

"Spacious villas with premium finishes." Renders only, no areas, no specification.

How Kolaboro checks it
Registry
Plans lodged with the approving authority are available and match the published plans.
Independent
An independent surveyor or architect confirms the plans.
Developer only
The developer publishes plans and a specification.
Contradicted
Approved plans differ from the plans shown to buyers.
None
No plans or specification are published.
D5

Core item

Developer track record

#

… of tracked projects publish this today (…)

Counts as published when a legal entity or delivered projects are named.

What to publish

The legal name of the selling company, its registration number and the registry it is in, and a list of delivered projects with addresses and completion years.

Why it matters to a buyer

You sign with a legal entity, not with a brand. A registration number shows who is behind it, and delivered projects with addresses can be visited and asked about.

Good example

Seller: [Company name], registration no. [reference] at [Companies Registry]. Delivered: [Project A], [street, town], completed [year], [18] units. [Project B], [street, town], completed [year], [6] units.

Bad example

"Decades of experience." A brand name with no company behind it, or "past projects" shown only as renders.

How Kolaboro checks it
Registry
The company is found active in the company registry with the published number.
Independent
Press, court records or stock exchange filings confirm the company and its deliveries.
Developer only
Only the developer's own description.
Contradicted
The company is dissolved, owned by someone else, or a listed project cannot be found.
None
No legal entity or past projects are published.
D6

Core item

No guaranteed returns language

#

… of tracked projects publish this today (…)

Counts as met when no guaranteed returns language is found.

What to publish

No promise of guaranteed rental income or returns unless a written, enforceable guarantee from a named party is published with its terms. Any rental projection is labelled as an estimate and shows its assumptions.

Why it matters to a buyer

Guaranteed returns are a common sales hook. They are often paid out of buyers' own money or built into the price, and regulators in several markets restrict them.

Good example

Rental estimate: [x]% to [y]% gross per year, assuming [occupancy]% occupancy at [nightly rate], before management fees of [z]%. This is an estimate, not a guarantee.

Bad example

"Guaranteed double-digit ROI for ten years!" Or: "The villa pays for itself."

How Kolaboro checks it
Registry
Not applicable: there is no register of advertising claims.
Independent
A regulator warning or press report about the project's return claims.
Developer only
We reviewed the developer's listings and found no guaranteed returns language.
Contradicted
Guaranteed returns are promised in ads, brochures or sales material.
None
Not reviewed yet.

How Kolaboro checks each item

Every item gets the strongest level of evidence we could find. The full method is on how we score, and the official sources we use are listed on official registers.

Registry
Confirmed on an official source: a land office, permit register, licence list or company registry.
Independent
Confirmed by an independent source such as a regulator notice, court record, stock exchange filing, satellite imagery or a major newspaper.
Developer only
Only the developer, its sales agents or listing portals say so.
Contradicted
Sources disagree, or an official source says something different from the developer.
None
Nothing published, or not reviewed yet.

For developers

Self-assessment checklist

Tick each item your project publishes today, in public, for any buyer. Core items are worth 12 points each and recommended items 3.5 each, for a total of 100. Nothing leaves your browser.

Core items (72 points)
Recommended items (28 points)

Cite and reuse

The standard is published under Creative Commons Attribution 4.0 (CC BY 4.0). You may copy, translate, adapt and use it, including commercially, as long as you credit Kolaboro and link here.

Item numbers (D1 to D6, R1 to R8) stay stable across versions, so you can cite a single item, for example "Off-Plan Disclosure Standard v1.0, item D2".

Suggested citation

Kolaboro (2026). The Off-Plan Disclosure Standard, version 1.0, 1 November 2026. https://kolaboro.com/standard/. Licensed under CC BY 4.0.

Changelog

Changes are versioned. Earlier versions stay available and item numbers do not change meaning.

  1. Version 1.0

    First public version. Six core items (D1 to D6), based on the six checks Kolaboro runs on every tracked project, and eight recommended items (R1 to R8). Self-assessment checklist and free templates published alongside.

Suggest a change: write to us through the developers page or the corrections page. We review suggestions before each new version.

Protect my purchase