How to Audit Your School's Technology Stack

Ask a primary head how many digital systems their school pays for, and you will usually get a pause, a guess, and then an uncomfortable trip to the finance spreadsheet. The real number is almost always higher than expected. A messaging app bought in 2019. A payments provider inherited from a previous business manager. An observation tool one nursery practitioner loved and nobody else ever opened. Two different places where parents' evening bookings live, depending on who set them up.

Most schools do not have a technology strategy — they have a technology collection. It accumulates the way staffroom mugs accumulate: one free trial, one urgent purchase, one well-meaning recommendation at a time. None of it is anyone's fault, but the cumulative cost is real, and it is paid in money, in staff time, and in parents who have no idea which app to check.

A technology audit fixes that. Done properly, it takes a couple of half-days spread over a term and it is one of the highest-return pieces of work a school leadership team can do. Here is how to run one.

Start With an Honest Inventory

Before you can evaluate anything, you need to know what exists. Open a blank spreadsheet and list every piece of software the school touches. Not just the big platforms — everything. The MIS, the communication app, the payments system, the observation tool, the safeguarding log, the cloud storage, the forms tool, the behaviour app, the survey tool, the thing the PE lead uses for sports day.

Three sources will get you most of the way there: the finance ledger for anything with a direct debit, the office team for anything they log into daily, and a short staff survey asking teachers to name every system they use in a typical week. That last one always produces surprises. Shadow IT — tools staff adopted themselves because the official option was too slow or too clunky — is extremely common in schools, and it is a symptom worth paying attention to rather than a rule to enforce.

For each entry, record what it does, who owns the relationship, what it costs annually, when the contract renews, and roughly how many staff genuinely use it. That final column is where the audit starts to bite.

Work Out What It Actually Costs

Subscription fees are the obvious number, but they are rarely the biggest one. Add the per-user charges that scale as your roll grows. Add transaction fees on payments, which quietly take a percentage of every trip, club and dinner money collection. Add setup and training costs. Add the cost of the staff hours spent rekeying the same pupil data into three different systems because none of them talk to each other.

Then add the invisible cost: a business manager spending an afternoon a week reconciling payment reports across platforms is a real salary line, even though no invoice says so. When schools total this up honestly, the duplicated-effort figure usually dwarfs the licence fees.

If you cannot answer question one with something specific, you have likely found a candidate for removal. If you cannot answer question three with a confident no, you have found an opportunity to consolidate.

Measure Adoption, Not Licences

Buying software is easy. Getting people to use it is the whole job. Nearly every school technology audit uncovers at least one platform with full licensing and almost no logins — paid for in good faith, abandoned quietly after the launch INSET, never cancelled because nobody was sure who still relied on it.

Ask your vendors for usage data; reputable providers will supply it. Then compare it with what staff tell you. A tool with high licence counts and low weekly active use is not a training problem to solve, it is a purchase to question. Conversely, a tool that staff use constantly and praise without prompting is worth protecting, even if it is not the cheapest line on the sheet.

The same applies to parents. Check how many families have actually activated accounts, how many have notifications switched on, and how many opened the last three announcements. Parent engagement is a measurable thing, and if you are not measuring it, you are guessing.

Map the Workload, Not Just the Features

This is the step most audits skip, and it is the one that matters most for reducing teacher workload. Pick three routine processes — reporting an absence, collecting trip money, writing end-of-term reports — and trace each one end to end. Who touches it, in which system, how many times?

A trip might start as a letter in a document tool, become a form in a survey tool, generate payments in a finance platform, require a reminder sent through a messaging app, and end in a spreadsheet reconciling who paid and who consented. That is five systems and four manual handovers for a single afternoon at a museum. Every handover is a place where something gets lost and someone chases it.

The question is not whether each tool is good. It is whether the joins between them are costing you more than the tools are saving you.

When you draw these journeys out on paper, the case for consolidation usually makes itself. Schools that bring communication, observations, homework, attendance and payments into one integrated platform are not chasing a shinier interface — they are eliminating the handovers.

Check Compliance and Safeguarding Properly

Every system holding pupil or family data needs a data processing agreement, a clear retention policy, and defined access controls. For each one, confirm where data is stored, who at the provider can see it, how long it is kept, and how you would export or delete it if you left.

Pay particular attention to safeguarding records. These should sit behind restricted access with a logged audit trail, available only to designated leads. If concerns are currently recorded in a shared document or a general-purpose tool, that is the most urgent finding your audit will produce. Also review staff authentication — two-factor authentication on accounts holding pupil data should be the norm, not an upgrade.

Test the Parent Experience Yourself

Borrow a phone that is not yours and try to be a parent for twenty minutes. Report an absence. Find next term's dates. Pay for a club. Message your child's teacher. Count the apps you need, the passwords you are asked for, and the dead ends you hit.

For families juggling two children in different year groups, or separated parents who both need access, or households where English is an additional language, friction compounds fast. A parent who has to remember which of four apps handles which job will simply stop checking all of them — and then you are back to paper letters in book bags.

Decide: Keep, Consolidate, or Cut

With the evidence gathered, sort every system into one of three piles. Keep what is well used, compliant, and does something nothing else does. Consolidate where two or more tools overlap or where a process crosses too many systems. Cut what nobody uses, nobody can justify, or nobody owns.

Then sequence the changes around renewal dates and the school calendar. Do not migrate your payments system in the week before a residential. Summer term, with September as the relaunch, is usually the sensible window, and it gives you time to bring staff and parents with you rather than announcing a change by notification.

Make It a Habit

The best version of this is not a one-off project but an annual rhythm — a standing item each spring, reviewed by the leadership team alongside the budget. Twenty minutes a year per system keeps the collection from growing back.

Good school admin software should reduce the number of places your staff have to look, not add to it. The point of the audit is not to buy more technology; it is to make sure what you already own is earning its place. Most schools find they can do more with less — and that the time they get back is the real return.