FlowsBook a callSign inCreate free accountSign up
Workflows by industry

How event rental companies plan delivery days with the forecast in view

Marquees, chairs and dance floors all go out before the weekend. Event rental delivery scheduling that puts drop-offs in order per van, with the rain forecast at each address.

Part of the guide Workflow automation

By the xMap team · · 4 min read

Event rental delivery scheduling works best when two questions are answered together on Friday afternoon: in what order should each van visit this weekend's drop-offs, and where is it going to rain? Put the addresses in the best visiting order per van, attach the forecast to each stop, and load the vans so the outdoor jobs facing rain get their marquees and flooring first. The drivers then leave the yard with a plan instead of a pile of delivery notes.

This is written for owners and dispatchers at party and event hire firms: marquees, furniture, staging, lighting, catering equipment. It goes through what the planning has to solve, an example built on invented orders, mistakes that cost a Saturday, and the AI employee that prepares the plan for you.

What a weekend delivery plan has to solve

Rental firms do not have a steady daily round. Most of the week's work is squeezed into Thursday, Friday and Saturday morning, and every job has its own constraints:

  • Order of stops. Vans should not cross the city twice. A good route per van gives back driving time on the busiest day of the week.
  • Splitting the work. Three vans with ten drops each beat one van with fifteen and another with five.
  • Weather at each address. A garden wedding with heavy rain forecast needs flooring, side walls and gutters, not just the marquee roof.
  • The return trip. Collections on Sunday or Monday follow the same addresses in a new order.

A spreadsheet and a map app can handle each of these on its own. Doing them together, every week, is where the hours go.

The forecast belongs on the delivery note

The Weather forecast block adds a short forecast to every address that reaches it: whether rain is expected, how many millimetres, the next rainy day, the highest temperature, the strongest wind and a one-line summary. A rain day counts from 0.5 mm. Wind is in km/h, which matters for marquees: many suppliers have their own limit above which a structure should not be put up, so put your limit in the plan rather than leaving it to each driver.

An invented weekend, start to finish

Picture a hire company in Cape Town with three vans and 27 drops for Saturday morning, kept in a Google Sheets file with the customer, address, items and whether the event is indoors or out. On Friday at 14:00 the flow reads Saturday's rows, looks up the forecast for each address, shares the drops between the three vans so each gets a compact patch, and orders each van's stops from the yard and back.

VanDropsRoute lengthOutdoor drops with rain expected
Van 1964 km2
Van 21071 km0
Van 3858 km3

Made-up orders and distances, for illustration only.

The AI then writes a loading note per van: Van 3 takes its two garden marquees with full side walls and flooring and visits them first, while the dry addresses can wait until the afternoon. Each stop in the email carries its place in the order, the distance from the stop before and a directions link the driver can open on a phone.

Mistakes that turn Saturday into a scramble

  • Planning on Wednesday. Orders change and forecasts sharpen. A plan made too early is redone by hand.
  • Forgetting time on site. Route times are driving times only. Putting up a large marquee can take hours, so cap each van's drops rather than trusting the total drive time.
  • Ignoring delivery windows. The route planner orders stops for the shortest drive; it does not know that a venue only opens its gates at 10:00. Note fixed times in the sheet and check the order against them.
  • Addresses without a position. A drop with a vague address cannot be placed and is left after the routed stops. Clean the address column when the order is taken.

How the AI employee does it each Friday

In xMap Flows the plan is one flow that runs on a timetable and appears in your Team inbox as an AI employee:

  1. Schedule: every Friday at 14:00.
  2. My data: the orders table, or the Google Sheets file you keep them in.
  3. Filter: delivery day is Saturday.
  4. Weather forecast: each incoming place, the next 2 days.
  5. Route planner: shared between 3 vans, starting and ending at the yard.
  6. xMap LLM: a loading note per van from the items and the forecast.
  7. Email to the dispatcher, or a row per stop in Google Sheets for the drivers.

By mid-afternoon the dispatcher has three routes with the weather beside every drop. A second copy of the flow, run on Sunday evening for collections, uses the same addresses in a fresh order. The event day weather plan template adds an approval step for plan B on the day itself, and next week's jobs planned around the weather is useful for the midweek jobs. More on routing for crews in the AI employee for field operations.

Questions

How many stops can one route hold?

Up to 50 stops a route. Stops beyond that, and orders with no usable address, are listed after the routes so nothing is lost.

Does the route allow for traffic at different times of day?

The times are for usual traffic on the roads, not the hour you leave. Leave some slack in busy parts of the city.

Can each driver start from home instead of the yard?

When every van loads at the yard, start there. For drivers who start elsewhere, give each driver's drops a field and plan one route per driver.

What if there is no forecast for an address?

Places without a position pass through the weather step unchanged, so fix the address and run the plan again.

Templates that do this

Read next

More on workflows by industry · 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.