Every roofing company has a checklist. It is taped inside a truck door, or it is a laminated card the production manager hands to a new crew lead, or it is a page in a binder that was current two years ago. Ask anyone on the crew whether the checklist matters and they will say yes. Ask whether a job has ever been held because an item on it was not done, and the room goes quiet.
That silence is the whole subject of this post. A checklist that cannot stop anything is a suggestion. The version worth building is the one that sits between a job and its next stage and does not move until the required items are done, by a named person, with the evidence attached.
A list and a gate are different things
A list is a memory aid. It helps a careful person remember what a careful person would do anyway. A gate is a rule the software enforces: when someone tries to advance a job from one stage to the next, the system first looks at the required items for the stage the job is currently in, and if any are incomplete the transition is refused and the reason is spelled out, item by item.
In BetterRoofingPro that check runs before the stage change is even evaluated for validity. The job stays where it is, and the message names each required item that is still open, so the person trying to move it knows exactly what is missing rather than being told the job is not ready.
Three places a roofing checklist can live
| The truck door | A shared document | A stage gate on the job | |
|---|---|---|---|
| Who decides an item is done | Whoever is holding the pen | Whoever last opened the file | A named user, with the time recorded on the item |
| What happens if it is skipped | Nothing, until the callback | Nothing, until someone notices | The job cannot advance, and the refusal names the item |
| Where the photo goes | Someone's phone | A folder, maybe | On the checklist item, with a thumbnail and the date it was taken |
| Where the customer signature goes | A carbon copy | A scan, eventually | On the item, with the signer's name; a required signature item is not complete without one |
| What a new hire learns from it | What the last crew lead remembered | What the document said when it was written | What this company requires at this stage, for this kind of job |
| How it fails | It fades | Two versions disagree | A required item nobody set up is a step nobody is asked to take |
The third column's failure mode is the honest one. The gate is only as good as the templates behind it. An empty template for a stage means the stage has no gate, and the software will not invent one for you.
What makes an item real
The weakest checklist item is a box. Anyone can tick a box, and a box ticked from the office looks identical to a box ticked on the roof. So the items that carry weight are the ones whose completion requires something that could only come from the work being done.
BetterRoofingPro gives a checklist item a type, and the type changes what counts as complete. A photo item can require a minimum number of photos before it is satisfied; each photo is stored against the item with a thumbnail and the date it was taken. A signature item is not complete until a signature has been captured and the signer's name recorded, and it can carry a witness signature alongside. A multiple choice item is not complete until a selection has been made. A text item takes a note, and if the template links that item to a field on the job, the customer or the property, completing the item writes the note into that field, so the checklist becomes the way the record gets filled in rather than a second copy of it.
Every completion, and every un-completion, writes an entry in the job's history naming the item, who did it, and what was written. That history is the difference between a checklist that says the tear-off photos were taken and a checklist that can show you the photos and tell you who took them.
Where the templates come from
The items on a job are not typed in per job. They are seeded from templates when the job enters a stage. A template belongs to a stage, and it is either company-wide or scoped to a program. When a job belongs to a program that has its own templates for the stage, those are used; when it does not, the company-wide templates are. If neither exists for that stage, nothing is seeded, and the log says so.
That precedence is what lets one company run more than one kind of job without one checklist trying to cover both. An insurance restoration program and a retail replacement program can each carry their own install-stage items, and the crew sees only the ones that apply.
Turning the truck-door list into a gate
- Write down what you already require, stage by stage Not what a perfect company would require. What you refuse to let happen today. If a crew lead would be spoken to for skipping it, it is a candidate. If nobody would notice, it is not a required item yet.
- Import what exists rather than retyping it An existing PDF or Word checklist can be uploaded and parsed into candidate items. The parse hands you a list to review; it does not create templates on its own, and you decide what is kept, what stage it belongs to, and what is required.
- Give the items that matter a type The completion photo becomes a photo item with a minimum count. The customer sign-off becomes a signature item. The measurement that has to be recorded becomes a text item linked to the field on the job so it lands in the record.
- Mark required sparingly Every required item is a reason a job can stall. That is the point, and it is also the cost. Start with the items whose absence has actually cost you a callback, a dispute or a re-inspection.
- Let a job get refused, then read the message The first time a job will not advance, the refusal names the items. That message is the checklist doing its job. If the items it names are the wrong ones, fix the template, not the crew.
- Split by program when one list stops fitting When the install-stage items for one kind of job start reading as noise on another, give the program its own templates. The job picks them up on its own from the program it belongs to.
What this does not do, said plainly
A gate enforces what is in the template. It does not know what should be in the template. A stage with no required items has no gate, and the job passes through it exactly as it did before, so the empty stage is the thing to look for first.
The gate checks the stage the job is leaving, not every stage behind it. Items that were never required cannot hold a job later. And a required text item is satisfied by any note, so the discipline of what gets written is still the crew's.
The file import uses a language model to turn a document into candidate items, and that means it will sometimes read a heading as an item or merge two lines into one. It returns the result for a person to review before anything is saved, which is the right shape for that kind of tool, and it means the review is part of the work rather than a step to skip.
The question to ask about your own checklist
Not whether it is complete. Whether it has ever stopped anything. If the answer is no, then either every job you have ever run was perfect, or the checklist is a list. The fix is not a longer list. It is a shorter one that the software will not let a job walk past.
BetterRoofingPro's stage checklists are that gate: per stage, per program when you need it, with photo, signature and multiple choice items that cannot be satisfied from a desk, and a history entry for every completion. If you would like to see how a job is refused and what the crew sees when it is, book a demo and bring the checklist off your truck door.
Ready to Stop the Morning Scramble?
BetterRoofingPro gives production managers a shared calendar, job-linked work orders, and material tracking so every crew starts the day prepared.