ScopeQueue Carrier estimate in, justified supplement package out.

The roof photos you can never take again

Most contractors do not lose supplements for taking too few photographs. They lose them for taking a hundred of the wrong subject.

Hail hits get photographed. Everyone photographs hail hits. The frames that decide the file are usually of things that were never damaged at all — the eave edge, the felt under the first course, the number of layers, the vents that were already up there. Those frames share one property that no amount of care later can restore: they can only be taken while the old roof is still on the building.

A shovel is a one-way door. At seven in the morning the roof is evidence. By noon it is in a dumpster, and everything you did not photograph has quietly turned into an assertion.

The frames that cannot be retaken

Take these before the first shingle comes off — not before the job, before the first shingle. Each one exists to defend a specific line item, and each one answers a specific rejection.

The attic frame is the one that gets skipped and the one that carries the most weight. The decking rejection to plan for is the one about time: the wood was already bad. The only thing that argues with a claim about time is a photograph taken earlier. From below, before the crew arrives, it takes a few minutes.

Where the code argument lands

Some of these frames are not about condition at all. They are the surface a code argument has to land on.

Drip edge at eaves and rakes sits at R905.2.8.5. Valley lining sits at R905.2.8.2. The ice barrier requirement sits at R905.1.2, and whether it reaches that particular address is decided by the climatic and geographic criteria at R301.2 as adopted locally. Metal panel roofs carry their own flashing requirement at R905.4.6. Adoption happens state by state and often by local amendment, so the accurate sentence is that your state adopted a particular edition of the IRC, not that the IRC as such says something — and the edition, along with the section number in that edition, is worth confirming with the authority having jurisdiction before you put it in writing.

None of that is proved by a photograph. What the photograph proves is the condition the requirement gets applied to: that there was no drip edge, that the valley was open metal, that the membrane stopped short of where the eave actually is. Without that frame the code paragraph has nothing to land on and reads as theory. There is a longer treatment of one of these fights in the drip edge write-up.

One frame, one line item

Here is the test. Point at any photograph in the file and ask: which line does this defend? If the answer takes more than a second, that photograph is decoration.

A stack of images at the back of a packet is not an argument. It is homework handed to a reader who did not walk the roof, and a reader rebuilding your scope out of a pile is rebuilding it from their reading of it rather than yours. Put the frame beside the item it supports, with a caption naming the slope and the measurement and nothing else.

Run it backwards too. Go down the items you are claiming and mark the ones with no frame. Those are the items you are asking someone to take on your word. The ones that turn on a condition nobody can see any more are the hardest to defend that way, because there is no longer anything to go back and look at.

Framing: a measurement, not an impression

Significant pitting on the north slope is an opinion, and an opinion invites a second opinion. North slope, a test square chalked out and measured, each mark circled and counted, the count written on the surface, shot from directly above and then close — that is a measurement. Someone else can check it. That is the entire difference, and it is most of the job.

How many is enough, and when it turns into too many

There is no correct total. The number that matters is coverage per item, and per item it is small: usually one wide and one close, plus, wherever a quantity is claimed, the frame that lets somebody count.

Too many looks like this. A run of near-identical shots of the same mark. The same slope from several angles that all show the same thing. Photographs of items you are not claiming at all. Every extra frame is one more place for a reader to find something that looks like it contradicts a quantity, and it buries the frames that were doing work. Volume is not thoroughness. Coverage is.

The tear-off morning sequence

  1. Before the first shovel. Everything in the list above, attic included.
  2. At the first cut. Layer count, tape laid across the stack, shot from the cut edge so the layers separate visually. That one frame records something nothing else will be able to show an hour later.
  3. Deck exposed. A wide of the plane, then each bad sheet with the tape in frame, then one overall shot with the bad sheets marked so the count reads in a single image.
  4. At the moment of discovery. Anything that was not in the estimate gets photographed before it is touched, and reported the same day. The frame establishes the condition; when you sent notice establishes the timing. Those are two different questions, and an invoice answers neither.
  5. Before dry-in. The last frame of the open deck. Once the membrane is down, everything underneath it is a statement about the past.

This is not the crew's trade and it slows their morning, so it does not happen unless someone owns it. Whoever owns the file owns the camera. Otherwise the first pass goes missing on exactly the jobs where it mattered.

What a photograph cannot do

A photograph establishes a physical fact: this material was there, in this condition, at this measurement, at this time. That is all it does, and it is a great deal.

It does not settle what is owed. A caption that argues coverage is doing the narrative's job, and it puts an opinion where the file needs an observation. Keep the caption to what is visible. Keep the reasoning in the narrative, item by item, where each rejection can be answered on its own terms — there is a line-by-line list of those rejections here.

The habit underneath all of it is simple, and it explains why the frames come before the argument. You are not photographing damage. You are photographing a building that is about to stop existing in its current form, so that later, when somebody asks what was under there, the answer is not a memory.

Written for contractors preparing their own documentation. This is not legal advice, it is not a reading of anyone's policy, and it does not tell you what any carrier owes on a given file. Code adoption, section numbering and local amendments vary by jurisdiction and by edition — verify the adopted edition and the section against the authority having jurisdiction for the property.

This is what ScopeQueue does with a file

You can work through all of this by hand, and plenty of good contractors do. ScopeQueue reads the carrier estimate and your photographs and drafts the same file for you to check — with the reason written under each item, and the code section left blank wherever it cannot be verified.

Try it on one file — free

More