Portable restroom rental scheduling: what a booking commits

What to take away

General guidance only. Service frequency and any sanitation requirement on a site are set by the authority governing that site, not by a rental company. On a construction site the federal floor is OSHA's sanitation standard, 29 CFR 1926.51, which fixes how many toilets a crew needs (see the safety section below); a state plan, a local health department or a permit condition can add to it.

A booking is three commitments

The middle row is the product. The bottom row is the one that is forgotten, because at the moment of booking the end feels a long way off and nobody assigns it an owner.

Schedule the return leg at the moment you schedule the delivery

Create the collection task when the booking is made, even if its date is provisional. For an event, the date is known. For a standing order it is not, so create it against the contract end date and let it move.

What you are protecting against is a unit that outlives its job. A collection task that exists, and appears on somebody's list, is what makes a dead site visible. A collection that is only created when the customer calls is a collection that sometimes never happens.

Then attach an access arrangement to it. Sites are frequently harder to enter at the end of a job than at the beginning, because fencing has gone up, a building has been closed in, or the person with the gate code has left.

What to ask before you promise anything

Question three is the one operators skip and pay for. Hose reach decides whether a stop is routine or a wrestling match, and it is far cheaper to establish at booking. If the answer exceeds the hose your truck carries, the booking either moves the units closer or is priced as a different job; the hose length itself is part of how the fleet and the truck are chosen.

Question five does double duty. The daily headcount sets how many units go on the order, and it is the input the service frequency is built on, so write both the number and the source of any frequency the customer quotes into the booking.

The commitment ledger

Keep, for every booking, an explicit record of what you promised: the delivery window, the service frequency, what a visit includes, the notice required to change it, and the collection arrangement.

The point is not administration. It is that in this trade the promise is made in a phone call and remembered differently by two people six weeks later. A ledger is what turns a disagreement into a reference. It also feeds the daily plan described in the operating day end to end.

Keep it with your business records rather than in a message thread. The IRS on which records a business keeps leaves the system to you provided it supports what you invoice, and a booking record is exactly the document that explains a disputed charge.

Four promises not to make

A specific time. Give a window and hold it. An appointment turns every earlier stop into a risk and every delay into a broken promise.

A specific unit. Customers who have seen a particular unit sometimes ask for it back. Promise the specification, not the serial number, or your yard has to hold stock against a name.

Same-day collection on a weekend. It is the request that most often cannot be met, and agreeing to it once creates an expectation you will meet at a loss thereafter.

Service during an event, unless you have planned for it explicitly. Servicing a unit in a crowd is a different job with different access, and it needs its own slot rather than being squeezed into a route.

Holds, deposits and releasing a date

For events, a date held without a deposit is not held. No regulator sets a hold period or a deposit size for this trade; they are your own policy. Write three lines into it before the phone rings: how long a verbal hold lasts, what converts it into a booking (a signed order, a deposit, or both), and when an unconverted hold is released. Then apply it consistently rather than case by case.

Then decide who has authority to override. Someone will always ask, and the answer is much easier when one named person makes it and the reason is recorded. What may be said in the offer itself is bounded by advertising rules and by what your agreement supports, which is covered alongside the permissions in which authorities regulate this trade.

Building the week before you sell it

Look at the week ahead as truck-days rather than as jobs. How many service visits are committed, how many deliveries and collections sit on top of them, and what is left.

That leftover capacity is what you are actually selling when someone calls. Selling beyond it produces a week that only works if nothing goes wrong, and something always does.

Who may drive which truck constrains it further, because a vehicle above a licensing threshold cannot simply be handed to whoever is free. That is worth settling before it bites, and is covered in which licenses apply where you work.

Safety inside the schedule

A schedule that only works by cutting corners is a safety problem before it is a service problem. The corners cut are always the same: the inspection at the end of the cycle, the second pair of hands for an awkward placement, and the visibility gear on a roadside stop.

OSHA's guidance on safety and health programs favors designing hazards out over managing them. In scheduling, that means a day with slack, not one that assumes everything goes well.

Sanitation on the customer's own site is separate, and on construction jobs it decides the unit count you book. Under 29 CFR 1926.51, Table D-1, a site with 20 or fewer employees needs 1 toilet; from 20 employees it is 1 toilet seat and 1 urinal per 40 workers, and from 200 it is 1 toilet seat and 1 urinal per 50 workers. The same section says that under temporary field conditions not less than one toilet facility must be available, and it lists chemical toilets among the facilities allowed on sites without a sanitary sewer, unless local codes prohibit them. Any state plan or permit condition comes on top.

How the work reaches the schedule in the first place is covered in who actually buys this service.

Common questions

How far ahead should events be booked?

Far enough that you can decline. The value of an early booking is not the revenue, it is knowing which weekends are gone before you promise them elsewhere.

What should happen when a delivery window is missed?

Tell the customer before they notice, offer a revised window, and record the cause. Almost all damage from a late delivery comes from silence rather than from lateness.

Can service visits be moved?

Within limits, and the limits belong in the agreement. What cannot be moved without a conversation is the frequency itself, because that reflects a requirement rather than a preference.

Who should own the schedule?

One dispatcher, with a documented handover. A schedule owned by whoever answers the phone produces double bookings in exactly the weeks it can least afford them.