How to Become a Fire Chief

The chief works at a different altitude than the captain. Where the captain runs a station and an apparatus, the chief runs a battalion (multiple stations on shift), a division (operations, training, prevention, EMS, support services), or the entire department. The work shifts from tactical execution to strategic planning, political coordination, executive personnel decisions, and organizational leadership.

Battalion chief

The BC is the on-duty senior officer across multiple stations during a shift. On a working incident, the BC is the IC. Off the incident, the BC supervises captains, coaches them through hard personnel and operational decisions, manages cross-shift standards, handles citizen complaints that escalate beyond the captain level, and serves as the interface between line operations and the chief's office. BCs typically command 4-8 stations and 30-60 personnel per shift.

Deputy chief

The DC runs a division. Operations DC oversees the BCs and the line. Training DC owns the academy, in-service training, and certification programs. Prevention DC manages inspections, plans review, public education, and investigation. EMS DC oversees the medical program. Support Services DC handles fleet, facilities, IT, and supply. The DC works at the executive team level with the chief and other DCs to set department direction.

Fire chief

The chief runs the department. Reports to the city manager (or board, depending on jurisdiction). Sets strategic direction, owns the budget, represents the department to council and the public, manages the relationship with the union, and is the final authority on department-wide decisions. The chief role is roughly 70% political/strategic, 20% personnel, and 10% operational on a typical day.

What stays the same across chief ranks

• The work is more administrative than tactical
• The political dimension is real (council, city manager, union, peer agencies, media, public)
• Personnel decisions get harder (terminations, formal discipline appeals, succession planning)
• The loneliness of the role increases (fewer peers, more separation from line members)
• Strategic thinking is the differentiator (5-year planning, capital cycles, succession, culture change)

Chief promotional processes share structure with captain promotions but operate at higher scope and weight. A typical cycle:

1. Promotional announcement. Department announces eligibility, source list, weighting, timeline. Source list typically includes NFPA 1021 (Fire Officer III/IV), IFSTA Chief Officer, executive leadership references, department-specific SOPs, and recent organizational documents (strategic plan, budget, policies).
2. Eligibility verification. Time-in-grade as captain (typically 3-5 years minimum), education requirements (often bachelor's degree), certifications, evaluations, sometimes additional executive credentials.
3. Written examination. Multiple-choice anchored to FO-III/IV plus department source materials.
4. Assessment center. Multi-station battery, typically 5-9 stations including multi-incident command, executive in-basket, presentation, labor/media roleplay, writing, oral.
5. Chief's interview. Some departments include a final interview with the fire chief or chief's executive team that carries weighted points.
6. Total score and list publication. Weighted combination produces the final list.
7. Selection from the list. As vacancies occur, candidates are selected per department rules.

Total cycle time from announcement to list publication is typically 6-12 months. Chief vacancies open less frequently than captain vacancies; lists may live 2-4 years and many candidates wait 1-3 years on the list before promotion. Plan accordingly.

Chief eligibility requirements vary by department but commonly include:

• Time-in-grade as captain (typically 3-5 years, sometimes more for DC or chief positions)
• Bachelor's degree (required by many departments for BC and higher)
• Fire Officer III/IV certification or eligibility
• Executive Fire Officer (EFO) program completion preferred or required for senior chief positions
• Recent performance evaluations meeting standard
• Significant operational experience (number of working fires as IC, etc.)
• No active discipline within a specified window

Plan your study runway 2-5 years out. Effective preparation requires substantially more than the captain process:

• NFPA 1021 (Fire Officer III/IV). Read both at least twice. III emphasizes managing programs and personnel; IV emphasizes executive direction.
• IFSTA Chief Officer text. Standard reference for many departments.
• Department strategic plan, budget, current SOPs. The chief candidate is expected to know the department's direction, financial structure, and operational policy framework.
• Executive leadership reading. Beyond fire-specific texts: organizational behavior, public administration, change management. The chief role draws on broader leadership literature.
• Department-wide projects. Captains who will promote to chief have led or significantly contributed to multi-station initiatives, training programs, policy development, or capital planning.
• Multi-incident command reps. The single hardest skill chief candidates have to demonstrate. Tabletop, live drills, and AC simulation reps build the capacity.

Chief written tests are typically multiple-choice, 100-200 questions, anchored to NFPA 1021 Fire Officer III and IV plus department-specific references.

Common content areas

• Strategic planning and program management
• Personnel management at scale (succession, EEOC, labor relations, formal discipline appeals)
• Budget development and financial management
• Community risk reduction strategy
• Inter-agency coordination and unified command
• Department evaluation, accreditation (CFAI), ISO PPC ratings
• Multi-incident and area command
• Health and safety program oversight (NFPA 1500, NFPA 1582)
• Department-specific policies and current strategic documents

How to study

Same discipline as captain but at higher scope. Build flashcards, drill multiple-choice under timed conditions, drill department SOPs systematically, and use the source list as a checklist. Many chief candidates underestimate how much pre-existing operational knowledge is assumed; refresh on it before the cycle, don't try to learn it during.

The multi-incident station is the marquee assessment-center exercise for chief candidates. You're presented with two or more concurrent incidents in your jurisdiction and have to triage by life safety, allocate resources across scenes, communicate with multiple ICs, request mutual aid, and manage the political dimension (city manager, EOC, media).

What's being graded

• Area command structure. Did you formally establish area command? Confirm captain command at each scene? Set communication cadence?
• Resource allocation. Did you triage by life safety and not by symmetry? Did you hold reserve capacity?
• Communication discipline. Multiple incident commanders, dispatch, mutual aid, executive team, EOC if activated.
• Judgment under pressure. The scenario will throw curveballs (a third incident, a change in conditions, a request for additional resources you don't have).
• Adaptability. The injects test whether you can pivot.

The framework

Establish area command formally on the radio. Confirm IC at each scene. Set a cadence (typically every 5-10 minutes) for situation reports from each scene. Triage by life safety priority: an active-shooter incident outranks a hazmat tanker which outranks a vacant building fire. Allocate resources by need, not by symmetry. Request additional command staff (an additional BC from the adjacent battalion, or chief on-call) before you need them. Communicate with the city manager / EOC / chief on cadence.

What separates strong candidates

• Decisive resource reallocation when conditions change
• Clean handoffs and command transfers
• Time-stamped decision documentation (multi-incident reviews are extensive)
• Awareness of political and external dimensions (media, family reunification, after-action review prep)

The single-incident station tests BC-level command of one significant working incident over time, not the initial size-up like the captain station, but the extended command picture as the incident develops.

What's different from captain tactical IC

• Scope. Multiple companies, multiple sectors, longer operational period, more resource decisions.
• Strategic IAP. The incident action plan (IAP) becomes a real document, with documented strategy and tactics across operational periods.
• Command transitions. You may receive command from a captain on arrival, or hand off to a chief later. Both are graded.
• External coordination. Media, mutual aid, utility, PD, EMS staging, family notification all factor in.
• After-action discipline. The decision to brief the chief, document the timeline, and lead the AAR is part of the BC role.

How to prepare

• Drill scenarios that span 25-45 minutes of decision-making, not 5-minute size-ups
• Practice command transfers in both directions (receiving from captain, transferring to chief)
• Build the radio discipline of running an extended incident with multiple companies talking to you
• Read your department's significant-incident AARs to understand how command is documented

The executive in-basket is similar to the captain version in format but operates at chief scope. Items include city-manager requests, council briefing prep, union president communications, peer-chief coordination, executive personnel decisions, capital plan submissions, and major-incident AAR coordination.

What's being graded

• Strategic prioritization. Items now compete on strategic rather than operational urgency. A council briefing prep ask outranks a routine apparatus maintenance question.
• Delegation. Chiefs delegate more than captains. Items that should go to a captain or program manager should be assigned, not personally handled.
• Stakeholder awareness. Recognizing which items have political weight (council, city manager, union) and handling them with appropriate care.
• Written communication for executive audiences. Memos to the chief, briefs for the city manager, responses to the council member each require their own register.
• Completeness. Address every item.

Strategy

• Read all items first (5-7 minutes), then prioritize on a scratch matrix
• Write less, decide more. The panel grades decision quality, not prose volume
• Use templates for memos, briefs, and decision documentation
• Document delegation explicitly (who, what, by when)
• Watch the clock; reserve final 5-10 minutes for review

Brief a non-fire audience on a chief-tier topic in 5-12 minutes after a 15-30 minute prep window. Common audiences and topics:

• City council briefing on annual operations or strategic plan
• Board of directors briefing on a specific program (cancer prevention, EMS expansion)
• Community meeting on a fatal-incident response and lessons
• Executive team briefing on a multi-year capital plan
• Media press conference (sometimes with rolling cameras)

What's being graded

• Structure. Open, body, close. Don't ramble.
• Audience fit. Translate operational concepts into the audience's language. Council doesn't speak fire jargon.
• Evidence. Specific data, specific examples, specific dollar figures when relevant.
• Delivery. Voice, pace, eye contact, body language.
• Command presence. Calm, composed, authoritative without being theatrical.

The opener and closer

The first 30 seconds and last 30 seconds carry disproportionate weight. The opener should land in one sentence what the briefing is about and why the audience should care. The closer should leave them with the explicit next step or ask.

Roleplay stations put you in a live conversation with an actor playing a labor representative, council member, peer chief, or media reporter. The panel observes.

Labor roleplay

Common scenarios: union president wants to discuss a discipline matter, member complaint about a captain, contract interpretation question, grievance brewing on a department-wide policy. The skill being tested is your ability to engage substantively with the union without conceding management authority. Listen, acknowledge concerns, defer to formal process where appropriate, document. Don't fight; don't capitulate.

Media roleplay

Common scenarios: reporter asking about a fatal incident, post-mayday press conference, controversial line-of-duty death briefing. The skill being tested is your ability to stay on message, defer to active investigations appropriately, honor the affected family, and avoid the sound bite that becomes the story. PIO is your real-world resource; in the AC, you're it.

How to prepare

• Practice with a partner playing the difficult role
• Build templates: opener, listening, acknowledging, addressing, agreeing on next step, documenting
• Read recent post-incident press conferences from departments that handled them well
• Know your department's media policy and labor agreement

The chief writing exercise typically asks for a longer-form document than the captain version: a council brief, board paper, AAR for a department-wide incident, policy draft, public response letter to a fatality family, or memo to the chief on a strategic topic.

Common document types

• Memo to the chief on a battalion-wide AAR finding (mayday, multi-incident, etc.)
• Council brief on annual operations summary
• Policy draft for a battalion-wide standards reset
• After-action report on a multi-incident response
• Public response letter to the family of a civilian fatality
• Memo to chief on the capital plan and operating budget asks

What's being graded

• Document structure appropriate to the type
• Clarity at executive register
• Audience fit (chief vs. council vs. family vs. internal staff each get different tone)
• Strategic framing (chief documents reflect organizational thinking, not single-incident thinking)
• Factual accuracy with the provided facts
• Tone: authoritative, honest, never defensive

The chief oral board is typically longer and broader than the captain version: 25-40 minutes, 5-7 questions covering knowledge, judgment, vision, communication, and values. Questions test executive thinking distinct from tactical decision-making.

What chief panels look for

• Strategic awareness. Beyond the incident or shift, can you think department-wide?
• Political fluency. Council, city manager, union, peer agencies, media. Do you understand how the chief navigates them?
• Personnel maturity. Hard discipline cases, formal terminations, succession planning, all chief-level personnel work.
• Budget and capital thinking. Multi-year planning, capital cycle, operating-budget tradeoffs.
• Vision. Where do you see the department in 5 years and why?
• Values. Honesty about hard tradeoffs, respect for all stakeholders, commitment to the long arc of the career.

Common question categories

• Coaching a struggling captain through a hard year
• Captain who lies to you (integrity, formal discipline)
• Captain reassignment against his wishes
• Battalion-wide standards reset
• EEOC complaint against a captain
• Conflict between two captains at adjacent stations
• Working with the deputy chief / city manager / union
• Suicide loss in the battalion
• Cancer or occupational illness loss
• Multi-year strategic planning
• Federal disaster declaration / FEMA reimbursement leadership
• Speaking at a firefighter's funeral

The transition to chief rank is harder than most candidates expect, especially for BCs who promote and immediately have to command captains they used to ride with. The relational dynamics shift instantly.

The first 30 days as a new BC

• Meet with each captain in your battalion individually. Listen first, don't pitch your vision.
• Visit every station on shift in your first week.
• Hold the line on standards from day one, but don't run a battalion-wide reset in week one. Observe before changing.
• Lean on peer BCs for daily check-ins. The transition is lonelier than the captain transition was.
• Build a documentation discipline immediately. Captain coaching files, near-miss observations, performance notes. The BC's notebook is where battalion management lives.

Watch for

• The instinct to immediately fix everything you saw as a captain that frustrated you
• The opposite instinct to defer to existing patterns to avoid friction
• Being pulled into operational decisions that captains should own (lets them off the hook, signals you don't trust them)
• The political dimension showing up faster than expected (city manager wants something, council member calls)