January often feels like the natural time to make a fresh start. For significant IT change, however, it can be late.
Many finance teams and IT estates operate a change freeze from mid-December into early January. Year-end close, locked accounting periods, audit work and reduced staffing make major system changes harder to govern and test. The dates vary by organisation, but the planning consequence is familiar: work not decided and scheduled in November may have to wait until mid-January.
That leaves a period when important systems are carrying the business through busy weeks, often with less cover available. A freeze can reduce the risk of disruption caused by planned changes. It cannot prevent failures, cyber incidents or supplier problems.
The useful question is not simply, “What can we postpone?” It is, “What must be assessed, tested or agreed before the freeze begins?”
Set the decision deadline before the technical deadline
A meaningful change needs more than an engineer’s diary slot. It needs business ownership, a defined scope, time for testing, a rollback or contingency plan, and people available to approve decisions. For a finance system or a critical network change, those requirements are difficult to assemble at short notice.
November is the time to review the change register and separate work into three groups:
- Essential before the freeze: resilience checks, renewal decisions and changes required to address material risk.
- Approved and scheduled: work with a clear business case, accountable owner and adequate testing time.
- Deferred deliberately: changes that can safely wait, with an agreed date and interim controls.
This is where a consultancy-first approach matters. The Fractal IT Director view is to assess how technology, people, suppliers and business processes fit together before deciding which technical tasks to execute. Helpdesk Support and other Managed IT Services can provide valuable bolt-on delivery and monitoring, but they should support a business-led IT strategy, not substitute for one.
Disaster Recovery: prove the route back before people leave
A successful backup report is useful evidence. It is not proof that the business can recover the services it needs, within an acceptable time, with the people available over the holiday period.
Before the freeze, identify the systems that underpin finance, payroll, orders, stock, customer service and communications. Confirm dependencies, service owners and the sequence in which systems must be restored. Then review backup coverage, test representative restores and record what the tests actually show.
Agree recovery time objectives (RTOs) and recovery point objectives (RPOs) in business language. For example: how long can finance processing be unavailable, and how much recently entered information could the organisation afford to re-enter? The right answers depend on the business; they should be agreed with the people accountable for operations, not assumed by an IT supplier.
A recovery plan also needs to work when the usual system administrator is on leave. Rehearse who can declare an incident, authorise recovery, contact suppliers and make operational decisions. The National Cyber Security Centre’s small business guidance on preparing for incidents recommends preparing roles and exercising response plans. Its advice on offline backups is also relevant when considering how to protect recovery copies.
A change freeze is not a freeze on failures. Monitoring, escalation routes and access to recovery support should remain active throughout it.

Business Central: scope the move before the year-end window
A move to Dynamics 365 Business Central is a business-system decision, not a last-minute software installation. It can reshape finance, purchasing, sales, stock control, reporting and the way teams work. A mid-December start is unlikely to provide the time and availability needed for proper discovery, data preparation, testing and user acceptance.
The Dynamics 365 Jump Start scoping conversation belongs in November if the organisation wants to plan a new-year implementation. That discussion should establish what the current system does, where data is held, which processes need to change, what integrations are required and who will own testing and sign-off. It should also assess whether standard Business Central functionality fits the need, rather than assuming customisation is the answer.
Microsoft’s Business Central on-premises to online migration overview sets out a migration process that requires planning and validation. A sound plan includes trial migrations, data reconciliation, checks on extensions and integrations, user preparation and a controlled cutover. Scoping now does not mean rushing a go-live; it means knowing what must happen, in what order, and whether the target date is realistic.
For businesses still relying on an ageing, unsupported on-premise finance or ERP system, carrying it through another year-end without reviewing risk is a decision too. It may be the right short-term choice, but it should be explicit, with suitable interim controls and a migration plan rather than indefinite deferral.
Legacy systems need cover, not assumptions
Some organisations depend on established IBM i (AS400) estates for core operational processes. These systems may be stable, but stability does not remove the risks of undocumented dependencies, limited specialist cover or reliance on one person who knows how the environment works.
That person may be on annual leave during the freeze. November is a good time to check monitoring, escalation arrangements, recovery documentation, supplier contacts and who can make decisions if an issue arises. Specialist IBM i Management can provide managed monitoring and 24/7 cover as part of a wider continuity strategy. The objective is not change for its own sake; it is ensuring the business understands how the service is supported when its usual expert is unavailable.

Audit renewals while there is still time to act
Technology Expense Management (TEM) is particularly valuable before the year-end freeze. Build a register of software, cloud, telecoms, support and maintenance contracts with renewal dates, notice periods, auto-renewal terms, quantities and accountable owners.
A renewal that falls during the freeze can be difficult to challenge in time. If a notice period passes or an auto-renewal takes effect, the organisation may be committed to another term before anyone has reviewed usage or value. Check active licences against actual users, identify duplicate services and review cloud consumption, but do not cut monitoring, backups or specialist support without checking the impact on recovery and security.
The point is to find avoidable cost and redirect it towards resilience where the business case supports it. TEM should inform strategic decisions, not simply reduce a line on an invoice.
Review the supporting services too. Cloud Solutions, Network Solutions and Voice and Connectivity all have dependencies that need to be documented, monitored and supported through reduced staffing. A renewal audit can reveal where service ownership or supplier escalation arrangements are unclear.
Treat the freeze as a compliance risk
A quiet office does not mean compliance responsibilities pause. Patch windows may be missed, certificates can expire over the break, monitoring alerts can go unattended, and evidence may be harder to gather if nobody has documented who is responsible.
For organisations working towards ISO 27001 or Cyber Essentials, the freeze period should be included in guided consultancy and compliance planning. Confirm who reviews security alerts, how urgent updates are authorised, which certificates and domains need attention, and where evidence of monitoring and action is retained. A change freeze should govern risk; it should not become a reason to ignore an urgent security issue.
Use November to make January safer
Before the freeze begins, business owners and finance directors should be able to answer four practical questions:
- Which changes must be completed, tested or deliberately deferred?
- Have backups and recovery procedures been tested against agreed RTOs and RPOs?
- Are critical systems covered when key staff are away?
- Which renewals or compliance tasks could become difficult to address during the freeze?
If those answers are unclear, the first step is a strategic review, not a rushed purchase or a stack of technical tasks. The right support may include consultancy, recovery planning and supplier coordination, with managed support bolted on where it helps execute the agreed plan.
For an initial discussion about strategy, resilience or a Dynamics 365 Jump Start, visit Evestaff IT Support and Consultancy. For the wider Evestaff group of services, 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, year-end IT change freeze, UK SME IT consultancy, Business Central migration planning
Join The Discussion