What a quarterly review is for
Day-to-day IT support is reactive by nature: something breaks, someone fixes it. A quarterly review is the opposite. It is a planned conversation about the bigger picture, where you and your provider step back from individual requests and look at trends, risks and upcoming decisions. Done well, it is where most of the long-term value of a managed IT relationship is created.
Many businesses let reviews drift. The meeting gets postponed, becomes a quick phone call, or turns into a sales pitch for new products. The fix is to treat it like any other management meeting: a regular slot in the diary, a simple agenda, the right people in the room and actions written down with an owner and a date.
What to prepare beforehand
Spend fifteen minutes before each review gathering input. Ask a few staff what has frustrated them about IT in the last three months. Note any upcoming business changes: new hires, departures, a move, a new client with security requirements, a new software system or a change in how people work. Your provider cannot plan for changes they do not know about.
Also ask the provider to send their reports a few days ahead so you can read them properly rather than skimming during the meeting. Write down two or three questions. Even a simple question like why the number of requests about printers doubled can lead to a useful conversation and a lasting fix rather than another quarter of the same complaint.
The reports worth reading
A useful review pack is short. Look for a summary of support requests by category and priority, response times against targets, patch compliance showing how many devices are fully updated, backup success rates with any failures explained, and security events with what was done about each. A list of devices approaching end of warranty or end of support is also valuable for planning.
Do not be impressed by volume. Pages of graphs are less useful than a clear sentence saying what changed and why it matters. If a report is hard to understand, ask the provider to explain it in plain English or simplify it for next time. The purpose is to inform decisions, not to demonstrate how much data their tools collect.
The questions to ask
Ask what the most common problems were and whether any have a root cause that could be fixed for good. Ask what the biggest risk in your environment is right now and what it would take to reduce it. Ask what is coming up in the next six to twelve months, such as hardware reaching end of life, licence renewals or vendor changes that will affect you.
Ask whether anything you are paying for is not being used, and whether anything you are not paying for should be considered. A good provider will answer both honestly. Finally, ask what they need from you, because many IT improvements stall waiting for a decision, an approval or information that only the business can provide.
Turning talk into action
End every review with a short written list of actions, each with an owner and a target date. Some will belong to the provider, such as fixing a recurring backup warning. Others will belong to the business, such as approving a laptop replacement budget or deciding on a security training date. Keep the list short enough that it actually gets done before the next meeting.
Start the next review by going through that list. This one habit transforms reviews from pleasant conversations into a steady programme of improvement. Over a year, four reviews with three or four completed actions each add up to real progress, often more than any single large project would deliver on its own.
Who should attend
From your side, include someone who can make decisions about spending and priorities, usually the owner or general manager, plus the person who deals with IT day to day, such as the office manager. From the provider, you want someone who understands your environment technically and someone who can speak to strategy and planning, sometimes the same person in a smaller provider.
Keep it to an hour. If reviews regularly run long, there is probably too much day-to-day detail being discussed, which belongs in normal support conversations. Once a year, consider a longer session focused on strategy and budget for the year ahead, using the quarterly reviews as the foundation for that conversation.
In short
- Quarterly reviews are where long-term value in managed IT is created.
- Gather staff feedback and business changes before each meeting.
- Ask for short reports on requests, patches, backups and security.
- End every review with written actions, and start the next by checking them.