Dispatching and operations
Dispatching and operations for roofing companies
Crew scheduling, material ordering and vendor coordination — so three independent things arrive on the same morning at the same address.
A roofing production day requires three independent things to be true at the same moment in the same place: a crew that is free, material that has arrived, and permission to proceed. Any one of them late costs the entire day, and nothing partial is salvaged.
That asymmetry is what makes this department unlike the others. A late invoice is late. A missed call is a lost opportunity. A crew standing in a driveway with nothing to install is a full day of labour spent, a homeowner inconvenienced, a schedule pushed and, frequently, a second mobilisation charged to a job that was priced for one.
The three inputs also fail independently, which is why the failures feel random. The supplier slipped a delivery. A crew ran long on a tear-off nobody had inspected. The authority took an extra week. None of those is a scheduling error; each becomes one the moment nobody notices in time to move the other two.
This department covers the six desks that keep those inputs aligned: scheduling, dispatch, general operations support, vendor coordination, material ordering and purchase orders, and warranty registration. What follows sets out how the alignment breaks, what a production week actually looks like, and where coordination stops and direction begins — a line that federal rules draw, not one we invented.
-
100+
Contracting companies supported
-
9
Back office departments
-
12
Platforms supported
-
Roofing only
Count the mobilisations last month that produced no installed roof. That number is the size of this problem.
Get in TouchWhen the three inputs miss each other
Alignment failures are rarely dramatic and almost never singular. A production board drifts out of truth by small increments, and then one morning the accumulated drift produces a wasted crew day that looks like bad luck.
The commonest version starts with a board nobody has closed out. Jobs that finished on Thursday are still showing open on Monday, so a crew that is genuinely available reads as busy and a crew that is still finishing reads as free. Every scheduling decision made against that board is a guess wearing the appearance of information, and the errors surface a week later as double bookings.
Material creates the second class. An order placed without a job attached cannot be checked against anything on arrival, so a short delivery is discovered by a crew rather than by a document. Roofing runs on a small number of suppliers making a high volume of deliveries to changing addresses, which is precisely the shape in which a missing bundle count goes unnoticed until the felt runs out at two in the afternoon.
The third is the approval nobody owned. Whether it is an authority sign-off, a property-manager confirmation or a homeowner who has not returned the signed change order, an unowned approval sits still. It generates no reminder and appears on no board, and it is discovered at the moment it blocks a crew that was already dispatched.
Then there is communication drift on reschedules. A moved job has four or five parties attached — crew, homeowner, supplier, waste collection, sometimes an inspector — and a change communicated to three of them produces a worse outcome than one communicated to none, because two of them will now act on stale information with confidence.
And finally the closeout debt. Warranty registrations, final photographs and completion records are easiest on the day and progressively harder afterwards. A registration missed at closeout costs nothing measurable that quarter and surfaces years later, as an unhappy conversation about a roof that should have been covered.
A production week, from the desk
The work has a rhythm rather than a lifecycle. Three moments in the week carry most of the risk, and they are not the moments most companies watch.
The build of the week itself
Before anything is committed, the schedule gets constructed against three independent constraints simultaneously — crew availability that reflects closed-out jobs, material lead times confirmed rather than assumed, and approvals actually in hand. A week built against two of the three is not a schedule; it is an intention with a good chance of a wasted Tuesday.
The evening before each production day
This is the highest-leverage half hour in the department and the one most frequently skipped. Confirm the crew, confirm the delivery, confirm access, confirm the approval. Almost every avoidable wasted morning was visible the previous evening to anybody who checked, and the check costs minutes against a failure that costs a day.
The moment something moves
Reality intervenes constantly — weather, a tear-off that revealed more than expected, a supplier truck that broke down. The department earns its keep in how fast the consequences propagate: who else is affected, what backfills the gap, which parties get told, and whether the board reflects the new truth within minutes rather than by the end of the day.
Closeout, before the crew has left the street
Completion photographs, final counts, waste collection, and the warranty registration filed while the details are still to hand. Treating closeout as part of the production day rather than as paperwork afterwards is the difference between a record that exists and a record somebody will try to reconstruct.
The limits on what a dispatch desk can do
There is a real distinction between telling a crew where to be and telling them how to work, and it is not a semantic one. Federal rules put weight on exactly that difference, in two separate ways.
Safety is the employer’s programme. The general provisions at 29 CFR 1926.20 state, under the heading Accident prevention responsibilities, that “It shall be the responsibility of the employer to initiate and maintain such programs as may be necessary to comply with this part.” That duty attaches to the employer of the people on the roof. A scheduling desk cannot assume it, discharge it, or relieve anyone of it, and any arrangement implying otherwise would be selling a comfort that does not exist.
Responsibility between contractors is allocated by rule. The rules of construction at 29 CFR 1926.16 address how obligations sit between a prime contractor and its subcontractors. The allocation is a matter of rule and agreement rather than of who happens to be sending the schedule, which is another way of saying that dispatching a subcontracted crew does not move the obligation onto whoever dispatched them.
Control over the work is itself a fact that gets weighed. Where a company engages subcontracted crews, the classification analysis at 29 CFR Part 795 looks at the economic reality of the relationship, and the degree of control exercised over how work is performed is part of that picture. A back office that started directing method would be adding a fact to your analysis on your behalf, without being asked and without carrying the consequence.
So the line is drawn deliberately and narrowly. This department communicates where, when, what job and what material. It maintains the record of what was agreed and what changed. It never instructs a crew in method, never supervises performance on a roof, and never assumes a duty that rule places elsewhere. Keeping to that lets a company hand over the whole coordination burden without handing over anything it cannot hand over.
This describes the limits of our work and the rules those limits are drawn against. It is not legal advice, it makes no determination about your crews, your subcontracts or your safety programme, and obligations vary by circumstance. Your own counsel is the right place for those questions.
The six desks that keep production moving
Separable, though these interlock more tightly than most — the schedule, the material and the purchase order are three views of the same production day.
Most boards have at least one day this week with only two of the three lanes actually confirmed.
Get in TouchThe board, and who else can see it
In your system. A dispatch board maintained anywhere other than where your crews and your office already look becomes a second source of truth, and a second source of truth in scheduling is not a redundancy — it is a collision waiting for a Monday.
- ServiceTitan
- JobNimbus
- AccuLynx
- Buildertrend
- CompanyCam
Roofing Back Office is not affiliated with, endorsed by, or certified by any software vendor named on this site. All product names and trademarks are the property of their respective owners.
Standing this up
The board gets made truthful before anything else
Open jobs that are actually finished get closed, crews get marked accurately, and the current week is reconciled against what is physically happening. Until that is done nothing built on top of it is worth anything, and this step usually takes longer than owners expect.
The rules of the road get agreed in writing
What we schedule without asking, what we escalate, how far ahead the board is built, what the confirmation routine is the evening before, and who hears about a change in what order. These are decisions rather than preferences, and having them written down is what makes coverage possible at all.
Then we run a week alongside you before taking it
The desk operates in parallel while your existing dispatcher still holds the wheel, so disagreements surface against real days rather than in a meeting. After that the board is ours to maintain and the reporting starts on the agreed rhythm.
What makes roofing dispatch particular
Weather is a scheduling input rather than an inconvenience, and it invalidates plans wholesale rather than individually. A dispatcher in most trades handles exceptions; a roofing dispatcher periodically rebuilds an entire week at short notice, and the process has to be built for that rather than surprised by it.
The unit of work is a crew rather than a technician, which changes the arithmetic completely. Crews have composition, capability and equipment attached; they are not interchangeable, and a board that treats them as interchangeable produces schedules that look feasible and are not.
Material is heavy, delivered to a roof or a driveway rather than a warehouse, and expensive to move twice. That makes ordering a scheduling decision as much as a purchasing one — a delivery that arrives on the right day to the wrong address is nearly as costly as one that does not arrive.
And storm work inverts the whole department periodically. Volume multiplies, suppliers ration, subcontracted crews appear and disappear, and the companies that come through it are the ones whose coordination did not depend on one person holding everything in their head.
What owners ask about handing over the board
Are you telling our crews what to do?
No. We tell them where to be and what the job is, which is scheduling. How the work is performed on the roof is directed by whoever supervises it for you, and the section below explains why that separation is drawn by rule rather than by preference. In practice the crew lead notices no ambiguity: the schedule arrives, the questions about method go where they always went.
What happens when a job has to move?
Everyone affected hears it from one place, once. That is the whole discipline. Reschedules fail when the crew is told and the homeowner is not, or the supplier delivers to an address nobody is at. We hold the single version and push the change to every party attached to that job, including the ones easy to forget, like the dumpster and the inspector.
Do you order material directly with our suppliers?
Against your accounts, your pricing and your approval rules — yes. Purchase orders get raised with a job attached, deliveries get confirmed against them, and discrepancies get raised the same day rather than surfacing on a statement six weeks later. Opening supplier relationships and negotiating terms stay with you.
How do you know when a crew is actually free?
Because the board reflects reality rather than intention, which is largely a matter of maintenance. Jobs that finished get closed, jobs that ran over get extended, and a crew marked available is available. Most dispatch failures we see are not scheduling errors at all — they are a board nobody has updated since Tuesday.
Can you cover dispatch during a storm surge?
That is the period where it matters most and where an internal dispatcher is least able to keep up, because volume triples while their day stays the same length. Cover for a surge gets agreed in advance, in writing, including which decisions still route to you and which we make against rules you have already set.
What about warranty registrations?
They get filed while the job is fresh, which is the only time the information needed is easy to obtain. A registration missed at closeout is very hard to reconstruct a year later when a homeowner asks, and the cost of that failure lands entirely on your relationship rather than on the manufacturer.
We run mostly subcontracted crews. Does that change anything?
It sharpens the boundary rather than moving it. Coordination with a subcontracted crew is scheduling and information flow; direction of their work is not ours and, for reasons the section below sets out, control over how work is done is one of the facts that a classification analysis actually weighs. We keep to the coordination side deliberately.
Connected departments
- All nine departments The other functions a roofing back office absorbs, each with the failure it prevents.
- Customer Support The booking that becomes a scheduled crew day, and the caller who has to be told when it moves.
- Estimating and Project Support The approval that has to exist before a truck is worth loading.
- Finance and Bookkeeping Where a purchase order meets a supplier invoice, and what happens when it does not.
- HR and Recruiting Whether the crew you are scheduling exists yet, and whether its records are complete.
- Compliance and Documentation The certificate a general contractor checks before a crew is allowed on site.
- Working in ServiceTitan Dispatch boards and technician routing at volume.
- Working in Buildertrend Schedules, purchase orders and supplier records in one system.
- Working in CompanyCam Field capture that proves what a crew found when they arrived.
- Every platform we work in The board stays in your instance; we work on it rather than beside it.
- Storm and claims operations Longer pieces on running production through a surge.
- About Roofing Back Office Who runs this, and why the roofing work got its own brand.
Rules referenced in this page
The boundary above rests on these rather than on assertion. They are pulled by identifier from the brand configuration, and the quoted clause was taken from the fetched document rather than recalled.
- 29 CFR 1926.20 — General safety and health provisions — U.S. Office of the Federal Register (eCFR)
- 29 CFR 1926.16 — Rules of construction — U.S. Office of the Federal Register (eCFR)
- 29 CFR Part 795 — Employee or Independent Contractor Classification — U.S. Office of the Federal Register (eCFR)
Stop losing mornings to a board nobody updated
Tell us how many crews you run and how the week gets built now, and we will come back with what holding the board looks like as a written scope of work.