Writing an AS 1851 service report a building manager will actually read

Most AS 1851 service reports are written for the technician who produced them. They are accurate, they are complete in the sense that every row has a tick, and almost nobody else can use them. The building manager opens an 80-page PDF, scrolls past the cover sheet and the hydrant tag list, cannot find the one thing that needs a decision, and files it. Three months later the same defect turns up in the next report, still unquoted and still unfixed.

The report is the only part of the service the client ever sees. It is how they judge whether you turned up, whether the building is safe, and whether your quote is worth approving. This guide covers who reads a service report and what each of them needs, what AS 1851-2012 actually requires you to record, how to structure a report so the important part is on page one, how to write defects that get fixed, and how a good report protects you as well as the client.

Who actually reads the report

A service report has several audiences, and they read it for different reasons. Writing for all of them at once is what produces the unreadable version. Writing in layers, so each reader finds their part quickly, is what produces the useful one.

Notice the pattern. The people with money and decisions want a short answer up front. The people with sign-off and enforcement responsibilities want the detail, and they want it organised so they can check it. A good report gives both, in that order.

What AS 1851-2012 actually requires you to record

Before talking about presentation, it is worth being clear about the minimum. The report is not optional decoration on top of the service. Records are a requirement of the standard, and in several states they are what the regulator, the certifier and the owner rely on.

The Building Commission NSW good practice guide (January 2026) is a useful plain-English summary of the requirements, and it applies AS 1851-2012 as the mandated maintenance standard for NSW buildings from 13 February 2026. Its main points on records and defects:

• Clause 1.16 of AS 1851-2012 sets out routine service records. Logbooks are required for each system, document inspection and test results on a pass or fail basis, reference the relevant section of the standard and the interval, and record defects found and corrective action taken.
• Logbooks must be accurate, legible and completed at the time of service. They can be digital, but the guide says a hard copy must be left on site at the end of the routine service, and that where electronic systems are used a printed and signed copy of the report is left on site.
• Where equipment is tagged or labelled (hydrants, hoses, hose reels, extinguishers, blankets and some passive items), a summary record goes to the responsible entity listing installed equipment, the work performed and any missing or defective items.
• Records are to be kept accessible for authorities, owners and other stakeholders, and the guide says they must be retained for a minimum of seven years.
• A yearly condition report, referenced in Appendix E of the standard, consolidates the year: condition and performance of each measure, outcomes of routine service and outstanding defects or non-conformances.
• Repairs are recorded too: the nature of the fault, what was done to rectify it and the date.
• A routine service done outside the permitted tolerance either side of its scheduled date is recorded as an out of tolerance activity and treated as a non-conformance.

The three outcomes, and when the owner must hear about them

AS 1851-2012 classifies findings as critical defects, non-critical defects and non-conformances, and clause 1.17.1 sets how quickly the responsible entity has to be told. The NSW guide summarises them like this:

Two things follow for report writing. First, a critical defect should never appear for the first time in a report that arrives a fortnight later. The report confirms and records a notification that has already happened, and should say when and to whom. Second, the classification is a judgement the technician makes on site against the standard, so the report needs enough detail for someone else to see why it was classified that way. Requirements and timeframes differ between states and territories, so check what your regulator and the building documents say for the site in front of you.

The structure of a report people use

The fix for an unreadable report is not less information. It is putting the information in the order people need it. Think of three layers: a one-page summary, a ranked defect register, then the detailed per-system results that form the record.

Layer one: a one-page summary

If the building manager reads nothing else, this page should tell them everything they need to act. It should fit on one page, and it should not contain a single clause number they have to look up.

• Site, address and the systems covered, with the visit date and the service interval performed (for example, six-monthly detection and alarm, monthly sprinkler).
• Overall status in one plain sentence: all systems operational, operational with defects, or one or more systems impaired.
• Critical defects, if any, with who was told, when, and what interim arrangement is in place.
• A count of non-critical defects and non-conformances, with a pointer to the register.
• Actions needed from the client, each with a reference: approve quote Q-1042, arrange tenant access to level 4, provide the missing block plan.
• Anything not tested and why (no access, tenant refused, system isolated by others), because an untested item is a gap the AFSS assessor will find.
• When the next service is due and which systems it covers.
• The technician’s name, licence or accreditation where relevant, and signature.

Layer two: the defect register, ranked by severity

Every defect and non-conformance from the visit goes into one table, sorted critical first, then non-critical, then non-conformance. Each line should stand on its own, so it can be copied into a committee paper or an email to an owner without the rest of the report. A good defect line has:

• A classification: critical, non-critical or non-conformance.
• A precise location that a stranger could walk to: building, level, room or grid reference, and what it is near.
• The asset ID that matches the tag on the equipment and the asset register, so it can be tracked across visits.
• What was found, in plain language, and what the consequence is if it is left.
• The recommended action, specific enough to quote from.
• At least one photo that shows the problem, not just the equipment.
• An indicative cost or a link to the quote, and whether it was raised on a previous visit.

Layer three: the detailed results

This is the record that satisfies clause 1.16, the certifier and the auditor: system by system, with the AS 1851 section and interval, each routine service activity, the result and the readings. It is long, and that is fine, because it is organised and nobody needs to read it to find out what is wrong. Put measured values in, not just ticks: pump pressures, flow results, battery voltages, detector sensitivity readings, door closing times where your procedure measures them. A number recorded this visit is what makes next visit’s number meaningful.

Before and after: one defect, written two ways

Here is the same finding, a damaged smoke detector in a strata car park, as it often appears and as it should appear.

The difference for the strata manager is immediate. The first version needs a phone call to understand. The second one can go straight to the committee with a recommendation.

The same applies to the summary page. Compare two openings:

• Weak: Six-monthly service completed. See attached logbook. Defects noted.
• Strong: Six-monthly detection and alarm service completed on 1 October. All systems operational. No critical defects. 3 non-critical defects and 1 non-conformance (register on page 2), quote Q-1042 attached for all three. Level 4 tenancy not accessed: 6 detectors untested, rebooking needed. Next service due April.

Plain language without losing precision

Plain language is not dumbing down. It means writing the consequence in words the reader already uses, while keeping the technical term for the people who need it. The certifier still needs to know it was a sprinkler valve set; the building manager needs to know the sprinklers on level 3 would not have worked.

• Lead with the effect, then the technical detail: “Fire doors on level 2 do not close fully (self-closer failed on FD-L2-03)”.
• Spell out abbreviations once. FIP, EWIS, MCP and FDCIE are second nature to a technician and noise to almost everyone else.
• Avoid vague verbs. Checked, inspected and attended say nothing about the result. Tested, passed, failed and measured do.
• Say what you did not do. Not accessed, isolated by others and out of scope are all legitimate, but they need to be explicit.
• Keep the AS 1851 section and interval references in the detailed results, where they belong, not in the summary.
• Use the same words for the same things every time. If it is a hose reel on page 3, it should not be an HRL on page 12.

Photos that prove something

A photo of a fire panel with no visible faults proves very little. A photo is evidence when it shows the specific condition being reported and lets someone else confirm it without going to site.

• Show the defect up close, then add a wider shot that shows where it is: the door number, the bay number, the riser.
• Include the asset tag in frame where you can, so the photo ties to the asset ID.
• Photograph gauges and displays so the reading is legible, which is better evidence than a typed number alone.
• For an obstruction or a damaged penetration, show the whole problem, not just a corner of it.
• After a repair, take the same shot again. Before and after pairs close out a defect cleanly.
• Leave out the photos that prove nothing. Twenty images of compliant extinguishers make the report longer and the defect photos harder to find.

Consistency across visits

One good report is useful. A run of consistent reports is far more valuable, because the client, the certifier and the next technician can compare them. That only works if each visit uses the same asset IDs, the same locations and the same structure.

• Keep a single asset register per site and use its IDs in every report. If an asset has been replaced, record that against the same location rather than inventing a new name.
• Carry open defects forward. A defect raised last visit and still present should show as still open, with the date first reported, not be rediscovered as new.
• Record readings in the same units and against the same reference each time, so drift is visible.
• Use the same report layout for every site and every technician. A strata manager with ten buildings will notice when one contractor’s reports all look the same and are all easy to read.
• Close defects explicitly. When something is fixed, say when, by whom, and link the completion record.

The common failures

Most bad reports fail in the same handful of ways. Every one of them is fixable, and most come from the reporting process rather than the technician.

How a good report wins work

Defects are where a maintenance contract earns its margin, and the report is the sales document for that work. A defect line that tells a building manager exactly what is wrong, where, why it matters and what it will cost is a quote they can approve in a few minutes. A defect line that says “replace” leaves them needing a phone call, a site visit and a revised quote, and that delay is often where the work goes to someone else or nowhere at all.

• Link every defect to a quote, or at least an indicative cost, so the decision is made from the report.
• Group small defects into one quote per visit where it makes sense, so the client approves once.
• Show history. A defect raised three visits in a row with no approval is a conversation worth having in writing.
• Keep the tone factual. A report that reads like an upsell is trusted less, and a clear one sells on its own.

There is also a quieter commercial benefit. Strata managers and facility managers with several buildings compare their contractors, and reports are what they compare. Clear reports are a reason to give you the next building.

How a good report protects the contractor

The same report that wins work is your best defence when something goes wrong. If a system fails in a fire, after an insurance claim or during a regulator’s inspection, the questions will be: did the contractor find it, did they tell the owner, and when.

• A defect recorded with location, photo and recommended action shows you found it.
• A recorded critical defect notification, with the time and the person told, shows you met the obligation to report it.
• Carried-forward defects with original dates show the owner knew and chose not to act.
• Explicit records of what was not tested, and why, stop a gap in access becoming a claim that you missed something.
• Readings rather than ticks show the service was actually performed, not just signed.

Frequently asked questions

Is a digital service report enough, or do I still need a paper logbook on site?

Records can be kept digitally, but check the local requirement. The NSW good practice guide says a hard copy must be left on site at the end of routine service, and where electronic systems are used, a printed and signed copy of the report is left on site. Other jurisdictions and individual buildings may set their own expectations, so confirm with the regulator and the building’s documents.

How long do service records need to be kept?

The NSW guide says routine service records must be retained for a minimum of seven years and be readily accessible to authorities, owners and other stakeholders. Requirements can differ elsewhere, so confirm the rule that applies to the site.

Should a critical defect wait for the report?

No. Under AS 1851-2012, as summarised in the NSW guide, the responsible entity is told before the technician leaves site, or as soon as possible, and the defect is confirmed in writing within 24 hours. The report records that this happened; it is not the notification itself.

What is the difference between a non-critical defect and a non-conformance?

A non-critical defect is an impairment or faulty component that is not likely to critically affect the system’s operation. A non-conformance is missing information or an incorrect feature that does not affect operation but is needed to support routine servicing, such as a missing block plan or an unlabelled valve. Both need to be reported to the responsible entity.

How long should a service report be?

As long as the detailed record needs to be, but the summary should fit on one page and the defect register should come straight after it. Length is not the problem; burying the decisions is.

Does the AFSS assessor rely on my report?

In NSW, the annual fire safety statement confirms that an accredited practitioner (fire safety) has assessed each measure, and the NSW guidance notes that AS 1851 routine service results may inform that assessment, though the two are distinct processes. A report with results, dates, readings and outstanding defects is far more useful to that assessor than one with ticks.

Should I include indicative costs in a compliance report?

Many contractors do, either as an indicative figure or as a link to a formal quote, because it lets the client make a decision from the report. Keep the compliance record itself factual and make it clear that the cost is a separate quotation the client can accept or not.

Sources and further reading

• Good practice guide for the inspection, testing, maintenance and repair of fire protection systems in NSW buildings, Building Commission NSW (January 2026)
• Responsibilities of building owners under AS 1851-2012, Building Commission NSW
• Fire safety certification, NSW Department of Planning
• AS 1851-2012 Routine service of fire protection systems and equipment, Standards Australia
• FSG-05 Maintenance of fire protection systems and equipment, ACT Fire & Rescue (August 2023)