What to take into your next appraisal
- Separate title evidence from planning and master-developer permission.
- Record who must satisfy each condition and by which date.
- Trace changes in permitted area through revenue, construction cost and land value.
Assemble the plot evidence
Read the title, survey, sale agreement and current plot-specific development controls together. DLD’s project-registration service also identifies approvals and, where the owner and developer differ, a development agreement. These documents serve different purposes and should not be substituted for one another.
Identify the permitting authority for the actual site. Dubai Municipality publishes its building-permit process, but a project team must establish which authority and master-developer requirements apply to the plot. A neighbouring project’s approval is useful context, not permission for your design.
Sources: Dubai Land Department: Register Project; Dubai Municipality: Building Permit Procedures
Convert each condition into a model input
For every condition, record the original wording, source date, responsible party, required evidence and effect on the model. A height limit affects massing; a parking requirement affects build cost and potentially saleable area; an infrastructure obligation affects cash before the first sale.
Keep build deadlines, extension provisions and completion requirements separate from an optimistic contractor programme. The model should show the deadline and the anticipated date, so any gap can be assessed before an unconditional land purchase.
| Condition to establish | Evidence | Appraisal consequence |
|---|---|---|
| Permitted use and envelope | Plot-specific control and authority confirmation | Area and revenue mix |
| Access and utility capacity | Written authority/provider response | Enabling cost and start date |
| Master-developer obligations | Executed agreement and NOC conditions | Fees, design gates and deadlines |
| Owner/developer relationship | Title and development agreement | Rights, payments and registration dependencies |
Worked example: a parking change consumes value
Assume a fictional scheme has 10,000 sq m of chargeable sale area at AED 15,000 per sq m, producing AED 150m gross revenue. A design response to verified parking requirements reduces sale area by 300 sq m and adds AED 2m of basement cost. Keep all other inputs unchanged.
Revenue falls by AED 4.5m and direct cost rises by AED 2m, so pre-finance surplus falls by AED 6.5m. Financing and timing may worsen it further. Recording only the basement invoice misses most of the economic effect.
Make the programme depend on approvals
A useful programme shows submission, review, required revisions, approval and conditions discharge as separate tasks where material. Link the first construction draw to the facility’s actual conditions. If approval is needed for a sales launch, update that launch and its buyer receipts as well.
Avoid assuming that a design change affects cost but leaves permit timing and sales brochures untouched. Use a single design-version identifier across area schedules, cost plans and pricing schedules to reveal inconsistent revisions.
Define the land commitment gate
Before committing, list the unresolved conditions that could change the land bid. State a decision owner and the latest date for resolution. Quantify the downside from smaller area, additional infrastructure or delayed approval separately before combining them.
The final appraisal should allow a reviewer to trace the most important plot conditions directly to their financial effect. That is a stronger basis for negotiation than an unexplained contingency percentage.
Sources and further reading
- Register Project Dubai Land Department
- Building Permit Procedures Dubai Municipality
- Valuation of development property RICS
Published by Feasly. How we prepare our guides. Suggest a correction.
