The short answer
Expo City Dubai is a roughly 3.5 km² legacy district where residents, offices, venues, schools and public attractions now coexist and dozens of operators share the territory. No single team owns every problem, so incidents must be routed, not merely handled. The workable model is a single operations entry point, a routing matrix that assigns an owner by incident type, tiered escalation to authorities such as Dubai Police and Civil Defence, and clear SLAs between operators.
Key takeaways
- Expo City Dubai evolved from a temporary world-expo site into a permanent mixed-use district with residential, office, school, exhibition, event and leisure uses, so no one operator owns the whole territory and handoffs between teams are unavoidable.
- Incidents on such sites stall mainly at boundaries: between a pavilion and a public walkway, a tenant and the community operator, or a public plaza and a residential quarter, where responsibility is ambiguous.
- A routing matrix that fixes, in advance, the first responder, the process owner, the escalation path and the reaction timer for each incident family is the core practical tool.
- The Expo and COP28 experience demonstrates the value of a shared operations centre where private and government units work from one point with common KPIs and a single incident identity.
- Part of every routing path necessarily leaves the site to authorities — Dubai Police, Civil Defence, emergency medical services and RTA — so the handover moment and accompanying responsibility must be defined beforehand.
- Routing quality is measurable: time-to-assignment, share of incidents closed by the first owner, repeat handoffs and closed-loop records are manageable indicators rather than abstractions.
- Every scheme has limits: detection and data quality cap what routing can do, contractor boundaries rarely match physical ones, and event schedules change, so drills and periodic revision are required.
A city, not a venue: who actually operates the territory
Expo City Dubai is the legacy of Expo 2020, reopened as a permanent district in October 2022 and embedded in the Dubai 2040 Urban Master Plan. Under the master plan approved in 2024, the roughly 3.5 km² area is organised into five districts — Expo Downtown, Expo Business, Expo Hills, Expo Fields and Expo Valley — designed for tens of thousands of residents and professionals and tied together by an efficient grid, a smart transport system and a network of green and blue spaces.
That mixed format means very different regimes coexist within one 'site': event halls and offices, open parks and residential quarters, school campuses and retail and leisure zones. Each regime is run by its own team — the events operator, the community management division, facilities-management contractors, security, transport, tenants, and municipal and government bodies. The job of incident routing is not to replace these operators but to decide, at any moment, which of them owns a given incident.
In practice this means replacing the idea that 'the site has one owner' with a model in which 'every incident type has one named owner at every stage'. Routing discipline is the connective layer that turns many teams into one operating system.
- Mixed use: residential, offices, schools, exhibitions, parks and events at once
- The district retained around 80% of Expo infrastructure and 123 LEED-certified buildings
- Different regimes (public, event, residential, commercial) need different process owners
Why incidents stall on large mixed-use sites
On a large multi-purpose territory an incident rarely stalls from a shortage of people. It stalls because responsibility blurs at the seams: a leak on the boundary of a pavilion and a shared gallery, damaged equipment in a zone served by both the event operator and the community contractor, or a stranger inside a residential courtyard while the adjacent park is open.
The second cause is shift and language multiplicity. Security, maintenance and cleaning teams work in shifts, and shift handover is a classic point where context is lost. Without a fixed handover protocol, an open incident is forgotten precisely where it has not yet been closed.
The third cause is the mismatch between contract boundaries and physical boundaries. A facilities contractor is responsible for the building, not the adjacent pavement; an event organiser owns the hall, not the approaches to it. When an incident physically crosses such boundaries, the decision must follow a pre-written rule rather than be improvised in the moment.
- Seams between responsibility zones are the main source of 'stuck' tasks
- Shift handover is a typical point of lost context without a protocol
- Contract boundaries rarely align with the physical boundaries of the site
A routing matrix: assign the owner before the event
The core tool is a matrix that links every incident family in advance to a first responder and a process owner. Convenient families include: life safety and fire, security and protection, medical, building technical failures, transport and movement, cleaning and environment, and visitor or resident enquiries.
For each family three roles are fixed: the first responder (who physically goes to the scene first), the owner (who carries the incident to closure), and the escalation (to whom the case passes and after how long if it cannot be resolved). A fire-alarm activation in an Expo Downtown building, for example, should first be handled by the security post and the duty engineer, but the duty to hand control to Civil Defence on a confirmed fire should be written down in advance, not decided on site.
Owner and first responder often coincide but need not: a visitor with heatstroke in an open park means first aid from security and an ambulance from the city, while the decision to close the zone rests with the territory operator. That separation between 'who arrived' and 'who decides' is what makes the whole scheme work.
- Fire and life safety: first responder site security/engineer, owner the building operator, escalation to Civil Defence
- Security and conflict: first responder site security, handover to Dubai Police on a suspected offence
- Medical: first aid on site, serious cases to the city emergency service
- Technical failures: engineering service; heavy systems (lifts, BMS) get a dedicated owner
- Transport and movement: on-site traffic the site operator, city roads RTA
- Cleaning and environment: soft-services contractor, environmental risk triggers escalation
The routing path: detect, triage, assign, escalate, close
A robust routing path has five steps. First the event is detected — by an operator, security, a resident, a sensor or a camera. Then it is classified by criticality (life-threatening, high, medium, low) and by family. On that basis the first responder and owner are assigned and the SLA timer starts.
Escalation then follows a predefined ladder: first the shift supervisor of the operator, then, when the case leaves the boundaries of the site or the requirements of law, the external services. Finally the owner closes the incident with a recorded reason and confirmation that the task is genuinely resolved, not merely 'passed along'.
The governing rule is a single incident identifier at every stage. When one situation carries one number in the security log, in the maintenance system and in the dispatcher's records, routing can be measured and improved. Without a shared number, a repeat handoff loses meaning — no one can tell where the case sits or who holds it.
- One incident identifier across all stages and systems
- Classify criticality before assigning a responder
- Start the reaction timer as soon as an owner is assigned
- Only the owner closes the case, recording the reason
External services and a shared picture of the site
The scale shows how deeply government bodies are involved in running such a territory. During Expo 2020 the main operations centre was the base for more than a hundred units of government and private organisations responsible for operations, safety and security — in effect, a working prototype of routing for a permanent district.
Transport authority RTA ran movement through seven integrated control centres during the exposition, with the transport coordination centre sitting inside the shared Expo operations centre and working with Expo and Dubai Police toward common KPIs for each service type. The same principle of co-location and a shared picture carries over to everyday operations at Expo City Dubai.
The practical lesson for a large-site operator: decide in advance which events fall under the jurisdiction of external services (Dubai Police, Civil Defence, emergency medical services, RTA, the municipality), at what moment transfer occurs, and who escorts the case to closure. The line between 'our incident' and 'a city incident' rarely follows the fence — it is set by the type of event and the law.
- An operations centre as the single coordination point for private and government units
- Transport handoff to RTA: on-site movement the operator, city roads RTA
- Dubai Civil Defence is connected to building monitoring around the clock
- Define the moment and method of handover to an external service in advance
Making routing measurable: KPIs, handover and joint drills
To keep routing from becoming mere words, it needs manageable indicators: time from detection to assignment of a responder, the share of incidents closed by the first owner without a repeat handoff, the number of tasks stuck at seams between operators or shifts, the reaction time by family, and the share of closed tasks with a recorded reason.
Shift handover should follow a fixed protocol: open incidents are transferred on a single list with owner, status and deadline, not 'verbally'. Expo City's transition between regimes — from steady-state community life to the high-security summit environment of COP28, which drew tens of thousands of accredited participants — showed that operational agility is possible only when workforce deployment and protocols are already embedded in everyday work.
Finally, the scheme is validated by drills and reviews. A planned test of a specific scenario (fire, a lost child, a lift failure during a peak event, a surge of visitors) reveals where routing breaks before it breaks for real. Bear in mind that the events calendar, the opening of new quarters and occupancy all change the load on the scheme, so it must be revisited as the district matures.
- Time from 'detection to assignment' by family
- Share of incidents closed by the first owner without repeat handoffs
- Number of tasks stuck at a seam between operators or shifts
- Validate scenarios with drills and a review after each event
Honest limits of any routing scheme
Do not expect a matrix to solve everything. It works only as well as the data feeding it: if an event is not detected, or is detected late, there is nothing to route. Routing therefore always sits beside the task of observation — of people flow, zone condition and system state.
There are organisational limits too. Contractors often answer for a narrow scope of services and are not obliged to think about adjacent zones, so the territory operator must act as integrator. In addition, legal and regulatory responsibility in the UAE rests with specific bodies and cannot be replaced by an internal regulation; when in doubt in a dangerous situation, pass the case to the responsible service rather than settle it on site.
Finally, a scheme lives only as long as it stays current. New districts, residents moving into Expo Hills and Expo Valley, and a changing events calendar all shift the load and the boundaries of responsibility, so routing should be treated as a living document with periodic revision rather than a one-off agreement.
- Routing quality is capped by the quality of detection and data
- The territory operator must act as integrator between contractors
- Regulatory responsibility in the UAE stays with the relevant authorities and cannot be replaced by internal rules
- Revise the scheme as new quarters are occupied and the events calendar changes
Put it into practice
Incident routing and ownership matrix for a large mixed-use site
A ready template for the working document that holds the scheme together. For each incident family it fixes the first responder, the process owner, the escalation threshold and route, and a reaction timer. Fill the columns for your own structure and agree them with contractors and external services before an incident, not during one.
- Fire / alarm activation: first responder the security post and duty engineer; owner the building operating organisation; escalate to Dubai Civil Defence on a confirmed fire; notify the dispatcher immediately.
- Medical case (collapse, heatstroke, injury): first responder site security trained in first aid; owner the zone operator; escalate to the city emergency service; log the response time.
- Suspected offence or conflict: first responder site security; owner the territory security function; on signs of an offence hand over to Dubai Police; record the shared incident identifier.
- Building systems failure (lift, HVAC, power): first responder the duty engineer; owner the FM contractor; a lift stopped with people inside requires immediate escalation and, if needed, Civil Defence.
- Water or leak emergency: first responder security isolating the zone; owner the building systems contractor; escalate if there is risk to people; notify the neighbouring zone operator.
- Transport incident or congestion inside the site: first responder site security; owner the transport service operator; when it reaches city roads hand over to RTA; align with the movement dispatcher.
- Lost child: first responder security with immediate broadcast to all posts; owner the zone or event operator; the search protocol is agreed with Dubai Police; lock exits per scenario.
- Visitor surge and crush risk: first responder security managing flows; owner the event operator; escalate to territory management; notify transport and police at capacity.
- Cleaning and environmental risk (spill, waste, odour): first responder the nearest soft-services crew; owner the cleaning contractor; on environmental danger escalate and isolate the zone.
- Non-urgent resident or visitor enquiry: first responder the community team; owner the district community management; escalate to the territory lead if the deadline slips.
Questions people ask
Who should be the single entry point for incidents on a large site?
The scheme depends on a single dispatch point (a control or operations centre) that receives every signal from security, sensors, residents and operators, classifies it and assigns an owner. If the entry point is diffuse — for instance security, maintenance and a community desk take requests in parallel — an incident is easily lost. Give everyone one rule: 'all reports go through the dispatcher', and give the dispatcher a single log with an identifier assigned at the first step. During Expo, operations centres worked precisely this way to consolidate dozens of units into one picture.
How do you split responsibility when an incident crosses the boundary between a pavilion, a plaza and a residential quarter?
The physical location of an incident should not decide the owner — the type of event and the regime of the zone should. In practice, fix a rule in the matrix in advance: what happens inside a building belongs to its operating organisation, an open public plaza belongs to the territory operator, and a residential courtyard belongs to community management. If an event crosses boundaries, appoint one lead owner (for example by where the main harm is or by the dominant threat) and make the other operators support that lead. The rule 'one lead per incident' removes the situation where every side regards the zone as someone else's. This matches the logic of Expo City's mixed districts, where event, office and residential uses sit side by side.
Which external services must be involved, and when does handover of an incident occur?
In Dubai the authorities relevant to such a territory are above all Dubai Police, Civil Defence (fire safety, response and building monitoring), emergency medical services and transport authority RTA. Handover occurs when the event moves beyond the operator's jurisdiction or capacity: a confirmed fire, signs of an offence, a serious injury, or a situation on city roads. The rule is simple: a danger to life or clear signs of a breach of law are passed to the responsible service immediately, while the territory operator keeps escorting the case to closure rather than 'washing its hands'. It is best to define the handover boundaries in advance and agree them with the services, as was done during Expo preparations.
How do you keep routing consistent across several contractors and shift-based teams?
Consistency rests on three elements: a shared classification and matrix, a common log with incident identifiers, and a fixed shift-handover protocol. On every shift, open incidents are transferred on a single list stating owner, status and deadline, not 'verbally'. Contractors receive one version of the matrix with clear roles and must work through the dispatcher rather than directly between themselves. Expo City's experience shows that large-scale workforce deployment and coordinated contractor work become possible when protocols and roles are embedded in normal operations before a crisis. Short joint reviews at the end of each shift also help keep everyone aligned.
Which indicators should you track to tell whether routing is working?
Track: the time from detection to assignment of a responder; the share of incidents closed by the first assigned owner without a repeat handoff; the number of tasks handed between operators or shifts more than once; the share of closed tasks with a recorded reason; and the reaction time by family (fire, medical, technical, cleaning). If repeat handoffs rise, the owner is being assigned wrongly or the zone boundaries are unclear; if time-to-assignment rises, the bottleneck is in the dispatcher or the classification. Review the indicators at a regular joint meeting of operators and contractors, in the manner of operations centres that work to common KPIs for each service.
How does routing of urgent versus non-urgent incidents differ, and how do you avoid overloading the dispatcher?
Urgent events (danger to life, fire, serious injury, an offence) take the short path: an immediate call to the relevant service and to security, with no waiting in queue. Non-urgent events (cleaning, minor repairs, a resident enquiry) go through classification and a planned assignment to an owner with a reasonable SLA. To stop the dispatcher from drowning, introduce categories and let part of the routine demand reach the contractor directly (for example cleaning straight to the crew), while the dispatcher keeps oversight and analytics. Crucially, the reporter must never lose a way to raise an alarm: urgent cases need a separate short channel rather than a shared request queue.
Sources and further reading
Sources were checked when this page was generated. Confirm changing dates, rules and prices with the original publisher.
- Aldar partners with Expo City Dubai for $476m mixed-use developmentThe National
- Mohammed bin Rashid announces opening of 'Expo City Dubai' in October 2022Dubai Media Office
- RTA manages traffic and transport of Expo 2020 from 7 control centresDubai Media Office
- Built to Last: Long-Term Resilience in Soft FM — Lessons from Expo 2020, COP28 and the Future of Expo City DubaiClean Middle East
- Ruler of Dubai tours Expo 2020 command centre to review preparationsThe National