The hidden cost of seven different login screens

One of the simplest exercises I do early in a systems audit is sit beside a head of department for a morning and count the platforms she opens.

The count usually shocks the person sitting next to me.

The most recent example. Compass for attendance. The school's own SIS for student demographics. Google Drive for shared lesson resources. OneNote for class notebooks. SeeSaw for the early years overlap with the primary campus. The state-level reporting platform for VCAA work. Three separate Google Sites for compliance documentation. The faculty's shared spreadsheet for assessment moderation. The school's HR portal for leave requests and absences. The wellbeing platform for student notes. The professional learning portal for PD bookings.

Eleven, before recess.

None of these platforms talked to each other. The head of department was the integration. She held the threads in her head, copy-pasted between systems, manually reconciled the data when it disagreed, and absorbed the cost when something fell through the cracks.

This is the hidden cost of tool sprawl. Most schools don't see it because each tool, in isolation, made sense when it was bought. The compliance tool was purchased to solve a compliance problem. The wellbeing platform answered a wellbeing problem. The reporting tool answered a reporting problem. Each looked like a sensible discrete decision.

The cost only becomes visible when you stop looking at any single tool and start looking at the person who has to use all of them. And it is rarely accounted for in the conversation about whether to add the twelfth tool.

The framing I find useful when schools are considering a new platform is to ask, before the demo even starts: which existing tool is this replacing? Not which tool is this adjacent to. Which tool will leave the building when this one arrives? If the answer is "none", the conversation gets harder. The cost of a new tool isn't only its annual licence fee. It is the additional cognitive load on every staff member who now has to know one more place to check.

The schools that have made the biggest reductions in admin workload haven't done it by adding a magic productivity tool. They have done it by ruthlessly removing the half they didn't need, building one or two integrations between the half they kept, and being explicit about which person owns which question.

If you can identify three tools in your school that no one would notice if you turned them off for a term, you probably have a quiet workload reduction sitting in front of you.