Compliance · By Tony Holz · 2 September 2026 · 8 min read

Fire safety logbooks under AS 1851: paper vs digital

The service record is the compliance product. A fire system that was serviced but not recorded was, for every purpose that matters — the audit, the annual statement, the courtroom — not serviced. What AS 1851 expects you to keep, who owns the logbook, where paper fails, and what actually changes when the record goes digital.

1. What the logbook actually is

Every fire protection system in an Australian building accumulates a service history: the routine inspections, tests, and maintenance performed against the cycles AS 1851 sets, the results of each activity, the defects found, and the work done to close them. The logbook — whether it is a cardboard book hanging off the fire indicator panel, a folder in the building manager's office, or a database — is wherever that history lives.

The word "logbook" undersells it. This is the evidence chain that the building's essential fire safety measures have been maintained to the standard, and it is what an auditor, an insurer, an assessor preparing an Annual Fire Safety Statement, or a coronial inquiry will ask for. The physical fire system proves it works today; the logbook proves it has been kept in a state where it could be expected to work every day in between.

2. What AS 1851 expects you to record

AS 1851 is built around scheduled service activities, and each activity generates a record. In practical terms, a service record that holds up needs to capture:

Which asset was serviced — the specific extinguisher, detector, pump, or door, not just "the extinguishers on level 3". Asset-level identification is what lets the next technician, and the auditor, reconstruct the history of one device.
Which activity was performed — the monthly, six-monthly, yearly, or five-yearly routine for that asset class, against the correct schedule for the system type.
The results — pass or fail, and the readings where the activity requires them: pressures, flow rates, discharge durations, battery voltages.
Defects identified — with their classification, the notice issued, and eventually the rectification and retest that closed them.
Who did the work and when — the technician, the date, and for anything contested, the time.
Baseline data — the system's approved design parameters, against which future test results are compared. A pump test result means nothing without the commissioning figure it is measured against.

Two records deserve special mention because they are the ones most often missing. The first is the baseline data: buildings change hands, contractors change, and the design figures quietly disappear, leaving every subsequent test result floating without a reference. The second is the close-out of old defects — a defect notice issued three contractors ago, never formally closed, sitting open in a logbook nobody reads.

3. How long records must be kept

The working rule: the current annual statement rests on the past twelve months of service records, so twelve months is the floor — every activity in the current cycle, available for inspection. But the floor is not the practice. Defect histories, baseline data, and five-yearly test results only make sense across years, and most regulators and assessors expect records to be producible for the life of the system, or at minimum across several service cycles. When a building is sold or a service contract changes hands, the records are part of what transfers — or should be.

Retention is where the format question starts to bite. Paper survives twelve months easily. It survives a decade, three contractor handovers, an office move, and a burst pipe far less reliably.

4. Who owns the logbook

The building owner carries the legal obligation to maintain the essential fire safety measures and to hold the evidence that they have been maintained. The service provider creates most of that evidence. In practice this splits the logbook in two: the on-site record the technician signs during the visit, and the service provider's own copy of every report, notice, and certificate issued.

The mature arrangement is explicit: the service provider maintains the master record and the owner has standing access to it. The worst arrangement — and the most common one under paper — is that neither party is sure who holds the complete set, and the answer is discovered at audit time to be "no one".

5. Where paper logbooks fail

Paper logbooks are not non-compliant. Plenty of buildings pass audit with a well-kept book. But the failure modes are structural, and every fire service company that has operated for more than a few years has met all of them:

The book disappears. Renovation, cleaning contractor, new building manager — the logbook that lived beside the panel for eight years is gone, and the history with it.
Entries are unverifiable. An undated signature and a tick prove very little. There is no timestamp, no photo of the asset as found, no reading recorded.
Asset identity is loose. "6 extinguishers serviced" does not establish that the extinguisher behind the new stud wall was one of them.
Gaps surface late. A missed six-monthly in March is discovered in February next year, when the assessor reads the book — eleven months too late to fix.
The book and the tags disagree. Field tags say one date, the book says another, and the discrepancy itself becomes the audit finding.
History cannot be aggregated. The owner of forty buildings has forty books in forty cupboards, and no way to answer "which of my sites has open critical defects" without forty phone calls.

None of these are technician failures. They are format failures — the record-keeping medium doing exactly what paper does at scale.

6. What the auditor actually looks for

Whoever is scrutinising the records — an assessor before signing, an insurer after an event, a fire authority on inspection — is asking the same four questions. Was every scheduled activity for every asset performed inside its window? Were the results within tolerance of the baseline? Was every defect notified, rectified, and retested? And can you show me, rather than tell me? A record system is fit for purpose exactly to the degree it can answer those questions on the spot, for any asset, without reconstruction.

7. What a digital logbook changes

A digital service record — sometimes written "log book", usually meaning the same thing — is not a scanned copy of the paper one. The structural difference is that the record is anchored to the asset rather than to the visit:

Every entry is timestamped and attributed at the moment of capture, on site, with the technician's identity attached — not written up later from memory in the van.
Evidence is captured inline. Photos of the asset as found, readings typed against the field that expects them, signatures on the device before anyone leaves.
The schedule is active, not passive. The system knows what was due, so a missed activity is a visible gap this week — found by the software before an auditor finds it, not eleven months later.
The history travels with the asset. Scan the tag and the device's whole life appears: every inspection, every defect, every close-out, the next due date.
The record is producible instantly — per asset, per building, or per portfolio — and the same live record is visible to the owner, so "who holds the complete set" stops being a question.
It cannot be left in a cupboard. Backed up, duplicated, and not subject to renovation.

The compliance obligation does not change. What changes is that the evidence chain assembles itself as a by-product of doing the work, instead of being a second job performed after it.

8. Moving off paper without losing the history

The transition is where good intentions stall, so three practical notes. First, the paper history does not need to be transcribed entry by entry — what must carry over is the asset register itself, the baseline data, open defects, and each asset's last service date, so that every cycle continues rather than restarts. Second, run the first full cycle treating the digital record as the master and the tags as the field artefact — the discrepancies that surface are the errors the paper system was already hiding. Third, keep the old books. They remain the evidence for the years they cover; retirement is not disposal.

9. How Maintenance Partners helps

In Maintenance Partners, the digital logbook is the asset record. Every AS 1851 activity is completed on the field app against the exact form for the asset's type and cycle, with photos, readings, and signatures captured on site — offline if the site demands it. The compliance engine measures every activity against its tolerance window, so gaps announce themselves. Defects flow from the inspection to the notice to the close-out in one record, and the owner sees the same live history through the client portal. When the assessor asks for the last twelve months, the answer is an export, not an archaeology project.

If the state of your service records is the thing you least want an auditor to ask about, that is exactly the problem we built for. Talk to the team for a walkthrough with your own asset list.

A note on jurisdiction

This article describes record-keeping as it applies under AS 1851 and Australian annual reporting frameworks in general terms. Specific record and retention requirements vary by state, by asset class section, and across editions of the standard. For sign-off on a particular building's records, consult a Competent Fire Safety Practitioner accredited for the measures involved.