HomeIndustriesEvents
A festival empties every unit once a day. A wedding empties them once, all weekend.
Deliver Thursday, hold the daily schedule for the length of the event, pick everything up Monday — while a wedding across town needs nothing more than a handful of VIP units for a single weekend. Two different businesses running on the same fleet, one tight window for each, and no room to miss it.
A short window, one fleet fought over by competing events
A festival means dozens of units spread across several zones of the site, delivered in one block Thursday or Friday, pumped out every day for the length of the event, then picked up entirely by Monday morning. A wedding or private event is the opposite: a handful of upscale units, delivered and picked up over a single weekend, with no schedule to hold in between. The same fleet serves both businesses — often the same week.
The window is short and public. A full unit on a Saturday afternoon in front of a line of festivalgoers isn't a problem you fix backstage — it's visible, immediate, and there's no making up for it on Monday. A two-day window doesn't give you a second chance.
Multiple events often run at the same time and compete for the same pool of units. Knowing exactly which unit is free on which date — not just "generally available" — becomes a condition for honoring both contracts without a double-booking. And the organizer, for their part, wants proof that every promised visit actually happened.
The data model covers the business, not just the contract
Every capability below exists because a real festival or wedding demands it — not because generic rental software needed a checkbox for it.
Per-unit service schedule
Daily pump-outs for the length of a festival, a single pickup after a wedding weekend — the same scheduling engine handles both formats with no separate setup.
Set unit by unit, not contract by contractVisits generate themselves
Once the schedule is set for the festival's run, daily visits appear on their own and group by site zone — no route to rebuild every morning.
No manual route entryNo unit ever double-booked
When two events compete for the same fleet on nearby dates, availability is calculated by date directly in the database — no overlap that only surfaces once the truck is loaded.
Enforced at the database level, not the interfaceRoutes on the real road network
The Thursday or Friday block delivery is sequenced on the actual road network, zone by zone across the site, rather than in the order contracts happened to be signed.
Calculated on the real road networkThe truck keeps working offline
A festival site out in a field, often with no reliable cell coverage, doesn't interrupt anything: the driver's app keeps its stops queued locally and resyncs the moment signal returns.
Local queue, resync with no duplicatesA swap in a single stop
A VIP unit that needs replacing mid-event is scheduled as a single truck stop — picking up the old one, dropping off the new one — not two separate visits to coordinate.
Planned swap, one tripOrganizers want to know every day was covered — not just take your word for it
Every pump-out follows a checklist specific to its type, with conditional steps based on the condition found on site, and it tracks who checked off what — a person on site or an automatic rule. A timestamped photo and the driver's location accompany completion, captured right on site — not reconstructed from memory after the event.
Before the truck leaves the yard for delivery or pickup, confirmation can be requested from the organizer — useful when a site zone moved at the last minute. At the end of the day, a configurable report goes out by email; billable visits are detected automatically instead of being reconstructed after the event, and the PDF invoice follows directly from them.
Quebec festivals are served in production by an operator running OpsNode since June 17, 2026: 561 logged visits across 184 units and 170 service schedules, as of July 31, 2026.
A festival or a weekend of weddings to plan?
Show us your fleet and your event dates — we'll show you how OpsNode would have sequenced the delivery, the daily schedule, and the pickup.
See a demo