It is 4:45 p.m. The shop takes a truck out of service and the evening dispatcher starts assigning jobs from yesterday’s roster. The truck may be physically parked in the yard, but that does not make it available. A backup plan begins with a reliable way to tell dispatch what can actually be assigned.
The goal is to keep service commitments honest while the truck is unavailable. This article covers scheduling, communications, and handoffs. It does not tell you when a defect is safe to ignore, what equipment to send, or whether you may transfer a contracted job. Those decisions belong to the qualified staff and authorities responsible for them.
Make availability a status, not a guess.
Use a single record with simple statuses: available, assigned, unavailable, or release pending. Include the unit, timestamp, person who changed the status, and next update time. Dispatch needs to know what is available for its approved work; it does not need every detail of a repair in the dispatch channel.
If a vehicle is taken out of service, remove it from assignment and make the change visible to the next shift. A whiteboard can work for a small shop if everyone can see the same current version. For a multi-location operation, the crew handling after-hours calls needs the same status without depending on a photograph of an old board.
Match backup coverage to the service you promised.
A backup truck on paper is not enough if the matching operator is unavailable or the truck is already assigned elsewhere. Identify the categories of work you can still handle, who can approve dispatch, and the hours and service area for that coverage. Keep unknown capability marked unknown. Never assign equipment outside the confirmed configuration or operator qualification to cover a scheduling gap.
If you plan to ask another company for help, agree in advance on the procedure and confirm it is permitted for the account or rotation involved. Write down who contacts the partner, who approves the handoff, who bills, and what customer information may be shared. A directory listing is a starting point for contacting a provider; it is not proof of capacity, insurance, approval, or availability.
Give customer updates before a promise goes stale.
Review open jobs as soon as the status changes. Separate jobs that can still be handled from jobs that need a revised arrival estimate or an authorized transfer. Contact the parties who need the update through the agreed channel. State what is confirmed and when you will follow up. Do not promise an arrival time before the backup is confirmed.
Keep the original job reference with any handoff. Record the new assignment, which customer or agency contact approved it, and when the receiving person acknowledged it. For a public safety call, coordinate with the dispatching authority rather than independently changing the responding provider.
Rehearse a two-truck example.
In a fictional exercise, Unit A becomes unavailable with two jobs in its queue. Unit B is already assigned and will not be free for an hour. One pending job belongs to a fleet account with an approved backup contact; the other is an agency call. Dispatch confirms the fleet account’s instructions and contacts the agency through its designated channel for the second job. Neither job is quietly reassigned to an unconfirmed provider.
Have a second person read the record at the end of the exercise. They should be able to identify the truck that is down, the status of each job, and who owes the next update. If any of those facts live only in a private text message, move the information to the approved record.
A five-line backup coverage plan
| What to record | Primary owner | Evidence it worked |
|---|---|---|
| Unit status and timestamp | Shop or designated fleet lead | Dispatch sees the same status |
| Jobs affected and next update | Dispatcher | Open jobs have a current owner and update time |
| Approved backup capability | Operations lead | Confirmed truck, qualified operator and account approval |
| Customer or agency handoff | Dispatch or account contact | Receiving party acknowledges the current assignment |
| Return to service | Authorized fleet or maintenance lead | Release is recorded before dispatch marks it available |
Define who can put a truck back on the board.
A repair estimate or parts-delivery notice is not a release to service. Keep the unit unavailable until the appropriate person confirms that the required work and checks are complete under your procedures and any applicable rules. Record the release with the unit ID, date, and the authorized person. Dispatch then updates availability and acknowledges the change.
Keep the maintenance record with the supporting work order and verification. If you need federal guidance for a covered operation, start with the FMCSA Motor Carrier Safety Planner and confirm the requirements that apply to your vehicle and operation. The dispatch board is not a substitute for those records.
Review downtime without confusing speed with readiness.
After the unit returns, review when the outage became known, when dispatch learned about it, and when affected customers were updated. Look for the delay that caused extra work. You may need a backup contact, clearer shift handoff, or a different method for showing a unit’s status. Avoid pressuring staff to mark the truck available before it has been released.
If the outage affected your monthly volume, update the cost per tow worksheet using the actual completed jobs and documented costs. That gives your planning team a better estimate of what happens when backup capacity is limited.
Common questions
Can a smaller truck cover a larger job if it is all we have?
Do not substitute equipment outside its confirmed suitability or operator qualification. Escalate for an approved response instead.
Can we refer a rotation job to another company?
Follow the rotation or agency rules and the instructions of the dispatching authority. A general backup arrangement does not override those requirements.
What should the dispatcher see about the repair?
Availability, approved limitations if any, the status owner, and the next update. Keep the detailed repair and release documentation in the appropriate maintenance record.