Implementations fail in predictable ways: everything switched on at once, data entered before structure exists, staff trained on screens they will not touch for months. The institutions whose go-lives feel uneventful follow the same order of operations — because the platform mirrors how a school is actually constituted.
Week one: structure before data
A school is a structure before it is a list of students: an academic session, departments, classes, sections, subjects per section. Build this first and every later import lands in its right place; skip it and every import invents its own. On ez.school this is guided setup measured in hours — but the principle holds on any platform: nothing enters the system before the structure that owns it.
Then people, in bulk and validated
- Students: bulk import with the register you already trust, validated before a single row writes — duplicates, missing guardians and malformed dates surface as a report, not as surprises.
- Staff: the employee register with designations and departments — the org chart draws itself.
- Roles: who may do what, decided while the stakes are low. Provisioning a teacher correctly takes minutes; un-provisioning a shared password takes a term.
Policies before habits
Roll-number rules, working-day calendars, shifts, fee structures and concessions: these are decisions the institution has already made on paper. Encode them before daily operations begin, because they are exactly the things staff will otherwise improvise — and improvisations calcify into "how we do it" within weeks.
Go live on ONE function
The calm pattern: pick attendance or fees — high-frequency, low-ceremony — and run it for real while everything else stays on the old routine. Staff build the daily habit on one screen; the office sees live data with stakes everyone can tolerate. Expand function by function from there. Institutions that go live on everything at once are training staff and firefighting simultaneously, and both suffer.
The first month, measured
- Attendance marked by 9am, every section, without chasing — the first sign of habit.
- Zero shared logins in the sign-in log.
- Parents receiving alerts from records, not from a teacher’s personal phone.
- One report — any report — pulled by leadership without asking the office.
When those four hold, the platform has stopped being a project and become infrastructure. That is the finish line of implementation — everything after is operations.