InvolveServicesSERVICE

Implementation

Live in one term, not one year.

A structured programme with a single project lead, clear school-side tasks and a fixed go-live date.

Because Involve isn't assembled from modules, implementation is configuration rather than integration. There are no vendor hand-offs and no middleware to commission.

01

Discovery

Two weeks of structured sessions with leadership, admin, finance and pastoral leads. We map your current systems, your data, your calendar and the workflows that matter, and agree what "done" looks like in writing.

02

Configuration

Your school structure, year groups, houses, timetable model, permissions and templates are configured to match how you actually work. Sensible defaults from schools like yours mean you start from a working system, not a blank one.

03

Data load and parallel run

Your data is migrated and reconciled, then you run Involve alongside your current system for an agreed period so staff can trust the numbers before the switch.

04

Go-live

A planned cut-over date, usually at a half-term or holiday boundary, with hands-on support on site or online for the first days of live use.

05

Aftercare

Thirty days of hypercare with daily check-ins, then a formal handover to your named support team and a 90-day review against the goals set at discovery.