Your Fire Department SOPs Aren’t the Problem. Your Policy System Is.

When Was the Last Time You Looked at the Whole System?

Most fire departments have policies. They have SOPs. They have SOGs. They have general orders, training memos, forms, checklists, and documents that have accumulated over years of operation.

The better question is whether all of those documents still work together as a system.

Think about the last time your department updated an SOP. Maybe an apparatus changed. Maybe a new piece of equipment went in service. Maybe an incident exposed a problem. Maybe a regulation changed, a new chief took over, or someone finally noticed that a document had not been touched in years.

That individual policy may have been corrected.

But what about everything connected to it?

A policy manual rarely becomes outdated all at once. It happens one document at a time. Terminology changes in one policy but not another. An apparatus designation gets updated in three SOPs but remains outdated in six others. A new operational practice gets implemented on the training ground but never makes it into the written procedure. Two documents address the same subject differently. An old policy remains active because nobody is sure whether it was ever formally replaced. Responsibilities still belong to a position that no longer exists. Forms referenced in an SOP cannot be found. Revision dates disappear, and eventually nobody can confidently say which version is current.

Individually, each issue may seem minor.

Collectively, they can create a policy system that no longer accurately reflects the department it is supposed to guide.

That is why reviewing fire department policies one document at a time is not always enough. At some point, somebody has to look at the entire system and ask whether the pieces still fit together.

Can your personnel easily locate the current policy?

Do your SOPs and SOGs use consistent terminology?

Do written procedures reflect how your department actually operates today?

Do policies contradict one another?

Can you identify when each document was last reviewed, what changed, who approved it, and which version is currently in effect?

Are there operational or administrative areas that simply are not addressed at all?

If those questions are difficult to answer, the problem may not be one outdated SOP.

The problem may be the system behind it.

Policy Drift Happens Slowly

Most departments do not intentionally build a dysfunctional policy system. It usually happens gradually.

Policies are added as new problems arise. Existing SOPs are revised after incidents. New equipment creates new procedures. Chiefs change. Officers promote. Apparatus is replaced. Mutual-aid agreements evolve. Standards and regulations change. Documents written years apart begin using different terminology and formatting.

Sometimes, departments also inherit or borrow policies from other organizations.

There is nothing inherently wrong with reviewing another department’s SOP or SOG when developing your own. Fire departments regularly learn from one another, and there is little value in reinventing every administrative concept from scratch. The problem begins when another organization’s policy is copied without being thoroughly adapted and validated for the department that intends to use it.

I have personally seen how far that can go.

At a department where I previously worked in western South Dakota, portions of the department’s hazardous materials procedures had apparently been copied from an organization in another state. Buried within those procedures was direction stating that, in the event of a hazardous materials incident, the department should request mutual aid from the Bangor Fire Department.

Bangor, Maine.

The department operating under that SOP was roughly halfway across the country.

That is an extreme example, but it illustrates a much larger problem. A policy can look professional, contain appropriate terminology, and occupy a place in an official manual while still being completely disconnected from the organization that supposedly operates under it.

Copied language may contain the wrong department names, apparatus designations, staffing assumptions, mutual-aid partners, radio procedures, organizational positions, response capabilities, laws, equipment, or operational expectations. Some errors are easy to spot. Others can remain buried until someone actually needs the procedure.

And that is where this stops being a formatting problem.

If an SOP directs personnel to contact an agency that is more than a thousand miles away, what else in the manual has never been validated?

Are mutual-aid resources correct?

Do the listed capabilities actually exist?

Are referenced positions still part of the organization?

Do personnel understand what the procedure expects them to do?

Does the policy reflect the department's current equipment, staffing, geography, and response model?

Problems like these can also damage confidence in leadership. Firefighters expect the policies governing their work to be relevant, accurate, and applicable to their department. When personnel discover obviously copied or outdated language in an official document, it can make leadership appear inattentive, unprepared, or disconnected from the systems they are responsible for maintaining. In severe cases, it can make the organization look incompetent to its own members, neighboring agencies, governing officials, or anyone else reviewing those documents.

A mistake like that can undermine confidence in far more than a single document. It suggests that the policy may have been adopted without a meaningful review of whether it was appropriate for the organization in the first place.

Departments do not need every policy to be written entirely from scratch. They do need every policy to become their policy before it is placed into service.

That means reviewing the language, validating local resources and responsibilities, checking references, reconciling the document with related policies, and confirming that what is written actually reflects how the department intends to operate.

A borrowed template can save time.

An unvalidated policy can create a liability.

The Warning Signs of a Broken Policy System

A policy manual does not have to be obviously dysfunctional to have problems.

In many departments, the warning signs are already there. They have simply become normal.

Firefighters know which SOPs to follow and which ones no longer reflect reality. Officers explain that “we don’t really do it that way anymore.” New members learn the actual process from the crew rather than from the written procedure. Old documents remain in circulation because nobody is certain whether they were officially rescinded. Policies get updated only when somebody happens to notice a problem.

Eventually, the unofficial way the department operates and the official way the department says it operates can become two different systems.

Some warning signs deserve a closer look:

• Policies with no issue date, revision date, or identifiable approval history
• SOPs or SOGs that have not been reviewed in years
• Multiple versions of the same document stored in different locations
• Different formatting, numbering systems, terminology, or organizational structures throughout the manual
• References to apparatus, stations, positions, equipment, forms, mutual-aid agencies, or programs that no longer exist
• Different policies giving conflicting direction on the same subject
• Procedures that no longer reflect current staffing or response capabilities
• Department practices that have changed operationally but were never updated administratively
• Policies copied from another organization that still contain language specific to that department
• References to outdated laws, regulations, standards, manufacturer recommendations, or external documents
• Forms or supporting documents referenced by policy that personnel cannot locate
• Policies that nobody can clearly explain, interpret, or identify ownership for
• Operational or administrative subjects that the department assumes are covered somewhere but actually are not

One or two of these issues do not necessarily mean a department's entire policy system is broken. They should, however, prompt another question:

If we found this problem by accident, what would we find if we intentionally looked for the others?

That is where a true policy review becomes different from opening an old SOP, changing the revision date, correcting a few sentences, and calling it current.

A meaningful review asks whether the document is still accurate, whether it conflicts with anything else, whether the references remain current, whether the responsibilities and resources identified actually exist, whether personnel can reasonably understand the direction being given, and whether another policy should be revised at the same time.

It should also ask whether the department is missing something entirely.

That last question is easy to overlook. A department can spend years revising the policies it already has without ever identifying the policies it should have but does not.

The goal is not to create the largest policy manual possible. More policies do not automatically create a better-run department. Every document should exist for a reason, provide useful direction, and fit into the larger administrative structure.

The real objective is alignment.

What the department says it does, what leadership expects personnel to do, and what firefighters actually do should not be three different things.

When those begin to separate, policy maintenance has become a policy-system problem.

A Review Is More Than Updating the Revision Date

There is a difference between touching a policy and actually reviewing it.

Opening an SOP, correcting a few grammatical errors, changing the chief’s name, updating the revision date, and placing it back into the manual may make the document look current. It does not necessarily make the policy current.

A meaningful review should go deeper.

Start with the most basic question: Does this document still accurately describe what the department expects its personnel to do?

From there, the review should examine the policy in the context of the organization around it. Is the apparatus, staffing levels, positions, equipment, response assignments, mutual-aid resources, terminology, forms, and responsibilities referenced in the document still accurate? Have operational practices changed since the policy was written? Does another SOP address the same subject differently?

External references deserve the same attention. If a policy cites a law, regulation, NFPA standard, manufacturer instruction, county policy, mutual-aid agreement, or another outside source, that reference should be checked rather than assumed to still be correct. Standards are revised. Regulations change. Equipment is replaced. Agreements expire or are rewritten. A citation that was accurate when the document was created may not remain accurate indefinitely.

Then comes one of the most overlooked parts of the review: cross-referencing the rest of the policy system.

Changing one SOP can create a problem somewhere else.

A department may revise its incident command procedure while an accountability policy still uses the previous terminology. An apparatus replacement may be reflected in the response guideline but not in the water-supply procedure. A staffing change may make an old operational assignment impossible to perform as written. A revised disciplinary process may conflict with language still sitting in another administrative policy.

Each individual document may look reasonable when reviewed alone.

The conflict becomes visible only when someone looks across the system.

A comprehensive review should therefore consider more than spelling and formatting. Depending on the document, the department may need to evaluate:

• Operational accuracy
• Current terminology and organizational structure
• Staffing and resource assumptions
• Internal consistency with related policies
• Current external references
• Roles and responsibilities
• Forms and supporting documents
• Version control and revision history
• Whether the policy can realistically be followed as written
• Whether the policy is still necessary at all

That last point matters.

Policy review should not automatically mean making the manual larger. Some documents may need to be consolidated. Others may be redundant. A procedure may have been superseded by another policy or by a change in how the department operates. Keeping obsolete documents simply because they have always existed can make the system harder to navigate and maintain.

The objective is not to make every SOP longer, more complicated, or more formal.

The objective is to make the policy system accurate, understandable, consistent, and usable.

And that requires something more deliberate than changing the date at the bottom of the page.

A revision date tells you when someone opened the document. A real review should tell you whether the document still belongs in the system.

Your Policies Have to Match Your Actual Department

A policy can be well written and still be wrong for the department using it.

That is why policy development cannot be separated from operational reality.

A rural volunteer department with limited staffing, long response distances, tanker operations, and significant reliance on mutual aid should not have the same operational assumptions as a fully staffed metropolitan department with multiple companies arriving within minutes. A combination department should not adopt language that assumes every position is staffed twenty-four hours a day. An organization without a hazardous materials team should not write procedures as though one exists internally.

The document has to match the department.

That means policy development should account for the organization’s actual staffing model, apparatus, equipment, geography, response area, dispatch procedures, mutual-aid relationships, training level, command structure, and available resources.

Otherwise, the policy may describe an operation the department cannot realistically perform.

This does not mean a department should lower expectations simply because resources are limited. It means leadership must understand the difference between establishing an operational objective and writing a procedure that assumes resources or capabilities the organization does not possess.

Consider mutual aid.

A policy that simply states “request additional resources as needed” may technically address the issue, but does the department know which resources are available, where they are coming from, how they are requested, and what capabilities those agencies actually provide?

The same questions apply internally.

If an SOP assigns four separate tactical functions on the initial response, does normal staffing allow those functions to occur as written?

If a policy assigns responsibility to a safety officer, training chief, battalion chief, or other position, does that position actually exist and respond in the manner described?

If a procedure requires specialized equipment, is that equipment carried on the apparatus expected to perform the task?

If the answer is no, the policy needs another look.

Departments should also be cautious about policies built around the ideal response rather than the response they routinely receive. Written procedures should provide direction personnel can realistically apply while still allowing incident commanders and officers to adjust to conditions, available resources, and the circumstances they encounter.

This is one reason copying another department’s manual without a comprehensive local review is so risky. Two departments may look similar on paper while operating under completely different conditions.

The name at the top of the SOP is not what makes it yours.

The content does.

A strong policy system should reflect the department that exists today while providing enough structure to guide the organization toward where leadership wants it to go.

If your written procedures describe a department that no longer exists - or one that never existed in the first place - the problem is not the firefighters failing to follow policy.

The problem may be the policy itself.

The Policy Manual Should Not Live in One Person’s Head

Some departments have a policy system.

Others have a person who knows where everything is.

There is an important difference.

Maybe it is the chief who knows which version of an SOP is current. Maybe the training officer remembers which policies still need revision. Maybe one administrative officer maintains the files, controls the templates, tracks changes, and knows why certain documents were written the way they were.

As long as that person is there, the system may appear to work.

Then they retire, resign, promote, change assignments, or simply stop being responsible for it.

Suddenly, questions that once had easy answers become much harder.

Which version of this SOP is current?

Was this draft ever approved?

Why was this section changed?

Where is the form referenced in this policy?

Which documents still need review?

Who is responsible for the next revision?

Was the old version formally removed from circulation?

If the answers depend on finding the one person who remembers, the department does not have a sustainable administrative process. It has institutional knowledge concentrated in an individual.

Policy management should survive personnel changes.

That starts with basic document control. Departments should be able to identify the current approved version of a policy, when it became effective, when it was last reviewed or revised, who approved it, and where the authoritative copy is maintained. Superseded documents should be handled consistently so personnel are not unknowingly referencing different versions of the same policy.

Ownership matters too.

Someone should be responsible for overseeing the policy system, but responsibility should not mean that person becomes the only one capable of understanding it. The process for reviewing, approving, publishing, revising, and retiring policies should be established well enough that another qualified person can step into the role and continue it.

The same principle applies to the reasoning behind major changes.

A revision history does not need to become a novel, but documenting why significant changes were made can prevent future leaders from unknowingly reversing a decision without understanding what originally drove it. That becomes particularly valuable after leadership transitions, significant incidents, organizational changes, or major revisions to operational practices.

This is where standardization becomes more than appearance.

Consistent numbering, naming conventions, formatting, approval fields, revision tracking, document locations, and review procedures create continuity. They allow the policy system to belong to the organization rather than to whoever currently manages it.

A department should be able to change chiefs without losing control of its policies.

It should be able to replace a training officer without rebuilding its administrative process from memory.

And it should be able to hand the system to the next person without beginning the conversation with:

“You need to talk to the guy who used to handle all of this.”

Good administration creates institutional memory.

It does not depend on it.

What a System-Wide Policy Review Should Actually Produce

A comprehensive policy review should result in more than a stack of documents with newer dates on them.

The department should come out of the process with a clearer, more organized, and more defensible administrative system than it had before.

That starts with knowing what actually exists.

A department should be able to identify its current policies, SOPs, SOGs, general orders, forms, supporting documents, and other administrative directives without relying on guesswork. Duplicate documents, obsolete versions, unfinished drafts, and policies that no longer serve a purpose should be identified rather than allowed to remain mixed into the active system.

From there, the department can begin answering larger questions.

Which documents are current?

Which need revision?

Which conflict with one another?

Which contain outdated references?

Which no longer match current staffing, equipment, or operations?

Which subjects are duplicated across multiple policies?

Which important areas are not addressed at all?

The review should also create priorities.

Not every document carries the same operational or administrative significance. A formatting inconsistency in a low-use administrative policy does not necessarily deserve the same urgency as an outdated incident command procedure, accountability policy, hazardous materials guideline, or apparatus response assignment.

Departments should be able to separate immediate concerns from long-term improvement projects.

A useful outcome may include:

• A complete inventory of active policies and related documents
• Identification of outdated, duplicated, conflicting, or obsolete material
• A prioritized list of documents requiring revision
• Identification of missing policy areas
• Standardized formatting, numbering, and terminology
• Clear document ownership and approval processes
• Consistent revision and version-control practices
• Updated internal and external references
• Alignment between policy language and actual department capabilities
• A defined process for future review and maintenance

The goal is not perfection.

No policy manual will remain current forever. Departments change. Personnel change. Apparatus and equipment change. Mutual-aid relationships evolve. Regulations and standards are revised. New operational lessons are learned.

The difference is whether the department has a system capable of recognizing and managing those changes.

A strong policy review should leave leadership with more than corrected documents. It should leave them with a better understanding of where the organization stands, where the weaknesses are, what needs attention first, and how the system will be maintained going forward.

That is the real value of looking at the manual as a whole.

You are not simply fixing policies.

You are building a process that makes it harder for them to become broken again.

You May Not Need a Complete Rewrite

Discovering problems in a policy system does not automatically mean the entire manual needs to be thrown out and rebuilt from the ground up.

In many cases, that would be unnecessary.

Some departments already have a solid foundation. Their policies may simply need to be organized, standardized, cross-referenced, updated, or brought into alignment with current operations. Others may have specific areas that require significant revision while the remainder of the manual is still usable.

The important part is understanding the true scope before deciding on the solution.

A department may need:

• A system-wide policy inventory and gap review
• A prioritized list of policies requiring immediate attention
• Targeted revisions to outdated SOPs or SOGs
• Standardized formatting and document control
• Consolidation of duplicate or overlapping policies
• Review of references, terminology, and internal consistency
• Development of missing policies in specific operational or administrative areas
• A structured review and revision process for future maintenance
• Or, when the existing system is too fragmented or outdated, a more comprehensive rebuild

The right answer depends on what is actually there.

This is also why beginning with an assessment can be more valuable than immediately rewriting documents. If the department starts revising policies without understanding the larger system, it may spend time fixing documents that should have been consolidated, replacing policies that were already adequate, or creating new conflicts somewhere else in the manual.

A better approach is to identify the problems first, determine their priority, and then build the scope of work around what the department actually needs.

That is where Fire Service Administrative Solutions can help.

FSAS can review an existing policy system, identify inconsistencies and gaps, help prioritize what requires attention, revise individual policies, develop missing documents, standardize the structure of the manual, or assist with a larger modernization project when needed.

The objective is not to sell a department more work than it needs.

It is to identify the administrative problem accurately and build the right solution around it.

If your department knows the policy manual needs attention but does not know where to start, start with the problem you can already see.

One outdated SOP.

One conflicting procedure.

One section of the manual nobody trusts.

One administrative process that has become difficult to manage.

That may be enough to uncover whether the issue is isolated or part of something larger.

Send Us the Problem You Already Know Exists

Most departments do not need someone to tell them that every policy is perfect.

They usually already know where some of the problems are.

There is an SOP nobody trusts.

A section of the manual that has not been touched in years.

A policy that no longer matches current staffing.

A procedure copied from somewhere else that never really fit.

A collection of documents that grew over time without anyone stepping back to look at the whole system.

The challenge is deciding what to do next.

That is where Fire Service Administrative Solutions is designed to help.

FSAS works with fire departments to review, organize, revise, standardize, and develop the administrative documents behind their operations. That may mean reviewing a single SOP, evaluating one section of a policy manual, identifying gaps and conflicts across an existing system, or helping a department build a structured modernization plan around a much larger project.

The process should start with the department itself.

What do you already know is not working?

What document keeps getting questioned?

What procedure no longer reflects reality?

What part of the manual has everyone been avoiding because nobody has the time to tackle it?

Start there.

Send FSAS the problem you already know exists.

We can review what you have, talk through how your department actually operates, identify whether the issue appears isolated or connected to something larger, and determine what a realistic scope of work would look like.

You do not need to commit to rebuilding an entire policy manual just to start the conversation.

You need one problem worth solving.

Take ten minutes and look at your policy system.

Find one SOP you are not completely confident in.

Find one procedure you know has not kept pace with the department.

Find one document you would not want to explain if someone outside the organization asked why it still says what it says.

Then contact Fire Service Administrative Solutions.

Bring us the problem.

We will help you determine what comes next.

Your policies should reflect the department you actually operate today - not the department you were ten years ago, not the department you copied them from, and not the department you hope nobody notices on paper.

Build a policy system your firefighters can use and your leadership can stand behind.