RoofGenius

RoofGenius Damage Detection

Drone photos in.
Inspection report out.

Drop your roof photos. RoofGenius flags the damage on every image, marks each hail hit, writes the slope-by-slope determination, and hands you a finished inspection report PDF.

Book a demo
Try it on a real job

Try it

Run a real inspection.
Right here.

This is the Photos tab inside a RoofGenius job, loaded with three drone photos from a real inspection. Upload them, run the AI, open any photo to see the marked hits, then build the actual damage report PDF the job produces.

app.roofgenius.ai

Sample Client

Address redacted · Photo Inspection

Photo Inspection

Job Photos

0 photos total

Photo Inspection starts here

Upload damage photos first. Your AI Autonomous Copilot will analyze them and then you can build the damage report.

Guided step 1 of 5Start with the roof photosClick Upload Photos. Three real inspection photos will be added to this job. Click the highlighted control1

Step 1 of 5This is the Photos tab inside a job. Upload the roof photos from the inspection.

Homeowner name and address redacted. Findings, hail-hit counts and marks come from the original report.

The damage you can't prove is money you don't collect.

"No visible damage" ends the claim

A folder of untitled photos is not evidence. Classified findings with severity and confidence on each image make the damage hard to wave off in the first review.

Manual photo review burns the estimator's day

Nobody should be squinting at 80 phone shots and typing captions. Each photo is read and written up automatically in about the time it takes to make coffee.

Undocumented hits become unbillable scope

Findings carry their component and unit of measure, so detected damage flows into scope lines instead of being retyped — or forgotten.

The deliverable

One report the adjuster can't wave off.

A cover letter with the summary of findings, the inspector verdict, then every photo with its marked hits, written finding and recommendation. Real report, homeowner redacted.

Cover letter
Addressed to the homeowner on your letterhead, with the inspection date and your recommendation in plain language.
Summary of findings
Every finding listed by slope with its hail-hit count and the written description.
Inspector verdict
The overall determination up front — full replacement, slope replacement, repair, or more documentation needed.
Findings at a glance
Total findings, safety hazards, recommendations and replacement call, in one row.
Photo findings
Each photo with its hail hits circled, the written finding, and the recommendation beside it.
All sample documents

What gets checked on every photo.

Each damage class maps to a roof component and the unit that carries into a scope line — so the finding is estimator-ready when you open it.

Damage classComponentUnit
Hail impact / bruisingField shingle
Granule lossField shingle
Cracked shingleField shingle
Missing shingleField shingle
Lifted shingleField shingle
Creased shingleField shingle
General impactRoof surface
DentsSoft metals
Vent damageRoof vent
Gutter damageGutter / downspout
Damaged flashingFlashing
Exposed underlaymentUnderlayment
Water damage / stainingDecking / interior
Broken tileTile field
Cracked tileTile field
Wind damageRoof surface / rake
Ridge / hip damageRidge cap

Hail, wind, mechanical, or wear.

Most denials are cause-of-loss arguments, not damage arguments. Findings are classified on what is visible in the frame, then checked against storm events for that address and date.

Random-pattern impacts, granule loss, soft bruised mat

Confirmed by: Round dents on gutters, vents, drip edge in the same direction

Creased tabs, lifted shingles, missing shingles

Confirmed by: Concentrated on exposed elevations and along the rake

Scuffs, broken tabs, crushed granules in a line

Confirmed by: Clusters on traffic paths and around HVAC or satellite mounts

Blistering, curling, uniform granule thinning

Confirmed by: Even across every slope and unrelated to any storm date

Made to hold up at re-inspection.

Per-photo classification

Each image is analyzed on its own and merged into one job-level summary — not a single guess made from a thumbnail grid.

Conservative by design

The model is instructed that false positives are worse than misses, and anything under 50 confidence never reaches the report.

Findings that carry units

Every damage class maps to a component and unit of measure, so evidence turns into scope lines instead of retyping.

Code-backed reasoning

State and local building-code research attaches to the findings that need it, so the repair requirement is argued, not asserted.

Storm history on the file

Verified hail and wind events for the property location and date of loss sit alongside the photo evidence.

Automatic photo write-ups

Professional descriptions and inspection notes are generated per image, so the report reads like a field inspection.

Under-5-minute turnaround

Photos are analyzed in parallel. No queues, no offshore reviewers, no next-day delivery window.

One connected job file

Damage findings, measurements, estimate, and supplement live on the same file and ship as one document.

Questions, answered.

How do you inspect a roof for hail damage?+

Walk the slopes you can safely reach and photograph each elevation, the ridge, valleys, penetrations and every soft metal — gutters, downspouts, vents, drip edge, flashing. Hail leaves random-pattern impacts with granule loss and a soft, bruised mat; soft metals show round dents that confirm stone size and direction. Upload the photos and each image is classified individually: damage class, severity, confidence score, and a written note. You are documenting evidence, not just looking at a roof.

What should be included in a roof inspection report?+

Property and date of loss, a photo-by-photo record with a written description of each image, the damage class and severity for every finding, a confidence score so the reviewer can see what is certain and what is borderline, the affected roof component with its unit of measure, verified storm history for that address, and the building-code requirements that drive the repair. Anything less and the adjuster is guessing.

What does a roof inspection report look like?+

A cover with the address and inspection date, a job-level damage summary, then one section per photo — the image, the detected damage, severity, confidence, and the inspection note written for it. Storm history and code citations attach at the back, and the measurement report and scope live on the same file, so the adjuster gets one document instead of three unrelated PDFs.

How do you tell hail damage from wind, mechanical, or manufacturing defect?+

Hail is random-pattern with granule loss and dented soft metals in the same directional pattern. Wind shows creasing, lifted tabs, and missing shingles concentrated on the exposed elevations and along the rake. Mechanical damage clusters on traffic paths and around HVAC. Blistering and defect are uniform across the slope and do not match a storm date. The model classifies each hit on what it can actually see in the frame, and the verified storm history on the file either supports the loss date or it does not.

What kinds of photos work — phone, drone, or aerial imagery?+

All of them. iPhone or Android photos taken on the roof, DJI drone captures, aerial imagery, or a synced CompanyCam album. Photos are normalized before analysis, so mixed resolutions, oblique angles, and imperfect light are fine. There is no special capture protocol to learn.

How accurate is it, and does it invent damage?+

The model is deliberately conservative: it is instructed that false positives are worse than missed items, and it must return a confidence score for every finding. Anything under 50 confidence is discarded before you ever see it. Job-level severity is derived from the highest-confidence finding, so borderline calls are visible rather than buried — your estimator confirms or removes them in review. We do not publish an accuracy percentage, because a single number across every roof type and lighting condition would be marketing, not measurement.

Does each photo get written up, or just tagged?+

Both. Beyond the damage tags, the system generates a professional photo description and inspection note for each image, so the report reads like a field write-up instead of a folder of untitled JPEGs.

Is the storm history verified, or just a date the homeowner gave you?+

Verified. Hail and wind events are pulled from NOAA storm-event data for the property coordinates and matched against the date of loss, with distance and reported stone size. If no qualifying event exists near that address, the report says so — that is worth knowing before you file, not after.

Do adjusters accept these reports?+

The report format is what a reviewer expects from a competent field inspection: photo-by-photo evidence, damage classification, severity, confidence, and a written description per image, with code and storm support attached. It removes the ambiguity that drives "no visible damage" denials and re-inspection requests.

How does it connect to supplements and measurements?+

Damage findings auto-attach to the same job file as your measurement report, estimate, and supplement. Detected components carry their unit of measure, so the scope lines are built from the evidence instead of retyped from it — one connected file to the adjuster instead of three unrelated PDFs.

How fast is the turnaround?+

Analysis runs per photo in parallel, so a typical 40–80 photo job finishes in under 5 minutes. No queue, no offshore review team, no waiting on a human reviewer.

How do I get started?+

Subscribe to the $297/month Retail plan to use damage detection, measurements, proposals, and job tracking across every job.

Get started

Your next storm job,
documented.

Damage detection comes with the Retail plan, alongside measurements, proposals and job tracking.

Book a demo