vintage, car, lights, shiny, chrome, classic, automotive, headlights, car wallpapers, history, detail, american dream, curiosity, retro, iconic, aesthetics, iconic car, vintage car, collectible, retro car. Mobile detailing workflow, from booking to done
Photo by Alexas_Fotos on Pixabay

Guides

Mobile detailing workflow, from booking to done

Mobile detailing operations mapped end to end: the eleven handoffs in a job, where each one fails, and the records that let a second technician run it.

What to take away

  • A detailing job is a chain of handoffs, and almost every operational failure happens at a handoff rather than during the work.
  • The van is a moving workshop with no back office, so anything not written down travels only in one person's head.
  • Water, power and daylight are scheduled resources. Treat them like a room booking, because running out ends a day.
  • Two records carry most of the weightthe condition record at arrival and the completion record at handover.
  • Design the day around the constraint, which for most operations is drive time rather than technician hours.

The eleven handoffs

Map the job as a chain and name what passes at each link. This is the document a second technician actually needs.

Eleven handoffs in a detailing job

  1. Inquiry to qualification: vehicle, condition, address
  2. Qualification to quote: tier, zone, package
  3. Quote to booking: scope, site requirements
  4. Booking to route: time window, drive time
  5. Route to arrival: directions, access, contact
  6. Arrival to work: condition record, confirmation
  7. Stage to stage: running order
  8. Work to inspection: finished vehicle, light
  9. Inspection to handover: customer walk-around
  10. Handover to invoice: completion record, extras
  11. Invoice to record: job time, materials, outcome
HandoffWhat passesWhere it fails
Inquiry to qualificationVehicle, condition, address, expectationsCondition taken on trust from the customer's description
Qualification to quoteAssessed tier, zone, packageAssessment done from one flattering photograph
Quote to bookingAccepted scope, site requirementsSite requirements never mentioned, so there is no water on arrival
Booking to routeTime window, drive time, resource loadThe day is built as a list of times rather than a route
Route to arrivalDirections, access notes, contactGate codes and parking notes living in one person's memory
Arrival to workCondition record, customer confirmationPhotographs skipped when running late
Stage to stageThe running orderOrder improvised, so contamination moves through the job
Work to inspectionFinished vehicle, inspection lightSelf-inspection in poor light
Inspection to handoverWalk-around with the customerCustomer absent, so a complaint arrives the next day
Handover to invoiceCompletion record, extras appliedSurcharges agreed verbally and never charged
Invoice to recordJob time, materials, outcomeNothing recorded, so pricing never improves

Fix the handoffs and most of what looks like a quality problem disappears.

The day as a route, not a calendar

A mobile day is a route with jobs attached. Build it in that order.

Build the day as a route

  1. Group bookings geographically first
  2. Fit jobs to time windows, not reverse
  3. Put longest, least predictable job last
  4. Keep buffer for worse-than-described vehicles
  5. Drive time decides how many jobs fit

Group bookings geographically first, then fit them to time windows rather than the reverse. Put the longest and least predictable job where an overrun does least damage, which is usually last. Keep a buffer for the vehicle that is worse than described, because that vehicle appears regularly enough to be planned for.

Drive time is the constraint that decides how many jobs fit, not technician stamina. An extra job at the far edge of the territory can cost more day than two jobs on the same street.

Scheduling the resources, not just the people

Three resources deserve to be scheduled explicitly.

Schedule three resources explicitly

  • Watermeasured use per vehicle, refill count
  • Powerwhat runs simultaneously, source capacity
  • Daylightcorrection early, interior late in winter

Water. Know your measured use per vehicle and how many jobs fit between refills. The EPA's WaterSense breakdown of vehicle washing shows which wash stages consume the most, and since a van cannot reclaim water the way a fixed site does, the tank is a hard limit on the day.

Power. Know what runs simultaneously and what your source can carry. Plan the high-draw work for the part of the day when the battery bank is strongest, if that is your setup.

Daylight. Inspection-dependent work needs light. In winter, put correction and protection work early and interior work late.

Wash water is an operational step, not an afterthought

Containment and disposal belong in the running order, with a named person responsible. Vehicle wash runoff carries hydrocarbons, brake dust and metals, and the EPA's fact sheet on best practices for vehicle maintenance and washing explains why municipalities treat it as a pollutant source rather than as dirty water.

Wash water containment procedure

  1. Containment goes down before water is used
  2. Recovery happens before the van moves
  3. Technician knows what to do if containment impossible

That last rule must exist because the alternative is a decision made under time pressure in someone's driveway. The permissions behind it are mapped in the licensing and compliance guide.

The two records that matter most

The condition record. Photographs of the vehicle before anything is touched, stored against the job. This resolves nearly every dispute about pre-existing damage and takes under two minutes.

Two records that matter most

Condition record

When
Before anything touched
Content
Photographs of vehicle
Purpose
Resolve damage disputes
Cost
Under two minutes

Completion record

When
After work done
Content
Time, materials, findings
Purpose
Input to pricing, training
Cost
Ongoing discipline

The completion record. What was done, what time each stage took, what materials were used, what was found, and what was agreed on site. It is the input to pricing, to training and to any complaint that arrives later.

The IRS description of records that clearly show income and expenses covers the financial half of this. The operational half has no regulator behind it and is skipped more often, which is why prices drift away from reality.

Handling the vehicle that is worse than described

This is the single most common operational disruption, and it should be a procedure rather than a judgment. Write down:

Worse than described

  • Who assesses, and against which published condition descriptions.
  • Which of the three responses appliessurcharge agreed before work starts, reduced scope at the quoted price, or rebooking.
  • Who has authority to decide, and what gets recorded.
  • What the technician says, in plain words, to the customer.

Rehearse the wording. A technician who has said the sentence before says it calmly, and calm is what determines whether the customer accepts it.

When a second person joins

Everything informal becomes a liability the moment two people are doing the work. The running order has to be written, the sign-off on each machine has to be recorded, and the quality standard has to be observable rather than remembered.

Labor cost also enters the operational picture properly for the first time. Occupational wage estimates by area published in the Bureau of Labor Statistics employment and wage tables are one input for checking that your assumptions are realistic, alongside the pricing structure in the pricing and profit guide.

Failure modes that end a day

Some disruptions cost an hour. A short list of them cost the whole day, and each has a cheap prevention.

Equipment failure mid-route is the classic one. A fuse, a hose fitting, a trigger or a pad can stop work entirely, which is why a small spares box lives in the van permanently rather than being restocked when someone remembers.

Running out of water at the second job of four is the second. It is entirely predictable from measured use, and it becomes a surprise only where nobody measures.

Access refusal is the third. A property manager or association objecting to washing or generator noise ends the job before it starts, and the prevention is a written permission obtained before the booking rather than an apology afterward.

The fourth is weather arriving mid-job on exterior work. The response has to be decided in advance: which stages can be paused safely, which cannot, and what the customer is told. A van with interior work available on the same route recovers from this far better than one with an all-exterior day.

Reviewing operations without a dashboard

A short weekly review beats a monthly report nobody reads. Four questions:

Reviewing operations

  • Which jobs overran, and was it condition, access or the running order?
  • Where did drive time exceed plan?
  • What did we go back to the van for repeatedly?
  • What did a customer have to ask for that they should have been offered?

Question three is the layout question, and it is answered by the van build described in the equipment and setup guide. Question four is usually a packaging question, answered in the services and packages guide.

Operations and territory

A route only works if the territory supports it. Long drives between scattered jobs will defeat any amount of scheduling discipline, which is why territory choice, covered in the startup and market overview, is an operational decision as much as a marketing one.

Common questions

How much buffer should a day carry?

Enough to absorb one vehicle arriving a condition tier worse than described. Take that figure from your own records rather than from a rule of thumb.

Should the customer be present at handover?

Whenever possible. A walk-around at the vehicle resolves in two minutes what a message the next day turns into a dispute.

How do I stop the running order drifting?

Write it down, and inspect against it rather than against the finished result. A vehicle can look acceptable and still have been done in an order that will cost you later.

What is the first thing to systematize?

The condition record. It is cheap, fast, and it prevents the most expensive category of argument.

More in Guides

Latest from Value Desk