The Dispute Desk

The Dispute Desk
  • 0.0 (0)
  • How To

The Dispute Desk is an educational podcast dedicated to the discussion of disputes within Dubai's real estate sector. It focuses on the various kinds of disputes or disagreements that may arise between stakeholders and how to navigate them. Topics include developer arrears, broker misrepresentation and disappearance. Please note nothing on the podcasts constitutes legal advice and in fact the entire desk is dedicated to pre-legal matters only. We aim to give our audience educational advice and observations on how to navigate commonly surfacing issues.

  1. Oct 1

    EPISODE 40

    Welcome back to the dispute.ae podcast. I’m Paul, and this is episode forty. In the last episode, we separated a regulatory complaint from a contractual refund route. Today, we close this run by separating four project labels buyers often treat as interchangeable. As always, this is general information, not legal advice. A handover date has passed. The site looks quiet. One buyer says the project is delayed, another says stalled, and social media says cancelled. These words do not establish the same legal or administrative status. Before considering a route, build four separate records. First, the contract. Record the completion or handover date, grace periods, extensions, notices, payment milestones and amendments. Second, the developer’s position. Keep revised timelines, payment demands, handover notices and explanations for delay. Third, observed site activity. Dated photographs may record what was visible, but they do not establish an official completion percentage or legal status. Fourth, check the current official project record through Dubai Land Department’s Project Status Enquiry or Dubai REST. Save the result and retrieval date. “Delayed” describes chronology, not necessarily a legal remedy. A missed date does not automatically establish a right to cancel, claim compensation or stop instalments. Those questions require review of the contract, facts and applicable law. “Stalled” or “suspended” also requires evidence. Record the latest construction information, developer communication, inspection information and official project status. If sources conflict, preserve them all. Formal cancellation is different again. A group chat, unanswered email or inactive site does not establish that a project has officially been cancelled. Dubai Decree No. 33 of 2020 concerns the Special Tribunal for Unfinished and Cancelled Real Property Projects in Dubai. Whether a project falls within that framework is a case-specific legal question. Keep three situations separate: a buyer wants to exit an active contract; a developer seeks termination for purchaser default; or a project is formally cancelled. The word “cancellation” does not make these processes the same. A useful file therefore creates four dated columns: contract, developer statements, observed facts and official records. Attach the source for every entry and flag conflicts. Dispute.ae can organise contracts, notices, payments, official status results and communications into a factual chronology and indexed review file. It does not determine legal project status, select a court or tribunal, interpret remedies or provide legal representation. The rule is simple: describe the project with dated evidence, not labels. Contractual delay, apparent inactivity and formal cancellation are different conditions. This closes our ten-episode return to buyer–developer disputes. The thread throughout has been simple: establish the record before choosing the route. Thanks for listening. The full transcript is at transcript.ae. For pre-legal dispute support, dispute.ae is where that work is done.

    EPISODE 40

  2. Sep 29

    EPISODE 39

    Here’s a condensed version that keeps the key distinctions while fitting under 2,500 characters: Welcome back to the dispute.ae podcast. I’m Paul, and this is episode thirty-nine. In the last episode, we built a defect-by-defect repair history. Today we look at a commonly misunderstood question: can a DLD or RERA complaint obtain a contractual refund? As always, this is general information, not legal advice. Start with the remedy RVS is Dubai Land Department’s Real Estate Violation System. It is designed for eligible real-estate violations and negative practices. It is not a general forum for every dispute involving a developer. Before filing, ask what outcome is actually required. Is the issue an alleged regulatory practice? Or is the customer asking to cancel a contract, obtain a refund or compensation, enforce a private obligation, or resolve a rental dispute? These may require different routes. What the RVS service covers DLD describes RVS as a service for reporting real-estate violations, negative practices and certain cold calls involving brokers or real-estate companies. Importantly, the official service information excludes contractual disputes, contract revocation, refunds and indemnity for lack of jurisdiction. Rental complaints are also excluded and directed to the Rental Disputes Settlement Center. So the words “developer complaint” do not determine the route. The conduct and requested outcome do. A contractual inquiry is not a judgment DLD also provides Inquiries Concerning Contractual Disputes, which can provide an automated response concerning a contractual dispute or unwillingness to fulfil a contract. That response should not be confused with a judgment, refund award, cancellation order or legal opinion. Separate the issues Consider a buyer who says a developer has not refunded a reservation payment and also alleges that an advertisement contained improper information. These may be separate issues. The refund request is contractual or financial in nature, while the advertising concern may need separate screening against current RVS eligibility requirements. Do not reshape a request for “SPA cancellation and refund” into a regulatory complaint simply to fit an RVS form. Evidence must match the route For a regulatory complaint, preserve the complete advertisement, company details, dates, URLs and communications. For a contractual dispute, keep the SPA or reservation document, payment evidence, notices, correspondence and relevant clauses. A five-business-day RVS service time should not be interpreted as a promise that money will be refunded or a private dispute resolved within five days. The rule is simple: choose the route based on the conduct, requested outcome and official service boundaries—not simply because the other party is a developer. Next episode: delayed, stalled, unfinished and officially cancelled projects—and why the distinction matters. Thanks for listening. The full transcript is at transcript.ae. For pre-legal dispute support, dispute.ae is where that work is done. Clarify the RVS versus RERA distinctionMake the refund route more actionable

    EPISODE 39

  3. Sep 25

    EPISODE 38

    Welcome back to the dispute.ae podcast. I’m Paul, and this is Episode 38. In the last episode, we built the escrow and payment trail. Today, we move from the ledger to the unit: what happens when a snag is marked “closed,” but the problem is still there? As always, this is general information, not legal advice. A buyer identifies 27 snags. Later, the developer’s portal shows 24 as closed. But on inspection, a pipe still leaks, a door still does not close, and a damaged tile has been filled rather than replaced. The issue is no longer simply what defects existed. The question becomes: what was reported, what work was attempted, and was the same condition properly retested? A snag list is only a snapshot. A repair-history file tracks each defect from first observation through notice, acknowledgement, access, attempted repair and retest. Start with the source documents: SPA, specifications, plans, handover notice, inspection records, snagging report and access records. Keep clean originals. Next, create one defect register. Give every snag a stable ID, such as kitchen-01 or bathroom-02. Record its location, condition, date observed, photographs or videos, notification date, ticket number, developer response, access dates, reported work, retest date and current status. Keep descriptions factual. “Water visible below the kitchen sink after the tap runs for three minutes” is stronger evidence than “major plumbing failure.” Photographs should show context and detail. Keep original files and link them to the relevant defect ID. For leaks, noise or intermittent faults, video may provide a clearer record. Preserve every portal submission, email, ticket number and access appointment. After repair work, retest the same defect. If the portal says “closed,” save that status—but remember: a closed ticket shows what the system recorded. It does not itself prove the physical condition was resolved. Keep quotations, inspection fees, emergency repairs and other costs separately. Do not automatically label them recoverable; responsibility and remedies require case-specific analysis. Dubai Law No. 6 of 2019, Article 40 addresses certain structural defects and defective installations, but those provisions are not a universal deadline or remedy for every snag. The SPA, handover documents, technical evidence, dates and applicable law still matter. For immediate safety risks—such as active flooding, exposed electrical components or fire-safety concerns—use the appropriate emergency or building channels and obtain qualified assistance. The administrative goal is simple: one defect register, one evidence folder, one notice history, one access log and one retest record. Remember: a snag list shows what was observed once. A repair-history file shows what happened next. Next episode: can a DLD or RERA complaint obtain a contractual property refund? Thanks for listening. Full transcript at transcript.ae. For pre-legal dispute support, visit dispute.ae.

    EPISODE 38

  4. Sep 22

    EPISODE 37

    Welcome back to the dispute.ae podcast. I’m Paul, and this is episode thirty-seven. Last episode, we separated inspection, acceptance and final payment. Today, we follow the money—from payment instruction and beneficiary to receipt, project and developer ledger. As always, this is general information, not legal advice. A common dispute starts simply: the buyer says, “I paid,” but the developer cannot locate the payment or has allocated it to another instalment, charge or unit. Sometimes the beneficiary or IBAN also differs from current project information. Do not start with accusations. Start with the transaction. For every payment, record the instruction date, amount, currency, purpose, beneficiary, bank, IBAN, reference, project and unit. Preserve the complete payment instruction and attach bank or SWIFT confirmation, cheque evidence, card records or other proof showing where the money went. Also record who paid. If a relative, company or representative made the payment, that difference should be explained in the reconciliation. Separate the property price from other charges. Reservation amounts, DLD fees, administrative charges, broker commissions and purchase-price instalments may serve different purposes. If the purpose is unclear, record it as unclear rather than assuming. Dubai Law No. 8 of 2007 provides the framework for project escrow accounts. The escrow account is opened for the project, and separate projects require separate accounts. This makes project identity important when checking payment instructions. Official project information can also help with reconciliation, but current information does not necessarily prove what bank details applied historically. A different beneficiary or bank is a question to investigate—not proof of misuse. Next, compare each payment with the developer receipt and statement of account. Classify discrepancies clearly: • Unallocated — payment completed but missing from the statement. • Misallocated — recorded against the wrong unit, project or charge. • Payee mismatch — beneficiary details require reconciliation. • Receipt mismatch — amount, date or purpose differs from the evidence. These are working labels, not findings of fraud, breach or liability. Then ask the developer in writing to confirm receipt, allocation, payment purpose and account authority. Keep the complete response. If payment instructions may be unauthorised, money may have reached the wrong recipient, or the discrepancy remains unresolved, seek prompt guidance through the bank, DLD and an appropriately licensed UAE legal professional. Remember: a project escrow account does not automatically guarantee completion, solvency or a refund. The rule is simple: follow every payment through the same chain—instruction, transfer, beneficiary, receipt, allocation and official project record. Where the chain breaks, document it precisely. A discrepancy tells you what question needs answering. It does not prove the answer. Next episode: building a repair history for defects the developer says are closed but the buyer can still see. Thanks for listening. The full transcript is at transcript.ae. For pre-legal dispute support, visit dispute.ae.

    EPISODE 37

  5. Sep 16

    EPISODE 36

    Welcome back to the dispute.ae podcast. I’m Paul, and this is Episode 36. In the last episode, we separated a payment demand from the construction record. Today, the developer says the unit is ready and wants final payment before the buyer has properly inspected it. As always, this is general information, not legal advice. A handover appointment can involve several separate events: readiness notice, inspection, defects, final payment, acceptance, key release and possession. They may happen together, but they do not mean the same thing. The starting point is not simply “sign” or “don’t sign.” Identify each document, what it confirms, what wording it contains and what remains unresolved. Build the handover file Keep the SPA, specifications, plans and amendments together with completion notices, payment demands, inspection forms, defects lists, acceptance forms, undertakings and key receipts. Request complete copies of anything referenced in a form, and save unsigned versions before signing. Check the unit number, floor, area and parking details across documents. If something does not match, isolate the issue before proceeding. Record the inspection Create a dated inspection record. Photograph the unit identifier and then each room systematically. Keep original timestamped files and clearly describe each defect. Separate observations from legal conclusions. “Crack visible above the bedroom window” records a fact. Whether that amounts to a contractual breach requires appropriate legal and, where relevant, technical advice. Read acknowledgements carefully A handover form may confirm attendance, inspection, defects, receipt of keys, possession, settlement or acceptance. The title of the document does not necessarily reveal everything it contains. Do not sign blank or incomplete schedules. If a representative attends, confirm their authority and POA scope beforehand. Reconcile the money separately Compare the payment schedule, receipts and developer’s latest statement. Identify unexplained charges separately from defects or inspection issues. Also save dated official project information from Dubai Land Department where relevant. Project-level information provides useful context but does not establish that an individual unit matches the contract or is defect-free. The rule to remember “Handover” is not one fact. Separate: • Readiness • Inspection and defects • Payment • Acceptance • Key release and possession After the appointment, record who attended, what was presented, what was signed or left unsigned, what defects were identified and what questions remain outstanding. Keep later rectification visits in the same record and close an item only when the evidence supports it. Separate the steps. Read every document. Preserve the condition found. And obtain appropriate advice before signing wording you do not understand. In the next episode, we follow an off-plan payment through the beneficiary, escrow information, receipt and developer ledger. Thanks for listening. The full transcript is at transcript.ae. For pre-legal dispute support, dispute.ae is where that work is done. I can also make it more natural and conversational for AI voice/podcast narration while keeping it under 2,500 characters.

    EPISODE 36

  6. Sep 15

    EPISODE 35

    Welcome back to the dispute.ae podcast. I’m Paul, and this is episode thirty-five. In the last episode, we looked at proving what changed in the property. Today, the issue is different: another instalment is due while construction appears behind. As always, this is general information, not legal advice. A buyer receives a payment demand, looks at the site and thinks: “If construction is late, why should I keep paying?” It is an understandable reaction, but not a safe conclusion without checking the file. Start with the SPA. Do not read only the payment table. Review the clauses explaining when an instalment becomes due, whether it is date-based or construction-linked, what notice is required, and whether a milestone needs certification. Keep the signed SPA, schedules, amendments and revised payment plans together. Next, build a payment ledger. Record every instalment, trigger, due date, amount paid, payment date, recipient account and receipt reference. Compare this against the developer’s statement. Look for missing or duplicated payments, unallocated transfers, replaced cheques, credit notes, late fees and amounts posted against the wrong unit. Describe each mismatch precisely rather than simply saying the account is incorrect. Also trace where payments were sent. Dubai’s escrow framework provides for project-specific real-estate development escrow accounts. Preserve payment instructions, bank confirmations and receipts, and compare available project information with the payment trail. Then identify exactly what triggered the latest demand. If it is a calendar date, record the relevant clause. If it is a construction milestone, identify the milestone wording and the evidence relied upon by the developer. Use Dubai Land Department’s Project Status Enquiry where relevant and save a dated result for the correct project. But remember: an official project status or completion percentage may not necessarily represent the same contractual measurement or certification required by the SPA. Avoid broad assumptions such as “construction is late, so stop paying” or “the developer demanded payment, so it must be due.” Both can create unnecessary risk. If a developer or DLD default notice has been received, preserve the original notice, delivery evidence, dates and attachments. Do not ignore deadlines or make admissions in an improvised response. Seek advice from an appropriately licensed UAE lawyer or legal consultant. The rule to remember: construction appearing behind does not automatically determine whether an instalment is due, and a payment demand does not automatically prove the account is correct. Reconcile the contract, payment trigger, ledger, official project record and notices before taking an irreversible step. Next episode: final payment, inspection and the documents presented at handover. Thanks for listening. The full transcript is at transcript.ae. For pre-legal dispute support, visit dispute.ae. I can also turn this episode into 10 SEO keywords with matching hashtags.

    EPISODE 35

  7. Sep 14

    EPISODE 34

    Welcome back to the dispute.ae podcast. I’m Paul, and this is episode thirty-four. Last episode, we built the handover chronology. Today, the issue is different: the unit, size, layout, view or amenities appear to have changed. As always, this is general information, not legal advice. The goal is to make the record clear before anyone changes position. A buyer may say: the apartment looks smaller, the balcony changed, a room moved, the promised view is different, or an amenity has disappeared. The developer says the change is permitted. What should the buyer preserve? For the operational comparison between what was marketed, contracted and ultimately presented, I drew on Marciniza “Izha” Manabat, Cendale’s Platform Partner. Start with the signed contract set. Keep the complete Sale and Purchase Agreement, including schedules, annexes, plans, specifications, payment schedules and amendments. Preserve reservation forms, booking documents, side letters and later variations. Marketing material may help show what was represented, but it is not interchangeable with the signed contract. Keep both and label them clearly. Preserve every version. Save the plan provided at reservation, the SPA plan, revised layouts, handover plans and any later measurement or as-built documents. Record where each came from and when it was received. Do the same with brochures, webpages and sales communications. Preserve the complete material rather than isolated screenshots. Define the difference neutrally. Do not begin with “the developer breached the contract.” Start with what can actually be compared. For example: the SPA states one area while the handover document states another. An original plan shows a door in one location; the revised plan moves it. A brochure shows an amenity that later project material no longer lists. Create a simple comparison: subject, earlier source, later source and unresolved question. Keep different records separate. DLD project information, Oqood records, contractual plans, marketing renders and handover measurements answer different questions. One should not automatically be treated as proof of another. Move the conversation into writing. Ask the developer to confirm whether a change occurred, when it occurred, what document or contract provision supports it, and which current plan or specification applies. Preserve the complete response. Do not assume every change creates an automatic cancellation or refund right. Equally, do not assume a broad variation clause resolves every issue. Stopping payments, refusing handover, signing waivers or accepting changes can require case-specific licensed advice. A useful dispute file does not simply say, “This is not what I bought.” It shows each version, its date, the exact difference and the unanswered question. The first question is not whether the property feels different. It is whether the difference can be described and evidenced precisely. In the next episode, we look at another instalment becoming due while construction appears behind. Thanks for listening. The full transcript is at transcript.ae. For pre-legal dispute support, visit dispute.ae. I can also make this more conversational and natural for AI voice/podcast narration while keeping it under 2,500 characters.

    EPISODE 34

  8. Sep 10

    EPISODE 33

    Here’s a shorter, cleaner version suitable for the podcast and comfortably under 2,500 characters: Welcome back to the dispute.ae podcast. I’m Paul, and this is Episode 33. Last episode, we separated the Oqood certificate from the official register entry. Today, we look at another common off-plan issue: a handover date that keeps moving. As always, this is general information, not legal advice. If your Dubai off-plan handover date has passed, don’t begin by asking, “Can I cancel?” Start with a more useful question: Which date has passed, according to which document? A delayed-handover file has two important clocks: the contract clock and the official project-record clock. First, review the complete signed SPA, including schedules, addenda and later notices. Look for terms such as estimated completion, scheduled completion, long-stop date, anticipated handover, inspection and key release. These dates are not automatically interchangeable. Marketing material may show one date while the signed SPA defines another or provides an extension mechanism. Create a simple timeline showing the exact date, the relevant clause and any later amendment or extension notice. Do not assume every Dubai SPA has a standard six- or twelve-month grace period. Next, check the official project record through Dubai Land Department’s Project Status Enquiry. Save the project number, developer details, status, completion information and update date. Remember: this is a snapshot of the official record, not automatically proof of contractual breach or a right to cancel, stop payments or claim compensation. Then verify the unit’s registration position in the Interim Property Register and keep your provisional registration records. Your own payment history matters too. Record every instalment, due date, amount paid, receipt, bank reference, reminder and default notice. A developer-delay allegation and a purchaser-payment issue can exist in the same file. One does not automatically cancel out the other. Build your file around five sections: 1. Contract and amendments 2. Official project and registration records 3. Payment history 4. Handover and inspection communications 5. Dated communication log Preserve original emails, attachments, photographs, videos and records of any financial consequences caused by the delay. Most importantly, do not stop paying, issue an online cancellation template, or sign a revised handover date, waiver, settlement or key-release document without understanding its effect. Once the record is complete, the real questions become clearer: Which date controls? Was an extension validly invoked? What is the effect of each party’s performance? What dispute route does the SPA provide? And what notice is required before taking action? If you remember one thing, make it this: Do not begin with the remedy. Begin with the record. Align the contract dates, official project status, payment history and notices first. In the next episode, we look at what happens when a unit’s size, view, layout or amenities no longer match what the buyer expected. Thanks for listening. The full transcript is at transcript.ae. For pre-legal property dispute support, visit dispute.ae. I can also make this more conversational and natural for voice recording, while keeping it under 2,500 characters.

    EPISODE 33
See All (40)

About

The Dispute Desk is an educational podcast dedicated to the discussion of disputes within Dubai's real estate sector. It focuses on the various kinds of disputes or disagreements that may arise between stakeholders and how to navigate them. Topics include developer arrears, broker misrepresentation and disappearance. Please note nothing on the podcasts constitutes legal advice and in fact the entire desk is dedicated to pre-legal matters only. We aim to give our audience educational advice and observations on how to navigate commonly surfacing issues.

Information

  • Creator
    The Dispute Desk
  • Years Active
    2026
  • Episodes
    40
  • Rating
    Clean
  • Copyright
    © N/A
  • Show Website
    The Dispute Desk