Most nonprofit crisis communication plans are documents about approval chains. They describe who signs off on a statement, which is useful on day three and useless in the first hour. The piece almost every template omits is the delivery layer: the mechanism that gets word to staff, volunteers, and program participants as quickly as possible, before rumor does. That layer is text messaging, and it has to be built, registered, and populated before the crisis, not during it. Here is the plan structure with that layer in place.
What Counts as a Crisis for a Nonprofit
Write your definitions down in advance, because the argument about whether something is a crisis consumes the hour you needed for response. Common categories:
- Facility emergency at a shelter, clinic, food site, or program location: fire, flood, utility failure, violence, lockdown, or evacuation.
- Weather closure or hazardous conditions affecting program delivery and staff safety.
- Client safety incident: injury, death, allegation of abuse, missing participant, or an incident involving a minor or vulnerable adult.
- Funding loss and layoffs: a grant terminated, a contract not renewed, a program wound down.
- Leadership misconduct or abrupt departure, including board-level conflict.
- Data breach affecting donor, client, or employee records.
- Event cancellation with money, volunteers, and sponsors already committed.
- Reputational allegation: a news inquiry, a viral post, a regulatory complaint.
- Mass-casualty or community-wide event affecting the population you serve, where your organization becomes part of the response whether or not it planned to be.
Plan Structure
Crisis Team and Roles
Many social-service agencies mirror the role structure of the Incident Command System within the National Incident Management System framework, because it is the structure their county emergency managers and partner agencies already use. Adapted for a nonprofit:
| Role | Owns | Backup required |
|---|---|---|
| Incident lead | Activation, tiering, decision authority | Two named deputies |
| Spokesperson | All external and media statements | One named alternate |
| Communications coordinator | Message drafting, channel execution, send logs | One named alternate |
| Operations lead | Program continuity, site status, client safety | Per site |
| Board liaison | Board chair notification and board updates | Board vice chair |
| People lead | Staff and volunteer welfare, HR issues | One named alternate |
| Counsel and compliance | Legal review, notification obligations, insurer contact | Outside counsel on retainer |
Every role needs a named backup with the same access, including access to the messaging platform. Crises happen while the executive director is on a plane.
Severity Tiering
- Tier 1, site or single-incident: contained, no imminent safety threat beyond the site. Notify affected staff and site participants; log it.
- Tier 2, organization-wide: multiple sites, program interruption, or an incident likely to reach funders or media. Full crisis team activates; staff, board, and volunteer notification within the first hour.
- Tier 3, existential or life-safety: death, breach, criminal allegation, or community-wide emergency. Everything in Tier 2 plus counsel, insurer, regulators, and a public holding statement.
Decision Authority, Single Source of Truth, and Approval Chain
Name the person who declares the tier and the person who approves external statements, and write down what happens when neither is reachable within a stated number of minutes. Designate one internal channel as the single source of truth, and one public page that every message points to, so you update one place instead of nine. Pre-approve the holding statements below so the first-hour approval chain is a confirmation, not a drafting session.
Activation Triggers
Write triggers as observable facts, not judgments: a 911 call from a program site, a site closure, a media inquiry about an incident, discovery of unauthorized access to a system, a formal complaint, notice of grant termination, or the death or serious injury of a participant or staff member. Anyone can pull the trigger; only the incident lead sets the tier.
The Audience Map
Sequence matters as much as content. Staff should never learn about their own organization from the news.
- Staff, first, always, including part-time and overnight shifts.
- Board, immediately after or simultaneously for Tier 2 and above.
- Volunteers, especially those scheduled in the next 24 hours.
- Clients and program participants, with attention to the accessibility and language obligations below.
- Donors and funders, with grant-specific notification terms checked.
- Partners and referral agencies whose operations depend on yours.
- Media, through the designated spokesperson only.
- Regulators, licensors, and insurers, per statutory and contractual deadlines.
Channel Matrix
| Audience | Tier 1 | Tier 2 and 3 |
|---|---|---|
| Staff | Internal chat, site call | SMS first, then email, then all-staff call |
| Board | Email summary | SMS alert plus scheduled call |
| Volunteers | Scheduling tool | SMS to scheduled cohort, then email to all |
| Clients and participants | On-site notice | SMS in preferred language, posted notice, partner agencies |
| Donors and funders | None | Direct email or call to major and institutional funders; broad email after |
| Media and public | None | Holding statement, website, social |
SMS is the fastest broad-reach layer you control, because it needs no app, login, or data plan, and it can reach the volunteer already driving to a site you just closed. Delivery is never certain, so pair it with a second channel and a call-down list for anyone whose safety depends on the message. The enrollment mechanics for building that list are covered in our guide to emergency alert opt-in campaigns.
Pre-Drafted Message Templates
Write these now, with blanks. Keep them short enough to arrive as a single message.
- Staff, site closure: "[Org] ALERT: [Site] is closed [today/until further notice] due to [reason]. Do not report to this site. [Instruction]. Updates at [URL]. Questions: reply here."
- Staff, incident holding: "[Org]: We are responding to an incident at [site]. [Name] is incident lead. Do not speak to media; refer all inquiries to [spokesperson]. Next update by [time]."
- Volunteers, shift cancellation: "[Org]: Your [day/time] shift at [site] is cancelled due to [reason]. Nothing needed from you. We'll text when shifts resume."
- Participants, service interruption: "[Org]: [Service] is unavailable [dates] because of [reason]. For urgent help, contact [alternative] at [number]. We are sorry for the disruption."
- Participants, safety instruction: "[Org] URGENT: [Instruction, e.g. do not come to the [site] entrance]. [Alternative]. This is a safety message from [Org]."
- Board: "[Org]: Tier [n] incident declared at [time]: [one line]. Call at [time], link in your email. No board comment to media."
- Donors, brief: "[Org]: You may hear about [event]. Here is what we know and what we are doing: [URL]. Thank you for standing with us."
- All-clear: "[Org]: [Site/service] has resumed normal operations as of [time]. Thank you for your patience. Details at [URL]."
The First-Hour Checklist
- Confirm facts. Write down what is known, what is not, and who verified it.
- Ensure life safety and call 911 or emergency services if applicable.
- Declare the tier and log the time.
- Notify the crisis team and the board chair.
- Send the staff message. Staff first, without exception.
- Send participant and volunteer messages for anyone whose safety or plans are affected.
- Post the holding statement to the single public page.
- Route all inquiries to the spokesperson and tell everyone else not to comment.
- Contact counsel and insurer if the incident touches injury, allegation, employment, or data.
- Start the incident log: every decision, message, and time stamp, from minute one.
Holding Statements
A holding statement acknowledges, commits, and stops. "We are aware of [situation] at [site]. Our first priority is the safety of the people we serve and our staff. We are working with [authorities or partners] and will share more as soon as we can confirm it. Inquiries: [spokesperson, contact]." Do not speculate on cause, do not assign blame, do not promise a finding, and never comment on a personnel matter or an ongoing investigation beyond confirming that one exists.
Notification Obligations You Cannot Improvise
- Data breach: every state has a data breach notification statute with its own definitions, timelines, and attorney general reporting duties, and you may owe notice in every state where an affected person lives. If your organization runs health-related programs and is a covered entity or business associate, the HIPAA Breach Notification Rule at 45 CFR Part 164 Subpart D governs individual, HHS, and in larger breaches media notification.
- Governance and documentation: IRS Form 990 asks about your conflict of interest, whistleblower, and document retention and destruction policies. Those answers are public, and a crisis is when the gap between the policy you claimed and the practice you have becomes visible. The retention policy governs what you must preserve the moment an incident is foreseeable.
- Funder-facing statements: state charitable solicitation registration offices regulate how you represent your organization and its programs. Grant agreements frequently carry their own notice requirements for material adverse events, litigation, and leadership change. Read them before the crisis.
- Accessibility and language access: the Americans with Disabilities Act imposes an effective-communication duty, and federally funded programs carry language access obligations under Title VI of the Civil Rights Act. An urgent message that a participant cannot read is not a delivered message. Pre-translate your templates into the languages your programs actually serve and keep an accessible-format path.
- Text messaging law: the Telephone Consumer Protection Act governs your messaging, with an emergency-purposes exception for genuinely urgent messages concerning health and safety. That exception is narrow, it does not cover updates that are merely convenient, and it never covers anything with an ask attached. Keep your standard consent, identification, and opt-out practices intact and use the exception for what it exists for.
Continuity Planning and After-Action Review
Build the plan on top of the continuity-of-operations planning guidance published by FEMA and Ready.gov, the standard framework your county emergency manager, your insurer, and increasingly your institutional funders expect to see: an essential-functions list, an order of succession, delegations of authority, vital records identification, and an alternate facility plan. Each one gives your crisis messaging something concrete to say.
Within two weeks of standing down, run an after-action review: timeline reconstruction from the incident log, what the plan got right, where it failed, which audience learned late, which templates needed rewriting mid-crisis, and which contact list was out of date. Update the plan the same week, while the memory is honest. Then exercise it: a tabletop twice a year, including one unannounced test send to staff, is the difference between a plan and a document. Fundraising events are a good low-stakes place to practice rapid audience messaging, as our gala and auction texting guide describes, and the same infrastructure serves both.
This article is general information, not legal advice. Requirements vary by jurisdiction and change over time, so confirm your own obligations with qualified counsel or the relevant regulator.
Frequently Asked Questions
What should be in a nonprofit crisis communication plan?
A named crisis team with backups for every role, a severity tiering scheme, explicit decision authority and approval chain, observable activation triggers, an audience map in notification order, a channel matrix by audience and severity, pre-drafted message templates with blanks, holding statements, a first-hour checklist, an update cadence and all-clear procedure, notification obligations for breach and funder reporting, and an after-action review process. The plan should be short enough that someone can execute the first hour from it under stress.
Who should a nonprofit notify first in a crisis?
Staff, without exception, followed immediately by the board chair for anything above a contained single-site incident. Then volunteers scheduled in the next day, then clients and program participants whose safety or services are affected, then donors and institutional funders, then partners, then media through the designated spokesperson only. Staff learning about their own organization from a news alert or a social post is the most common and most damaging sequencing failure in nonprofit crisis response.
Can nonprofits text people during an emergency without consent?
The Telephone Consumer Protection Act includes an emergency-purposes exception for messages concerning imminent health and safety, which is why genuine emergency alerts sit differently from routine messaging. The exception is narrow: it does not cover operational updates that are merely useful, and it never covers messages carrying a fundraising or promotional ask. The reliable approach is to build a consented emergency alert list in advance, keep identification and opt-out handling intact, and treat the exception as a backstop rather than a strategy.
How often should a nonprofit send crisis updates?
Commit to a next-update time in every message and keep that commitment even when you have nothing new, because silence is filled by speculation. A common pattern is hourly in the first several hours of an active incident, then at named times each day, then daily until resolution. Always close with an explicit all-clear, sent to everyone who received the alert. An unclosed crisis leaves participants unsure whether services resumed and staff unsure whether to report.
Why include SMS in a nonprofit crisis plan?
Because it is usually the quickest way to reach staff on shift, volunteers already in transit, and program participants who do not check email, without requiring an app or a login. Email and social media are essential for detail and for the public record, but they do not reliably interrupt someone in time to change what they are about to do. Build the list, register the campaign, and pre-load the templates before you need them.
Write the Plan Before You Need It
FRANSiS gives nonprofits a registered alert channel with pre-built crisis templates, audience segmentation by site and role, delivery logs for your incident record, and an AI Powered Helper handling the question volume that follows any alert, with compliance supported throughout. See how it fits your nonprofit communication stack, then Contact us to build the layer most plans leave out.


