FlowsBook a callSign inCreate free accountSign up
Roads and traffic

Exhibition move-in traffic planning: trucks, slots and the roads to the halls

Build-up days put hundreds of trucks on a few roads. How organisers and stand builders can watch live speeds and closures near the venue and keep delivery slots on time.

Part of the guide Location intelligence automation

By the xMap team · · 4 min read

Exhibition move-in traffic planning is about a few roads and a lot of trucks. During build-up, stand builders, exhibitors' vans and freight forwarders all head for the same loading docks, usually in timed slots, and a slow approach road or one closure can push every slot behind it. Measuring the roads around the venue, the truck holding area and the loading gates every 15 or 30 minutes during the build days shows the live speed against what those roads allow, a jam level from 0 to 10, and closed stretches, so the logistics desk can hold trucks back or bring the next slot forward before the queue reaches the halls.

This piece is for exhibition organisers' operations teams, official freight and logistics contractors, and stand building firms that send crews and trucks to large venues. It covers the points worth measuring, a build-up schedule with the checks that go with it, an invented example, the limits of the data, and an AI employee that runs the checks through the build days.

Where trucks lose the time

On build days the delays rarely come from the motorway. They come from the last kilometre.

  • The turn off the main road into the venue's service roads.
  • The holding area or marshalling yard, where trucks wait for their slot.
  • The loading dock gates for each hall.
  • Nearby streets trucks use when drivers try to beat the queue, often residential and narrow.
  • Roadworks or event closures nobody told the freight forwarder about.

Put a named point on each in a table in My data. Traffic Flow then measures the roads around each point at the moment the flow runs: current speed, free-flow speed, jam factor, congestion as a percentage, a level in words, roads measured and roads closed. Keep points at least 300 m apart, since closer ones share a measurement.

A build-up schedule with checks

Build stageWho is on the roadWhat to check
Day 1: hall floor and riggingHeavy freight, cranes, rigging trucksClosures on the service roads; speed at the main turn-in
Days 2 and 3: stand constructionStand builders' trucks and vans in timed slotsJam factor at holding area and dock gates every 15 minutes
Last day: exhibitors' goodsMany small vans, often without slotsCongestion on nearby streets; queues spilling out
Show daysVisitors' cars, taxis, shuttlesArrival roads at opening time and close
Break-down nightEverything at once, leavingClosures and the turn back onto the main road

A typical pattern; every venue and show differs.

Closures are checked with Traffic incidents, which lists road closures, roadworks and other incidents around a point or in a city, each with its street and district. Run it the evening before each build day as well as during the day: a planned closure found at 6 pm can still be passed to drivers.

An invented example in Barcelona

Say a trade fair in Barcelona has two build days and uses a holding yard 2 km from the halls. The example is made up to show how the readings are used.

  1. At 7:00 the service road turn-in reads Light and the yard is filling as planned.
  2. At 9:15 the dock gate for Hall 3 turns Heavy, with a jam factor of 8. The busiest road named is the internal road between halls 2 and 3.
  3. The logistics desk holds the 9:30 and 9:45 slots for Hall 3 in the yard and calls forward two Hall 5 slots instead.
  4. At 10:00 Traffic incidents shows new roadworks on the street drivers use as a shortcut. A message goes to every forwarder: use the main approach only.
  5. By 10:30 Hall 3 reads Moderate and its slots restart.

None of that is new to an experienced logistics manager. What changes is that the warning reaches the desk from the data every 15 minutes, rather than by radio from a steward at the gate after the queue has formed.

What the readings can and cannot do

Traffic Flow measures the speed of traffic, not the number of trucks, and it has no direction split. Your own slot system remains the record of who is booked when. The readings are live, so they tell you what is happening now; to plan next year's slots, keep every reading in a sheet and look at which hours jammed. Weather matters on build days too: the Weather forecast block can warn of strong wind for rigging or rain for outdoor stands.

An AI employee for the build days

  1. Schedule every 15 minutes, with active hours from 6:00 to 20:00 on build days.
  2. My data brings in the named points.
  3. Traffic Flow measures them; Traffic incidents adds the nearest closure to each.
  4. Branch: a jam factor of 7 or more, or a closed road, goes to the logistics desk chat; everything goes into a sheet.
  5. A second flow at 18:00 the day before sends forwarders a note of closures for the next morning.

The Road closures around the venue, for guests on the day and Morning site briefing: weather and road closures templates are near this already. The general idea of turning live road data into a team's next move is covered in location intelligence automation.

Questions

Can I see how many trucks are queuing?

No. The data gives the speed and jam level of traffic on the roads, not vehicle counts. Your slot booking system and stewards remain the source for queue length.

How often should roads be checked during build-up?

Every 15 minutes during slot hours catches a jam early enough to act. Outside slot hours, hourly or the evening before is enough.

Can drivers get the closures directly?

Yes. A flow can send a short note of closures near the venue to drivers or forwarders by email or app message each evening.

Does it work for outdoor shows too?

Yes. Points can sit anywhere, and the Weather forecast block adds wind and rain for open-air builds.

Templates that do this

Read next

More on roads and traffic · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.