Plant logbook and maintenance records: the data provenance that holds up in an audit
In an audit the question is not whether the work was carried out, but whether the record that attests to it was written that day or reconstructed afterwards. A plant logbook and a maintenance register follow a heating, electrical or fire safety installation for its whole service life, and in ordinary operation they are enough: they say that the required operations were performed on schedule. The picture changes as soon as a third party enters, meaning an inspector, a loss adjuster, the officer assessing a public funding claim, or a court deciding a dispute. At that point formal completeness stops being sufficient, because none of the filled-in fields says when it was filled in. A maintenance register that no external party can date carries modest evidentiary weight, however tidy it is. What makes it usable against someone else is the ability to trace each line back to the moment and the place where the observation was made.
What makes up the documentation file of an installation
The documentation file of an installation is not a single document but a chain of separate acts, produced by different parties at different points in the life of the asset. The first is the declaration of conformity, issued by the installing company to the client at the end of the works, after the checks required by the applicable technical rules, functional testing included. The second is the plant logbook, which stays with the installation for its whole existence and collects its technical data sheets and the history of interventions. The third is the maintenance register, whose upkeep sits among the documentation duties that occupational safety legislation places on the employer, following the framework set by Directive 89/391/EEC on safety and health at work. Authors do not coincide and neither do timings: the installer writes once, the maintenance contractor writes at every visit, the person responsible for the installation keeps the file and makes it available. Treating the three acts as one folder is the mistake that surfaces in every audit.
Declaration of conformity and mandatory annexes
The declaration of conformity attests that the installation was built to the applicable technical standards, and it is kept by the owner of the property or by the building manager for the entire life of the asset, available to the competent authorities on request. National implementing rules make it mandatory and, for pre-existing installations, generally admit a declaration of correspondence issued by a qualified technician in its place. The annexes normally required are:
- the design documentation signed by the technical officer of the installing company
- the report listing the type of materials used
- the as-built diagram of the installation
- the certificate recognising the technical and professional requirements of the installer
A declaration without its annexes stays incomplete, and the gap comes to light almost always at the worst moment: a sale, an inspection, the assessment of a claim.
Plant logbook and periodic maintenance records
The maintenance register is the document in which checks, tests and interventions carried out on an installation are recorded, with the date, the type of operation and the party who performed it. Safety legislation requires it to be kept but does not prescribe the medium: paper and digital are both admissible, and fire safety rules in most European jurisdictions state this explicitly for the register of fire protection checks. The same applies to electrical installation registers and to the other maintenance records required for specific categories of equipment. The medium is not the dividing line: a digital fire safety register is not inherently more solid than a notebook, and a notebook is no more reliable than a file simply because it is made of paper. The fields a maintenance register has to contain are few and always the same:
- identification data of the installation or asset
- date and time of the intervention
- type of operation performed
- components replaced or checked
- outcome of the check
- party who carried out the work
- due date of the next inspection
The logbook of a heating installation collects instead the data sheets of the plant and the outcomes of periodic checks. The Energy Performance of Buildings Directive requires that regular inspections of heating and air conditioning systems produce a report handed to the person responsible for the installation, and national schemes typically have a copy transmitted to the competent authority and entered into a public register of installations. In the report the technician notes the maintenance carried out and the date of the next scheduled visit. For renewable installations the logic does not change, which is why practitioners speak of a photovoltaic plant logbook to mean the file that collects technical sheets, inspections and the register of maintenance interventions.
Failure to compile or to keep the logbook and the maintenance register is normally punished with an administrative penalty, in amounts that vary with the rule breached and with the party at fault, whether installer, maintenance contractor or the person responsible for the installation. It remains, though, a formal sanction: it targets the absence of the document, not its reliability.
Why maintenance records written after the fact do not hold up in an audit
A maintenance register compiled after the fact does not hold up in an audit because formal completeness and chronological verifiability are two different qualities, and the person checking cares about the second. A register can contain every required field, show dates consistent with the prescribed intervals and carry the technician's signature, and still offer nothing that demonstrates when each line was actually written. The signature proves who did the work, not when the line was entered. The date in the relevant field is a statement by the same party that has an interest in it, and in a dispute it is weighed as such. Courts dealing with private construction contracts tend to give more credit to technical documentation formed as the work progressed than to documentation reconstructed later, and in insurance assessments the criterion is the same.
The comparison comes down to five points, which are also the questions an adjuster asks on opening the file, the same ones behind the requirements for court-ready digital evidence.
| Aspect | Register compiled after the fact | Observation certified at source |
|---|---|---|
| Moment of writing | stated by whoever compiles it, not demonstrable | attested by a qualified timestamp at the instant of the observation |
| Proof of place | absent, beyond what the operator says | coordinates captured by the device during the acquisition |
| Integrity of the content | not verifiable, the file can be replaced without leaving a trace | cryptographic hash of the content, which changes with every edit |
| Verifiability by a third party | requires taking the company that wrote the register at its word | the adjuster or inspector checks it independently |
| Under challenge | counts as a statement by an interested party | stays usable against the other side years later |
Contract dispute, insurance claim, funding audit
The three situations in which the evidentiary value of maintenance documentation is tested are a dispute with the client, an insurance assessment and an audit on public funding. In the first, the company has to show it performed the contractual services on the agreed schedule, and the maintenance register is often the only document that tells that story. In the second, the insurer appoints an adjuster to establish whether the damage came from omitted or insufficient maintenance, and in a property damage assessment the photographs count as much as the written entries. In insurance work, TrueScreen lets the adjuster independently verify the date, the place and the integrity of every photograph attached to the file.
The third case is the most treacherous, because it arrives long after the site has closed: audits on public funding can be documentary or carried out on site, and they can come years later. Incentive schemes for energy efficiency work typically require photographic documentation of the condition before the intervention, of the work performed and of the installed equipment, allow the granting body to reject a claim for inadequate photographic evidence, and impose retention of the file for several years after the last payment, as happens with renewable plant evidence in incentive audits.
Maintenance companies use TrueScreen to make every line of the register traceable to the moment and the place of the observation, so that an adjuster or an inspector can check it years later.
What makes a maintenance data point verifiable by a third party
A maintenance data point is verifiable by a third party when it carries three elements that do not depend on the word of whoever produced it: the moment it was acquired, the place it was acquired, and the integrity of its content. The moment is attested by a qualified electronic timestamp, which under the eIDAS Regulation carries a presumption of accuracy of the date and time it indicates and of the integrity of the data it is linked to. The place is attested by the geographic coordinates captured by the device at the instant the acquisition happens. Integrity is attested by a cryptographic hash computed on the content, which changes if even a single bit of the file changes. The digital seal that TrueScreen applies through a qualified trust service provider makes any later modification detectable.
Timestamp, coordinates and cryptographic hash of the content
The three elements work together and none of them is sufficient on its own. A legal grade timestamp gives the record a date that can be relied on against others, meaning a date that does not depend on the clock of the phone nor on the good faith of the person holding it. Coordinates place the observation in front of that specific switchboard and not another one, a detail that decides matters when a company manages dozens of similar plant rooms. The cryptographic hash binds the photograph, the measurement or the service report to its own content: if someone retouches the image or changes a figure, the hash no longer matches and the discrepancy is demonstrable by anyone. What comes out of this is the digital provenance of the record, its history verifiable from the origin, which is precisely what a maintenance register kept on a spreadsheet cannot offer.
Certification at source of a maintenance data point
TrueScreen certifies every photograph, measurement and service report at the moment it is captured in the field, binding date and time, coordinates and the cryptographic hash of the content. Certifying at source means forming the evidence at the instant of the observation, rather than reconstructing it in the office when somebody asks for it: the record is born dated, located and sealed, and stays that way for its whole retention period. This changes the nature of the technical file that installation and safety legislation requires, which turns from a collection of statements into a set of records an outside party can check. The technician works as before, with the phone already in their pocket: the only difference is that the photograph of the replaced component and the report countersigned by the client leave the site already dated and sealed.
In practice three things are needed: certified photos and videos of the switchboard, the nameplate or the replaced part, service reports signed on site by the client, and an orderly collection of all of it that can still be handed over years later. Companies working on critical installations find the full picture on the page dedicated to certified installation and maintenance.
An example makes the difference concrete. A maintenance company manages the plant room of a residential building. Eighteen months after the last intervention a failure occurs and the building manager alleges omitted maintenance. The company produces the register, every line is there and so is the technician's signature, but the adjuster appointed by the insurer asks what the date of those entries rests on. The register, filled in at year end on a shared spreadsheet, has nothing binding each line to the day the work was done. With observations certified at source the conversation would have lasted ten minutes: the adjuster opens the photographs, checks date, coordinates and hash, and the matter ends there.
How to organise the logbook and maintenance records so they hold up in an audit
A plant logbook and a maintenance register hold up in an audit when every piece of them can be dated by a third party, retrieved years later and linked to the right installation. The first step is deciding what has to be certified at the moment of the observation and what can stay a simple note: as a rule, certification goes to the photograph of the condition before and after the intervention, the instrument readings, the signed report and any anomalies found. The second is giving the crews a single form, because twenty technicians with twenty habits produce twenty files nobody can compare; custom certification workflows exist for this, and they serve an installation company as much as the facility manager coordinating external contractors, along the lines of the audit evidence expected under ISO 41001 in facility management.
The third step is retention. The documentation has to be kept for the whole life of the installation and, in the case of incentives, for several years after the last payment, with access and change tracking that makes it possible to say who opened what and when. Asset management practice codified in ISO 55001 and the control of documented information required by ISO 9001 point in the same direction: records have to be identifiable, retrievable and protected from unintended alteration. Companies that also work on construction sites meet the identical problem in the photographic evidence of work progress and in the proof of a field service visit: showing what was done and on which day. Standard forms and templates are the starting point, not the finish line. Somebody else supplies the form; the proof that the form was filled in that day has to be built by whoever fills it in.
