Organizing an event on public roads: procedures, obligations and points of vigilance (2026)

A clear but demanding legal framework

In France, the organization of an event on public roads is based on two pillars: the right to occupy public domain and administrative police powers. In other words, public space cannot be used freely, even temporarily.

Each event is therefore analyzed in terms of its impacts: traffic, safety, pollution, traffic.

What is expected is not only a request, but a demonstration of mastery.

What the legal framework says in concrete terms:

• Any occupation = prior authorization (AOT)
• Competent authority:
  • Town hall (the most common case)
  • prefecture (structuring or risky events)
• Legal basis:
  • General Code of the Property of Public Persons
  • Police power of the mayor/prefect

Authorization or declaration: understanding the right procedure

Depending on the nature of the event, the procedure varies. A local event, with no major impact, will fall under the responsibility of the town hall. Conversely, an event involving a course, a large number of participants or a traffic disturbance will require a declaration at the prefecture.

In practice, these procedures sometimes combine. A road race, for example, involves both a permit to occupy and a specific declaration.

Where to file your request:

• Town hall:
  • local event
  • fixed installation (stand, market, entertainment)
• Prefecture:
  • sports event on public roads
  • Cortege or parade
  • event impacting several municipalities

Deadlines to respect:

• legal minimum: 1 month
• recommended: 2 to 3 months
• important event: 3 months +

👉 Late filing = frequent reason for refusal

The administrative file: a demonstration of seriousness

The file is not an administrative formality. It is the document that allows the training services to understand your project and assess its feasibility.

A clear, structured and coherent file greatly speeds up the investigation. On the other hand, an inaccurate file creates uncertainty, and therefore refusal.

Documents generally requested:

• Written request or form:
  • object, date, timetable
  • precise location
  • estimate of attendance
• Identification of those responsible:
  • name, first name
  • coordinates
  • security referent
• Layout plan:
  • public access
  • emergency exits
  • technical areas
• Safety device:
  • number of supervisors
  • flow management
• Insurance certificate

Specific forms (depending on the case):

• Cerfa 13447 → simple sports event
• Cerfa 13390/13391 → motorized events

Security: the heart of evaluation

Today, security structures the whole of thinking. The organizer is responsible for the protection of the public, and this responsibility may be incurred.

Beyond the principles, very concrete elements are expected: access organization, emergency response capacity, flow management.

What the authorities are looking at first:

• Emergency device:
  • sized according to attendance
  • often insured by the French Red Cross or Civil Protection
• Access management:
  • entrances/exits identified
  • Limiting congestion points
• Coordination:
  • municipal or national police
  • traffic stops if necessary

Additional obligations, which are often underestimated

Beyond the core of the case, several obligations complete the regulatory framework. They are rarely blocking individually, but can weaken a project if they are forgotten.

To be expected systematically:

• Organiser liability insurance
• Music declaration to SACEM
• Drinking permit (town hall)
• Compliance of installations (tents, stages → ERP)
• Compliance with health rules if catering

(article updated April 2026)

Anticipating flows: the operational tipping point

In the field, the majority of difficulties are not administrative. They are linked to the management of flows: saturated accesses, queues, overcrowded car parks.

These situations are not random. They often reflect a discrepancy between actual attendance and the initial assumptions.

This is where the success — or failure — of an event comes into play.

Useful guidelines for sizing:

• 1 car ≈ 2 to 3 people
• concentrated arrival peaks (often the start of the event)
• secondary accesses that are often undersized

Points to anticipate:

• car park capacity
• Pedestrian traffic
• grouping areas

Attendance data: from useful tool to structuring tool

For a long time, the assessment of attendance was based on estimates. Today, this approach is showing its limits, especially in the face of the requirements of the authorities.

Measuring flows not only makes it possible to adjust the event in real time, but also to document its progress.

A measured event is more legible, more defensible, and more easily repeatable.

What the measure allows in practice:

• Adjust security teams
• Detect peak traffic
• avoid saturation of accesses
• Justify the gauge to the authorities
• document the event for future editions

What (often) causes a file to be refused

In the majority of cases, a refusal does not sanction an idea, but a lack of foresight.

Common causes of refusal:

• late deposit
• Incomplete file
• Unclear layout
• Inconsistent gauge
• undersized security

A simple approach to structure your project

Organizing an event on public roads means, above all, structuring your thinking. Define your project precisely, formalize a clear file, anticipate flows and secure uses.

Administrative requirements are not isolated constraints. They reflect an expectation: that of events that are better thought out, better managed and better understood.

A compliant event is an anticipated event. And more and more, an event that is based on real data.