Case study · Seasonal operations and pricing
One driver, one rented vehicle, eleven weekends, and a group of international staff paying out of their own pockets to see the region. What looks like a scheduling problem turns out to be a pricing problem with a scheduling problem inside it.
A seasonal residential program needed weekend transportation for its international staff — day trips, coastal outings, and longer runs to two major cities. One driver, one rented vehicle, roughly eleven weekends, and a staff who mostly could not drive themselves and were paying out of their own pockets.
What looks like a scheduling problem is really a pricing problem with a scheduling problem inside it.
The geometry of the operation
The driver’s base, the rental depot and the site are three separate locations. The vehicle has to be collected before any trip begins and returned after it ends.
What the rate has to cover
Vehicle hire is a fixed weekend cost regardless of how many trips run. Fuel is reimbursed at cost. Positioning time is real work that no passenger is in the vehicle for. Payment processing differs by nationality.
Both a lower and a higher hourly rate were built out fully, with the fixed costs, the positioning time and the processing fees carried through each. The recommendation went to the higher rate — not as a preference but as the arithmetic. At the lower one, a weekend with two short trips does not cover the vehicle.
With one driver and one vehicle, every trip competes with every other trip. Deciding that weekly by conversation is exhausting for everyone and produces resentment. So the operation runs on published rules instead.
| Rule | What it prevents |
|---|---|
| Short trips may run Saturday or Sunday; the group chooses by Wednesday | Two groups discovering on Friday that they wanted the same day |
| All longer trips are Sunday only | A long trip eating a weekend that could have carried two short ones |
| The furthest destination departs a day early | A trip that cannot physically fit in a weekend being booked as one |
| Payment due Wednesday at three; Tuesday for the long trip | Chasing money after the vehicle has already been hired |
| Overnight accommodation is included in the trip price | An unrecovered cost that only appears after the season ends |
| A published standby procedure | A cancellation leaving a paid-for vehicle idle |
The staff are seasonal, international, and largely unfamiliar with the distances involved. Written rules that they read before they book remove every argument before it starts. The rule that matters most is the Wednesday cutoff, because it is the point at which a weekend stops being hypothetical and becomes a committed cost.
| Document | Who it is for |
|---|---|
| Transportation analysis with both rate scenarios | The program director deciding whether to endorse it |
| Staff handbook | Staff, before they book anything |
| Transport guide | Anyone needing to know how a trip actually works |
| Trip planning guide | A group organizing an outing themselves |
| Destination guide | Deciding where to go and what is worth the drive |
| Administration manual | Whoever runs the program next |
| Standby addendum | The cancellation and backfill procedure |
| Season calendar file | Everyone, on their own phone |
Every guide was produced twice — a document version for the office, and a phone-formatted version, because the people who need the transport guide are standing in a parking lot in another country holding a phone.
A booking and cash-flow tool covering the season overview, trips and bookings, an actual expenses ledger, a cash flow statement, cost settings and reports. Without it the operator finds out in September whether the season made money. With it, they know on the Thursday of week three — while there is still time to change the rate.
| The usual approach | What was done here |
|---|---|
| Pick an hourly rate that sounds fair | Model the fixed costs and unbilled time, then let the arithmetic pick the rate |
| Sort out the schedule each week | Publish rules that decide it in advance |
| One document | Eight, each written for a specific reader, in two formats |
| Reconcile at the end of the season | A live ledger and cash flow from week one |
Any small operation with a fixed asset, a short season and variable demand — equipment hire, seasonal tours, mobile services, event logistics. The pattern is always the same. The fixed cost is known, the demand is not, and the rate has to be set before either is certain. That is a modeling problem, and almost nobody treats it as one.
Marketing Analytics Consultants
We model the fixed costs, the unbilled time and the awkward edges — then write the rules and the ledger that keep the operation honest with itself while the season is still running.