The Developer Changed the Unit, Size, View or Amenities. What Evidence Matters?

Welcome back to the dispute.ae podcast. I'm Paul, and this is episode thirty-four. In the last episode we built the handover chronology. Today the date is not the only concern — the unit, view, size, layout or amenities appear to have changed. As always, this is general information, not legal advice.

The apartment looks smaller. The balcony has changed. The view is no longer what the salesperson described. A room has moved. An amenity has disappeared from the latest plan. The developer says the change is permitted. What should the buyer actually preserve? The first discipline is to separate disappointment from a provable difference — not because disappointment is unimportant, but because a developer-dispute file needs to show exactly what was represented, exactly what was agreed, exactly what now appears different, and when each version entered the record.

Begin with the signed contract set

Start with the complete Sale and Purchase Agreement, not the signature page alone. Keep every schedule, annex, plan, specification, payment schedule and amendment, and if the developer issued a reservation form, booking form, side letter or later variation, preserve that too. Buyers often compare the current unit with a brochure while overlooking the document that defines the contractual description; a brochure may still be relevant evidence of what was marketed, but it is not interchangeable with the signed contract. Keep both and label them accurately. Do not annotate the only clean copy — save an untouched original, then make a working copy in which the unit number, stated area, plan reference, floor, view description, finish schedule and amenity references can be indexed.

Preserve every version, not only the latest

A changed plan is difficult to analyse if the earlier plan has vanished. Keep the plan supplied at reservation, the plan attached to the SPA, any revised plan, the handover plan and any as-built or measurement document provided later. Record where each version came from and the date received: a file named "final plan" is not enough — a useful label might say "SPA schedule received with signed contract on 14 March" or "revised layout emailed by developer on 22 August." The source and date give the document meaning. The same applies to marketing material: save the complete brochure or webpage, including the publication date where available, the project name and the context around the statement. A cropped image of one sentence is weaker than the complete item from which it came.

Define the alleged difference neutrally

Avoid beginning with a conclusion such as "the developer has committed a breach" — that requires contract-specific legal analysis. Begin with an observable comparison: the SPA schedule states one internal area, the later handover document states another; the original plan shows a door in one location, the revised plan shows it elsewhere; the brochure depicts a named facility, the current project communication no longer lists it; the sales email uses a particular view description, the present condition appears different. Put each claimed difference into a comparison note with four columns — the subject, the earlier source, the later source, and the unresolved question. That is far more useful than a long emotional email, because another professional can see the point without reconstructing it from dozens of attachments.

Distinguish official project information from private promises

Check the project through Dubai Land Department's Project Status Enquiry and save a dated result — it can show project and developer information, registered status, reported completion details and other fields, but it does not decide whether a particular design change gives a buyer a remedy. Likewise, an Oqood certificate or Interim Property Register entry helps identify the off-plan unit and registration position; it is not a guarantee that every marketing representation will appear in the completed property. Each record answers a different question: project status is not the contractual unit description, a marketing render is not a registered record, and a handover measurement is not an agreed legal conclusion. Keep the categories separate.

Move the conversation into writing

If the concern was raised by telephone, follow up with a short factual email. Identify the unit, identify the document being compared, and ask the developer to confirm whether a change occurred, when it was approved, which contract term or document it relies upon, and what current plan or specification it says applies. Do not turn that request into a legal notice unless an appropriately licensed adviser has drafted or approved it — the administrative objective is narrower: obtain a written position and preserve the response. Keep the whole exchange, not only the message that appears helpful; a complete thread shows the question asked, the attachments supplied, any correction and the final position.

A composite example, and what not to do

Consider a composite example, not a real client account. A buyer says a promised study has disappeared. The brochure shows a study, but the SPA plan labels the same space as storage, and a later plan removes the partition altogether. Those three records do not tell us, by themselves, what legal result follows — but they tell us precisely what must be reviewed: the contractual plan, the marketing representation, the later change, any variation provision and the developer's written explanation. That is the difference between a complaint and a usable file: the complaint says "this is not what I bought," the usable file shows the three versions, their dates, the exact difference and the unanswered question.

Do not assume that every change creates an automatic cancellation or refund right — and do not accept the opposite assumption that a broad variation clause answers every question. Do not stop scheduled payments, refuse handover, sign a waiver or concede acceptance because of a general podcast or website article; those are case-specific decisions for licensed advice. And do not let the evidence become harder to verify: save the original files, full email headers where practical, dated photographs, inspection material and the complete contract set, and keep a version log so nobody mistakes an old plan for the current one. A well-organised file cannot determine the buyer's rights, but it can make the factual question visible — the first question is not whether the property feels different, but whether the difference can be described and evidenced precisely.

Official sources referenced

In the next episode, we look at the buyer facing another instalment while construction appears behind.

Thanks for listening. The full transcript is at transcript.ae. For pre-legal dispute support, dispute.ae is where that work is done.