Electrical equipment sub-scheme Initial special inspection to NEN 1010 File per installation

SCIOS scope 8 inspection file

Scope 8 covers the fixed electrical installation, with an initial special inspection based on NEN 1010 and periodic inspections after that. Appfront builds the software in which your inspector records those measurements and findings on site, and in which the installation data from the initial inspection is still available years later at the periodic inspection.

What a scope 8 file must contain

Scope 8 falls under the SCIOS electrical equipment sub-scheme and focuses on the fixed electrical installation. The initial special inspection assesses the installation after completion or before it is put into use, and is based on NEN 1010, the standard for low-voltage installations, in particular the part on inspection. Periodic inspections follow, with the baseline from the initial inspection remaining the reference point.

What sets a scope 8 file apart from a general inspection is that it is built around the installation rather than the visit. Distribution boards, circuits, earthing provisions and protective devices each get their own place, along with the measurements that belong to them: insulation resistance, earth resistance, continuity, disconnection times. At the next inspection you want to be able to compare that series, because a value that slowly drops says more than a single measurement on its own.

In practice, many inspectors work with a template in a spreadsheet or with a measuring instrument that produces its own export. The back office then combines that into a report. Every handover is a chance for an error, and in an audit by your certification body that is exactly where they dig deeper: where does this figure come from and how do you know it belongs to this circuit?

How we build your scope 8 software

We start with the structure of the installation, not the report template. Once the structure is right, the report follows from it; it doesn't work the other way round.

1
Designing the installation structure

Distribution boards, groups, final circuits and the measurement points that belong to them. That tree is the foundation: everything you later want to compare over the years hangs off it. We also decide how you handle changes to the installation between two inspections.

2
Separating the EBI and the PI

The first special inspection (EBI) records the baseline and requires more than the periodic inspection (PI) that follows. We design the two as separate forms on the same installation, so that the inspector can see what was established at the EBI when carrying out a PI.

3
Building in sprints

We work in sprints and start with the periodic inspection, where the volume is. Your inspectors take part and try an interim version on a real distribution board early on; only there does it become clear whether entering data is faster than on paper.

4
Measuring equipment and handover

We look into what data your measuring instruments can provide and integrate what we can. Then a handover to your back office, with a trial run in which we walk through a completed file against the questions your certification body asks.

What the software actually does

Six components that together make up the file. Which ones you need depends on the size of the installations you inspect.

Installation tree with measurement points

The installation built up to group level, with the values that belong to the type of protection and earthing system at each measurement point. The inspector works through the tree rather than a list, and sees along the way what is still outstanding.

Measurements with limit values

Insulation resistance, earth resistance, continuity and disconnection times, each with the limit that applies to that situation. A value outside the limit stands out immediately, and the series over the years shows whether something is deteriorating.

EBI as the reference for every PI

During a periodic inspection, the app shows what was recorded at the first special inspection and what has changed since. Without that reference point, a periodic inspection is just an isolated snapshot.

Findings with classification

Every finding is given a classification and stays open until it has been resolved and verified. At the next visit, the inspector sees what was still outstanding, so they don't report again what has already been fixed.

Recognition on site

A code on the distribution board opens the right part of the file directly. In a building with twenty distribution boards, that saves searching and, more importantly, prevents recording something under the wrong board by mistake.

Report and client portal

The report is generated from the recorded data and signed by the inspector. Your client retrieves it from a portal in which they see only their own installations, with the outstanding findings alongside.

Who we build for

Four situations in which this file delivers the most. The difference lies in the size of the installation and in who will be reading the report.

Certified inspection bodies

The core. Your certification depends on the quality of the file, and your margin on the turnaround time per installation. If you also inspect combustion installations, scopes 1 to 6 are the same system with different forms.

Industry with its own electrical engineering department

Large installations with many distribution boards and an in-house team. Here the scope 8 inspection often runs alongside regular maintenance and your own inspection duty as an employer.

Property management and institutions

Many buildings, each with its own installation, where the central overview matters more than the depth per building. The question is usually: which buildings have outstanding findings.

Work required by insurers

Some assignments arise from a policy condition. What matters most then is that the report is demonstrable and on time, and that the client can show that findings have been resolved.

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 your situation. Meter cupboards and technical rooms rarely have coverage, so offline working is a requirement, not an extra. What we connect to your measuring equipment depends on the data your instruments make available.

Native iOS and Android Offline-first storage QR and NFC labels on distribution boards Node.js / Python / .NET PostgreSQL Installation tree down to circuit level Limit values per measuring point Import from measuring instruments Time series per measuring point Signed PDF reporting Client portal per customer Integration with scheduling Audit logging of changes Hosting in the EU

Why Appfront

The structure determines everything

An inspection app that ticks off a checklist per visit cannot show a trend. We build around the installation, because that is where the value that accumulates over the years lies.

Measurements belong to a point

An insulation value without a circuit is just a number. By attaching every measurement to a measuring point, you can compare results and see deterioration before anything fails.

Connecting to what you already run

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

Honest about the limits

We are not a certification body and we do not assess inspections. We build the system in which your inspector records their findings; the technical judgement remains theirs.

Security and privacy

The file contains little personal data, but it does record which inspector carried out which inspection and under which competence. That is traceable to an individual and bears on their certification. We use that record for its intended purpose and focus reports on the installation, not on the individual inspector.

More significant is that you work with data about your customers' installations, including outstanding defects. That is information you do not want to leak to other customers or to the outside world. Access is therefore strictly per customer, with a portal that only shows their own installations. A finalised report cannot be changed silently: a correction is visible as a correction and does not overwrite the original, because a report that can be altered unnoticed afterwards has no value in an audit or after an incident. 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 8

Scope 8 covers the fixed electrical installation and falls under the SCIOS sub-scheme for electrical equipment. The first special inspection assesses the installation after completion or before it is put into use and relies on NEN 1010, the standard for low-voltage installations. Periodic inspections follow after that. Individual electrical work equipment is not covered by scope 8; that belongs to scope 9, and inspection for fire risk to scope 10.

Scope 8 covers the installation, scope 9 covers electrical work equipment and scope 10 covers the inspection of electrical equipment for fire risk, which is the application of NTA 8220. They sit within the same sub-scheme but answer a different question: is the installation in order, is the equipment safe, or does the equipment pose a fire risk. We cover scope 10 separately on that page.

NEN 3140 is the standard for the safe operation of electrical installations and is aimed at the employer: which installations and work equipment do you have, how often do you inspect them and who is responsible for that. Scope 8 is a certification scheme for an inspection body that carries out a specific inspection and issues a report on it. We cover the employer's side on the NEN 3140 page.

Often partly. Many installation testers can export measurement series, and these can then be linked to the measuring points in the file. Exactly what comes out, and whether it can be traced per circuit group, varies greatly by make and model. During the discovery phase we establish what is possible, rather than promising an integration that breaks down on your instrument, and we make sure manual entry is kept short in any case.

Yes. Meter cupboards, technical rooms and basements have poor coverage, and that is exactly where the installation is. The app stores data locally and synchronises as soon as a connection is available, showing clearly which inspections are still pending. What we explicitly design for is the situation where two inspectors have worked offline on the same installation.

This is one of the trickiest points in this file, and it is a design question, not a data-entry problem. An extended distribution board must not wipe the history of the existing circuit groups. We therefore model modifications as dated additions, so that during a periodic inspection you can see which part is new and which part has a series of measurements.

Yes, and it saves your back office a lot of email traffic. Each client gets a portal in which they see only their own installations, with the reports and the outstanding findings. For managers with multiple locations, this is the most requested feature, because above all they want to know where something is still outstanding.

That depends on how deeply you want to model the installation and whether integrations with measuring equipment and scheduling are involved. A file at distribution board level is considerably lighter than one down to final circuit level. We advise on this, because deeper is not always better: it has to match what your inspectors actually record in practice. We will give a well-founded estimate after the discovery phase.

Want to build a scope 8 file?

Tell us how your inspections are currently recorded and where your back office loses time, and we will help you think through the installation structure, the measurements and the integration with your measuring equipment. We build this as a standalone application and as part of a broader project involving custom software or an app. If you supply to new-build projects in consequence class 1, your declaration belongs in the Wkb file for the competent authority.

Edit content