How to Stop Forgetting Roofing Supplements That Never Get Filed

There is a special kind of money that roofing companies lose without ever feeling it leave. It is not the job you bid and lost. It is not the canvasser who quit. It is the supplement you legitimately earned, documented in your head, meant to write up, and then never sent. The replacement decking you found once the old shingles came off. The drip edge the original scope missed. The second layer of ice-and-water the code now requires. The steep-and-high labor that the desk estimate never accounted for. Real work, performed or required, fully supportable with photos and code citations, and it died in the gap between "I'll get to that" and the day the job closed out.

A forgotten supplement is worse than a lost lead, because you already paid for it. You bought the marketing that found the homeowner, you paid the rep who knocked the door, you mobilized the crew, you ate the material cost, and you performed the labor. The only thing you skipped was the fifteen minutes of documentation and the email that turns that work into recoverable dollars. Roofers obsess over cost-per-lead and close rate while quietly leaving four-figure sums on jobs they already own, because nothing in their process forces the supplement to get written before the file goes cold.

What follows is a working system for making sure a supportable supplement never slips through again: where they actually get lost, the triggers that catch them at the source, the documentation discipline that makes them stick, the routing that gets them out the door on a schedule instead of on a whim, and the metrics that tell you whether your fix is holding. It stays strictly on the side you are allowed to be on, which is documenting your own scope and writing an accurate estimate of the work, and it is blunt about where roofers get themselves in legal trouble by drifting past that line.

Why supportable supplements get forgotten in the first place

If you want to stop losing supplements, you have to be honest about why they vanish. It is almost never one big failure. It is a chain of small, ordinary moments where the work was real but the documentation step had no owner, no trigger, and no deadline. Name the failure points and most of them turn out to be fixable with process, not with hiring a "supplement guy" and hoping.

The timing gap between discovery and write-up

Most supportable additional scope is discovered at tear-off, which is the single worst moment to document it. The crew is moving, the dumpster is filling, the homeowner is anxious, and the production lead has nine other things in front of him. He sees the rotted decking, mutters "we'll bill that," dry-rots a mental note, and gets back to keeping the job on schedule. By the time anyone with estimate authority touches the file, the decking is covered, the crew has demobilized, and the only evidence is a vague recollection that "there was some bad wood on the back slope."

The discovery and the documentation are separated by hours or days, and memory is a terrible storage medium for billable detail. The fix is not "remember better." The fix is to move documentation to the moment of discovery and make it physically impossible to keep working until it is captured.

No single owner of the supplement

On a lot of crews, everyone touches a supplement and no one owns it. The sales rep assumes the production manager will catch it. The production manager assumes the office will write it up from the photos. The office assumes the rep already flagged it. The result is the classic diffusion-of-responsibility failure: a task that three people could do becomes a task that zero people did. When you ask later, each one sincerely believed it was handled.

A supplement needs exactly one accountable owner per job, named before the crew rolls, with a backup. Not a committee. One name.

The file closes before the supplement is written

This is the quiet killer. The job gets marked complete in your system, the final invoice goes out, the crew gets paid, and the file drops off everyone's active list. Out of sight, out of mind, out of money. Once a job is closed, the supplement has to fight the gravity of "we already moved on," and it almost always loses. Nobody reopens a closed job to chase eight hundred dollars of drip edge they forgot.

Your close-out has to have a gate: a job cannot be marked complete until the supplement question is explicitly answered yes-or-no, with documentation attached if yes.

Knowledge concentrated in one person's head

In a surprising number of companies, the only person who actually knows what is supportable is the owner or one veteran estimator. When that person is on a roof, on vacation, or buried, supplements stall. Worse, the knowledge never transfers, so when that person leaves, the company's supplement recovery quietly collapses and nobody connects the dots.

The knowledge has to live in a checklist and a line-item template, not in one skull. The rest of this piece is largely about getting it out of the skull.

Fear of looking greedy or sloppy

Some reps and even owners avoid supplements because they worry it makes them look like they padded the original bid or like they missed something. Both fears are misplaced when the supplement is for genuinely unforeseen conditions or code-driven items that you cannot see from the ground. Decking condition under old shingles is, by definition, not visible until tear-off. Documenting it accurately is the opposite of sloppy. But the emotional friction is real, and it causes people to "just eat it," which trains the whole company that supplements are optional.

The cure is a clear internal standard for what is legitimately supportable, so reps are documenting a defensible fact, not making an awkward ask.

What you are allowed to do, and the line you cannot cross

Before any system, get the legal frame right, because crossing the line here can cost a roofer their license, their reputation, and in some states expose them to charges. The mistake is not usually malicious. It is a contractor who slides from "documenting my work" into "handling the homeowner's claim" because it feels like the same thing. It is not.

Here is the side you are firmly allowed to operate on. You can inspect the roof. You can document damage and existing conditions with photographs and measurements. You can identify code-required items for the work you are performing. You can write a thorough, accurate estimate for the scope of repair or replacement, line by line, aligned to standard estimating line items and your local code. You can hand that estimate and that documentation to the homeowner. You can state plain facts about your own scope and your own findings to anyone, including a carrier's representative, when those facts concern the work you are doing.

Here is the side you cannot touch, and these are the things that turn a contractor into an unlicensed public adjuster in most states. You cannot, for a fee, negotiate or adjust or "handle" the homeowner's insurance claim. You cannot interpret what their policy does or does not cover. You cannot promise a specific payout, a specific approval, or that any particular item will be paid. You cannot tell a homeowner their deductible will be waived, absorbed, eaten, or made to disappear, and you cannot structure your pricing to do it. You cannot advertise a "free roof." You cannot represent the homeowner against their insurer. Public adjusting is a licensed activity, and doing it without a license is a real offense that state departments of insurance prosecute.

The clean mental model is this. You document the physical reality and you price the work. The homeowner files and communicates with their carrier. The insurer decides coverage. A supplement, in the honest sense, is simply additional documentation of additional scope that was not in the original estimate, written accurately and handed over. You are correcting the estimate to match the roof. You are not arguing the claim.

The do-not-say list, taught plainly

Train every rep and every estimator on the phrases that cross the line. These are the ones that get contractors in trouble, and they should never come out of your people's mouths or appear in your marketing:

• "We'll handle the whole claim for you." You document and estimate; you do not handle claims.
• "We'll get this approved." You cannot promise an approval; the insurer decides.
• "Don't worry about your deductible, we'll take care of it." Deductible erosion is fraud exposure in many states and is never something you promise.
• "Free roof." Never. The homeowner is responsible for their deductible and for whatever their policy does not cover.
• "Your policy covers this." You do not interpret coverage. You state what the roof needs; coverage is between the homeowner and the carrier.
• "We'll negotiate with your adjuster." You can share factual documentation about your scope; you do not negotiate the claim for a fee.

Keep this list on the wall. The point is not to avoid supplements. It is to write supplements that are pure documentation of real scope, so your work is bulletproof and your license is safe.

The supplement trigger map: catch it at the source

The core of never forgetting a supplement is to stop relying on memory and start relying on triggers. A trigger is a physical or scheduling event that forces the documentation step to happen in the moment, tied to a specific condition. Build the map once and the supplements catch themselves.

There are four natural trigger points in a roofing job, and a supportable item should be captured at whichever one it first becomes visible.

Trigger point 1: the original inspection

Some supportable scope is visible before you ever sign the job, and capturing it early both strengthens the original estimate and prevents a "surprise" later. During the initial inspection, your rep should be documenting the damage and every condition that drives line items the eye-level bid tends to miss.

The discipline here is simple: the rep photographs and notes every one of these on the first visit, even if the original estimate already includes them. That record becomes the baseline that makes any later supplement obviously legitimate rather than something that looks invented.

Trigger point 2: tear-off (the big one)

This is where the most money is found and the most money is lost, because the supportable conditions are invisible until the old roof comes off and they appear at the worst possible moment for documentation. The fix is a hard rule: the crew does not dry-in over any unforeseen condition until it has been photographed and logged.

The conditions that show up at tear-off and the documentation each one needs:

• Deteriorated, rotted, or delaminated decking. Photograph each affected area with something for scale, mark the sheets, and note square footage. Decking replacement is priced by the sheet or by the square foot and is one of the most commonly forgotten supplements because the crew just replaces it and moves on.
• Decking that does not meet code spacing or thickness. If the existing deck cannot legally receive new roofing without correction, that correction is supportable. Cite the code.
• Missing or inadequate underlayment that code now requires. The original roof may predate current ice-and-water or synthetic underlayment requirements; the new install must meet current code.
• Rotted or damaged fascia and rake boards exposed at tear-off. Photograph and measure linear footage.
• Rusted or undersized flashing, valleys, and pipe boots that have to be replaced rather than reused. Each is a line item.
• Damaged or deteriorated ventilation that code or manufacturer specs require you to address.

The rule that makes this stick: a crew lead's photo of the dried-in section is not accepted as proof of completion until the supplement-condition photos for that section are already in the job folder. You tie progress payment or crew sign-off to the documentation, and the documentation stops being optional.

Trigger point 3: dry-in and install

Even after tear-off, conditions surface during the install that are supportable. Decking that fails once weight is on it. A chimney that turns out to need a full flashing rebuild rather than a reseal. Ventilation that has to be reconfigured. These are smaller and easier to forget precisely because the dramatic tear-off moment has passed and everyone assumes the surprises are over.

The trigger here is the install checklist itself. Every install checklist should carry a standing line: "Any conditions discovered during install requiring added scope? Yes / No. If yes, photos attached and owner notified." A forced yes-or-no on a checklist that someone has to sign catches the items that would otherwise evaporate.

Trigger point 4: final inspection and close-out

The last net. Before a job can be closed, someone walks it against the original scope and the photo record, and the explicit question gets asked: is there any documented condition that was performed or required but never written into a supplement? This is the gate described earlier, and it is the difference between a leaky bucket and a sealed one. We will detail the close-out gate below because it is where most of the recovery actually happens.

The documentation standard that makes a supplement stick

A supplement is only as good as its evidence. The reason a lot of supportable scope dies is not that nobody noticed it, it is that nobody documented it well enough to be worth submitting, so it quietly gets eaten. A consistent documentation standard solves this and has the side benefit of making your supplements far stronger when the homeowner submits them to their carrier.

Photograph like the photos have to stand on their own

Assume the person reviewing the documentation was never on the roof and is skeptical. Your photos have to prove the condition without you in the room to narrate.

Every supportable condition gets the same three-shot treatment:

1. A context shot showing where on the roof the condition is. The facet, the slope, the side of the house. This anchors the close-up so it cannot be dismissed as "could be anyone's roof."
2. A detail shot showing the condition itself clearly and in focus. Rot, rust, delamination, layer count, pitch.
3. A scale shot with something for measurement reference. A tape measure across the rotted decking, a pitch gauge on the slope, a coin or a marked board. Scale turns "some bad wood" into "thirty-two square feet of delaminated decking on the rear slope."

Capture the metadata too. Date and time stamps and, where your software supports it, GPS coordinates that tie the photo to the address. A photo that can be tied to the property and the date is far harder to wave away than a loose image with no context.

Write the line item in standard estimating language

When you write the supplement, write it the way professional estimating software writes it, because that is the language carriers, homeowners, and reviewers expect to see. That means a line item, a quantity with a unit, and a description that names the work. "Replace 1x6 fascia, 24 LF, rear elevation, rotted at tear-off." "R&R drip edge, 180 LF, missing on original install, code required." Each item ties back to a photo and, where relevant, to a code section.

The goal is an estimate that reads as a faithful, granular description of the actual work and conditions. You are not inflating anything. You are matching the paper to the roof. An accurate, line-itemized, photo-backed supplement is both the honest thing and the durable thing.

Cite code by section number, not by vibe

"Code requires it" is weak. "2021 IRC Section R905.2.7.1 requires drip edge at eaves and rake edges" is strong, when that is in fact what your adopted local code says. Keep a short reference sheet of the code sections your jurisdiction has adopted that commonly drive supplements: ice-and-water shield coverage, drip edge, decking attachment and condition, ventilation, valley construction. Know which version your local building department enforces, because adopted code varies by jurisdiction and amendment. When a supplement is code-driven, the citation is the strongest evidence you have, and it is factual rather than argumentative.

Keep everything in one job folder, not in someone's phone

Photos scattered across three crew members' phones is the same as no photos. Every image, the original estimate, the supplement, and the code citations live in one place tied to the job in your system. If your photos live on personal phones, you will lose them to broken screens, full storage, and ex-employees. A shared, job-tied folder is the minimum.

The supportable items roofers forget most, line by line

It helps to know exactly which items leak. Across residential reroofs, the same handful of supportable line items get performed-and-forgotten over and over, because each one is either invisible until tear-off, easy to absorb into the crew's flow, or small enough that nobody thinks it is worth chasing until you add up a year of them. Build your trigger map around these and you catch the bulk of the lost money.

None of these are exotic. They are the everyday conditions a competent crew handles without thinking, which is precisely why they vanish. The work gets done, the documentation does not, and the line item never appears. When you audit closed jobs, this table is your checklist for what to look for.

Handling the homeowner without crossing the line

A supplement involves a conversation with the homeowner, and that conversation is where reps most often drift into territory that is not theirs. Keep it factual and you stay safe; the homeowner stays informed, and your documentation does its job.

What you say is descriptive, not predictive. "When we pulled the old shingles off your rear slope, we found thirty-six square feet of rotted decking that we replaced so your new roof has a sound surface to attach to. Here are the photos and the measurement, and here is the line item for that work. You will want to add this to what you submit to your insurer." That is a contractor describing his own work and handing over documentation. It is accurate, it is yours to say, and it never touches the claim.

What you do not say is anything predictive about coverage or payout. You do not tell the homeowner the carrier will pay for the decking, because you do not decide that. You do not tell them it is covered, because you do not interpret their policy. You do not tell them their deductible will shrink, disappear, or be handled. You do not offer to call their adjuster and work it out for them for a fee, because that is adjusting their claim. The homeowner submits the documentation; the insurer decides. Your job ended when you accurately documented and priced your own scope and handed it over.

A useful internal test for any sentence a rep is about to say: is it a fact about the roof or my work, or is it a prediction about money or coverage? Facts about the roof and your work are yours to state all day. Predictions about money or coverage are not, and they are exactly where contractors lose licenses. Train the test alongside the rules, and reps will self-correct in the field.

Build the routing system: from discovery to sent

Triggers catch the supplement and documentation makes it stick, but a supplement that is captured and documented and then sits in a folder is still a forgotten supplement. The last and most-skipped piece is routing: a defined path with an owner and a deadline that moves the documented item out the door on a schedule. This is where you convert "we have great photos" into "the supplement is sent."

Assign one owner per job before the crew rolls

At the moment a job is scheduled, name the supplement owner for that job. One person who is accountable for answering, by close-out, whether a supplement exists and getting it written and sent if it does. Put the name in the job record. Give them a backup for when they are out. This single move kills the diffusion-of-responsibility failure that swallows most supplements.

Give the documentation a deadline, not a "when I get to it"

A documented supplement condition should convert to a written, sent supplement within a fixed window, for example three business days from discovery. The window matters because the strongest moment for a supplement is while the evidence is fresh, the homeowner is engaged, and the job is still active. Every day that passes makes it more likely the file closes first. A deadline on the calendar beats good intentions every time.

Use a simple status pipeline you can see at a glance

You cannot manage what you cannot see. Track every supplement through a short, visible set of stages so nothing stalls invisibly:

A whiteboard works. A spreadsheet works. Your existing software with a custom pipeline works better. The point is that an item in "Flagged" that has not moved in three days is visible and chaseable instead of silently dead.

Install the close-out gate

The most important single rule in the whole system: a job cannot be marked complete until the supplement question is explicitly answered. Add a required field to your close-out: "Supplement: none required / written and delivered." If "none required," the person closing the job is putting their name on that judgment against the photo record. If "written and delivered," the documentation has to be attached. No job closes without one of those two answers. This gate alone recovers more money than any other single change, because it stops the file from closing before the supplement is dealt with.

A worked example: the eight-hundred-dollar job nobody remembered

Make it concrete. A residential reroof, signed at fourteen thousand on a steep two-story colonial. The crew tears off on a Tuesday. On the rear slope, under the old architectural shingles, they find a band of delaminated decking along an old valley where water tracked for years. The crew lead, a good one, replaces four sheets of decking to keep the job moving and the homeowner dry, snaps one blurry photo because he is supposed to, and keeps working. The job finishes Thursday, looks great, and the homeowner is thrilled.

Here is the leak in the old way. Nobody owned the supplement. The crew lead assumed the office would see his photo and bill it. The office never opened the photos because the job looked complete and the final invoice matched the original estimate. The job closed Friday. The four sheets of decking, the labor to replace them, and the disposal, call it roughly six to eight hundred dollars of supportable scope, were performed, paid for in material and labor, and never written up. The company ate it and never knew.

Here is the same job with the system. Before the crew rolled, the production coordinator was named supplement owner. At tear-off, the crew lead hits the delaminated decking and the rule kicks in: no dry-in over that section until it is documented. He shoots the three-shot set, context, detail, and a tape measure across the affected area showing thirty-six square feet, and logs it as "Flagged" in the pipeline with the address-stamped photos. The job folder now has proof. Within the three-day window, the supplement owner writes the line item, "R&R roof decking, 36 SF, delaminated, rear slope, discovered at tear-off, photos attached," moves it to "Written," and delivers the documentation to the homeowner so they can submit it to their carrier. The close-out gate on Friday shows "supplement written and delivered," and the job closes clean. Same roof, same crew, same condition. The only difference is that the work that was already done got documented and the homeowner got an accurate paper trail, instead of the company quietly absorbing it.

Run that delta across a hundred jobs a year and the forgotten-supplement leak is frequently the difference between a thin year and a healthy one, on work you already performed.

Where most contractors get the system wrong

Even contractors who try to fix this tend to fail in predictable ways. Knowing the failure modes lets you skip them.

They make it a sales initiative instead of a documentation habit. When supplements are framed as "find more money," reps get uncomfortable and the legal risk goes up because the pressure pushes people toward over-reaching. Frame it as "document the roof accurately." The money follows from honest, complete documentation, and the framing keeps everyone on the safe side of the line.

They rely on the best person instead of the best checklist. If your supplement recovery depends on one veteran, it is fragile and it does not scale. Get the knowledge into a trigger map, a documentation standard, and a line-item template that a competent new hire can execute.

They document on personal phones. Photos die on personal phones. Anything not in the job folder does not exist for purposes of a supplement.

They have no deadline, so "later" becomes "never." Without a fixed window from discovery to written, the file always closes first.

They skip the close-out gate because it slows things down. The gate feels like friction. The friction is the point. It is the only thing standing between a documented condition and a closed-and-forgotten job.

They drift across the legal line because nobody trained them. A rep who starts promising approvals or talking about deductibles is not a supplement problem, it is a liability problem. Train the do-not-say list as hard as you train the documentation standard.

Targeting the jobs where supplements live, before you bid them

Everything to this point is about catching supplements on jobs you are already doing. There is an upstream move that compounds it: spending more of your selling time on the roofs where supportable, code-driven, and storm-related scope is most likely to exist in the first place. A roof that is genuinely aging out or that has actually taken storm impact is far more likely to produce legitimate additional scope at tear-off than a roof that is five years old and pristine. If you can aim your knocking and mailing at the roofs that are actually due, you both close more jobs and walk into more jobs where honest supplements are real.

This is where roof-by-roof targeting data earns its place in the workflow. RoofPredict scores the roofs in your area by an estimated roof-age range from aerial imagery and by the storms each individual roof has actually taken, modeling hail and wind impact house by house rather than just showing you where a storm passed on a map. It is not a lead service and it does not handle anything on the claim side. What it does is tell you which roofs are most likely due, so you point your crew and your mailing at the houses where age and storm history make additional scope plausible, and skip the new roofs where it is not.

Be clear-eyed about the limits, because honesty is the whole point of a system like this. The roof age is a range, not an install date, and the storm modeling gives you odds and history, not a guarantee of damage or a promise that any item will be covered. It tells you where to look and what the roof has likely been through. It does not tell you what the carrier will decide, it does not document your scope for you, and it never touches the claim. The documentation discipline above is still yours to run on every job. What the data changes is the front of the funnel: more of your jobs start on roofs where age and real storm exposure mean the conditions you find at tear-off are genuine and supportable, which makes the whole supplement system more productive and keeps it firmly on the honest side of the line.

The metrics that tell you the leak is closed

You fixed the system. Now prove it is holding, because a process without measurement quietly decays back to the old way within a quarter. Track a small number of honest numbers.

Supplement capture rate

Of jobs where a supportable condition was discovered, what percentage resulted in a written, delivered supplement? This is the headline number. If you are capturing conditions but only converting half of them to written supplements, your routing or your deadline is broken. The target is that essentially every documented condition becomes a written supplement, because by the time it is documented, the hard part is done.

Time from discovery to written

Measure the days between "Flagged" and "Written." If that number is creeping up, your supplements are aging toward the close-out cliff. A tight cycle time is the single best predictor that you are not losing items to a closing file.

Close-out gate compliance

What percentage of closed jobs went through the close-out gate with an explicit supplement answer? This should be one hundred percent, because the gate is mandatory. Any closed job without an answer is a hole in the system and tells you the gate is being skipped.

Forgotten-scope audits

Periodically pull a sample of closed jobs and compare the tear-off and install photos against the supplements written. Find any performed-or-required scope that never got documented. This audit is uncomfortable and it is the most valuable thing you can do, because it tells you in dollars what the leak still costs and whether the gate is actually working.

A simple monthly review

When the audit keeps surfacing the same missed item, for example decking every time, that is not a discipline failure, it is a trigger gap. Fix the trigger rather than scold the crew.

A 30-day rollout you can actually run

You do not need a software project or a consultant to start. You need to install the four moving parts in order over a month.

Week 1: Write the trigger map and the do-not-say list. Sit down with your best estimator and list every condition that is legitimately supportable on your typical jobs, mapped to the trigger point where it first becomes visible. Build the one-page documentation standard, the three-shot photo rule, the line-item language, and the code-section reference sheet for your jurisdiction. Print the do-not-say list and put it where reps and crews will see it.

Week 2: Name owners and set the deadline. Add "supplement owner" to your job-scheduling step so every new job gets one. Set the discovery-to-written window, three business days is a reasonable default. Tell every crew lead the tear-off rule: no dry-in over an unforeseen condition until it is photographed and logged.

Week 3: Stand up the pipeline and the close-out gate. Create the visible status pipeline, whiteboard or spreadsheet or software. Add the required supplement field to your close-out so no job can be marked complete without an explicit answer. Move the job folder for photos into one shared, job-tied place if it is not already.

Week 4: Start measuring and run the first audit. Begin tracking capture rate, discovery-to-written days, and gate compliance. At the end of the week, pull five recently closed jobs and audit the photos against the supplements. Whatever you find missing is your week-five training topic. Then repeat the audit monthly.

Inside one month you will have moved supplements from "something we remember to do when we remember" to a system with triggers, owners, deadlines, a gate, and numbers. The forgotten-supplement leak is one of the few places in a roofing business where you can recover real money without selling a single new job, because the work was already yours. You just have to stop letting the documentation die in the gap between the roof and the file.

The short version, for the wall

If you do nothing else, do these five things, and most of the leak closes:

1. Name one supplement owner per job before the crew rolls.
2. No dry-in over any unforeseen condition until it is photographed with context, detail, and scale, and logged.
3. Convert every documented condition to a written supplement inside a fixed window, three business days.
4. No job closes until the supplement question is answered: none required, or written and delivered.
5. Keep every rep and crew on the right side of the line. Document and estimate your own scope. The homeowner files, the insurer decides, and you never promise a payout, erase a deductible, or handle the claim.

FAQ

Why do supportable roofing supplements get forgotten so often?

Almost never from one big failure. It is a chain of small ones: the condition is discovered at tear-off, the worst possible moment to document it, while the crew is moving and the homeowner is anxious; no single person owns the supplement, so three people each assume someone else has it; and the job gets marked complete and the file closes before anyone writes it up. Memory is a terrible storage medium for billable detail. The fix is process, not willpower: capture the documentation at the moment of discovery, name one owner per job, and never let a job close until the supplement question is explicitly answered.

What is the single most important change to stop losing supplements?

The close-out gate. A job cannot be marked complete until someone explicitly answers the supplement question: none required, or written and delivered. If they answer none required, they are putting their name on that judgment against the photo record. If they answer written and delivered, the documentation has to be attached. This gate alone recovers more money than any other change, because the quiet killer is the file closing before the supplement is dealt with. Once a job is closed, nobody reopens it to chase the scope they forgot.

How do I document a supplement so it actually holds up?

Assume the reviewer was never on the roof and is skeptical. Use a three-shot set for every supportable condition: a context shot showing where on the roof it is, a detail shot of the condition itself in focus, and a scale shot with a tape measure or pitch gauge so the size is provable. Capture date stamps and, where your software allows, GPS tied to the address. Then write it as a standard line item with quantity and unit, for example R&R roof decking, 36 SF, delaminated, rear slope, discovered at tear-off. Tie each item to its photo and, where relevant, to a code section by number.

Which supplement items do roofers forget most?

The everyday ones a good crew handles without thinking, which is exactly why they vanish. Decking replacement found at tear-off, drip edge and ice-and-water shield required by current code, steep and high labor charges the desk bid skipped, detach-and-reset of gutters and accessories, flashing and pipe boots that get replaced rather than reused, valley material, ventilation driven by code or manufacturer spec, disposal overage from extra layers, and rotted fascia or rake board exposed at tear-off. Build your trigger map around this list and you catch the bulk of the lost money.

When during a job should each supplement be caught?

At whichever of four trigger points it first becomes visible. Original inspection catches steep slope, height, existing layers, and code items you can see from the ground. Tear-off catches the big ones: deteriorated decking, missing underlayment, rotted fascia, rusted flashing. Dry-in and install catch the conditions that surface once weight is on the roof. Final inspection and close-out is the last net, where you walk the job against the original scope and the photo record. The rule that makes tear-off work: the crew does not dry-in over any unforeseen condition until it is photographed and logged.

Where is the legal line between writing a supplement and adjusting a claim?

You can inspect the roof, document conditions with photos and measurements, identify code-required items for your work, write an accurate line-itemized estimate of the scope, and hand that documentation to the homeowner. You can state plain facts about your own scope. You cannot, for a fee, negotiate, adjust, or handle the homeowner's claim; interpret what their policy covers; promise a payout or approval; tell them their deductible will be waived or absorbed; advertise a free roof; or represent them against their insurer. That last set is unlicensed public adjusting, which state departments of insurance prosecute. You document and price; the homeowner files; the insurer decides coverage.

What should a rep never say to a homeowner about a supplement?

Anything predictive about money or coverage. Do not say we will handle the whole claim, we will get this approved, do not worry about your deductible, free roof, your policy covers this, or we will negotiate with your adjuster. Each of those crosses into interpreting coverage, promising a payout, eroding a deductible, or adjusting the claim. A safe internal test for any sentence: is it a fact about the roof and my work, or a prediction about money or coverage? Facts are yours to state all day; predictions about money or coverage are not, and they are where contractors lose licenses.

How fast does a documented supplement need to be written and sent?

Inside a fixed window, three business days from discovery is a reasonable default. The window matters because the strongest moment for a supplement is while the evidence is fresh, the homeowner is engaged, and the job is still active. Every day that passes makes it more likely the file closes first and the scope is lost. Track the days between flagged and written; if that number creeps up month over month, your supplements are aging toward the close-out cliff and your routing or your deadline is broken.

How do I know my fix is actually working?

Measure a few honest numbers. Supplement capture rate: of jobs where a supportable condition was discovered, what share became a written, delivered supplement. Time from discovery to written, which should stay inside your window. Close-out gate compliance, which should be effectively one hundred percent. And periodic forgotten-scope audits where you pull a sample of closed jobs and compare the tear-off and install photos against the supplements written. When an audit keeps surfacing the same missed item, that is a trigger gap to fix, not a reason to scold the crew.

Can targeting data help me find jobs where supplements are more likely?

Indirectly, at the front of the funnel. A roof that is genuinely aging out or that has actually taken storm impact is far more likely to produce legitimate additional scope at tear-off than a five-year-old pristine roof. RoofPredict scores the roofs in your area by an estimated roof-age range from aerial imagery and by the storms each individual roof has actually taken, modeling hail and wind house by house rather than just where a storm passed. It is not a lead service and it never touches the claim. The roof age is a range, not an install date, and storm modeling gives odds and history, not a guarantee of damage or coverage. It helps you aim; the documentation discipline on every job is still yours to run.