Solar Energy Incident Report

---
name: solar-energy-incident-report
description: |
  Respond to, record and learn from incidents involving homeowners, businesses and energy companies in rooftops, solar farms and offices.
  TRIGGERS - Use when a solar PV engineer needs a incident reporting & response for homeowners, businesses and energy companies in rooftops, solar farms and offices.
category: Solar Energy
license: MIT
version: 1.0
---
# Incident Reporting & Response — Solar Energy

Respond to, record and learn from incidents involving homeowners, businesses and energy companies in rooftops, solar farms and offices. The deliverable is a factual incident report and a lessons-learned action list.
This skill is written for a solar PV engineer working with homeowners, businesses and energy companies in rooftops, solar farms and offices.

## When to use
- You are a solar PV engineer preparing, delivering or reviewing this part of your work in rooftops, solar farms and offices.
- You need a defensible, repeatable approach that produces a factual incident report and a lessons-learned action list.
- A colleague, auditor or client asks how this was done and what evidence supports it.

## Key Concepts
| Term | Meaning |
|------|---------|
| Inverter | the device converting panel DC output to usable AC |
| Performance ratio | actual output compared with theoretical maximum |
| Feed-in | electricity exported to the grid |

## Workflow
1. **Step 1** - Make the situation safe first; attend to people before paperwork, and escalate if falls from roofs is still live
2. **Step 2** - Record facts while they are fresh: what happened, when, who was involved, what was observed — in system designs
3. **Step 3** - Notify the people and bodies who must know, within the timeframes that apply in rooftops, solar farms and offices
4. **Step 4** - Support those affected, including honest communication with homeowners, businesses and energy companies about what happened and what happens next
5. **Step 5** - Analyse causes without blame, agree preventive actions with owners and dates, and track them to closure

## Profession-Specific Components
| Component | Details for Solar Energy |
|-----------|-------------------------------|
| Core documentation | system designs; performance reports; installation certificates; maintenance logs |
| Core tools & equipment | PV panels and inverters; monitoring platforms; testing instruments; scaffolding |
| People involved | homeowners, businesses and energy companies; the solar PV engineer; colleagues and other services in rooftops, solar farms and offices |
| Primary record | system designs — keep it current, dated and attributable |

## Output Format
**Context:** [Situation in rooftops, solar farms and offices] | **Objective:** [What this must achieve] | **Audience:** [homeowners, businesses and energy companies and other stakeholders]

The finished output is a factual incident report and a lessons-learned action list, structured as:
1. Summary of position and evidence
2. Detail, following the workflow above
3. Decisions, actions, owners and dates
4. Review point and escalation route

### Action Plan
1. **Immediate:** Confirm scope, consent and the evidence available in system designs.
2. **Short-term:** Complete the workflow steps and record outcomes against system performance ratio.
3. **Medium-term:** Review results, close actions, and update local procedures in rooftops, solar farms and offices.

## Success Metrics
| Metric | Target | Method |
|--------|--------|--------|
| system performance ratio | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |
| installation times | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |
| fault response | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |
| customer savings reported | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |

## Guardrails & Quality Checks
- Never let this happen: falls from roofs.
- Never let this happen: electrical faults.
- Never let this happen: underperforming systems unnoticed.
- Work only within the competence and authority of a solar PV engineer; escalate or refer anything beyond it.
- Record facts and observations, not speculation, and keep records confidential to rooftops, solar farms and offices's rules.
- Verify names, dates, figures and measurements twice before anything is issued or signed off.
- Use only real, verified information from the case in hand — never invent results, credentials or evidence.

## Example (illustrative)
A solar PV engineer in rooftops, solar farms and offices applies this workflow for homeowners, businesses and energy companies: they open
system designs, work through the five steps using PV panels and inverters, and close by recording
the outcome against system performance ratio and agreeing the next review date. (Illustrative example only —
replace with the real details of the case in hand.)