WeavrCRMWhy Vehicle Availability Is a Fleet-Specific Problem
Retail detailing customers bring one vehicle and they control its schedule. Fleet customers operate vehicles as business tools, and those tools move independently of your appointment. Delivery trucks go out early, service vans finish routes late, company cars travel with employees, and shop vehicles cycle in and out of a mechanic bay on no fixed timetable. None of that is malicious; it is just how fleet operations work, and your process needs to account for it.
The operational consequence is that a missed vehicle on a fleet visit is not like a single no-show. You may still have eight vehicles present and a full crew ready, so you cannot simply leave. But the two missing vehicles were part of your quoted scope and your expected revenue for the day. Without a written process, you end up either absorbing the shortfall or having an awkward conversation about partial payment that you were not prepared for.
Related resource: Test Fleet Payment Terms Against Your Detailing Cash Flow
Assign a Single Staging Contact Before Every Visit
Every fleet account needs one named person who is responsible for confirming vehicle availability before you arrive. This is not the person who signed the contract; it is whoever physically controls vehicle movement on the day of the visit, often a dispatcher, a fleet supervisor, or a yard lead. Get their direct mobile number and confirm it works at the location. An email-only contact is not sufficient for same-day logistics.
When you onboard the account, document the staging contact by name and role in your records. Also document a backup contact in case the primary is unavailable. When you reach out before a visit, address that specific person by name and reference the date and expected vehicle count. A generic message to a general inbox tends to get treated as low priority until it is too late to act.
Set a Firm Cutoff Window and Put It in Writing
A cutoff window is the point by which you need a confirmed vehicle list before you mobilize. Without it, you are making a fully committed dispatch decision based on unconfirmed information. A reasonable cutoff is the business day before the visit, at a specific time such as 3 p.m. This gives the fleet manager time to check their schedule and gives you time to adjust crew size or supply loads if the count changes significantly.
Include the cutoff in your service agreement or in a written confirmation you send before each visit. The language does not need to be legalistic. Something like: if the confirmed vehicle count falls below the agreed minimum by the cutoff time, you will discuss adjusting crew size or rescheduling the visit. The goal is not to threaten the customer; it is to create a shared expectation that both sides plan around the same deadline.
Build a Substitute Vehicle List With the Fleet Manager
Most fleets have more vehicles than they schedule in a single visit. Ask the fleet manager to identify a short list of vehicles that can serve as substitutes if a scheduled unit is unavailable on the day. These might be vehicles that are slightly lower priority, ones that are usually parked during the visit window, or units that were skipped on the previous visit. Writing down three to five candidate substitutes costs almost no time and gives you a ready answer when a scheduled vehicle disappears.
The substitute list also signals to the fleet manager that you are trying to make the visit as productive as possible. It shifts the conversation from you absorbing a loss to both sides actively managing the day together. Confirm which substitutes are approved in scope before the visit so you are not negotiating condition or service level on site.
Related resource: Quote Fleet Detailing Without Guessing at the Scope
Run a Completed and Skipped Log During Every Visit
Track every vehicle touched and every vehicle missed during the visit, with a note on why each missed vehicle was unavailable. This log has two jobs: it gives you accurate data for invoicing, and it gives the fleet manager a record they can use to plan the next visit. Without it, disagreements about what was completed are common, especially across a large account where the manager was not watching the work.
The log does not need to be elaborate. A simple table with vehicle ID, service performed, technician, time completed, and a skip reason for any missed unit is sufficient. Capture it on site rather than reconstructing it from memory later. When you hand over a completed log at the end of each visit, you are also building a professional reputation that most detailers in fleet work do not bother to establish.
FLEET VISIT LOG
Account name:
Visit date:
Site contact:
Scheduled vehicle count:
Actual vehicles completed:
Vehicle ID | Service Performed | Tech Initials | Time Completed | Skip Reason (if missed)
---------- | ----------------- | ------------- | -------------- | -----------------------
| | | |
| | | |
| | | |
| | | |
| | | |
Substitute vehicles added this visit:
Vehicles deferred to next visit:
Scope exceptions or damage noted:
Fleet contact sign-off (name and time):
Notes for next visit:Confirm Scope Before You Touch Substitute Vehicles
A substitute vehicle may be in a different condition than the scheduled unit it is replacing. Before you start work on any substitute, confirm with the on-site contact that the standard scope applies and that no additional approval is needed for condition issues. A fleet exterior wash on a scheduled sedan and a fleet exterior wash on a mud-coated cargo van are not the same job, even if they carry the same line-item name.
If the substitute vehicle clearly needs work beyond the standard scope, note it, give the contact a rough time and cost estimate, and get a verbal yes before you start. Write that confirmation in your visit log under scope exceptions. This protects you from disputes later and prevents you from doing extra work that the fleet manager had no visibility into until the invoice arrived.
Related resource: Detailing Quote Template: Scope, Price, and Approval
Hypothetical Scenario: Eight-Vehicle Visit, Two Missing at Arrival
Hypothetical situation: you have a recurring visit for a landscaping company with eight vehicles scheduled every other Tuesday. Your service agreement sets a minimum of six vehicles and a cutoff the afternoon before. On Monday at 3 p.m. you message the yard supervisor, who confirms seven vehicles will be available. You mobilize one tech plus yourself.
Tuesday morning you arrive and find six vehicles, not seven. One van left early for an emergency job. You check your substitute list, which includes a pickup that was skipped last visit. The supervisor approves the pickup as a substitute, bringing you back to seven. You complete six vehicles, skip one sedan that has a cracked window you cannot work around safely, and note it in your log with a skip reason. At the end of the visit you hand the supervisor a completed log showing seven vehicles attempted, six completed, one skipped with the reason noted. You invoice for six completed units at the agreed rate. The supervisor signs the log. At the next visit, the sedan goes first on the schedule. The visit took three hours and fifteen minutes with two people, which matches your pre-visit estimate closely because you had an accurate count before mobilizing.
How Weavr Can Support the Staging Process
Staging a fleet visit involves several moving pieces: the fleet contact, the cutoff confirmation, substitute vehicle notes, and the completed/skipped log tied to the appointment. In Weavr you can keep the fleet contact record and their staging contact details in the CRM, attach notes to the recurring appointment covering the substitute vehicle list and any scope exceptions from the previous visit, and use linked tasks to prompt yourself to send the cutoff confirmation message the day before. After the visit, notes on what was completed and skipped can be logged against the appointment before you close it out, giving you a running record across visits without relying on separate spreadsheets.
The practical takeaway
Assign a named staging contact, set a written cutoff window, keep a substitute vehicle list, and log every completed and skipped vehicle on site. Those four steps prevent most of the revenue and time losses that come from showing up to a fleet visit with an unexpected vehicle count.
Explore the relevant WeavrCRM workflow · Review integrations and requirements