Most leadership teams hear about IT in two situations. Something broke, or someone wants to buy something. Both conversations start late, and both tend to focus on the item in front of the room instead of the condition of the systems the business runs on.
A short quarterly review changes that pattern. You do not need a long slide deck or a technical deep dive. You need the same set of questions, asked on a regular schedule, with answers written down and compared to the quarter before.
Why a quarterly rhythm works
IT problems build slowly. A backup job fails for weeks before anyone needs a restore. A vendor contract auto-renews because the notice date passed without a review. Access for former staff stays active because offboarding covered the office key and missed three cloud accounts.
A quarterly check gives you a chance to catch those items while they are still routine fixes. It also creates a record. When a question gets the same vague answer three quarters in a row, that pattern tells you something about ownership and follow-through.
Five questions to keep on the agenda
1. What changed in our access and security since last quarter?
Ask who joined, who left, and whether access was added and removed on time. Ask about admin accounts, multi-factor authentication coverage, and any security alerts that required action. Request counts and dates, not general assurances.
2. When did we last test a restore, and what did we restore?
A backup report shows whether jobs ran. A restore test shows whether the data can be used. Ask for the date of the last test, the system that was restored, and how long the work took. If there was no test this quarter, schedule one before the meeting ends.
3. What contracts renew or expire in the next two quarters?
Review software, support agreements, phone and internet service, and your IT support contract. For each item, note the cost, the renewal date, the notice period, and the person who owns the decision. Surprise renewals usually come from a missing calendar entry, not from a difficult vendor.
4. What are we working on, and what is waiting?
List the active IT projects, the business reason for each one, and the expected finish date. Then list the requests that are waiting and name the reason: budget, staff time, a vendor dependency, or a decision leadership still owes. That second list is often where the real discussion belongs.
5. What new tools, including AI tools, did teams start using?
Ask each department what it adopted, what company data the tool can access, and who approved it. New tools are not a problem by themselves. Unrecorded tools are, because nobody has checked the cost, the terms, or the data handling.
How to run the meeting in 45 minutes
Send the five questions a week ahead. Ask for a one-page summary with dates, counts, contract amounts, and project status.
Spend the first half reviewing changes since last quarter. Spend the second half on decisions: approve, defer, or cancel projects; accept or fix a risk; assign an owner and a date for each open item.
Close by reading back the decisions and the names attached to them. Send that list out the same day, and open the next meeting with it.
What good answers look like
Good answers are specific and easy to verify. October 12, restored the accounting file server, took 40 minutes. Multi-factor authentication is on for 96 of 98 accounts, with two service accounts under review. The phone contract renews March 1, notice is due January 15, and operations owns the decision.
Answers that need a follow-up are broad and timeless. Backups are fine. Security is handled. The project is in progress. Ask for a date, a count, or a document, and record the date by which it will be provided.
You will not solve every IT issue in one meeting each quarter. You will build a habit that surfaces issues early, assigns them to a named person, and checks whether they were actually closed. For most mid-market companies, that habit is where better IT management starts.
Not sure where your IT really stands? Start with a Clarity Audit: a focused assessment of your backups, security, vendors, and AI readiness. It's the first step in every engagement I take on.
About the author: Chris McGlasson is a fractional CIO and the founder of ClearStack Advisory, where he helps mid-market companies build AI governance, IT strategy, and technology roadmaps without the overhead of a full-time CIO. He previously built and sold LANPRO Systems, an IT services firm serving 350+ enterprise clients.