The busiest day
A seasonal hire has six weeks of usefulness in them. Every hour spent learning your fifth system comes out of that.
Most rental operations double their headcount for the season and lose it again in September. The people arriving in June are capable and new, and the thing they have to learn first is not the job. It is your stack.
The booking platform for reservations. A routing app for the runs. A folder of waivers, or a separate waiver product. A spreadsheet for what is in the workshop. A group chat where the day is coordinated and where the real state of the business lives.
Five tools, four of which contradict each other by Saturday afternoon. A new hire learns the contradiction as folklore: the spreadsheet is wrong after lunch, ask Dana about the yellow carts.
Say eight seasonal hires and six hours each before they can work unsupervised. That is 48 hours of a manager's June, spent in the fortnight where the manager has the least of it.
Then the error tail. Weeks one to three carry the mistakes: a booking taken against the wrong location, a unit released without a licence on file, a delivery loaded from an out-of-date list. Each costs somebody an hour and occasionally costs a customer.
The number worth measuring is time to first unsupervised shift. Most operators have never measured it, and it is the cleanest indicator of how much complexity you are asking a nineteen-year-old to hold in their head in week one.
A driver should need one screen: their run, in order, with the stops they have to close. A counter member of staff should need one screen: today, the units, and the documents outstanding.
Where a role needs a second system to do the ordinary version of its job, that is where the training time and the errors come from. Write down what each role touches on a normal day and count the tools. Two is workable, five is a tax you pay every June.
Do not ration logins. Per-seat pricing pushes operations into sharing one account across a summer team, which destroys any record of who did what, and the audit trail is exactly what you want in September when a unit is missing.
One system covers reservations, inventory, routing, documents, messaging and returns, so a seasonal hire learns one interface and one vocabulary. The driver's view is the run and nothing else, on the phone they already carry.
There are no seat licences and no per-user charge, so every member of your summer team gets their own login and the record shows who closed which stop.
The thing that survives the season is the record. When the same person comes back next June they are not relearning folklore, because the folklore has been replaced by what the system says.
The nine stages, in order
Nine writes to one row. A platform that needs a second system for any of these stages needs somebody to keep the two of them agreeing.
Reservation 2511-003
Every stage writes one line here. Nothing is exported, reconciled, or keyed in a second time to make that true.
Running underneath all nine
The guest finds you on a site you own rather than through a reseller taking a commission on the way in. The pages that have to rank and the availability they show read from this record, so nothing is edited by hand to stay true.
Judgement about a guest, a hurricane forecast or a bent axle stays with your people, and a platform that claims to remove that is selling something else.
A migration mid-season is also the wrong time to try any of this. If your summer is already running, the honest advice is to fix the run sheet and the confirmation now, and to move platforms in the shoulder season.
Measure time to first unsupervised shift. Most of that number is spent learning the tools rather than the job, so an operation running a booking platform, a routing app, a waiver folder, an inventory spreadsheet and a group chat is training five systems before anybody touches a bike.
Design each role around one screen, give every member of staff their own login rather than sharing one, and the number falls. Bodhisys runs reservations, inventory, routing, documents, messaging and returns as one system, with no seat licences and no per-user charge.
No. There are no seat licences and no per-location fees. The only charge is 4.5% added to each reservation and paid by your customer at checkout.
Their run for the day, in sequence, with the stops to close and the loading list behind it. Each stop closes with a photo, a timestamp and a location.
The shoulder season. Migration runs alongside your existing platform until you switch over, and the sensible window is the one where a bad week costs the least.
A demo takes six fields and someone who understands rental operations calls you back. Where Bodhisys is the wrong fit you will hear it on that call rather than after three meetings.
