Skip to content
Tailboard

The building guide

From blank page to adopted policy in nine steps.

No tricks, no templates yet — just the process. If you follow these steps, you’ll end up with a policy that’s clear, defensible, and actually used.

Before you start

You don’t need to write the whole book in a weekend.

One good policy beats twenty half-baked ones. Write one this month. Train it next month. Write another. Departments that try to do it all at once end up with a pile of policies nobody follows.

Our recommended list sorts policies by priority so you know what to tackle first.

01

Pick a real problem.

Good policies answer a question someone already asked. Start with the last call that felt uncertain — who was in charge, what the plan was, how it ended. That’s your policy topic. Don’t write for problems you’ve never had.

Quick tips

  • Ask your officers: “What did we argue about on the last call?”
  • Check NIOSH or state LODD reports in your size/region — they’re a roadmap of gaps.
  • Look at your insurance carrier’s last recommendations. Useful outside perspective.
02

Get three people in a room.

Policy written by one person — no matter how smart — misses things. At minimum: a senior firefighter, a company officer, and the chief. Add EMS, fire prevention, or mechanics if the topic touches them.

Quick tips

  • 15 minutes of argument now saves 15 hours of rework later.
  • The person who runs the call should write the first draft — not the chief.
  • If nobody disagrees in the meeting, you probably haven’t been specific enough.
03

Find the standard that already covers it.

Almost every topic you’ll write about is already addressed by NFPA, OSHA, your state fire code, or your region’s model practice. Don’t reinvent — align. Cite the source in the policy so reviewers can find it.

Quick tips

  • NFPA 1500 (safety), 1710/1720 (deployment), 1700 (strategy) cover most of it.
  • OSHA 1910.134 (respiratory), 1910.146 (confined space), 1910.120 (HAZWOPER) are federal law.
  • Your state might have its own stricter rules — check before you write.
04

Write it for the newest recruit.

If your 90-day probie can’t understand it standing next to an engine at 2 a.m., rewrite it. Short sentences. One idea per bullet. No jargon you didn’t just define. No “shall,” no “hereby,” no paragraph-length requirements.

Quick tips

  • Use second person (“You will…”) or imperative (“Don the mask…”). Skip “the firefighter shall.”
  • If a sentence takes more than 20 words, it’s probably two sentences.
  • Every “usually” or “typically” is a decision waiting to happen. Say who decides.
05

Use a boring, predictable structure.

Every policy in your book should look the same. Purpose, scope, definitions, procedure, responsibilities, references. Boring is good. Crews reach for the right section faster when the pattern never changes.

Quick tips

  • Number every section. Reference numbers by ID, not page.
  • Put the most important thing first. Skim-readability beats completeness.
  • Include a “related policies” section. Policies don’t stand alone.
06

Review for traps.

Now read it back like you’re an outside reviewer who wasn’t on the call. Anywhere the policy says one thing and you do another, you’re exposed. Anywhere it’s ambiguous, someone will get it wrong. Fix those before adoption, not after.

Quick tips

  • Run it past one person who wasn’t in the room. Their confusion is a quick audit.
  • Check consistency with other SOGs. Contradictions between docs come back to bite you.
  • Cross-check the language against the NFPA / OSHA standard you’re aligning to. Word choice matters.
07

Chief signs. Clock starts.

A policy isn’t in effect until the chief (or AHJ, depending on your structure) formally adopts it. Date it. Number the version. Archive the old one — don’t delete it.

Quick tips

  • Adoption signature should include: name, title, date, effective date.
  • Announce effective dates in roll call and by email. Two channels, minimum.
  • Never backdate. The old policy was in effect until the new one was signed.
08

Train it. Document the training.

An un-trained policy is worse than no policy. If there’s a bad call tomorrow, “nobody knew about it” is not a defense — it’s an aggravating factor. Train, sign in, file the sign-in sheet.

Quick tips

  • Tabletop new policies at the next drill, even if they seem obvious.
  • Roster sign-in sheets are the paper trail. Keep them for at least 7 years.
  • Pop-quiz during company inspections. Comprehension, not memorization.
09

Review it on a schedule.

Every policy gets a review date. Annual is a good default; critical safety SOGs (RIT, Mayday, SCBA) should be reviewed after every major incident, too. Out-of-date policy is worse than no policy.

Quick tips

  • Put review dates in the policy footer. Calendar them.
  • After-action reviews feed straight into policy updates. Close the loop.
  • If nothing has changed in 3 years, you probably aren’t looking hard enough.

Anatomy

What every policy should include.

Boring structure beats clever structure. Use the same skeleton every time so crews always know where to look.

Header

Title, number, effective date, review date, adoption signature, version.

Purpose

One sentence. Why does this exist? What does it prevent?

Scope

Who does it apply to? Career? Volunteer? Mutual aid? All apparatus?

Definitions

Every term of art, spelled out. If you use it once, define it.

Procedure

The actual what-to-do. Numbered steps. One action per line.

Responsibilities

Who does what. IC. Company officer. Crew. Dispatcher.

Training requirements

How often, what format, who’s responsible for verification.

References

NFPA/OSHA/state code sections this policy is anchored to.

Watch out

Common ways this goes wrong.

Writing policy no one follows.

If the real procedure is different from the written one, you have two problems: a useless document and a legal liability. Write what people actually should do, then train to it.

Copy-pasting another department.

Borrowing is fine — it’s how the fire service has always worked. But staffing, apparatus, water, and response times differ. Adapt every policy to your conditions or it’ll lie to you on a call.

Using “shall” everywhere.

Crews skim. Use “must,” “will,” or plain imperatives. Reserve “shall” for the handful of places you truly mean “no deviation ever.”

No version control.

Two versions of the RIT policy floating around the station is how someone gets hurt. One current version. Archive everything else. Date every adoption.

Don’t start from scratch

Grab a template and start editing.