Fire Prevention Plans Across Many Sites: The Roster That Goes Stale First

Ask the head of operations at a company with sixty locations whether every site has a fire prevention plan and the answer is usually a confident yes. A corporate document exists, it carries the company's name and a revision date, and each site manager signed that they received it. Ask a different question, though: at the warehouse that was reorganized in the spring, who is the person named in the plan as responsible for maintaining the equipment that prevents ignition? The honest answer at too many locations is that the person named left the company, or that the plan names a role no one at the site recognizes, or that nobody has opened the document since the day it was signed.

That is the practical shape of the problem under 29 CFR 1910.39, OSHA's fire prevention plan standard. The rule is short. Its difficulty at scale is not in understanding it but in keeping a set of plan elements true across many buildings whose equipment, staff, and stored materials keep changing. This post is about where that fails, and what an accountable executive can check without becoming a fire protection engineer. It is general information, not legal advice.

What the standard actually requires

Start with the part that surprises people: 1910.39 does not apply to everyone by itself. Paragraph (a) says an employer must have a fire prevention plan when another OSHA standard in Part 1910 requires one. The first job for a multi-site operator is therefore a mapping exercise. Which of your operations, at which locations, are covered by a standard that calls for a plan? A company with offices, distribution centers, and a few manufacturing plants may find the answer differs by site type, and that is a question for your safety lead or counsel to settle, not something to assume from the standard's title.

Where a plan is required, paragraph (b) says it must be in writing, kept in the workplace, and made available to employees for review. The standard also allows an employer with ten or fewer employees to communicate the plan orally. Operators with small satellite locations should resist the temptation to build a shortcut on that provision. A site whose headcount drifts around that line would flip between compliance formats, and a written plan at every location is easier to audit than a patchwork of oral ones.

Paragraph (c) lists the minimum content. The plan must include a list of the major workplace fire hazards, the proper handling and storage procedures for hazardous materials, potential ignition sources and their control, and the type of fire protection equipment necessary to control each major hazard. It must include procedures to control accumulations of flammable and combustible waste materials, and procedures for regular maintenance of safety equipment installed on heat-producing equipment to prevent accidental ignition of combustible materials. Finally, it must name, by name or job title, the employees responsible for maintaining equipment to prevent or control sources of ignition or fires, and the employees responsible for control of fuel source hazards.

Paragraph (d) adds the training duty. The employer must inform employees upon initial assignment to a job of the fire hazards to which they are exposed, and review with each employee those parts of the plan necessary for self-protection.

Why a template cannot carry the content

Read that list again and notice how much of it is local fact. The major fire hazards of a bakery are not those of a battery-charging area or a cold-storage warehouse. Ignition sources depend on which ovens, heaters, forklifts, and electrical panels exist at that address. The right fire protection equipment depends on what is stored and how. A corporate template can supply the structure and the language, but the hazard list, the ignition source inventory, and the equipment match are things only someone standing in the building can write down.

This is the same structural trap that appears in emergency planning, which we discussed in the piece on emergency action plan consistency across sites. A company-level document can look complete while no individual establishment has finished it. A fire prevention plan with the headings filled in generically, "all flammable materials will be stored properly," satisfies the outline of paragraph (c) without telling the reader at that site anything. When an inspector asks the manager to show where combustible waste accumulates and who controls it, a generic sentence is not an answer.

The roster is the part that decays fastest

Of all the plan's elements, the named responsibilities in paragraph (c) go stale first, and they matter most. The standard asks for the names or job titles of the people responsible for maintaining ignition-prevention equipment and for controlling fuel sources. Naming a person is accurate on the day it is written and wrong the day that person transfers. Naming a job title is more durable, but only if the title exists at that site and the person holding it has been told about the duty.

Across a portfolio this produces predictable failure patterns. A title like "maintenance supervisor" appears in the corporate template, yet a third of the sites have no such role because maintenance is outsourced or handled by a general manager. A site is restructured, and the duty falls into the gap between two job descriptions. A person is named, leaves, and is never replaced on paper. In each case the plan still reads correctly and still cannot be carried out. A responsibility assigned to no one who knows about it is the same as no assignment.

The fix is not a longer document. It is tying the roster to an event. Whenever someone in a named role leaves, transfers, or is replaced, the site's responsibility assignment gets reviewed as part of that same change. Organizations that already run a joiner-mover-leaver process for building access or system accounts have the mechanism; they just have to add the safety duties to it.

Fuel, waste, and housekeeping drift between audits

Paragraph (c) also requires procedures to control accumulations of flammable and combustible waste. Anyone who has walked many facilities knows this is the element that varies most between a site on a good week and the same site on a bad one. Cardboard against a wall, oily rags, a compactor that fills faster than it is emptied, dust building up on overhead surfaces: none of that is visible in a document review, and all of it can change within days.

For a multi-site operator, the lesson is that a plan cannot be verified from head office alone. A written procedure for waste accumulation needs a corresponding observation at the site, performed at a frequency matched to how fast the material builds up. The frequency is itself a plan decision to be made locally. A site that generates a lot of packaging waste may need a daily walk, while a low-volume site may be fine with a weekly one. What matters is that the plan states the frequency, someone is assigned to it, and a record exists showing the walk occurred.

Equipment maintenance follows the same logic. Paragraph (c) requires procedures for regular maintenance of safety equipment installed on heat-producing equipment. At sites that rely on contractors for that maintenance, the plan should say so, and the operator should be able to produce proof that the contractor's visits occurred. This connects to the broader contractor oversight questions we cover in contractor management across multi-employer worksites, because a vendor who services a fryer hood or a boiler on your behalf is performing a duty your plan promises.

Acquired and leased sites arrive with their own assumptions

Two kinds of locations deserve a closer look. The first is the acquired site. It comes with a fire prevention plan from its previous owner, written for different equipment, different parent policies, and often different terminology. Folding that plan into the corporate framework is easy to defer, and the deferral can last years. Our discussion of integrating acquired sites makes the general case; for fire prevention in particular, the first walk-through should check whether the inherited hazard list matches what is actually in the building today.

The second is the leased location. In a multi-tenant building, many fire protection systems and structural features belong to the landlord, and some ignition and waste sources are shared with neighbors. The plan still has to describe what your employees need to know and who in your organization is responsible for the parts you control. It should also record where responsibility passes to the landlord, so that a manager does not assume a system is being maintained by someone who thinks it belongs to someone else.

What an accountable executive can ask for

None of this requires fire engineering expertise to oversee. A handful of questions will separate sites with a working plan from sites with a filed one. For each location covered by the standard, can the site produce a plan that lists the hazards actually present, not the hazards in the template? Is every responsibility in paragraph (c) assigned to a named person or a role that exists at that site, and did that person confirm they know it? Does the plan state how often waste accumulation is checked, and is there a record? Do employees assigned to the location recall being told of the fire hazards of their job, as paragraph (d) calls for, rather than simply having been handed a handbook?

The harder problem is seeing the answers across the whole portfolio at once. An operator who has to phone sixty site managers to learn which plans are current has a visibility problem before they have a fire safety problem, and the first one makes the second invisible. If your organization cannot say today which sites have a completed, current plan with a live responsibility roster, that is a gap worth raising with your safety and compliance leadership, because the fix is confirming what is actually true at each site and not simply issuing another policy from the center.