What a real systems audit finds (and what schools are surprised by)

A systems audit, done properly, takes about two weeks of part-time work in a school. We sit beside people. We follow workflows from beginning to end. We read the documents. We talk to the staff who actually do the work, not just the staff who manage the work.

In the audits we have run, the things that surprise the leadership team at the end are remarkably consistent. They are not the things on the agenda when the audit started.

The first surprise. The amount of work being done by a single person whose name nobody in the senior team would think to mention. Every school has them. The administration officer who has quietly become the source of truth for student data because the SIS has been unreliable for years. The lab technician who manages the ordering across three departments because nobody else picked it up. The placement coordinator who is also, in practice, the careers counsellor. The maths department coordinator who is in fact the person running half of Year 12. These people show up in every audit. They are usually load-bearing. They are usually not paid what they are worth, and they are usually one resignation away from a crisis.

The second surprise. The reporting flow that the leadership team thinks is automated is actually being typed by hand by somebody every Friday. There is nearly always at least one of these. Sometimes the leadership team genuinely doesn't know it. Sometimes they know it but assume it's faster than it is. Sometimes the person doing it has stopped mentioning it because the answer was always "we'll fix that next term".

The third surprise. Two systems that the school has been paying for for years are doing the same job. Or worse, two and a half jobs, with overlap in confusing places. In most audits we find licences the school is paying for twice, or no longer using. Schools are usually not surprised that this exists. They are surprised by how easy it was to find once someone was actually looking.

The fourth surprise. The communication channel that the leadership team thinks parents prefer is not the one the parents actually use. Schools have invested heavily in their portals, their apps, their emails. The audit conversation with parents almost always reveals that the most important channel is text messages from the homeroom teacher, and the second most important is word of mouth at school pickup. None of which is in any system the school has bought.

The fifth surprise. The single biggest opportunity to reduce admin load is almost never the system everyone is complaining about. The system everyone is complaining about is usually a symptom. The actual cause is two layers down: a process that was designed for a school half this size, a data model that nobody owns, or a handover assumption that stopped being true two years ago.

The audit doesn't fix any of this. The audit names it, prioritises it, and gives the leadership team a defensible plan. The fixing happens afterwards, and only if the school is willing to do the unsexy work of choosing what to stop doing.

Most schools are. The ones that aren't, we politely decline to start work with. There is no point producing a roadmap for a school that has already decided it isn't going to follow one.