The most underused tool in school operations: a clear data model

Most operational problems I see in schools, when I trace them back far enough, do not turn out to be tool problems. They turn out to be data problems. Specifically, they turn out to be problems with the school's data model.

A data model is an unglamorous phrase for a very practical question. For each piece of information that matters in your school, where is the source of truth, and who is allowed to change it.

The schools that have answered this clearly have remarkably calm operations. The schools that haven't are quietly chaotic in ways the leadership team rarely sees, because the chaos has been absorbed by the staff working close to the data.

Let me give a concrete example. Consider a single piece of information: a student's emergency contact number. In a typical school, that number can be in:

The SIS. The emergency contact list printed at the front office. The medical office's spreadsheet. The Year 12 coordinator's personal phone. The bus operator's running list. The first aid officer's binder. Compass or Sentral or whichever parent-facing platform the school uses.

When the parent updates their number, where do they update it? Usually one place, sometimes two. The other five places are now slowly drifting from reality. Which one does the staff member call when there is a real emergency? Whichever one they remember, which is usually the one closest to hand.

This is not a tool problem. It is a data model problem. Until somebody at the school decides which one is the source of truth and that all the others are derived, the drift will continue, and so will the small but persistent risk of using the wrong number at the worst possible moment.

The exercise of building a clear data model is not technical. It is organisational. It requires the leadership team to decide, for each major category of information, which system owns it and which other systems are allowed to read it. It also requires deciding what happens when two systems disagree, because they will. The system you have chosen as the source of truth wins, and the other system gets corrected. Not the other way around.

Most schools I work with have never had this conversation explicitly. They have inherited a data landscape that grew up organically over a decade, with each new system adding its own copy of the same information rather than referring back to a single source. The cost of fixing this isn't large. The cost of not fixing it shows up as a long tail of small operational problems that nobody can quite trace.

If your school has not had this conversation, the simplest place to start is with a single piece of information that turns up in operational decisions weekly. Student emergency contacts. Student medical conditions. Staff allergies. Year level rolls. Pick one. Map every place it currently lives. Pick the source of truth. Decide what changes when, and update every other system to reflect it.

The exercise will take longer than you think and will reveal more than you wanted to know. It will also be the most valuable single piece of operational work the leadership team will do this year.