Solar Panel Removal Inventory: What to Record Before Roof Work

Use this record alongside the project plan

The overall roof-and-solar plan assigns crews, dates and approvals. This inventory answers a narrower question: what equipment was present, where did it go and what came back? DOE describes roof replacement as a possible occasion for removing and reconsidering an existing system. [2] Do not turn a removal appointment into an assumed authorization to replace equipment. Keep an equipment-owner approval, if required by the actual agreement, beside the accepted scope.

Start the file before the removal crew arrives. Name the property, owner contact, removal contractor, roofing contractor and person accepting stored equipment. Write down which documents are missing. An incomplete original plan is a reason to record uncertainty, not to copy the panel count from a sales proposal and treat it as a field inventory.

Create one row for each identifiable item

Use these worksheet columns: temporary inventory ID; component type; make and model; serial number if available; original roof position; photograph reference; observed condition; removal date; storage location; and final disposition. Keep module identities distinct from microinverter or optimizer identities. Ask the contractor which paired components will stay together and how that relationship will be recorded.

DOE’s O&M guidance includes equipment identifiers and location diagrams in the system record. [1] Homeowners can collect contracts, monitoring exports and safely accessible labels. Rooftop labeling, electrical identification and condition assessment belong to qualified personnel. Do not climb the roof, unplug connectors or open covers to complete a worksheet. A blank serial field should say “not yet verified,” with a named person responsible for resolving it.

Separate condition from conclusions about blame

A useful condition entry states what was observed and when: a photograph shows a frame mark, a monitoring export shows an existing alert, or a technician reports a damaged connector. It should not say that a party caused damage simply because the condition was first noticed during removal. Preserve the original photograph or report, including its date and reference, instead of replacing it with a retouched image or summary.

Create an exception list for missing labels, pre-existing faults, uncertain component counts and items proposed for replacement. Ask who will review each exception, whether work can proceed around it and which decision requires owner authorization. Keep a proposed remedy separate from a completed remedy.

Make custody a dated handoff

Record each transfer as a separate event: who released the equipment, who received it, the date, location, counted items and unresolved exceptions. The contractor should specify storage and handling requirements appropriate to the equipment. This worksheet is not a packaging instruction. Ask what happens if roofing is delayed, storage must move or an item cannot be found at reset.

For a clearly hypothetical 24-module system, the removal list might identify 24 modules, while the return list shows 23 original modules and one authorized replacement. A total of 24 on both sheets would hide the substitution. The useful reconciliation identifies the removed serial, replacement model and serial, approval reference and disposition of the old component. It establishes a traceable change without making a warranty determination.

Close every row before closing the inventory

Use a final disposition such as reinstalled, replaced under an approved change, retained by owner, returned to supplier or awaiting a documented decision. Do not mark an item “complete” merely because the truck left. Reconcile the final equipment list with the contractor’s as-built record and monitoring map. If one row remains unresolved, record a next action, responsible party and agreed follow-up date.

Read the actual product and workmanship terms when a claim is involved. The FTC recommends retaining purchase evidence and reviewing written coverage. [3] An inventory supports a factual discussion but does not itself establish warranty coverage, insurance payment or responsibility for every cost.

Send a compact packet for a useful service review

Provide the address, accepted roof scope, planned dates, panel count, equipment list, known faults and inventory exceptions. Share monitoring access through the provider’s approved access process, not by putting passwords in a general form. Keep the original and final records in the same folder with distinct dates.

For a Tampa Bay or Central Florida property, Origin can review the requested work and confirm coverage, supported equipment and scope for the address. This article does not promise an installation date or authorize work. If the inventory is missing after completed roof work, request the removal and return records first; a fresh field visit may be needed to establish facts that photographs alone cannot recover.

Primary sources

1. U.S. Department of Energy FEMP: Optimizing Solar Photovoltaic Performance for Longevity

   Reviewed October 14, 2026. Federal O&M guidance supports equipment identification, location records, maintenance logs and reacceptance testing; the homeowner worksheets here are original planning examples.

2. U.S. Department of Energy: Should I Replace My Rooftop Solar System?

   Reviewed October 14, 2026. Roof replacement can require solar removal and creates a decision about reusing or replacing equipment; it does not prescribe a particular home’s scope.

3. Federal Trade Commission: Warranties

   Reviewed October 14, 2026. Read the written coverage and remedy and retain purchase records. No particular manufacturer claim or workmanship coverage is promised.

Planning examples and questions are Origin’s editorial guidance, not a property-specific diagnosis, engineering design, tax determination or promise of savings. Manufacturer and utility references do not imply an affiliation with Origin.

Related guidance

• Plan the complete removal and roofing handoff
• Reconcile the monitoring map after reset
• Review removal and reinstall service
• Request existing-system service