Dispatching and Operations
Vendor Coordination for roofing contractors
You can move a crew and you can move a day. You cannot move a supplier, and wanting it sooner has never once worked.
A date somebody actually gave you
A commitment on the record with a day attached to it, obtained from the supplier rather than inferred from how long it usually takes. The difference between those two is invisible right up until the week it matters.
A named person at the other end for each order. Not a branch, not a general inbox — somebody who knows your account and can be asked a question that gets a real answer.
And a record of what slipped, attached to the job it affects. Slippage recorded in isolation is trivia; slippage attached to a crew booked for Thursday is a decision waiting to be made while there is still time.
The one constraint effort cannot touch
A roofing business spends most of its time on problems that yield to work. Behind on paperwork, somebody stays late. Short a crew, you move one. Weather takes a day, the day gets rebuilt. All of it responds to attention, which is why attention is the instinctive answer.
A supplier is not like that. Their production, their allocation and their transport are theirs, and your urgency is one of many inputs they are already weighing. Ringing twice a day does not advance the queue. The only thing you genuinely control is what was agreed at the start and how early you learn that it has changed.
Which relocates the whole job. The work is not chasing — chasing is what a company does when it has no early warning and has substituted effort for information. The work is getting a specific commitment from a specific person, and then checking in on a rhythm that surfaces a slip before it becomes an emergency. Both of those happen long before the delivery date.
The failure this prevents is also specific and expensive. It is not the late delivery. It is the crew that arrived, the morning that was lost, and the customer who now knows something went wrong — all of which happened because a fact that existed at the supplier’s end two days earlier had not travelled.
The delivery date nobody actually agreed
An order placed without an agreed date is not an order with no date. The law fills the gap, and what it fills it with is deliberately elastic. Taking one state’s enactment of the commercial code as a worked example, California Commercial Code section 2309 provides that the time for delivery or any other action, where it is not agreed upon, “shall be a reasonable time”.
That is a sensible default and a poor basis for a schedule. Reasonable is decided after the fact, by reference to the circumstances, by somebody who was not there — which is precisely the position a contractor does not want to be in with a crew booked. It is worth knowing mainly for what it implies: the vagueness in an unstated delivery date is not neutral, it resolves somewhere, and probably not where you assumed.
The same section adds that where a contract provides for successive performances but is “indefinite in duration it is valid for a reasonable time”, which is the standing-order case most roofing companies have with at least one supplier and have never written down.
This is a commercial code provision governing contracts for goods between the parties to them. It does not bind this brand, which is not a party to your supply arrangements, buys nothing on your behalf and holds no account with any supplier. It is quoted for one narrow purpose: a date left unsaid is a term left vague rather than a term left out, and asking for the day is cheaper than discovering later what reasonable turned out to mean.
This describes one state’s commercial code in general terms. It is not legal advice, it makes no determination about your contracts, your orders or your suppliers, and the position differs by state and by agreement. Those questions belong with your own counsel.
The part of the plan somebody else holds
This desk sits inside Dispatching and Operations, and the department boundary is set out there rather than repeated here. What is particular to this page is the counterparty: every other function in the department coordinates something the company controls, and this one coordinates something it does not.
What owners ask about their suppliers
Our supplier says it is coming. Why is that not enough?
Because "coming" is not a date and cannot be planned against. It is usually said in good faith by somebody who genuinely expects it, which is exactly why it goes unchallenged. The useful question is narrower and slightly awkward to ask: what day, and who at your end is confirming that. An answer to it is something a schedule can be built on; a reassurance is not.
What do you actually do here?
Get the commitment on the record, keep a named person at the other end attached to it, and check in early enough that a slip is news rather than a discovery. Most of the value lands in the gap between when a supplier knows something has moved and when you would otherwise have found out.
Do you choose our suppliers or negotiate pricing?
No. Which suppliers you use and on what terms is a commercial relationship that belongs to you, and it depends on things this desk has no view of — volume, history, credit, who took your call in a bad week. We coordinate what has been agreed rather than deciding who you agree it with.
Why insist on a named contact?
Because an order attached to a company is attached to nobody. A general number gets a general answer, and the person who reads the message may not be the person who knows. One name, who knows your account, converts every future question from a fresh explanation into a short conversation — and tells you immediately when that person leaves.
What happens when something slips anyway?
It gets recorded against the job it affects rather than noted in isolation, because a delivery moving by two days is meaningless on its own and important if a crew is booked for that morning. The point of tracking slippage is not to build a case against a supplier. It is that the schedule can respond while responding is still cheap.
Should we be putting delivery dates in writing?
Where it matters, yes, and the reason is worth knowing: an unstated date is not an absent term, it is a vague one, and vague terms get filled in by a default nobody chose. The section below sets out what that default looks like. Writing the date down is less about enforcement than about two parties discovering now rather than later that they meant different things.
The commercial code provision cited here
- California Commercial Code section 2309 — Absence of specific time provisions — California Legislative Counsel
Name the person at your main supplier
If the answer is a branch rather than a person, that is where your early warning was supposed to come from.