SOG and SOP Development Guide for Fire Departments

SOGs Are How Your Department Operates

Standard Operating Guidelines (SOGs) and Standard Operating Procedures (SOPs) are the documented playbook for your department. They define how personnel are expected to respond, operate, and conduct themselves. Without them, every decision is made on the fly by whoever happens to be in charge. With them, there's a baseline of consistency that transcends individual officers, shifts, and experience levels.

SOG vs SOP: The Difference

• SOP (Standard Operating Procedure): A mandatory, step-by-step protocol. Deviation requires specific justification. Examples: SCBA inspection procedures, hazmat decon sequence, evidence preservation at fire scenes.
• SOG (Standard Operating Guideline): A recommended framework that allows officer discretion based on conditions. Examples: fireground ventilation tactics, apparatus placement, search priorities.

Most fire departments use a mix of both. Anything involving safety, legal compliance, or regulatory requirements should be an SOP. Tactical operations that require flexibility should be SOGs. The key: call them what they actually are. If an "SOG" has no room for judgment, it's an SOP. Label it correctly so members know the expectations.

What Topics to Cover

A comprehensive SOG/SOP library should address at minimum:

Emergency Operations

• Structure fire response and operations
• Wildland/urban interface operations
• EMS patient care protocols
• Hazardous materials response
• Technical rescue operations
• Incident command and accountability
• Mayday and firefighter rescue procedures
• Apparatus placement and positioning
• Radio communication protocols
• Water supply operations

Safety and Health

• SCBA use and air management
• Rapid intervention team (RIT) procedures
• Rehabilitation (NFPA 1584)
• Exposure tracking and reporting
• Infectious disease prevention (bloodborne pathogens)
• Fitness and wellness programs

Administrative

• Apparatus and equipment maintenance
• Training requirements and documentation
• Station operations and duties
• Personal protective equipment care and maintenance
• Driver/operator qualifications

How to Write Effective SOGs

1. Keep it concise. SOGs should be 1–3 pages maximum. If it's 10 pages, nobody will read it. If nobody reads it, it doesn't exist.
2. Use clear, direct language. Write at a level that a probationary firefighter can understand. Avoid jargon-heavy, overly technical language that obscures the intent.
3. State the purpose first. Why does this SOG exist? One sentence. Then get into the specifics.
4. Define roles and responsibilities. Who does what? If the SOG covers fireground ventilation, spell out the engine company's role vs. the truck company's role vs. the officer's decision authority.
5. Include "when this applies." Define the scope — what incidents or situations trigger this SOG.
6. Reference standards. Tie SOGs to NFPA, OSHA, or other national standards where applicable. This provides the legal foundation and shows the guideline isn't arbitrary.
7. Get input from the people who'll follow them. SOGs written in a chief's office without crew input face immediate resistance. Involve company officers and senior firefighters in the development process.

Review Cycle

SOGs are living documents — they must be reviewed and updated regularly.

• Annual review: Every SOG should be reviewed at least once per year. Assign each SOG a review date and an owner (typically the training division or a designated officer).
• Incident-driven review: After any significant incident, near-miss, or LODD, review the related SOGs. Did they work? Were they followed? Do they need revision?
• Standard updates: When NFPA, OSHA, or other standards change, review all affected SOGs for compliance.
• Version control: Date every revision, archive the old version, and ensure only the current version is in circulation. Nothing is worse than a crew operating on an outdated SOG.

Ensuring Compliance

The best SOGs in the world are worthless if nobody follows them. Compliance requires:

• Training on every SOG. Don't just publish it — train it. Hands-on when possible, classroom at minimum. Document that members received and understood the training.
• Accessibility. SOGs should be available on every rig, in every station, and on members' phones. If they can't find it, they can't follow it.
• Officer enforcement. Company officers must hold their crews accountable to SOGs. Ignoring non-compliance erodes the entire system.
• After-action review. After incidents, review whether SOGs were followed. If they weren't, determine whether the deviation was justified or represents a training/discipline issue.
• Member acknowledgment. Have members sign that they've read and understood new or revised SOGs. This creates accountability and legal documentation.

SOGs protect your members, protect your department, and establish the professional standard your community expects. Write them well, review them often, and train on them constantly.