How to Package Photo Evidence for a Roof Supplement

Photo evidence is not just a stack of images. In a roof supplement, it is part of the reasoning chain between the requested line item and the field condition.

When a reviewer has to scan a bulk photo dump and guess which image supports which request, the packet slows down and credibility drops.

Start with the line item, not the camera roll

Each important request should have a photo anchor attached to it. The image should help answer what is visible, where it is located, and why it matters to the scope being requested.

Use callouts, not volume

A few labeled images are usually stronger than dozens of unmarked photos. Annotation reduces interpretation and shows the reviewer exactly what changed.

Tie photos back to quantity logic

Photo proof works best when it is paired with measurement support, perimeter math, or accessory counts. The image proves the condition; the quantity trail proves the ask.

Keep the packet narrow

• Group photos by requested issue, not by upload order
• Match each callout to the line item or support note it informs
• Avoid repeating the same visual proof in multiple places unless it changes the conclusion
• Do not use photos to imply broader scope than the packet is actually requesting

Use a measured explanation

The note beside the image should stay concise: what the reviewer is seeing, how it connects to the request, and where the quantity source lives. The goal is clarity, not persuasion theater.

If your current packet format makes reviewers hunt, reorganizing the photo evidence is often one of the fastest ways to reduce back-and-forth. PactPack’s public sample pack shows one way to combine photo callouts, line-item support, and scope boundaries in a calmer review format.