Most schools have structure. Almost none of it is written down where software can read it — which is why follow-up depends on memory and reports still get typed by hand.
Ask a principal who reports to whom and you will get a complete, accurate answer in about forty seconds. Ask the school's software the same question and you will get nothing at all.
That gap is not a filing problem. It is the reason a dozen daily frustrations exist, and they are usually treated as separate problems with separate fixes.
Every school we talk to recognises most of this list.
Instructions live in a WhatsApp group, so there is no record of who a job went to or whether it was done. Follow-up depends on whether the person who asked remembers to ask again — which means the quiet jobs are the ones that never finish. When something is missed, "I was never told" cannot be settled either way, so the conversation becomes about blame. Dates slide one reasonable week at a time until the deadline is close. Staff logins are either wide open, so fee and salary information sits in front of people who should not see it, or locked so hard that nobody can do their job. And somebody spends part of every day collecting status by phone and typing it into a summary that is a day old by the time it is read.
Six symptoms. One cause: the school's hierarchy is not available to the software.
A system that does not know that a particular teacher is Head of Science, that four teachers report to her, and that she reports to the Vice Principal, cannot route an approval, cannot escalate an ignored job, cannot show her the department and nobody else's, and cannot produce a report without somebody typing it.
One field. Each member of staff has exactly one reporting manager.
That sounds trivially small, and it is — which is why it gets rushed. It is also the field that every other mechanism reads. Leave approval routes through it. Escalations climb it. "Their team's records" is resolved from it. The day's report is grouped by it. Get it right in the first hour and a dozen features start working as a consequence; skip it and each of those has to be configured by hand, one person at a time, for ever.
The one rule worth insisting on is that it is never blank. In Jupeak One the question "who does this person answer to?" works down four answers and takes the first real one:
It never answers "nobody", because every place that answer appears is a place where something silently stops working.
A manager who leaves is not a dead end: the chain simply moves on. And a loop — making a teacher report to somebody who already reports to her — is refused when you save it, with both names in the message, rather than discovered three months later when a report looks wrong.
Schools form groups constantly: the Annual Day committee, the inspection team, the bus route 4 crew. These are real and worth recording, but they are not the hierarchy, and conflating the two causes a specific kind of accident.
A named team is an audience — who work can be handed to as a group. The reporting line is a line of authority — who may see and manage whose work.
In Jupeak One, membership of a named team grants no additional access to data at all. If it did, adding a teacher to the Annual Day committee would quietly hand her every committee member's records — which nobody intends, and no screen would warn about.
Departments are a third axis: which part of the school somebody is in. Their value is in reports — narrow a report to Transport and staff from other departments disappear from the rows, the totals and the people picker. A department with nobody in it shows an empty report, never everybody, because a filter that silently falls back to "everyone" is how confidential figures reach the wrong reader.
This is the part that pays for the setup.
A task in Jupeak One carries one owner, a date, and its own history. Give it those two things and the follow-up arms itself — you do not have to remember to switch it on, because forgetting to is exactly the failure it exists to prevent.
Two details in that list matter more than the rest.
The numbering. "Reminder 3" is the difference between "I never got it" and a fact. Nobody has to remember who was told what.
The stopping. A tool that pings somebody every thirty minutes about the same job gets muted, and a muted reminder protects nothing. This is why the cadence is deliberately gentle, and why anything the owner says — a comment, a reply, or "ask me again at 4 pm" — ends it.
There is one thing worth checking before trusting any of this: escalation needs somewhere to go. If no escalation target exists, the escalation is skipped silently; the reminders run to their cap and stop, and nobody senior is ever told. Escalation that reaches nobody looks exactly like escalation that was never needed. Set it once, then test it with one real task.
Every time a due date moves to a different day, the task counts it. Past a limit the school sets — three by default — the owner's reporting manager is told, and told again on each further move.
Setting a first date does not count. Clearing one does not count. Nudging the time within the same day does not count. Only a job genuinely sliding to another day.
It is the difference between finding out about a problem while it is still a scheduling problem, and finding out the week before the deadline.
The same handful of mechanisms carry most of a school's recurring work.
In every case the school configures the work once, and the follow-up is a consequence. Nobody is employed to ask "is it done?" — and that question is where most of a school office's day currently goes.
Not with the software. With the list.
Write down every member of staff and who they answer to. If that list takes longer than an hour to produce, or two people produce different versions of it, you have found something more valuable than any feature comparison — and it needed no system to discover.
A companion piece covers the other half of running a school's staff: why teacher appraisals collapse, and the three things that fix them.
Thirty minutes is usually enough to set up the departments and the reporting line for a school of 150 — and then the rest of the decisions make themselves.