Dispatching and Operations
Dispatching for roofing contractors
The plan was made once, carefully. The day gets decided twenty times, in a hurry, by whoever picked up the phone.
A day that holds after the first thing goes wrong
Movements made against a plan rather than against a blank morning, so that when something has to give it is clear what else is affected and who else is now waiting.
The decision captured as it happens — what moved, why, and who was told. Not reconstructed at the end of the week, when the only remaining source is what several people think they remember.
And one message going out rather than several. The most common failure on a changing day is not a bad decision; it is a good decision communicated three times in three slightly different forms.
Re-deciding is not the same activity as deciding
A schedule is built with the whole picture in view: every crew, every job, time to think. A dispatch decision is made at ten past seven with a crew sitting in a truck, one fact that has just changed, and no view of what else depends on the answer. They are different cognitive jobs, and treating the second as a quick version of the first is why days unravel.
The cost of a change also lands somewhere other than where the decision is made. Move a crew from one job to another and the office does not feel it — a homeowner does, and a supplier who delivered to the original address does, and tomorrow’s schedule does, because the work that was displaced still has to happen. None of that is visible to whoever is holding the phone.
Which produces the characteristic failure. Every individual decision on a bad day is defensible, and the day is still a disaster, because the decisions were made serially by people who could not see each other. Nobody was wrong. There was simply no single place where the day was being held.
So the deliverable is less about making better calls than about there being one version of the day, one route for a change to travel, and a record of what was decided while it can still be checked. That is also what makes the next bad day cheaper than this one.
How far, and released by when
Distance and finishing time are usually treated as separate questions, and for some vehicles a federal rule ties them together. The hours of service rules carry an exception whose conditions are, in effect, a dispatching constraint. Under 49 CFR 395.1, one condition is that the driver “operates within a 150 air-mile radius (172.6 statute miles) of the normal work reporting location”, and another that “The driver, except a driver-salesperson, returns to the work reporting location and is released from work within 14 consecutive hours”.
Read that from the dispatch desk rather than from a lawyer’s chair and it is a single combined limit: how far you send them and when you let them go are the same decision. A crew sent a long way and then held late has crossed a line that neither the distance nor the finishing time would have crossed alone.
It does not reach every vehicle, and the page would mislead if it implied otherwise. The definition at 49 CFR 390.5 provides that a “Commercial motor vehicle means any self-propelled or towed motor vehicle used on a highway in interstate commerce to transport passengers or property” where it has a gross vehicle weight rating or gross combination weight rating “of 4,536 kg (10,001 pounds) or more”. A pickup under that rating, used locally, sits outside it; the same pickup towing a loaded trailer may not.
These rules bind motor carriers and drivers. They do not bind this brand — nothing on this desk drives anything or determines anyone’s duty status — and nothing here is a determination about your vehicles or your operation. They are cited because a dispatch decision that looks purely commercial can have a records consequence, and knowing which of your vehicles that could apply to is worth establishing once, with your own adviser, rather than per job.
This describes federal motor carrier provisions in general terms. It is not legal advice, it makes no determination about your vehicles, your drivers or your obligations, and the position depends on facts about your operation. Those questions belong with your own counsel.
Where coordination stops
This desk sits inside Dispatching and Operations, which owns the boundary for the whole department — where coordinating work stops and directing how it is performed would begin, and where responsibility for a jobsite actually sits. That is set out there rather than repeated here, and it is worth reading alongside this page rather than instead of it, because this is the function that sits nearest to it.
What owners ask after a bad morning
What does this desk do that the schedule does not?
It handles the difference between the plan and the day. The schedule decided who was going where; by seven in the morning somebody has not turned up, a homeowner has not left a gate unlocked, and it is raining twenty miles away but not here. Dispatching is the sequence of small re-decisions that follow, and the record of them.
Do you tell our crews how to do the work?
No, and the line is worth stating precisely because it is narrower than people expect. This desk deals in where and when — which address, what time, what changed. How the work is carried out once a crew is on site, and everything about how it is done safely, belongs to you and to whoever runs your production. The department page linked below sets out that boundary for the whole department.
Our days change constantly. Can any of this be systematised?
The changes cannot. What can be systematised is the response: who decides, who gets told, and where it is written. Most of the damage from a chaotic day is not the chaos — it is that three people made three reasonable decisions without knowing about each other, and nobody can reconstruct afterwards which one the crew actually acted on.
Why does it matter that a decision gets written down at the time?
Because it is unrecoverable afterwards. A day with fifteen changes leaves no trace if none of them were captured, so the following week the same conflict arrives and is solved from scratch. The record also settles the ordinary argument about whether somebody was told, which otherwise comes down to two recollections.
Who talks to the customer when their day moves?
Somebody does, immediately, and that is the part most often missed. A crew reassigned at eight in the morning means a homeowner waiting at ten who has taken time off work. The reassignment may be entirely correct and the failure is still the phone call nobody made.
Does how far we send a crew matter beyond the fuel?
It can. Once a vehicle over a certain weight is involved there are federal rules about how far and how long, and they interact with what time a crew is released rather than only with distance. The section below sets out the shape of it and where it stops applying.
The motor carrier provisions cited here
- 49 CFR 395.1 — Scope of the hours of service rules — Federal Motor Carrier Safety Administration, via eCFR
- 49 CFR 390.5 — Definitions — Federal Motor Carrier Safety Administration, via eCFR
Reconstruct last Tuesday from what you have
If nobody can say what moved and who was told, that is the gap, and it is a recording problem rather than a judgement one.