Custom app for on-site EPBD inspections
Inspections take place on a roof, in a boiler room or behind a steel door. What is found there has to become a report, and must be in the national portal within four weeks. Between those two moments, most inspectors have a notebook and an evening of typing.
Where the time goes
An inspection is largely observing and noting: installed capacity, the condition of the system, settings, measurements, and the recommendations that follow. On site, this goes into a notebook or a PDF form on a tablet that closes halfway through. Afterwards, someone has to turn it into a report and a registration, and that step is where the days slip away.
Administration has a hard deadline. The registration of an air conditioning inspection must be in the national portal within four weeks of the inspection. With one inspection a week, you can keep up. During a spring peak, when everyone wants their cooling checked, that deadline becomes a pile.
There is also a quality side. Only a registered company or a qualified expert with a valid certificate may register, and clients can verify this. That makes your own records important: which inspector carried out which inspection, with which certificate, and whether that was correct on that date. In the event of a complaint or an audit, that is the first question asked.
How we build this
The report must be created on site, not afterwards. Anything an inspector still has to retype in the evening is work you cannot invoice and that introduces errors.
A code on the unit or panel opens the correct installation with its history and the previous inspection. Searching a list on a roof happens once, not every time.
The order of the screen must match the order of the actions, not that of the report. Otherwise people end up flicking back and forth.
Roofs, basements and technical rooms have no signal. Everything is recorded locally and synchronised later, keeping the original timestamp.
The registration deadline runs from the inspection date. It should live in the system, not in the planner's head.
What the app does in practice
Capture on site carries the whole process. What else you include depends on how many inspections you carry out and whether you work for multiple clients.
Opening the installation by scanning
A code on the unit opens the correct installation with the previous inspection alongside. That saves searching and prevents registering against the wrong unit.
Capture in inspection order
Capacity, condition, settings and findings, in the order you encounter them. A form that follows the report structure doubles the number of actions.
Measurements with time and place
Values recorded where they were measured. Measurements entered afterwards are hard to defend in the event of a complaint.
Photographs of findings
A dirty condenser, missing insulation, a setting that is wrong. A timestamped photo makes a recommendation concrete rather than disputable.
Works on the roof and in the basement
No signal is the normal state in these places. The app keeps working locally and synchronises later, keeping the original timestamp.
Monitoring the registration deadline
Four weeks from the inspection date, tracked per inspection, with a warning before it expires rather than after.
Who we build for
Who carries out the inspection determines the design. Four situations.
Inspection companies and installers
Multiple clients, seasonal peaks and a registration deadline per inspection. This is where the gain lies in turnaround time from inspection to report.
Owners who have their own systems inspected
As the client, you want to be able to check whether the inspector was qualified and registered. See also software for the inspection obligation.
In-house technical teams
You have the inspection carried out yourselves, but the recommendations land with your own people. The finding then needs to flow through an integration into a work order.
Advisory firms and energy consultants
You combine the inspection with advice on savings. The findings from the inspection then become your work pipeline rather than the end point. See also the inspection app.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
Inspection methodology and registration requirements change with European regulation. Everything relating to forms, fields and deadlines should be configurable.
Why Appfront
There is no signal on a roof
We build offline as the starting point. An app that needs synchronisation to save a field is not going to be used on site.
The screen follows the inspection
We design the sequence around how you move, not around how the report is structured. That saves half the steps.
Four weeks is shorter than it sounds
We track the registration deadline for each inspection. In a seasonal peak, that is the difference between keeping on top of it and a pile of backlog.
Who inspected, and under which certificate
We record that for each inspection. In the event of a complaint or an audit, it is the first question asked, and it cannot be reconstructed afterwards.
Security and privacy
An inspection file contains data about your clients' installations and about what is not in order there. If you work for several parties, those files must remain strictly separated. We set access per client and per property, and log every view.
For evidential value, the timestamp matters. A measurement that can be entered on a different day afterwards says nothing about when the inspection took place, and that very date starts the registration deadline. We store recordings as unalterable with their original timestamp, even when synchronisation happens later, and any correction appears as a visible amendment alongside the original value. How we handle security ourselves is set out in our information security policy; reports from outside come through our CVD policy.
Frequently asked questions about the EPBD app
That depends on what the portal allows. Where an integration is possible, we build it; where it isn't, the app prepares the registration and monitors the deadline, so entering the data becomes a task of minutes rather than an evening. Check the options with the portal administrator before you plan around them.
Yes, and that is the starting point. Roofs, boiler rooms and plant rooms rarely have coverage. Everything is recorded locally and synchronised later, with the original timestamp preserved. The last part matters, because that date determines when the registration deadline runs out.
For an air conditioning inspection, registration must appear in the national portal within four weeks of the inspection. Check the current deadlines and the correct portal with RVO, as these can differ by installation type.
Yes. The recording on site is the source; the report is built from it rather than retyped. That is where most of the time goes and where most errors arise, because retyping happens at a moment when the installation is no longer in front of you.
The EPBD software covers the owner's side: which installations fall under the obligation, when the next inspection is due, and whether the inspector was qualified. This app covers the executing side: the inspection itself and the report. The two connect with each other.
Yes, and that is necessary. Installation types differ and the methodology is revised periodically. We therefore keep inspection forms as a setting per installation type, so that a change does not become a development request.
Yes. An inspection establishes and advises, but the recommendation usually disappears into the report. We route a finding on to a work order or to the client, so that something actually happens. See also the installation check app.
That depends on the number of installation types, whether you work for multiple clients and whether an integration with the portal is possible. The recording with report generation is usually quick to put to use and saves time straight away; integrations cost more. We give a reasoned estimate after the discovery phase.
Cut out the evening of typing?
Work out how much time passes between your last inspection and the moment the report goes out. That time is almost entirely spent retyping what you already knew on site. We build this as a standalone app and as part of a broader app development project.