When is a continuity plan needed?
Problems we help solve
During a failure, there is no time to determine which system is most important, who makes decisions and where access is. A business continuity plan organises these decisions earlier, before time pressures arise.
- It is unclear which systems need to be restored first.
- Backup exists, but there is no set return-to-work time.
- There is a lack of contacts to suppliers, administrators and decision-makers.
- The company does not have a work scenario when the Internet, server or application is unavailable.
- After a failure, decisions are made chaotically and without documentation.
Fit
Who is this service for?
Companies with critical systems
We determine the order of restoring ERP, email, files, databases and industry systems.
Companies after failure
We help turn the incident experience into specific procedures and corrections.
Companies before the audit
We prepare a description of business continuity, backup, liability and tests.
Companies with multiple suppliers
We organise contacts, areas of responsibility and the order of escalation.
Service scope
What does a business continuity plan cover?
Business priorities
We determine which processes and systems need to return the fastest.
- list of critical systems,
- minimum scope of work,
- required RTO and RPO times.
Failure scenarios
We describe possible situations and the first steps.
- internet loss,
- server or application failure,
- ransomware and data loss.
Roles and escalation
We organise responsibility on the part of the company and suppliers.
- decision-makers,
- emergency contacts,
- communication order.
Testing and updating
We check whether the plan is feasible.
- selected data recovery test,
- review of procedures,
- update after changes.
Outcomes
What will you receive?
- a list of critical systems and expected recovery times,
- operating procedures for the most important failure scenarios,
- established roles, contacts and escalation rules,
- recommendations regarding backup, redundancy and suppliers,
- documentation that can be updated as the company changes.
The plan does not have to be an extensive corporate document. For many companies, the most important thing is practical instructions that can be used in stressful situations.
Delivery approach
How is the service delivered?
- Discovery. We determine processes, systems and the consequences of their unavailability.
- Priorities. We determine the order of recovery and the minimum scope of work.
- Dependencies. We check backup, internet, suppliers, accounts and infrastructure.
- Procedures. We describe scenarios, roles and first actions.
- Test. We verify a selected element of the plan, for example data restoration.
- Update. We determine when the plan needs to be reviewed again.
Delivery standards
How do we create a plan?
- We describe procedures in simple language so that they work under time pressure.
- We do not assume that all systems are equally important.
- We combine the plan with real backup and recovery tests.
- We include decision-makers, not just technical administrators.
- We leave a document that can be maintained and updated.
Cost
What determines the price?
The price depends on the number of systems, locations, suppliers, level of detail required, recovery tests, backup analysis and the number of emergency scenarios.
FAQ
Frequently asked questions
Is a business continuity plan the same as a backup?
No. Backup is one of the elements of the plan, but priorities, roles, procedures and tests are also needed.
Does a small business need such a plan?
Yes, although usually in a simpler form. Even a short manual helps avoid chaos after a failure.
Are tests necessary?
It is worth doing them, because without a test it is difficult to assess whether the plan and copies will work in practice.
Does the plan cover external suppliers?
Yes. Contacts, responsibilities and escalation of suppliers are an important part of the document.
How often should you update your plan?
Following major changes to systems, suppliers, locations or responsibility structure.