Fire & EMS
The standard that set out how a fire department organizes and administers itself no longer exists on its own. NFPA 1201 has been folded into NFPA 1750 along with three other standards, and the 2020 edition of NFPA 1201 is the last one that will ever be published as a stand-alone document.
Separately, and more uncomfortably, NFPA's own research foundation surveyed fire departments about their standard operating guidelines and found that more than half have no set time frame for revising them. Those two facts land in the same place: the documents that govern how your crews operate on the fireground, and whether anybody can show which version was in force on the day of the call you're now being asked about.
This is for fire chiefs, training officers, and whoever in your department ended up owning the SOG binder. That is usually a company officer or an assistant chief who inherited a Word folder from someone who retired. What follows is what changed at NFPA, what a standard operating guideline is supposed to contain, why the review cycle is the part that fails, and how to judge whether the system you keep them in can prove any of it.
NFPA 1201, Standard for Providing Fire and Emergency Services to the Public, has been combined into a new consolidated standard, NFPA 1750, under the Emergency Response and Responder Safety Document Consolidation Plan approved by the NFPA Standards Council. NFPA 1750 also absorbs NFPA 1710, NFPA 1720 and NFPA 1730, and its current edition is 2026. The 2020 edition of NFPA 1201 remains the last published edition of that content as a stand-alone standard.
NFPA 1201 is the National Fire Protection Association standard on providing fire and emergency services to the public. It carries requirements on the structure and operations of fire emergency service organizations, and it applies to municipal and private organizations alike. Its last stand-alone edition is 2020, and Chapter 4 covers governance and administration.
NFPA 1201 is the standard people reach for when the question is organizational rather than tactical. It does not tell a crew how to ventilate a roof. It sets out how the organization that sends them there is supposed to be structured, governed, planned and administered, across governance and administration, community planning, emergency operations and code enforcement.
That makes it the standard behind the documents nobody enjoys writing. Master plans, mutual aid arrangements, staffing models, the division of responsibility between a chief and a governing board, and the written direction that turns all of it into something a firefighter can act on at two in the morning.
The 2020 edition made three changes worth knowing. Chapter 4, governance and administration, was revised with added requirements. The horizon for projecting future emergency service needs moved from twenty years to ten, which brought it into line with how master planning is actually practiced. And a requirement was added to identify company staffing models as part of intercommunity organization.
What NFPA 1201 does not do is dictate the contents of your SOG manual clause by clause, whatever a vendor has told you. The standard sets the governance frame. The detailed guidance on what a standard operating guideline should contain comes from a different NFPA source, and that source is the spine of the rest of this article.
NFPA 1750 is the Standard for the Organization and Deployment of Fire Suppression Operations, Emergency Medical Services, Special Operations, and Fire Prevention Activities. Its current edition is 2026. It consolidates four previously separate standards: NFPA 1201, NFPA 1710, NFPA 1720 and NFPA 1730.
NFPA has spent several years collapsing a sprawl of emergency response documents into a smaller set of consolidated standards. That work runs under the Emergency Response and Responder Safety Document Consolidation Plan, approved and amended by the NFPA Standards Council, and NFPA 1750 is one of its larger outputs.
Four standards went in. Here is what each of them was, and where its content now lives.
| Standard | What it covered | Who it applied to |
|---|---|---|
| NFPA 1201 | Providing fire and emergency services to the public: governance, administration, community planning, emergency operations, code enforcement | All fire emergency service organizations, municipal and private |
| NFPA 1710 | Organization and deployment of fire suppression, emergency medical and special operations | Career fire departments |
| NFPA 1720 | Organization and deployment of fire suppression, emergency medical and special operations | Volunteer fire departments |
| NFPA 1730 | Organization and deployment of fire prevention inspection and code enforcement, plan review, investigation and public education operations | Fire prevention and code enforcement functions |
NFPA describes the consolidated standard as covering the organizational aspects of providing fire and emergency services, from the criteria for all hazard emergency service operations, through developing and implementing a community risk reduction plan, to improving the health and safety of career and volunteer personnel.
The practical consequence is a documentation one, and it is small but real. If your fire department policies and procedures cite NFPA 1201 by number, that citation now points at a standard that is no longer maintained on its own. The content survives inside NFPA 1750, so nothing you built on it has been withdrawn. But a citation to a superseded document is exactly the kind of detail that an assessor, an attorney or a new chief will notice, and it is the kind of thing that only gets found and fixed if somebody is reviewing the manual on a schedule.
Two cautions before you rewrite anything. NFPA 1201 is still listed as active with a 2020 current edition, so it has not vanished from NFPA's catalog, and copies you hold remain the last stand-alone version of that text. And NFPA has not published an effective date for the 2026 edition of NFPA 1750 on the standard's own pages, so treat the edition year as the fact and do not build a deadline out of it. Buy the standard, or read it through NFPA's free access, before you commit to language in your own documents.
Most fire departments write standard operating guidelines rather than standard operating procedures, and the reason is legal exposure rather than semantics. The word procedure reads as an instruction to be followed exactly, and a department that issues one may be held to it. Guideline signals that an incident commander can deviate as conditions require. NFPA's own research treats the two as one document type: any official written document that sets forth an operational guideline is a standard operating procedure.
This is the question every new training officer asks, and it deserves a straight answer, because it is also the reason a fire department cannot simply buy what a city buys. Ask ten chiefs what they call the document and you will get fire department standard operating procedures from some and standard operating guidelines from others, often for the same content.
Start with the exposure. A United States Fire Administration applied research paper written for the National Fire Academy's Executive Fire Officer Program sets out the doctrine clearly. Fire departments are generally immune from suit for negligent fireground operations under the public duty doctrine. One important exception is where a public safety agency assumes a special duty to individual citizens by issuing written operating procedures or guidelines. The theory is that when a department establishes formal procedures, it assumes a duty to follow them.
That inverts the usual assumption about paperwork. The same paper quotes the conclusion directly: poorly written SOPs may actually increase a department's liability for emergency operations. Writing nothing down is indefensible. Writing something down and then not operating to it can be worse than writing nothing at all.
Hence the vocabulary. The paper records that many authors use standard operating guideline in place of standard operating procedure, and quotes the reasoning: many people interpret procedure to mean follow or else, whereas guideline implies some degree of flexibility, and the assumption is that a department's liability might be reduced or avoided altogether where a department has guidelines rather than procedures. Dr. Harry Carter's version of the same point is blunter, and it is the one chiefs tend to remember: the term guideline exists because there is no way on this green earth to make every decision for every situation of circumstance you might encounter.
Two things follow for the document itself. The paper's recommendation is that an SOG manual open with a preamble stating that the procedures are general guidelines which may be modified by incident commanders, unit officers and other personnel as conditions dictate, and that the document does not create rights or duties enforceable in court. If your manual carries no such preamble, that is half a day with your attorney and it will do more for your exposure than any software will.
The second is that nobody should pretend the distinction is settled. Departments run fire department SOPs, fire department SOGs, general orders, directives and rules and regulations, sometimes several at once with different approval routes. Plenty of departments label the manual fire department standard operating procedures on the cover and then write guideline language throughout, which is the worst of both positions. NFPA's research foundation sidesteps the argument by defining the category functionally: any official written document that sets forth an operational guideline counts. That is the sensible working position. Decide which word your department uses, use it consistently, and put the preamble in.
The Fire Protection Research Foundation, NFPA's research affiliate, collected and analyzed standard operating guidelines from North American fire departments and published a twelve section model template. The twelve sections are title, date of implementation, revision date, name of fire department, purpose and scope, table of contents, definitions and terminology, risk assessment, operational responsibilities, responsibilities of command and the incident management system, references, and appendix.
The source is worth naming because it is the only analysis of its kind. In March 2019 the Fire Protection Research Foundation published Review of Emergency Responder Standard Operating Procedures and Guidelines, written by Lana Benny of the Department of Fire Protection Engineering at the University of Maryland. Thirty six North American fire departments answered a fourteen question survey, and twenty three of them handed over the SOGs they actually use. The purpose was to build a model template for NFPA 1700, the Guide for Structural Firefighting.
The departments in that sample were not a narrow slice. Forty two percent were all career, eleven percent mostly career, nineteen percent mostly volunteer and twenty eight percent all volunteer. Ninety two percent had some form of SOG in place.
Here is the template, with what each section is for.
| Section | What it does |
|---|---|
| 1. Title | States clearly what type of SOG or SOP this is, for example structural firefighting |
| 2. Date of implementation | The date the document took effect, so a reader can judge how relevant its contents still are |
| 3. Revision date | The most recent revision, on the front page. For a first edition it matches the implementation date |
| 4. Name of fire department | Makes clear which department the document is tailored to |
| 5. Purpose and scope | How the SOG is to be enforced, which incident types it applies to, why it was written, and which personnel it binds |
| 6. Table of contents | Lets a reader find a section fast, which matters most under time pressure |
| 7. Definitions and terminology | Defines the terms used throughout, so the document cannot be read two ways |
| 8. Risk assessment | The risk based approach the department applies, the factors it weighs, and a risk matrix |
| 9. Operational responsibilities | What to do on arrival, by company, unit, apparatus or member, with tactical and safety considerations |
| 10. Command and incident management | How the chain of command is handled, the techniques used, and the reports required through the incident |
| 11. References | The scientific material behind the tactics, or a statement where the content draws on research generally |
| 12. Appendix | Supplemental material: further discussion of tactics or responsibilities |
What the twenty three real manuals were missing is more useful than the template itself. The report scored each submitted document against the features it had identified, split by career and volunteer departments.
| Section | Volunteer | Career |
|---|---|---|
| Firefighting tactics | 90% | 92% |
| Purpose and scope | 90% | 85% |
| Operational responsibilities | 80% | 92% |
| Incident management system | 80% | 85% |
| Revision or effective date | 80% | 85% |
| Table of contents | 80% | 15% |
| Appendix or definitions | 70% | 77% |
| Safety considerations | 70% | 77% |
| Risk based approach | 60% | 54% |
| Staffing and job descriptions | 20% | 23% |
| Scientific references | 0% | 15% |
Three rows are worth acting on. Scientific references barely exist: none of the volunteer manuals and fifteen percent of the career ones cited the research behind their tactics, which the report calls a critically important gap given what NFPA 1700 is built on. Risk based approach appears in roughly half. And staffing and job descriptions sit around twenty percent, which is a strange omission in a document that tells a member what is expected of them.
The table of contents split is the oddity: eighty percent of volunteer manuals had one against fifteen percent of career manuals. The report offers no explanation for it. Worth checking whether yours has one, because a manual nobody can navigate under time pressure is a manual nobody uses.
One more finding, about where SOG content comes from. Sixty seven percent of departments used another organization's SOPs as a reference, forty four percent used NIST research and thirty six percent used UL research. Twenty eight percent used no policy source or scientific research at all. Borrowing a neighboring department's manual is normal practice and there is nothing wrong with it, as long as somebody then does the work of making it yours. The report's own closing note is that organization size, geography, resources and preferences shape the process, and each department has to tailor the material to its own needs.
Fifty three percent of the fire departments surveyed by NFPA's Fire Protection Research Foundation have no set time frame for revising their standard operating guidelines. Twenty five percent revise annually, fourteen percent less often than annually, and eight percent more often. The report's own conclusion is that departments need a fixed time frame for revision.
More than half of departments revise their SOGs when something prompts it, and what prompts it is usually an incident, a near miss, a complaint or a lawsuit. The document that was supposed to prevent the event becomes the thing you edit after it.
| Revision cycle | Share of departments |
|---|---|
| No set time frame | 53% |
| Annually | 25% |
| Less than annually | 14% |
| More than annually | 8% |
Put that next to the liability doctrine from earlier and the shape of the problem is clear. Issuing a written guideline creates a duty to follow it. A guideline that has not been read in nine years still creates that duty. So the department carries the exposure of the document while getting none of the benefit, because nobody is operating to it and half the crews are not sure it exists.
There are four failure modes, and they are worth naming separately because they need different fixes.
The third and fourth are the ones a fire department policy manual kept in a shared drive cannot fix, and it is worth being precise about why. Version history is not the same as a folder of files named final, final2 and revised. Nobody can testify to a filename. What has to exist is a record that binds four things together: the individual, the document, the version they were served, and the date. Any one of those on its own is worthless.
Test your own setup against one question. Pick a guideline that has been revised twice. Can you produce the text that was in force eighteen months ago, and the list of people who had acknowledged that specific version at that specific time? If the answer takes more than a few minutes, that is what it will cost under pressure, multiplied by however many people are asking.
The fix is unglamorous and it works. Split the manual into five roughly equal groups and review one group a year, so the whole thing turns over on a known cycle with the review date printed on each document. That is what section two and section three of the model template are for. Twenty percent of a fire department SOG manual a year means everything gets looked at inside five years and nothing sits untouched for a decade.
Three rules make the calendar hold. Group by subject rather than alphabetically, so the year you review fireground guidelines you review all of them and the crews get one consistent set of changes instead of a trickle. Pull a guideline forward out of its year whenever an incident, a near miss or a change in law touches it, and put it back on cycle afterwards rather than treating the incident review as its annual review. And record the review even when nothing changes, because a fire department SOG with a review date and no edits is evidence of a working process, while one with neither is indistinguishable from neglect.
The reason to publish the calendar rather than keep it in a chief's head is that it survives the chief. A fire department SOG program that depends on one person paying attention lasts exactly as long as that person's tenure, and the fifty three percent above is largely what that looks like after a retirement.
Eighty one percent of the departments in the NFPA survey deliver training to support their standard operating guidelines, fourteen percent do so partially and five percent do not. Classroom instruction is the most common method at eighty nine percent, followed by station drills at seventy two percent and hands on training without live fire at sixty seven percent. Six percent reported that training had not been developed.
Acknowledgment and training are two different records, and conflating them is a common mistake. An acknowledgment says a member received a document and confirmed it. Training says a member was taught to do what the document says and was assessed on it. A fireground guideline needs both, and the second one is the one that stands up.
| Method | Share |
|---|---|
| Classroom with an instructor | 89% |
| Station drill | 72% |
| Hands on, no live fire | 67% |
| Multi company drill | 61% |
| Hands on with live fire | 50% |
| Online | 36% |
| Training not developed | 6% |
The number that should bother you is not the eighty nine percent. It is the fourteen percent who train partially and the five percent who do not, because a guideline issued without training is the exact scenario the special duty exception describes. You have created the duty and skipped the part that lets your members discharge it.
The record you want, for a substantive revision, has three parts. The revision itself, dated and versioned. The acknowledgment from each affected member against that version. And the drill or class where the change was taught, with the roster, the hours and the officer who ran it. Those three sit naturally on one employee record, and in most departments they sit in three unrelated places: a shared drive, an email folder and a training spreadsheet.
That split is the practical argument for keeping SOGs on the personnel system rather than beside it. When an attorney names one firefighter and asks whether they were trained on the current rapid intervention guideline, the answer is one query if those three records share a subject, and a week of reconstruction if they do not.
There is a reporting benefit too, and it is quieter. A department that trains against a revised guideline generates training hours, and those hours count toward the reporting your department already does. Logging the drill as SOG training rather than as generic company training costs nothing at the point of entry and makes the hours retrievable later, by guideline, which is exactly the cut nobody can produce.
In most fire departments standard operating guidelines are written by subject matter experts from inside the department and by department management, each reported by seventy two percent of surveyed departments. Only fourteen percent involve legal counsel and fourteen percent bring in outside expertise. The recommended structure is a standing committee with representation below command level, owning a fixed review calendar.
Who writes your SOGs decides whether they get reviewed, so it is worth looking at the survey data on this directly.
| Group involved | Share |
|---|---|
| Subject matter experts from within the department | 72% |
| Department management | 72% |
| All available parties | 22% |
| Subject matter experts from outside the department | 14% |
| Legal counsel | 14% |
The fourteen percent for legal counsel is striking given that the whole reason fire departments say guideline instead of procedure is legal. Most departments are managing a liability instrument without a lawyer in the room. That is a defensible call for a small volunteer company and a harder one for a career department with a risk manager on staff.
The structural recommendation from the Executive Fire Officer paper cited earlier is a standing SOG committee rather than a chief's project, and the composition matters: a firefighter and a line officer from each company alongside the fire marshal or training officer, drafting guidelines for the chief and the governing body to adopt. The reasoning it quotes is that it is desirable to get as many fingerprints on the proposed document as possible.
That is not only about buy in, though buy in is real and the paper is candid that members kept in the dark provide the most resistance. It is about who notices that a guideline has gone stale. A chief will not notice that the tanker shuttle guideline no longer matches how the crews actually run it. The captain who runs the shuttle will.
Give that committee three standing jobs and the review problem largely solves itself. Own the calendar, so a fixed share of the manual comes up for review every year. Decide what counts as substantive, because that decision determines whether a revision triggers a fresh acknowledgment cycle and a drill or just a version bump. And read the acknowledgment reporting, because a guideline that forty percent of the department has not opened is telling you something about the guideline as much as about the department.
On the substantive question, most departments land on the same rule. A typo correction does not pull an agency back through acknowledgment. A change to a mayday or rapid intervention guideline plainly does, and so does anything your counsel would want to point at later. Write that rule down before you need it, because deciding it document by document is how the process quietly erodes.
Committees also need to be tracked, which sounds administrative until you try to answer who is currently on the SOG committee, when they were appointed and what their term is. That belongs on the same personnel record as everything else about those members.
A fire department's standard operating guidelines are rarely worth buying a dedicated system for. What matters is whether the fire department management software you already run can hold a versioned document, record who acknowledged which version and when, and connect that acknowledgment to the drill where the guideline was taught. Judge it on the record it leaves behind rather than on the publishing workflow it shows you in a demo.
Departments arrive at this question from two directions. Some are replacing a shared drive and want the narrowest possible tool. Others are already choosing a broader fire department management software platform and want to know whether the SOG problem comes with it. The second group has the easier decision, because the acknowledgment record is only useful next to the personnel record it refers to, and fire department management software that already holds the roster is the cheapest place to put it.
Dedicated SOG software exists, and for a large department with a full standards operation it can be the right answer. For most departments it creates a fourth system to log into and a fourth place your evidence lives. Before you buy anything, work out which of these four things is actually broken.
Can you retrieve the superseded text, not just the current one? A system that shows you today's guideline and nothing else is doing half the job.
Does the record say which revision the member acknowledged, or only that they clicked something at some point? A tick with no version attached proves very little.
Can you publish to a station, a shift, a company or a rank, and does the system understand volunteer, part paid and career status? City wide tools usually cannot.
Does the drill that taught the revision live on the same record as the acknowledgment, or in a separate training system?
The third one is where general purpose tools fail fire departments specifically, and it is worth testing hard. A guideline that applies to engine companies but not to the ladder, or to interior qualified members but not to support personnel, is normal in the fire service and awkward in software built around a flat employee list. Ask to see a distribution list built from rank and qualification rather than from a group somebody maintained by hand.
Two questions cut through a demo faster than a feature list. Ask the vendor to pull the acknowledgment record for a guideline that has been revised twice, live, and watch whether the superseded versions are still retrievable and whether the ticks are attributed to the right revision. Then ask how the guideline connects to the training record, and listen for whether the answer involves an export.
One thing no SOG software solves, and it is worth saying before you shop. Migrating years of documents into any system is the bulk of the effort, and departments that do it well treat it as a review rather than a copy. SOG software cannot tell you which of your guidelines are dead. Load everything unchanged and you have bought a tidier version of the same problem, and you have carried a decade of obsolete guidelines into a system that will now prove your members acknowledged them.
The same caution applies at the other end of the scale. Fire department management software bought mainly for scheduling or incident reporting often lists policy posting among its modules, and the module is frequently a file store with a read receipt bolted on. That is not the same product as the one described above, and the two version test will tell you which you are looking at inside a minute.
At Essential Personnel we publish guidance to the employee record rather than to a document library, so an acknowledgment sits on the same profile as the member's certifications, training hours, evaluations and issued equipment. Guidance is one of our four suites and it costs 30 dollars per user per year.
My co-founder and I started EP in 2020 in Wilmington, North Carolina. We both came out of the fire service, and we built the platform as professional standards software for public safety rather than as a document system with a fire logo on it. Our Guidance suite posts policies, memos and directives, handles Adobe, Word and video content, and carries Version Control and Acknowledgment Tracking.
Three things about how it works bear on the review cycle problem above. Guidance publishes five content types rather than one, so policies, memos, announcements, lessons learned and research all sit together, which matters because the memo that amends a guideline is usually filed somewhere else entirely. Version Control keeps every revision rather than overwriting it, and lets you revert, so the question of what the guideline said on a given date is a lookup. And Acknowledgment Tracking creates a record of receipt against the version the member was served, which is the four part record described earlier.
The part that only works because it is one platform is the training tie. Certification management, task books, the hours logbook, field training and training events sit in our Talent Management suite on the same employee record. So the revision, the acknowledgment and the drill that taught it are three entries against one member rather than three systems. Special teams and committees are tracked there too, which covers the SOG committee itself and who currently sits on it.
Lessons Learned is the content type most departments underuse, and for a fire department it is the one we would push hardest. A serious near miss produces a good debrief and then evaporates, because there is nowhere durable to put it. Published as a document with acknowledgment, the crew joining that station in three years still meets it.
We don't write your standard operating guidelines, and for a fire department that gap is bigger than it sounds. We are the repository and the acknowledgment layer. We don't supply guideline content and we don't draft or maintain model documents for your state, so if what you need is somebody to write the tanker shuttle guideline, keep it current and defend the language, that is a separate thing you still need.
Worth knowing where fire departments actually get that content, because it is not mainly a software market. Your state fire marshal's office and state firefighter association often publish SOG templates at no cost. Your insurer or risk pool frequently provides them to policyholders and has an interest in you using them. A neighboring department's manual is the most common starting point and, per the survey above, what sixty seven percent of departments already do. Beyond that there are policy content subscriptions written and maintained by attorneys, which is a real business and a reasonable purchase if your guidelines are a decade old and locally written.
We also don't audit your operations against a standard. Acknowledgment records and version history evidence that a document reached your people, which is one of the things an assessor asks for. They do not tell you whether your department complies with NFPA 1750. If you want a full standards file operation with an indicator library, that is a different category of tool and you should scope it separately.
And there is an honest limit on what any acknowledgment proves. It establishes receipt, not comprehension and not compliance. No system can prove a firefighter understood a guideline. What it removes is the defense that they never got it, which in practice is the argument departments most often have to rebut.
What you get in exchange is a record that holds together across a career. The guideline, the acknowledgment, the drill, the certification it depended on and the incident it was written after are one employee record rather than five exports. We publish our pricing, which is unusual in this category: Guidance is 30 dollars per user per year, the whole platform is 175 dollars per user per year across all four suites and 33 tools, and there is a one time 3,000 dollar startup fee. Our pricing page carries the rest, including size based discounts and optional single sign on. We run in AWS GovCloud with SOC 2 Type II attestation and CJIS aligned controls, and you can buy us through GSA Advantage, NASPO, Omnia Partners, NCSA and VSA.
Four things, in this order, and none of them needs a purchase.
If you want to talk any of it through with people who came out of the fire service, we will walk your own manual and your own roster rather than a demo dataset. Have a look at how we set the platform up for fire and EMS first if you would rather look before you talk. Call (910) 390-0011 or email info@essper.com.
Bring one guideline that has been revised twice and we will build the record around it, using your department's ranks and stations.
NFPA 1201 is still listed as active with a 2020 current edition, but it has been combined into the consolidated standard NFPA 1750. NFPA describes the 2020 edition as the last published edition of that content as a stand-alone standard, so nothing was withdrawn and nothing further will be published under the 1201 number.
NFPA 1750 replaced it. The consolidated standard combines four documents: NFPA 1201 on providing fire and emergency services to the public, NFPA 1710 on career deployment, NFPA 1720 on volunteer deployment, and NFPA 1730 on fire prevention inspection and code enforcement. Its current edition is 2026.
Functionally yes, and NFPA's research foundation treats them as one category: any official written document that sets forth an operational guideline. The word choice is about liability. Procedure reads as an instruction to follow exactly, and guideline signals that an incident commander may deviate as conditions require.
No standard sets a required interval, but the practice worth adopting is a fixed cycle rather than review after incidents. Twenty five percent of departments surveyed by NFPA revise annually and fifty three percent have no set time frame at all. Reviewing a fifth of the manual each year turns everything over inside five years.
Most departments run both and the split is by subject. Administrative rules on conduct, leave, discipline and harassment sit in the policy manual. Operational direction for the fireground sits in the guidelines. Keeping them in one repository matters more than which document a given item lives in.
The Fire Protection Research Foundation model template has twelve sections: title, date of implementation, revision date, department name, purpose and scope, table of contents, definitions and terminology, risk assessment, operational responsibilities, command and incident management, references, and appendix. The sections most often missing are scientific references and staffing descriptions.
A standing committee with representation below command level, not the chief alone. In the surveyed departments internal subject matter experts and department management each contributed in seventy two percent of cases, while legal counsel was involved in only fourteen percent. For a document that exists partly to manage liability, that last figure is low.
No. An acknowledgment establishes receipt, not comprehension and not compliance. What it removes is the defense that a member never got the document. Comprehension is what the supporting drill or class evidences, which is why the training record and the acknowledgment record are two separate things.
Usually not. A large department running a full standards operation may justify it, but for most the requirement is that whatever system already holds your personnel records can version a document, record acknowledgment against a specific version, and sit alongside the training record. A separate tool adds a fourth place your evidence lives.
Written by Scott Monroe, Chief Executive Officer and Co-Founder of Essential Personnel. Published 10 September 2026.
We sell the guidance and acknowledgment software described in the second half of this article. The standards information above comes from NFPA's own published pages for NFPA 1201, NFPA 1750 and NFPA 1700. The survey figures come from Review of Emergency Responder Standard Operating Procedures and Guidelines, report FPRF-2019-01, published by the Fire Protection Research Foundation in March 2019 and written by Lana Benny of the University of Maryland, based on 36 North American fire departments. The liability doctrine and the committee structure come from an applied research paper submitted to the National Fire Academy's Executive Fire Officer Program by Richard M. Lesniak in February 2002. The United States Fire Administration also publishes a Guide to Developing Effective Standard Operating Procedures for Fire and EMS Departments, FA-197, which is worth holding. This is a summary written for fire service readers and it is not a substitute for the standards themselves.
