5 Preparedness Questions Every Nonprofit Leadership Team Should Ask

The questions nonprofit leaders should ask about preparedness start with a practical concern: if your nonprofit suddenly lost access to its systems tomorrow, how long could you continue serving the people who depend on you?

An hour? A day? Several days?

For nonprofit leaders, the real concern is not simply that “the technology went down.” It is what happens next.

Programs may be delayed. Staff may lose access to critical information. Donations could be interrupted. Sensitive donor or client information may become unavailable. And eventually, someone on the board may ask:

“Were we prepared for this?”

September is National Preparedness Month, making this a useful time to answer that question before something goes wrong.

You do not need an all-day planning retreat to get started.

Bring your leadership team together for 15 minutes and work through these five questions nonprofit leaders should ask about preparedness.

1. If We Couldn’t Operate Tomorrow, What Would Need to Come Back First?

Most nonprofits depend on more technology than leadership may realize.

Email. Donor management systems. Financial applications. Client records. Grant documentation. Microsoft 365. Phones. Scheduling. Cloud files. Payment systems.

But if everything suddenly became unavailable, trying to restore everything at once could create more confusion.

The better question is:

What absolutely has to work for us to continue carrying out our mission?

For one nonprofit, that may be access to client records so caseworkers can continue serving families.

For another, it may be the donor database during an important fundraising campaign.

For a healthcare-related nonprofit, access to sensitive records and communications may be essential.

For an organization providing meals, shelter, counseling, education or other critical services, even a few hours of downtime can affect real people.

Leadership should identify the most mission-critical functions first, then determine which systems those functions depend on.

It should also understand how long each critical function can realistically remain unavailable before the disruption begins affecting services, funding, staff productivity or the people the organization serves.

That is why organizations evaluating zero downtime IT services should focus first on the systems and services where extended interruption would create the greatest mission impact.

That simple exercise gives your organization something incredibly valuable during a disruption:

priorities.

Instead of scrambling to restore everything, your team knows what needs attention first so you can get back to serving people faster.

7tech’s nonprofit client experience reinforces the importance of looking at the technology behind the mission, not just individual applications. At both STARRY and ChildSafe, the way employees accessed systems and information affected how flexibly or effectively they could work.

STARRY’s distributed workforce was hindered by its existing server and VPN environment, while ChildSafe’s reliance on on-premises file storage limited employees’ ability to work flexibly.

Both organizations later reported benefits from moving toward more flexible, location-independent access. Their experiences do not establish what every nonprofit should restore first, but they do illustrate why recovery planning should consider how employees actually reach the systems and information their work depends on.

Preparedness takeaway: Restore systems according to their effect on mission delivery, not simply according to which technical problem appears first.

2. Who Has the Authority to Make Decisions During a Disruption?

A crisis is a terrible time to figure out who is in charge.

Yet that is exactly what happens in many organizations.

One person calls the IT provider.

Someone else contacts the board.

Another person starts emailing employees.

A department head begins making decisions without knowing what leadership has already decided.

Meanwhile, everyone is asking the CEO or executive director what to do.

Your nonprofit should know in advance:

• Who activates the response plan?
• Who communicates with employees?
• Who communicates with the board?
• Who contacts donors, funders or community partners if necessary?
• Who works with IT and cybersecurity providers?
• Who makes decisions about program or service interruptions?
• Who determines when normal operations can safely resume?
• Who serves as the backup if the primary decision-maker is unavailable?

The goal is not to create more bureaucracy.

It is to eliminate hesitation.

When people know their responsibilities ahead of time, the organization can respond with greater confidence instead of waiting for someone else to make the first move.

For executive leadership, defined authority also reduces the risk of becoming the bottleneck for every decision.

It creates accountability while allowing the right people to act.

Preparedness takeaway: Every critical response responsibility should have a primary owner and a backup.

3. How Would We Communicate if Our Normal Tools Were Unavailable?

Email feels dependable until no one can access it.

Microsoft Teams or another collaboration platform works beautifully until it does not.

Your phone system may work every day for years until the day you desperately need it and discover that it relies on the same systems that just went offline.

Your leadership team should have a simple answer to this question:

“If our normal communication systems disappeared, how would we reach each other?”

Consider:

• Employees
• Board members
• Volunteers
• Vendors
• Community partners
• Donors
• Clients or the people you serve

Your backup plan does not need to be complicated.

It might include:

• An updated emergency contact list
• Personal phone numbers for key leaders
• An alternate messaging system
• A designated place employees can check for instructions
• Vendor escalation information stored outside the primary environment
• Clear responsibility for external communications

What matters is that people know where to turn.

During a disruption, silence creates uncertainty.

Clear communication creates confidence.

Leadership should also think about what happens if the issue is not the application itself, but the connection employees rely on to reach it.

A nonprofit may have functioning cloud applications, phones and collaboration tools while still being unable to use them if its primary connection fails. A properly designed backup internet strategy can reduce dependence on one circuit and provide another path to critical services when the primary provider is unavailable.

Preparedness takeaway: Your alternate communication method should be documented, accessible and understood before primary systems fail.

4. What Is the One Dependency That Could Hurt Our Mission the Most?

Every nonprofit has dependencies hiding in plain sight.

Of the five questions nonprofit leaders should ask about preparedness, this one can reveal some of the most consequential single points of failure.

It may be:

• One employee who understands an important process nobody else has documented
• One cloud application that stores essential information
• One internet connection supporting an entire office
• One outside vendor
• One donor or client database
• One fundraising platform
• One server
• One person who knows all the passwords

During a normal week, these arrangements may seem harmless.

During a disruption, they can become a serious problem.

Ask your leadership team:

“What do we depend on that would be difficult to replace tomorrow?”

Then look at what would happen if it disappeared.

Would programs stop?

Would fundraising slow down?

Would payroll be affected?

Would staff lose access to client information?

Would grant reporting become difficult?

Would donor data become inaccessible?

Would employees have a secure way to continue working?

Once you identify these dependencies, you can decide whether you need better documentation, redundancy, backup systems, additional training, stronger security or outside support.

The concern is not that every dependency will fail.

The concern is discovering too late that one dependency affects several parts of the mission at once.

Preparedness is not about assuming everything will break.

It is about making sure one failure does not take the mission down with it.

Preparedness takeaway: Identify dependencies by mission impact, then decide how your organization would continue operating without them.

5. If Something Happened Tomorrow, What Would We Wish We Had Done Today?

This may be the most important question of the meeting.

Imagine it is tomorrow morning and your organization has experienced a major outage, cyberattack or other disruption.

Staff cannot access an important system.

Programs are being affected.

Leadership is getting questions.

The board wants to understand what happened and what comes next.

Now ask:

“What would we wish we had prepared yesterday?”

Maybe you would wish you had:

• Tested your backups
• Updated your emergency contact list
• Documented a critical process
• Clarified who communicates with the board
• Reviewed employee access
• Confirmed that former employees no longer have access to systems
• Identified which applications should be restored first
• Documented critical vendors
• Tested alternate connectivity
• Verified that your recovery plan actually works

None of these tasks feels urgent on an ordinary Tuesday.

That is exactly why they get postponed.

But after a disruption, they suddenly become the things everyone wishes had already been done.

Preparedness gives your organization the ability to respond instead of react.

It also gives leadership something equally valuable:

Confidence that reasonable steps have been taken to protect the mission entrusted to the organization.

Preparedness takeaway: The work you would regret postponing during a service interruption is the work worth addressing before one occurs.

Preparedness Is About Protecting Mission Continuity

Nonprofit leaders rarely think about disaster recovery in isolation.

They think about whether programs can continue.

Whether staff can reach the information they need.

Whether donors and funders can trust the organization.

Whether sensitive information remains protected.

Whether the board can be confident leadership has acted responsibly.

Technology preparedness supports all of those outcomes.

Recent research also shows why that planning deserves attention. In the UK government’s Cyber Security Breaches Survey 2025/2026, only 20% of charities reported having a business continuity plan that covered cybersecurity.

A well-designed backup and disaster recovery strategy connects data protection with the operational realities behind recovery: which systems must come back first, how restoration is validated, which dependencies exist and what staff need to continue serving the mission.

That matters because recovery is not simply about having a copy of the data.

It is about restoring usable access to the systems, information and communications employees depend on.

Reliable systems, tested backups, resilient connectivity, clear recovery priorities and defined ownership help reduce the chance that one technical problem turns into a broader mission disruption.

The objective is not perfection.

No organization can eliminate every possible outage or incident.

The goal is to make the nonprofit harder to surprise and faster to recover.

Where the Right Technology Partner Fits

After working through these questions nonprofit leaders should ask about preparedness, you will probably notice something.

Some answers will come quickly.

Others will begin with:

“I think…”

“Someone probably has that…”

“Our IT company should know…”

or

“We haven’t tested that recently…”

Those are the answers worth paying attention to.

They are also the kinds of questions to ask your IT provider when determining whether your technology partner understands the operational, governance and mission consequences of downtime.

A provider of managed IT services can help turn those assumptions into clearer answers by identifying technology risks, validating backups and recovery processes, documenting critical systems, protecting sensitive information, coordinating vendors and helping align technology with operational and compliance responsibilities.

But the goal is not to bury leadership in technical language.

It is much simpler than that.

Technology should help protect the mission, not become another source of uncertainty for leadership.

For nonprofit executives, the business value is visibility.

You do not need to understand every technical configuration.

You do need confidence that the systems supporting programs, staff, donors and clients can recover when the organization has to rely on them.

Put This 15-Minute Preparedness Meeting on Your Calendar

Your nonprofit’s leadership team already carries a lot.

Fundraising.

Programs.

Staffing.

Budgets.

Compliance.

Board expectations.

Community needs.

Preparedness can easily fall to the bottom of the list because there is always something more urgent demanding attention.

Do not let it stay there.

Bring together leadership, operations and IT and work through these questions nonprofit leaders should ask about preparedness:

1. What must be restored first?
2. Who has authority during a disruption?
3. How will we communicate if normal systems are unavailable?
4. What is our biggest mission-critical dependency?
5. What would we wish we had prepared today?

If your leadership team can answer them clearly and those answers are supported by documented, tested processes, you have greater assurance that the organization can continue serving its mission when something unexpected happens.

If you discover gaps, that is valuable too.

You found them before a crisis found them for you.

Frequently Asked Questions About Nonprofit Preparedness

What should a nonprofit disaster recovery plan prioritize?

A nonprofit recovery plan should prioritize systems according to their effect on programs, client services, fundraising, financial operations, communications and sensitive information. Recovery order should reflect mission impact rather than technical complexity.

What is the difference between backups and disaster recovery for a nonprofit?

Backups preserve copies of data. Disaster recovery determines how applications, systems, connectivity and data will be restored so employees can continue serving the organization’s mission.

Why should nonprofit executives and board leaders care about IT preparedness?

Technology disruptions can affect programs, donor trust, compliance, finances and sensitive information. Executives need enough visibility to know that critical risks have been identified and that recovery responsibilities are clear.

What are common technology single points of failure for nonprofits?

Common dependencies include one internet connection, one critical cloud application, one donor database, one vendor, one server or one employee who holds undocumented knowledge about an essential process.

How often should nonprofits test backups and recovery processes?

Testing should occur regularly and whenever critical systems, vendors, staff responsibilities or workflows change. The purpose is to confirm that recovery works in practice rather than assuming successful backup jobs are sufficient.

Why is internet redundancy important for nonprofits?

Nonprofits increasingly rely on cloud applications, Microsoft 365, donor platforms, communications and remote access. A backup connection can reduce the chance that one provider outage cuts staff off from multiple mission-critical systems at once.

How can an IT provider help improve nonprofit preparedness?

An IT provider can identify dependencies, document systems, test backups, strengthen security, coordinate vendors and align technology recovery priorities with programs, staff needs, compliance responsibilities and mission continuity.

Turn Preparedness Into a Defensible Recovery Plan

Nonprofit leadership should not have to discover its recovery strategy while staff, clients, donors or board members are already waiting for answers.

7tech helps nonprofit organizations identify where technology could disrupt the mission, validate backup and recovery processes and create greater visibility into the systems, people and information the organization depends on.

Start with the five questions nonprofit leaders should ask about preparedness above. Then determine whether your answers are documented, tested and strong enough to hold up when your nonprofit actually has to rely on them.

Not sure how prepared your nonprofit really is? Start a conversation with 7tech to identify technology and recovery gaps before they become larger operational problems.

Call (844) 701-6777 or visit 7tech.com.