The Three Decisions That Determine Whether Public Realm Creates or Destroys Value

Emaar ended 2025 with a revenue backlog of AED 155 billion, up 39% year on year. Aldar's UAE development backlog reached an all-time high of AED 57.3 billion in Q3 2025. Between them, more than 47,000 Emaar residential units alone are under development waiting to be delivered.

Across Dubai, forecasts place scheduled residential handovers in 2026 at between 70,000 and 83,000 units. Based on historical delivery rates, actual completions will likely come in lower. But even the conservative estimates represent roughly double the city's five-year annual average of around 35,500 units. The scale of what is about to hand over is without precedent.

Behind every one of those units is a community promise: a lifestyle, a public realm, a managed environment, a quality of daily life that was used to justify the price. The question most developers have not yet answered is whether the operational layer they are handing over can keep it.

The developments that will hold their value and retain residents are not the ones with the best renders. They are the ones where three decisions were made correctly before the masterplan was fixed. Most were not.

What happens in the space

Most public realm is designed for how it looks, not for how it gets used. The activation question, what should happen in these spaces, for whom, and how is that sustained over time, is the one most developers answer last. Usually after handover. Usually reactively.

That is the wrong sequence. Activation that is programmed to fill a calendar rather than to serve a specific community need tends to fade. The events stop when the developer's marketing budget runs out. The community centre sits empty because it was sized and fitted for a general resident who does not exist, rather than for the specific households who actually live there.

The activation brief has to come from the same place as the experience brief: the people who will live in the development, what they need from their shared environment, and what will make them want to stay. That question, asked properly and early, determines what gets programmed, who gets the brief, and what the community management operation needs to be able to sustain. It also determines which spaces can generate revenue and which are purely experiential, a distinction that matters significantly for the financial model.

What the operational layer needs to be

Operational space gets sized by convention. Rule of thumb ratios, FM industry norms, whatever the consultant's model defaults to. The underlying assumption is that public realm area drives operational requirement. It does not.

The variables that actually determine how much operational infrastructure a development needs are the nature of the assets being maintained, the experience the development has promised to deliver, and the resident and user profiles that generate that demand. A high-density urban development with a luxury promise, active programming, and a mixed user base needs fundamentally different provisions than a suburban residential scheme of equivalent land area. Neither the area nor the unit count tell you that. Only understanding what the development has promised its residents and what their daily lives will actually require gets you to the right answer.

Getting this decision right requires a cross-portfolio view. Applied across one major Abu Dhabi master developer's portfolio of 12 projects, this logic identified a 42% reduction in operational GFA requirements and AED 252 million in construction cost savings through cross-portfolio synergy analysis. Neither figure was visible from a single-project perspective. Both came from asking what the experience actually required, rather than applying convention.

The governance question sits within the same decision. The strata framework determines how the operational layer is managed, funded, and held to account once the developer steps back. A strata framework drafted for legal compliance produces a governance structure that satisfies registration requirements and little else. RERA and DLD have both strengthened oversight of owners association governance in recent years; service charge disputes and conflicts between owners and management companies remain among the most common issues flagged to regulators. These are not random failures. They are the predictable outcome of strata treated as a legal formality rather than as a community design decision.

A strata framework designed to support the experience promise, with governance principles that reflect how the community is intended to function, produces a structure that sustains the development's brand beyond handover.

How it gets resourced and what it returns

The sourcing decision is not primarily a commercial one. It is an experience decision that has commercial consequences.

Developers who procure FM and CM on price, through competitive tender against an SLA, are not making a sourcing decision. They are choosing a contractor to manage a cost centre. The contract is structured to minimise cost, not to deliver an experience. The result is predictable: service quality drifts, the developer's brand suffers, and residents who can choose, do.

Developers who specify FM and CM against an experience brief, who define what residents should experience before they define what they are willing to pay, procure differently, manage differently, and retain differently. The service charge becomes a justified cost rather than a complaint. The brand equity holds.

Ownership decisions sit in the same territory. Which operational assets does the developer retain? Which transfer to authorities, third parties, or community associations? Which are shared across asset classes within the development? Most of these decisions are made implicitly: by convention, by regulatory default, or because no one asked the question at the right moment. By the time handover arrives, the retention and transfer structure is fixed. The financial consequences are not.

Revenue from operational assets is the other side of the same question. Most developers treat public realm operational assets as cost centres by default. None of this is inevitable. Assets designed for revenue from the outset, where programming, tenanting, and service monetisation are part of the brief, contribute to the financial model rather than drawing from it. In a market where 70% of Dubai residential transactions are off-plan, the service model and community experience are often the primary differentiator between comparable products. The developer who has modelled that revenue, and built the operational layer to capture it, has a fundamentally different asset than the one who assumed it.

Not through cutting. Through thinking about the problem correctly from the start.

Public realm is the biggest cost line on most master developments. Done properly, it is also the biggest reason people stay.