Updating your department's standard operating guidelines

A brigade's standard operating guidelines are the quiet backbone of every callout, training night, and incident debrief. When they are current, clear, and aligned with how the team actually works, responders act with confidence and crews come home safely. When they gather dust or fall out of step with new equipment, new laws, or new tactics, the cracks appear in the worst possible moments.

Volunteer brigades across New South Wales, Victoria, Queensland, and beyond work with a mix of paid and volunteer personnel, ageing fleet, and changing conditions. Bushfire seasons have grown longer, structure fires hotter, and community expectations higher. A practical review checklist keeps the document alive rather than archived, and helps you tap into the wider volunteer firefighting community for shared learning.

Why routine reviews matter

Standard operating guidelines are not a one-and-done document. They should be a living file that mirrors brigade realities. Outdated procedures create confusion on the fireground, expose members to legal risk, and undermine training consistency across shifts. A documented review cycle — every twelve months or after any significant incident — protects the brigade, individual members, and the community served.

In Australia, every state has its own legislative backdrop. Work health and safety laws require employers and PCBUs (persons conducting a business or undertaking) to maintain safe systems of work, and volunteer organisations are not exempt. A routine review of SOGs is also a chance to align language and expectations with current AFAC guidelines, AIIMS incident management principles, and the Australian Fire Danger Rating System.

Assembling your review committee

A useful set of updated SOGs is rarely the work of a single person. Pull together a small committee that reflects the people who actually respond — a captain or group leader, a senior firefighter with operational experience, a junior or probationary member, and someone handling records and reporting. Newer members often spot gaps in wording that veterans stop noticing.

Set a realistic cadence — perhaps one Saturday morning meeting per month over a quarter — and assign clear ownership for each section. Where your brigade sits alongside a paid service, such as in regional Queensland or parts of regional Victoria, invite a liaison from that service so expectations on mutual aid, handover, and joint operations are captured accurately.

Mapping the existing documentation

Before rewriting anything, take stock of what you actually have. Pull every printed manual, laminated card, shared drive file, and old binder into one place. Note the date on each document and the version number where it exists. Many brigades discover they are operating from a mix of documents — some from a previous era of the service, some borrowed from neighbouring brigades, and some never formally adopted.

This is also a moment to consider equipment and fleet realities. Ladder configurations, slip-on units, breathing apparatus, and rescue tools have all evolved, and SOGs need to reflect the gear in the shed today. Looking for spare gear or replacement items at sensible prices can be made easier through overstock equipment listings, with similar Australian classifieds keeping fleets current within budget.

Aligning with standards and legislation

Standards and legislation shift more often than most brigades realise. Australian Standard AS 1851 governs routine servicing of fire protection systems, and volunteer brigades with structural response roles need to be familiar with its scope. State-based acts — such as the Rural Fires Act in NSW or the Country Fire Authority Act in Victoria — impose duties that should be reflected line by line in operating guidelines.

Funding and grant programs also carry their own compliance expectations. Whether you are applying for a community capability grant, a heavy vehicle replacement subsidy through NHVR, or state-level capacity funding, your SOGs may be assessed as part of the application. Understanding the practical difference between NOW and ICWP waivers can help when navigating the paperwork, even though most Australian programs run on different instruments.

Drafting, approving, and distributing

Once gaps and alignments are mapped, start drafting in plain English. Avoid legalese — SOGs are read by tired people in poor light at stressful scenes. Use short numbered steps, bold headings, and consistent formatting. Each section should answer three questions: who is responsible, what action is expected, and what the boundary is.

Approval should be a formal step, ideally minuted in a brigade meeting and signed off by the captain and a committee member. Once signed, distribute through every channel you have — printed copies in the truck, PDF on the brigade app or WhatsApp group, and a version-controlled copy in the cloud. Version control is non-negotiable: every change should be dated, and superseded copies should be clearly marked or removed to avoid confusion.

Training, drills, and continuous improvement

An updated SOG that nobody has rehearsed is just paper. Build the new guidelines into your next training cycle — even a quick walk-through at a Tuesday night training counts. Use scenarios drawn from local incidents: a grass fire heading toward a property at Doreen, a structure fire in a heritage building in Ballarat, or a motor vehicle accident on the Pacific Highway.

Schedule a feedback window after each drill. Junior members often surface wording that senior members gloss over. Capture every change request in a simple register, and review the register at your next committee meeting. This is how SOGs stay alive — not because someone wrote them, but because the brigade keeps using, questioning, and refining them together.

Share your revised guidelines with neighbouring services, post a summary on the brigade noticeboard, and invite feedback from members and partner agencies. If your brigade has a social media presence or community newsletter, run a short piece explaining what changed and why. Then set a date for the next review and put it in the calendar — the only thing worse than an outdated SOG is one updated once and then forgotten.