The Installed-System Record: Materials and Components Filed by Job for Future Repairs

Every question about a roof gets harder with time. Three years after the build, a leak call, a small repair, or a warranty question all start with the same sentence: "What is actually up there?" If the answer has to be reconstructed — from the original proposal, a supplier invoice someone half-remembers, and a crew lead who has since left — the company pays for the guessing in mismatched materials, a second trip, and a claim conversation that starts on the back foot. The installed-system record is the closeout habit that prevents it: one short record, filed by job before the job closes, of the materials and components that actually went on the roof. Not the plan. The roof.

Record what was installed, not what was proposed

The signed estimate is a plan written before tear-off. The finished roof is that plan plus everything the job itself changed: the product substitution agreed when the original line was unavailable, the extra decking sheets approved by change order, the ventilation correction added once the attic was open, the flashing that turned out to need replacing rather than reusing. Each of those changes may exist somewhere — on a change order, in a text thread, in the crew lead's head — but unless someone gathers them into one as-installed record, the file your office keeps describes a roof that was never quite built. That is why ranking closeout and handover guidance repeats the same instruction: record the system and products actually used, and keep the approved changes together with the final scope. The estimate stays in the file too — it is the pricing record — but it should not be the only description of the roof.

What the record should contain

• The main covering: manufacturer, product or line name, color, and system type — two roofs that look alike from the street can carry very different products, specifications, and warranty terms
• The underlayment: what type went on, and where each type was used — which areas received ice-and-water protection (eaves, valleys, penetrations) and which received the field underlayment
• Decking: how many sheets or boards were replaced and where, matching the photographed count on the approved change order — the number our change-order guide has the crew and the customer agree on at tear-off
• Metals and flashing: drip edge, valley metal, and flashing — what was replaced new, and just as important, what was inspected and reused
• Ventilation as installed: the intake and exhaust products fitted, baffles added, and any fan rerouted outdoors — the finished state of the scope our guide to ventilation corrections as estimate scope prices before the job
• The smaller components that define the system where they matter: fastener and sealant or adhesive products used at details, recorded in plain words rather than left to assumption
• Each roof section recorded separately when it differs: a slope, addition, or section roofed with a different product or at a different time gets its own lines, so a later repair is matched to the section it is actually on
• The dates and the hands: the installation or completion date the warranty clock runs from, and which crew installed it
• Product evidence attached: a photo of the packaging or label, or the product literature, filed with the record — one label photo taken on delivery day settles arguments memory cannot

Capture it during the build, not at closeout from memory

The record takes minutes if it is assembled while the job is open and hours if it is reconstructed at closeout. The raw material is already passing through the crew's hands: packaging and labels are on site on delivery and install days, the decking count is photographed during tear-off because the change order needs it, and a substitution is a decision made on a specific day for a specific reason. The routine is simply to write each of those down on the job record the day it happens — the same capture discipline behind the during set in our field photo checklist — and then to check the assembled record once, against the roof, at the final walkthrough. A record written from the truck at closeout, from memory, will quietly copy the estimate — which is the one document it exists to correct.

The questions this record answers later

Give the customer a copy; keep yours findable by job

The record belongs in the closeout package handed over at the final walkthrough: the customer holds what was installed on their home, and your office keeps the same record filed with the job — alongside the completion photos, the warranty paperwork, and the final invoice. Keep it for the life of the roof, and file it so it can be found the way the future question will arrive: by property address and job, retrievable by whoever answers the phone that day, not by which crew lead ran the job or whose inbox the delivery photos landed in. Roofs outlast crew turnover, office moves, and software changes; the record only earns its keep if it survives all three.

Where GableFlow fits — and the honest limit

GableFlow does not track inventory, and it does not fill this record in automatically — no honest tool can know a substitution was made until a person writes it down. What GableFlow holds is the one place the record lives: the job record carrying the branded estimate and its approved changes, the before/during/after photos as a captioned photo report, documents, invoices and payments, and the job's stage from Lead → Prospect → Approved → Completed → Invoiced → Closed, visible to the whole team under roles for owner, admin, manager, and user. That gives the installed-system record a permanent home next to everything it will later be checked against, instead of a spreadsheet on one machine. Build the record for one real closing during the 7-day free trial and see how long it actually takes. See GableFlow's features for how the job record holds estimates, photo reports, documents, and invoicing together, or check the flat $40/month pricing — every feature included, unlimited seats, no per-seat fees.