Resource

Spotting a Child in Trouble

Attendance, behaviour, marks and unpaid fees are four registers every school already keeps and no school can read together. This is what happens when they are read together: one risk board, one standing rule that maintains its own membership, one form tutor told on the morning it matters — and one child’s whole record in date order.

School AdminForm Teacher
Spotting a Child in Trouble

The child nobody notices is visible in four places at once

Ask any head of year how a child ends up in real trouble and the answer is never one dramatic event. It is a Monday absence a fortnight, a core average sliding from sixty to forty-six, four late marks nobody joined up, a clinic visit where the nurse noted she had not eaten, and a family that quietly stopped paying in May. Each of those lives in a different register, each is individually unremarkable, and in four separate systems nobody ever sees them in the same place. This walkthrough starts with those registers apart, exactly as a school holds them, and then puts them together: a score, a rule that maintains its own list every morning, an intervention that fires on the day a child crosses the line, and a record that reads like a story rather than five exports.

On this page
Step 1 · School office

Three registers that would normally never meet

Start where every school already is. These are three real screens from three different parts of the platform, and each is genuinely useful on its own — but each is also the reason the child in this story stays invisible: no one of them contains enough to raise an eyebrow.

1

Attendance, watched rather than filed

Who is missing today, which registers were never taken, and which pupils have crossed the school’s own attendance thresholds. It is the single best early-warning signal a school has, and on its own it says “87%” — a number that is worrying only if you already know what else is happening.

Today’s picture and the term’s trend for every pupil
Registers not yet taken, by class and period — the gap that quietly ruins attendance data
The school’s own concern thresholds, not a vendor’s idea of them
Both registration and per-lesson attendance, because a child present at 8am and missing from period four is a different problem
2

Behaviour, in points and incidents

Awards, incidents, detentions and the net position per pupil. Four late marks in a fortnight is a mild negative here and nothing more — the system has no way, on this page, to know that the same fortnight contains a fall in her marks.

Positive and negative points, awarded by the teachers who saw the behaviour
Incidents and their outcomes, kept separate from routine points
The net position per pupil across the term
Which staff are awarding what, which is its own useful and uncomfortable number
3

And the register nobody thinks of as pastoral

Unpaid fees, by pupil and by class. Bursary schools treat this as a money screen, and it is — but a family that has stopped paying in May is very often a family where something has changed, and that is a pastoral fact sitting in a finance system.

Outstanding balances per pupil, with the age of the debt
Promises to pay and the conversations already had
Chasing tasks, so the follow-up is a workflow rather than a memory
The same pupil record the register and the gradebook read — which is what lets the next screen exist at all

Ready to run your school on this?

Every screen in “Three registers that would normally never meet” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 2 · School office

One board, computed from all of it

The risk board is the platform reading those registers together and scoring each pupil against the school’s own definition of concern. This is the screen that only exists because the modules share a record — not because a clever report was written, but because there is one pupil row for attendance, behaviour, marks and fees to be about.

1

Every pupil, scored, worst first

Attendance, behaviour and academic standing rolled into one score, with the components still visible beside it so a head of year can see what drove it. Sorted worst first, because that is the order this page is actually read in on a Monday morning.

A composite score per pupil, with its attendance, behaviour and academic parts shown separately
High, medium and low bands drawn at the school’s own thresholds
The stat row is the server’s count over the whole roll, not over the page you are looking at
Filter by band, class or grade, and open the pupil behind any row
Recomputed as the underlying registers change, so it is never a report somebody forgot to run
2

And the school decides what “at risk” means

Two numbers, set by the school. This matters more than it looks: a boarding school with 98% baseline attendance and a large day school in a city do not share a definition of concern, and a platform that hard-codes one of them is wrong for the other.

The high and medium thresholds, as plain numbers
Validated against each other, so an impossible pair cannot be saved
Changing them re-bands the board immediately — no recalculation to schedule
Who changed them, and when, is on the audit trail like every other consequential setting

See this on your own school’s data.

Every screen in “One board, computed from all of it” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 3 · School office

A list that maintains itself

A board tells you who is at risk today. What a school actually needs is a list that keeps itself — because the intervention list agreed in a September meeting is accurate for about three weeks, and then it is a document that quietly becomes wrong while everyone still believes it.

1

The school’s standing rules

Each row is a sentence a school already says out loud — “the ones whose attendance has slipped”, “the ones we agreed to watch after Easter” — expressed as a rule and re-evaluated every morning. Some are watchlists with actions attached; some are just cohorts.

Membership is recomputed on a schedule, so the list is never older than this morning
Watchlists (rules with actions attached) and plain cohorts in one register, marked as which
Archive a rule when its year ends without losing the record that it existed
Evaluate one on demand when something has changed and you cannot wait until tomorrow
The stat row carries the number that matters most: how many were evaluated today
2

Writing one

Conditions joined with AND and OR, over the fields the platform actually holds: attendance percentage, behaviour points, discipline incidents, core-subject average, risk band, year group, pupil premium, EAL, SEN status. The rule in this walkthrough is two clauses — and it is two clauses from two different modules, which is the entire point.

Fields drawn from every module the school runs, not from a fixed list of three
Comparisons a person would use: below, above, equals, is one of, is true
AND / OR between clauses, so “low attendance AND falling marks” is different from “either”
Mark it a watchlist to attach actions, or leave it a plain cohort
Auto-refresh on or off — some lists should freeze, most should not
3

The rule, who is on it, and what happens automatically

One watchlist opened: the two conditions, the nine pupils currently inside them with the date each joined, and the five things the school has decided happen without anybody remembering to do them. The dates are the useful part — a pupil who joined this morning and one who has been on the list since February are two different conversations.

Members with their join dates, and the ones who have left again — a rule nobody can leave is a rule nobody trusts
Actions on join: tell the form tutor, raise it for Monday’s pastoral meeting, enrol in the literacy intervention
An action on leave, too, so a successful intervention gets closed rather than quietly forgotten
A scheduled attendance letter to the guardians — held for a human to approve before it sends
When each action last fired, which is how you find the one that silently stopped working

Set this up for your team.

Every screen in “A list that maintains itself” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 4 · Form teacher

The person who will actually have the conversation

None of this is worth anything if it stays in the office. The form tutor is the one who sees this child every morning, and the action attached to the watchlist means they were told on the day she crossed the line — not in a half-term review after the damage was done.

1

Their class, with the pupils who need them marked

A form tutor’s own roll, with attendance, results and behaviour standing for each pupil. They see their class and no other — a teaching workspace is scoped to the classes the role grants, which is what makes it safe to put this much on one screen.

The home class roll with each pupil’s current standing
Attendance and results in the same view as the pastoral picture
Scoped to their own class by the role, not by a filter they could widen
The starting point for the daily register, the broadsheet and the psychomotor report
2

One pupil, from the tutor’s own module

The behaviour record of a single child, opened from the tutor’s own workspace: what was awarded, what was deducted, by whom, and why. Same view the school’s Behaviour module shows the office — bound to an endpoint that refuses a pupil this teacher does not teach.

Every award and deduction with its reason and the member of staff who made it
The net position and how it has moved across the term
Positive points shown as prominently as negative ones — the picture is rarely uniformly bad
A pupil outside this teacher’s roster is refused by the server, not hidden by the page

Ready to run your school on this?

Every screen in “The person who will actually have the conversation” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 5 · School office

And here is the screen no stack of systems can produce

This is the end of the argument. Everything above has been about noticing; this is about understanding, and it is the one screen that is impossible without a shared record. Not a dashboard — a sequence.

1

One child’s whole record, in the order it happened

Admission, class moves, results, attendance milestones, behaviour points, a clinic visit, an unpaid invoice, a pastoral note, and the morning she joined the watchlist — one column, in date order, drawn from every module that touched her. Read top to bottom it tells a story that no single register on its own would ever have shown anybody.

Events from academics, attendance, behaviour, health, finance, the library and the school office, on one thread
Each entry says which module produced it, so anything on it can be opened where it lives
Filter by kind when the whole record is too much and only one strand is wanted
Nothing here was entered for this screen — every row is a by-product of ordinary work in another module
Which is the honest version of “integrated”: not an import, not a nightly sync, just one record with many authors
2

And whether any of it is working

The last question, and the one schools are rarely able to answer: is the intervention doing anything? Enrolment, attendance and punctuality across the whole school, so a pastoral programme can be judged on the cohort rather than on the two cases everybody remembers.

Attendance and punctuality trends across the school and by year group
Enrolment and demographic breakdowns behind them
Drawn from the same registers the risk board reads, so the chart and the board can never disagree
Arranged and read like every other module’s reporting, because it is the same reporting

See this on your own school’s data.

Every screen in “And here is the screen no stack of systems can produce” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Run your whole school on one connected platform

Start with the base package, switch on the modules you need, and give every parent, student and staff member a single place to log in.