How to Plan a Full Saturday of Bouncy Castle Deliveries — A Step-by-Step Guide for UK Hire Companies

Saturday is where every bouncy castle hire company either wins or loses the week. Twenty or thirty bookings landing in an eight-hour window, each with a specific drop time, a specific pickup time, a van it needs to be on, and — usually — a customer expecting a call if you're running late. Get it right and the day runs itself. Get it wrong and you're still driving at 9pm apologising to a birthday party.

This guide walks through how experienced UK operators plan a full Saturday of deliveries and collections. It's the manual process — no software, no shortcuts — so you can see every step and where the time actually goes.

Why Saturday is the hardest day to plan

Weekday hires are usually one-offs. Saturdays are dense: you might have 25 bookings across three vans, all delivering between 8am and 11am, all collecting between 4pm and 7pm. Because delivery and collection are two separate journeys to the same address (drop it in the morning, come back later), one Saturday booking is effectively two stops. Twenty-five bookings = fifty stops. That needs planning.

Add the constraints operators actually deal with — a customer who insists on delivery before 9am, a school hall with a hard-stop at 4pm, a driver who can't work past 6pm, a castle that only fits in your Luton — and you can see why most companies still spend Friday evening staring at a printed booking sheet.

The five-step manual process

Almost every established operator follows a variation of the same five steps. The differences are just in tooling: some use spreadsheets, some use paper, some use whatever booking system their platform gives them. The logic is identical.

1. Consolidate every booking into one list

Pull every Saturday booking off your booking platform and get them into a single view. For each booking you need — at a minimum — the customer name, full delivery address (with postcode), asset name, delivery time, collection time, and phone number.

If you take bookings across multiple platforms (BCN, KBS, phone, website enquiries), this is the step that eats the most time. Copy-paste, retyping, checking you haven't missed anything — an hour, easily, if you have twenty bookings.

Print the list. You'll want to scribble on it later.

2. Group by geographical area

Sort the delivery addresses by postcode area. All the CR0s together, all the SM4s together, and so on. This gives you a rough sense of how many separate zones you're covering and which drivers should take which zone.

A quick rule of thumb: one van can comfortably do 8-10 delivery stops in a morning if they're clustered geographically. Beyond that, either add a second van or accept later collection times.

3. Sequence stops by time constraint, not just distance

Distance-optimal isn't always customer-optimal. If Booking A needs delivery by 9:30am and Booking B by 11am, you deliver A first even if B is technically closer to base. Constraints beat geography.

Draft the delivery sequence per van. Then draft the collection sequence — this is usually different, because the last booking you delivered isn't necessarily the first you'll collect. Collections are driven by end times, which the customer chose independently of when they wanted delivery.

This is the step that catches everyone out. Deliveries and collections need two separate route plans. Most operators underestimate how different they are.

4. Calculate load per van

For each van, list every castle it needs to carry that morning (deliveries) and confirm it physically fits — length, weight, volume. If a castle is going to Winterbourne School and a soft play is going to Croydon, you need to know both fit in the same van at the same time. This is where you'll catch the “wait, we double-booked the Jungle Castle” problem before Saturday morning, not on Saturday morning.

5. Brief your drivers

Print each driver a route sheet: their stops in order, addresses, times, customer phone numbers, castle name, and any access notes (gate code, garden entrance, stairs, surface type). Some operators text the sheet, some email a PDF, some hand over physical paper. Either way — every driver leaves the yard knowing exactly where they're going and in what order.

The most common mistakes to avoid

• Planning deliveries and collections as one route. They're two different journeys with different constraints. Plan them separately.
• Forgetting the depot as a stop. Every van starts and ends at your yard. Both trips are loops. If your plan doesn't include return-to-depot, your driver's day is longer than you think.
• Ignoring collection service time. A collection is not instant. Deflating, folding, loading, sweeping — call it 15 minutes per stop minimum. If you sequence collections back-to-back with no buffer, you'll be late by stop three.
• Trusting a satnav to sequence stops for you. Google Maps optimises for shortest driving, not customer-happy delivery windows. Sequence yourself, then use the satnav.
• Only briefing the driver on Saturday morning. Get the route sheet in front of them Friday night. If something's wrong, you want time to fix it.

How long this actually takes

A rough honest estimate for a company doing 20 Saturday bookings across two vans, all done manually with a spreadsheet:

1. Consolidating bookings from your booking platform: 45-60 min
2. Grouping and sequencing deliveries: 30-45 min
3. Sequencing collections separately: 20-30 min
4. Load checking and van assignment: 15-30 min
5. Writing/printing driver briefs: 20-30 min

Call it two and a half hours of Friday evening, every week. Every week the exact same steps. Every week the chance of a typo or a missed booking. Every week ending with “did I remember to add the Bromley delivery?”

The automated version

The reason we built CastleRunner is that every one of those five steps is mechanical. Booking consolidation is a data-fetch problem. Geographical grouping is a clustering algorithm. Sequencing with time constraints is vehicle-routing maths that's been solved for decades. Load checking is a database lookup. Printing driver briefs is a template. None of it requires human judgement — but doing it manually still eats every Friday night in the country's bouncy castle industry.

Paste your bookings calendar link into CastleRunner and the whole thing runs in under a minute. You still make the calls, own the customer relationship, and stress about the weather. But you get Friday nights back.

Try CastleRunner FreeFree during beta. No card required.