Every school in the group, side by side.
A fifth portal for the organisation above the schools. Form a group, bring schools in with their consent, and see the whole estate’s headline figures on one page — enrolment, staff, attendance, credit runway and what needs attention. Head office members open a school with the reach their role carries, and every visit is on the record.
Built for Proprietors and head office teams running more than one school
What the head office portal does
The same live data as the rest of the school, surfaced for the person looking at it.
The estate on one page
Every member school’s enrolment, staff headcount, attendance today, credit runway and open attention items, refreshed daily and on demand.
Schools join by consent
Invite a school by its short code or issue a join code. A school accepts, declines or leaves from its own settings, and a school never belongs to two groups.
Open a school, on the record
A head office member opens a member school with the reach their group role carries. Every entry is logged, time-boxed and visible to the school.
What needs attention, estate-wide
Stale figures, schools suspended for credit, setup blocking a module and invitations waiting on a reply, in one queue.
A head office team with real roles
Executive, finance, academic, HR, communications and viewer roles, each scoped to every school or to named ones.
One audit trail for the group
Everything done at head office and everything done inside a school by a head office member, in a single register.
One head office, every school in the group
Everything below is the real application, running live on this page with sample data — not screenshots. Start where a group comes from — a proprietor forming it from the school they already run — then follow the estate as schools join, figures land side by side, and a head office member opens a school on the record.
On this page
- Two doors into a head office
- Every school, side by side
- Schools join by consent
- What a member school sees
- Inside a school, on the record
- One wallet funds every campus
- Standards set once, applied everywhere
- Staff and pupils between member schools
- Accept, release, place
- Broadcasts
- The estate compared, and what needs attention
- Roles with a reach
- Approvals that come to head office
- What the school sees while it waits
- Central procurement
- One application for the group
- The admissions pool
- Profile, branding, standing, ownership and the trail
Two doors into a head office
A group has two beginnings. A proprietor who already runs a school on the platform forms it from their own dashboard. Someone who runs none of their schools here yet starts from this site: create an account, name the group, fund its wallet. Either way the person who forms it is its owner of record, and the schools that join keep every record they have.
Name the group
The public way in, for a proprietor who belongs to no school on the platform yet. The short code becomes the group’s handle — the thing a school types to find it — and the billing currency is the currency the group wallet will hold. Neither can change afterwards.
Say how head office is reached
Contact details and a tagline, all optional — but a school weighing an invitation looks for them. Submitting this step is what actually creates the group, and the person who submits it becomes its owner of record.
Fund the wallet to open
A head office opens on a funded wallet. The first top-up is a deposit rather than a bill — it stays in the group wallet and pays the per-school fee later, or goes out to a school as an allocation. The group turns on the moment the payment settles.
Or form it from inside a school
The other door. A proprietor already on the platform forms the group from their own dashboard and is signed in at head office the moment they do — no deposit, because the school is already a paying tenant.
Ready to run your school on this?
Every screen in “Two doors into a head office” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Every school, side by side
Signed in at head office. The estate page is the whole reason a group exists: one row per member school, the same headline figures on every row, refreshed every night and on demand. Nothing here is a register — it is the figures a proprietor asks for on a Monday morning, for every school at once.
The estate at a glance
Enrolment, staff headcount, attendance today, credit runway and open attention items for every school, with the exceptions called out — a runway that is short, figures that are stale, setup blocking a module.
One school, from head office
Open a row and the school’s summary is what head office is allowed to know: its standing, its named contacts, where its attention items sit by module, and who from head office has been inside recently.
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.
Schools join by consent
A group cannot claim a school. It invites one by its short code, or issues a join code the school types in from its own settings — and the school accepts, declines or ignores it. A school belongs to at most one group, and can leave from its own side at any time.
The member schools register
Every school in the group with how it joined: created by head office, accepted an invitation, or joined by code. Currency mismatches are flagged here, because a school billed in a different currency is one the group cannot fund.
Invite a school by short code
Type the short code of a school already on the platform. Its administrators receive the invitation in their own settings and answer it there — head office only sees the reply.
Or issue a join code
For a batch of schools joining at once, a code with a use limit and an expiry. It is shown once, hashed after that, and any school that types it in from its own settings becomes a member.
Invitations, answered and waiting
Every invitation and code the group has issued, with its status. The ones waiting more than three days surface in the attention queue, so a proprietor does not have to remember to chase.
Set this up for your team.
Every screen in “Schools join by consent” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
What a member school sees
Back inside a school for one screen. Its administrators have a page of their own that states exactly what the group can see about them, who from head office has been inside, and the invitations waiting on an answer — with the leave button on the same page.
Organisation, from the school
The group the school belongs to, spelled-out visibility — headline figures yes, registers no — and the count of head office entries currently open. A school that wants out leaves from here, with a reason the group is shown.
Ready to run your school on this?
Every screen in “What a member school sees” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Inside a school, on the record
A head office member does not get a login at every school. They open a member school from the estate, with the reach their group role carries — an executive reads everything and writes settings, a finance director works inside fees — for at most eight hours. The school sees the entry; the group sees every action.
The entry log
Every time a head office member has opened a school: who, which school, with what reach, for how long, and how many actions they took inside. Live sessions sit at the top and can be ended from here.
See this on your own school’s data.
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.
One wallet funds every campus
The group has a wallet of its own. It is topped up once, it pays the group’s own fee, and it funds member schools by allocation: a signed movement out of the group wallet and into a school’s. Each school then pays its own days from its own balance, exactly as a standalone school does. Nothing about per-school charging, statements or enforcement changes.
The group wallet
Balance and health, today’s group fee at the current member count, the combined daily burn of the schools the group funds, and the runway that combination leaves.
Top up the wallet
One amount, one secure checkout. The wallet is credited the moment the payment settles, and any school the sweep left short that morning is funded straight after.
Funding policies
One row per member school: whether the group funds it, to what target runway, within what monthly cap, and what it has had this month. The 00:15 sweep tops each funded school up before its own daily charge runs.
Set a school’s target
Choose the mode, the runway the sweep keeps the school at, and the most the policy may move in a calendar month.
Allocate now
Move credit into one school’s wallet immediately: two ledger entries, one on each wallet, that name each other. Nothing is clawed back later; unspent credit belongs to the school.
Every allocation on the record
Applied, short or refused, with the reason where there is one. A policy that could not fund a school in full records the shortfall, and the estate’s attention queue names the school.
The group ledger
Top-ups, allocations by school, the group fee by day, platform grants and reversals, each with the balance after it. The statement reconciles to the wallet balance whatever the filter shows.
How each school is collecting
Per school for the term: invoiced, collected, outstanding, the collection rate and overdue invoices, from the nightly snapshot. Schools under the group’s own threshold are flagged.
Set this up for your team.
Every screen in “One wallet funds every campus” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Standards set once, applied everywhere
A template is a standard of one kind of school setting — the calendar, the grading scheme, the fee chart, the theme, the document designs, behaviour rules, leave types, who may message whom — authored once at head office, frozen as a version, and bound to member schools in one of three modes. Locked schools take every version and their page goes read-only; default schools take it once and may then edit; suggested schools are only offered it. Whatever the mode, the write goes through the school’s own module, so its validation and its audit trail apply.
The templates register
Every template the group holds: kind, current version, how many schools are bound in each mode, and how many are not on the current version.
A new template
Choose the kind and name it. The draft that follows is the module’s own settings, edited against the template instead of a school.
Draft the standard
The grade scale and the assessment policy, exactly as a school would set them. Nothing reaches a school until it is published.
Publish a version
Notes for the schools and an effective boundary. Grading and fees are term-anchored: they never change mid-term, and each school’s own next term is the boundary.
Every version, frozen
The history of the standard, newest first, with who published it, when, and its boundary. Open a row for the payload as it was.
Bind schools, choose the mode
One row per member school within reach: mode, adopted version, status. Locked applies now and stays read-only at the school; default applies once; suggested waits for the school.
Lock the standard, leave a section to the school
A locked binding can still leave named sections to the school. Here the Lagos campus keeps its own assessment policy while the grade scale stays the group’s.
The application log
Every attempt to write a version into a school, with its outcome: applied, skipped, failed, and the reason where there is one.
Drift
Every binding not on its current version across the estate, with what clears it: apply now, nudge the school, or ask it to re-adopt.
What a locked school sees
The school’s academic-year page with the calendar managed by the group: a chip naming the group, the template and the version, and every write disabled. A request that still arrives is refused with the group named.
Adopting a version
On a default or suggested binding the school stays in charge. The chip says which version it started from and what it has overridden; re-adopting shows the field-level difference first.
Ready to run your school on this?
Every screen in “Standards 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.
Staff and pupils between member schools
A group moves people the way a single school cannot. A colleague keeps one account and one professional record while their employment moves from one school to another on a date both schools agreed; a pupil’s record goes straight from the old school to a class at the new one, with no claim code and no application in between. Head office proposes; each school does its own part.
Staff transfers
Every colleague moving between member schools: waiting for the receiving school, accepted and dated, held by clearance, completed or declined.
Propose a move
Pick the school, the colleague and where they are going, and the date. The receiving school is asked to accept with a department and a title.
Pupil transfers
Every pupil moving between member schools, from the exit at the old school to the class at the new one.
Start a pupil’s move
Choose the school, the pupil and the sister school. A transfer exit opens at the old school at once, so clearance starts the same day.
Families across schools
How many guardians have children in more than one member school, by school and by pair of schools. Counts only; no names leave a school.
See this on your own school’s data.
Every screen in “Staff and pupils between member schools” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Accept, release, place
Each school does its part from its own portal, under its own permissions. The receiving HR office accepts a colleague and chooses where they sit; the sending school releases a pupil’s record once clearance is done; the receiving school places the pupil in a class.
Group transfers in HR
Colleagues joining or leaving this school. Incoming ones wait for an answer; outgoing ones show whether custody is holding them.
Accept a colleague
Choose the department and, if it changes, the job title. On the effective date the colleague signs in as usual and sees this school; nobody is re-invited.
Group transfers in Students
Pupils moving to or from a sister school: releases this school still owes, and released pupils waiting for a class here.
Place a released pupil
Pick the class. The pupil is enrolled from the released record with a new admission number here, and their guardians are attached.
Set this up for your team.
Every screen in “Accept, release, place” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Broadcasts
Head office writes a message once. Each member school publishes it as its own announcement, labelled as from the group, and delivers it through its own channels to its own staff, pupils or parents. Schools cannot reword it; they can take it down.
The broadcasts register
Every broadcast with its audience, channels, how many schools published it, and when it went or is due to go.
Write a broadcast
A title and a message, who should hear it inside each school, which channels, which schools, and when: now, at a set time, or later.
School by school
Each school’s own announcement and how its delivery went: recipients reached, recipients missed, and the reason a school could not publish.
Ready to run your school on this?
Every screen in “Broadcasts” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
The estate compared, and what needs attention
Analytics compare member schools from the nightly snapshots. The same “needs your attention” queue every portal has covers the estate: stale figures, setup blocking a module, credit suspensions, transfers waiting on a school, broadcasts that failed. The activity feed shows what head office did, what schools did in its name, and the school events the group chose to follow.
Estate analytics
Enrolment, collections, attendance, runway, attention and template compliance, school beside school. Arrange the cards; your layout is kept.
The estate’s queue
Counted from the latest snapshots and the invitations register, so a proprietor reads one card instead of every school’s overview.
The activity feed
One feed, newest first: head office actions, writes inside schools made in the group’s name, and school events such as top-ups and exits.
Board exports
The estate’s figures for any period up to 400 days, as a spreadsheet a board analyst can pivot or a PDF with a page per school.
See this on your own school’s data.
Every screen in “The estate compared, and what needs attention” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Roles with a reach
Colleagues join head office by invitation, with a group role that decides two things: what they can do in the group portal, and how far they reach when they open a school. A role can cover every member school or only named ones.
The team register
Everyone with a group role, their reach, and whether they have signed in yet. Roles and reach can be changed from the row; removing someone ends any school they are inside.
Invite a colleague
An email, a role and a reach. The invitation sets the colleague’s password and lands them at head office; an existing account simply gains the group beside its schools.
Roles, the system seven and the group’s own
Every head office role with what it may do here and how far it reaches inside a school, and how many colleagues hold it.
Write a role for the group
Tick the head office actions, choose what the role may do inside a school, and limit the templates it may author. Members holding it change as soon as it is saved.
Set this up for your team.
Every screen in “Roles with a reach” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Approvals that come to head office
Head office sets an amount per approval type. When a school approves a purchase or a funds request above it, the request does not issue its memo; it waits for head office, which approves or refuses it with a reason the school reads.
Set the thresholds
One amount for purchases and one for funds requests, in the group’s currency. Leave a type empty and schools decide it alone.
What is waiting
Every school request approved above the threshold, with who raised it, who approved it at the school, and what it costs.
Decide
Approve and the school’s memo is issued as usual. Refuse and the reason goes to the school and to whoever raised the request.
Ready to run your school on this?
Every screen in “Approvals that come to head office” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
What the school sees while it waits
Back in the school’s own register. The request it approved above the group’s threshold is still pending, marked with the group that has the final say, and no memo goes out until head office decides.
Awaiting head office
Approved here by the Principal, waiting for the group. The school sees who approved it at the school and which group decides next; head office’s decision lands on the same record.
See this on your own school’s data.
Every screen in “What the school sees while it waits” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Central procurement
Head office places one order with one supplier and pays for it. As the goods arrive it sends each school its share, which lands in that school’s inventory as a purchase order already received, with the stock moved and no expense on the school’s books.
The procurement register
Every central order with its total, how much has reached a school’s stock, and how many schools have had a share.
Draft an order
The supplier and a line per item: SKU, name, unit cost and quantity. A school that already stocks the SKU receives into that item.
Lines and deliveries
What was ordered, what has gone out, and each school’s delivery with the purchase order number it carries in that school.
Send a school its share
Choose the school and the quantities. The school’s inventory gets a received order, the stock movement and a notice that head office paid.
Set this up for your team.
Every screen in “Central procurement” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
One application for the group
A family that wants a Brightfield place but not a particular campus applies once, on the group’s own public page, and names up to three schools. There is no account to create.
Apply to the group
The child, the class wanted, the schools in order of preference, and how to reach the guardian. A reference comes back by email.
Ready to run your school on this?
Every screen in “One application for the group” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
The admissions pool
Head office places each pooled child at a member school’s open intake. The school receives an ordinary application with its own applicant number, and its admissions team takes it from there.
Open the form
Switch the public form on, and write the introduction families read first.
The pool
Every family who applied, the class and schools they chose, and where each child was placed.
Place at a school
Pick the school and one of its open intakes and grades. The application appears in that school’s admissions, and the family is told which school has it.
See this on your own school’s data.
Every screen in “The admissions pool” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
Profile, branding, standing, ownership and the trail
The group’s own settings: who it is, how it looks in the switcher and on the schools that belong to it, the thresholds its attention queue uses, who owns it, and the one audit trail that holds everything done at head office and everything done inside a school by a head office member.
Profile
Name, contact details and address. The short code is fixed once schools have used it to join.
Branding
A logo, a colour and a tagline. They appear in the context switcher, on the group’s own pages and as a small mark on each member school’s settings — never in place of the school’s own brand.
Standing and thresholds
The group’s standing with the platform, and the two thresholds the estate uses to call an exception: how few days of runway is too few, and what collection rate is too low.
Who owns the group
The owner of record is whoever formed the group, until they hand the title on. They lead head office: nobody can remove them or change their role, and executives are theirs alone to appoint.
Hand the title on
Only the owner can transfer the group. They pick an active colleague, type their name, give a reason and re-enter their own password; the title moves at once and they stay on as an executive.
The audit trail
Every recorded action in the group’s name — at head office and inside member schools during an entry — in one register, with the sponsor named on rows written inside a school.
Set this up for your team.
Every screen in “Profile, branding, standing, ownership and the trail” is the live product, not a mockup. Create your school account, or have us walk you through it on a call.
The group sees the headlines. The school keeps its records.
A head office reads figures about a school, not its registers. Pupils, grades, invoices and messages stay the school’s own unless a head office member opens that school — and that visit is recorded for both sides.
Read from head office
Enrolment, staff, attendance, runway, standing and open attention items for every member school.
Opened with a reach
A group role carries a school reach. Opening a school grants exactly that, for a few hours, on the record.
Owned by the school
The school sees what the group sees, who has been inside, and can leave the group from its own settings.
No exports. No re-keying. No separate tools.
The head office portal is part of the same connected platform as every other role — so what changes anywhere shows up here, live.
- Headline figures for every school, side by side
- Schools join and leave by consent, never by force
- Entries into a school are time-boxed and logged
- Priced per member school, on the group’s own wallet
Explore the other portals
Every role in your community gets a portal built for them.
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.