Demo build on sample data

The school handbook, running on its own across every campus

Registers, absence letters, weekly plans, detention, clinic reports, fees and the uniform store, done by the system and approved by staff. Plus an online academy.

This is a demo build. It runs on sample data. We keep the group's name private.

At a glance

Demo build, sample data

Business
Multi-campus K-12 group
What we built
  • A School OS
  • An automations page
  • An online academy
Multi-campus school demo build: the automations page, where each handbook procedure runs as a rule that can be switched off, from absence letters to store reorders.
Handbook automations, school group demo.Demo build, sample data.

The problem

This education group runs several K-12 campuses with English and French tracks. Each campus has a thick handbook: registers, absence letters, detention, clinic visits, weekly plans, fees and the uniform store.

Almost all of it ran on paper and goodwill. Registers came in late. Absence slips got lost. Teachers were chased for weekly plans over group chats. The store's stock never matched the till. Each campus did things a little differently, and the owners had no single view.

The group also wanted to open a fully online school without hiring a second back office.

What we built

A School OS

The handbook's procedures become rules. When a rule fires, the system does the typing, filing and chasing. Anything that leaves the building waits for a person to approve it. A campus picker gives each school its own view, and the owners get a group view.

An automations page

Every rule is listed in plain words, with the handbook section it comes from, and can be switched off.

An online academy

A self-paced high school where students enrol any day, learn at their own pace and earn credit that posts back to the School OS.

What's in it

  • Today: attendance by campus, registers still missing and items waiting for a person.
  • Attendance: mark a student absent and the guardian is told, the daily absence form builds itself, and the parent's reply is filed as an excuse note.
  • Weekly plans: teachers fill them once, missing entries get a nudge, and plans publish to the parent portal on schedule.
  • Gradebook: the school's weightings, academic warnings and parent letters drafted for the principal.
  • Discipline and clinic: an incident log that follows the handbook's steps, detention scheduling, and accident reports written from a one-line note.
  • Gate passes for drop-off and pickup.
  • Admissions, fees and family accounts, with a three-step reminder ladder and receipts.
  • Store and inventory: charges to family accounts, stock-takes, recounts and drafted purchase orders.
  • Online academy: a course catalogue, a weekly study plan built from each student's pace, a transcript that fills itself in, billing, and teacher training that feeds the appraisal file.

What it would take to go live

The handbook, read with the people who use it. We learn where each campus does things differently before we write a single rule.

The group's real systems, connected in place of the sample data.

A first version in about 10 days. Staff approve what goes out, and every message is logged.

The group owns its data, and it stays with the group.

See also industries we serve and workflow automation.

Run more than one campus?

Book a call and we'll show you the demo, from a missing register to an approved letter.