Solar Inspection After a Storm, Hail, or Lightning Event

A solar inspection after a storm should begin with people, not panels. Fire, smoke, arcing, a chemical odor, a hot or deformed battery, downed conductors, floodwater near electrical equipment, structural movement, or an unstable roof is an emergency boundary. Keep people away and call 911, the fire department, and the serving utility as appropriate. Do not use a website form as an emergency channel.

Once public-safety officials have excluded immediate danger, the homeowner’s safe job is limited: document the event from the ground, save monitoring evidence, preserve records, notify the correct contract and insurance parties, and arrange qualified inspection. Do not climb onto the roof, touch wet or damaged equipment, open an enclosure, disconnect a solar connector, clear debris from beneath the array, or try an unfamiliar shutdown sequence.

Teamsun publishes a solar maintenance and repair service page, but the public record reviewed for this guide does not verify emergency response, storm-inspection capacity, repair coverage for a particular system, insurer relationships, response times, or warranty authority. After the site is safe, owners in Connecticut, Massachusetts, or Rhode Island may send the evidence packet to Teamsun for a scope review. That inquiry is not an emergency dispatch or a promise that Teamsun can inspect or repair the system.

The short answer: Treat the array, roof, service equipment, and battery as one affected site. Establish a time-stamped pre-storm baseline, record safe ground-level observations and portal screenshots, and get a written inspection scope. A normal-looking roof or a green monitoring screen does not clear hidden cell cracks, loose attachments, wet wiring, insulation damage, surge damage, or a compromised battery.

Use this immediate post-storm triage tree

The U.S. Department of Energy warns that damaged PV equipment can present electrical and fire hazards, while OSHA identifies shock and arc-flash hazards in PV work. Solar modules can produce electricity in daylight even when utility power is out. A rapid-shutdown control or disconnect can reduce hazards in a designed zone, but it does not justify treating every conductor or internal component as de-energized (DOE fire-safety guide; OSHA solar electrical hazards).

Gate	What you observe without approaching	What to do
RED — emergency	Fire, smoke, arcing, sparking, electrical buzzing near damage, downed wire, flooded electrical equipment, major roof/structure movement, battery heat/swelling/odor, or a person in danger	Move away. Keep others out. Call 911/fire and the serving utility as appropriate. Tell responders the property has PV and whether a battery is present. Do not operate equipment.
RED — unsafe access	Tree on the array, loose module or roofing material, broken glass overhead, exposed conductor, standing water near electrical equipment, unstable canopy, or debris trapped under modules	Establish distance. Do not climb, touch, move, tarp, sweep, or retrieve an item. Have the authority or qualified party control access.
YELLOW — no immediate danger, condition uncertain	Inverter or battery alert, missing monitoring data, new production change, visible crack from the ground, roof leak, displaced flashing, fallen branch nearby, utility outage, or unexplained shutdown	Preserve screenshots and photos. Avoid repeated resets. Contact the system owner, installer/service party, insurer if applicable, and utility/AHJ when required. Keep the system in the state directed by the proper authority.
GREEN — documentation only	No hazard observed, utility service normal, and no visible or portal anomaly	Record the event and baseline anyway. Review the event severity and equipment exposure with a qualified party when hail, lightning, flooding, windborne debris, roof damage, or nearby strikes justify it. “No alarm” is not an inspection result.

FEMA advises people to assume downed lines may be energized, avoid wet electrical equipment, and wait for officials to say reentry is safe. If water surrounds equipment, do not enter it to reach a switch (FEMA flood-return safety). Product instructions reinforce the boundary: Tesla’s module instructions prohibit touching live parts or disconnecting connectors under load, and its Powerwall emergency guidance says to stay out of water around a flooded or submerged unit (Tesla module safety; Tesla Powerwall emergency guidance). Those are product-specific examples, not generic operating instructions for another brand.

Build a time-stamped event and evidence packet

Evidence should be captured before alteration only when it is safe. Life safety and reasonable emergency mitigation come first. FEMA and the National Association of Insurance Commissioners recommend documenting damage before cleanup where practical and keeping receipts, but neither source guarantees that a particular policy covers solar work (FEMA damage documentation; NAIC claims guidance).

Create one folder and one event log. Use blanks instead of guesses:

Record	Owner entry	Source or attachment
Property and utility account	___	Latest electric bill
Storm date/time and time zone	___	Official alert/weather record if available
Event types	Hail / wind / lightning / flood / tree / outage / other	Do not estimate hail size from memory as fact
First safety observation	___	Ground-level photo/video only
911/fire/utility contacts and incident numbers	___	Call or ticket record
Utility outage start/restoration	___	Utility outage notice
System operating state	Running / off / unknown / authority-directed state	Who directed it and when
Monitoring status before, during, after	___	Original screenshots and exported data
Pre-storm production baseline	___	Same-season daily/monthly or circuit-level export
Equipment identity	___	Module, inverter, optimizer/microinverter, gateway, battery, racking models/serials
Ownership and service parties	Cash / loan / lease / PPA; installer; manufacturer	Contracts and warranties
Roof/structure observations	___	Ground photos; roofer/engineer report later
Insurance notice	Carrier, claim number, adjuster, restrictions	Policy/claim correspondence—not a coverage assumption
Every site visit or alteration	Person, license/company, time, purpose, component touched	Work order and before/after photos

Keep original files, not only annotated screenshots. Save the monitoring system’s time zone, device status, alert codes, per-device layout if available, and the utility outage window. A blank data interval may be a communications failure; flat production may reflect grid loss, a tripped device, shade or snow, damaged hardware, or a reporting issue. Do not diagnose the cause from one graph.

Record serial numbers from existing paperwork or safe, accessible labels. Do not lean over damaged equipment or open covers to obtain them. Preserve removed parts until the insurer, manufacturer, owner, and contractor give written disposition instructions. Track who took each item and why; that chain of custody can matter to a warranty or claim review.

Separate hail, wind, lightning, flood, debris, outage, and battery pathways

One storm can create several failure paths. The inspection should not stop after finding the first visible defect.

Exposure	Possible evidence	What remains unknown	Qualified inspection focus
Hail	Broken glass, impact marks, displaced frame, roof/gutter damage, new device mismatch	Cell microcracks can exist without broken glass or immediate app alarm	Module/glass/frame visual, electrical comparison, and event-specific IR or electroluminescence only when justified and performed under a defined procedure
Wind	Shifted module, lifted roof material, bent conduit, loose-looking skirt, displaced debris	Attachment, flashing, sheathing, rafter, fastener, wire-management, and torque condition	Roof and structure plus racking, attachments, wiring, setbacks, and weatherproofing
Lightning or surge	Inverter/gateway fault, failed communications, tripped protection, scorch/odor, sudden multi-device loss	Direct strike versus nearby induced surge versus utility event; internal or latent damage	Service, grounding/bonding, surge devices, inverter, optimizers/microinverters, gateway, network, and battery per exact manuals
Flood or driven water	Waterline, wet enclosure, conduit water, staining, corrosion, loss of communications	Internal wetting, insulation damage, contaminated components, water transported through conduit	Electrical and structural assessment before energization; manufacturer disposition for submerged/wet equipment
Tree or flying debris	Broken glass, bent frame, damaged roof, cable contact, shaded/buried module	Hidden roof/attachment damage and energized conductors under debris	Controlled debris removal, roof/structure, full affected circuit and component inspection
Utility outage/voltage event	Grid code, shutdown during outage, restart problem	Normal anti-islanding response versus equipment or service damage	Confirm utility status first, then service voltage, settings, event logs, and approved return path
Battery exposure	Heat, swelling, smoke, odor, fluid, impact, water, enclosure or communications alert	Internal cell condition and safe transport/disposition	Fire/authority boundary first; exact manufacturer emergency and service procedure

DOE’s hail guidance says hail may crack cells without breaking front glass and calls for visual and electrical inspection before return to service when visible damage exists (DOE hail-damage mitigation). DOE’s broader weather guide discusses wind-related flexing and attachment damage and assigns advanced tests to trained personnel (DOE PV weather-vulnerability guide). NREL fleet research likewise notes that extreme weather can create hidden cell cracks; the practical conclusion is not that every storm caused damage, but that appearance alone cannot resolve a credible exposure (NREL extreme-weather research).

Flooding needs its own hold. DOE guidance for federal PV sites says total submersion requires replacement of affected PV components and warns that conduit can transport water (DOE flood-damage guidance). For a home, the manufacturer, licensed electrical professional, insurer where involved, and authority having jurisdiction should document exact disposition. A homeowner should never “dry it out and try it.”

Lightning evidence is also not binary. SolarEdge says a nearby lightning or grid event can affect power electronics and communications, and that surge protection reduces risk but cannot protect against every event, especially a direct strike (SolarEdge surge technical note). An intact surge device, normal production total, or working app therefore does not prove every circuit and communication path is healthy.

Reconcile the insurer, system owner, installer, manufacturer, and contractor

The party who sold the system may not own it, service it, approve a warranty claim, perform roof work, decide insurance coverage, or authorize reconnection. Fill this responsibility map before approving permanent work:

Decision	Named party	Written evidence required
Equipment owner and authority to approve work	___	Purchase, lease, or PPA agreement; transfer documents
Emergency site control	___	Fire/utility/AHJ direction or incident record
Insurance coverage decision	___	Insurer/adjuster communication and policy—not contractor opinion
Temporary mitigation approval	___	Written insurer/owner direction where feasible and safe
Product warranty diagnosis/RMA	___	Exact manufacturer claim procedure, authorization, exclusions
Workmanship or roof-penetration claim	___	Contract, warranty owner, notice deadline, inspection rule
Roof/structure assessment	___	Roofer/engineer scope and credentials applicable to work
Solar electrical diagnosis/repair	___	Contractor/electrician scope and applicable license
Utility or municipal approval	___	Written classification, permit/interconnection requirement
Monitoring administration and data	___	Portal owner, site-transfer permission, export and retention
Removed-equipment custody	___	Claim/RMA instructions and signed receipt

Contact the insurer before permanent repair when a claim may exist, unless urgent action is necessary to prevent injury or additional damage. Save receipts and document why temporary work was necessary. Do not let a contractor promise coverage, negotiate a claim outside lawful authority, demand assignment of a check, or pressure you into a same-day contract. The FTC says to verify licensing and insurance, insist on a written contract, and remember that a contractor does not decide what an insurer will pay (FTC post-disaster scam guidance). Connecticut’s July 2026 storm-scam alert gives similar advice about registration, written terms, and utility-worker identification (Connecticut DCP storm alert).

For a leased or PPA system, the contract owner may control inspections, approved contractors, insurance notices, repairs, monitoring, and equipment removal. Unauthorized third-party work can complicate obligations. That does not override an emergency order; it means the contract path should be reconciled as soon as safety permits.

Require a written, qualified inspection scope

“Inspect the solar” is not a test plan. The proposal or work order should say which layers are included, what methods will be used, what conditions make results valid, and what deliverable the homeowner receives.

1. Site and safety control: access boundary, utility status, roof condition, energized-work assumptions, fall protection, battery condition, and stop-work triggers.
2. Roof and structure: roof covering, penetrations, flashing, attachments, racking alignment, fasteners, uplift evidence, drainage, deck/rafter concerns, and whether a structural engineer is needed. FEMA wind guidance treats PV and rooftop equipment as wind-loaded building components, not isolated appliances (FEMA windstorm resilience).
3. Module and array: exact module map; glass, frame, backsheet where accessible, junction boxes, connectors, wire management, grounding/bonding, displaced components, and affected-area boundaries.
4. Electrical system: service equipment, disconnects, conductors, raceways, overcurrent protection, grounding/bonding, rapid-shutdown equipment, signs of water/heat/arcing, and comparison with the approved one-line.
5. Power electronics and communications: inverter, optimizer/microinverter, gateway, meter/CT orientation, event logs, firmware/context, network and cloud reporting. A portal symptom must be reconciled with physical and electrical findings.
6. Storage and backup: battery enclosure and mounting, controls, gateway/transfer hardware, protected-load topology, event logs, manufacturer escalation, and controlled functional tests only after safety clearance.
7. Performance baseline: pre-event and post-event data compared over like weather, season, operating state, curtailment, shade/snow, and outage conditions. State the uncertainty; do not turn one daily total into a damage verdict.
8. Findings package: annotated component map, photos, measurements and test conditions, observed/non-observed/untested status, safety disposition, repair alternatives, notification needs, and acceptance criteria.

Advanced testing is not a homeowner checklist. Insulation-resistance testing can apply test voltage to circuits and may require isolation under manufacturer procedures. Current-voltage tracing exposes workers to live PV circuits. Infrared findings depend on irradiance, load, angle, weather, access, and interpretation. Electroluminescence is specialized and may not be proportionate for every residential claim. The qualified party should explain why a test is needed, who is competent to perform it, how equipment is protected, and what threshold controls the decision. NFPA 70E provides the electrical safe-work framework, while NFPA 70B addresses maintenance programs; neither turns a named instrument into proof by itself (NFPA 70E, 2024; NFPA 70B, 2026 listing).

Define shutdown and re-energization authority before testing

A generic internet shutdown sequence is unsafe because system architectures differ. The correct plan starts with the as-built one-line, exact equipment manuals, ownership contract, utility status, and direction from the fire department, AHJ, utility, manufacturer, or qualified contractor as applicable.

Use a written control log:

Control point	Entry
Who ordered or performed shutdown?	___
Exact devices operated and positions	___
What may remain energized in daylight or from storage/grid?	___
Lockout/tagout or site-control owner	___
Required inspection/tests before return	___
Utility/AHJ/manufacturer approvals required	___
Who is authorized to re-energize?	___
Staged restart order from exact manual/one-line	___
Observations and readings at each stage	___
Stop condition and safe fallback state	___

Do not repeatedly reset breakers, cycle an inverter, silence an unexplained battery alert, or operate a rapid-shutdown device to “see if it clears.” A reset can erase useful event context, reapply energy to a damaged component, or produce a false sense of resolution. If responders shut down or isolate the site, only the authority they designate should release it.

Re-energization is an acceptance test, not a single switch movement. It should verify safe physical condition, electrical readings, protective functions, expected inverter and battery state, communications, monitoring, utility interaction, and production behavior under documented conditions. Any abnormal heat, odor, sound, fault, unexpected voltage/current, loss of communication, or inconsistent device count should trigger the written stop condition.

Choose repair, replacement, or monitoring from evidence

The inspector should not jump from “storm occurred” to a whole-system replacement, nor from “the app is green” to no action.

Path	Minimum support	Important unresolved items
Repair	Damage is bounded; retained components tested as appropriate; compatible parts and instructions exist; roof/electrical integrity is documented	Labor, permits, warranty effects, weatherproofing, monitoring recommissioning, downtime
Replace affected equipment	Exact damaged component and affected circuit are identified; replacement compatibility and design impacts are documented	Module electrical/mechanical match, inverter/optimizer compatibility, code changes, utility amendment, color/appearance
Partial or full repower	Legacy incompatibility, unavailable parts, broad damage, or redesign is demonstrated in writing	Retained-equipment warranty, new one-line, program/tariff treatment, tax and ownership boundaries
Monitor under a written plan	No active safety defect; baseline and initial tests support operation; uncertainty is explicit	Measurement interval, thresholds, responsible party, follow-up date, escalation trigger
Keep shut down/defer	Safe isolation state is documented and the next authority/action is named	Lost production, battery state-of-charge care, roof protection, deadlines, site security

A monitoring plan must name the metric, baseline, comparison window, weather/curtailment adjustments, alert threshold, review date, and person responsible. “Watch the app” is not enough. Similarly, replacement scope must list every retained, removed, and added model, not merely “replace damaged panels.”

Cost should be separated into diagnosis, access/lift or roof work, engineering, equipment, electrical labor, roofing, permits, utility work, monitoring transfer, commissioning, disposal/claim custody, and follow-up. No current, audited Teamsun storm-inspection or repair pricing was available for this guide, so no company price or response-time range is presented.

Route Connecticut, Massachusetts, and Rhode Island decisions correctly

Teamsun’s verified geographic context for this page is Connecticut, Massachusetts, and Rhode Island. The emergency route is always site-specific: 911/fire for immediate danger and the serving utility for downed lines, outages, or utility equipment. Material repair, equipment substitution, service work, relocation, or system redesign may also require municipal permits, an electrical inspector/AHJ review, and a utility interconnection amendment. Do not assume every like-for-like part swap has the same path; obtain the classification in writing.

State	Emergency and outage route	Repair/return-to-service questions
Connecticut	911/fire and the serving utility; use the correct Eversource or United Illuminating outage channel	Ask the local building/electrical official and Eversource or UI whether the exact retained/removed/added equipment, export setting, service work, meter work, or design change requires a permit, interconnection amendment, inspection, or new authorization (Eversource CT interconnection; UI interconnection process).
Massachusetts	Call 911 for downed lines or emergency; report the outage to the serving electric company (Massachusetts outage safety)	Reconcile the local Inspector of Wires/AHJ and utility. Massachusetts says customers need an executed interconnection agreement and authorization to connect before connection; ask how that applies to the exact storm repair or reconfiguration (Massachusetts interconnection guidance).
Rhode Island	911/fire for danger and Rhode Island Energy for outage/downed-line reporting; stay away from lines (Rhode Island Energy storm safety)	Ask the local AHJ and Rhode Island Energy to classify equipment, service, meter, export, and configuration changes under current electric specifications/interconnection rules (Rhode Island Energy electric specifications).

Record the name, title, date, question asked, answer, application/permit number, and document revision. “The contractor said no paperwork” is not a complete approval record.

Close out the storm event with acceptance evidence

Do not close the claim, service ticket, or work order merely because energy production resumed. Request a closeout package containing:

• the final cause and scope statement, including uncertainty;
• the inspected area and explicit uninspected areas;
• roof/structural and electrical findings from the responsible disciplines;
• retained, removed, and added equipment with models and serials;
• test method, conditions, readings, pass criteria, and instrument identity where relevant;
• before/after photos and updated array map;
• permits, inspections, utility correspondence, and permission/authorization required for the work;
• manufacturer ticket, RMA, warranty decision, and excluded labor or shipping terms;
• monitoring owner/admin, device count, layout, communications, and data continuity;
• removed-equipment chain of custody and disposal authorization;
• staged re-energization and functional test record;
• post-repair production baseline and a scheduled review date;
• workmanship, roof-penetration, equipment, and service responsibility documents; and
• invoices separated by diagnostic, equipment, electrical, roofing, engineering, permit, monitoring, and other scopes.

If the array was removed for roof work, reconcile the original and final attachment plan, flashing/weatherproofing, conductor routing, grounding/bonding, one-line, module map, and warranty responsibility. The dedicated solar roof-leak guide covers leak triage and responsibility in more depth; this page owns the storm evidence and system-return decision.

After immediate danger is excluded and the packet is assembled, you can request a non-emergency scope review. Include only photos obtained safely. Teamsun availability, exact equipment support, inspection scope, trade coordination, price, and schedule must all be confirmed in writing for the property.

Use the stop, pause, or proceed gate

Verdict	Conditions	Next action
STOP	Active fire/smoke/arcing; downed conductor; flooded equipment; unstable roof/structure; loose overhead component; battery heat/swelling/odor; exposed live part; or official isolation	Keep distance. Call 911/fire/utility/AHJ as appropriate. Do not document at the cost of safety and do not re-energize.
PAUSE	Immediate danger excluded, but ownership, claim authority, roof safety, inspection scope, equipment identity, qualified test plan, permit/utility route, replacement compatibility, or return authority is missing	Preserve safe evidence. Obtain written decisions and qualified findings. Keep the system in the authority-directed safe state.
PROCEED	Immediate hazards cleared; responsible parties reconciled; qualified inspection completed; repair/monitor scope supported; approvals recorded; re-energization and acceptance tests passed; follow-up assigned	Close out with the complete record and monitor against the new documented baseline.

Proceed does not mean “nothing happened.” It means the evidence supports a controlled operating state and names the future trigger for review.

Frequently asked questions about solar inspection after a storm

Should I climb onto the roof to photograph hail damage?

No. Storm damage can make a roof, ladder path, module, attachment, or conductor unsafe. Take only ground-level photos from a safe location after immediate danger is excluded. A qualified roof/solar party should control roof access.

Can I touch a cracked solar panel if the inverter is off?

No. Daylight can energize PV conductors, and “off” does not establish that every component is electrically safe. Keep away, prevent access, and let the proper responder or qualified worker control the hazard.

Does normal production prove hail caused no damage?

No. A production screen is useful evidence, but cell cracks, attachment damage, insulation problems, or localized defects may not create an immediate whole-system alarm. Inspection depth should match credible exposure and observed evidence.

Does a monitoring alert prove storm damage?

No. An alert can reflect a utility outage, communications failure, service-voltage issue, device fault, configuration, or damage. Preserve the exact code and time rather than repeatedly resetting it.

Who should shut down the solar system after a storm?

Follow the direction of 911/fire, the utility, AHJ, manufacturer, system owner, and qualified contractor as applicable to the actual hazard and architecture. Do not copy a different product’s online shutdown sequence or operate unfamiliar controls.

Will homeowners insurance pay for a solar storm inspection or repair?

Only the insurer and policy/claim process can decide coverage, limits, exclusions, deductibles, valuation, and required documentation. Ask before permanent work when feasible, preserve safe evidence, and do not rely on a contractor’s coverage promise.

Do microcracks require electroluminescence testing?

Not automatically. EL can reveal cell damage, but access, cost, test setup, event evidence, insurer/manufacturer requirements, and the decision it would change matter. A qualified inspector should justify EL, IR, IV-curve, or other testing in a written plan.

Can I remove branches or debris caught under the panels?

No. Debris may hide damaged glass, conductors, unstable racking, or roof damage. It can shift while being moved. Establish distance and have a qualified party plan controlled removal.

Can a lightning surge damage monitoring but leave production running?

Yes, communications and power paths are different, but the symptom alone does not identify cause or scope. Preserve event logs, utility timing, gateway status, and inverter/device data for qualified diagnosis.

What if the battery was exposed to floodwater?

Stay out of the water, keep others away, and contact emergency services when there is heat, smoke, odor, deformation, or other danger. Follow the exact manufacturer’s emergency path and authority direction. Do not touch, dry, restart, open, or transport the unit yourself.

Does every storm repair require a new interconnection application?

Not necessarily. Requirements depend on the utility, municipality, exact equipment change, electrical scope, export/control settings, service or meter work, and existing approval. Ask the AHJ and utility to classify the specific retained/removed/added scope in writing.

When is monitoring alone a reasonable outcome?

Only after active safety concerns are excluded and qualified findings support operation. The plan should define the baseline, metric, uncertainty, alert threshold, follow-up date, and responsible reviewer. “No visible damage” is not a monitoring plan.

Method and evidence boundary

This guide was researched and checked on August 10, 2026. It prioritizes OSHA, DOE, FEMA, NFPA, state, utility, and exact manufacturer safety material. Search results and homeowner forums were reviewed to identify recurring buyer questions—especially whether an app or naked-eye check is enough, who pays for diagnosis, and whether a homeowner should climb or improvise a repair. Forum anecdotes and commercial checklists were not used as proof of safety, damage, coverage, or system performance.

No first-party Teamsun emergency protocol, storm ticket sample, technician credential roster, equipment authorization list, inspection method, insurer agreement, rate card, response-time record, storm outcome, or warranty-claim dataset was available. This article therefore provides a buyer-controlled evidence and decision framework, not a representation that Teamsun offers a particular emergency, inspection, repair, insurance, or warranty service.