What an Australian building inspection report needs to contain
31 July 2026 · 8 min read · Aiman Salem
Inspection reports in Australia are written to be read twice: once by the client who commissioned it, and once — sometimes years later, sometimes by a lawyer — by someone trying to establish what was and was not looked at. The second reader is the one who determines whether the report was any good.
This is a practical guide to the structure. It describes what reports generally contain and why, in our own words. It is not a substitute for the standards and guidance your own practice works to — check those, and work from the current editions.
The parts a report is expected to carry
Identification. Address, date and time of inspection, weather at the time and recently if it bears on what you saw, who the report was prepared for, who carried out the inspection and under what licence or registration. Weather is not filler: whether a site was dry or had three days of rain changes what a damp reading means and whether drainage could be assessed at all.
Scope and purpose. What the inspection was for, what was included and — at least as importantly — what was not. A pre-purchase inspection, a defects inspection during a build, a structural assessment of one element, and a dilapidation survey before neighbouring works are four different jobs with four different scopes, and a report that does not say which one it is invites the reader to assume the widest.
Limitations and accessibility. Covered below, because it is the section that carries the most weight.
Observations. What you saw, organised by area or element, with the photographic record attached to the finding rather than dumped in an appendix. Descriptive and factual.
Assessment. What the observations mean — significance, likely mechanism where you can support one, and whether something is a defect, a maintenance item, or normal for the age and type of construction.
Recommendations. What should happen, by whom, and with what urgency.
Photographic record. Captioned, located, and referenced from the findings they support.
The limitations section is the most important one
Inspectors treat limitations as boilerplate. Lawyers treat them as the first thing they read. Every dispute about an inspection report is, at bottom, an argument about whether something was within scope — and the limitations section is where that was decided, in advance, by you.
Two rules make it work.
Generic limitations protect nothing. "Areas that were inaccessible were not inspected" is true of every inspection ever performed and tells the reader nothing. "The subfloor was not entered: access hatch in the laundry was obstructed by stored goods and the crawl height at the hatch was approximately 300 mm" is a fact about this building on this day. The second one is a limitation. The first is a sentence.
Specific limitations belong where they happened. A general limitations section at the front plus the specific ones recorded against the relevant area — with the photograph of the obstructed hatch — reads as a record. Everything swept into an appendix reads as a disclaimer, and disclaimers get discounted.
The same applies to what an inspection type inherently does not cover: no opening up, no moving of stored goods or furniture, visual and non-invasive only, no comment on matters requiring a different discipline. Say it plainly and early rather than burying it.
Separate what you saw from what you concluded
The structural weakness in most reports is a single narrative that moves between observation, interpretation and recommendation without signalling the change.
"The eastern wall has stepped cracking to the mortar beds, up to 4 mm at the widest, extending from the window head to the eaves" is an observation. It is either true or false and it stays true. "This is consistent with foundation movement associated with the mature tree to the east" is an interpretation — supportable, arguable, and open to revision on further evidence. "Remove the tree" is a recommendation, and it commits your client to spending money.
When a second opinion arrives, the observations should be common ground and only the interpretation should be in contention. In a report that blends them, everything is in contention, and you end up defending your description of a crack.
Write recommendations someone can act on
"Further investigation recommended" is the most common sentence in Australian inspection reports and one of the least useful. Investigation by whom, of what, to answer what question?
A recommendation that works names the discipline (a structural engineer, a licensed plumber, a geotechnical engineer), the question to be answered, and the urgency relative to other items. "A structural engineer should assess the eastern wall to determine whether the cracking is ongoing; this should occur before settlement" gives the client something to do. "Further investigation recommended" gives them something to worry about.
Rank by urgency rather than by the order you walked the building. Clients act on the first three items in a list and skim the rest, which means the ordering is a safety decision, not a formatting one.
Make it navigable
Numbered sections, a table of contents with real page numbers, photographs numbered and referenced from the text, and consistent heading levels. This sounds like presentation and it is not: a fifty-page report that cannot be navigated will be read in full by nobody, including the person who eventually has to rely on it.
Consistency between reports matters as much as within one. When every report you issue has the same structure, a returning client finds what they need immediately, a reviewing engineer can compare two jobs, and you stop re-deciding the skeleton on every file.
Where the software fits
reportai.au drafts reports structured around AS 4349.1 — meaning the section skeleton and the kind of limitations wording an Australian residential inspection report carries, so you are not rebuilding that skeleton every job. It drafts from the evidence you captured on site and then checks for empty sections, leftover placeholder text and non-Australian spelling.
What it does not do is decide anything. It cannot tell you whether a finding is right, and it does not certify that a report complies with any standard — no software can. The draft is prepared for you to check, correct and sign, and the professional judgement in it is yours.
Written for practising inspectors and engineers. This is general guidance about documenting an inspection, not engineering advice about any particular building. reportai.au is software for writing reports — it does not carry out inspections, and it does not certify anything. Professional judgement stays with the person who signs the report.
More field notes · What reportai.au does · Pricing
Home · Pricing · FAQ · About · Field notes · Contact · Create an account · Sign in · Terms · Privacy · Refunds
reportai.au is a report documentation tool. It does not carry out inspections, does not assess or certify the condition of any building, and does not provide engineering services. Reports are AI-assisted drafts prepared for the inspecting engineer to check, correct, and sign off. All professional judgement remains yours.
Aiman Salem, trading as ReportAi.au · ABN 95 973 765 172 · admin@reportai.au · Prices in Australian dollars.