When a shared drive, internet connection, payment system, phone line, or cloud app stops working, the issue is not only technical. Staff still need direction. Clients, donors, customers, or partners may still be waiting. Someone has to decide what matters first.
For small teams, that responsibility often falls to whoever is available. That can work for a small hiccup, but not when the disruption affects payroll, appointments, service delivery, donations, invoices, or internal communication.
A simple IT response plan helps your team make the first few decisions before things feel urgent. It does not need to cover every possible problem. It just needs to answer four questions: who leads, what gets restored first, what the team can do temporarily, and where to get help.
Start With the Work
A list of software and devices is helpful, but it will not tell you what matters most in the moment. Start with the work your team needs to keep moving.
For some organizations, email is the priority. For others, it may be a scheduling tool, donor or customer database, accounting system, shared folder, payment page, or phone system. The priority depends on what stops when that system is unavailable.
For each essential system, write down what it supports, how long your team can work without it, and whether there is a safe temporary option. This gives your IT partner a clear recovery order based on how your organization actually operates.
Name the Person Who Leads
When no one is clearly responsible, people often try to help in different directions. One person contacts support. Another messages a vendor. Someone else starts giving staff instructions without the full picture.
Your plan should name one person who coordinates the response and one backup person if they are away. They do not need to fix the issue. Their job is to gather basic facts, contact the right support team, share updates, and make sure urgent decisions reach the right person.
Keep support details, vendor contacts, account information, and approval names somewhere the team can reach even if your usual systems are down.
Decide What Happens While You Wait
Good support matters, but not every issue can be fixed right away. Your team should know what it can safely do while the main system is being restored.
That might mean using mobile internet, redirecting calls, recording appointments manually, working from approved offline files, or switching to a communication channel everyone can still access.
Keep the temporary process simple. If it depends on equipment no one can find or a login no one remembers, it will not help much during a busy morning.
Check What Your Backups Cover
Many organizations know they have backups, but not exactly what is included. That gap matters when important information lives across shared drives, email, staff devices, cloud apps, and third-party platforms.
Ask your IT partner what is protected, how often backups run, how long information is kept, and how long a typical restore would take.
A backup test can be small. Restoring one file, folder, mailbox, or record can confirm the process works and reveal anything that has been missed.
Keep Communication Clear
During a disruption, most people do not need a technical explanation. They need to know what is unavailable, how it affects their work, what to do instead, and when they will get another update.
Choose one person to share updates through a channel the team can still access. This is especially important when staff, volunteers, contractors, or board members work from different locations.
Clear updates also reduce repeated support requests, mixed instructions, and people trying fixes that may create more problems.
Review the Plan When Things Change
Your plan should be reviewed when your organization changes systems, adds a new location, switches providers, moves more work to the cloud, or changes key staff responsibilities.
The review can be simple. Pick one likely scenario, such as losing access to the shared drive at the start of the day, and walk through what would happen. Who contacts support? What work comes first? What temporary process would the team use? How would updates be shared?
Any question your team cannot answer shows you where the plan needs attention.
Make the First Steps Clear
A useful IT response plan does not need to be long. It needs to reflect the systems your team depends on, the people who rely on you, and the way decisions are made in your organization.
When the first steps are clear, your team can spend less time sorting out the response and more time keeping essential work moving. Your IT partner also gets better information from the start, which helps them focus on restoring what matters most.
If your current process mostly lives in people’s heads, we can help you turn it into a simple response plan your team can actually use. The Human IT Company will walk through your key systems with you, clarify the first steps, and help your team feel more prepared when technology gets messy.
