By mid-November, many UK businesses are looking at the festive leave calendar and trying to make sure essential work is covered. It is also an opportunity to ask a more revealing question: what can only one person do, explain or approve?
Most SMEs discover their key-person IT dependencies by accident, when leave is already approved and a routine task suddenly has no obvious owner. The annual-leave approval queue can be the cheapest, most honest audit of the IT estate a business ever runs. It shows where knowledge sits, where access is concentrated and whether continuity plans work without the usual people in the room.
This is not an argument for cancelling holidays. It is a prompt to build an organisation that can operate when people are away, as they are entitled to be.
Treat the leave calendar as a diagnostic
Start with the weeks when several people are away, then map the work that must continue. For each critical task, ask:
- Who owns it, and who is the trained deputy?
- What system, data, supplier or approval does it depend on?
- Is there a current runbook, and can the deputy access it?
- What decisions can the deputy make without waiting for the usual owner?
- What happens if the primary contact is unreachable?
Include routine but consequential work: payroll inputs, payment approvals, month-end close, order processing, user access changes, backups and supplier escalations. The revealing question is not simply “who is covering?” It is “could that person complete the task with the information and authority available to them?”
Record the answer in a dependency register, with a named owner and deputy, relevant systems, supplier contacts and links to current procedures. Check that access is delegated properly through named accounts and approved controls, not by sharing passwords. Where cover is thin, arrange cross-training or specialist support before the gap becomes urgent.

Disaster Recovery must work with the people who are present
A backup is valuable only if the business can restore what it needs, within an acceptable time, using people who are available. That makes annual leave a useful test scenario for Disaster Recovery planning.
For each important system, agree recovery objectives in business language:
- Recovery Time Objective (RTO): how long the business can manage without the service.
- Recovery Point Objective (RPO): how much recent data the business can afford to lose.
These are business requirements, not settings to accept by default from a backup product or cloud provider. A finance system, for example, may have different recovery needs from an archive. The right objectives depend on the effect of disruption on customers, cash flow, compliance and operations.
Then test the practical question: could recovery actually be executed by the people in the office that week? Verify that backups are accessible and restorable, that the recovery sequence is documented, and that the people covering understand who can authorise actions and where to escalate. A completed backup job is not proof that the service can be recovered.
The NCSC’s small business guidance on response and recovery encourages preparation, clear responsibilities and testing. A tabletop exercise during a quieter period can expose a missing account, outdated supplier contact or undocumented dependency before it becomes a live incident.

Make the core finance system survivable without its expert
A finance or ERP platform should not depend on one employee remembering undocumented steps to complete month-end. Yet in some businesses, a critical process rests on a personal spreadsheet of workarounds, a set of local files or knowledge that has never been transferred.
For an organisation considering change, Microsoft Dynamics 365 Business Central can provide a supported, cloud-hosted core finance and ERP system. The strategic question is not simply whether a new platform is available; it is whether processes, data, responsibilities and recovery arrangements are designed so the business can operate without a single individual.
A structured Dynamics 365 Jump Start can help assess process fit, data quality, roles, approvals, integrations and implementation risks before a larger commitment. A successful outcome should include usable documentation and runbooks, defined ownership and an operating model that makes routine work understandable to trained colleagues. Vendor support can help, but it does not replace internal accountability or a tested handover.
The contrast is an ageing on-premise system where month-end depends on one person’s spreadsheet of workarounds. That is not necessarily a reason to replace the system immediately. It is a reason to document how it works, assess the risk and agree a practical roadmap.
Give legacy platforms proper cover
Some businesses depend on established IBM i (AS/400) environments for finance, distribution or other operational processes. When the person who knows the machine books the same fortnight off every December, the answer is not to hope nothing happens.
IBM i Management can provide specialist oversight for these estates, including system knowledge, operational procedures, supplier coordination and recovery planning. A review should identify which workloads are critical, who can perform essential tasks, how backups are restored and what cover is available if the usual administrator is away.
Legacy does not mean unimportant. Nor does it mean the platform must be replaced on an arbitrary timetable. It means its risks, costs and support requirements need informed attention, and continuity must not be held in one person’s head.
Use the leave audit to find hidden technology costs
Absence can also reveal who understands the business’s subscriptions and renewals. Is there one person who knows which licences are still needed, which supplier contracts renew automatically, or why an old service is still being paid for?
A Technology Expense Management review can bring those details into view. Reconcile invoices and contracts with actual users, service owners, business purpose and renewal dates. Record who can approve a change and what the operational effect would be if a service were cancelled.
The aim is not indiscriminate cost-cutting. It is to remove avoidable waste where appropriate and understand whether identified savings can fund better documentation, cross-training or specialist cover. A renewal calendar and a clear owner for each subscription turn private knowledge into a managed process.

Turn the findings into evidence, not a paper exercise
ISO 27001 and Cyber Essentials are useful guided consultancy domains for examining how an organisation manages information security and technology risk. They should not be treated as guarantees of continuity, or as paperwork detached from daily operations.
A well-maintained asset register, documented responsibilities, supplier contacts, current procedures and cross-training can help show how the business manages its systems when key people are unavailable. The ISO overview of ISO/IEC 27001 describes the information security management standard; the NCSC’s Cyber Essentials guidance explains the scheme’s baseline approach to common cyber risks. Specific evidence depends on the organisation, its scope and the requirements being assessed.
Start with a short action list based on the leave calendar:
- Identify critical tasks that rely on a single person.
- Name and prepare a deputy for each high-priority task.
- Check that instructions, access and supplier contacts are current.
- Agree business-led RTOs and RPOs for essential services.
- Schedule a recovery exercise that includes staff absence.
- Review licences, subscriptions and upcoming auto-renewals.
Strategic oversight should come first; operational services should support it. A Fractal IT Director can help turn these findings into a prioritised plan, while Managed IT Services, Helpdesk Support, Cloud Solutions, Network Solutions and Voice and Connectivity can be added as execution services where they fit the strategy. A trusted network of specialist partners can provide technical depth without confusing support delivery with strategic ownership.
The leave calendar cannot tell you everything about your IT estate. But it can show where resilience depends on a person being present, and that is a sensible place to begin. For an overview of the wider Evestaff group, visit evestaff.co.uk.
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, key-person risk, business continuity, UK SME IT consultancy, annual leave planning, ISO 27001, Cyber Essentials
Join The Discussion