What AS 1851 covers
AS 1851 is the Australian Standard for the routine service of fire protection systems and equipment. It sets out how installed fire safety measures are inspected, tested and maintained once they are in service, and how the results of that servicing are recorded.
It is organised by system type. Portable extinguishers, fire hose reels, hydrant and booster systems, fire pumpsets, detection and alarm systems, special hazard systems, smoke control and sprinkler systems each have their own routine service requirements and their own records.
Two ideas run through the whole standard and shape how your checklists should be built: routine service happens at defined intervals, and the outcome of every routine service must be recorded, including any defect found and what was done about it.
Service intervals and why they drive your schedule
Routine service is defined at intervals - typically monthly, six-monthly, yearly and longer-cycle intervals such as five-yearly, depending on the system and the specific test item. A single site therefore carries several overlapping cycles at once, and different equipment on that site falls due at different times.
This is the single biggest reason spreadsheets break down. Tracking one annual visit per site is manageable. Tracking the correct interval per system, per device, across a portfolio of hundreds of sites is not.
In practice the fix is to attach the frequency to the asset rather than to the customer, and let the system generate the work order when the next service falls due. Always confirm the exact intervals and test items applicable to each system against the current edition of the standard and any additional requirements imposed by your jurisdiction.
What a routine service checklist should capture
Whatever the system type, a defensible record answers the same questions. Build your checklist so each of these is captured as structured data rather than free text in a comments box.
- Which asset - a unique identifier, its location on site, and ideally a barcode or QR tag scanned on arrival so the record cannot be attached to the wrong device.
- Which service level - the interval being performed, so a six-monthly routine is never confused with a yearly one.
- The individual test items - each with an explicit pass or fail result rather than a single overall tick.
- Evidence - photographs against failed items in particular, plus readings and measured values where the test requires them.
- Defects - recorded against the asset, described in plain language, classified by severity, with a photo attached.
- Who and when - the technician performing the service, their qualification where relevant, and the date and time of completion.
- Sign-off - technician sign-off on site, and where required, a customer or site representative acknowledgement.
Handling defects properly
A defect that is only written on a service sheet is a liability. It has been observed and documented, but nothing downstream is guaranteed to happen.
The workflow that actually closes the loop is: capture the defect against the asset during the routine service, quote the rectification, convert the accepted quote into a repair job, complete the repair with evidence, and mark the defect closed with that evidence retained on the asset history.
Two things follow from doing this digitally. Compliance improves, because outstanding defects are visible per site instead of buried in PDFs. Revenue improves too, because remedial work that used to be forgotten between the inspection and the office gets quoted.
Moving from paper to digital checklists
Most fire businesses start with printed schedules and a filing system, then move to spreadsheets, then hit the ceiling when the portfolio grows or a client asks for a defect register across all their sites.
A workable transition looks like this: build the asset register per site first, attach the correct service frequency to each asset, convert your existing paper checklists into configurable digital forms per asset type, then switch technicians to mobile capture with offline support so plant rooms and basements are not a problem.
Once that is running, reporting is a by-product rather than a monthly scramble. You can produce a per-site service record, an outstanding defect register, and a portfolio view of what is overdue, without assembling anything by hand.
This guide is general information about inspection record-keeping and software, not compliance or legal advice. Requirements vary by jurisdiction, building and system. Always work from the current edition of AS 1851 and the conditions applying to the specific building.
Frequently asked questions
- Is AS 1851 mandatory?
- AS 1851 is a standard rather than legislation in itself, but it is commonly referenced by state and territory building regulations, by fire safety statement requirements and by contracts with building owners. Whether and how it applies to a specific building depends on the jurisdiction and the approval conditions for that building, so confirm the requirement locally.
- How often do fire protection systems need routine servicing?
- Intervals are defined per system type and per test item, and commonly include monthly, six-monthly, yearly and longer-cycle requirements. Because different equipment on the same site falls due at different times, the practical approach is to store the frequency against each asset and generate work automatically as it becomes due.
- What records do I need to keep?
- You need to be able to show what was serviced, at what level, when, by whom, the result of each test item, any defect identified, and what was done to rectify it. Retaining the evidence - photographs, readings and sign-off - against the asset makes that record far easier to defend later.
- Can inspection checklists be digital?
- Yes. Digital checklists are generally easier to defend than paper because they enforce structure, timestamp entries, attach photos to the specific failed item and cannot be lost between the van and the office. Fieldmagic's checklists work offline and sync when the technician regains coverage.
- How does Fieldmagic help with AS 1851 servicing?
- Fieldmagic holds the asset register per site, schedules routine servicing at the frequency you set for each asset, gives technicians configurable pass/fail checklists on a native offline mobile app, captures defects with photos, converts those defects into remedial quotes and repair jobs, and produces per-site and portfolio compliance reporting.
Fire protection software
The full picture: asset registers, scheduling, defects and compliance reporting.
Australian compliance checklist
Download the printable checklist for Australian field service compliance.
Turn your paper checklists into digital ones
We will show you how your existing routine service sheets look as configurable Fieldmagic checklists, with defects flowing straight into remedial quotes.