Fire department SOPs and SOGs: keeping policy usable

Updated July 2026 · about a 5-minute read

Every department has SOPs and SOGs. Far fewer have SOPs and SOGs their members have actually read, that reflect how the department operates today, and that anyone could find in under a minute. A binder of policy nobody opens isn't protection — it's a false sense of it.

SOP vs. SOG — and why it matters

A Standard Operating Procedure spells out a required, step-by-step way of doing something; a Standard Operating Guideline gives direction while leaving room for judgment on scene. The distinction matters legally and operationally — "procedure" implies you must, "guideline" implies you generally should. Departments use both; what counts is that each document is clear about which it is.

Why they're worth the effort

• Safety and consistency — everyone operates the same way, which is what keeps people safe on the fireground.
• Training — SOPs/SOGs are the backbone of how you onboard and drill members.
• Liability — after an incident, "what's your policy, and did you follow it?" is one of the first questions asked.
• Accreditation and grants — documented, current policy is table stakes for both.

Where policy programs break down

• The binder is at the station, so nobody references it when it would help.
• Documents go stale — a procedure references apparatus you sold two years ago.
• There's no clean record of who acknowledged which policy.
• Finding the right SOP means flipping through a tab-divider binder instead of searching.

Keeping them alive

1. Put them where members already are. Policy on the same device as the roster and the incident report gets read; a binder in the office doesn't.
2. Make revisions painless. If updating a procedure is easy, it'll actually stay current.
3. Review on a schedule. A standing review cycle catches the drift before it becomes a problem.
4. Keep it searchable. The right SOP should be a search, not a scavenger hunt.