Roof age, ACV and the records that decide a claim

Carriers look harder at roofs than they used to, at the point of writing a policy, at renewal and at claim. That much is visible to anyone selling roofs this year.

What decides how a particular claim settles is not the adjuster's mood and not your invoice. It is a clause in the homeowner's own policy, the roof payment schedule, which sets whether that roof is settled on a replacement cost basis or an actual cash value one. For a roofing company, the part you control sits entirely on the other side of that: whether the age, the condition and the photographs exist when somebody asks for them.

The two settlement bases, briefly

You know these already, so this is the short version for the sake of what comes after.

Replacement cost value pays toward putting a new roof on. Actual cash value applies depreciation to that figure, so the payment reflects the age and condition of what was there, not the cost of what replaces it. The gap between the two lands on the homeowner, and it is where a signed job stalls.

The thing that decides which applies is written into the policy in advance. It is not decided at the claim.

Why we are not giving you an age

Everywhere you look right now there is a number: coverage drops to actual cash value at a specific age, carriers will not write above another specific age, replacing a roof cuts a premium by a specific percentage.

We went through those and could not verify them at any carrier's policy form or any state insurance department bulletin. They come from contractor and agency blog posts, and they disagree with each other. Some are probably accurate for the one carrier and one state the author had in mind.

Publishing a threshold would be easy and it would be the wrong thing to do, because a homeowner may make a real financial decision on it, and because a roofing company that repeats a wrong number in a kitchen loses more than it gains. The answer for a given house is in that policy's roof payment schedule, and nowhere else. That is a genuinely useful thing to be able to tell a customer.

What this changes about the job

Documentation stops being paperwork and becomes part of the work.

If a roof's condition at the time of a storm matters to how a claim settles, then the record of that condition has value, and the record is made by whoever is standing on the roof. Not later, and not from memory.

Four things are worth having on every job. The roof's age, if the homeowner knows it, written down, not remembered. Dated photographs of the condition before anything is touched. The condition described in words as well as pictures, because a photograph does not say what the person holding the camera was looking at. And a plain record of what was replaced, which is what makes the next claim on that house straightforward.

None of this is new advice. What is new is how frequently it gets asked for.

Where it breaks

Not at capture. Crews take photographs constantly.

It breaks at the filing, and it breaks quietly. A photograph taken on a personal phone and sent to a supervisor by text has no address attached and no reliable date once it has been forwarded twice. The roof age gets mentioned in a call and lives in whoever took the call. The condition is described in a text thread that is forty messages long by the time the job closes.

Eighteen months later an adjuster asks what the roof looked like before the work, and the honest answer is that somebody knows, somewhere.

Run the test on a job you finished last year, not on one you are working now. Pick one. Ask for the before photographs, the roof's age and who inspected it. If the answer takes more than a couple of minutes or involves texting a crew lead, the record lives in people, not in the company.

What to do this week

Pick the oldest job you might still get a claim on and try to assemble those four things. That tells you where you stand, which is more useful than any policy you could write today.

Then decide where roof age is supposed to live. Roofing software rarely ships an obvious field for it, so it ends up in a note. A note is not something you can search when you want every job with a roof over a certain age.

What a real field changes

That last sentence is worth sitting with, because it points at something bigger than claims.

Make roof age a field with a date in it instead of a sentence in a note, and two things follow. The first is defensive: when a claim arrives you can produce the age, and you can produce every job on that street with a roof of a similar vintage, which is what an adjuster conversation actually turns on.

The second is not defensive at all. A searchable roof age is a list of every customer whose roof is approaching the end of its life, ranked by how close it is. You already sold those roofs. You already have the address, the material, the install date and the photographs. Nobody in the market knows those houses better than you do, and that list is usually unpullable, because the information sits spread across notes, a filing cabinet and somebody's memory.

The capture side is ordinary engineering. A photograph taken on a phone already carries a timestamp and usually a location in its metadata, so a photo taken at the job's address can attach itself to that job without anyone filing it, with the date preserved rather than lost in a forward. Condition can be a short structured form completed on the roof, which takes a minute and produces something searchable, instead of prose typed from memory that evening. What was replaced is already on the invoice, so it can be read from there instead of entered twice.

Assemble those and a claim packet is a query, not an afternoon: age, dated photographs from before the work, recorded condition, and the line items that were replaced, for one address, in one click.

The general principle holds beyond insurance. A record that lives in a person leaves when the person does, and a record attached to a job stays with the job. Claims are the place where that difference presents a bill, and the aging-roof list is the place where it pays one.