Fire department policy-management software

Get your policies in order.Keep them there.

SOPReady is policy-management software for fire departments. Start from scratch or bring the binder you already have, then build, organize, review, distribute and maintain your policies in one place — find what's missing and stay ahead of the reviews and acknowledgments.

  • Free for 30 days
  • No credit card required
  • PO & invoice billing
See a finished one — real SOP, 3 pages, PDF
Your approval
Nothing becomes department policy until you approve it
Your current version
Members receive the version actually in effect
Your records
Versions, acknowledgments and review history stay on the record

Two ways in

Start from scratch, or start from the binder.

Either way it is the same software, the same price and the same lifecycle after the first week.

Starting from scratch

Build the program from the ground up.

A new department, a rebuild, or a manual that never got past the first few policies.

  1. Start with the 95-topic reference list and pick the policies your department needs.
  2. Each one is drafted from your own apparatus, staffing and rank titles. Edit any line before it goes anywhere.
  3. Everything lands in one library as a numbered draft, in no effect until your department approves it.
  4. Approve, distribute, collect acknowledgments. The program exists from the first approval.

Already have SOPs

Keep the manual you already have.

Seventy policies in a binder, a shared drive nobody has opened since 2019, or both.

  1. Upload what you have — PDF or Word, up to 4 MB each, one SOP per file.
  2. SOPReady matches each file to a topic by name and credits it, so your list shows what's already on file.
  3. Your document stays yours. SOPReady credits the file you uploaded; it doesn't rewrite it.
  4. Ask for a read on any file and it reports the topic it covers and whether it looks out of date.
  5. Draft only the topics with nothing behind them.

Credited, not converted

Distribution, version history and acknowledgments apply to SOPs you keep in SOPReady. An upload stays the file you uploaded — write that topic here when you want those on it.

Most departments do both — upload what exists, draft what doesn't. There is no separate plan for either, and no limit on how many SOPs you write or keep.

See where you stand

Know what you have. See what needs attention.

SOPReady lines your department up against 95 fire-department policy topics and shows, topic by topic, what is on file and what isn't. Bring in the SOPs you already have and the picture includes them. Bring in nothing and the same list is your manual's table of contents.

Verified
An approved SOP in effect, or an uploaded document you confirmed covers the topic. Those are the only two states that count toward your coverage figure — SOPReady will not report a topic as covered on an AI read alone.
Needs review
SOPReady read an uploaded document and proposed a topic for it. It waits for you to confirm or correct it, and is not counted as covered in the meantime. Confident proposals can be accepted in one batch; unsure ones ask you to open the file.
Outdated
A document that was read, matched to the topic, and came back with something to look at — a missing element, or a citation to check. It is on file and still needs a decision.
Filename only
An upload named like the topic that nothing has read yet. It is on your list and it is not counted either way until someone settles it.
Missing
Nothing on file for the topic at all. For a department starting out, this is most of the list — and it is the build plan.

Pick the gaps you want closed and they arrive as drafts for your department to review.

Worth knowing

A filename is not a reading

Matching by name puts a file on your list; only a read counts the topic as covered. You ask for a read one file at a time, and it reports the topic that document covers and whether it looks out of date.

A gap is a gap, not a finding

SOPReady compares your documents against a reference list of fire-department policy topics and tells you what you have nothing on file for. It does not audit your department, speak for a reviewer, or certify anything.

See it work

One department, one policy, one year.

Six screens from the product itself — from where the department stands, through one policy into effect and signed for, to the review that brings the whole thing back twelve months later.

Steps 2 to 5 follow SOP-041 Daily Apparatus Inspection from a gap to a signed record. Steps 1 and 6 are the program it lives in, before and after.

SOPReady

Shows where the department's policy coverage stands, what is due, who is behind, and what is mid-revision — the same screen the app opens on.

You

Picks the next thing worth doing. Close a gap, approve a draft, chase an acknowledgment, or start a review that is coming due.

/dashboard

Dashboard

Riverview Fire Department

18 active members

Policy coverage

68%

65 of 95 topics verified · as of Mar 4, 2026

SOPs in effect

62

Approved, with a version members are held to

Ack rate

78%

4 members behind on at least one SOP

Needs attention

4

Reviews due and drafts awaiting approval

Action required

  • 3SOPs due for reviewStill in effect — the date is a prompt to re-read, not an expiry
    Review
  • 1Draft waiting on your approvalNot in effect and not sent to anyone until you approve it
    Open
  • 4Members behind on acknowledgmentsBehind on at least one SOP in effect
    Remind

Revision in progress

SOP-017Mayday Operations

Current policy

Version 3 · In effect

What members are held to, and what they acknowledge.

Revision

Version 4 · Draft

Not in effect. Nothing changes for members until it's approved.

Add to the library

Build manualGenerate an SOPUpload existing SOPs

A department starting with nothing on file sees this same screen — coverage at zero and the whole reference list waiting under Build manual, every topic pre-selected. No upload required to begin.

You open on what needs attention, not on an empty document. A department with nothing on file sees the same screen with the whole reference list waiting.

Step 1 of 6

Illustrative walkthrough. Riverview Fire Department, its roster, its apparatus and the dates and counts shown are invented for this example — no customer's data appears here.

The repeating work

The SOP is done. The job isn't.

A revision, a new hire, a review date, a carrier asking for the records — each one starts work the writing never finished. That is what SOPReady is doing in year five.

Every version sent

Acknowledgment status

Who has acknowledged the current version of each SOP and who hasn't, per member and per document. Remind whoever is outstanding.

Every revision

Version history

Every approved version is kept. See what changed from the version before it, and which version each member actually signed — a revision doesn't inherit last year's signatures.

Every new hire

New hires

Send one link. A new member reads the SOPs you selected and signs for them before their first shift, without an account to create.

Every twelve months

Annual review

A generated SOP carries a review date twelve months out. Once it's approved you get an email 30, 14, and 7 days before that date — so a stale SOP is a decision, not an oversight. Mark it reviewed with no changes needed and the date moves while every signature stays.

Every action

Audit trail

Generations, edits, approvals, distributions and acknowledgments are written to your department's audit log, readable and filterable in the app.

When someone asks

Reports and exports

Pull a department compliance report or a per-member training certificate as a PDF, or export your whole department — SOPs, roster, acknowledgments, audit log — as a ZIP you keep.

Policy framework

A 95-topic framework built for fire departments.

Standards are referenced where one applies. Most topics are mapped to a published NFPA standard, cited by number and never reproduced. The rest are topics no standard covers but a manual still needs: EMS patient-care protocols, dispatch and radio practice, department administration. A citation is not a certification, and some topics have no standard to cite.

Fireground Operations15
Administration & Organization10
Personnel10
Safety & Health10
Apparatus & Equipment9
EMS Operations8
Special Operations7
Training6
Fire Prevention6
Hazardous Materials5
Communications5
Emergency Management4
12 categories, referencing 15 NFPA standards
NFPA 470NFPA 921NFPA 1010NFPA 1020NFPA 1030NFPA 1142NFPA 1400NFPA 1550NFPA 1580NFPA 1660NFPA 1750NFPA 1850NFPA 1910NFPA 1930NFPA 2500

Generated SOPs are draft material

Every generated SOP requires department review and approval. You edit it and approve it, or it never goes anywhere.

References, not certification

SOPReady cites the standard sections it drew from. It does not reproduce NFPA text and it does not certify your department.

NFPA 1500 has called for written standard operating procedures as part of a department's occupational safety and health program since its first edition in 1987. It is a consensus standard until your state or your AHJ adopts it — and many have.

Why this exists

Our mission is to give every fire department the tools to keep its policies current, understood, and on the record.

Fire departments shouldn't need a dedicated compliance staff or an enterprise software budget to maintain professional, accountable SOPs. We build SOPReady around the way departments actually operate.

Built for fire departments across the United States — from single-station volunteer companies to career departments with a training division.

Pricing

One complete policy system. One price.

Enter your active roster size and read your annual price right here.

Everyone who needs to read and sign SOPs, counted once each: career, volunteer, paid-on-call, probationary, officers. Former members you deactivate stop counting.

$3,000/year

Up to 25 active members12-month subscription

$250 a month equivalent.

  • Unlimited SOPs, written or uploaded
  • Acknowledgment tracking, per member and per version
  • Compliance reports and member certificates
  • Full audit trail and data export

One product, priced on your active roster size. Every department gets every feature.

How to buy

Term
Paid once for the year, or in 12 equal payments. Both come to the same annual total on the same twelve-month term.
Paperwork
The price is on this page. Settings → Billing has a formal quote PDF with a blank PO line, and a W-9 comes back when you ask for one.
Invoicing
Card, or an invoice to your treasurer on NET 30 carrying your PO number.
Your price
Locked for the term. Hiring or losing members doesn't change the bill — your roster is read again at renewal.
Start free for 30 days

No credit card to start · No setup fees

Common questions

Questions chiefs ask before signing up

Straight answers on approvals, acknowledgments, billing, and what happens to your data.

Get your policy program in order. Keep it that way.

Starting at $3,000/year for departments with up to 25 active members.