Dispatching and Operations
Job Status Tracking for roofing contractors
Four people can tell you where a job stands. The problem is that all four are right and none of them agree.
One answer to where a job stands
A single record the whole company reads, rather than a private version per desk. Not a new system — the one you already use, made into the one everybody actually looks at.
Stages with written definitions, so that a word means the same thing to the person who sold the job and the person who has to deliver it. The definitions matter more than the names.
And a date stamped when a job moved, not when somebody noticed. That one field turns a status board into something that answers the question worth asking, which is not what stage a job is in but which jobs have stopped.
Four correct answers to one question
The interesting thing about job status in a roofing company is that it is rarely wrong. Ask the salesperson and the job is sold. Ask production and it is waiting on material. Ask the office and the permit is in. Ask finance and it has been invoiced for the deposit. Every one of those is accurate, current and useless, because none of them is the status of the job.
This is a different failure from a record going stale, and it needs a different fix. A stale record has one version that lags; updating it sooner solves it. Divergence has several versions that are each up to date within their own frame, so updating faster makes it worse — each desk maintains its own copy more diligently and they agree no better than before.
It also degrades quietly, because everyone has a workaround. People learn which colleague to ring for a real answer, and that habit hides the problem while making it permanent — the knowledge lives in a person rather than a record, and it leaves when they are on holiday. Nobody experiences a system failure. They experience a company where you have to ask around, which feels like the normal cost of doing business.
The remedy is unglamorous and mostly definitional: agree what the stages mean, pick which record is the one, and make updating it cheaper than maintaining a private copy. Almost none of that is software.
Some of the dates are not yours to set
Most stage transitions are internal conventions and you can define them however suits the business. A few are not. Once money has changed hands, some states put an explicit clock on what happens next, and it runs from the payment date rather than from whenever the job reaches the top of a list. Taking one state as a worked example of the class, Florida Statutes section 489.126 requires a contractor in the circumstances it describes to “Apply for permits necessary to do work within 30 days after the date payment is made” and to “Start the work within 90 days after the date all necessary permits for work, if any, are issued”.
Read that as an operations question rather than a legal one and it says something specific about record-keeping. Two of the dates that matter most about a job — when a payment was taken, and when permits were issued — are held by two different desks, and the obligation that connects them belongs to neither. A status board that shows a stage without those dates cannot answer the question at all.
Every state constructs this differently and many do not construct it at all; the provision is quoted to show the shape of the thing rather than to describe anyone’s duties. This brand holds no contractor licence, takes no deposits and makes no determination about whether any provision reaches your work. What this desk does is make sure the dates a question could be asked about are recorded somewhere findable, which is worth doing regardless of which state you are in.
This describes one state’s statute to illustrate that such timelines exist. It is not legal advice, it makes no determination about any contract, payment or job of yours, and requirements differ materially by jurisdiction. Those questions belong with your own counsel.
The record the other desks read
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 that it produces no movement of its own: scheduling and dispatching change what happens, and this function only ensures that everybody is looking at the same account of it.
What owners ask about their own board
Everybody already tracks jobs. What is missing?
Usually nothing is missing — there is too much. Sales has a pipeline, production has a whiteboard, finance has an invoice list, and each is accurate about the slice its owner cares about. What does not exist is one place where the job has a status, so the real answer to any question is produced by ringing two people and reconciling them.
Why do stage names matter so much?
Because a stage nobody defined means something different at each desk. "Scheduled" can mean a date exists in someone’s head, a date the customer has been told, or a date with a crew committed to it. Three readings of one word, and the disagreement only surfaces when somebody acts on the wrong one. Defining them is dull and it removes an entire class of argument.
Do you replace our systems?
No. We work inside whatever you already use rather than introducing another place for a job to be recorded, because adding a system is how companies get into this position. The work is deciding what the stages mean, getting one record to be the one everybody reads, and keeping it moving.
What does "the date it last moved" tell us?
Which jobs are stuck, which is a different and more useful question than which stage a job is in. A job sitting in the same stage for a long time is not necessarily a problem, but it is always worth a look, and it is invisible on a board that shows only current status without a timestamp.
Who updates it?
Whoever caused the movement, at the point it happened — that is the only version that works. A record maintained by one person interviewing everybody else is a report, and it is out of date the moment it is compiled. The job of this desk is to make updating cheap enough that the person who knows does it themselves.
Is this just for the office, or does it matter outside?
Both, and the outside part surprises people. Some of the dates attached to a job are set by law rather than by preference — what happens after a deposit is taken, when work is expected to begin. Those run whether or not anybody is watching the board, and the section below sets out one state’s version as an example.
The deposit-timing statute quoted here
- Florida Statutes section 489.126 — Moneys received by contractors — Florida Legislature
Ask three people where one job stands
Do it without warning and write down the three answers. The gap between them is the size of this problem.