Mobility and command around complex events. From one place.

We manage the movement around your event.

Event Mobility Partners plans, coordinates and operates mobility around sports, cultural and urban events. Event Mobility Command is our platform where every organisation runs its events, team, event day, partners and public information from one command centre.

How it works in your organisation

  1. 1Your organisation gets a plan: events, users and SMS within a quota.
  2. 2In the command centre you create an event and invite the team with roles.
  3. 3The workspace holds the map, traffic management, transport, playbook and budget.
  4. 4On event day the control room, marshals and scanners work from a phone, also offline.
  5. 5The public, partners and authorities see only what has been published to them.

Every organisation responsible for how people and vehicles move

The platform is built so that any organisation can run its event, happening or any activity whose resources and people are managed on the platform. Every customer sees only its own data; every person does only what their role allows.

Event organiser

Triathlon, marathon, cycling, festival, song celebration or city event: courses, closures, control room, volunteers, athlete and spectator flows.

Traffic management contractor

Schemes, stages, segments and marshals in one system; the field worker sees their position and instructions on a phone, the control room sees presence live.

City and authority

Public transport changes, permits and approvals through links; the authority confirms or comments without creating an account.

Partner and supplier

Partner portal: tasks, requests for quotation, offers and invoices in one place, reviewed and approved by the organiser.

From organisation to event day and the post-event report

One logic throughout: organisation → plan → events → team and roles → preparation → event day → public → report and billing.

  1. 1
    Organisation and planThe customer is an organisation. The plan sets the quota of events, users and SMS; usage and invoices live in the customer portal.
  2. 2
    Command centreMy events, a new event within the quota, the event journey (start → plan → staff → publish → race day → close) and a setup percentage.
  3. 3
    Team and rolesOrganisation roles (owner, admin, member) and event roles (manager, editor, operator, viewer). Permissions are enforced in the database, not in the browser.
  4. 4
    Preparation in the workspaceMap, traffic management plan, stages and segments, transport, volunteers, partners, authorities, playbook, budget, calendar and deadlines.
  5. 5
    Event dayControl room: presence, incidents, chat, SMS, segment status, weather and the operational map. Field: marshal, traffic manager and scanner apps on a phone.
  6. 6
    Public and partnersPublishing is a controlled snapshot: closures, buses, parking, resident notices, public chat and a closures feed for navigation apps.
  7. 7
    Report and historyRule-based post-event report, feedback from marshals and partners, every change in history with restore.
  8. 8
    BillingPlan, usage and invoices live in the customer portal. Invoices are immutable and auditable; the price is agreed per plan.

Modules that exist today

Nothing listed here is a roadmap or a promise: everything below works on the platform and is used in the preparation of our own events.

Command centre and customer portal

Running the organisation and its events

  • My events status, journey, setup percentage, favourites and recently viewed.
  • Customer portal plan, usage, team, invoices.
  • Calendar all deadlines, playbook checkpoints, shifts and stages in one view; .ics export.
  • Help and tour role-based onboarding, FAQ, help requests by text or voice, system notices.

Workspace: preparation

Map, plan, money and partners

  • Map points, lines, areas, layers; KML and Google My Maps import; snapping to the road network; history and undo.
  • Traffic management schemes, stages, segments, signs, public transport; drawing storage; next year's plan on the same base.
  • Project and budget areas, activities, risks, milestones, quantities from drawings and budget lines.
  • Transport and volunteers lines, stops and timetables per day; shifts, points and QR passes; areas and movement intensity.
  • Partners and authorities link-based portals: posts with acknowledgement, tasks, RFQs, offers, invoices, decisions on public transport changes.
  • Playbook and briefing event playbook with checkpoints, digital briefing with confirmation, movement matrix.

Event day

Control room and field

  • Control room presence per position, alerts, segment status, internal and public chat, SMS, weather, operational map, big screen.
  • Incidents category, priority, owner, timeline, notes; a voice message becomes an incident.
  • Marshal app code entry, position and instructions, SOS, voice message to the control room, focus mode with a big clock, feedback.
  • Traffic manager and scanner opening and closing segments, checkpoints, pass and bus scanning.
  • Offline mode the control room and marshal keep working without a network: last data, a write queue, conflict choice.
  • Watcher plan versus reality: a segment should have opened, nobody is present, a device is silent.

Public

Visitor, resident, taxi, media

  • Public event page closures, diversions, buses, parking and a question chat; only published layers.
  • Closures feed a machine-readable feed for navigation apps and partners.
  • Resident notices AI drafts the notice in Estonian, English and Russian from published facts only.
  • Taxi and traffic info info desk map and a page for taxi drivers.

Complex events don't only happen at the venue.

Major events place pressure on roads, residents, emergency services and city operations. A traffic plan alone is not enough: complex events need a mobility system that is planned, coordinated, tested and operated.

Road closures
Emergency access
Resident and business access
Public transport
Authority coordination
Event-day decisions
Parking and arrivals
Reputational risk

Plan. Coordinate. Operate. Review.

The platform is a tool. The know-how of actually managing mobility around a complex event comes from our team. We offer the service together with the platform or on its own.

01 — PLAN

Mobility strategy

Mobility strategy, road closure planning, traffic management plans, diversions, emergency access and resident access.

02 — COORDINATE

Stakeholders

Authorities, police, emergency services, transport operators, local contractors, event teams and volunteers.

03 — OPERATE

Event-day command

Mobility control room, incident management, closure activation and real-time decisions on event day.

04 — REVIEW

Audit and readiness

Mobility audits, readiness reviews, risk reports, post-event analysis and lessons learned.

Event Mobility Kickoff

A structured early-stage process that helps organisers and host cities identify mobility risks, align stakeholders and create a practical planning roadmap before detailed traffic planning begins. The result goes straight into the event's playbook and calendar on the platform.

Request a Kickoff proposal
  • Event and route complexity scan
  • Stakeholder mapping
  • Road closure risk review
  • Emergency access baseline
  • Resident and business access principles
  • Public transport and parking assumptions
  • Mobility governance model
  • Planning and readiness roadmap

How ready is your event's mobility plan?

Answer 40 questions across 10 areas and get your Event Mobility Maturity Score, a breakdown by area and your five highest risks before race day.

Take the readiness check →

Event Mobility Playbook: organising know-how the platform tracks for you

All our experience with mobility around major events lives in the platform as a playbook: modules, checkpoints and templates with deadlines calculated from the event start. The calendar, the journey and the watcher make sure nothing is left undone.

We understand both the event and the road.

Most event teams understand the event. Most traffic contractors understand the road. Complex event mobility requires both, and a platform that carries that know-how every day.

Major event traffic management experience
Road infrastructure and engineering knowledge
Road safety expertise
Temporary traffic management background
Authority and stakeholder coordination
Event-day operational leadership
Our own platform, developed from the lessons of every event

What it all runs on

Event Mobility Command is a web application that runs in any browser and phone without installation. Data lives in the Supabase cloud (PostgreSQL), permissions are enforced in the database and every change is logged.

90data tables, all with row-level access rules
7 + 15roles and permissions at organisation and event level
34server functions: field, public feeds, AI, SMS, import
45audited tables: every change in history
3languages for field workers and the public: ET, EN, RU
Tenant isolation in the databaseAn organisation sees only its own events, people and invoices. The rules are at PostgreSQL level, not only in the browser.
Roles and permissionsOrganisation roles (owner, admin, member) and event roles (manager, editor, operator, viewer). Field workers enter with a code and get a device token; partners and authorities use a link.
Real time and offlineChat, incidents and the map update live. The control room and marshal app keep working offline: last data, a write queue, conflict choice.
History and restoreEvery change logged column by column; row history with comments, one-click restore, trash for deleted rows.
IntegrationsGoogle Maps and My Maps, KML, snapping to the road network, public transport open data, weather service, SMS, Dropbox import of drawings, AI assistant.
Publishing is controlledThe public sees only a published snapshot; internal points are filtered out. A closures feed for navigation apps without a key.

Figures reflect the platform in October 2026. The detailed technical map is in docs/PLATFORM-MAP.md.

How different roles experience the platform

The platform is used by people with different jobs and different devices: the organiser on a laptop, the control room operator on a big screen, the marshal on a phone in the rain. Below are three role-based scenarios showing what each of them gets.

Illustrative scenarios: written from the platform's real capabilities, not quotes from a specific customer. Real feedback is collected after every event through the platform's feedback form.
I used to have the map in one file, the marshal list in another and the closure times in a third. Now the event is in one place, the journey shows the next step and the calendar tells me which deadline is tomorrow. When something went wrong, I restored the change with one click.
Event managerIllustrative scenario: marathon organiser, preparation in the workspace
On race day I no longer ring around. I see who is at their position and who is not, a segment turns green on the map when the marshal opens it, and an incident reaches me with location and photo. When the mobile network dropped, the control room kept working and sent everything later.
Control room operatorIllustrative scenario: traffic management contractor's control room on event day
I entered with a code, saw my point on the map, the instructions and the control room phone. Focus mode has a big clock and one button. My voice message reached the control room as clean text and the confirmation came straight back.
MarshalIllustrative scenario: field worker on a phone

Experience from roads, safety and major events

Lauri Lillmann

Founder and Mobility Director

More than a decade at the intersection of road infrastructure, temporary traffic management, road safety and major event operations. I help organisers and host cities deliver mobility systems that are safe, realistic and ready for event day.

My background gives me a rare perspective: I understand both the event and the road. The platform is developed further from the lessons of every event.

  • Traffic Safety Manager — IRONMAN EstoniaTraffic and safety management for a major international endurance event, including road closures, athlete and spectator flows, emergency access and multi-agency coordination.
  • Traffic Safety Manager — Estonian Song and Dance Celebration 2025Traffic and safety management for a national mass cultural event, ensuring smooth traffic flow, crowd mobility, resident access and public safety.
  • Temporary traffic management and road infrastructureProject management experience in temporary traffic management and road infrastructure delivery.
  • Road safety and infrastructureBaltic Sales and Project Manager at Saferoad: road safety products and traffic infrastructure.

Trusted on major sports and cultural events

Selected reference projects delivered for complex, high-visibility events.

Traffic and safety management leadership for a major international endurance sports event, including extensive road closures, athlete and spectator flows, emergency access and multi-agency coordination.

Reference project
IRONMAN — Estonia

Traffic and safety management for a national mass cultural event, managing large-scale crowd movement, public transport pressure, resident access and city-level stakeholder coordination.

Reference project
Estonian Song and Dance Celebration 2025

Project experience in temporary traffic management and road infrastructure, delivering safe work-zone traffic solutions and contractor coordination.

Reference project
Road infrastructure and safety

References and recommendations available on request.

Let's talk about your event mobility

Event Mobility Partners

Planning a complex event, a road closure or a host-city mobility challenge? Ask for a demo, a proposal or simply an opinion: the platform is priced per plan, the service per event scope.

Phone: +372 511 3525

Email: info@eventmobilitypartners.eu

Location: Tallinn, Estonia

Serving: Baltics, Nordics and Europe

Request a demo by email Call: a 30-minute conversation