A 14,000 SF warehouse roof inspection with 412 photos. The carrier wanted a defensible report in 48 hours.
This guide is for field operators who produce inspections, property documentation, construction QA, or claims deliverables. You get concrete habits, repeatable examples, and a checklist you can run in the truck before you submit a package.
Read this when you need a report that gets decisions, not compliments. Before you pick up the camera, confirm the decision you must support.
Start with the client's question — not the camera
Identify the decision
Before you take a single photo, name the decision the client will make from your deliverable. Is it approve a repair, accept a turnover, or file a claim? The decision drives scope, access, and the shot list.
Frame shots to answer the question
- Structural or warranty decisions: Capture context, then images of defects that affect performance.
- Claims or damage decisions: Show origin, progression, and current condition. If you can't show cause, don't guess — show what you saw.
- Turnover or QA: Capture compliance items and the defects that will block acceptance.
On-site example: a property manager called about a stairwell slip. We shot the stair configuration, landing, lighting, and the foreign material. We included access shots to show sight lines and obvious hazards. If you can't state the decision in one sentence, refine the scope before shooting.
Make your visuals defensible
Metadata and verification
Photos without time, date, and location fail in claims and disputes. Use a camera or app that writes metadata or export a stamped PDF. If a timestamp is questioned, your file metadata is the primary defense.
Non-invasive, clear observation
Report what you observed without invasive work unless contracted. Log what you did not confirm and recommend intrusive testing where needed. Use clear language: "observed denting consistent with hail" rather than speculation on timing.
Field story: on a hail claim we documented the roof with overall shots, close-ups of strikes, and photos of nearby exposed equipment. We logged three roof zones we couldn't access. The metadata-backed package got the carrier to fund a $48,200 scope for permanent repair instead of denying the claim. Always attach a metadata export or explain why you couldn't capture one.
Context wins over pretty photos
Organization and annotation
One clear photo with a caption beats ten untagged images. Tie each visual to a location and a concise caption that states condition and implication.
- Map or floorplan reference: Drop a thumbnail map or plan with the photo pin. It removes guesswork.
- Shot hierarchy: Start wide, then mid, then close. The sequence orients reviewers immediately.
- Captions with action: End captions with the recommended action: "repair, monitor, test further."
Mini case — multifamily turn: on a four-unit turnover we grouped 312 photos by system: kitchen, bath, HVAC, flooring. Each group started with a plan pin, then wide and focused shots. Captions noted habitability impact. The owner approved the punch list in two days and avoided a $9,600 holdover by prioritizing the critical items first. Group images by system and include a plan pin on the first image of each group.
Deliver for the decision — not just the record
Actionable captions and recommended next steps
Every issue must have one of three prescribed next steps: "Immediate fix," "Schedule repair," or "Monitor and re-inspect." Keep captions prescriptive and short. That makes it easy to convert the report into an RFI, change order, or work order.
Prioritize risk and cost drivers
Not every blemish matters. Highlight items that affect safety, operations, or compliance first. Include a simple risk-cost note for each high-priority item so the decision-maker can act without another call.
Field story: during a warehouse roof review we located a membrane breach near a high-traffic loading bay. We photographed the breach, the bay layout, and downstream ceiling staining inside the warehouse. Our three-line recommendation said: close the bay, install temporary cover, and schedule a permanent repair. That sequence triggered an immediate emergency repair and avoided an estimated $62,000 loss from inventory damage. For each defect, give one prescriptive next step and a cost or risk note.
Practical tools and workflows that actually work in the field
Minimal tech stack
You don't need every app. Pick one camera solution that embeds metadata, one annotation tool, and one delivery format. Complexity slows you down under deadline or bad weather.
- Camera choice: Use a rugged camera or phone with a reliable timestamp. Test it before big jobs.
- Annotation: Draw arrows, circle issues, and add short notes — don't write a paragraph on the image.
- Delivery: Export a structured folder: map or plan, photographic groups, then a summary page with recommendations.
Workflow on site
- Talk to the client or rep and confirm the decision you need to support.
- Run the shot hierarchy for each area: wide, mid, close.
- Log access limitations and safety issues immediately in notes.
- Annotate photos on site if possible — it saves back-and-forth later.
- Deliver a short executive summary in the same package as the images.
Don't let auto-tagging pick your key images without a field operator review. If you use AI, validate its picks before sending. Pick one camera, one annotation tool, and one delivery format before mobilizing.
Before You Leave the Site, Check This:
- Confirm the decision you documented matches the client's stated need.
- Export a metadata-stamped copy or stamped PDF for every critical image.
- Pin a plan/map thumbnail for each image group and verify pins match photos.
- Annotate critical defects and assign one clear next action per item.
- Log access limitations, safety holds, and who you spoke with (name, company, time).
- Run a quick folder check: map, groups, summary, raw files. If anything is missing, stay on site until it's complete.
Run this checklist before you leave; missing items will likely force a return visit.
Key takeaways
- Name the decision first; shoot to answer it.
- Attach metadata and export a timestamped set for claims or disputes.
- Group photos by system and supply a plan pin with each group.
- State one prescriptive next step for every defect and add a risk or cost note.
- Keep the tech stack to one camera, one annotation tool, and one delivery format.
If you can't check each box in under 10 minutes, rework your workflow.
FAQ
How many photos should I include in a deliverable?
Include the shots that tell the decision-maker's story: wide, mid, close for each issue, plus verification shots like access points. If you can't explain why each image exists in one sentence, cut it.
Do clients want marked-up photos or raw files?
Provide both when it matters. Send marked-up images for immediate understanding and keep raw files available for legal or insurance review. Always label which version is which.
Can I use drone footage as the main deliverable?
Yes, for roofs and exteriors. Pair drone footage with ground-level shots to show access, safety, and interior effects when relevant.
What do I do when I can't access the area I need to document?
Document the limitation, capture what you can from a safe vantage, note why access was restricted, and recommend the method to gain access. Clients prefer transparency over assumptions; state the missing verification and next steps.
Use these FAQ answers as on-site rules-of-thumb and document any exceptions during the job.