Blog › Compliance Checking

BAL Ratings and AS 3959: Making Drawings Match the Bushfire Assessment

ParitySense team · September 2026 · 6 min read

A BAL (Bushfire Attack Level) rating is the classification a bushfire assessment assigns to a site under AS 3959 — from BAL-LOW through BAL-12.5, BAL-19, BAL-29 and BAL-40 up to BAL-FZ — and AS 3959 specifies the construction requirements each level triggers for buildings in bushfire-prone areas. The assessment is a single report. Its consequences are not: they land in the window schedule, the external door schedule, the deck and subfloor details, the roof details, the services penetrations and the specification — documents owned by different consultants, revised on different cycles. BAL compliance is therefore not a design problem; it is a flow-through problem, and the flow-through is where sets fail.

One report, many landing sites

Take a project assessed at BAL-29. The standard specifies, at that level, requirements across the building envelope; the documentation consequences look like this:

• Windows and external doors. The window schedule must specify units compliant for the assessed level — the standard sets requirements for glazing, frames and screening that vary by BAL. A schedule row reading W07 — aluminium awning, 6 mm float on a BAL-29 job is a finding, regardless of what the bushfire report says, because the report cannot install itself. This overlaps with the AS 1288 safety glazing check — the same schedule row carries both obligations.
• Roof and sarking. Roofing details must show the sealing, sarking and ember-protection measures the level requires. Standard details reused from a non-bushfire project are the usual offender.
• Decks and subfloor. Decking materials, supports and the treatment of the subfloor space are BAL-dependent. Deck details are frequently architectural standards sheets that predate the bushfire report.
• Gaps, vents and penetrations. Ember protection drives screening and sealing requirements on vents and penetrations — typically documented, if at all, in a specification clause nobody maps to the mechanical and hydraulic penetration schedules.
• The specification. The spec should invoke AS 3959 at the assessed level and align its window, door, roofing and timber clauses accordingly. A spec that says "BAL as per bushfire report" without flowing the requirements into its trade sections has delegated the problem, not solved it.

Reconciling the set against the assessment

1. Register the assessment. The bushfire report is a controlled document with a revision, in the drawing register like everything else. Its assessed level (and any per-elevation breakdown) is the reference value for every check that follows.
2. State the BAL on the drawings. The assessed level belongs on the cover sheet, the site plan and each schedule it constrains. A reviewer who has to leave the drawing set to learn the project's BAL will sometimes not bother; certifiers notice the omission.
3. Map the landing sites. List every document that carries a BAL-dependent requirement: which schedules, which details, which spec sections. This map is what turns a reassessment from a scramble into a checklist.
4. Compare element by element. For each external opening, deck, roof junction and penetration: does the specified product or detail meet what the standard specifies for the assessed level? Where the answer requires interpreting the standard's tables, the finding should cite the schedule row and the assessment, and phrase the requirement qualitatively — "BAL-29 imposes screening and glazing requirements this row does not evidence" — for a human to close out. Asserting exact table values from memory is how checkers get burned; the standard specifies them, and the reviewer confirms them.
5. Re-check on revision of either side. A new window schedule revision, or a new assessment revision, re-opens the comparison for the affected elements. Revision-triggered re-checking is the mechanism — the same one that drives every discipline in the ParitySense check suite — and it is the difference between "checked once at DA" and "checked against what we're actually building".

Why this one is worth doing properly

Bushfire construction requirements exist because the failure mode is catastrophic, and the compliance regime reflects that: bushfire-prone-area determinations are statutory, certifiers check BAL documentation closely, and post-fire investigations read the paper trail. But the practical, unheroic reason to reconcile the set is commercial: BAL-rated windows, doors and roofing carry long lead times and real price premiums. A schedule that under-specifies gets caught at certification and reprocured at crisis prices; one that over-specifies (the whole house at BAL-40 "to be safe") hands away margin on every opening. The assessment already contains the right answer per element. The work is making every document agree with it — which is the whole argument of the compliance checking guide in one discipline.

FAQ