Solar power installations Often an insurance requirement Roof work without coverage

SCIOS scope 12 inspection of PV installations

Scope 12 covers solar power installations, including the peripheral equipment that feeds the generated power back into the grid, and for large-scale roofs it is almost always required by the insurer. Appfront builds the app your inspector uses on the roof to record what they see and measure, even where there is no signal, and in which the installation remains traceable per string and inverter.

What a scope 12 inspection involves

Scope 12 falls under the SCIOS sub-scheme for electrical equipment and concerns installations with photovoltaic panels and the associated peripheral equipment for generating electricity and feeding it back into the grid. So it covers the whole system: panels, DC-side cabling, inverters, the connection to the installation and the mounting on the roof.

The immediate trigger is usually not a legal obligation but a policy condition. After a series of fires, insurers have become stricter on large-scale PV, and require an inspection for new installations and at renewal. This means the client needs the report for their insurer, and the turnaround time between inspection and report counts commercially.

What makes this work technically difficult is the environment. The inspector is standing on a roof, often in the sun, wearing gloves and with no signal, and has to record what they see for each string. A 1,000-panel installation consists of dozens of strings that look alike. If you record this on paper and write it up later, you can no longer be sure at your desk which string a particular defect belonged to. That is the problem this software exists to solve.

How we build your scope 12 app

We start on the roof. A form that looks logical in an open-plan office proves unworkable up there, and then it ends up being filled in from memory afterwards.

1
Defining the installation structure

How do you record a PV installation: per inverter, per string, per panel group or per roof section? That choice determines whether you can trace defects later and whether a series over the years tells you anything. We also look at how you handle extensions, because PV roofs grow.

2
Detailing the inspection points

For each component, the points to be assessed: mounting and roof penetrations, condition of the cabling and connectors, earthing and surge protection, the inverters and their alerts, and the connection to the installation. For each point, we establish whether a measurement or a photo belongs with it.

3
Building in sprints

We work in sprints and start with the inspection itself. Your inspector takes an interim version onto a real roof early on; that yields more than any workshop, because that is where you find out that a drop-down menu cannot be operated with gloves on.

4
Report and handover

We tailor the report format to what your client has to submit to their insurer. Then comes a handover, with a trial run in which we walk through a completed file using the questions your certification body asks.

What the app actually does

Six components that make the difference between ticking off a list and a file in which a finding can be traced back to the right string.

Installation by inverter and string

The installation is structured down to string or panel group level, with a floor plan or roof layout where possible. A finding is attached to a specific component, so the engineer who repairs it knows where to go.

Identification on the roof

Codes on inverters and distribution boards open the right part of the file directly. With dozens of virtually identical strings, this is the only thing that reliably prevents mix-ups.

Thermography linked to the finding

Thermal images belong to the component where they were taken, not to the visit. A hot contact on a connector is only useful if you can later trace which connector it was and what the ambient temperature was at the time.

DC-side measurements

Insulation resistance, string voltages and currents, with the value that applies to that type of string. Deviations between strings that should be identical stand out immediately.

Findings with classification and remediation

Every finding gets a classification, a photo and a status, and stays open until it has been fixed and verified. At a re-inspection, the inspector can see what was still outstanding.

Report for the insurer

The report is generated from the recorded data, with the photos and measurements in the right place. Your client can forward it straight away, which significantly shortens the time between inspection and policy.

Who we build for

Four situations where this applies. The difference lies mainly in who pays for the inspection and who ultimately reads the report.

Certified inspection bodies

The core. If you also carry out scope 8 or 10, this is the same system with different forms; see scope 8.

PV installers with their own inspection service

You install the system and then inspect it periodically. If this connects to your existing quoting and installation software, the installation doesn't have to be entered twice.

Owners of multiple roofs

Commercial property, distribution centres and agricultural businesses with PV at multiple locations. Their need is a central overview: which roof was inspected when, and where is something still open.

Work that stems from a policy condition

The inspection is a condition for cover or renewal. What matters most here is that the report is demonstrable and on time, and that the remediation of findings has been recorded.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

What we use depends on how you work. For roof work, offline use matters most, along with readability in bright light and usability with gloves on. Those are design requirements, not details to sort out afterwards.

Native iOS and Android Offline-first storage Readable in bright sunlight Large touch targets for gloves QR labels on inverters Photos and thermal images attached to the component Node.js / Python / .NET PostgreSQL Roof layout or floor plan Measurements per string Signed PDF reporting Client portal per customer Audit logging Hosting in the EU

Why Appfront

We go up on the roof

Before we design anything, we join an inspection. The difference between an app that gets used and one that gets skipped lies in things you only notice on a roof.

Mix-ups are the real risk

With dozens of identical strings, the problem is not the measurement but knowing which string it belonged to. We solve that with identification on the spot, not with a longer checklist.

Turnaround time matters commercially

Your client is waiting for the report for their insurer. Completing it on site removes the week of write-up between inspection and delivery.

Alongside what already runs

Your scheduling and invoicing stay in place. We build the layer in between using integrations, so an inspection is never entered twice.

Security and privacy

The file contains little personal data, but it does record which inspector prepared which report and under which competence. That is traceable to an individual and touches on their certification, so we structure reports around the installation rather than the inspector.

The nature of the information weighs more heavily: open defects in a PV installation are sensitive towards your client's insurer and sometimes towards the installer who laid the roof. Access is therefore strictly per client, with a portal that only shows their own locations. A finalised report cannot be changed silently: corrections are visible as corrections and do not overwrite the original. Photos and thermal images are timestamped, because in the event of a fire this file becomes evidence, and then its reliability is what counts. How we handle security ourselves is set out in our information security policy; external reports go through our CVD policy.

Frequently asked questions about scope 12

Installations with photovoltaic panels and the associated peripheral equipment for generating electricity and feeding it back into the grid. That is the whole scope: panels and their mounting, the DC-side cabling, connectors, inverters, earthing and surge protection, and the connection to the electrical installation. Scope 12 falls under the SCIOS sub-scheme for electrical equipment, like scope 8 and scope 10.

Not as a general legal obligation. In practice, the requirement almost always comes from a policy condition: insurers have become stricter on large-scale PV and require an inspection on completion and periodically afterwards. That makes the requirement just as firm in practice, because without a report there is no cover. In addition, the usual obligations around a safe electrical installation continue to apply.

That depends on what the insurer has put in the policy and on the risk assessment of the installation; it is not a fixed period set by law. In practice we see an inspection on completion followed by a periodic cycle. Because the interval can differ per client, we make it configurable per installation rather than per customer or per type.

Yes, and here that is not an extra but the core. Large roofs rarely have coverage and the inspector cannot keep going back down. The app stores data locally, including photos and thermal images, and syncs as soon as there is a connection. We also pay attention to readability in bright sunlight and usability with gloves on; that sounds minor, but in practice it decides whether the app gets used.

Yes, and they should be attached to the component, not to the visit. A hot contact is only useful if you can later trace which connector or which string it concerned and what the conditions were. We therefore link every image to the installation component, with a timestamp and environmental data. For inspecting the fire risk of other electrical equipment there is scope 10.

Yes, and it's worth it because you then record the installation only once. If you already run software covering quote to installation, we build the inspection layer on top of it and pull the installation data from there. That not only saves data entry but also prevents two systems from holding a different picture of the same installation.

That is a trade-off, and more detail is not always better. Per inverter is often enough for a simple roof; per string is needed as soon as you want to be able to trace and compare deviations. Per panel is rarely workable, except for very large installations with panel-level monitoring. We advise based on your roofs and your inspection pace.

That depends on how detailed your installation model is, whether thermography and measurements are added, and whether you need a client portal. The inspection app itself is usually quick to get working; the portal and integrations cost more. We provide a well-founded estimate after the discovery phase, once we know how your inspectors work.

Want to build a scope 12 inspection app?

Tell us how many installations you inspect and how the report is currently produced, and we'll help you think through the per-string structure, the thermography and the turnaround time to your client. We build this as a standalone app and as part of a broader project for custom software or an app.

Edit content