Maryland NFPA staffing benchmark — methodology

1 · Maryland's jurisdiction-based structure

Unlike New Jersey, where each independent municipal fire department is its own record, Maryland fire and rescue protection is organized by jurisdiction — 24 of them: the 23 counties and the independent city of Baltimore. A single jurisdiction typically combines county career personnel, municipal departments, independent volunteer corporations, combination stations, and automatic/mutual aid — all under one countywide (or citywide) deployment system. Forcing this into NJ's one-department-per-record model would misrepresent how Maryland actually delivers fire protection.

2 · One assessment per jurisdiction — never duplicated

Each of the 24 jurisdictions is assessed exactly once. Department, company, or volunteer-corporation names are recorded only as context — to explain governance or deployment — and never receive a separate NFPA verdict for the same underlying evidence. A jurisdiction combining a county fire department with several independent volunteer corporations is still one record, one assessment.

3 · Composition is never guessed from governance names

Many Maryland "volunteer fire companies" are staffed, in whole or part, by county career personnel — the name alone proves nothing. A jurisdiction's career/volunteer/combination composition is recorded only from an official statement (the jurisdiction's own fire/EMS department, county government, or an adopted budget/ordinance) — never inferred from a corporation's name, a county's size, or its rural/urban character.

4 · Benchmark: NFPA 1750:2026, Chapters 4–6

This reuses the exact NFPA 1750:2026 benchmark engine built for New Jersey — no separate standards module. Career-staffed companies are compared to the baseline minimum of 4 per engine, ladder/truck, or quint (tanker/tender: 2). The elevated (5) and maximal (6) zone/hazard minimums are applied only where a jurisdiction's own source documents the qualifying condition — urban, high-volume, geographically restricted or isolated, tactical-hazard, high-hazard, or dense-urban — and are never inferred from a county's population, density, or reputation.

5 · What this does not assess

The effective response force (low 20/21, medium 28/29, high 42/43) and response-time objectives (turnout 80s fire / 60s EMS; travel 240/360/480/610s, each ≥90%) are not assessed in this staffing-only layer. A jurisdiction's baseline result is never a claim of full NFPA 1750 compliance.

6 · Evidence rules

• Roster is not on-duty staffing. Career/volunteer membership counts are never used as a staffing figure.
• No arithmetic. Personnel are never divided by shifts, stations, companies, or apparatus to manufacture a per-company figure.
• Department-wide ≠ per-company. A disclosed department-wide daily total is shown, but produces no per-company verdict unless the source explicitly states that relationship.
• Source quality is ranked. Official county/city/fire-department/state sources; adopted budgets, CBAs, codes, ordinances, annual reports, policies; CPSE/CFAI accreditation and Standards of Cover; official volunteer-corporation/municipal sources; institutional reports — in that order. News, social media, job postings, and vendor pages are context only, never proof.

7 · Benchmark, not mandate

NFPA 1750:2026 is a consensus deployment standard, not automatically a legal mandate. A department is legally bound only where its Authority Having Jurisdiction has adopted it. This assesses baseline company staffing only — not higher zone/risk staffing, effective response force, or response-time performance — and is not a legal finding.