5 Steps To Build A Storm Damage Portfolio As A Roofing Contractor

A storm damage portfolio is a curated, privacy-safe collection of documented roofing jobs that proves how your company works after severe weather: how you assess safely, what you observe, how you scope and complete the repair, and how clean your records are when the job closes. Built right, it is the single strongest piece of trust-building you own, because it shows real work instead of asking a homeowner to take your word.

Here is the short version, so you can act today. Build it in five steps. First, decide what the portfolio must prove before you shoot a single photo. Second, capture damage safely and the same way every time, so your files are consistent. Third, turn every job into a standard record at the file level, not at the marketing level. Fourth, promote only the cleanest records into public case examples, with a neutral format and signed permission. Fifth, run every example through a truth, privacy, and usefulness review before anyone outside the company sees it.

The biggest mistake roofers make is treating a portfolio as a highlight reel of the most dramatic hail and wind shots they can find. That gets you a wall of caved-in roofs and zero proof of process. Worse, it tempts captions like "insurance bought this whole roof," which invite arguments, expose private claim details, and can cross advertising lines you do not want to cross. A strong portfolio is boring in the best way: it is documented, repeatable, honest, and easy to audit back to a real job file.

There is a second payoff most contractors miss. The same discipline that makes a portfolio credible also makes your outbound sharper. When every storm job is recorded with location context, storm date, roof age, observed conditions, and outcome, you stop guessing which neighborhoods to work next season. Your portfolio and your job list become two views of the same clean data. The rest of this page shows how to build that system, what to document, what to leave out, and how to keep it legal and useful.

What A Storm Damage Portfolio Actually Is (And Is Not)

A storm damage portfolio is proof of process, not proof of drama. Its job is to answer the question every storm-season homeowner is silently asking: Are these people legit, or are they another out-of-town crew that knocked after the hail and will be gone by winter? You answer that with documented, finished work, not with adjectives.

Think of it as three things stacked on top of each other:

• A training library your crews and sales reps learn from.
• A quality record that shows whether your field documentation is actually consistent.
• A marketing asset that lets a homeowner see comparable work before they sign anything.

The order matters. If the marketing layer is built on top of a real training and quality system, it is honest by construction. If you build the marketing layer first and reverse-engineer the records, you end up with captions your files cannot support, which is exactly where contractors get into trouble.

Here is what a storm damage portfolio is not, stated plainly so nobody on your team gets confused:

It is	It is not
Proof you respond safely and document well	Proof every roof was "totaled"
A record of work you actually performed	A gallery of the worst-looking roofs you can find online
Privacy-safe and customer-approved	A dump of claim numbers, checks, and adjuster names
Neutral about insurance outcomes	A claim that you can guarantee a payout
Easy to audit back to a job file	A set of captions your records cannot back up

You are a roofer, not a public adjuster and not the insurance company. Your portfolio should make that boundary obvious. The most persuasive thing you can show a skeptical homeowner is not a roof that got "approved." It is a roof that got handled: documented before the tarp went on, scoped in writing, replaced cleanly, photographed at closeout, and backed by a warranty handoff. That reads as competence. "We beat the insurance company" reads as a sales pitch.

Why the boring version wins

After a major hail or wind event, a neighborhood gets flooded with knockers. Some are real, some are storm-chasers who will subcontract the work and disappear. Homeowners know this, and the trade press and consumer agencies remind them constantly. The National Roofing Contractors Association and consumer guidance from groups like the National Association of Insurance Commissioners tell homeowners to slow down, verify the contractor, and be wary of high-pressure storm pitches. Your portfolio is your answer to that warning. A clean, documented, modest set of records does more to separate you from the chasers than any "storm specialist" badge.

Step 1: Define What The Portfolio Must Prove

Write the purpose down before you collect anything. A page of intent saves you from a hard drive full of useless photos.

A strong storm portfolio proves five claims, and only these five:

1. You respond safely. Your access decisions follow real fall-protection and hazard rules, and your files show it.
2. You document what you observe. Same photo set every time, ground-up, with context shots and close-ups.
3. You separate facts from coverage opinions. You report conditions; you do not promise what an insurer will pay.
4. You complete appropriate work. Scope, authorization, production, closeout.
5. You keep records. Anyone in the company can pull the file behind any public example.

Notice what is not on that list: that every roof was destroyed, that every carrier paid, that every job was wildly profitable. Those claims create risk and, counterintuitively, persuade less than clean records do.

Group by job type, not by storm

Decide your folders up front so capture has a home. A workable set:

• Emergency / temporary protection (tarping, shrink-wrap, board-up)
• Wind damage (lifted tabs, missing shingles, creased shingles, ridge cap loss)
• Hail evaluation (test squares, marked impacts, soft-metal dents)
• Tree and debris impact (penetrations, structural)
• Flashing, gutter, and penetration work
• Ventilation and decking discovery
• Full replacement after a storm event
• Commercial / low-slope membrane storm response
• Multifamily / HOA storm response

Keep one or two strong records per folder, not fifty loose photos. Five excellent, fully documented jobs beat a chaotic archive every time.

Write your "never publish" list now

Decide what is permanently off-limits in public materials, then enforce it. At minimum, keep these out of any public portfolio item:

• Claim numbers, policy pages, declarations, and checks
• Adjuster names and carrier-vs-carrier comparisons
• Full street addresses and recognizable house numbers
• License plates, faces of children, and people who did not consent
• Interior personal belongings, mail, and documents
• Customer signatures and contracts
• Any photo that makes unsafe work look normal

Those details live inside the job file, never in marketing. This is not only good manners; it keeps you clear of advertising and privacy problems and protects the customer relationship that earned you the job.

Step 2: Capture Damage Safely And Consistently

Everything downstream depends on this step. Inconsistent capture means you cannot compare jobs, cannot train from them, and cannot trust your own marketing. And the capture has to be safe, because the most expensive thing on any storm job is an injured worker.

Safety decides access before anyone climbs

Under federal OSHA rules for construction, fall protection is generally required for work at heights of six feet or more above a lower level; the residential roofing requirements live in 29 CFR 1926.501 and OSHA's residential fall protection guidance. As of July 1, 2025, California's Cal/OSHA aligned its residential standard with the federal six-foot trigger, lowering it from the old fifteen-foot threshold, which means crews working in California face the stricter requirement on most residential roofs. If you operate in multiple states, do not assume the looser rule still applies anywhere.

Before a crew member gets on a roof after a storm, the access decision should run through a short hazard check. Make it a habit, and document the decision in the file.

STORM ACCESS / SAFETY CHECK (complete before climbing)
[ ] Weather clear, surfaces dry enough to walk
[ ] No downed/contacting power lines near access or roof
[ ] No standing water under access routes
[ ] No leaning trees, hanging limbs, or unstable debris overhead
[ ] No visible structural movement / sag / partial collapse
[ ] Roof pitch and condition allow safe footing
[ ] Fall protection set for 6 ft+ (and any height on steep slopes)
[ ] Daylight adequate; not rushing to beat dark
DECISION:  [ ] Walk roof   [ ] Drone only   [ ] Ground only   [ ] Postpone
If not walking the roof, note WHY and the next safe step: ____________

Ground photos, drone photos where legal, or a postponed visit are all legitimate outcomes. "We documented from the ground because the deck was unstable" is a stronger portfolio note than a hero shot taken on a roof nobody should have been standing on. OSHA's own Blue Roof / roof tarping safety materials exist precisely because temporary protection work after storms is where people get hurt.

Shoot the same set every time

Consistency is the whole game. A repeatable capture set means any two jobs are comparable, which is what makes training and honest marketing possible. Use this as your standard sequence:

Shot	Why it matters
Front, rear, left, right elevations	Establishes the property and orients every later photo
Full roof-plane context (per slope)	Shows where close-ups came from
Close-ups of observed conditions	The actual evidence; granule loss, creasing, dents, cracks
Hail test squares (10 ft x 10 ft) with marked impacts	Standard method adjusters recognize
Soft-metal accessories (vents, valleys, gutters, flashing)	Soft metals often show impacts first and clearest
Penetrations and flashing	Common leak origins after wind/debris
Interior leak signs (only if customer-approved)	Ties roof condition to interior effect
Temporary protection in place	Shows you stabilized before further damage
Work in progress (only when safe to shoot)	Decking, underlayment, install sequence
Completed work and closeout	The "after" that proves the job is done

Date and time stamps matter. Use your phone's native camera so timestamp and, where appropriate, geotag data are embedded; restoration teams and adjusters increasingly expect date-stamped images that tie damage to a specific event. Industry documentation guidance consistently calls for wide context shots before close-ups, date-stamped images, and systematic coverage of every roof component rather than a few dramatic angles.

Document the hail the way the industry does

If you do storm work, learn the test-square method and use it. InterNACHI's hail damage material and Haag's published test-square method describe the standard approach: a 100-square-foot test area (typically 10 ft by 10 ft) placed on each slope in the most-damaged areas, away from spots shielded by overhanging branches, with impacts marked in chalk and photographed. Mark, count, and photograph. Note granule loss, mat fracture, and dents in soft metals. You are recording what you observe, in a format an adjuster and an engineer would recognize, not declaring a verdict on coverage.

A portfolio built from this kind of capture looks like the work of a careful operator. That impression is worth more than any caption.

Step 3: Build A Standard Job Record

Every portfolio candidate should begin life as a job record, never as a marketing asset. If the record is good, the marketing version is easy and honest. If the record is thin, no caption can save it.

The record format

Use one consistent structure for every storm job. Fill it as the job moves, not from memory afterward.

STORM JOB RECORD
Job ID: ______________________
Date(s) on site: ______________
Location (privacy-safe): neighborhood / cross-streets, not full address
Property type: SFH / townhome / multifamily / commercial low-slope
Storm context: type (hail/wind/tree) + event date if known + source
Estimated roof age (range): __________   Source of estimate: __________
Customer concern (their words): ______________________________________
Inspection limits / not inspected (and why): _________________________
Safety notes / access decision: ______________________________________
Observed conditions (neutral language): _____________________________
Temporary protection installed + authorization on file? Y / N
Proposed scope (written): ____________________________________________
Signed authorization / change orders: ________________________________
Production notes (decking, ventilation, surprises): _________________
Completion photos captured? Y / N
Warranty handoff delivered? Y / N
Unresolved issues / callbacks: _______________________________________
Marketing permission: none / internal-only / public-approved

This record is the backbone of both your operation and your portfolio. It is also where the targeting payoff lives: storm type, event date, roof-age range, and outcome are exactly the fields you want when you decide which streets to work next season.

Label like a professional, not a salesman

The difference between a credible file and a sketchy one is often just the language in the labels. Compare:

Weak, salesy label	Neutral, defensible label
"Totally destroyed storm roof"	"North slope: missing shingle tabs and creasing after wind event"
"Emergency save!"	"Temporary tarp installed over active hallway leak, authorized [date]"
"Insurance had to pay"	"Damage documented and scope provided; coverage determined by carrier"
"Hail wrecked this roof"	"Test square, south slope: granule loss and soft-metal dents marked and counted"

The neutral version is what survives a homeowner's skepticism, a manager's review, and an advertising standard. "This roof was handled correctly" is a stronger sale than "this roof was a disaster," anyway.

Keep the private parts private

The job file legitimately contains things the public portfolio never will: the contract, the authorization signature, change orders, internal notes about a tricky customer or a supplier delay, and any insurance correspondence the customer shared. That is fine. Just keep a hard wall between the file and the marketing folder. When you promote an example to public, you copy out the privacy-safe pieces; you never publish the file.

Step 4: Turn Clean Records Into Case Examples

Once a job closes, decide whether it earns a spot in the public portfolio. Most will not, and that is correct. You are selecting a few excellent, fully documented examples, not promoting everything.

What makes a job promotable

A promotable case has all of these:

• Clear before photos and clear after photos of the same roof
• A defined problem stated in neutral language
• A written scope of what you did
• Signed customer permission for the specific public use
• A lesson or process point worth showing

A job is not promotable if it leans on dramatic language, has blurry or context-free photos, makes any unsupported insurance statement, or exposes customer details that should stay private. When in doubt, keep it internal.

The public case-example format

Write every public example to the same neutral template so they read as a consistent body of work, not a grab bag.

CASE EXAMPLE (public)
Title: short, factual ("Wind-lifted ridge cap, two-story SFH")
Property type: ______________
Storm context: hail / wind / tree, season/year (no exact address)
What the customer was concerned about: ______________________
What we observed (neutral): _________________________________
Safety / access note: _______________________________________
Work performed: _____________________________________________
Documentation provided to customer: _________________________
Closeout: photos delivered, warranty handed off

A good public caption sounds like this: "Wind-damaged ridge and missing shingles documented after a severe storm. Temporary protection installed after written authorization. Damaged materials replaced and closeout photos delivered to the homeowner."

A caption that gets you in trouble sounds like this: "Insurance tried to deny this, but we proved them wrong and got the homeowner a brand-new roof for free." Cut that. It exposes private claim details, promises an outcome you do not control, and reads as a pitch.

Stay out of the carrier conversation

Do not organize your portfolio by insurer, compare payouts, rate adjusters, or quote approval rates. None of that is your lane, all of it invites coverage disputes, and most of it risks the customer's privacy. Your value is safe assessment, clean documentation, honest scopes, quality work, and a tidy closeout. Sell that.

Use your records as a targeting asset, not only a brochure

Here is where the back end pays off. Because every storm job is now a structured record with storm date, roof-age range, location context, and outcome, you can mine it. Which neighborhoods produced the most real work after the last event? Which roofs you walked but did not sell are now another year older and worth a follow-up? Which past estimates went cold and should get a second touch this season? A clean portfolio system feeds a clean follow-up list.

This is also where a targeting platform earns its place. RoofPredict tells a contractor which roofs in an area are actually due for work, house by house, by pairing an estimated roof-age range with real storm physics, modeling hail trajectory and wind impact on each individual roof instead of just flagging where a storm passed. Used alongside your portfolio, it sharpens the outbound you already do: skip the brand-new roofs, focus mailers and door-knocks on homes a storm likely wore out, and re-engage the cold estimates sitting in your old records. Be clear about its limits, though: it does not inspect roofs, diagnose damage, certify remaining roof life, or decide insurance coverage. The roof-age figure is a planning range, not an exact date. It helps you pick the right houses; your crew, your eyes, and your job file still do the proving.

Step 5: Review For Truth, Privacy, And Usefulness

Nothing goes public until it clears three tests. Make this a checklist anyone can run, so portfolio selection is a process and not one person's taste.

Test 1: Is it truthful and supported by the file?

Every claim in a public example must trace to something in the record. The Federal Trade Commission's advertising basics require that advertising be truthful and substantiated, and the FTC's updated Endorsement and Testimonial Guides at 16 CFR Part 255 make clear that a company must have substantiation for the claims it makes, including implied ones, and cannot present an atypical result as if it were typical. In practice:

• If the caption says "rapid response," the file shows the response timing.
• If it says "temporary protection installed," the file shows authorization and photos.
• If it says "code-related repair," the file shows who verified the code requirement.
• If it shows a dramatic before/after, the file shows that this outcome is representative of the work, not a cherry-picked extreme presented as normal.

If you cannot back the wording with the file, change the wording, not the file.

Test 2: Is it privacy-safe?

Run the "never publish" list from Step 1 against every image and caption. Strip personal identifiers, claim details, interiors, signatures, plates, and unique address clues unless you have clear, specific permission for that exact use. When in doubt, blur or cut.

Test 3: Is it useful?

A portfolio item should help a homeowner understand your process or help your staff repeat good work. If it only makes the company sound dramatic, it fails this test even if it passes the other two. Drama is not the product. Competence is.

The QA scorecard

Score every candidate before it goes public. One point each:

Criterion	Point
Privacy clearance on file	[ ]
Clear before photo	[ ]
Clear after photo of the same roof	[ ]
Documented safety / access decision	[ ]
Signed work authorization	[ ]
Scope consistent with photos	[ ]
Closeout record present	[ ]
Useful lesson or process point	[ ]

Rule: do not publish without privacy clearance, clear before/after photos, and a caption the file supports. Internal training items can score lower and still be valuable, especially if they show a mistake you want crews to avoid.

Add a risk flag for sensitive categories: any example touching active insurance disputes, litigation, an unresolved complaint, an employee injury, a utility hazard, a code dispute, a financing issue, or a payment dispute goes to a manager before anyone considers publishing it. Those jobs may still teach your team something internally, but they rarely belong in public marketing.

Over time, the scorecard does something useful beyond gatekeeping: it exposes process gaps. If lots of jobs lack closeout photos, fix closeout. If many lack signed permission, fix intake. If many lack safety notes, fix field documentation. The portfolio becomes a mirror for your operation.

Build It Into The Workflow, Not As An Afterthought

A portfolio you assemble at year-end from scattered photos will always be thin. A portfolio that captures itself as a byproduct of the job is rich and honest. Wire the steps into the workflow and assign ownership.

Capture points across a job

Stage	What gets captured	Who owns it
Intake	Storm context, customer concern, internal-use permission, ask about future public use	Office / scheduler
Inspection	Standard photo set, safety/access decision, test squares, neutral condition notes	Field lead / inspector
Scope & sign	Written scope, signed authorization, change orders	Estimator / PM
Production	Work-in-progress photos when safe, decking/ventilation discovery	Crew lead / PM
Closeout	Final photos, warranty handoff, unresolved items	PM
Post-closeout	Portfolio eligibility review, scorecard, permission check	Marketing owner + approver

Ownership prevents drift

Split the roles so no single person is both creator and approver of risky wording:

• The field lead captures technical photos and the safety decision.
• The project manager confirms scope and closeout notes.
• The office manager checks permissions and privacy.
• The marketing owner writes the neutral public caption.
• The owner or a compliance reviewer signs off on any high-risk wording before publication.

Keep an audit trail

Store the final public caption next to the original job-file reference, the permission status, the source photos, and the approval date. If a customer later withdraws permission or a detail becomes sensitive, you need to find and pull the item fast. An organized recordkeeping setup, whether a dedicated tool like RoofPredict for property records and follow-up tasks or a disciplined folder structure, is what makes that auditability real instead of aspirational. Treat any such tool as recordkeeping and operations, never as a claim-decision system.

Internal Version vs. Public Version

Maintain two versions of the portfolio on purpose.

The internal version is richer because it teaches. It can include access limits, missed photos, callbacks, supplier delays, and candid production notes. Control access to it, because it contains customer details and honest operational warts.

The public version is narrower. It shows the problem, your process, the work, and the final condition without exposing private information or making claims you cannot support. Every public example should survive four questions:

1. Is permission on file for this specific use?
2. Does the caption match the job file?
3. Does it avoid coverage advice and payment promises?
4. Does it show safe work and finished quality?

If any answer is no, keep it internal or cut it.

Regional And Seasonal Variation

Storm portfolios are not one-size-fits-all, because storms are not. What you emphasize should track your climate and your customers.

Hail country (Texas, Oklahoma, Colorado, the Plains)

Hail is your headline. Lean on test squares, marked impacts, granule loss, mat fracture, and soft-metal denting. Note shingle type and impact rating where you can observe it; the Insurance Institute for Business & Home Safety publishes impact-resistant shingle ratings and runs realistic manufactured-hail testing, and impact-resistant products behave differently under hail than standard three-tab or architectural shingles. Cross-reference event dates against the NOAA NCEI Storm Events Database so your "after a hail event" language ties to a real, dated, county-level record rather than a vague memory.

Wind and hurricane coast (Gulf, Southeast, Atlantic)

Wind drives your story: lifted and creased shingles, missing tabs, ridge-cap loss, and the fastener and edge-metal details that decide whether a roof stays on. IBHS's FORTIFIED program and its technical documents are worth knowing, because more homeowners in these regions are asking about wind-rated and FORTIFIED installs, and a portfolio that shows you understand edge metal, sealed decks, and proper nailing reads as serious.

Mixed and northern climates

Wind events, the occasional hail swath, ice and snow loading, and tree impacts all show up. Your folders should reflect the actual mix you work, and your captions should not import "hail belt" language into a market that mostly sees wind and trees.

Commercial and multifamily

Low-slope membrane work after storms has a different documentation rhythm: access planning, tenant or HOA coordination, staged repairs, and ponding or seam issues that read nothing like a shingle close-up. Keep these in their own folders rather than blending them with steep-slope residential, or your portfolio will read as confused.

Seasonally, review the portfolio before storm season and again after it. Before the season, make sure your examples reflect current crews, products, and safety rules. After the season, harvest the best new jobs while the files are fresh.

Tooling, Storage, And Metadata

The portfolio is only as good as the system that holds it. A pile of photos in a shared phone gallery is not a portfolio; it is a liability waiting to be lost, leaked, or argued over. You do not need expensive software, but you do need discipline about where files live and what travels with them.

Keep the metadata, protect the privacy

Photos carry hidden data. Your phone's native camera embeds a timestamp and, often, GPS coordinates and the device used. That metadata is gold inside a job file, because it ties an image to a date and place no one can argue with. It is also a privacy hazard if you publish the raw file, since GPS coordinates can reveal an exact address. The rule is simple: keep originals with metadata intact inside the job file, and publish only stripped, resized copies. Most photo tools can export a web version without location data; make that a standard step before anything goes public.

Folder structure that survives turnover

Name things so a new hire can find them without asking. A workable convention:

/Storm-Jobs/
  /2026-04-spring-hail/
    /JOB-1042_oakwood-neighborhood/
      /01_elevations/
      /02_roof-context/
      /03_close-ups/
      /04_test-squares/
      /05_temp-protection/
      /06_production/
      /07_closeout/
      record.txt  (the standard job record)
      permission.pdf
  /_PUBLIC-APPROVED/
    JOB-1042_caption.txt + 2 stripped photos

The public-approved folder is the only place marketing pulls from, and every file in it points back to a job ID. That single rule keeps your marketing auditable and stops anyone from grabbing a raw, un-cleared photo straight off a phone.

Backups and access control

Storm season generates a flood of files fast. Back them up automatically, because a lost SD card or a cracked phone should never erase a job's documentation. Limit who can edit the public-approved folder, and keep an approval log. The point is not bureaucracy; it is being able to answer, months later, "where did this photo come from and who said we could use it?" in under a minute.

Documenting Roof Age And Cost Drivers Honestly

Two facts shape almost every storm conversation: how old the roof is and what the work will cost. A good portfolio handles both without overclaiming.

Roof age is a range, and you should say so

You cannot read a roof's exact install date from the curb, and neither can anyone else. What you can do is estimate a range from observable signs: granule loss, shingle curling and brittleness, the generation of materials present, layering, and any permit or prior-work evidence the homeowner shares. Record it as a range in the job file, and present it that way to homeowners. "This roof looks like it is in the fifteen-to-twenty-year zone for this material" is honest and useful. "This roof is exactly nineteen years old" is a guess dressed up as a fact, and homeowners can smell the difference.

This is also where roof age and storm exposure intersect, and where targeting tools earn their keep before you ever knock. A roof that is already near the end of its service life and then takes a hail or wind hit is a very different conversation from a three-year-old roof that a storm grazed. Knowing the rough age before you arrive helps you skip brand-new roofs and focus on homes where a storm likely pushed an aging roof over the line. Your portfolio then documents what you actually found, closing the loop between the planning estimate and the on-roof reality.

Talk about cost drivers, not magic numbers

Do not publish dollar figures in a portfolio, and do not let a rep imply a number a homeowner cannot rely on. What you can do is help homeowners understand what moves cost, which builds trust without boxing you in. The honest drivers are familiar to any veteran:

Cost driver	Why it matters
Roof size and pitch	More squares and steeper slopes mean more labor, material, and fall-protection setup
Number of layers to tear off	Two or three layers of old roofing add disposal and labor
Decking condition	Rotten or delaminated decking found at tear-off adds material and time
Accessibility	Tight lots, height, and landscaping affect staging and safety
Material choice	Three-tab, architectural, impact-resistant, and premium lines differ widely
Flashing, ventilation, and accessories	Chimneys, skylights, and valleys add complexity
Permit and code requirements	Local code may require specific underlayment, ventilation, or edge details

A portfolio example that quietly shows decking discovery, a proper ventilation correction, or code-compliant edge metal teaches a homeowner why a careful bid costs what it does, far better than a price tag would. Show the work; let the value speak.

A Worked Example: Canvass To Closeout

To make the system concrete, consider a hypothetical job from first knock to portfolio entry. Nothing here is a real customer; it is an illustration of the workflow.

Say a contractor works a neighborhood after a documented spring hail event. Instead of knocking every door, the rep focuses on homes flagged as likely due, where an aging roof took a real hit, and skips the obviously new roofs two streets over. At the first interested home, the rep does not climb anything yet. They photograph the four elevations from the ground, note the homeowner's concern in the homeowner's own words, and record a rough roof-age range from what they can see.

The access check comes next. Power is on, the deck looks sound, the pitch is walkable, and fall protection is set for the six-foot trigger, so the inspector goes up. They shoot roof-plane context for each slope, place a test square on the most-affected slopes, chalk and count impacts, and photograph soft-metal dents on the vents and gutter aprons. Granule loss is noted in neutral language. A downspout and a section of drip edge show clear impacts; those get close-ups. The inspector writes what was not inspected, and why, in the file.

The homeowner is concerned about an active drip in a hallway, so, with permission, the inspector photographs the interior stain and the matching roof area, then installs a temporary cover over the affected slope. The authorization for that temporary work is signed and saved. The rep walks the homeowner through observed conditions, hands over a written scope, and is careful to say that coverage is the carrier's call, not the contractor's.

The job sells. During tear-off, the crew finds a small area of soft decking, photographs it, and documents the change order. Production photos capture underlayment and the install sequence where it is safe to shoot. At closeout, the PM captures finished photos, delivers a warranty handoff, and notes that there are no open callbacks.

After closeout, the file goes through the scorecard. It has privacy clearance, clear before and after photos, a documented access decision, signed authorization, a scope that matches the photos, a closeout record, and a clean lesson about decking discovery. The marketing owner strips metadata from two images, writes a neutral caption, and files it in the public-approved folder beside the job ID and the approval date. The internal version keeps the decking surprise and the change-order note as a training point for estimators.

That is the whole loop. Notice that the marketing came last, was honest by construction, and cost almost nothing extra because the capture happened as a byproduct of doing the job well. Notice too that the same record now feeds next season's follow-up list: the neighborhood produced real work, and the cold doors the rep did not sell are worth a second touch as those roofs age.

How To Tell If The Portfolio Is Actually Working

A portfolio is a tool, and tools should earn their place. You will not have precise attribution, and you should be suspicious of anyone who promises it, but you can watch a few honest signals over a season.

Watch whether homeowners reference your documented work in conversations, whether reps reach for the portfolio unprompted because it helps them close, and whether new hires get up to speed faster because they have real examples to study. Watch your own quality data: as the scorecard runs job after job, are the gaps shrinking? Are more jobs closing with signed permissions and complete closeout photos than a year ago?

The operational signals matter as much as the marketing ones. A portfolio system that forces clean records makes your estimating more consistent, your callbacks easier to diagnose, and your follow-up list sharper. If you find yourself re-engaging old estimates and past customers more effectively because the records are finally organized, the portfolio is paying for itself on the back end, regardless of how many homeowners click through a gallery.

The one thing not to measure by is drama. A portfolio that makes your company look impressive but generates arguments, privacy worries, or claims you cannot back is failing even if it gets compliments. Quiet, documented competence is the result you want.

Common Mistakes That Sink A Storm Portfolio

Most bad portfolios fail in predictable ways. Watch for these:

• The drama wall. Fifty shots of caved-in roofs, no process, no closeouts. Impressive for two seconds, persuasive to nobody who is actually deciding.
• Borrowed or generic photos. Using images that are not your own work is a fast way to destroy trust and run afoul of advertising rules the moment a homeowner notices the same photo on three companies' sites.
• Insurance bragging. "We got this approved" captions leak private claim details, promise outcomes you do not control, and invite the customer's carrier into a fight.
• No "after." A before photo with no matching finished shot proves nothing. Always pair them, same roof.
• Captions the file cannot back. "Same-day response" with no timestamp. "Code upgrade" with no verification. If the file does not say it, the caption cannot.
• Privacy leaks. Visible addresses, plates, mail, kids, interiors, signatures. One screenshot and you have a problem.
• Stale examples. Work from a crew you no longer have, products you no longer install, or a response speed you can no longer staff. A current, modest portfolio beats an impressive archive that misrepresents today's company.

What To Ask Before You Publish (Quick Reference)

Keep this taped near the marketing owner's desk:

BEFORE THIS GOES PUBLIC:
[ ] Is this our own work, on a real, identifiable job file?
[ ] Do we have signed permission for THIS public use?
[ ] Is every personal identifier removed (address, plate, mail, faces, signatures)?
[ ] Are there clear before AND after photos of the same roof?
[ ] Does the caption avoid any insurance/payment promise?
[ ] Can I point to the file line that backs every claim in the caption?
[ ] Does the photo show SAFE work and finished quality?
[ ] Does this teach a homeowner or our crew something real?
If any box is empty: keep it internal or cut it.

Licensing, Contracts, And The Storm-Specific Legal Edges

Storm work attracts extra legal scrutiny because it attracts extra bad actors. Many states have tightened rules specifically around post-storm roofing, and your portfolio and intake process should reflect that you operate inside those lines.

Several states restrict or prohibit a contractor from acting as, or appearing to act as, the homeowner's representative in the insurance claim, and some prohibit offering to pay, waive, or rebate a homeowner's deductible as an inducement to sign. Rules vary by state, so confirm your own state's contractor licensing board and department of insurance requirements rather than assuming. The practical effect on your portfolio is the same everywhere: do not market in a way that implies you handle the claim or guarantee the homeowner pays nothing. Show the roofing work; leave the insurance relationship to the homeowner and their carrier.

Contracts matter for storm jobs in particular. Many jurisdictions require a written contract for residential roofing above a dollar threshold and grant homeowners a right to cancel within a set window, especially for door-to-door sales, which describes a lot of post-storm canvassing. A portfolio that quietly demonstrates clean, written scopes and proper authorizations signals that you follow these rules. It is one more way documentation discipline doubles as legal protection.

Keep your licensing current and visible. The consumer guidance homeowners read after a storm, from NRCA to state agencies, tells them to verify licensing and insurance before signing. A portfolio that shows licensed, insured, code-aware work answers that screening before the homeowner has to ask.

Turn The Portfolio Into A Sales Tool Without Overpromising

When a rep uses portfolio examples with a homeowner, the rule is simple: keep it grounded in the homeowner's actual situation. An example can show how you document a roof, how you install temporary protection, or how you complete a replacement. It cannot be used to predict a claim outcome or to pressure a decision.

If a homeowner points at a case and asks, "So will my insurance pay too?", answer carefully and honestly. Coverage decisions vary by policy and carrier, and the homeowner should confirm coverage with their insurer or a qualified advisor. Then steer back to what you actually control: documentation, a written estimate, temporary protection, the repair scope, the schedule, and the closeout record. That is a more honest and, in the long run, more convincing pitch than any payout promise.

Finally, keep the portfolio matched to your real capacity. If your examples imply a fast storm response you cannot staff this year, the portfolio is misleading even if every individual record is true. Archive old promises, update your service areas, and note when an example reflects a former process. A current, honest, modest portfolio outperforms an impressive one that no longer matches your crews, equipment, or service standards. Review it before each storm season and after major staffing changes.

Sources checked: June 18, 2026.

FAQ

What is a storm damage portfolio for a roofing contractor?

It is a curated, privacy-safe set of documented roofing jobs that shows how your company handles storm work: how you assess safely, what you observe, how you scope and complete the repair, and how clean your records are at closeout. The point is to prove process and competence with real, finished work, not to show a wall of dramatic damage photos or to imply that you can guarantee an insurance payout.

Should a storm damage portfolio include insurance claim results?

Usually no. Public examples should focus on observed conditions, work performed, documentation, safety, and closeout quality. Claim numbers, payout amounts, adjuster names, and carrier-versus-carrier comparisons expose private information, invite coverage disputes, and promise outcomes you do not control. You are a roofer, not the insurance company, so keep coverage decisions out of your marketing and steer homeowners to their insurer or a qualified advisor for coverage questions.

What photos belong in a storm damage portfolio?

Use a repeatable set every job: four elevations, full roof-plane context per slope, close-ups of observed conditions, hail test squares with marked impacts, soft-metal accessories, flashing and penetrations, temporary protection in place, safe work-in-progress shots, and clear completed-work and closeout photos. Date-stamp images with your phone's native camera. Always pair a before photo with an after photo of the same roof, and exclude private documents, interiors, plates, and identifiable people.

How many jobs should be in a roofing storm portfolio?

Fewer than you think. Five excellent, fully documented examples per job-type folder beat fifty loose photos. Each one should have clear before-and-after images, a neutral problem statement, a written scope, signed permission, and a lesson worth showing. A small, clean, current portfolio reads as competent and is easy to audit back to real files. A large, dramatic, thinly documented archive reads as a sales pitch and is hard to defend.

Is it legal to use customer roof photos in my marketing?

Generally yes, if you own the photos, have the customer's permission for that specific public use, and remove private identifiers like full addresses, plates, mail, faces, and signatures. Federal advertising rules require that claims be truthful and substantiated, and the FTC's endorsement and testimonial guides require backing for claims and warn against presenting an atypical result as typical. Get permission in writing, keep an audit trail, and pull any item fast if a customer withdraws consent.

What safety rules apply when documenting storm roof damage?

Federal OSHA generally requires fall protection at six feet or more above a lower level for residential roofing, under 29 CFR 1926.501, and California's Cal/OSHA aligned its residential standard with that six-foot trigger on July 1, 2025. Before climbing, run a hazard check for power lines, standing water, unstable trees, structural movement, pitch, and footing. If conditions are unsafe, document from the ground or by drone where legal, or postpone, and note the reason in the file.

How is a storm portfolio different from a regular roofing portfolio?

A general portfolio shows finished aesthetics and craftsmanship. A storm portfolio additionally has to prove safe, disciplined response to severe weather and stay carefully neutral about insurance. It emphasizes hazard assessment, standardized damage documentation such as hail test squares, temporary protection with authorization, and clean closeout records. It also avoids coverage claims entirely. The storm version lives or dies on documentation discipline, because storm-chaser skepticism is high and homeowners are screening for legitimacy.

How can a tool like RoofPredict help with storm portfolio and follow-up work?

Tools like RoofPredict help organize property records, inspection photos, source tags, job status, and follow-up tasks, and they help you target outbound by flagging which roofs in an area are likely due for work based on an estimated roof-age range and modeled storm impact per home. That sharpens the homes you mail or knock and helps you re-engage cold estimates. It does not inspect roofs, diagnose damage, certify roof life, or decide insurance coverage, so your crew and job file still do the proving.

How often should I update my storm damage portfolio?

Review candidate jobs right after closeout, while files are fresh, then audit the public portfolio at least quarterly and again before and after storm season. Remove outdated, weak, duplicate, or privacy-sensitive examples, and retire work that no longer reflects your current crews, products, service areas, or safety practices. A regular refresh keeps the portfolio honest and also surfaces process gaps, like missing closeout photos or unsigned permissions, that you can then fix at the source.