LibreHow to Run Roofing Quality Control Across Every Branch
At one location, quality control is a person in a truck. At three, that person is the bottleneck and the standard is already drifting.
What breaks at the second location
In a single-location roofing company, quality control is undocumented and it works. The owner or production manager drives past four jobs a day, knows which crew leaves nails in the grass and which one rushes valleys, and corrects it in the driveway. None of that is written down, and it doesn't have to be, because the standard and the inspector are the same person. Open a second branch and three things break at once. Standards drift: whoever the strongest crew lead is at that branch becomes its de facto standard, and within a year the two locations build roofs two ways. The one QC person becomes a bottleneck: every final roof inspection now waits on one person's windshield time, so jobs close out uninspected or close out late. And the owner loses the view: what you know about branch two is what branch two chooses to tell you, filtered through the person whose numbers depend on the answer. Acquisitions make all three worse, because the company you bought arrives with its own habits and its own idea of what a finished roof looks like.
Five moves that make QC survive growth
Write one photo standard for the whole company
Not one per branch, and not one per crew lead. Branches can differ in how they stage a job, order material, or run a schedule. They cannot differ in what the record of a finished roof looks like, because the record is the only thing you can compare across locations. Write the required shots by phase once, at the company level, and hand the same list to every branch on the same day.
Move the first QC pass onto the roof
The cheapest inspection is the one done by the person who did the work, while the work is still exposed. Load the standard as a checklist whose items require a photo before they can be marked complete, and the crew walks the post-installation inspection themselves before the ladder comes down. That doesn't replace your inspector. It means your inspector stops spending their day discovering that nobody photographed the valleys.
Review the job record the same day, not Friday's camera rolls
End-of-week review is archaeology. The crews are three jobs past it, the roofs are closed, and the only fix available is a truck roll. Reviewing the day's active jobs the same afternoon means the correction goes back to a crew that is still on site. Give the review a fixed time and a named role, or it gets bumped by whatever is on fire.
Run job audits from the record instead of the truck
Pull a sample per branch per month, at random, and look at the same phases every time across every location. That's a real quality audit, and it works the same whether the branch is twenty minutes away or two states over. Windshield time then goes where the audit says to look, rather than being spread evenly across jobs that were fine.
Put new branches and acquisitions on the standard before the first job
An acquired company shows up with its own process, its own photo habits, and a crew that has never been asked for a dry-in shot. Load them onto the same checklist before their first job under your name, not after their first callback. Day one is the only time changing a documentation habit is easy.
What makes this run across locations
The same checklist in every branch
One set of photo checklists per job type, used by every location. When branch three's numbers look different from branch one's, you can compare the same phases on the same kinds of jobs instead of comparing two people's opinions.
Every job visible the same day
Photos sync to the job record as they're taken when the crew has signal, and queue when they don't. The job timeline puts each job day by day, so an ops lead in one city can see what happened on a roof in another without calling a branch manager to ask.
Audit without asking a branch for anything
Search by address, date, tag, or caption across every location. A job audit stops being a request that gives a branch manager a week to prepare, and starts being something you do on a Tuesday morning.
Coverage that doesn't get rationed by branch
Software priced per user forces somebody at every location to decide which crew members get a camera, and the branches furthest from the office cut the deepest. Every employee gets one here, with role-based access so a branch sees its own work and the office sees all of it.
A second set of eyes on the photos
On-device damage detection highlights cracks, water stains, and missing materials in a photo set, which helps a reviewer working through a lot of jobs catch what they'd skim past. It's an aid to the reviewer, not the reviewer.
Where to start
Start with the document, not the software. The roofing photo requirements template is the company-level SOP, and the roofing QC checklist is the post-installation inspection your production manager runs against it. Once both are written, load them as checklists so every branch works from the same steps, and set up the same-day review described in seeing photos from every crew. The multi-location roofing page covers how the whole thing fits together across branches. What LibreCam will not do is audit for you: it does not grade a photo set against your checklist, score a branch, or flag failed work. It records what each crew did and shows what is still unshot. Comparing that to your installation standards is your production manager's job.
Frequently Asked Questions
Separate checklists by job type, not by location. A low-slope recover and a steep-slope tear-off need different shot lists; branch two and branch five do not. The moment checklists vary by branch, you've lost the ability to compare them.
Pull a random sample of that branch's recent jobs and read the photo record for the same phases you'd check in person. You'll catch documentation gaps and visible install problems from the record; anything the record raises is what you buy a plane ticket for.
Take the best shots from their list into yours, then run one standard company-wide. Keeping two standards to avoid a hard conversation costs more in year two than the conversation costs in week one.
No. There's no auto-QA, no grading, and no pass or fail. The checklist shows what is still unshot, damage detection highlights conditions a reviewer might miss, and a person decides what it means.
Nothing changes on a bill, because there isn't a per-user charge. That matters for quality control specifically: the reason to give a new branch's laborers cameras shouldn't have to survive a budget conversation.