How to Conduct a Clean ICS Transfer-of-Command Briefing

A transfer of command is more than a change in names. It is the point at which responsibility for the incident moves from one Incident Commander to another, and the quality of that handoff can directly affect safety, coordination, and continuity of operations.

FEMA’s ICS 200 materials describe transfer of command as a defined process that includes a briefing, a clear effective time, and notification to incident personnel. The arrival of a more qualified person does not automatically require an immediate transfer; agency policy, jurisdiction, incident needs, and command effectiveness still govern the decision.

Know why command is transferring

Command may transfer because a jurisdiction or agency is legally required to assume it, the incident has changed in complexity, an incoming team has additional capability, leadership needs relief during an extended operation, or an agency administrator directs the change. Establish the reason before the briefing so both commanders understand the authority, timing, and expectations.

If jurisdictional authority, agency policy, or a delegation of authority is unclear, resolve that issue through the responsible officials. A briefing supports the transfer; it does not create authority that does not otherwise exist.

Set an exact transfer time

A vague handoff creates operational risk. The outgoing and incoming commanders should agree on when the transfer becomes effective and how it will be announced. Until that point, personnel need to know who holds command authority.

Notify the Command and General Staff, communications or dispatch functions, agency representatives, cooperating organizations, and other personnel who need the information. The announcement should identify the incoming Incident Commander and the effective time without interrupting urgent life-safety operations.

Use a structured briefing

FEMA identifies the ICS Form 201 as a standard tool for briefing an incoming Incident Commander or team. It captures the incident situation, current objectives and actions, the active organization, and the status of assigned or ordered resources. The form supports the conversation; it should not replace a direct briefing when conditions allow.

A practical transfer-of-command briefing should cover:

• Situation: what has happened, the current operating picture, affected area, projected changes, and significant unresolved facts.
• Safety: responder and public hazards, controls already in place, urgent medical concerns, and any activity that should be stopped or reassessed.
• Objectives and priorities: current incident objectives, command emphasis, legal or policy constraints, and decisions awaiting command direction.
• Organization: the activated ICS structure, key personnel, agency representatives, span-of-control concerns, and anticipated expansion or contraction.
• Resources: resources assigned, available, out of service, ordered, en route, or needing relief; staging and accountability status should also be clear.
• Communications: primary and alternate channels, contact methods, interoperability issues, and any degraded systems.
• External coordination: cooperating agencies, elected or executive leadership, public information issues, community impacts, and partner commitments.
• Planning cycle: the current operational period, meeting schedule, IAP status, reporting deadlines, and the next decisions required.

Brief from current information—not memory alone

Bring the latest map, objectives, organization chart, resource status, communications information, safety concerns, open actions, and significant messages. Label uncertain information as unverified and identify who is working to confirm it.

For an initial response, the ICS 201 may serve as an initial action worksheet and part of the initial IAP. As the incident matures, the incoming commander should also receive the current IAP and relevant status products. Local forms and systems may supplement these documents, but the briefing still needs a coherent operational picture.

Confirm understanding before the announcement

The incoming commander should restate the most important priorities, immediate hazards, resource gaps, and pending decisions. This short confirmation helps reveal misunderstandings before responsibility shifts. The outgoing commander should identify what support remains available after the transfer and whether a formal closeout, reassignment, or demobilization step is required.

Practice the handoff before a real incident

Transfer of command is an excellent tabletop objective because it forces participants to connect authority, situation reporting, resource tracking, safety, and communications. A useful inject might require a local Incident Commander to brief an incoming team while communications are degraded and several resource orders remain unresolved.

Response Depot’s Tabletop Exercise Design Kit includes editable materials for building the scenario, managing injects, capturing observations, and tracking improvements. Customize any exercise to your organization’s authorities, procedures, and hazards.

Practical takeaway

A clean transfer answers four questions for everyone involved: who is in command, when the change takes effect, what the incoming commander understands, and how the organization was notified. Treat the briefing as an operational control—not a ceremonial exchange.

Official sources

• FEMA EMI: Transfer of Command, extracted from IS-200.c
• FEMA EMI: ICS Form 201, Incident Briefing
• FEMA EMI: ICS Resource Center and forms
• FEMA EMI: IS-200.c course overview

Sources checked October 22, 2026. This article provides general organizational guidance. Follow applicable laws, authorities, agency policies, incident-specific direction, and current FEMA materials. Cover image is an original editorial illustration and does not depict an actual incident.