At 11am on 11 November, people across the UK pause for two minutes to remember those who have served and sacrificed. It is a fixed moment in the calendar, observed with care and respect.
That act of remembrance is not a productivity technique, and an IT review is no comparison to it. But there is a useful discipline in the idea of a scheduled pause: choosing a date in advance, stopping to reflect, and making space to consider what should not be forgotten.
Many UK businesses have no equivalent point in their IT year. Systems keep running, renewals pass and incidents are resolved as they arise. Then an outage, a failed recovery or an unexpected invoice forces attention at the worst possible time.
A fixed annual review gives owners and finance directors a chance to ask, before the next disruption: what happened, what did it reveal, and what needs to change?
Remember the incidents, not just the tickets
Closing a helpdesk ticket is not the same as learning from an incident. A recurring login problem, a delayed restore or a supplier failure may each have been resolved, but the underlying cause can remain.
Set aside time each year to review significant incidents and recurring support patterns. Ask:
- Which business processes were interrupted, and for how long?
- Did the response depend on one person or supplier?
- Was the cause technical, procedural or unclear ownership?
- Did the incident expose an unsupported system, weak integration or missing documentation?
- What action would reduce the chance or impact of a repeat?
The point is not to produce a long list of faults. It is to connect operational experience to business risk and investment priorities. A Fractal IT Director can help turn those findings into a practical roadmap, with owners, costs and decisions rather than an ever-growing queue of tickets.
Put Disaster Recovery on the calendar
Disaster Recovery should be reviewed on a planned date, not first discussed after a system goes down. A backup report marked “successful” does not, on its own, prove that the business can restore its data and resume work.
At the annual review, confirm that backups are completing, protected and usable. Test a restoration, and check that the plan reflects the systems, suppliers and dependencies the business has today. Identity services, applications, integrations and access to cloud platforms may all matter to recovery.
Agree recovery objectives in business language:
- Recovery Time Objective (RTO): how long the business can accept a service being unavailable.
- Recovery Point Objective (RPO): how much recent data the business can afford to lose, measured in time.
These should reflect the impact on trading, customers and essential operations, not simply the capabilities of a backup product. Rehearse the plan, record what the test demonstrated, and update it after significant changes. The NCSC’s small business response and recovery guidance offers practical advice for preparing to recover from an incident.

Decide on the core systems before the year-end freeze
The annual review is also a useful decision point for finance and ERP platforms. If an ageing on-premise system is still carrying core processes, ask whether it remains fit for purpose, or whether it is simply surviving because nobody has scheduled a decision.
For some businesses, Microsoft Dynamics 365 Business Central may provide a supported, documented, cloud-hosted core for finance and operations. That is a strategic choice, not an automatic answer. The review should establish the business requirements, data and integration needs, implementation capacity, security responsibilities and total cost before a decision is made.
A Dynamics 365 Jump Start can help assess readiness and clarify the route forward. Starting that discussion before the year-end change freeze gives decision-makers room to plan, rather than rushing a major change into a narrow window, or carrying an ageing platform into another year by default.
Microsoft’s Business Central cloud migration guidance is a useful reference for the questions involved in moving from on-premise systems. The review should also identify who will own ongoing governance after implementation. Cloud hosting changes the operating model; it does not remove the need to manage it.
Ask who knows the legacy system
Legacy systems can be business-critical while remaining poorly documented. For an IBM i (AS/400) estate, an annual review should ask a deceptively simple question: who actually knows how this machine and its applications work?
Identify which people understand the jobs, interfaces, recovery steps and specialist access. Then consider what happens if they are unavailable, leave or retire. If knowledge is concentrated in one person, the risk is not theoretical; it is an operational dependency that needs a plan.
IBM i Management can provide specialist support for assessing and managing these environments. The review should establish whether to retain, improve, modernise or replace each workload, based on business value and risk, not on fashion or a presumption that old means useless.
David Evestaff’s experience in IBM i system administration, multinational onboarding and Google-certified IT project management informs a practitioner-led consultancy approach: understand how the business actually operates before recommending change.
Audit what the business actually pays for
Technology Expense Management (TEM) is more than a budget check. It is the annual reconciliation of what the business uses, what it is contracted to buy and what it is actually paying.
Review software licences, subscriptions, cloud consumption, connectivity, support contracts and supplier invoices. Look for unused accounts, duplicated services, overlapping suppliers, changed rates and automatic renewals that passed without an active decision. For each material cost, confirm a business owner, purpose and renewal date.
A Technology Expense Management review can help make those costs visible and identify where spend no longer supports the operating plan. The objective is not to cut indiscriminately. It is to protect return on investment by directing spend towards services the business needs and removing waste where it does not.

Treat assurance as a year-round record
ISO 27001 and Cyber Essentials are useful consultancy domains, but neither should be treated as a certificate to file away and forget. Make the annual review part of a continuing cycle of risk assessment, evidence and improvement.
Confirm the scope, asset register, security responsibilities, continuity arrangements and open corrective actions. Check certificate expiry dates and the timing of relevant surveillance or recertification activity. Keep records current enough to support an assessor’s questions, rather than reconstructing a year’s decisions at short notice.
Cyber Essentials and ISO 27001 are distinct schemes. Review the relevant requirements and evidence for each, and do not assume that maintaining one automatically fulfils the other. The NCSC’s Cyber Essentials overview explains the scheme and its core technical controls.
Make the review an investment decision
A useful annual pause should end with decisions, not just observations. Agree a short, prioritised plan: what needs attention, who owns it, when it is due, what it will cost and which risks the business is choosing to accept.
Some actions may require strategic consultancy; others may be execution work. Managed IT Services, Helpdesk Support, Network Solutions, Voice and Connectivity and hardware or software licences can support the agreed direction as bolt-on services. They should not substitute for deciding what the business needs in the first place. A trusted network of specialist partners can provide technical depth where required, with consultancy retaining oversight of priorities and outcomes.
The annual date matters because it creates a reliable moment to look beyond the next ticket or renewal. Put it in the diary before the year begins. Then use it to remember what went wrong, verify that recovery still works, challenge silent costs and make deliberate decisions about the systems the business depends on.
For IT strategy and consultancy, visit itandconsultancy.co.uk. For 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, UK SME IT consultancy, business continuity, Microsoft Dynamics 365 Business Central, IT estate review, ISO 27001 consultancy, Cyber Essentials
Join The Discussion