When a fire occurs, when an insurance claim lands, when an HSE inspector turns up unannounced, the first thing anyone asks for is your maintenance records. What they find determines whether your company is protected or exposed.
Paper-based records fail at that moment in predictable ways. The logbook is at the site but the wrong site. The engineer signed the form but forgot to date it. The test was performed but the result was never written down. The certificate was issued three years ago and no one renewed it.
This article covers what automated compliance documentation actually looks like in practice, why it holds up under audit and insurance scrutiny in ways that paper doesn't, and how the mechanics differ across elevator maintenance, fire safety, HVAC refrigeration, and access control.
Why paper compliance records fail
The failure mode for paper compliance records is not usually negligence, it's the natural fragility of a system that depends on perfect execution by field engineers under time pressure, at dozens or hundreds of sites per month.
Missing records
A maintenance visit happened. The engineer was competent. The test was performed correctly. But the paper job sheet stayed in the van, got left on site, or was lost during transit back to the office. The visit exists in payroll records but not in the compliance file. When an auditor asks for the last three service records for a specific asset, you produce two.
Unsigned or undated forms
Clause references matter. BS 5839-1 Clause 45.1 requires the inspection record to include the date of the service and the name and signature of the engineer. An undated form is not a compliant record. A form signed with an illegible scrawl and no printed name leaves the auditor unable to verify that the work was done by a certified individual.
Incomplete test data
"Fire alarm system tested, satisfactory" is not a compliant service record. It does not specify which detectors were tested, what sensitivity readings were obtained, whether the cause-and-effect matrix was verified, or what the battery voltage under load measured. The engineer knew all this information when standing at the panel. None of it made it onto the paper form.
No photo evidence
For anything involving physical condition, corroded contacts, damaged cable containment, a door seal that needs replacing, a written description creates disputes. An auditor, loss adjuster, or solicitor reading "cable tray damage noted" cannot determine the extent of the damage, when it occurred, or whether it created a system risk. A timestamped photograph with GPS coordinates removes all of that ambiguity.
Certificates not tied to assets
Service certificates, inspection reports, and third-party inspection documents accumulate in filing cabinets or PDF folders named by date. Finding the current LOLER certificate for Lift 3 in Building B means searching manually. Confirming that the annual service was completed for every one of 47 fire panels across 12 sites means cross-referencing spreadsheets, or guessing.
What automated compliance documentation looks like
When compliance documentation is built into the work order system rather than bolted on afterwards, the record is created as a by-product of the job itself, not as a separate administrative task.
Checklists tied to specific work orders
Each work order type carries its own checklist template. A monthly elevator communication test generates a different checklist than an annual fire alarm service or a quarterly F-Gas leak check. The checklist is not generic, it maps directly to the regulatory requirements for that asset type and service interval.
The engineer cannot close the work order without completing the checklist. There is no mechanism for "we'll fill this in later." The checklist exists in the app, on that specific work order, tied to that specific asset, and it must be completed before the job is marked done.
Timestamped and GPS-tagged entries
Every checklist response, every pass/fail, every measurement recorded, every anomaly noted, carries an automatic timestamp from the moment the engineer entered the data, and a GPS coordinate from the device. You cannot backdate a reading. You cannot complete a test at the office and claim it was done at site. The metadata is part of the record.
This is not a small detail. When an insurance claim or legal action questions whether maintenance was actually performed on the date stated, the difference between a paper form filled in retrospectively and a digital record with 47 timestamped entries from a known GPS location is the difference between a defensible position and an exposed one.
Photos auto-attached to work orders
The engineer photographs damaged components, measurement device screens, test equipment in position, replaced parts, and completed repairs. Those photographs are attached directly to the work order for that asset, tagged with the same timestamp and location as the checklist entries.
Three months later, when the customer queries whether the compressor shaft seal was inspected on the March visit, the evidence is in the asset history. Not in someone's phone camera roll. Not lost when the engineer leaves.
Electronic signatures with name capture
The engineer signs on the technician's mobile device at completion. The responsible person at the site signs to confirm the visit occurred and any defects were communicated. Both signatures carry the time and date of signing, and both are stored against the work order.
The record contains the signing person's identity, not just an illegible mark but their name as registered in the system. If a question arises about whether the responsible person was informed of a defect at the time of the visit, the signature and timestamp answer it.
Auto-generated certificates
For inspections that produce a certificate, EN 81-28 monthly test records, F-Gas service records, LOLER examination reports, the certificate is generated from the completed work order data. The engineer does not write a certificate by hand. The system populates the certificate template with the asset details, the test results, the date, and the engineer's certification number.
The certificate is automatically filed against the asset record. It is also available for the customer. The maintenance company retains the original; a copy goes to whoever the regulation designates as the record holder.
Industry-specific compliance requirements
Elevators: EN 81-28 monthly test logs
EN 81-28 requires monthly testing of the emergency communication system in every elevator car. The standard does not prescribe the exact format of the test log, but the inspection body (in Germany: TÜV; in the UK: UKLIFT/LEIA; in Poland: UDT) will verify that tests occurred, that the results were recorded, and that failures were acted on.
A compliant monthly test log must show:
- Date of the test
- Which shaft was tested (building, shaft designation)
- Whether the connection was established within 30 seconds
- Whether audio quality was satisfactory in both directions
- Emergency power supply status
- Name of the technician performing the test
- Any remedial action taken if the test failed
Paper-based monthly test logging across a portfolio of 200 elevators means 200 separate paper entries per month, stored at the relevant sites, and reconciled manually to confirm that none were missed. A missed monthly test is not just an administrative failure, it is a potential safety liability if a trapped passenger incident occurs and the system had not been verified as working.
Automated logging means the test checklist appears in the engineer's app for each elevator on their route that month. Completing it creates the record. Skipping it leaves the work order open and flagged. The operations manager sees a live dashboard of which tests have been completed and which are outstanding, before the month ends, not after the audit.
For more detail on EN 81-28 requirements, see EN 81-28 Compliance Checklist for Elevator Maintenance Companies.
Fire safety: BS 5839 zone rotation tracking
BS 5839-1 Section 45 requires that weekly manual call point tests rotate through all zones. An inspector checking a logbook for a 10-zone system expects to see each zone tested over a representative period, not the same zone tested every week for 12 months.
Zone rotation tracking is almost impossible to maintain reliably on paper across a large building portfolio. The responsible person at each site is meant to maintain the logbook, but the contractor needs to verify rotation compliance at every visit and flag gaps to the responsible person in writing.
Automated tracking assigns each weekly test a zone sequence. The next test automatically prompts the responsible person (or the engineer, on-site visits) to test the next zone in the rotation. The system maintains a running record of which zones have been tested and when. At any point, the operations manager can see whether Zone 7 at Site 14 has been tested in the last 30 days.
When a fire authority inspector visits and asks for the zone test log, the system generates it as a dated table showing every zone, every test date, and the test result. This takes seconds to produce. Finding the equivalent information in a handwritten logbook, with entries made by different people in different handwriting, takes considerably longer, and may not be possible at all if pages are missing.
For full BS 5839 requirements, see BS 5839 Compliance for Fire Alarm Maintenance Companies.
HVAC: F-Gas leak check records
EU Regulation 517/2014 Article 6 requires operators of equipment containing fluorinated refrigerants above 5 tonnes CO₂-equivalent to maintain an equipment record covering every service visit. The contractor who performs the service is practically responsible for creating that record and ensuring the operator receives it.
A compliant F-Gas service record contains:
- Refrigerant type and GWP
- System charge in kg and CO₂e equivalent
- Quantity of refrigerant added, in kg
- Quantity recovered, in kg
- Running charge after the visit
- Leak check method (electronic detector, UV dye, nitrogen pressure test)
- Specific points inspected
- Whether a leak was found, and if so, the location and repair action
- Follow-up leak check date if a repair was made
- Technician name and certificate number
- Company certificate number
A paper job sheet completed by hand rarely captures all of this. The refrigerant quantity recovered is estimated rather than weighed. The specific inspection points are summarised as "system checked." The follow-up check date is noted on the paper form, and then never followed up because the form is filed and no one monitors the open item.
Automated documentation prevents this by requiring each field to be completed before the job closes. The CO₂e calculation is performed automatically from the refrigerant type and charge size. The follow-up check, where triggered, is scheduled as a new work order against the same asset and remains open until an engineer closes it with a dated result.
For the full F-Gas compliance picture, see F-Gas Regulation Compliance for HVAC & Refrigeration Contractors.
Access control & gates: EN 13241 inspection logs
EN 13241 is the harmonised European standard for industrial, commercial, and garage doors and gates. For automatic gates, EN 13241 in combination with EN 12453 (safety in use) requires regular inspection and testing of safety devices, force limitation, safety edges, photo-electric cells, loop detectors, and emergency stop functions.
Unlike elevators and fire systems, EN 13241 inspection logs are often the only compliance documentation a gate maintenance company produces. The standard does not mandate the format, but the manufacturer's installation and maintenance manual specifies the inspection intervals and test procedures. Compliance evidence is what you have when a gate causes an accident, which is when solicitors and loss adjusters become interested.
A compliant inspection log for an automatic gate must show:
- Date of inspection
- Which safety devices were tested and the results
- Operating force measurement (Newton values, not just "pass")
- Whether the gate's movement profile matches the installation specifications
- Any defects found and the remedial action taken
- The technician's identity and qualification
Automated gate inspection logs follow the same model as other verticals: the work order carries the specific checklist for that gate type. The engineer records the force measurement as a number, not a checkbox. Any defect triggers an open remedial item. The inspection certificate is generated from the completed checklist.
How compliance automation protects you in audits and insurance claims
The audit or insurance claim scenario is where the quality of your documentation system gets tested against real consequences.
In a regulatory audit
A competent authority inspector, HSE, TÜV, local fire authority, environmental agency, arrives and requests your maintenance records for a specific site or asset type. They are checking three things: that maintenance was performed at the required frequency, that it was performed to the required standard, and that records were kept as the relevant regulation prescribes.
Paper records can satisfy the first test if everything was filed correctly. They rarely satisfy the second test because paper forms don't capture sufficient technical detail. They almost never satisfy the third test consistently across a large asset portfolio, because some forms are missing, some are incomplete, and some were never provided to the responsible person.
Digital records generated as part of the work order process give you a complete audit trail in minutes. Every asset, every visit date, every test result, every defect, every certificate, retrievable by site, by asset, by date range, by inspection type. The inspector asks; you produce.
In an insurance claim or legal action
When a claim follows a fire, a trapped passenger incident, a refrigerant leak with environmental consequences, or a gate injury, the loss adjuster or solicitor will examine whether maintenance obligations were met. If records exist, they are dated and signed, and they show the correct test results for the period in question, your liability position is clear. If records are missing, incomplete, or internally inconsistent, the exposure is substantial.
The specific protection that timestamped digital records provide is provenance. A paper form with a date written in ink proves nothing about when the date was written. A digital record with server-side timestamps, GPS coordinates from the engineer's device, and photo attachments with embedded EXIF data is significantly harder to challenge.
In contract disputes
When a customer disputes whether a service was performed, or claims a defect was not communicated to them at the time of the visit, the electronic signature of the site contact, captured at the time of the visit, is the most direct evidence available.
How RemoteOps handles compliance documentation
Every work order in RemoteOps is linked to a specific asset. The asset record carries the asset type, the applicable compliance requirements, the service history, all previous certificates, and all open defects.
When the work order is completed, the compliance checklist, specific to that asset type and service type, is part of the completion flow. The engineer cannot mark the job done without completing the checklist. Measurements are recorded as numbers. Photos are attached in the app. Signatures are captured on-screen. The certificate is generated and stored against the asset.
The operations manager has a live view of compliance status across the entire portfolio: which assets have upcoming tests due, which have outstanding defects, which certificates are approaching expiry. Before an audit happens, the compliance gaps are visible. That is when they can be addressed, not after the inspector asks for a record that doesn't exist.
Internal links for specific industry compliance guidance:
- EN 81-28 elevator compliance
- BS 5839 fire alarm compliance
- F-Gas HVAC compliance
- FSM software buyer's guide
Frequently asked questions
What is the difference between a digital service record and a scanned paper form?
A scanned paper form is an image of a document that was completed at some point. It carries no provenance, the scan timestamp tells you when the scan happened, not when the work was done. A digital service record created through a field service app contains timestamps for each data entry, GPS coordinates from the engineer's device, and is stored on a server that logs the creation time independently of the device. In any dispute about when work was performed, these are fundamentally different forms of evidence.
Do regulations require digital documentation, or is paper still acceptable?
Most field service regulations, BS 5839-1, EU Regulation 517/2014, EN 81-28 requirements as verified by inspection bodies, do not mandate digital formats. Paper remains legally acceptable. However, paper records are accepted only if they are complete, legible, dated, signed, and available for inspection. The practical reality is that paper records rarely meet all of those criteria consistently across a large field operation. Digital documentation does not guarantee compliance, but it substantially reduces the failure modes.
How do you handle situations where there is no internet connection on site?
Field service mobile apps designed for maintenance work operate offline. The engineer completes the checklist, captures photos, and takes signatures with the device in offline mode. The records sync to the server when connectivity is restored. The sync timestamp is the server-side record time; the data creation timestamps remain from when the engineer entered them. No compliance data is lost because of a poor signal.
How long do compliance records need to be kept?
This varies by regulation and jurisdiction. F-Gas equipment records under EU Regulation 517/2014 must be kept for at least 5 years after the entry was made. LOLER examination reports in the UK must be kept for 2 years (or until the next examination report, whichever is later). BS 5839-1 recommends that records be kept as long as the system is in operation. For any situation that resulted in injury, incident, or insurance claim, records should be retained until any legal proceedings are concluded. Most companies retain all service records indefinitely, storage is cheap; the inability to produce a record in litigation is not.
Can automated compliance documentation replace a physical site logbook?
For most purposes, yes, provided the digital system can produce a complete printed record for the site on demand. BS 5839-1 Clause 45.1 specifies that the log book must be available at the protected premises. If your digital system can generate and print the current site log at any time, and a copy is available on-site, this satisfies the intent of the requirement. Some inspection bodies are more conservative and expect a physical book to be present regardless. It is worth confirming with your relevant inspection body or fire authority what they accept before relying entirely on digital records for site-based documentation obligations.