School automation: the order to do it in
Institutions that try to automate everything at once usually end up back on paper. The order matters more than the tooling.
Attendance and fees first, and only those
These two are the daily habit. They are recorded every single day by people who are already at their desks, which means the system gets used often enough for everybody to learn it, and the records they create are what everything else reads.
Resist the temptation to start with the exciting module. A reporting dashboard built on records nobody is entering is an empty dashboard, and an institution that sees an empty dashboard in week two concludes the software does not work.
Then the documents your office retypes
Once students and marks are in the system, the documents come almost free: report cards, admit cards, ID cards, transfer and character certificates, fee receipts. Each of these is currently somebody retyping a name that is already written down somewhere else.
This is the stage where staff stop experiencing the change as extra work. Up to here they have been putting data in; from here the system starts handing things back, and that is when adoption stops needing to be enforced.
Leave the ambitious things until last
Public websites, online admissions, guardian portals and analytics are all worth having. They are also all downstream of clean records, and switching them on early means publishing incomplete data to the people least able to interpret it.
A reasonable pace is one new area per term. It feels slow in a planning meeting and fast by the end of the year, which is the opposite of how a big-bang rollout feels.
Questions people ask
Should we run paper and software in parallel for a while?
For the first month of the register, yes — it is cheap insurance and it settles arguments about whether a day was marked. Beyond that, parallel systems double the work and people quietly abandon one of them, usually the new one.
Who should own the rollout?
Somebody in the office who is there every day, not the most senior person and not the most technical. The rollout succeeds or fails on whether the daily register gets marked, and that needs a person who notices when it has not.
What if our teachers are not comfortable with computers?
Start them on the one screen they need. A class teacher marking a register touches a single page, on a phone browser, once a day. Training that covers the whole system in one session is where most of the discomfort actually comes from.