
A disaster recovery plan (DRP) is an operational document that describes how to bring your critical applications and data back into service after a major outage: hardware failure, cyberattack, an incident on your premises or human error. It sets out the order in which to restart, who steps in and how to check that everything works. This guide is for owners and managers of small businesses and SMEs who want to prepare a realistic plan, even without a dedicated IT team.
Understanding the disaster recovery plan
The DRP comes into play after the incident. It does not replace your backups: it organises how they are used. Our guide to business data backup describes the backup strategy upstream; the recovery plan describes what you do with those copies on the day you need to restart.
- It limits how long your operations are interrupted.
- It reduces the risk of data loss.
- It gives teams a clear course of action that can be followed under pressure.
- It makes it easier to talk to your customers, partners and service providers after an incident.
A small organisation can start with a short plan, focused on a few critical functions and realistic procedures.
DRP and BCP: disaster recovery or business continuity?
The two concepts are often confused, even though they cover two different moments.
- The business continuity plan (BCP) aims to keep vital functions running during the crisis, possibly in degraded mode, using fallback solutions or manual procedures.
- The disaster recovery plan (DRP) accepts a temporary interruption and describes how to restore systems, applications and data once the incident is under control.
Take invoicing software that has become inaccessible. The BCP provides a temporary procedure so that invoices can still be issued. The DRP details how to restore the software, recover the data and return to normal operation. A small business or SME can start with a well-structured recovery plan, then consider continuity for its most sensitive functions.

Why a small business or SME needs a recovery plan
Online tools, email, management software, remote working: day-to-day business depends on the information system. Without a recovery plan, an outage quickly turns into blocked orders, invoicing that cannot be done, delayed projects and a loss of customer confidence.
Depending on your sector and your contracts, specific recovery requirements may apply; check them with your advisers and your principal clients. Beyond these obligations, formalising recovery remains useful: it is the last safety net when prevention is no longer enough. The plan therefore complements the measures described in our guide to cybersecurity for SMEs, presented further down.
Taking stock of critical applications and data
Before describing the "how", you need to clarify the "what".
- List the assets: business applications (ERP, CRM), email, website, online shop, databases, shared files, office tools.
- Rank by criticality: critical (invoicing, customer follow-up, order taking), important (reporting, internal communication), secondary (archives, old projects).
- Identify the dependencies: some applications will not restart until the database, the network or authentication are available.
- Locate the data: local server, hosting provider, online service, workstations. If some of your tools have been moved to a hosting provider, as explained in our guide to cloud migration for SMEs, specify what is your responsibility and what is the provider's.
Setting recovery priorities and objectives
Two questions guide prioritisation, application by application.
- How long can the business withstand the outage? This is the recovery time objective, also called the maximum tolerable downtime.
- How much recent data can you accept losing? This is the recovery point objective, also called the maximum tolerable data loss. It determines how often backups are made.
An invoicing or order-taking tool generally calls for fast recovery and very little data loss. Archives or old files can tolerate a longer delay. These objectives are not universal values: they are decided with the business managers, who are best placed to gauge the effect of an outage, and they then steer backup and hosting choices.
Recovery priorities table
The heart of the plan often fits in a table that can be read at a glance. The levels below are examples to adapt to your business.
| Business process | Application or system | Priority | Owner | Main steps |
|---|---|---|---|---|
| Invoicing | Management or accounting software | High | Management and IT lead | Restore the database, check data integrity, restart the service. |
| Customer relations | CRM, order taking | High | Sales manager | Check access, restore the data, test a complete journey. |
| Communication | High | IT lead | Re-establish access, check synchronisation, inform the teams. | |
| Online presence | Website | Medium | Marketing manager | Restore the latest backup, test the display and the forms. |
| Collaborative work | Shared files | Medium | IT lead | Restore the folders, check access rights. |
Keep this table offline, in printed form or as a local copy, so that it can still be consulted if the servers are unavailable.
Putting the plan in place, step by step
- Analyse the risks: hardware failure, cyberattack, human error, an incident on your premises.
- Take stock of and prioritise applications and data, as described above.
- Define the recovery scenarios: restoring from a backup, restarting on other equipment, temporarily falling back on a standby service.
- Write the procedures: short sentences, actions in order, screenshots where needed. Each document must remain understandable in a stressful situation.
- Check the backups: they must cover the priority systems and exist as several copies on different media, including one off site.
- Test the procedures, then fix whatever got stuck.
- Update the plan after every change to the information system.
Roles, responsibilities and crisis communication
A recovery plan is not just a technical matter: it organises responsibilities.
- Decision maker (management): triggers the plan and signs off on the trade-offs.
- IT lead (in-house or service provider): carries out the technical procedures and coordinates the restoration.
- Business contact for each department: reports priorities on the ground and checks that everything works properly after recovery.
Specify who communicates internally, who informs customers and partners, and who coordinates with the service provider. Keep essential contacts and administration access available even if the main email system is down. Prepare simple messages, focused on what is being done to restore the service.
Tests, exercises and updating the plan
A plan that has never been tested remains theoretical. Schedule regular exercises, at a pace suited to your business.
- Tabletop review: reading through a scenario in a meeting, checking roles and procedures.
- Partial restoration test: restore an important application, note the time it takes and check data integrity.
- Full exercise: simulate the unavailability of a server or a business tool and run through the whole plan.
Document each test: what worked, what got stuck, the improvements to make. Update the plan with every significant change: a new application, a change of hosting, the opening of a site, the arrival or departure of a manager.
Common mistakes to avoid
- Settling for backups without a documented and tested restoration procedure.
- Focusing on the technical side while forgetting business processes and communication.
- Never testing the plan, or only on secondary items.
- Writing a plan that is too complex for the size of the company.
- Forgetting online services: administration accounts, authentication, password management.
- Keeping the plan only on the server that may be affected by the incident.
- Neglecting the cyberattack scenario; our guide to cybersecurity for SMEs presents the preventive measures that complement the recovery plan.
Checklist for building or reviewing your recovery plan
- The list of critical applications and data is up to date.
- Each application has a recovery order and a realistic time objective.
- The backups cover all the critical systems identified.
- The full restoration of a major application has already been tested.
- Crisis roles are assigned and known to everyone.
- The plan remains accessible if the main servers are unavailable.
- A cyberattack scenario is provided for: isolating the affected workstations, restoring onto a clean environment.
- The IT service provider knows where to find the plan and how to apply it.
- An exercise is scheduled and the results of the previous one are documented.
- The plan was updated after the latest change to the information system.
Frequently asked questions about the disaster recovery plan
Does a small business really need a DRP?
Yes. Size protects against neither outages, nor cyberattacks, nor incidents on the premises. A simple plan that can evolve is already real progress compared with having no plan.
What is the difference between a backup and a recovery plan?
The backup is one element of the plan, not a substitute. The plan organises the whole: in what order to restore, who steps in, how to check the data and how to communicate.
How often should the plan be tested?
There is no universal pace. Schedule regular exercises, supplemented by partial restorations of critical applications, and run a test again after every significant change.
Who should lead the recovery plan in a small business or SME?
Management, supported by an in-house or external IT lead. You need someone who knows the business priorities and has the authority to trigger the plan.
Preparing your recovery plan with UnzipTech
A disaster recovery plan rests on a rigorous inventory, clear priorities, defined responsibilities, reliable backups and regular tests. It extends the company's good backup and cybersecurity practices.
UnzipTech, an IT consulting and development company based in Fez, designs custom software, websites and mobile applications, and supports businesses with IT and digital consulting. Our projects include a free personalised quote, training and documentation on delivery, as well as maintenance contracts. Discover our services or contact us to discuss your recovery plan.
