A driver says the car is “at the exit by the gas station.” Dispatch puts the nearest truck on the call. Ten minutes later, the operator is on the wrong side of a divided highway, looking at a different gas station. The mistake began when an uncertain location got written down as a confirmed one.
A useful towing dispatch sheet separates what the caller reported, what the dispatcher verified, and what still needs a supervisor’s decision. Use the outline below to design a call record for your own operation. Public safety calls and rotation jobs follow the instructions and communication channels of the responsible agency. This guide is about collecting and relaying information; it does not select a truck, set a recovery plan, or authorize a response.
Identify who is requesting the service.
Start with the caller’s role: motorist, fleet manager, roadside assistance network, property representative, or public safety agency. Record the callback number and, when relevant, the account or incident reference. A direct customer request and a rotation call may have different authorization and billing routes. Use the process attached to that job rather than copying details from an earlier call.
If the caller reports an injury, fire, immediate traffic danger, or another emergency, follow your escalation policy and direct them to emergency services as appropriate. Do not ask callers to walk into traffic or inspect a vehicle to answer your questions. Mark facts reported by a caller as unconfirmed until the appropriate person verifies them.
Confirm the location in words the operator can use.
For a street address, confirm the municipality and identify which entrance is intended. At a large parking lot, the business name alone may not narrow the location enough. Ask for a designated gate, lot letter, or another visible landmark the caller already knows. A map pin can help but should be checked against the caller’s description.
For a highway call, record the route, direction of travel, and the exit, marker, or crossroad the caller can identify safely. Include whether an agency is already coordinating the scene and its approved contact route. Repeat the location back: “Eastbound, just past Exit 14, not the westbound ramp.” If you still cannot distinguish two locations, leave the record marked uncertain and use your escalation process.
Capture the vehicle and job without guessing.
Write down the vehicle type and, if known, its year, make, model, unit number, and any trailer or load. Record the requested service and the reported condition or access restriction. For example, a commercial vehicle in a gated yard raises different questions from an unattended passenger car at a repair shop. The information helps a qualified person determine the right response; a dispatcher should not infer equipment capacity from a vehicle label or an incomplete description.
Ask about the destination before the truck leaves when possible. Verify that the receiving location expects the vehicle, can accept it at the expected time, and has a clear instruction for after-hours arrivals. Record who approved a destination change. A driver should not have to choose between an old address in the dispatch text and a new address the customer gave to the office.
Send one handoff and make updates easy to spot.
Give the operator one current record: location, vehicle, request type, destination or pending destination, who is coordinating, and the unresolved questions. Use timestamps and distinguish “assigned,” “acknowledged,” and “arrived.” The fact that a message was sent is not proof that it was received or understood.
If the customer moves, the scene changes, or the destination closes, update the same record and tell the assigned operator through the approved channel. For public safety work, relay changes according to the agency’s procedures. Do not put sensitive incident details in open group chats, and collect only the information needed for the job.
Copy these fields into your dispatch sheet
| Field | Record | What requires a follow-up |
|---|---|---|
| Request and authority | Caller role, callback, account or incident reference | Missing authorization or conflicting instructions |
| Location | Confirmed street or route, direction, landmark or gate | Two possible locations or a changed scene |
| Vehicle | Reported type, unit ID, trailer or load if applicable | Unknown vehicle configuration or access limits |
| Destination | Approved destination, hours, receiving contact | Closed or unavailable receiving location |
| Updates | Latest change, who approved it, who acknowledged it | Operator has not acknowledged a material change |
Walk through a fictional call at a shift meeting.
A fleet caller reports a van “near the loading dock” at a campus with two loading areas. The dispatcher records the company unit number and work order, confirms that the caller means Gate B on Service Road, and verifies the receiving shop closes before the expected arrival. Instead of assigning a closed destination, the dispatcher marks it pending and contacts the fleet account’s authorized approver. The updated record identifies the approved after-hours location and the person who confirmed it.
Run this example with someone who did not take the call. Can they find the current location, see who approved the destination, and explain what would trigger a second call to the supervisor? Any answer that depends on reading an employee’s private text thread is a handoff gap worth fixing.
Use closed jobs to improve the sheet.
For a week, tag a few calls that required a second trip, a corrected location, or an invoice follow-up. At the end of the week, look for the missing fact that would have prevented the extra work. Add one field or change one prompt, then check whether the same issue returns. A form gets better by preventing predictable errors, not by collecting more information on every call.
If you dispatch for a contracted fleet customer, connect this call sheet to the fleet account setup checklist so the operator can see the approved contacts and billing reference without searching through the original agreement.
Common questions
Should we make a customer complete every field?
No. Record what the customer knows safely and what the operator or agency must confirm. Keep the distinction between reported and verified details.
Is a dropped map pin enough?
A pin is useful if it matches the address, route direction, or gate the caller described. When those disagree, flag the location as uncertain and verify it through your normal process.
Can we use one form for all jobs?
Use a short common record and add the fields required for particular fleet accounts, roadside programs, or public safety agreements.