I4Electrical contractorsEnd-of-works file and subcontractor file
End-of-works file and subcontractor folder: what is missing
Reads an installation's or a subcontractor's folder — PDFs and phone photos — and tells you whether the file can be handed over or the firm may start on site, with what is missing and the law that asks for it.
The problem
Before handing over an installation or letting a subcontractor on site, the folder has to be checked: declaration, test report, diagrams — or company record, DURC, safety plan, certificates — often PDFs mixed with phone photos, with due dates to work out.
Who it is for, and when
- Who it is for
- The technical office of an electrical contractor before handing over an installation, and the main contractor's before a subcontractor starts on site.
- When
- Before every handover to the client, and every time a subcontractor has to start on site — often on Friday for Monday.
What you give it, what you get
You give it
The photos or PDFs of the folder — DiCo, materials report, as-built diagram, test report, data sheets, company registration — or the subcontractor's: DURC, POS, list of workers, training certificates, appointments.
You get
On top, the verdict with the gaps — deliverable or not, can start or not; the register with each document's status and page, the expiries at the date, the obligations after handover and the e-mail with what is missing, ready and never sent on its own.
How it works, in three steps
- Upload the folder and choose: installation handover or subcontractor
- Read the verdict and the gaps on top, each with its rule
- Forward the e-mail with what is missing, or hand over the file
On its own, in a flow. Connect it to a webhook: if the file is deliverable it asks for your go-ahead; if not, at 08:00 you get the gaps and the e-mail already written for whoever has to complete them.
The rules it applies
In the agent's own words: what it checks and what it never does.
- Verdict first: deliverable or not, may start on site or not
- Two sourced checklists: DM 37/08 and D.Lgs. 81/08, editable
- Expiries computed in code: DURC, training, certificates
- 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.
The dossier photographed on site with a phone
Board QS-5's file was never scanned: it is nine phone photographs taken on the site bench, one declaration split across two shots, the phone's shadow and the lamp's reflection in the corners. The declaration is signed and stamped, the test report says «esito positivo» and the chamber-of-commerce extract is there. At the end there is also a photo of the board on the wall, which is not a document.
The recorded result
Document read.
real time 5 min 26 s17 credits
Frequently asked questions
Which rules does it check the file against?
A checklist with its sources cited — D.M. 37/08 and annex XVII — that you can edit. The due dates of DURC, certificates and attestations are worked out by code; every gap comes with its source and the e-mail to send to whoever must complete it.
What does it cost, and how long does it take?
Usually 12–26 credits a folder (≈ €0.50–1.07) and 4–9 minutes. It depends on the folder: more documents and more photos cost more. The recorded example cost 17 credits in about 5 minutes.
Can it run on its own, in a flow?
Connect it to a webhook: if the file is deliverable it asks for your go-ahead; if not, at 08:00 you get the gaps and the e-mail already written for whoever has to complete them.
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.