Most firms I talk to have the same shape. It started with one file server and three laptops, and over the years it grew into a document store, a practice management system, a cloud file share, a dozen browser extensions, a handful of vendor contracts, and a shared password for the server room. Nobody designed that environment. It accumulated, one reasonable decision at a time, and everyone in the firm knows roughly how it works because somebody, at some point, had to make it work.

The problem is not that any single piece of that is broken. The problem is that nobody ever looks at the whole thing. The newest associate does not know why there are two document stores. The partner who chose the practice management system left three years ago. The renewal notice from the document vendor arrived in an inbox, was forwarded to someone who was on vacation, and renewed at a higher price by default.

A quarterly IT review is the smallest unit of attention that reliably catches this drift before it turns into an incident. It is not a technical audit. It is a recurring, scheduled look at the systems, vendors, and access your firm depends on, run by someone who is actually able to make decisions about them.

What a Quarterly IT Review Is (and Is Not)

It is worth being precise about this, because "quarterly IT review" gets used for two very different activities.

What it is:

  • A 60 to 90 minute meeting, on the calendar, once a quarter. It ends on time.
  • Owned by the person accountable for the firm's operations: the owner, a managing partner, or an office manager. That person attends, and they can decide.
  • Run from a short, written agenda with a fixed order.
  • Recorded in a living document, one page per quarter.
  • Cheap. It costs about ninety minutes of somebody's attention and no money.

What it is not:

  • It is not a technical audit of every system you own. That is a separate, larger project with a different scope and a different budget.
  • It is not a vendor demo or a renewal negotiation meeting. Renewals come up in the review as items to decide, and the decision happens separately.
  • It is not a test of whether staff can use the software they already use. Training problems are real, but they belong in a different conversation.
  • It is not a report delivered upward to a partner or a board. It is a working session with people who can act on what they find.
  • It is not a one-time project. A single review is a snapshot with no context. The value comes from doing it four times a year and comparing notes.

The Agenda: Eight Sections to Walk Through

Keep the order the same every quarter. A consistent sequence means you can stop thinking about structure and spend the whole session looking at content. Here are the eight sections, and what "good" looks like in each one.

1. Access and offboarding

Put the list of people with access next to the list of people employed. Then check everyone who left since the last review and every account that belongs to somebody who is not there. Look at the document store, the practice management system, the billing system, the domain registrar, the shared calendar, the office door system, and any shared drive.

Good looks like: the two lists match, with two named exceptions you can explain. Staff who left are off the document store and out of the practice system, and their files were moved to whoever inherited their matters or clients. Nobody still has administrator rights in a system because they set it up in 2019.

2. Vendor and renewal review

List every vendor that bills the firm on a recurring basis, every contract with a renewal date, and every service nobody can name an owner for. A renewal falling in the next ninety days is the important one, because auto-renewal quietly removes your negotiating position without removing the cost.

Good looks like: you know what each vendor does, what it costs, who actually uses it, and when it renews. Every renewal in the coming quarter has a named person responsible for the decision, and that decision gets made before the notice arrives. A subscription nobody logs into has been cancelled or has a reason written down.

3. Backup and restore verification

The point is not that backups exist. The point is that a restore has been attempted. Pick something that is not critical, a document from six months ago or a closed matter folder, and restore it somewhere disposable. See what happens.

Good looks like: you can name the date of the last restore test and what was restored. The backup covers the document store, the practice management system, and the firm's email, which are the three things that would hurt most to lose. The person who could perform a restore is not only the person who set the backup up, or there is a second person who has done it once. Restores happen on a schedule rather than during an incident.

4. Recurring incidents and what they reveal

Pull the previous quarter's support requests, IT emails, and whatever notes staff kept. Count the things that came up more than once, because repetition is the signal. One-off problems are noise. The third password reset for the same person is a configuration problem, not a person problem.

Good looks like: each repeated issue is sorted by what it actually is. "The second-floor printer jams" is a nuisance with a hardware owner. "Nobody can reach the shared drive from the conference room" is a configuration gap. "The practice system locks up when two people save at once" is a capacity issue and a reason to talk to the vendor. Every recurring item ends in one of three states: fixed, owned with a date, or explicitly accepted as-is.

5. Security posture check

This is not a penetration test. It is a short check of the handful of things that account for most of the exposure in a firm this size.

  • Multi-factor authentication on email, the document store, the practice management system, banking, and the domain account itself.
  • No shared login used for more than one system.
  • Full-disk encryption on the laptops.
  • The firm's email can send from a known address, and no personal email is used for client work.
  • Remote access goes through a VPN or a managed tunnel. Nothing is directly exposed to the internet.
  • One written sentence describing where client files live.

Good looks like: you can answer all six without hesitating, and the answers are recorded in a place other people can find.

6. Capacity and cost review

Pull the last quarter's IT spend and read it line by line: subscriptions, hardware, services, and the invoices that arrived quietly enough to escape notice. Check whether anything is approaching a limit, storage filling up, an office machine old enough to be a liability.

Good looks like: you can produce a monthly total for the firm's IT spend and split it between subscriptions, hardware, and services. You know what happens when the main document store fills up, whether that is an overage charge, an upgrade, or nothing at all. Nothing on the list is a surprise. If a number is a surprise, that surprise is the finding.

7. Documentation gaps

The most valuable missing document in a small firm is usually the one nobody wrote. Check for a password manager, an inventory of accounts and vendors, the location of client data, an offboarding checklist, and a written answer to what happens if the office cannot open the doors on a Monday.

Good looks like: a departing employee's checklist exists as a document, even if it is a single page. Somebody knows where the master list of accounts and vendors lives, and it is not in one person's inbox. Where client data lives is written down in one sentence that a new hire could read on their first day.

8. Next-quarter commitments

The review does not end with findings. It ends with a short list of things that will happen before the next one, each with a name attached.

Good looks like: three to five items, each with an owner and a date, each small enough to actually get finished. "Send the offboarding checklist to the two people who handle departures." "Ask the document vendor for a usage export so we can see what we are paying for." Nothing on the list is shaped like "improve IT."

How to Run It

Who should be in the room

Two people maximum, and both need authority. The owner or managing partner, because most of the decisions this review produces involve money or risk acceptance. Plus whoever actually does the hands-on work: an office manager, a senior associate who handles the systems, or your outside IT provider.

The person who raises a problem is rarely the person who can decide what happens about it. If one person holds both roles, that works, but bring one other person for a second set of eyes on the access and offboarding sections, because those are the ones where you are least likely to notice your own leftovers.

An outside provider can sit in the review without driving it. If the firm uses one, the meeting goes faster: they can answer most of the access, backup, and vendor questions in minutes, which leaves the owner free to spend the time on decisions instead of status. If you do not have one, a colleague who is comfortable with the systems can fill that role.

What to gather beforehand

Send the agenda out two or three days ahead with a short request for inputs:

  • Anyone who joined or left since the last review
  • Any IT bill that arrived and was not obviously processed
  • Any vendor communication about renewals or price changes
  • The support requests that came in during the quarter

Ten minutes of gathering per quarter is enough. If gathering takes longer than the meeting itself, the firm is running on undocumented systems, and that is worth recording as the first finding of the review rather than treating as a reason to skip the gathering.

How to record the output

One document, one page per quarter. A log, not a report. Each page has the date, who was there, what was found, what was decided, and what was committed. Include the things you decided to accept as-is, not only the things you fixed. A quarterly review that records only problems turns into a complaint list, and a complaint list gets skipped within two quarters.

Keeping it useful across quarters

Open the previous quarter's page before you start, and read the commitments list first. Did each item happen? When one did not, the useful question is why: it was not important enough, it had no real owner, or the owner was buried in billable work. That answer tells you more than the item itself, because it tells you whether the problem is the list or the capacity behind it.

Over a year, four pages start to tell you something no single quarter can. Where the same issue keeps coming back, where the same vendor keeps being renewed without a decision, where the same person keeps being the only one who knows how something works. That pattern is worth more than any individual finding.

When the Review Shows Something You Cannot Fix In-House

Every quarter, one or two items on the list will be more than an office manager can handle in an afternoon. That is normal, and it is not a failure of the review. The finding is correct. The question is whether the firm has the people and the hours to do the work.

Common examples:

  • Restructuring identity and access across the document store, the practice system, and the mail server at once. It is slow, fiddly work, and it has to happen without locking anyone out during a busy week.
  • Verifying that backups actually restore. A restore only means something if you know what a correct result looks like, and untested restores often fail for boring reasons.
  • Segmenting a network that grew by accretion over eight years.
  • Deciding what to do with a server somebody built that nobody has touched since 2023.
  • Keeping track of patching, renewal dates, and vendor notices on a continuous basis when nobody's job title is IT.

None of this requires a managed provider. Some firms have an employee or a partner who genuinely wants to own it, and that can work well. The honest test is whether the work will actually get done when the billable work is pressing. For most firms the answer is no, because this work competes with revenue-generating work every single time it comes up.

If your review keeps producing findings that stay open, that is a signal worth acting on. It means the gap is structural rather than informational. Another quarter of attention will not close it, because the missing ingredient is time and expertise, not another look.

Where to Start

  • Put ninety minutes on the calendar for the first week of the quarter. Same week, every quarter, and treat it like a client meeting rather than a task.
  • Run the first one yourself with one other person. It will be rough and it will find something in the first twenty minutes.
  • Write the page. A rough page that exists beats a good template that does not.
  • Read the previous page before you start the next one.

If you want a second set of eyes on the environment, Techneek runs a focused 30-minute qualification conversation. We respond within one business day. It is not a free technical audit; it is a conversation about the environment, the operating pain, and whether there is a sensible next step. If your first review surfaces something the firm cannot fix in-house, that conversation is the natural place to bring it.

The free 25-item IT security checklist covers much of the security section and takes about ten minutes, so it makes a reasonable starting point before the first review.

Want a second set of eyes on your environment?

Request a focused 30-minute qualification conversation. We will look at the operating picture together and tell you plainly whether there is a sensible next step.

Request a qualification conversation
Share this article:
NM

Nico Mancinelli

Founder of Techneek. Builds and manages production infrastructure for small businesses, specializing in private AI, self-hosted systems, and managed services. Learn more.