The Office Is Empty but the Systems Are Not: Disaster Recovery for the Hybrid Workforce

  • 1 week ago
  • 0

It is Saturday morning. The office is locked, but orders are being processed, invoices are due and staff are checking in from home. Then the finance system becomes unavailable.

For many UK SMEs, disaster recovery (DR) plans still assume that people, equipment and decision-makers are together in the office. Hybrid working has changed that. When a disruption happens, the team may be spread across kitchen tables, spare rooms and mobile connections. Recovery must work there too.

The question is no longer only, “Can we restore the server?” It is, “Can the people who need to work reach the systems and information they need, securely, from wherever they are?”

Build recovery around the work, not the building

Business continuity is about keeping essential activities running at an acceptable level during disruption. Disaster recovery focuses on restoring the technology and data those activities depend on. A plan that considers servers but not staff access, communications and decision-making covers only part of the problem.

Start by identifying the services your business must keep running: perhaps finance, order processing, customer communications or a specialist operational system. For each, map the people, applications, data, suppliers and connections it relies on. Then ask what happens if the office network is unavailable, or if employees cannot connect from home.

This is not a theoretical exercise. The National Cyber Security Centre’s small business guidance recommends identifying critical information and systems, making regular backup copies, testing that they can be restored, and assigning shared responsibility so recovery does not depend on one person.

Abstract layered data vault forms linked to a stable central core, representing secure backup and recovery

Agree recovery targets in business language

Two measures help turn a general promise of “getting back online quickly” into an operational plan:

  • Recovery Time Objective (RTO): how long the business can tolerate a service being unavailable.
  • Recovery Point Objective (RPO): how much recent data the business can afford to lose, measured as time.

These are not technical targets to choose in isolation. A finance director and service owner should agree what disruption means in practice: missed payments, delayed orders, lost productivity or a risk to customer commitments. The acceptable downtime for a historical reporting tool may be very different from that for a system processing orders.

For each important service, record the agreed RTO and RPO, its dependencies and a workable alternative if it cannot be restored immediately. A manual process might keep a limited activity moving, but only if staff know when to use it, what to record and how to reconcile it afterwards.

Finally, check that your backup arrangements and suppliers can meet the targets. A recovery objective is a business requirement; it is not proof that recovery will happen within that time.

Test backups from a home-working scenario

A backup is useful only if it can be restored in a way that lets people resume work. Test more than files: consider applications, user accounts, permissions, configurations and the connections between systems. Confirm who can authorise recovery and who has the knowledge to carry it out if the usual system administrator is unavailable.

Rehearsals should reflect the working week your team actually has. Run through a scenario where the office cannot be entered, a key person is away and staff are relying on home broadband or mobile data. Can everyone find the instructions and contact details? Can decision-makers communicate if the usual email or collaboration platform is down? Is there a safe, clear process for staff to follow?

A test that reveals a gap is doing its job. Record what happened, compare actual recovery with the agreed RTO and RPO, and assign owners to corrective actions. Repeat the exercise after significant changes to systems, suppliers or working arrangements.

Treat remote access as a continuity dependency

A working system is not available to the business if staff cannot reach it. Remote-access failures (such as a VPN outage, identity-provider issue, locked account or unavailable authentication device) can therefore become continuity incidents in their own right.

Review how employees securely connect to essential services and what happens when the primary route fails. Confirm that access controls, authentication and device security are appropriate for the systems and data involved. Make sure remote access has been tested under realistic conditions, including the number of people likely to need it at once.

The same review should cover the practicalities: spare or replacement devices, access to current recovery instructions and a reliable way to contact staff. Do not assume everyone can retrieve a plan stored in the system that has just failed.

Voice and Connectivity: the second pillar

Hybrid recovery depends on connectivity as well as computing. Home broadband quality varies, mobile coverage is not uniform, and an office-based DR plan may assume that staff can simply return to their desks.

Check whether critical remote workers have suitable connectivity and define what happens if their broadband fails. Mobile data can be a useful fallback where coverage, device compatibility, security and cost have been considered. It is not a universal substitute, so test it rather than relying on a hopeful signal bar.

Voice systems also need to follow the user, not the desk. Review whether business calls can be answered through an approved alternative when an office phone or local network is unavailable. Set out how customers and suppliers will reach the organisation during an incident and who is responsible for updating them.

These decisions belong in your Network Solutions strategy. Any voice, connectivity or network support should be an execution layer for that strategy, not a substitute for deciding which services matter and what resilience they require.

A mobile handset and wireless access point on a home desk, illustrating resilient voice and connectivity

Choose core systems with recovery in mind

A cloud-hosted finance and ERP platform can help staff work from different locations, provided the service, user access, devices and internet connection are available and supported. For a suitable organisation, Microsoft Dynamics 365 Business Central may offer a more accessible core than an ageing on-premise server that depends on the office network. Cloud hosting does not remove continuity planning: businesses still need to understand provider recovery arrangements, data protection, identity dependencies and their own responsibilities.

A Dynamics 365 Jump Start is a strategy-led way to assess Business Central against finance and operational needs before committing to a wider implementation. The work should clarify processes, integrations, data quality, user roles and recovery requirements, not simply configure software. Explore the Dynamics 365 Jump Start and Business Central consultancy context and Microsoft’s Business Central overview.

An abstract cloud-like glass form above a dark desk, representing a cloud finance platform and business continuity

For organisations that rely on IBM i Management, remote access and recovery deserve particular attention. Established systems can be vital to day-to-day operations, while access may depend on specialist configurations or the knowledge of a small number of people. Document the dependencies, recovery process and accountable contacts, and test how authorised staff will reach the environment when the office is unavailable. Managed cover can support that plan; it should be based on a clear understanding of the business’s requirements.

Use Technology Expense Management to find hidden costs

Hybrid working can reveal technology expenditure that has accumulated without a joined-up review: home-worker connectivity allowances, unused mobile services, duplicated VPN or remote-access tools, and licences that no longer match how people work.

A Technology Expense Management review can bring these costs into view by comparing invoices, contracts and licences with actual use and business need. The aim is not to cut essential resilience. It is to identify unnecessary duplication and redirect justified savings towards controls, connectivity or recovery capabilities that support agreed business priorities.

This is particularly useful when reviewing who pays for home connectivity, what happens when a device is replaced and whether staff have more than one tool performing the same function. Managed IT Services and Helpdesk Support can then provide practical support for the arrangements the strategy has approved.

Make security evidence part of the plan

Home working extends the security perimeter beyond the office. Cyber Essentials and ISO 27001 can provide useful consultancy frameworks for reviewing how the organisation manages that risk. The right scope and controls depend on your systems, information and operating model.

Assessors will expect a clear account of relevant remote-access controls, device management, patching and staff responsibilities. Where home-working devices fall within scope, the organisation should understand how their security is managed. Policies should also explain secure working practices, incident reporting and what employees should do if equipment is lost or access appears compromised. See the NCSC’s Cyber Essentials guidance and the ISO guide for SMEs.

An abstract glass perimeter around a laptop and geometric shield form, representing remote-work security

Make the plan fit the way your business works

A useful hybrid DR plan does not begin with a product list. It begins with business priorities, agreed recovery targets and a realistic picture of how people work outside the office. Particularly at weekends, when key staff or suppliers may not be immediately available.

A Fractal IT Director approach brings those elements together: strategy first, then the infrastructure and specialist execution needed to deliver it. Start by testing one essential service from a home-working scenario. Find out what fails, what staff need and whether your recovery target is achievable. Then improve the plan before the next disruption writes it for you.

For a wider view of Evestaff’s group of services, visit the Evestaff gateway.

SEO tags: Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, hybrid working, business continuity, remote access, UK SME IT consultancy, ISO 27001, Cyber Essentials

Join The Discussion