Repairs & Maintenance
Fire Inspections: Why NSW Strata AFSS Reports Don’t Always Match
Conflicting fire inspection reports are common in NSW strata buildings. This explains why AFSS results change, what AS 1851 means, and how committees can keep better records.
· 13 min read

On this pageWhat the AFSS Actually MeansOn this page
- What the AFSS Actually Means
- Why Two Reports Don’t Match
- How Committees Make It Worse
- How to Actually Get Consistent Results
- What’s Really at Stake
- The Real Issue Isn’t the Inspectors
- What the statement is actually certifying
- Monthly, yearly, and the logbook
- How to reconcile two conflicting reports
- Access, e-bikes and the things the schedule never listed
- What to take to the AGM
- Who pays, and how fast
Fire safety compliance in NSW strata buildings tends to feel like nothing more than a yearly paperwork routine: the Annual Fire Safety Statement (AFSS) has to be lodged every year, no matter what. Most committees just get the inspection done, fix whatever's flagged, submit the statement, and forget about it until things get weird.
That’s usually when the building changes contractors, brings in a new strata manager, or even just seeks a second quote. Suddenly, last year’s “all clear” fails this time, while previous “issues” vanish completely from the new report. You’ve got two licensed professionals, looking at the same fire doors and sprinkler pipes, and they come back with totally different conclusions.
What’s a committee supposed to believe?
This is more common than people think, and it always surfaces at the worst moments, right before the AGM, when everyone wants a clean status and, instead, you’ve got a mess of conflicting reports. Some committees play it safe by fixing only what both reports agree on, ignoring the disputed stuff until next year. More than a few simply go with the cheaper report and cross their fingers. But neither strategy actually solves the core problem: what’s really up with the building’s fire safety?
What the AFSS Actually Means
An AFSS is supposed to confirm that every essential safety system, including alarms, hydrants, sprinklers, fire doors, all of it, actually works to the standard it’s meant to. The law is clear under NSW planning and fire-safety rules: strata committees, as owners, are responsible. Skip the statement, or let it lapse, and council can issue an order, slap on fines, and even take you to court. Insurance companies notice, too; messy or inconsistent AFSS histories can mess up a payout or policy renewal if anything goes wrong.
And, starting 13 February 2026, the rules get even tougher. Now, inspections and maintenance must exactly follow AS 1851-2012, Australia’s routine fire protection servicing standard. That means regular, structured checks; a physical logbook on site (not just scanned PDFs hiding in emails); baseline performance data for every system; and records kept for seven years. Some items that used to get yearly checks now need monthly servicing. But you don’t have to upgrade your actual fire systems, just prove, in writing, that you’re maintaining what’s already there.
That last bit is key. A huge chunk of inconsistency between reports comes down to missing or patchy records.
Why Two Reports Don’t Match
It’s tempting to chalk things up to one company being good, the other being sloppy or greedy. Sometimes, sure. But AFSS assessments have some baked-in pitfalls that have nothing to do with which company’s better.
The first big one? There’s no single, fixed standard for everything. If your building has an updated fire safety schedule, the inspector checks against it. If it doesn’t, or the schedule is ancient, the inspector has to figure out what standard applied when the equipment was installed. So, a fire door installed in 1991 gets checked against 1991’s rules, not today’s. That’s a messy research job, and two inspectors might (often reasonably) land on different conclusions, especially in older buildings missing documentation.
Baseline data also disappears during contractor changes. AS 1851 requires you to keep documented “normal” performance data for your systems, so you know when something falls out of line. But when you switch companies, those records don’t always transfer, or they show up in formats the new provider can’t use. The new contractor is stuck recreating the baseline from scratch. Different starting points, different conclusions, even if both are doing honest work.
And now the standards have gotten stricter. A report done before February 2026 uses looser benchmarks than one done after. So, the same building, with the same gear, could look like it’s declined in a single year, simply because the test changed.
Money also plays a role. Companies that both inspect and repair have a reason to find more defects. Others, trying to keep contracts or offer rock-bottom prices, tend to miss stuff and rush inspections. Committees reading these reports rarely have any real way to tell which incentive’s behind which findings.
Then there’s the simple fact that inspection depth varies. Some contractors open every door and check every smoke alarm; some just sample. Unsurprisingly, a deeper inspection turns up more issues. It’s not that the building’s worse, just that someone looked harder this time.
Practitioner skill and experience vary, too. The law only guarantees a minimum bar; some people in this space are just better than others at spotting problems and understanding what they’re reading in the test results.
And what “counts” as a problem changes all the time. New risks, like e-bike and scooter battery charging, weren’t on the radar in AFSS reports a few years ago, but now contractors flag them. So, your “suddenly bad” AFSS might just be a sign your inspector is up to date, not that something’s gotten worse.
None of this means you should just shrug off inconsistent reports. Sometimes, what gets missed is actually serious. There are documented cases where only a new contractor finally spotted critical defects that had been there for years. In one case, finding (and fixing) a missed defect ended up determining whether a sprinkler system really worked when there was an actual fire. The stakes aren’t just bureaucratic; they’re life-and-property level.
How Committees Make It Worse
When a report looks bad, the first instinct is to get another opinion, which is reasonable. Problem is, if you don’t supply the history and baseline, you just end up with one more disconnected report, a third opinion, not a tiebreaker. Now you’re juggling even more conflicting lists.
Lowball quotes for “same-day” certification should also raise eyebrows, not hopes. Proper inspections take time. If you go cheap, you’re paying for a shallower look, and that’ll catch up with you in the end.
Switching providers year after year or whenever the manager changes keeps resetting your baseline. Each new contractor starts fresh, making it look like you’re backsliding, even if nothing in the building’s actually changed.
Separating inspections into multiple site visits, a common move for “convenience”, rarely saves money in the long run and can let integrated problems slip by undetected, especially if defects only appear when the system is considered as a whole.
How to Actually Get Consistent Results
You’ll never get every inspector to see things identically, but you can drastically reduce the confusion.
Keep your fire safety schedule updated and hand it directly to new contractors; don’t make them hunt it down from council archives or prior managers. It’s your first line of defense against ambiguity, especially in older buildings.
Treat baseline data and service history as the building’s assets, not the contractor’s. From February 2026, you’re meant to keep that history on-site anyway. If all the info lives in one contractor’s system, you lose crucial evidence the moment you change providers.
Check who’s actually inspecting (and signing off) on your AFSS. Make sure they hold current fire safety practitioner accreditation and know exactly what they’re inspecting. Full access, or just a sample? Which systems? How did they decide on the benchmark numbers?
Read the report details. A strong report references specific clauses in AS 1851, includes photos, and explains failed measurements, not just “non-compliant” as a vague label. If you’re comparing two reports, the one with detailed evidence always carries more weight.
Don’t jump to a new provider every time for price alone. Building a long-term relationship with a good contractor, and keeping your data independent and transferable, is usually the surest way to stability and accuracy.
Help the inspection by making it easy for them: give plenty of notice to residents, use clear signage, make sure everyone in the building knows about the inspection window. Half the time, incomplete reports are the result of blocked access, not a rushed or lazy inspector.
Use your AGM for what it’s meant for: AFSS is now a required agenda item. Get the whole committee involved, put conflicting reports on the table, ask hard questions, and actually document which problems will be fixed and why. Don’t leave it up to the strata manager alone.
What’s Really at Stake
Defects that slip past can become much more than paperwork headaches. Councils have the power to force urgent repairs, hit you with escalating penalties, and, if you keep ignoring things, take you to court. But if you can show a well-documented maintenance history, even in a tough case, councils are far easier to negotiate with.
The Real Issue Isn’t the Inspectors
When you get two different reports, it’s easy to think the contractors can’t be trusted, or the whole AFSS system’s broken. Truth is, most buildings lack good, continuous records of their own fire safety. Every change of manager, provider, or even a misplaced file sets you up for conflicting results all over again.
This is a record-keeping problem first. That’s why tools like UnitBuddy exist: to give buildings a “memory” that survives committee turnover, manager swaps, and contractor changes. That way, your next fire safety inspection actually starts with what’s really there, not guesswork and lost paperwork.
What the statement is actually certifying
The AFSS is not a warranty that the building cannot burn. It is a statement, signed by a competent fire safety practitioner, that the essential fire safety measures listed on the building's fire safety schedule have been assessed and were capable of performing to the relevant standard at the time of inspection.
That schedule is the document councils care about. It lists each measure: sprinklers, hydrants, hose reels, detection, warning, emergency lighting, exit signs, fire doors, smoke-proof construction, stair pressurisation, and so on. If the schedule is missing, outdated, or still describes a 1990s system that was later modified, two honest inspectors will disagree because they are not inspecting against the same list.
The owners corporation lodges the statement with the local council and displays a copy on site. Late or missing lodgement is a council problem first, then an insurance problem. A "clean" statement built on a sample inspection and no logbook is still a statement. It is just a weak one.
Monthly, yearly, and the logbook
AS 1851-2012 is a servicing standard, not a design standard. It tells you how often to look at what you already have. Some measures need monthly or six-monthly attention. The AFSS is the annual wrap-up, not the only visit of the year.
From 13 February 2026, NSW expects that servicing to follow AS 1851 and that records live on site for seven years. A folder of emailed PDFs in the manager's inbox is not an on-site logbook. If the new contractor cannot see last year's pressures, door-gap measurements and isolation history, they will recreate a baseline. Recreated baselines are how "all clear" becomes "fail" without a single pipe moving.
Ask the contractor, in writing:
- Which fire safety schedule version they used
- Whether they inspected every measure or a sample
- Where the on-site logbook is, and who holds the keys
- What baseline data they inherited
- Which failed items are life-safety now versus paperwork to tidy this year
How to reconcile two conflicting reports
Do not pick the cheaper one. Do not average them. Line them up measure by measure.
- Put both reports next to the current fire safety schedule
- Mark items both agree fail. Those get quoted and fixed
- Mark items only one report fails. Ask that contractor for the clause, the measurement and a photo
- Mark items that vanished. Ask the new contractor why last year's defect is gone: repaired, reclassified, or not inspected
- If the dispute is about which historic standard applies to a 1991 door, pay a fire engineer for a short opinion. That costs less than two more competing AFSS reports
Record the committee's decision against each disputed line. "We will follow report B on fire doors because it cites AS 1851 clause X and includes measurements" is a defensible minute. "We went with the cheaper guy" is not.
Access, e-bikes and the things the schedule never listed
Half of incomplete inspections are access. Fire doors wedged open, cupboards locked, a resident who would not let anyone into the lot that contains a booster or a stair discharge. Give notice, post the dates, and treat refused access as a recorded defect of process, not a reason to skip the measure.
E-bike and scooter charging in lobbies, stairs and lots is now a common extra flag. It may not appear on a 2010 fire safety schedule. That does not make it imaginary. If a contractor photographs lithium batteries stored against a fire door, the committee has a safety decision to make: a by-law, a designated charging point, or a written reason for doing nothing. Ignoring it because "it is not on the AFSS form" is how the next report, and the next claim, gets worse.
What to take to the AGM
NSW now expects fire safety on the AGM agenda. Bring:
- The lodged AFSS and the date council received it
- The two reports, if they conflict, with the reconciliation table
- Open defects, quotes and which fund will pay
- Confirmation the logbook is on site
- The contractor's accreditation and contract end date
If owners only see "AFSS lodged — noted", they will discover the real list when a council order or an insurer's surveyor arrives. Put the list on the table while it is still a maintenance job.
Who pays, and how fast
Most AFSS defects are admin-fund maintenance: a door closer, a cracked exit light, a service visit. Replacing a fire panel, a hydrant booster or a full detection system is capital and should already sit in the 10-year plan. Mixing those two is how a "routine inspection" becomes an ambush special levy.
Life-safety failures do not wait for the next AGM. The committee should have a spending limit for urgent fire work and a rule that owners are told the same week. Cosmetic or documentary items — missing tags, an outdated block plan — can be batched. Treating every line as equally urgent is how the real ones get lost.
If two contractors disagree on whether a door must be replaced or only adjusted, pay for the measurement, not a third AFSS. A 10-minute engineer note citing the schedule beats another 40-page report that still does not choose.
Keep the practitioner's name and accreditation number with the statement. If council or an insurer later asks who signed, "the fire company" is not an answer. People move firms. The name on the AFSS is the name you need.
If council writes, answer with the schedule, the logbook extract and the open-defect list, not a promise to "look into it". A documented program of work is how an order stays a letter. Silence is how it becomes a fine.
Keep the scheme file in one place the committee and the manager can both open. Features, pricing, or book a tour.