Multi-Campus Attendance: Reporting Across a District

Run three schools and you will eventually be asked a question that sounds simple and is not: how are we doing on attendance across the group? A single number feels like it should be a click away. In practice, getting an honest answer across several campuses forces a district to resolve a tension that a single school never has to think about — between a shared view from the centre and the independence each school needs to run itself.

Get the balance wrong in one direction and you have a uniform system that fits no campus well. Wrong in the other and you have three islands that cannot be compared, which was the entire point of grouping them.

Why a central view is hard

The instinct is that combining attendance across schools is just addition. It is not, for a reason that trips up nearly every district that tries it with spreadsheets: the schools are not measuring the same thing the same way.

One campus marks a student late after five minutes; another after fifteen. One counts an authorised medical absence differently from how the next one records it. One closed for a local holiday that the others did not observe, so its "attendance rate" that week is depressed by a closure, not by absent children. Stack three schools' numbers side by side without reconciling any of this and you get a league table that measures definitions, not performance.

So the first job of district reporting is not technology. It is agreement.

Shared standards come first

Before any dashboard is worth looking at, the schools in a group have to agree on what the words mean.

• One definition of late, present and absent. If a student who arrives at 9:05 is late at one school and present at another, no comparison between them is honest.
• Consistent absence categories. Authorised, unauthorised, medical, exclusion — the same codes, meaning the same things, everywhere.
• A shared view of the calendar. Comparisons have to account for which campus was open on which day, or a holiday reads as an attendance collapse.

This is dull work and it is unavoidable. Each school can apply the same standards once the group agrees them — the same categories, the same thresholds — but no system can invent the agreement. That is a leadership decision the district has to make first, and then set up in each school.

Isolation and roles: separate, then combine

The counterweight to central reporting is that each school is still its own place, with its own staff and its own duty of care over its own students' data. A teacher at one campus has no business browsing the individual records of children at another. Central oversight cannot become a backdoor that dissolves that boundary.

This is where roles and data isolation do the real work.

1. Each school's data is walled off by default. Staff see their own school. The boundary is the baseline, not an afterthought bolted on later.
2. Multi-school access is deliberate. A leader who administers several schools can switch between the ones they are responsible for — because their job needs it, and only to the schools it needs.
3. The granularity stays honest. Comparing campuses usually works at the level of rates and trends. A leader needs to know that one school is slipping; they do not need every named child's record from another to see it.

The model, in short: isolate by default, aggregate on purpose, and let the role decide who sees across the wall.

Comparability is the point, so protect it

Once standards are shared and roles are clean, the district gets the thing it actually wanted — the ability to compare campuses fairly and act on what it sees.

Fair comparison surfaces the questions worth asking. Why is one school's Year 10 attendance drifting while the others hold steady? Is a dip at one campus a real problem or an artefact of a local closure? Which site has quietly improved, and what did they change that the others could borrow?

None of those questions can be answered if the underlying numbers were never made comparable in the first place. Which is why the sequence matters and cannot be shortcut: agree the standards, enforce them consistently, keep each school's data properly isolated, and only then read across the group with any confidence.

A district that skips straight to comparison and hopes the definitions sort themselves out ends up making decisions on noise. Classable is built for groups of schools on exactly this basis — each campus isolated as its own tenant with its own roles, and a leader who administers several schools can switch between them to compare how each is doing, without tearing down the walls between them. The shared standards that make those comparisons fair are a decision the group applies in each school, not an automatic cross-school roll-up — the honest comparison is the one you set up deliberately.