Walkthrough

Running a Group of Schools

A head office above the schools: every campus side by side, a school opened only on the record, one standard set once and applied everywhere, one wallet that tops each school up, and colleagues who move campus without a new account.

School AdminGroup Owner
Running a Group of Schools

The second school is not twice the first one

One school is run by people who are in it. A group is run by people who are in none of them, and every conversation that used to happen in a corridor becomes a question about consent, access, standards and money. This walkthrough follows those questions from head office into a member school and back: how a school joins, what head office may see and do inside it, how one standard reaches every campus, who pays, and what happens when a teacher moves across the group. Every screen is the real application.

On this page
Step 1 · The school’s side

A school joins by saying yes

A group cannot claim a school. Head office invites a school by its short code, or hands it a join code, and the school answers from its own settings. The same page tells the school exactly what it is agreeing to, and it is where the school leaves again.

1

Organisation, from the school

The group the school belongs to, the platform’s own statement of what head office can see (figures and standing, never a register of pupils or staff), the sister schools by name, and the leave button. A school with an invitation waiting accepts or declines it here.

Accept or decline an invitation, or join with a code head office issued.
The visibility statement is the platform’s; head office cannot edit it.
Leaving detaches every group standard into the school’s own settings and ends any funding.
A school cannot leave while a colleague or pupil is part way through moving; the move finishes or is cancelled first.

Ready to run your school on this?

Every screen in “A school joins by saying yes” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 2 · Head office

Every school, side by side

Signed in at head office. The estate is the reason a group exists: the same headline figures for every member school on one page, taken from a nightly snapshot rather than by reaching into fifty schools at once, and sorted so the schools that need a look come first.

1

The estate

Pupils, staff, attendance today, credit runway and open attention items for every school, with the exceptions called out on the row: a short runway, stale figures, setup blocking a module. The schools with exceptions sort to the top.

Filter by standing, region, funding mode, template status, or exceptions only.
Every figure carries the date of its snapshot.
Refresh one school on demand, once an hour.
2

One school, from head office

Open a row and the summary is everything head office may know about that school: its figures, where its open items sit by module, the group standards it is bound to and where it stands on each, how it is funded, its named office holders, and who from head office has been inside.

Standards: each template, its mode, and whether the school is current, behind or overridden.
Funding: self-funded or funded by the group, the target runway and this month’s allocation.
No named pupil or member of staff appears anywhere on this page.

See this on your own school’s data.

Every screen in “Every school, side by side” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 3 · Opening a school

Inside a school, on the record

Nobody at head office gets a login at every school. A member opens a school from the estate with the reach their group role carries, for at most eight hours, and a banner inside the school says whose session it is. Every action lands in the school’s own trail with the group named beside it.

1

The entry log

Every session a head office member has opened: who, which school, with what reach, when it ended and how many actions it took. This is the page a proprietor shows a principal who asks who looked.

Sessions end on their own, on “Back to group”, or the moment the school leaves.
A finance director’s reach is finance; an executive’s is the whole school.
The school sees the same sessions in its activity feed.

Set this up for your team.

Every screen in “Inside a school, on the record” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 4 · One standard

Set once, applied everywhere

A grading scale, a calendar, fee categories, branding: head office writes the standard once, publishes it as a version, and binds each school in one of three modes. Locked schools take it and cannot change it; default schools start from it and may override; suggested schools see it and decide.

1

Bind the schools

One row per member school, with its mode, the version it runs and whether it is current. A locked row can leave named sections to the school, and escalating a school from default to locked gives it seven days’ notice first.

Locked, default or suggested, per school.
A school already on default is told at once and locked a week later.
The group never writes a school’s tables; each school’s own service applies the version.
2

Where it applied

Every application of every version, per school: applied, deferred to the next term, skipped, or failed with the school’s own reason. Nothing silently half-applies.

Term-anchored standards wait for each school’s own next term.
A failure names the reason and holds that school, not the others.

Ready to run your school on this?

Every screen in “Set once, applied everywhere” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 5 · The school’s side of a standard

Managed by the group

Back inside the school. A governed page says who governs it. Locked means read-only with the group named; default means the school’s own page with a note of where it started and what it has changed.

1

A locked page

The chip names the group, the template, the version and when it applies, and every write on the page is off. A request that arrives anyway is refused with the group named.

The school changes a locked standard by asking head office.
Sections left to the school stay editable and say so.
2

Adopting a new version

On a default or suggested binding the school stays in charge: it sees its settings beside the group’s, field by field, and adopts or dismisses the version. A dismissed version comes back when the group publishes the next one.

Adopt applies it through the school’s own service.
Dismissing quiets the reminder until the next version.

See this on your own school’s data.

Every screen in “Managed by the group” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 6 · One wallet

Head office pays for the schools it chooses

The group has its own prepaid wallet. Head office tops it up once and funds any member school from it: by hand, or with a policy that keeps a school’s runway at a target every night, within a monthly cap. Each school still pays its own daily charges from its own wallet, so its statement and its standing work exactly as before.

1

Who is funded

One row per member school: self-funded or funded by the group, the target runway, the monthly cap, what has gone out this month, and the school’s runway now.

A school in another currency cannot be funded, and the row says why.
A school that leaves returns to self-funded; what was sent stays with it.
2

A funding policy

Keep this school at fourteen days of runway, never more than a set amount a month. The sweep runs each night and tops the school up by exactly what its burn needs.

A shortfall is recorded and raised to head office with the school and the amount.
A school runs on its own wallet as before; the policy only decides when the group adds to it.
3

Every allocation

Each movement from the group wallet into a school, by policy or by hand, with the matching entry in the school’s own statement, which reads “From” the group.

Both wallets move in one transaction.
The group fee itself is per member school per month, charged to the group wallet a day at a time.

Set this up for your team.

Every screen in “Head office pays for the schools it chooses” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 7 · A colleague moves campus

One account, two employments

A teacher needed at a sister school does not resign and reapply. Head office proposes the move with a date; the receiving school accepts; on that date the teacher’s employment at the old school closes and a new one opens at the new school, on the same account, with both on their professional record.

1

Propose the move

From school, colleague, to school, date. Only active staff with a completed account can move, and anything they still hold from the old school’s store holds the move until it comes back.

The receiving school chooses the department and title.
A move accepted on or after its date completes at once.
Pupils move the same way: the old school releases the record, the new one places the pupil in a class.

Ready to run your school on this?

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

Step 8 · The school they join

Accepted where they will work

The receiving school does its part from its own HR pages, under its own permissions. It is the school that says yes.

1

Accept a colleague

Choose where they sit and, if it changes, their title. They sign in with the password they already have and land in their new school; nobody sends them an invitation.

The old school’s record closes the day before the move, not deleted.
Their professional record shows both employments, each asserted by its school.

See this on your own school’s data.

Every screen in “Accepted where they will work” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.

Step 9 · The final say

Above a threshold, head office decides

A group can set an amount for purchases and for requests for funds. The school still decides first, in its own register, with its own offices; a request it approves above that amount then waits for head office instead of issuing its memo.

1

Awaiting head office

The benches for the new laboratory were approved here by the Principal, but they cost more than the group’s threshold, so the request stays pending with the group named beside it. No memo is issued until head office approves.

The school’s own decision is recorded as “approved here”.
Head office approves or refuses inside the school, on the record.
A school that leaves the group gets its waiting requests back to decide itself.

Set this up for your team.

Every screen in “Above a threshold, head office decides” 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.