Guides
Keeping a mobile detailing business on schedule
Scheduling mobile detailing jobs: build the day as a route, size the buffer from your own overrun record, and stop the two bookings that wreck a week.
What to take away
- Build the route first and hang time windows on it. A calendar built from arrival times produces a day that cannot be driven.
- The buffer is not guesswork. Take it from the distribution of your own overruns, not from a comfortable feeling.
- Two booking types cause most delaysthe vehicle described optimistically, and the job at the edge of the territory taken on a whim.
- Give the customer a window, not a time, and tell them what would move it.
- A day that ends late is a scheduling failure, not a technician failure, and it repeats until the schedule changes.
Step 1: Cluster before you sequence
Take the week's bookings and group them geographically before touching times. Streets, then neighborhoods, then zones. The unit of planning is a cluster you can work through with short drives between stops.
Cluster before sequencing
- Group week's bookings geographically
- Streets, then neighborhoods, then zones
- Plan clusters with short drives
- Offer a day, not a time
- Hold window until cluster set
Offer customers a day rather than a time when they book, and hold the time window until the cluster is set. Operators who commit to exact arrival times at booking are choosing customer convenience over the ability to keep the promise, and the second one is what customers actually remember.
Step 2: Sequence inside the cluster
Three rules do most of the work.
Sequencing rules inside a cluster
- Longest, least predictable job last
- Customer-present job first
- Water-needing jobs early
- Shade or cool panels where needed
- Longest and least predictable job last, so an overrun runs into your evening rather than into three other customers.
- The job that needs the customer present first, while everyone's day is still on plan.
- Jobs needing water early, so a refill does not sit between two bookings.
Where the vehicle needs shade or cool panels for protection work, put it where those conditions exist, not where it fits the map.
Step 3: Size the buffer from your own record
Look back at your last thirty jobs and write down how much each overran or came in early. That distribution is your buffer, and it is usually asymmetric: jobs rarely finish much early and occasionally run very late.
Size buffer from overrun record
- Review last thirty jobs
- Record each overrun or early finish
- Treat distribution as asymmetric
- Set buffer so bad day ends on time
- Check fraction of days still breaking
Set the buffer so that a typical bad day still ends on time, then check what fraction of days would still break. If a large share still break, the problem is not the buffer, it is that condition is being assessed too optimistically at booking.
The permanent fix for that is a condition assessment with observable descriptions and a rule for what happens when arrival contradicts booking, which is part of the handoff design in the operations and workflow guide.
Step 4: Schedule the resources, not only the people
Water, power and daylight all run out, and each ends a day when it does.
Resource scheduling inputs
- Measured water use per vehicle
- Jobs the tank supports
- Refill point on route
- Power availability
- Daylight hours
- Containment and recovery time
Plan water explicitly. Know your measured use per vehicle and how many jobs the tank supports. The EPA's WaterSense breakdown of vehicle washing shows how consumption divides across wash stages, so you know where to cut if the tank limits the route.
A mobile unit has no reclaim loop, so tank size and the refill point are scheduling inputs. What the van can carry is settled by the equipment and setup decisions.
Containment and wash water recovery also take time and belong in the plan. Vehicle wash runoff carries hydrocarbons, brake dust, and metals, so the EPA fact sheet on vehicle maintenance and washing practices treats it as a pollutant source.
Recovery is not a step to compress when running late. Local requirements behind it are chased down through the licensing and compliance guide.
Step 5: Control the two bookings that wreck a week
The optimistically described vehicle. Ask for photographs at booking, including the driver footwell, the cargo area and the worst panel. Describe your condition tiers in terms the customer can apply to their own vehicle. Then hold the rule when arrival contradicts the booking.
The distant one-off. A single job at the far edge of the territory can consume a third of a day. Set a minimum job value for outer zones and a day of the week when you serve them, so distant work clusters instead of scattering.
Step 6: Make cancellations cost something and rescheduling easy
A same-day cancellation with no consequence trains customers to treat the booking as provisional. A deposit or a stated notice period changes that, and it does not need to be punitive to work.
At the same time, make rescheduling easy and obvious, because the customer who cannot easily move a booking simply does not answer the door.
Weather deserves its own rule. Decide in advance what postponement means, who decides and by when, and tell customers the rule at booking rather than on the morning.
Step 7: Review the week, not the day
Once a week, look at four things: which jobs overran and why, where drive time exceeded plan, how many bookings were moved, and how many days ended late. Keep the record where you can compare periods, which is the same discipline the IRS applies to financial records in its guidance on what a business should keep.
Patterns show up quickly. Overruns concentrated in one service mean the time estimate for that service is wrong. Overruns concentrated in one technician mean training, which is the subject of the hiring and training guide. Overruns spread evenly mean the buffer is too small.
What a good schedule looks like from the customer's side
What a good schedule looks like
- A window rather than a time, with a message when the technician is on the way.
- A clear statement of what is needed at the sitespace, water, power, access.
- A named consequence for weather, stated at booking.
- An easy way to move the appointment.
- An arrival that matches the window, most of the time, and a phone call when it will not.
That last point is where reputations are made. Customers forgive a delay they were told about and remember one they discovered by waiting. The territory and access reasoning behind realistic windows starts back at the phased start sequence.
Common questions
How far ahead should the book be open?
Far enough to cluster properly, which usually means at least a fortnight, and not so far that condition assessments go stale.
Should I schedule back-to-back jobs?
Only within a cluster with short drives, and only with the buffer sized from your own overrun record. Back-to-back across the territory is how a good day becomes a late one.
What about emergency or same-day requests?
Hold a slot for them if they are a real part of your demand, and price them for the disruption they cause to the cluster. Fitting them in for free is where the rest of the day goes.
How do I handle a customer who is never home?
Confirm the day before, require a contact number, and have a written rule for a failed visit. The rule matters more than the fee.
