A fleet parked outside a depot at 06:40 is not a set of dirty vehicles; it is a schedule that has already started. If the washing bay cannot turn each unit around between shifts, the wash either slips into the next day or it never happens, and nobody can say afterwards which of the two it was. A service provider who wants to clean truck exteriors between shifts therefore has two problems at once: a cleaning duty that finishes inside a fixed window, and a written record that proves what was actually done on each unit. The second problem is the one most operators leave unsolved, and it is the one that decides whether the service is worth paying for.
What the record is for before it is for anyone else
Three readers need the same document for different reasons, and a record built for only one of them fails the other two. The customer's transport manager wants evidence that a specific vehicle was cleaned on a specific date, because their own audits and their own hygiene or brand standards rest on that. Your shift supervisor wants to know whether tonight's run finished, what stopped it, and what the next shift has to pick up. You want to defend an invoice when a customer claims a unit was missed, and to price the next contract from real cycle times instead of a guess. A log that answers all three is a one-page record per vehicle per visit, not a stack of photos on a phone.
That framing matters because it changes what gets written down. Nobody needs a line that says "washed". They need the vehicle identifier, the start and end time of the wash, the surface covered, the method used, anything deliberately not cleaned, and who signed the job off.
Define the exterior once, in writing, and keep it narrow
"Truck exterior" is not a scope. Before the first shift, write down what is inside the service and what is outside it, per vehicle class. In practice an exterior for this purpose is the painted body panels, the cab surfaces, the wheels and wheel arches, the step areas and handholds, and the load-contact surfaces on tankers and bulk bodies that food or feed operators ask about. Engine compartments, and the vehicle's electrical and sensor assemblies, are normally excluded from a between-shift exterior wash and are handled as a separate job with its own procedure. The PowerDe page for the fixed steam cleaning machine describes vehicle exterior cleaning at filling stations and parking areas and treats engine-compartment work as a distinct task; that separation is exactly what a written scope needs, because the exclusions are where disputes start.
Put the exclusions in the log template as a checkbox, not as a footnote. The person doing the wash should be able to record "engine bay not cleaned, per scope" in one mark.
Match the deposit to the method, not the vehicle to the ritual
Between shifts there is rarely time to soak anything. What a driver can see on the panel is usually one of three things: loose road film, oil and grease carry-over from the road, or dried salt and mud concentrated behind the wheels and in the chassis shadow. Each needs a different response, and the difference is what makes the window. Loose film needs water and a wipe. Greasy film needs heat at the surface, which is where truck steam cleaning equipment earns its place in a bay that cannot afford dwell time. Thick caked mud behind the arches needs a mechanical pass first, and on a tight window that is often the item you cut and record as cut, rather than the item that quietly breaks the schedule.
The published parameter rows on the PowerDe HW02 page - 220 V working voltage, 6 kW heating power, an 80 L SUS304 tank, a tap-water inlet with a 4-point internal-tooth joint, and both dry-steam and wet-steam modes - are page records for one fixed machine, not a claim about your cycle. Two of them are directly useful to a between-shift plan anyway: a fixed machine has a water budget you can plan against, and dry versus wet steam is a switch you make per surface rather than a decision for the whole fleet.
Build the window itself, with named positions and real clock times
A shift-interval wash is a sequence of blocks, and each block needs an owner and a measured duration taken from your own yard, not from a brochure. In a typical depot layout the blocks are: move-in and chock, dry brush-down of caked deposits, the cleaning pass working top-down on panels, wheels and arches, a wipe-down and inspection walk, and move-out into the staging lane. Write the sequence down once with a clock time against each block and one unit per lane, so that a 40-minute window is a real constraint people can see rather than an aspiration on a whiteboard.
Three site items decide whether the sequence runs at all. A fixed unit needs a stand position with measured clearance around it - the HW02 page lists 1,200 x 800 x 1,200 mm including handles, which is the space you have to keep clear, not a number to admire. It needs an accessible power supply and a water connection at that position, and it needs somewhere for the run-off to go. A drainage point that is not decided before the first shift is the most common reason a bay stops cleaning after two weeks.
Write the evidence fields you will actually be asked for
Keep the per-visit record short enough that it gets filled in. The fields that hold up in a dispute are fixed: vehicle identifier and odometer or depot reference; date and shift; time in and time out; who performed the wash; scope item ticked and exclusions ticked; method used for the greasy areas; anything re-cleaned and why; the name of the person who signed it off; and any defect noticed on the body that is being reported back to the customer. The re-clean line is worth its weight. A panel re-passed once, recorded honestly, is evidence of a process; a panel that was quietly ignored is a claim you cannot answer.
Add one summary line per shift - units attempted, units completed, units not completed and the reason - and keep that sheet for 12 months. That is the page you take into a contract review.
Prove the claim with one bounded trial, not a whole-fleet launch
Before you sell a between-shift product, run it on three units of the dirtiest class, on a real window, with the evidence fields already printed. Decide in advance which surfaces you expect to fail - usually the arch shadow and the door seams - and record them as failures instead of polishing them for the report. Then compare the trial against your own numbers: minutes per unit, water used per unit, whether the wash finished before the first truck left, and whether a supervisor could read the records without asking questions. A fleet vehicle steam cleaning machine decision is then made on your depot's data. If a fixed machine does not suit your lane, the customized steam cleaning equipment brief at PowerDe's solutions page is where you send the measured figures - vehicle classes, the deposit you are fighting, the window you have, the power, water and drainage you actually have at the stand position - rather than asking for a recommendation in the abstract.
Review the record, and change the procedure when it lies
A logging routine dies the week nobody reads it. Put a 15-minute review at the end of each week: which exclusion appeared most often, which block ran over, which units were re-cleaned. Every one of those answers should be allowed to change the written procedure, and the change should be dated on the procedure itself. That is what turns a pile of forms into a service specification you can quote from, train a new driver-operator against, and hand to an auditor without explanation.
Three things to settle before the next shift starts
First, the scope: what "exterior" means for each vehicle class, in one page, with exclusions named. Second, the record: one sheet per vehicle per visit, with the fields above, reviewed weekly. Third, the window: measured block times, a stand position with clearance, power, water and drainage settled. Settle those three and a between-shift exterior programme becomes something a provider can promise, evidence and price - and something a customer renews.
