LibreHow to Write a Roofing Photo SOP Your Crews Will Actually Follow
A photo standard is not a policy document. It's a shot list a crew member can read on a roof in ten seconds.
Most photo SOPs fail the same way
They get written in the language of a contract. "All work shall be photographed prior to concealment, and documentation shall be retained in accordance with company policy." Nobody standing on a 6/12 at two in the afternoon parses that sentence, and nobody was ever going to. A crew member has four questions and only four: what do I shoot, when do I shoot it, how close do I get, and who is going to look at it. A standard that answers those four in plain words gets followed. Everything else in the document is there for the person who wrote it. The other failure is scope. A shot list long enough to be thorough is long enough to be triaged, and when the crew triages, they decide which photos you lose, on the job where it matters most.
What a roofing photo standard should contain
A shot list organized by phase, not by job
Every roof is different; the phases are not. Arrival and existing conditions, tear-off and deck, dry-in, flashing and details, field and finish, cleanup and site. Write the required shots under each phase. A crew working a slate reroof and a crew working a low-slope recover read the same six headings, and each phase tells them what has to be in the camera before that phase ends.
The wide-then-close rule, stated as a rule
Every detail shot is a pair. The wide shot proves where on the building it is; the close shot proves what it is. Write it once as a general rule at the top instead of doubling the length of the list by naming both shots for every item. Crews remember rules better than they remember lists.
The address in the first frame of every job
First photo, every job, before anything else: the house number, the suite placard, the street sign at the corner. It makes the set self-identifying when somebody opens it two years later without context, and it marks a clean start to the job in the day's photos.
Every layer photographed before it is covered
This is the one rule that earns its place above all the others. Deck before underlayment. Underlayment and ice-and-water before the field. Step flashing before the counter. Curb and penetration flashing before the membrane goes over it. Fastening pattern before it disappears. Once the layer is covered, the photograph is the only remaining evidence of what you installed, and no amount of later documentation brings it back.
Who shoots, written as a role
Name roles, not people, or the standard dies when the person quits. Every crew member shoots what they are working on. The crew lead confirms the set is complete before the truck leaves the site. Say it in one sentence. If your standard implies one designated photographer, expect coverage to follow whoever that is around the roof and nowhere else.
When the office reviews, and who
A standard with no reviewer is a suggestion. Write the review into the document: the production manager looks at each active job the same day, and anything missing goes back to the crew while they are still on site. That one line is what converts a shot list into a habit, because the crew learns within hours that somebody actually opens the photos.
Four ways a photo SOP dies
It asks for too many shots
A sixty-item list looks rigorous on paper and gets cut to fifteen on the roof, by a crew choosing under time pressure. Cut it yourself instead. Keep the shots you would put in front of an owner, an architect, or an attorney, and drop the rest.
Nobody owns the review
If reviewing photos is everyone's job, it's nobody's, and crews figure that out inside a month. Put one role on it by name and give that person a fixed time of day to do it.
It lives in a document
A standard on a shared drive is a standard nobody opens on a roof. It has to be in the same device the photos are taken with, as a checklist whose items require a photo, or it is decoration. This is the difference between a policy and a procedure.
It never changes
Every callback, warranty question, and payment dispute is telling you which photograph you wish you had. Add that shot to the standard the same week. A standard that hasn't been edited in two years isn't stable, it's abandoned.
Put the SOP where the work happens
Start from the roofing photo requirements template, cut it down to the shots your company would actually defend, then load it as a checklist so the standard rides along in the camera on every job. Training the crews on it takes one real roof once the checklist exists. If you run more than one branch, write the standard once for the whole company rather than letting each location grow its own. One honest note: LibreCam does not enforce your SOP, certify an install, or decide that a job met the standard. It records what the crew shot and shows what is still missing. The standard is yours, and so is the call on whether the work is right.
Frequently Asked Questions
One page, or twelve to twenty required shots. If it doesn't fit on a page, it won't fit in a crew member's head, and the parts that don't fit are the parts that quietly stop happening.
Same structure, two shot lists. Low-slope work runs to seams, flashings and terminations, drains and scuppers, curbs, and penetrations. Steep-slope and specialty work runs to starter and eaves, underlayment and ice-and-water, valleys, step and counter flashing, and ridge and ventilation.
Write the shot list into the agreement so it's part of the scope, not a favor. Then give them a way to put photos into your job record rather than texting them to a project manager, and check the set before you release payment.
No. Checklist items can require a photo before they're marked complete, and the checklist shows what is still unshot while the crew is on site. Whether the work met your installation standard is a judgment a person makes from the record.