Building a useful year-end technology review
Use a year-end technology review to connect inventories, staff friction, recovery evidence and supplier renewals with a prioritized plan for the next year.

A year-end technology review should end with decisions for the next year. Bring the business owner, the people running the work and the person or provider managing IT into the same discussion.
Use evidence from the year: support issues, service changes, renewal dates and recovery tests. Don’t wait for the annual meeting to remove departed users or address an urgent security issue.
Start with the business changes
Record planned hiring, locations, customer commitments and changes in how staff work. Ask which technology dependencies those plans introduce.
Compare them with the current inventory. The Cyber Centre’s IT asset management guidance treats lifecycle information as part of security management. Include service owners and support dates alongside device names.
List uncertainties that need investigation before a budget decision. An incomplete inventory can hide a renewal, or a system no one knows how to recover.
Review where work gets stuck
Ask staff for examples of repeated re-entry, unclear file ownership and slow handoffs. Follow one example from start to finish. A satisfaction score alone won’t show you where it slows down.
Try the customer’s route to finding information, making contact and receiving a response. Compare the result with the service the business intends to provide.
Check whether existing tools can resolve a gap before planning another subscription.
Review operational evidence
Look at recovery tests, significant incidents, access reviews and unresolved vulnerabilities. Ask what the evidence shows and what remains untested.
Review policies against how people work now, including remote work and personal devices. When a policy changes, tell staff and check that the controls behind it work.
Check privileged and unused accounts through the normal access process. Before you delete an account or service, keep the records you’re required to hold. Tidying up shouldn’t cost you business records.
Examine supplier and cloud commitments
List renewals, cancellation windows, licence use and integration dependencies. Identify unsupported products and services with unclear ownership.
For tools staff signed up for on their own, find out what work and records they hold first. Plan the move to a tool the business has chosen, and don’t abruptly close an account that holds the only copy of business information.
Finish with a small roadmap
For each proposed item, record the business reason, responsible person, estimated cost, dependencies and acceptance evidence. Separate urgent corrections from projects requiring further discovery.
Schedule review points during the year so the plan can respond to changes. Our IT consulting work can help turn the review into a sequenced roadmap with clear owners.


