WeavrCRMWhat Dispatch Covers and What It Does Not
Dispatch readiness is about logistics and communication, not about how to clay bar a panel or inspect paint for swirls. Those live in your SOP and vehicle inspection guides. Morning dispatch answers one question for each job on today's board: is everything lined up for the technician to start on time and finish what was quoted? If the answer is no, you have time to fix it before the truck leaves.
The practical scope is narrow on purpose. You are checking job-level facts that can change overnight: weather, a customer who added a service by text last night, an address that turned out to be a gated complex, or a piece of equipment that got left at yesterday's last stop. Keeping dispatch tight means it actually happens every morning instead of getting skipped when things are busy.
Related resource: Write a Detailing SOP Your Team Will Actually Use
The Five Dispatch Checkpoints
Run these five checkpoints in order. Each one has a clear pass or fail state. If something fails, you either resolve it before dispatch or you flag it as a known exception with an owner and a fallback plan. Leaving a failure unresolved and sending the truck anyway is the source of most same-day service calls.
The five checkpoints are: access, customer reachability, scope lock, equipment load, and open exceptions. They are explained in detail below, and the copyable checklist further down formats them for daily use.
- Access: gate codes, parking permissions, HOA restrictions, key handoff arrangements
- Customer reachability: confirmed contact method and a backup if the primary fails
- Scope lock: no unapproved add-ons or scope changes added since the quote was confirmed
- Equipment load: job-specific supplies and tools verified on the truck before departure
- Open exceptions: any known issue has an assigned owner and a fallback action
Related resource: Close the Detailing Day Without Leaving Loose Ends
Access: The Most Common Morning Failure
Gate codes go stale, parking spots get reassigned, and customers forget to tell the HOA that a service vehicle is coming. Access failures are the most common reason a technician arrives on time and cannot start. Checking access the morning of the job, not the night before, catches last-minute changes.
For mobile jobs, confirm the exact address, any entry instructions, and where the technician can set up water and power if applicable. For shop drop-offs, confirm the customer's drop-off time and who is handling the key. If a job requires a code or a contact to let someone in, that information needs to be in writing in the job record before the truck leaves, not in the technician's memory.
Scope Lock: Catching Changes Before They Become Disputes
Customers add requests after the quote. They text at 9 PM asking if you can do the engine bay while you are there. If that request was never approved and priced, the technician has to decide on the spot whether to do unpaid work or disappoint the customer. Neither outcome is good. Scope lock means you review the job record each morning for any changes that arrived after the quote was confirmed, and you either approve them with a revised quote or note them as declined before dispatch.
Scope changes that arrive the morning of the job are the hardest to handle. Have a simple policy: same-day add-ons need approval before the technician starts, not after. If the customer asks at the vehicle, the technician contacts the office and gets a go or no-go. That keeps pricing decisions with the person who owns pricing.
Equipment Load: A Job-Specific Review, Not a Generic Truck Check
A general truck check asks whether the truck has supplies. A job-specific load check asks whether the truck has what this particular job needs. A paint correction job needs pads and compounds that a basic wash-and-wax job does not. A ceramic coating appointment needs a climate-controlled space and specific prep chemicals. Checking the generic inventory is not sufficient if the job has non-standard requirements.
The simplest way to run this is to pull the service type for each job and match it against a per-service equipment list. Flag any job where the required item is not confirmed loaded. Equipment failures discovered in a customer's driveway cannot be quickly fixed without canceling or delaying the job, which costs you credibility and schedule time.
Copyable Morning Dispatch Checklist
Print or display one row per job. A dispatcher, a lead technician, or the owner runs through each column before the truck leaves. Any cell marked with a flag needs a resolution note before dispatch is complete. This is not a form the customer sees; it is an internal readiness gate.
The table below covers a standard three-job morning. Add or remove rows to match your day. The notes column is where you record the resolution for any failed checkpoint, such as the gate code you confirmed by text or the add-on you declined and communicated to the customer.
MORNING DISPATCH CHECKLIST — Date: ___________ Job #1 Customer: _______________________ Address / Drop-off time: _______________________ Service booked: _______________________ Checkpoint Pass / Flag Resolution note -------------------------------------------------------------- Access confirmed [ ] / [ ] _________________ Customer reachable [ ] / [ ] _________________ Scope locked, no unapproved adds [ ] / [ ] _________________ Job-specific equipment loaded [ ] / [ ] _________________ Open exceptions assigned [ ] / [ ] _________________ Job #2 Customer: _______________________ Address / Drop-off time: _______________________ Service booked: _______________________ Checkpoint Pass / Flag Resolution note -------------------------------------------------------------- Access confirmed [ ] / [ ] _________________ Customer reachable [ ] / [ ] _________________ Scope locked, no unapproved adds [ ] / [ ] _________________ Job-specific equipment loaded [ ] / [ ] _________________ Open exceptions assigned [ ] / [ ] _________________ Job #3 Customer: _______________________ Address / Drop-off time: _______________________ Service booked: _______________________ Checkpoint Pass / Flag Resolution note -------------------------------------------------------------- Access confirmed [ ] / [ ] _________________ Customer reachable [ ] / [ ] _________________ Scope locked, no unapproved adds [ ] / [ ] _________________ Job-specific equipment loaded [ ] / [ ] _________________ Open exceptions assigned [ ] / [ ] _________________ Dispatch approved by: _______________________ Time: _______
Worked Scenario: A Scope Change and a Weather Call on the Same Morning
This is a hypothetical example. Suppose a two-person team has three jobs on a Tuesday: a full detail at a gated community at 8 AM, a paint correction at a private residence at 11 AM, and a maintenance wash at a shop drop-off at 2 PM. During the 7:45 AM dispatch review, the lead checks the job record for the first appointment and finds a text from the customer that came in at 10 PM: can you also do the leather conditioning on my wife's car that is in the same garage? That service was never quoted.
The lead flags the scope checkpoint for Job 1. Before dispatch, she texts the customer with the price for the leather conditioning add-on and asks for a confirmation. The customer responds yes at 7:52 AM and the revised scope is noted in the job record. The truck leaves at 8:00 AM with a clean scope. For Job 2, the dispatch check also surfaces a weather flag: a storm is forecast to arrive at noon, which would prevent the paint correction from curing properly. The lead calls the customer at 7:55 AM, explains the issue, and moves the appointment to Thursday. The 2 PM drop-off is unaffected because it is a covered shop. The dispatch review took twelve minutes and prevented two potential problems from becoming mid-job crises. Note that the hypothetical cost of the add-on and any rescheduling terms depend on your own pricing and policies.
Where Dispatch Fits in Your Daily Workflow and How Weavr Supports It
Dispatch works best when it draws on information that is already organized, not when someone has to hunt through texts and paper notes to reconstruct what a job requires. If your job records, customer contact details, and scope notes live in one place, the ten-minute review actually takes ten minutes. If they are scattered, it takes longer and things get missed.
Weavr's appointment and contact workflow gives you a single job record that holds scope, contact method, and linked tasks, so a morning dispatcher can review each job without switching between tools. Linked tasks can flag unresolved items from the previous evening, such as an unanswered quote or a missing gate code, that carry into the morning review. The day-close process handled by a closing checklist and the dispatch review handled by this one are complementary: a clean close the night before makes the morning review faster.
Related resource: Link Detailing Follow-Up Tasks to the Customer and Appointment
The practical takeaway
Run the five checkpoints in order before the truck leaves: access, reachability, scope lock, equipment load, and open exceptions. Any failed checkpoint needs a resolution note and an owner, not a hope that it works out on site.
Explore the relevant WeavrCRM workflow · Review integrations and requirements