In short In short: from 1 October 2026, any event expected to draw more than 800 attendees, or any event at all staged on a road corridor in Dubai or Abu Dhabi, must lodge a Transport Coordination Plan with the local roads authority at least 21 working days before load in. A TCP is a single document that combines your venue access plan, shuttle timetable, ride-hail pick up zone, coach parking, and a valet marshal matrix. Producers who do not file by day T minus 21 will see their existing event permit stamped 'conditional' and last minute road closure requests will be refused outright. This guide explains what a TCP is, who needs to file, what the plan must contain, where to send it, what it costs, and how it interacts with the other permits on the calendar this season.
Last checked against the sources below: 6 October 2026.
What a Transport Coordination Plan is, and where the new rule comes from
The Transport Coordination Plan, or TCP, is a single document the Roads and Transport Authority in Dubai and the Department of Municipalities and Transport in Abu Dhabi began requesting in pilots during the 2025 to 2026 season. The pilot quietly grew into policy, and the formal notice that landed in late September 2026 makes the TCP a required attachment for any event permit that meets the size or road criteria below.
What triggers the rule. Two thresholds, either of which switches the TCP on. First, any event expected to draw more than 800 attendees at peak, measured at the gate, not the total session. Second, any event of any size that touches a road corridor, including a single lane closure, a coach drop off on a public street, a temporary taxi rank, or a ride hailing pick up zone on a public curb. Weddings inside a private villa on a private road do not need a TCP. A wedding with a coach drop on Al Wasl Road does. A corporate gala for 500 people inside a hotel ballroom does not. A corporate gala for 500 people on a hotel terrace with a road closure for red carpet arrival does.
Why it is being asked for. The roads authorities in both emirates are blunt about the reason. The 2025 to 2026 season produced a string of traffic incidents linked to event load out, several ride hailing surges around the same exit, and a small number of pedestrian conflicts on shared coach bays. A TCP forces producers to think about transport in the same detail they think about sound, fire, and waste. The DMT and RTA view the TCP as a desk review item, not an approval gate. Their language in the briefing was 'file, do not wait to be asked, we will accept the plan you lodge unless it is unsafe'.
What the TCP looks like. A four to eight page document, not a permit in its own right. It includes a venue access map at one to five hundred scale, a coach and shuttle timetable with dwell times, a ride hailing pick up and set down zone drawn on a street view, a valet marshal matrix that names supervisors and radio channels, an emergency egress diagram, and a short narrative on how guests will be told which mode of transport to use before they arrive. The narrative is the new part. Past practice was to push transport messaging only on the night. The TCP wants a pre arrival comms plan, usually an SMS or WhatsApp template and a landing page URL.
Who must file, and who can ignore the TCP for now
The threshold is generous on paper, so most small events stay outside the rule. Here is how we are reading the size and road tests for our clients in October 2026.
Counts toward the 800 attendee trigger. Everyone expected on site during the busiest hour, including guests, crew, performers, press, and on site vendors. Children count. Security staff and venue staff do not. If you are planning a wedding for 600 with 80 on site suppliers, you are at 680, under the line. If you are planning a wedding for 720 with 100 on site suppliers, you are at 820, over the line and the TCP is required.
Counts as a road corridor trigger. Anything that uses a public road, even briefly. A coach drop for 15 minutes counts. A single lane closure for a red carpet rollout counts. A temporary taxi rank that displaces the normal kerb use counts. A ride hail pick up zone inside a hotel porte cochère does not, as the porte cochère is on private property. A ride hail pick up zone on a kerb outside the hotel does.
Who is exempt. Film shoots that already hold a road closure permit through the existing film process do not need a separate TCP, because the road closure consent itself covers the same fields. Private events inside a gated community with private roads and no public transport interface do not need a TCP. Government hosted events of state significance are processed under a different fast track and do not need a TCP.
Who is in the grey zone. Pop ups, road shows, and brand activations that are smaller than 800 attendees but sit on a public plaza adjacent to a road corridor. Our reading is that any activation that queues guests onto a public footpath, hands out valet tickets, or asks guests to wait on a public kerb for a shuttle will be asked for a TCP even if headcount is under 800. Confirm with your permit runner before you sign the venue contract, because the venue will not always volunteer this.
What the Transport Coordination Plan must contain
The RTA and DMT have published a TCP template that runs to four pages. We have helped clients complete three in the last two weeks. Here is the structure of the form and what to put in each section, in the order the form asks for it.
Section 1, event basics. Event name, permit reference if you have one, venue name, peak attendance, load in and load out windows, and the single point of contact who will answer the regulator on the phone at 6pm on event night. Use a phone number, not an email. The DMT and RTA both said the first thing they do when a plan looks thin is call the named contact to test responsiveness.
Section 2, venue access map. A one to five hundred scale site plan showing all vehicle gates, all pedestrian gates, the coach bay, the ride hailing pick up and set down zone, the valet queue, the taxi rank if any, the nearest metro station and its walking route, and any road closure extent in red. Hand drawn plans are accepted if they are legible. The most common reason plans bounce on first review is that the ride hailing zone is shown as a dot with no indication of how many cars it can hold. Add a note. 'Holds 6 cars end to end, supervised by 2 marshals' is enough.
Section 3, coach and shuttle timetable. Arrival time, departure time, route description, dwell time at the venue, and coach operator name. If you are running more than one shuttle wave, list each wave on its own line. The regulator wants to see that you have thought about the queue that will form if two coaches arrive at once with 90 second dwell. The cheapest fix is to add a 10 minute buffer between coach arrivals. The regulator will accept a buffer written into the timetable as a substitute for a separate queuing plan.
Section 4, valet marshal matrix. Names, role, mobile number, radio channel, supervisor. If you are using a third party valet operator, attach their operating procedure and the supervisor name. The matrix looks bureaucratic but its purpose is to give the regulator a single name to call if a valet queue overruns the kerb at 1am. Write a real supervisor name with a real mobile. 'TBC' will bounce the plan back on review.
Section 5, emergency egress. A short diagram of how guests leave on foot if the road is closed and the venue is evacuated. The DMT and RTA both flagged this as the most common failure point. A diagram that shows guests spilling onto the road you have just closed is not an emergency egress plan. Draw a route that uses a side street or a service road.
Section 6, pre arrival comms. A short narrative plus the actual SMS or WhatsApp template plus the URL of the landing page. The regulator will not approve a TCP that says 'we will tell guests by email' without showing the email text. Show the message. We have found that the most useful template is a 60 word message that names the mode of transport, the drop off point, the recommended arrival window, and a single phone number for help on the day.
How the TCP interacts with the other October 2026 rule changes
October 2026 has been a busy month for new paperwork. Producers running events in the same week are juggling the TCP with the night shoot noise permit, the event waste sorting rule, the AI ticketing dynamic pricing cap, and the event cybersecurity disclosure rule. The TCP is a separate document but it has knock on effects on three of these.
TCP and the night shoot noise permit. If your event ends after 11pm and you are loading out on a public road, the load out is itself a road use that triggers the TCP. The night shoot noise permit covers sound. The TCP covers road use. You will lodge both, and the regulator has said that the road closure aspect of the load out will be assessed against the TCP, not against the noise permit. Plan your load out to use the venue service yard where possible, so the TCP stays simple.
TCP and the event waste sorting rule. The October 2026 waste sorting rule requires a waste plan as part of the event permit. The TCP does not duplicate the waste plan, but the two plans should be consistent on vehicle routing. If the waste plan says 'collection at 2am by a single truck from the service yard', the TCP should not say 'the service yard is closed to vehicles from 11pm to 6am'. We have seen a TCP bounced because the two plans disagreed on the same vehicle. Read both plans side by side before you lodge.
TCP and the AI ticketing dynamic pricing cap. The dynamic pricing cap, which landed earlier in October, regulates how resale and last minute ticket prices move. The TCP does not regulate prices. Where the two meet is in your pre arrival comms. If you are sending guests an SMS that says 'limited tickets at the door', the regulator will want to see that the door pricing is consistent with the cap. Attach the price schedule to the pre arrival comms section if you are promoting a door sale.
TCP and the event cybersecurity disclosure rule. The cybersecurity rule, also October 2026, requires you to disclose the platforms you are using for ticketing, registration, and guest WiFi. The TCP requires a landing page URL for pre arrival comms. If the landing page is on a third party platform, you should reference the same disclosure that is in the cybersecurity form. We have started adding a single line to the TCP that says 'landing page hosted on platform X, see cybersecurity disclosure Y'. This has cut TCP review time by about a day in our last three submissions.
Where to file, what it costs, and how long the review takes
Both emirates have moved the TCP onto the same online portal that already handles event permits. You do not need a new account. You do need to log the TCP as a permit attachment, then upload the document and the supporting map.
Dubai, RTA. File through the RTA permit portal, linked from the existing event permit page on the Dubai events portal. There is no fee for the TCP itself in Dubai for events under 2000 attendees. For events at 2000 or more, there is a review fee of AED 1,200 that is charged at submission, not on approval. Standard review is 7 working days. The RTA has said that a TCP that fails first review will be returned with comments and a second review of 5 working days, but only if the resubmission addresses the comments line by line.
Abu Dhabi, DMT. File through the DMT events portal, again as an attachment to the existing event permit. The DMT review fee is AED 900 for events under 2000, AED 1,800 for events at 2000 or more. Standard review is 10 working days, with a 5 working day turnaround on resubmission. The DMT has said that it will accept a TCP filed up to 7 days after the event permit itself, but only if the event permit is still in draft. Once the event permit is issued, late TCPs are not accepted.
Sharjah and the northern emirates. Sharjah has confirmed it is mirroring the TCP for events of 1000 or more, and is consulting on a road corridor trigger. Ras Al Khaimah and Fujairah have not announced a TCP equivalent as of the date of this guide. Confirm locally, because the rules in these emirates are not identical and tend to lag Dubai by 4 to 8 weeks.
What the first round of TCP submissions taught us
Three of our clients lodged TCPs in the last two weeks for events in late October and early November. The patterns are worth sharing because they are likely to repeat.
Pattern one, named contacts matter. The single fastest bounce on a TCP is a phone number that does not pick up. The regulator calls the named contact at random during the review window, sometimes at 8pm. A real supervisor with a real mobile answered on first review. A 'TBC' or a 'will be appointed' line bounced on first review both times. Cost the client about four working days.
Pattern two, the pre arrival SMS is the most overthought section. Producers are treating the SMS template as a marketing document, with multiple variations, A/B tests, and brand language. The regulator wants a plain 60 word message. The overthought template bounced on first review because it included a discount code, which the regulator flagged as inconsistent with the dynamic pricing cap. The plain 60 word version went through on first review.
Pattern three, coach timetable buffers are the cheapest fix. Where two coaches were originally timed to arrive 3 minutes apart, adding a 10 minute buffer cost nothing and removed a queueing concern that the regulator had flagged. The amended timetable went through on second review. The original timetable would have bounced a second time.
Pattern four, valet operator procedure is now being read. Earlier in the season the valet section was skimmed. In the last two weeks the regulator has started reading the third party valet procedure in detail and asking about the supervisor to marshal ratio. Aim for 1 supervisor per 8 marshals, with at least one bilingual marshal at the queue front. This is not in the form, but it is what the regulator is now asking for.
Practical checklist for producers filing a TCP this week
Use this list as a working document before you sit down to write the TCP. It is the same list our producers have started using, and it cuts the time to lodge a clean first submission.
1. Confirm the size and road triggers. Count peak headcount including crew, suppliers, and press. Check the venue access plan for any public road use. If either trigger is hit, the TCP is required.
2. Decide the single point of contact. Name a real person with a real phone who will be on the event phone at 6pm. Not the owner, not the venue manager. The person who will answer.
3. Draw the venue access map. One to five hundred scale, all gates, all coach bays, ride hailing zone, valet queue, taxi rank, metro walking route. Add a one line note for each zone on capacity and supervision.
4. Build the coach and shuttle timetable. List each wave on its own line. Add a 10 minute buffer between coach arrivals. Name the coach operator.
5. Build the valet marshal matrix. Real names, real mobiles, real radio channels, real supervisor to marshal ratio of about 1 to 8. Attach the third party procedure if relevant.
6. Draw the emergency egress. Use a side street or service road. Do not route guests onto a road you have just closed.
7. Write the pre arrival SMS. 60 words, plain text, names the mode of transport, drop off point, arrival window, and one help number. Match any pricing to the dynamic pricing cap.
8. Cross check the TCP against the night shoot noise, waste sorting, AI ticketing, and cybersecurity documents. Same vehicle routing, same platforms, same named contacts.
9. File at least 21 working days before load in. If the event permit is not yet issued, file the TCP as a draft and update once the permit number is known.
10. Answer the phone during the review window. The regulator will call the named contact at least once.
What is still soft, and what to confirm before you sign
The TCP is a new requirement, and the regulators have been candid that the form is still being refined. Three areas are soft as of the date of this guide, and we recommend you confirm them with your permit runner before you sign the venue contract.
First, the fee structure for events at exactly 2000 attendees. The RTA form says 'events of 2000 or more'. The DMT form uses the same language. Both regulators have told us informally that the threshold is intended to be 'above 2000', but the form text has not been updated. If you are at exactly 2000, expect the lower fee, but ask.
Second, the treatment of pop ups under 800 attendees on a public plaza. The DMT briefing said the road corridor trigger applies to any public kerb use. The RTA briefing was less clear. Our reading is that any activation with a valet ticket, a queue on a public footpath, or a shuttle drop on a public kerb will be asked for a TCP. Confirm with your permit runner, because the venue will not always flag this in advance.
Third, the interaction between the TCP and a private venue with a shared driveway. Some hotels and private estates share a driveway with a public road. The regulator has not been explicit on whether the shared section triggers the TCP. Our conservative reading is that any vehicle movement on the shared section is treated as public road use. Confirm before you commit to a venue whose main vehicle entrance is on a shared driveway.
If you are working on an event in late October, November, or December 2026, the TCP is now part of the standard paperwork stack. Plan the venue, the coach operator, and the valet supervisor at the same time, and the TCP will lodge clean on first review. If you leave the transport plan until the event permit is issued, expect a bounced submission and a four to five working day delay.
Questions
- Does a wedding under 800 guests ever need a Transport Coordination Plan?
- Yes, if the wedding uses a public road for any reason, including a coach drop, a temporary taxi rank, or a ride hailing pick up on a public kerb. A wedding on a private road with a private drop off does not.
- How long is the standard TCP review?
- Seven working days in Dubai and ten in Abu Dhabi for a first review, with a 5 working day turnaround on resubmission if the regulator returns the plan with comments.
- What is the fee for a Transport Coordination Plan?
- In Dubai there is no fee for events under 2000 attendees and AED 1,200 for events at 2000 or more. In Abu Dhabi the fee is AED 900 under 2000 and AED 1,800 at 2000 or more.
- Does the TCP replace the existing event permit?
- No, the TCP is an attachment to the event permit, not a replacement. You lodge both. The TCP is reviewed in parallel with the event permit and the review windows are independent.
- Can a film shoot with a road closure use the same paperwork?
- Yes. Film shoots that already hold a road closure permit through the existing film process do not need a separate TCP, because the road closure consent covers the same fields.
Sources
Planning something in the UAE?