Fire Protection Business Software Australia: AS 1851 Compliance, Defect Notices, and Same-Day Invoicing in One Place
Australian fire protection contractors are technically skilled. The business side is what gets them. Two problems show up in every operation, from sole traders servicing extinguishers to mid-size contractors maintaining sprinkler systems across commercial portfolios: cash flow that drags because invoicing falls behind, and AS 1851 compliance records that pile up faster than they get filed. This post breaks both down and shows what purpose-built fire protection software actually does about each one.
Problem 1: Cash Flow
Materials hit your supplier account before the job is invoiced. Defect remediation quotes sit unsent while the building manager waits. Inspection cycles are predictable but invoicing is not. The gap between spending money and receiving it quietly drains working capital — even in a busy month.
Problem 2: AS 1851 Compliance
Every service visit under AS 1851 requires a written record. Every defect requires a notice. Annual fire safety reports must be signed and lodged. Records must be retrievable years after the visit. Paper, email, and spreadsheet tracking fails at volume — and the consequences when it does are not just administrative.
Why Australian Fire Protection Contractors Struggle with Cash Flow
The cash flow problem in fire protection is structural. Inspection contracts provide predictable work — quarterly, six-monthly, and annual visits scheduled months in advance — but the revenue from those visits is almost never collected on the day. The technician completes the inspection, writes site notes, drives to the next job. The invoice gets raised at the end of the week, or the end of the fortnight, or when the service report has been typed up and the building manager has approved the works. By then, the materials that went into that visit have already been charged to your supplier account.
For a fire protection contractor running 40 commercial buildings on annual inspection contracts, each visit generates materials usage — replacement detector heads, extinguisher refills, suppression components, hose reel fittings. Those materials are picked up from your supplier on the day of the job. They hit your trade account immediately. The invoice for the inspection visit that consumed them might not go out for another week. At scale, this creates a persistent gap between your outgoings and your income that does not show up as a profitability problem, because the business is genuinely profitable — but it shows up in the bank account on the 15th of the month when your supplier payment is due and several large inspection invoices are still outstanding.
Defect remediation compounds the problem. When a technician identifies a defect during routine inspection — a failed detector, a damaged sprinkler head, a hose reel that will not pressurize — the building owner needs a defect notice and a remediation quote before they can authorise the repair work. If the quote sits in a notebook or an email draft rather than going out the same day, the remediation job gets delayed. The delay pushes the invoice out further. Meanwhile, your technician has already spent time assessing the defect and your materials may already be ordered.
Quoting is its own time sink. A commercial fire protection quote requires a clear scope of work, correct materials costing, a labour estimate, and 10% GST applied to both. Without a system, this means returning to the office to build the quote, looking up current supplier pricing, writing the scope, and emailing it from a desktop. For a contractor doing six to eight site visits per week, each generating at least one quote, that is four to six hours of weekly admin that generates no billable revenue.
The inspection cycle billing gap
A contractor with 60 buildings on annual contracts and an average invoice value of $800 per inspection is managing $48,000 in annual contract revenue. If invoices go out an average of five days after each inspection, that is $6,500–$8,000 of revenue consistently in the billing pipeline rather than in the bank — not because the work is not done, but because the admin has not caught up.
The BAS adds a layer of exposure that compounds over time. GST at 10% must be applied correctly to both labour and materials on every invoice. The ATO's data-matching cross-references your reported GST collected against your supplier invoices and bank deposits. If your invoicing lives in a spreadsheet or a generic accounting tool that is not connected to your quoting and job management, discrepancies accumulate between what you report and what your supplier invoices show. A BAS query from the ATO costs a day to untangle — and if it reveals a pattern of underreported GST, the back-payment and penalties are significant.
Materials tracking at the job level is where most fire protection businesses lose margin quietly. A technician servicing three buildings in a day may stop at the supplier twice — once for planned materials, once for a replacement part they did not have on the van. Both purchases hit the trade account. If they are not logged against the specific building and job at the time of collection, they disappear into general overhead. At year end, the accountant sees the cost but cannot allocate it to a job. You cannot tell which inspection contracts are profitable and which are just keeping you busy.
The AS 1851 Compliance Documentation Burden
AS 1851 — Routine Service of Fire Protection Systems and Equipment — is the Australian Standard that governs the maintenance activities every licensed fire protection contractor performs. It specifies what must be inspected, tested, and recorded for each type of fire protection system, and at what frequency. It is not a voluntary guideline. Building owners have a legal obligation under state building regulations to maintain fire protection systems to the standard specified in their occupancy permit, and AS 1851 is the mechanism through which that obligation is discharged.
What this means in practice is that every service visit — every fire alarm check, every sprinkler inspection, every extinguisher service, every hydrant flow test — must produce a written record. The record must document what was inspected, the tasks performed, the test results, any defects identified, and the technician responsible. That record must be retained against the building and made available to the building owner and to the relevant fire authority on request.
A fire protection contractor maintaining 40 buildings — a realistic portfolio for a two-technician operation — might be running 200 to 300 individual service visits per year across quarterly, six-monthly, and annual inspection cycles. That is 200 to 300 individual AS 1851 service records per year, each needing to be created, issued to the building owner, and stored in a retrievable system. Paper logbooks at each site, or a shared drive folder organised by building name, work until they do not — and they tend to stop working precisely when the building changes hands, an insurance claim is filed, or a regulator asks for three years of records with two weeks' notice.
Defect notices: the most time-sensitive obligation
When a defect is identified during routine inspection — a faulty detector, a damaged sprinkler head, a fire door that does not close properly, a hose reel with insufficient pressure — the contractor is required to issue a defect notice to the building owner promptly. In practice this means the same day or within 24 hours. The notice must describe the defect, identify the system affected, and state the recommended remediation action.
The defect then remains open — and on your records — until remediation is confirmed. If your team completes the remediation, the follow-up job closes the defect in your system. If the building owner engages their own contractor to fix it, you need written confirmation before you can close it. In NSW, an open unresolved defect prevents an accredited practitioner from signing an Annual Fire Safety Statement for that building. In Queensland, a defect that poses an immediate risk to life triggers a mandatory notification to QFES directly.
Managing open defect registers across 40 buildings in a spreadsheet is possible — until someone is sick for a week, or a technician leaves, or the spreadsheet is on a laptop that dies. Fire protection software maintains a live defect register per building, automatically linked to the original service record and the defect notice, visible to every technician in the team.
State-by-state compliance requirements
| State | Authority | Annual requirement | Defect regime |
|---|---|---|---|
| QLD | QFES / QBCC | Essential Fire Safety report maintained per building | Defect notice issued to owner; QFES notification required for serious or immediate danger defects |
| VIC | FRV / CFA | Essential Safety Measures maintenance log maintained; annual ESM report for buildings subject to Building Regulations 2018 | Owner must maintain and act on defect records; serious defects notified to relevant fire authority |
| NSW | Fire and Rescue NSW | Annual Fire Safety Statement (FSS) lodged with council and displayed on building | Accredited practitioner signs FSS confirming measures are adequate; defects must be remediated before FSS can be issued |
| SA | SAMFS / CBS | Essential Safety Provisions maintenance report maintained per building | Defect notices issued to building owner; records maintained and available for inspection |
| WA | DFES | Maintenance records retained as a condition of occupancy permit; available for inspection | Records of defects and remediation retained per building |
NSW: Annual Fire Safety Statements
New South Wales has one of the most structured annual compliance requirements in Australia. Most Class 2–9 buildings in NSW must have an Annual Fire Safety Statement (FSS) prepared by an accredited practitioner and lodged annually with the local council. The FSS declares that every essential fire safety measure in the building has been assessed and found to be performing to the standard specified in the building's fire safety schedule.
The practical implication for fire protection contractors is that the full year's service history for each building must be current and accurate before the FSS can be signed. Any outstanding defects that have not been remediated create a problem: the accredited practitioner cannot sign the FSS in good conscience, and the building owner faces council enforcement if the FSS is not lodged. This means defect records need to be airtight, and remediation follow-up cannot be allowed to slip.
Fire extinguisher test records and hydrostatic testing
Fire extinguisher servicing generates two layers of records. The service tag on the extinguisher is the visible field record — but behind it, AS 1851 requires a service register maintained by the contractor documenting the service date, technician, condition of the extinguisher, and any recharging or parts replacement. Hydrostatic pressure testing — required every five years for most steel cylinders — produces a permanent test record: the pressure applied, the hold time, and the result. These records must be retained for the life of the cylinder.
A sole trader servicing extinguishers across 30 commercial tenancies, each with an average of four extinguishers, is managing 120 individual service histories plus hydrostatic test records scattered across a five-year rolling window. The practical failure mode is straightforward: hydrostatic test due dates get missed because they are tracked in a notebook rather than in a system that surfaces them automatically.
The record retrieval exposure most fire protection contractors underestimate
A compliance query can arise years after the work was done — when a building is sold, when an insurance claim follows a fire event, or when a coroner's inquest requires service records. If your records from three years ago are in a shared drive folder that no one has organized since the technician who created them left the business, they are not retrievable in any meaningful sense. Software that stores records against the building, the system, and the technician makes retrieval a search rather than an excavation.
What Purpose-Built Fire Protection Software Actually Fixes
Generic small business software — accounting tools, spreadsheets, generic invoicing apps — was not built around the fire protection maintenance workflow. It does not know what AS 1851 is. It cannot generate a defect notice. It cannot link a hydrostatic test record to a specific extinguisher at a specific site. The gap between what generic software provides and what a fire protection business needs is precisely where both problems live and compound each other. Purpose-built fire protection software closes that gap specifically.
Quotes sitting unsent while the building manager waits
Build a GST-inclusive quote from your phone before you leave the site. Labour rate applied automatically; materials logged against the job. Send before you drive away.
Invoices following days after inspection completion
Convert the completed service visit to a tax invoice in one tap. 10% GST is itemised correctly on both labour and materials every time — no BAS reconciliation surprises at quarter end.
AS 1851 service reports typed up after the fact
Generate AS 1851-compliant service reports from the job record on completion. System type, tasks performed, defects found, technician details, and building address are pre-filled. Send to the building owner and retain the record automatically.
Defect notices issued late or tracked in a spreadsheet
Issue defect notices from the app at the time of inspection. The defect is logged against the building, the notice is sent to the owner, and the open defect is tracked in your system until it is remediated and closed.
Timesheets done on Friday from memory
Technicians clock in and out from their phone, per job. Superannuation at 11.5% is calculated automatically per pay run — no manual spreadsheet step.
Materials absorbed into overhead with no job allocation
Log suppression heads, detectors, extinguisher refills, and hose reel parts against each job at the time of use. Know your margin per job before the invoice goes out.
The compound effect matters more than any single feature. When quotes go out on site, invoices follow on job completion, AS 1851 service reports are generated from the job record rather than typed up separately, defect notices are issued at the point of discovery, and materials are logged at collection — the two problems stop feeding each other.
Consider a typical Thursday for a two-technician fire protection operation: morning quarterly inspection of a commercial office block (fire alarms, emergency lighting, extinguishers), midday remediation of a defect found last month at a strata complex, afternoon annual inspection of a retail tenancy. Each generates a service record obligation. The office block visit found two faulty detectors — a defect notice needs to go to the building manager today. The strata remediation closes an open defect from last month's service report. Without software, by 5pm none of the records are filed, the defect notice has not been issued, and the invoices for two completed visits are sitting in someone's head waiting for a report to be typed. With software, the technician logs everything on-site: the service record is generated on completion, the defect notice is issued from the app, the completed remediation closes the open defect, and the invoices go out the same afternoon.
What to Look for in Fire Protection Software
Not all field service management tools are built for the Australian fire protection industry. Before committing to a platform, verify it covers these specifically:
- Australian GST compliance — 10% on both labour and materials, with a BAS-ready summary at quarter end
- AS 1851 service report generation — structured report output from job data, sent to building owner on completion
- Defect notice generation — issued from the app at the time of discovery, tracked per building until remediated
- Open defect register — live view of unresolved defects per building, linked to the original service record
- Annual inspection cycle scheduling — automatic surfacing of upcoming inspection windows per building per system
- Hydrostatic test due date tracking — per extinguisher, per cylinder, with automatic upcoming due date alerts
- Fire extinguisher service register — full service history per extinguisher per site, separate from the physical tag
- Sprinkler and fire alarm test result capture — numerical test data logged per visit, not just pass/fail
- Building portfolio view — all buildings, all open defects, all upcoming visits in a single view
- Superannuation calculation — 11.5% calculated automatically from timesheet data per pay run
- Mobile-first design — the full workflow must work from a phone or tablet on-site, not just from a desktop in the office
- Record retention in the cloud — records stored against the building, not on a local device or physical folder
Any platform that misses even one of these will require a workaround. Workarounds are where both problems — cash flow drag and compliance exposure — come back.
Frequently Asked Questions
What is AS 1851 and what does it require for fire protection maintenance?
AS 1851 is the Australian Standard for Routine Service of Fire Protection Systems and Equipment. It specifies the minimum inspection, testing, and maintenance activities for each type of fire protection system — fire alarms, sprinklers, hydrants, hose reels, extinguishers, suppression systems, and more — along with the required frequency (monthly, quarterly, six-monthly, or annual, depending on the system). Every service visit under AS 1851 must produce a written service record documenting what was inspected, what tasks were performed, any defects found, and the technician responsible. These records must be retained per building and made available to the building owner and relevant authorities on request.
How often do fire protection systems need to be serviced under AS 1851?
Service frequency under AS 1851 depends on the system type. Fire extinguishers typically require six-monthly service visits and an annual inspection. Automatic sprinkler systems (AS 2118) require monthly, quarterly, and annual tasks at different intervals. Fire detection and alarm systems (AS 1670.1) require routine inspection and testing at least every six months for most components, with some elements tested annually. Emergency warning and intercommunication systems have similar schedules. A fire protection contractor managing multiple commercial buildings simultaneously will have overlapping inspection cycles running every month of the year — which is exactly where a paper-based tracking system starts to fail.
What is a defect notice in fire protection and when must it be issued?
A defect notice is a written notification to the building owner or manager when a fault or non-compliance is found with a fire protection system during routine service. Under AS 1851 and the relevant state building regulations, the contractor who identifies the defect is required to issue the notice promptly — in many cases on the same day as the inspection. The notice must describe the defect, the system affected, and the recommended remediation. Open defects must be tracked until remediation is confirmed. In NSW, an accredited practitioner cannot sign an Annual Fire Safety Statement while known defects remain unresolved. Losing track of open defects across multiple buildings creates both compliance and legal exposure.
What is an Annual Fire Safety Statement in NSW and who can sign it?
An Annual Fire Safety Statement (FSS) is a document required under the Environmental Planning and Assessment Regulation 2021 for most Class 2–9 buildings in NSW. It must be prepared by an accredited practitioner — typically a fire protection contractor holding the relevant accreditation — and lodged annually with the local council. The FSS declares that each essential fire safety measure in the building has been assessed and found to be performing to the standard required by its current fire safety schedule. Any known defects must be remediated before the FSS can be signed. Buildings that fail to lodge a valid FSS face council enforcement action. Fire protection software that maintains a complete service and defect history per building makes FSS preparation straightforward rather than a multi-day records chase.
What are Essential Safety Measures in Victoria and who maintains the records?
Essential Safety Measures (ESMs) are the fire and safety systems in a building that are required to be kept operational under Victoria's Building Regulations 2018. They include fire sprinklers, smoke alarms, emergency lighting, exit signage, fire doors, and fire hydrants, among others. The building owner is legally responsible for ensuring ESMs are maintained, but in practice they engage licensed fire protection contractors to perform the maintenance under AS 1851. The contractor produces the service records; the building owner must retain them. An annual ESM report is required for most commercial buildings, summarising maintenance activities and confirming the systems are performing adequately. Fire Rescue Victoria and the Country Fire Authority have powers to inspect these records.
What licence do I need to work as a fire protection contractor in Australia?
Licensing requirements vary by state. In Queensland, fire protection work typically requires a QBCC licence. In Victoria, contractors working on fire protection systems under the Building Regulations must hold the relevant occupational licence from the Victorian Building Authority (VBA). In NSW, the Fire Protection Association Australia (FPAA) operates an industry accreditation scheme, and some work requires a contractor licence under the Home Building Act 1989. In South Australia, consumer and business services licences apply. In WA, contractor registration is required for certain building work. Before taking on commercial fire protection maintenance contracts, confirm the specific licence or accreditation required in each state you intend to operate in.
How does the Queensland Essential Fire Safety regime work?
Queensland's building fire safety obligations are governed by the Fire and Emergency Services Act 1990 and the Building Fire Safety Regulation 2008. Building owners must maintain fire safety installations to the standard required at the time of occupancy. Regular maintenance under AS 1851 is the practical mechanism for meeting this obligation. Fire protection contractors who identify a serious defect — particularly any that creates an immediate risk to life — are required to notify Queensland Fire and Emergency Services (QFES) directly, in addition to issuing a defect notice to the building owner. This dual-notification obligation for serious defects distinguishes Queensland's regime and adds a compliance tracking dimension that software needs to support.
What does AS 1670 cover and how does it affect fire alarm maintenance records?
AS 1670.1 is the Australian Standard for Fire Detection, Warning, Control and Intercom Systems — System Design, Installation, and Commissioning. AS 1670.3 covers smoke alarms and heat alarms in residential buildings. The maintenance requirements for systems installed to AS 1670 are specified in AS 1851, which prescribes the inspection and testing frequencies for detectors, sounders, control panels, isolators, and interconnections. Each maintenance visit must be documented: what was tested, the test results, any faults identified, and corrective action taken. For a contractor maintaining fire alarm systems across 20 or 30 commercial buildings, that documentation load accumulates quickly — and a paper logbook at each site is not a retrievable system when you need to answer a regulator's question.
What does AS 2118 require for fire sprinkler system maintenance?
AS 2118 is the series of Australian Standards covering automatic fire sprinkler systems (residential, combined, rural, and special hazard). Maintenance of installed sprinkler systems is governed by AS 1851, which requires monthly, quarterly, six-monthly, and annual tasks depending on the component — pump set operation tests, pressure gauge checks, valve inspections, flow tests, and system pressure tests, among others. Every test result must be recorded. Water supply tests in particular produce numerical readings (pressure, flow rate) that must be documented against a known baseline. If the readings fall outside the acceptable range, a defect notice is required. For contractors maintaining large strata complexes or commercial properties with multiple sprinkler zones, this generates hundreds of data points per year that need to be stored against the building and retrievable on demand.
How do I manage fire extinguisher test tags and hydrostatic testing records?
Fire extinguishers require six-monthly service inspection and an annual internal inspection (for most types) under AS 1851. A physical test tag is attached to the extinguisher after each service — but the tag is only the field record. The contractor must also maintain a service register per extinguisher per location, recording the service date, the technician, the condition findings, and any recharging or parts replacement. Hydrostatic pressure testing is required at intervals specified by AS 1851 (typically every five years for steel cylinders). The test result — the applied pressure and the outcome — must be retained as a permanent record for each cylinder. Fire protection software stores the full service history per extinguisher, per location, so test due dates are automatically surfaced and records are retrievable without hunting through paper registers.
How does 10% GST apply to fire protection invoices in Australia?
GST at 10% applies to both labour and materials on Australian fire protection invoices. A tax invoice in the ATO's required format must include your ABN, the words "Tax Invoice," the GST amount itemised or a statement that the total price includes GST, and the recipient's details for invoices above $1,000. The ATO's data-matching now cross-references reported GST collected against bank deposits and supplier invoices. If your quoting and invoicing live in a spreadsheet or disconnected apps, discrepancies accumulate between your BAS submissions and your supplier records. Purpose-built fire protection software applies 10% GST automatically to every line item and produces a BAS-ready GST summary at quarter end — removing the manual reconciliation step.
What superannuation rate applies to fire protection employees in FY2025-26?
The Superannuation Guarantee rate for FY2025-26 is 11.5% of ordinary time earnings. It applies from an employee's first day of employment with no minimum earnings threshold. Most fire protection technicians in Australia are covered by the Fire Protection Industry (OHS, Quality and Environmental) Award 2010 or, for some installation work, the Building and Construction General On-site Award. These awards specify minimum pay rates, overtime classifications, and allowances for travel, uniforms, and confined-space or height work. Timesheet software that maps clocked hours to the correct pay classifications and calculates super automatically reduces Fair Work underpayment exposure — now a personal liability risk for business owners under wage theft provisions.
How do I track defect remediation across multiple commercial buildings?
Tracking open defects across a portfolio of commercial buildings is one of the highest-risk admin tasks in a fire protection business. A defect found during a quarterly inspection must be notified to the building owner, tracked through to the point where remediation is either completed by your team (generating a follow-up job) or confirmed by the owner's own contractors. Until the defect is resolved, it remains your documented obligation. In NSW, an open defect prevents FSS sign-off. In Queensland, a serious unresolved defect may trigger a QFES notification obligation. Fire protection software maintains an open defect register per building, linked to the original service record and the defect notice. When the remediation job is completed, the defect is closed and the record is updated — so nothing falls through between inspection cycles.
Can fire protection software generate AS 1851 service reports?
Yes — generating service reports directly from the job record is one of the most time-saving features in purpose-built fire protection software. Rather than typing up a report after the fact from handwritten site notes, the technician logs their inspection findings, test results, and defects on the mobile app during the visit. On job completion, the software generates a structured service report pre-populated with the building details, system type, tasks performed, and any defects noted. The report is sent to the building owner immediately and a copy is retained in the system against the building record. This eliminates the after-hours report-writing session that most fire protection contractors currently do the evening after a busy inspection day.
What are the record retention requirements for fire protection maintenance records?
Record retention requirements vary by state but the practical standard across Australia is that AS 1851 service records, defect notices, and remediation records must be retained for the life of the building — or at minimum for seven years, which aligns with the general commercial record retention standard under the Corporations Act. In practice, records need to survive property sales, changes of ownership, insurance claims, and regulatory audits that may arise long after the work was completed. A fire protection contractor who holds these records only in a paper logbook at the site, or in a filing cabinet in their office, faces significant retrieval risk. Software that stores records in the cloud against the building, the system, and the technician makes retrieval a search rather than a physical archive exercise.
Is fire protection business software worth it for a sole trader doing extinguisher servicing?
Fire protection software is often most valuable for sole traders, because there is no admin staff to handle the quoting, invoicing, service report writing, defect notice issuing, and scheduling that the business generates. A sole trader servicing extinguishers across 30 commercial tenancies has the same compliance obligations per visit as a larger contractor — AS 1851 service records, test tag records, defect notices where applicable, GST invoicing, and super on any employees — but no one to manage them. Software compresses that admin into a few taps per job rather than a Friday catch-up session that never quite catches up. The other benefit for sole traders is scheduling: service contract renewals, six-monthly visit windows, and hydrostatic test due dates are surfaced automatically rather than tracked in a wall planner.
How do annual inspection cycles affect cash flow in a fire protection business?
Annual and six-monthly inspection cycles create a predictable but lumpy revenue pattern. A contractor with 60 buildings on annual contracts might complete 5 inspections in one week and none the next, depending on how contracts were staggered at sign-up. The problem compounds when invoicing lags behind: a day of inspections generates the work but the invoices might not go out until the following week, or later if the technician's site notes are incomplete and the report needs to be typed up. Materials — replacement extinguisher cylinders, suppression heads, detector modules — hit the supplier account the day they are picked up. The gap between spending money on materials and receiving payment for the job those materials went into can stretch to 30 or 40 days in a poorly managed billing cycle. Fire protection software that enables same-day invoicing on job completion — with materials already logged against the job — compresses that gap significantly.
TPT Field Service — Built for Australian Fire Protection Contractors
Quotes, GST invoicing, AS 1851 service reports, defect notice generation, open defect tracking, extinguisher service registers, inspection cycle scheduling, timesheets, and materials tracking — in one platform built around the Australian fire protection workflow.