Who can approve a statement when the CEO is unreachable? Who checks the facts before a customer update goes live? Define crisis response team roles and responsibilities around those decisions—not just a list of job titles.
Start with a named response lead, then assign owners for facts, communications, review, and stakeholder updates. Give each owner a backup and a clear handoff. Use the role map below to decide who leads, who advises, and who can act.
What does a crisis response team own?
Use a crisis response team to coordinate business decisions, establish confirmed facts, and manage stakeholder communications. Assign a response lead, an operational fact owner, a communications lead, relevant reviewers, and audience-specific owners. Separate the authority to approve a message from the task of publishing it, and name backups for both.
Why define ownership before a crisis?
Build the plan around moments when someone must act: activating the team, checking an allegation, approving an update, answering a reporter, or changing a public statement. For each moment, write down the owner and the limits of that person’s authority.
Do not make marketing responsible for fixing the underlying incident simply because the issue is public. Assign operational work to the people who can investigate and resolve it. Assign communications work to the people who can explain the response accurately.
Use the executive sponsor for decisions that require senior authority, not as the default editor of every message. Decide in advance which updates the communications lead may release and which commitments must go to leadership.
Who should be on the crisis response team?
Choose people by the work they can own. Treat this as a starting role map, not a requirement to create a separate position for every row. Add specialists when the incident calls for them.
| Role | Primary responsibility | Decision boundary |
|---|---|---|
| Response lead | Activate the team, set priorities, assign actions, and maintain the decision log. | Coordinate the response within delegated authority; escalate decisions outside it. |
| Executive sponsor | Authorize major business commitments and resolve disputes beyond the lead’s remit. | Own executive decisions without taking over every draft or channel. |
| Operations or incident lead | Investigate the problem, coordinate corrective work, and supply checked operational facts. | Own the incident work; do not release public claims independently. |
| Communications lead | Draft the message, coordinate audiences, brief speakers, and manage revisions. | Own message development within the agreed approval process. |
| Legal and relevant specialist reviewers | Review applicable obligations, sensitive disclosures, and technical accuracy. | Identify specific concerns and required changes rather than leave vague objections. |
| Spokesperson | Deliver approved statements and handle assigned interviews or briefings. | Speak within the brief; route unanswered questions back to the team. |
| Employee and customer owners | Prepare managers, support teams, and account teams to answer their audiences. | Use approved facts while adapting instructions to each audience’s needs. |
| Digital channel and monitoring owner | Publish approved updates, log inquiries, and flag claims that need review. | Own channel execution, not independent policy or factual decisions. |
Name a primary person and a backup for every active role. Include how to reach them outside normal hours and what the backup may approve.
Can one person hold more than one role?
For a small business, combine roles where practical, but keep the tasks distinct. An owner may lead the response and act as spokesperson. Before speaking, that person should still receive a checked fact brief and the appropriate review.
Avoid assigning one person to investigate, draft, approve, publish, and monitor at the same time. Where staffing is thin, prioritize a second set of eyes on consequential statements and a backup who can take over.
When should the team activate?
Set activation criteria in the crisis response plan. Consider credible threats to people, disruption to core services, sensitive allegations, possible reporting obligations, and issues that require several departments to coordinate. Do not use social engagement alone as the trigger.
For an issue below the activation threshold, name an issue-management owner and a review point. Specify what new information would require escalation. Give staff a route to report concerns without having to judge whether something is already a crisis.
If there is an immediate threat to people, follow established emergency procedures and involve the appropriate responders. Do not wait for a communications meeting to authorize urgent protective action.
How should facts become an approved statement?
Use an explicit handoff: the incident lead supplies checked facts; communications drafts; the relevant reviewers assess the draft; the named approver authorizes release; the channel owner publishes that version.
Keep one shared incident brief. Record what is confirmed, what remains unknown, who supplied each fact, and when it was last checked. Give unresolved questions an owner rather than treating them as blanks to fill with assumptions.
What should the approval record include?
Record the message version, intended audience, channels, approving person, and approval time. Include any limits on reuse. Approval for an employee update should not automatically mean approval for a press statement.
Set review deadlines that fit the incident and any applicable obligations. If the approver is unavailable, use the named backup. If reviewers disagree, escalate the specific disputed wording and the decision required—not the entire conversation.
What can the team say while facts are incomplete?
Prepare a holding statement that acknowledges the issue, describes only confirmed action, gives people a useful contact or update location, and states when further information is expected. Avoid unsupported causes, guarantees, blame, or a resolution date the team cannot substantiate.
If a published fact changes, assign someone to correct the affected channels and brief the people answering questions. Keep the earlier version in the internal record so the team can trace the change.
Who owns media, employee, and customer responses?
Give each audience an owner, but keep the underlying facts consistent. Change the level of detail and the requested action—not the account of what happened.
Media response
Route reporter inquiries to the communications lead. Log the outlet, question, deadline, and response owner. Brief the spokesperson on confirmed facts, unresolved questions, and commitments they may make. Do not improvise an answer simply to fill a silence.
Employees and managers
Assign an employee communications owner to prepare manager talking points and internal updates. Include what staff should do, where they should send inquiries, and when the next update will arrive. Avoid leaving managers to interpret a public statement as an internal instruction.
Customers and partners
Give support and account teams a shared response brief with clear escalation rules. Have them log questions the brief does not answer. Do not let separate teams make conflicting promises about refunds, service restoration, or other remedies.
Social and search visibility
Ask the digital owner to maintain the approved update location and check that channel messages point to it correctly. Log material questions and inaccurate claims for review. Decide which require a response, which need a correction, and which should be documented without engagement.
After the immediate response, use search reputation management as a separate recovery workstream. Assign its owner and review process rather than folding it into every urgent media decision.
How does the role map work in practice?
Use a hypothetical service outage to test the plan. Customers report failures while a reporter asks whether customer data is affected. The team has confirmed a service problem but has not established its cause.
The response lead activates the agreed group. The incident lead checks the scope and current operational status. Communications prepares an update that separates confirmed disruption from unanswered questions. Relevant technical and legal reviewers assess the wording before the named approver authorizes release.
The digital owner publishes the approved update. Customer support receives the same factual brief plus instructions for handling individual cases. The spokesperson answers the reporter within the approved scope and commits only to a follow-up the team can support.
Pause the exercise at each handoff. Ask who may act, what information they need, and who takes over if they are unavailable. Revise any instruction that depends on finding the right person by chance.
What should an outside crisis PR team own?
Scope an agency’s role around specific work: message development, media inquiry management, spokesperson preparation, monitoring, or response planning. Keep operational facts, business commitments, and final approval with named internal owners unless authority has been explicitly delegated.
Use the guide to what a crisis communications agency does to clarify the support you want before assigning it. Ask who will be available, how escalation works, and which tasks remain with your team.
When comparing crisis management firms, request a clear responsibility split. A proposal should distinguish drafting from approval, monitoring from engagement, and advice from authority to act. Test the handoff during a practice scenario before relying on it.
What mistakes should companies avoid?
- Making everyone an approver. Name the final approver and define each reviewer’s remit.
- Confusing speaking with deciding. Give the spokesperson boundaries for commitments and unanswered questions.
- Publishing unchecked assumptions. Keep confirmed facts separate from theories and open questions.
- Forgetting backups. Document who can act when the primary owner is unavailable.
- Leaving routine marketing unattended. Assign someone to review scheduled posts, emails, and campaigns against the incident.
- Closing the response without closing actions. Give each unresolved task an owner and a due date.
Look for these problems in the plan and in practice exercises. A correct job title is not enough; the person needs usable authority, access, and instructions.
How should success be measured?
Measure the team’s execution separately from the incident’s operational outcome. Review whether people received accurate, useful information and whether assigned work reached a clear decision. Do not treat a drop in mentions as the only sign of progress.
- Activation and coverage
- Record when the issue was escalated, when owners accepted their roles, and which responsibilities lacked coverage.
- Approval flow
- Track time from a review-ready draft to a decision. Document where work waited and why.
- Accuracy
- Review corrections, conflicting statements, and claims released without a recorded factual basis.
- Audience support
- Check whether employees, customers, and partners received usable instructions and whether unanswered questions reached an owner.
- Follow-through
- Track promised updates and corrective actions against their recorded owners and due dates.
Set targets that fit the incident, your staffing, and applicable obligations. Afterward, review the decision log with the people who did the work. Fix unclear ownership before adding more steps to the plan.
Start with one deliverable: a current role map with named people, backups, decision limits, and contact routes. Then run a short scenario that forces a real handoff. Use what breaks to revise the plan.
Put the handoffs on the agenda
Bring your current role map and approval path to a strategy conversation with Percepture. Focus the discussion on ownership, escalation, and the communications support your team needs.
About Bob Generale
Bob Generale is President of Percepture.
