The Law of Evidence on Site:
Mandatory Logbook Standards

In the technical landscape of Australian fire safety, there is a fundamental axiom that many facility owners learn far too late: If it isn't recorded in the logbook, the service never happened. This is no longer merely a matter of administrative preference. Since 13 February 2026, section 81A of the Environmental Planning and Assessment (Development Certification and Fire Safety) Regulation 2021 requires essential fire safety measures in NSW to be maintained in accordance with AS 1851-2012, and the records to be kept on site for 7 years. The logbook is now core evidence for your Annual Fire Safety Statement (AFSS) and your broader Work Health and Safety (WHS) compliance.

The fire safety logbook is, in essence, the "Black Box" of a building's mechanical history. It provides a chronological, tamper-evident record of the maintenance, testing, and periodic inspections required under **AS 1851—2012**. For the modern Facility Manager or PCBU (Person Conducting a Business or Undertaking), understanding the evolution of logbook standards is the difference between a seamless inspection and a compliance problem. The maximum penalty under section 81A is 600 penalty units for a corporation.

The Evidentiary Weight of Documentation

To understand the weight of a logbook, one must look at the way regulators like Fire and Rescue NSW (FRNSW) and local councils now approach building audits. In our experience, inspections increasingly start with the paperwork. An inspector will want to see the logbook early. This is because a physical inspection of a detector only tells the inspector that it exists today; the logbook tells them if it has been functional for the last twelve months.

Under section 27 of the **WHS Act 2011**, officers must exercise due diligence, which includes verifying that safety resources and processes are in place and used. Without an up-to-date logbook that follows the AS 1851 frequencies, a director has little evidence to point to. If a fire occurs, a system fails and the logbook is missing or incomplete, it will be very hard to prove the maintenance was done. You cannot easily argue due diligence on the basis of a missing record.

The Failure of the "Passive Service" Record

The most common problem we see in NSW facilities is the "Passive Service" record. This is when a contractor visits a site, performs the testing, and then takes the record of that service back to their head office, leaving nothing onsite. Section 81A is explicit: records required by AS 1851 must be kept **on site** for at least 7 years and made available to Fire and Rescue NSW or the council.

A digital report sitting in a contractor’s email inbox is not a compliant onsite logbook. Digital records are fine, but the core requirement is that the records are on site and accessible. If a fire officer arrives at 2:00 AM following a localised alarm and your security team cannot produce the logbook to verify the last maintenance of the EWIS (Emergency Warning and Intercommunication System), you have a problem.

AS 1851-2012: The Frequency Baseline

For a logbook to be considered "The Law of Evidence," it must precisely mirror the frequencies of **AS 1851-2012**. Since section 81A, this standard isn't a suggestion; it is the legal maintenance standard in NSW. Your logbook should show a continuous record across several key frequencies:

The "Gap in the Chain" is where the liability lives. If a building owner has 11 months of records but is missing the March inspection, there is no evidence that inspection happened. For that month, the system status is "Unknown", and that is a hard gap to explain to an inspector, an insurer or a court.

The Move to Digital Logbooks

The industry is moving toward digital, tamper-evident audit trails. Handwritten entries in a paper logbook are steadily giving way to QR-code-verified digital logs.

The reason for this is "Verification of Presence." For years, the industry suffered from the "Clipboard Hero"—technicians who would sign off on an entire floor's detectors from the comfort of the loading dock. Digital logbooks tied to NFC tags or QR codes on every asset help show that the technician was physically at the asset they are claiming to have tested.

For the PCBU, this is the ultimate tool for liability management. It allows you to monitor your contractors in real-time. You no longer have to wait for the end of the year to find out if your quarterly services were missed; the digital logbook provides a live dashboard of your compliance state.

The "False Security" of the Fire Indicator Panel (FIP)

Many facility managers believe that the internal logs of the Fire Indicator Panel (FIP) serve as their logbook. This is a technical error. While the FIP records "Event History" (alarms, isolations, and faults), it does not record "Service History." It cannot tell you if the dry-pipe valves were exercised or if the pump engine oil was changed.

The audit requirement is for a consolidated record that covers BOTH the electronic systems and the mechanical/passive systems. Your logbook must include the fire doors, the dampers, the intumescent seals around pipe penetrations, and the manual call points. Relying on the FIP log as evidence of total building compliance is like relying on a car's odometer to prove you changed the brake pads.

Actionable Steps for PCBUs and Facility Managers

To ensure your logbook stands up as a piece of legal evidence, you must implement the following three protocols immediately:

1. **The Onsite Audit**: Locate your physical logbook today. Is it in the FIP cabinet? Is it in the Manager's office? If it isn't on the premises, you are not meeting section 81A, which requires the records to be kept on site.

2. **The Metadata Check**: Open the last three service entries. Do they list the technician's name, their accreditation number, and the specific pass/fail result for every asset? A signature with "All Checked" is weak evidence.

3. **The Gap Analysis**: Compare your logbook entries against the baseline of AS 1851. Are the monthly, six-monthly, and annual milestones clearly defined, or is it a random collection of invoices?

Summary: From Paper to Proof

The era of the "She'll be right" logbook is over. In the 2026 regulatory environment, the logbook is your strongest defense or your heaviest liability. It is the narrative of your commitment to safety. When a major incident occurs, the courts will not look at your intentions; they will look at your ink (or your digital timestamp).

At Compliance Ready, we specialize in the "Audit-Ready" transition. We move facilities away from fragmented, missing, or unreliable records and into a state of continuous, reliable evidence. Don't wait for a Fire and Rescue NSW audit to discover your logbook is a liability. Make it the law of evidence that protects your business, your people, and your future.