Field notes
PMS
Playbook
School ERP
A school's first month on an ERP: what to ship, what to wait on
Most school ERP rollouts fail in the first thirty days, not because the software is wrong, but because the team tries to go live on everything at once. Admissions, fees, attendance, timetable, exams, transport, library, payroll, all on day one. Nobody learns anything; everybody hates everything.
Here is the order we ship in. It assumes a 600-1,200 student K-12 school and an office team of three to five.
Week 1: Ship Admissions and Fees only
Get the student master clean. Get the fee structure clean. Send the first fee invoices from the system. That is it. If those two work, parents see a difference in week one and the school owns the data.
Week 2: Add Attendance and Timetable
Once the student master is trustworthy, attendance is a one-day rollout. Timetable can be imported from the existing Excel. Both produce daily wins teachers feel, which buys you political capital for the harder modules.
Week 3: Add the Parent App
Now the parents get notifications for absences, fee dues, and circulars. This is the moment the school stops sending paper notes home. Do not turn this on before fees are correct, angry-parent volume will sink the rollout.
Week 4: Exams and report cards
Save this for last. It is the most opinionated module, grading schemes, weightages, remarks, formats, and the most painful to migrate mid-term. Set it up in week four, dry-run on one class, then roll out at the next exam cycle.
What to wait on
Transport, library, hostel, biometric staff attendance, all of these can wait for term two. Shipping them in month one costs more in support tickets than they save in efficiency.
Related reading
More from the playbook stack.
AI agents
Product