Scope
The pressure point, the people it involves, the systems it touches and the exceptions that actually matter. We would rather map one process properly than tour eleven modules. Ends with a written scope you can take to your governors.
Implementation and support
Live in weeks, planned
around your school calendar.
This page is the plan: what we do, what we need from you, and how long each part takes, so your team knows exactly what a switch looks like before committing to one.
The first rule
Start with one thing, then compound
Pick the pressure point that costs you most, land it properly, then extend. The platform is designed for exactly that path, our pricing is built around it, and every module you add makes the previous ones work harder.
Timing
September is a go-live date,
September is a go-live date,
not a start date.
A module with no hardware in it is usually a matter of weeks: connect to your data, configure the roles and rules, test it against your real cases, train the people who will use it daily, and launch. Anything touching your building is different, because it starts with a survey and ends with a commissioned handover, and a fire panel interface involves your own fire alarm contractor.
The practical consequence is that a September launch implies a spring decision, and a hardware installation implies a survey before you commit to anything. We would rather tell you that in February than in July.
The five stagesWhat happens,
What happens,
in order.
Each stage ends in something you can look at, rather than in a status update.
Connect
Your instance is created, connected to your MIS data route, and populated with your real people, groups, rooms and codes. Ends with you logging in and recognising your own school rather than a demo one.
Configure
Roles and permissions, your categories, your thresholds, your booking rules, your leave types, your letters. This is where a platform either fits your school or fights it, and it is the stage we spend the most time on.
Rehearse
Run your real scenarios, including the awkward ones: the concern that has to be restricted, the trip that gets rejected, the drill. Train the people who will use it daily, which is usually fewer people than you expect. Ends with a launch decision you make, not one we announce.
Live, then review
We stay close for the first weeks, then review what is actually being used and what is being avoided. Something being avoided is information, not failure. Extending to the next module happens when you want it, not on a schedule.
Division of labour
What we do.
What we do.
What we ask of you.
We do: create and configure your instance, connect and validate the data, build your rules and letters with you, run the scenario testing, train your teams, survey and commission any hardware, and stay on the end of the phone through launch.
What we ask of you: decide who holds which permissions, agree the categories and thresholds that reflect your policies, give us a data protection contact, provide someone who can answer “how does your school actually do this?”, and put a couple of hours of the right people’s time into the rehearsal stage. That last one is the single biggest predictor of a smooth launch.
Nobody needs to become an administrator of the system to use it, and we do not expect a school to have spare technical capacity. A platform that touches safeguarding, money and doors is configured with your team, around your policies, which is precisely why it fits your school on day one rather than resembling a generic install.
One named person on our side, throughout
Configuration decisions stay yours
No launch in the first fortnight of term
Support
You will not be routed to a queue
Support goes to the people who build and run the platform. Response commitments, hours and escalation are written into your agreement rather than described in adjectives on a website, and we would rather you held us to a contract than to a promise.
CommercialsAnnual or three-year.
Annual or three-year.
Priced around your scope.
Annual
Establish the platform, review priorities each year. Suits a school taking one or two modules first and wanting to keep its options open.
Three-year
Suits a phased rollout, a hardware programme, or a trust standardising across schools, where the plan spans more than one budget year.
Why there is no price list
A price per pupil for a platform this modular would either overcharge the school taking two modules or undercharge the trust taking twelve with hardware. We quote against the scope agreed at stage one, and the proposal shows what each part costs so you can remove any of it.
See your rollout plan before you sign anything.
Tell us the module and the term you want it live, and we will map the stages onto your actual calendar dates. Bring the person who would run it day to day; the plan is for them.
Book a scoping conversation ↗