A concept by Patrick BusheDeveloped & drawn into this page by Claude (AI)Concept · not an insurance program · not legal advice
The Roof Certificate
A roof’s age decides whether an insurer will cover a home and what it costs, yet nobody keeps the roof’s record. The roofer, the city, the insurer and the owner each hold a piece. This page borrows the fix the web already uses for its padlock: a certificate issued by a licensed roofer, kept in one public log, checked by every insurer.
The chain of the argument: insurers price and drop homes by roof age and condition → the age on file is often a guess, a seller’s word or an aerial photo → in 2023 an insurer in Texas dropped a home over a photo of a roof about a year old, then said it had read the wrong report → the web had the same trust problem with SSL certificates and solved it with licensed issuers and an append-only public log → so make roofers issue a signed certificate for every new roof, put it in a public log, and have insurers check the log instead of guessing.
Please read this first
This is a concept, not a program or a law. The Florida rule, the Texas story, the California FAIR Plan count and the way SSL logs work were checked in November 2026 and are linked at the bottom. The phase-in dates are Patrick’s proposal. The sample certificate and the roof’s life story are made up to show the idea. Not legal or insurance advice.
Start here
The whole idea, in plain English
No insurance or computer knowledge needed. Read this part and you’ll understand the entire page.
Insurers care a lot about your roof. An old or damaged roof leaks, blows off and burns more easily, so its age and condition move the price of a home policy and can decide whether you get one at all. Florida even has a law about it: an insurer can’t refuse a home only because its roof is under 15 years old.
But the roof’s age is often a guess. In a popular r/Insurance thread, an agent said the first thing to fix when a home policy is too expensive is a wrong roof age on file, because when a roof is replaced, nobody tells the insurer. Another agent said some sellers fudge the roof’s age to close a sale.
Insurers have started checking from the sky. They buy aerial photos and software that rates roofs. Reporters in Texas found a homeowner whose policy was dropped over a photo of a roof that was about a year old. The insurer later said its underwriter had looked at the wrong report.
The web had this problem too. When you see the padlock on a website, your browser is trusting a certificate that says “this really is that site.” Certificates are issued by approved companies, and since 2018 Chrome only trusts new ones that are written into public logs anyone can check. A fake can still be made, but it can’t hide.
Here’s the redesign. When a licensed roofer finishes a roof, they issue a signed roof certificate: address, date, material, fire rating, permit number and photos. It goes into one public log. Insurers check it at every quote and renewal. A storm claim flags it until the repair is logged. In Patrick’s version, roofers must issue one for every new roof from day one, and insurers must have one on file for every home they cover by 2030.
Quick answer
Does roof age affect home insurance?
Yes: whether you get a policy, whether you keep it, and what it costs. Checked November 2026.
What happens
A real example
Getting a policy
Insurers can turn down homes with old roofs, and some states set limits on that.
Florida law bars refusing a home only because its roof is under 15 years old. A roof 15 or older gets an inspection, and if it has 5 or more years of life left, its age alone can’t be the reason (Fla. Stat. 627.7011).
Keeping it
Insurers rate roofs from aerial photos and can drop a home at renewal.
In Austin, Nationwide declined to renew a home in 2023 over an aerial photo showing a roof in “poor condition.” The roof was about a year old; Nationwide later said its underwriter had reviewed the wrong aerial report (KUT, 2025).
The price
An older roof on file usually means a higher premium or less coverage for the roof.
An agent in the r/Insurance thread said a wrong roof age is the first thing to fix to lower a home policy, since a replaced roof often never reaches the insurer’s file.
How to prove your roof’s age today: the city or county permit for the reroof, the roofer’s invoice and warranty papers, or a home inspection report. Send a copy to your agent; it’s the paperwork the certificate below would replace.
A roof leaves a paper trail, but it’s scattered. The city has a permit, if one was pulled. The roofer has an invoice. The manufacturer may have a warranty registration. The insurer has whatever age was typed in when the policy started, and an aerial photo bought from a data company. The owner has a drawer. When the house sells, the next owner gets the seller’s word.
So prices run on guesses, and the guesses go both ways. A homeowner pays for an old roof they already replaced. An insurer covers a roof that’s older than the seller said. And when software reads a photo wrong, the homeowner finds out from a cancellation letter.
The web faced the same kind of trust problem. In 2011 a certificate company was hacked and issued fake certificates for Google. The fix that followed, Certificate Transparency, didn’t try to make fakes impossible. It made every certificate public, in logs that can only be added to, so a fake gets caught. This page asks what that would look like for a roof.
15 yrs
under this, a roof’s age alone can’t block a Florida policy
~1 yr
age of the Austin roof an insurer dropped over an aerial photo
698,307
California FAIR Plan policies, Sept 2026, up 157% since 2022
2018
since then Chrome only trusts new SSL certificates found in public logs
R‑1 The padlock’s chain of trust, copied for roofs
The web row is how SSL works today · the roof row is the redesign
R‑1. On the web, a browser trusts a site because an approved company vouched for it and the certificate sits in a public log. For a roof, the license board plays the root, the licensed roofer is the issuer, and the insurer is the browser that checks before it trusts. Nobody has to take the seller’s word.
R‑2 What one certificate says, and one roof’s life in the log
Sample · made-up address, numbers and dates
R‑2. The certificate holds the facts an insurer asks for and a buyer worries about, signed by the roofer who did the work. Everything after that is added to the log, never edited: a storm flag, the repair that clears it, a sale, an inspection that extends the roof’s life. The photos stay with the registry; the log keeps a fingerprint of each one, so nobody can swap them later.
R‑3 The phase-in, with Patrick’s deadline
Proposal · this sketch starts in 2027
R‑3. New roofs are the easy part: the roofer is already there, with a license and a permit. Older roofs catch up at the moments a roof already gets looked at, like a sale or a renewal inspection. Insurers lose the option of guessing in 2030.
The design · five rules
Only licensed people can issue one. A licensed roofer for a new roof or a repair, a licensed inspector for an existing roof. The license number is on the certificate, so a bad issuer can lose the license, the way a certificate company that misbehaves loses browser trust.
One public log, add-only. Certificates, repairs, flags and renewals are added, never edited or deleted. Anyone can check it, and the owner gets a notice whenever something is added at their address, the way site owners watch the SSL logs for certificates they didn’t ask for.
Insurers read it instead of guessing. Quotes and renewals pull the certificate. An aerial photo that looks wrong can trigger an inspection, not a drop.
A storm flag, not a black mark. A roof claim flags the certificate until a licensed repair is logged, then the flag clears. Buyers see that the roof was hit and that it was fixed.
It ends with the roof. The maker’s rated life sets the expiry date. An inspection can extend it in steps; a new roof starts a new certificate.
Why a public log, not a blockchain
Patrick’s first idea was an SSL-style certificate or a blockchain. The SSL logs show why the blockchain part isn’t needed. A Certificate Transparency log is run by a known operator, takes new entries in order, and proves with cryptography that nothing earlier was changed; independent monitors keep copies and raise an alarm if it was. That gives the two things a roof registry needs, a record nobody can quietly rewrite and someone accountable for running it, without tokens, mining or a crowd of anonymous servers.
The accountable keeper matters here. Roofers are licensed by the states (in California, the Contractors State License Board licenses roofers under its C-39 roofing class) and insurers answer to state insurance departments. One of them can run the log, or several states can share one.
The honest catch
2030 is fast. Every insured home needs a certificate, and most older roofs would need an inspector’s visit. That costs time and money, and somebody has to pay. A slower path starts with sales and renewals and lets the deadline follow.
A certificate is only as honest as the roofer. The log doesn’t stop a roofer from signing a bad record. It makes the record public and tied to a license, so it can be caught and punished. License boards have to act on it.
It won’t fix wildfire insurance. California’s FAIR Plan, the insurer of last resort, grew to 698,307 policies by September 2026 because insurers pulled back from fire risk, not because roof records are messy. A certificate prices the roof, not the hillside around it.
Privacy. A public log of addresses and roof photos is a lot to publish. The log should hold the facts an insurer needs and a fingerprint of each photo; the photos themselves stay with the registry, shown to the owner, their insurer, and a buyer the owner lets in.
Insurers might still say no. A certificate tells an insurer the truth about a roof. It doesn’t make them like the answer.
The whole idea, in one line
Your browser doesn’t take a website’s word for who it is. Your insurer shouldn’t have to take a seller’s word, or a blurry photo, for your roof.