A crisis briefing agenda should do more than organize speakers. It should convert the latest incident information into priorities, decisions, assigned actions, communication requirements, and a clear next briefing time.
If the meeting ends with everyone better informed but no one clearer about what happens next, the agenda has failed.
In short
BCMMetrics practitioner guidance uses APIE as a simple operating rhythm: Assess, Plan, Implement, Evaluate. The model is not a substitute for an organization’s command structure, regulatory duties, or formal incident-management system. It gives the briefing a repeatable path from changing facts to the next cycle of work.
The Federal Emergency Management Agency’s incident action planning process follows a comparable progression: understand the situation, establish objectives, develop the plan, prepare and disseminate it, then execute, evaluate, and revise. FEMA does not prescribe APIE or this corporate agenda, but its guidance reinforces the value of recurring planning cycles tied to operational periods.
| APIE stage | Questions for the briefing | Required output | Record to update |
|---|---|---|---|
| Assess | What changed? What is confirmed? What remains unknown? Who and what are affected? Are there immediate life-safety, operational, legal, regulatory, financial, customer, or reputational concerns? | Concise situation summary, material changes, current impacts, assumptions, and open questions | Incident log and situation report |
| Plan | What must the team accomplish before the next briefing? Which decisions are required now? What constraints, dependencies, or scenarios could change the plan? | Priorities, three to five objectives, decisions, escalation items, and communication needs | Briefing record and incident action plan |
| Implement | Who owns each action? What is due, by when, and with what resources? Which teams, suppliers, sites, or executives must be involved? | Actions, owners, deadlines, resource needs, handoffs, and approved messages | Action tracker, communications record, and incident action plan |
| Evaluate | What was completed? What effect did it have? What is late, blocked, or no longer appropriate? What should continue, change, or stop? | Status updates, revised assumptions, changed priorities, lessons, and the next briefing time or trigger | Incident log, updated plan, and next agenda |
This table is adaptable practitioner guidance, not a formal standard or exhaustive control set. The organization should tailor it to the incident, industry, response structure, and legal or regulatory obligations.
Start with what changed since the previous briefing. A full retelling of the incident consumes time and can bury the decision that brought people together.
Separate three categories:
FEMA’s ICS 201 Incident Briefing form includes a situation summary, current and planned objectives, current and planned actions, the response organization, and allocated resources. Corporate teams do not need to copy the form unless it fits their operating model, but those categories are a useful check against incomplete briefings.
Define the period the team is planning for. It may be the next 30 minutes during a fast-moving cyber event, the next shift during a facility disruption, or the next day during an extended supplier outage.
State the few outcomes that matter most during that period. Keep objectives separate from tasks. “Maintain customer order intake through the next shift” is an objective. “Call the alternate contact center provider” is an action that may support it.
Every action needs an owner, due time, and completion condition. “Operations will investigate” is not an assignment. “The operations lead will confirm alternate-site capacity by 2:30 p.m.” is.
The briefing should also expose dependencies. An owner cannot complete a customer message without legal approval, confirmed service impact, and an agreed release time. Record those conditions beside the action rather than discovering them after the meeting.
Do not use the next briefing only to request new updates. Start by evaluating what the previous plan produced.
Ask:
The answers become the assessment for the next APIE cycle. Download APIE in Action: A Strategic Briefing for Crisis Management Teams for a practical explanation of the full cycle.
A standard agenda reduces the chance that pressure, hierarchy, or the loudest voice will control the meeting. The exact order can change, but every briefing should produce five visible outputs:
Michael Herrera has observed in client work and exercises that improvised crisis documentation and unstructured briefings create confusion about the current situation, required actions, and ownership. His broader guidance on crisis event documentation explains why standardized situation reports, agendas, action plans, and trackers work as a connected system.
A practical agenda can follow this sequence:
The readback matters. It gives each owner a final opportunity to correct an assignment, deadline, or decision before the team disperses.
Consider a critical distribution site that loses utility power. The generator is running, but building cooling is unstable, network access is intermittent, and the last same-day shipping cutoff is approaching.
An unstructured meeting may produce 20 minutes of overlapping updates. An action-oriented briefing produces a usable record:
The example is hypothetical. The thresholds, authorities, safety requirements, and external obligations must come from the organization’s plans and subject-matter experts.
Operational and executive briefings should use the same underlying incident record, but they should not contain the same level of detail.
| Operational crisis-team briefing | Executive briefing |
|---|---|
| Current facts, impacts, assumptions, and unknowns | Concise incident scope, business impact, and likely trajectory |
| Progress against objectives and detailed cross-functional actions | Progress against the few priorities that matter to the organization |
| Owners, deadlines, dependencies, resource needs, and blocked work | Decisions, approvals, risk acceptance, funding, or external commitments requiring executive authority |
| Detailed communication tasks and handoffs | Material employee, customer, regulator, investor, insurer, or reputation considerations |
| Tactical decisions for the next operational period | Strategic choices, exposure, confidence level, and decision deadlines |
The executive briefing should not become a transcript of the operational call. Distill the information to what leaders need to understand, decide, approve, or communicate.
Conversely, do not let an executive discussion change priorities without recording the decision and returning it to the operational team. The two briefings must share one decision trail.
For guidance on escalation, see How to Tell an Incident from a True Crisis. For team behavior under pressure, read 6 Traits That Set Great Crisis Teams Apart.
The agenda should not live as an isolated meeting document. It sits between the information entering the response and the work leaving the meeting.
This connection is an important software-evaluation criterion. During a demonstration, ask the vendor to show how a team would:
BCM One supports this execution layer. Approved product materials show that teams can maintain location details, connect recovery plans, store site contacts, log events by site, update incident details as events unfold, create briefing-session agendas, attach incident action plans, and access archived closed incidents.
The software does not decide what the team should prioritize or whether a decision is sound. The organization remains responsible for leadership, authority, judgment, communication, and execution.
For the written plan that follows the briefing, see Corporate Incident Action Plan: What to Include. For deeper advisory guidance on emergency-plan design, see MHA Consulting’s six essential emergency-plan tasks.
Use the agenda during an exercise before relying on it during a live event. Test whether the team can move from situation assessment to priorities, decisions, assignments, communication, and a new briefing cycle without inventing the process as it goes.
After the exercise, review where the agenda slowed the team down, where information was missing, which decisions lacked an owner, and whether the incident record matched what participants believed had been decided.
A strong briefing does not eliminate uncertainty. It gives the team a disciplined way to act, document, evaluate, and adjust while uncertainty remains.