I5Electrical contractorsInstallation checks schedule
D.P.R. 462 verification schedule and client recall list
Reads your table of the clients' installations and tells you which DPR 462 earthing verifications are overdue and what the client risks, which fall due in 60 days, and which clients to call next month for your own visits — every date computed with its source.
The problem
Dozens or hundreds of client installations, each with its own interval: a dental practice is not verified every five years like an office. Keeping the schedule by hand means finding overdue verifications when it is too late.
Who it is for, and when
- Who it is for
- The owner or the office of an electrical installation firm with a few dozen to a few hundred clients' installations under maintenance: condominiums, medical practices, shops, factories, schools.
- When
- Once a month, before planning the next month's visits; and whenever a new client or a colleague's client base comes in.
What you give it, what you get
You give it
The installations list as you keep it: the office's Excel sheet or the management software's CSV export — client, address, contact and phone, kind of site, systems, last DPR 462 verification, contract, last visit — even with dates written in different ways.
You get
A first line (installations, verifications falling due, already overdue with the most exposed by name, the month's calls); the overdue verifications with the client's exposure in one line; the next 60 days; the call list for the phone, one client per row with the 462 reminder beside the visit; the schedule per installation and two CSVs; every interval with its source.
How it works, in three steps
- Upload the installations sheet or the software's export
- Read the overdue verifications and what the client risks first
- Download the call list or hand it to the phone calls
On its own, in a flow. Every month by itself: the flow receives the updated sheet and, when a verification is overdue, sends you the clients' exposure first and then the call list; otherwise just the month's calls. The 462 verification is commissioned by the client from an accredited body: the schedule reminds, it never performs it.
The rules it applies
In the agent's own words: what it checks and what it never does.
- Overdue verifications first, the client's exposure named
- The dental studio at 2 years, not 5: by the law, in code
- Next month's recall list, ready for the phone
- Every total is recalculated from the lines and compared with the printed one; what cannot be read stays empty and is said in the notes, never invented.
A real example
A case from the demo catalogue, with anonymised documents.
An 80-installation sheet — 3 DPR 462 verifications overdue, the dental studio at two years not five, 48 calls for November
It is 1 October: Giulia, in Acme Impianti's office, has the Excel sheet of the clients' installations — 80 rows in six sections, kept by three people over the years, dates written five ways and the Corvi dental studio marked «5 anni». She needs to know which DPR 462 verifications are overdue or due in the next 60 days, what those clients risk, and whom to call for November's visits.
The recorded result
80 impianti · 12 verifiche in scadenza entro 60 giorni · 3 già scadute (Studio dentistico Corvi: locale medico, biennale, scaduta il 3/5) · 48 richiami per novembre · 1 senza data dell'ultima verifica
real time 25 s8 credits
Frequently asked questions
How does it know how often an installation must be verified?
From the type of premises, with the rule in code: the dental practice every two years, not five. Every date in the schedule is worked out with its source, and overdue verifications come first, with the client's exposure.
What does it cost, and how long does it take?
Usually 6–13 credits a list (≈ €0.25–0.54) and under a minute. It depends on the list: more installations cost more; the code computes the dates. The recorded example cost 8 credits in 25 seconds.
Can it run on its own, in a flow?
Every month by itself: the flow receives the updated sheet and, when a verification is overdue, sends you the clients' exposure first and then the call list; otherwise just the month's calls. The 462 verification is commissioned by the client from an accredited body: the schedule reminds, it never performs it.
Who checks what the agent did?
You do — and it takes a minute, not an afternoon. Every run is a trace: the live timeline, each tool call, each document read, the cost per step, the confidence and sources. Actions that leave the building wait for your approval. The platform never sends, never touches a live store, never moves money.
Where does my data live, and how do you handle GDPR?
Your data is stored in the EU, on one server in Germany. The EU/US data-region setting limits which models an agent can be saved with, not where your data is stored. A no-retention mode and a local runner on your own machine are available. Your plan sets how many days your data is kept — you can change it — and when they run out it is deleted automatically. You download each run's results and delete files, agents and connections in the console; an owner deletes the whole workspace and each person their own account from Settings. The “Your data” page names the services that handle your data.
Related agents
- I1Bill of materials for the wholesalerFrom the panel builder's list, a manual or a photocopy to the order: both codes, the boxes, the questions.
- I2Delivery notes (DDT)Reads the supplier's delivery note — photographed on site too — and tells you line by line what arrived, what is short and what is over against the order.
- I3Job sheetsReads the week's signed job sheets and computes each technician's hours, the km and the material to invoice; the unsigned sheet first.
Try it on your own documents
The demo shows the recorded cases without an account; with your own workspace you run it on your files.