Inspection and testing

No retyping readings. And the signature is checked before it is the wrong one.

For inspection bodies, safety advisers and businesses that inspect as well as install.

Test report · Apartment block, Lindenweg 812 of 30 circuits
CircuitRisoZsFI
S1 · Kitchen>300 MΩ0.42 Ω18 ms
S2 · Bathroom245 MΩ0.51 Ω21 ms
S3 · Laundry room0.42 MΩ0.63 Ω24 ms

Signature blocked. Your business changed this installation in 2024 — the inspection has to be carried out by an independent third party (NIV Art. 33).

The week you know

Thirty circuits, recorded twice

On Tuesday you tested thirty circuits in a cellar. The values are on a sheet in the folder and on the tester's display. On Thursday evening you type them in a second time, into the test report, after a long day. On one value a digit slips. Nobody notices — until somebody does, and then it is your signature underneath. And on the next property you spend half an hour looking for what was measured on the same board five years ago.

What changes

The reading is recorded once

The test run is created on site

Circuit by circuit, on the device in your hand, even with no signal in the basement. The test report as a PDF comes out of it — nothing is retyped any more.

The measurement history stays on the installation

Every circuit carries its values over the years. What is measured today stands beside what was measured last time, and a deterioration is something you see rather than something you remember.

Inspection intervals and authorisations run alongside

The interval under the NIV — 1, 3, 5, 10 or 20 years — hangs off the installation. Authorisations at person and business level speak up before they expire.

Independence is checked, not assumed

Whoever built or altered the installation may not inspect it under NIV Art. 33. The software knows both sides and blocks the signature instead of faulting it afterwards.

The run

From the distribution board to the next inspection interval, without retyping

Five stations, one record. What the photo in the cellar captures ends up in the test report — and the interval afterwards runs on by itself.

  1. 01

    The request comes in

    The grid operator's request or the inspection body's defect report arrives as a PDF or a photo and is read: one line per defect with the item, the location, the standard referred to and the deadline for putting it right. The defect texts are taken over word for word rather than summarised, and a deadline that is not clearly on the sheet stays empty rather than being guessed.

    Defect report · PDF read

    Defect 3 of 7 · distribution board UV1

    NIN 5.3.3.1 · taken over word for word

    Deadline — not printed, left empty

  2. 02

    The distribution board is photographed

    One photo of the consumer unit, and the circuits are there: designation, type, rated current, RCD rated current and number of poles read off the labelling. That too is a proposal with a tick box — once ticked it takes the same route as any entry made by hand, and waits if it has to until there is a signal again.

    Photo · distribution board UV1

    S4 laundry room · MCB C16 · 1-pole

    FI 30 mA · 4-pole

    Suggestion 24 lines · all ticked

  3. 03

    The testing is done, circuit by circuit

    The test run is created in the cellar, on the device in your hand, with no signal. Every value hangs off the circuit it was measured on — and not off a sheet still to be typed up on Thursday evening.

    Test run · S4 laundry room

    Riso 245 MΩ · Zs 0.51 Ω

    FI 21 ms

    Basement · recorded offline

  4. 04

    Test report and safety verification certificate

    The test report is produced as a PDF from the recorded runs. Before the signature, the software checks independence under NIV Art. 33: whoever built or altered the installation may not inspect it. It knows both sides and blocks.

    Test report · 30 circuits

    PDF created

    Safety verification certificate prepared

    NIV Art. 33 · signature blocked

  5. 05

    The next inspection interval runs alongside

    The interval under the NIV — 1, 3, 5, 10 or 20 years — hangs off the installation and counts on from this inspection. The measurement history stays on the circuit, so the next value stands beside today's and a deterioration is something you see rather than something you remember.

    Installation · Lindenweg 8

    Inspection interval 20 years, NIV

    next inspection 2046

    Measurement history S4 2006 · 2016 · 2026

Here too the AI proposes and you tick. No circuit and no defect stands on a document without somebody having looked at it and confirmed it.

Inspection interval under the NIV

The interval belongs to the installation, not to your calendar

Depending on the type of installation, the inspection interval under the NIV is 1, 3, 5, 10 or 20 years. The software tracks it per installation, counts from the last inspection and speaks up before the next one falls due. The chain from the measurement through the test report to the safety verification certificate stays audit-proof throughout.

Calculate inspection intervals

What stays

You keep what works

An inspection depends on notification routes and master data that have been right for years. We do not touch those.

  • Your accounting — export to bexio, Abacus and Banana
  • Your notifications to the grid operator through M2 and ElektroForm — that is where they stay
  • Your article prices and terms with the wholesaler
  • Your existing customer base with property managers and owners

After 45 minutes you will know how many of your installations fall due next year.

We take a handful of your properties, assign the inspection intervals and show you what work comes out of that. The list is yours, contract or no contract.

Arrange a conversation