Ask any school that has launched new software and they will tell you the same thing: the software was fine — the launch was the problem. Parents could not log in, fee receipts printed with the wrong session year, teachers marked attendance in the old register because nobody told them to stop, and the office discovered on fee day that half the guardian phone numbers were missing. Every one of these disasters is a school software go live checklist item that was skipped.
This checklist covers the 25 checks that matter, grouped into data, training and access, communication, and fallback plans. Work through it in the final two weeks before launch, and go-live week becomes a calm, controlled switch rather than a crisis.
Why Go-Live Week Goes Wrong
Go-live failures share one root cause: the school treats launch day as the start of the project, when it should be the end of it. By launch day, data should already be verified, staff should already be trained, parents should already know what is changing, and someone should already own every decision. A checklist forces that discipline. Print this list, assign an owner to each item, and do not declare the school ready until every box is ticked — with evidence, not assumptions.
Timing matters too. Never go live on fee-collection day, exam week, or the first day of a new session. Choose a quiet week, ideally mid-month, and launch one module first — usually attendance or fee receipts — before switching on everything. A phased launch contains problems; a big-bang launch multiplies them. Our software implementation timeline shows how the weeks before launch should be sequenced.
Data Checks (1-8)
1. Student records complete: every active student has a full name (as on B-form), date of birth, class, section, guardian name, and guardian mobile number. Export the list and check for blanks. 2. No duplicate records: run the duplicate check on B-form numbers and phone numbers. 3. Fee plans assigned: every student is linked to the correct fee plan, concession, and transport charge — spot-check ten students per class against the old register.
4. Opening balances correct: any arrears carried into the new system match the old ledger to the rupee. Reconcile one class fully before trusting the rest. 5. Staff records loaded: every teacher and staff member has a login, correct designation, and correct class assignments. 6. Timetable and sections match reality: the sections in the system are the sections that actually meet — including any mid-session section splits. 7. Fee structure verified: generate a sample fee bill for one student in each class and compare it with last month's bill line by line. 8. Backup taken: a full export or backup of both the old records and the new system exists before launch day, and someone has confirmed it can be restored. If your data needs cleaning first, follow our data migration guide before importing anything.
Training & Access Checks (9-15)
9. Every role has a login: principal, office staff, teachers, accountant, and transport in-charge each have accounts with the right permissions — and nobody is sharing a login. 10. Role permissions tested: a teacher account cannot see payroll; an accountant account cannot edit marks. Test this by logging in as each role. 11. Core staff trained on their daily tasks: each person can perform their own five most common tasks without help — marking attendance, issuing a receipt, entering marks, printing a report.
12. Urdu-language help available: quick guides or videos in the language staff actually read — usually Roman Urdu or Urdu — for the tasks they will do most. 13. One champion per department: each department has a named "super user" who can help colleagues and escalate problems. 14. Vendor support contacts saved: the support number, email, and escalation path are printed and posted in the office, not buried in someone's inbox. 15. Test transactions done: at least one full cycle — attendance, a fee receipt, a marks entry, a parent SMS — has been completed in the live system and verified end to end.
Training is the most commonly under-scoped item. Our guide to training non-technical staff covers how to run it without losing teaching days.
Parent & Staff Communication (16-20)
16. Parents informed in advance: a letter or WhatsApp message — in Urdu and English — explaining what is changing, what parents need to do, and where to get help. 17. Parent logins or numbers verified: if parents will use an app or portal, their registered mobile numbers are correct and they have received test messages. 18. Payment instructions published: if fee payment changes, parents receive step-by-step instructions with screenshots at least a week before the first online collection.
19. Staff briefing held: a full staff meeting where the principal explains what changes, what stays the same, and that the old registers stop on a specific date. 20. Notice board and diary updated: the school's physical notice board and student diaries carry the same message as the digital channels, so no parent hears about the change second-hand. Change communication is a discipline of its own — see our change management guide.
Launch-Day Rule
Fallback Plans & Launch-Day Command (21-25)
21. Fallback plan written: if the system is unavailable on launch day, staff know exactly what to do — paper attendance sheets, manual receipts, and how those records will be entered later. A fallback plan is not pessimism; it is professionalism. 22. Old system available in read-only mode: keep the old registers or spreadsheets accessible for one month after launch, read-only, so any disputed figure can be checked.
23. Launch-day command: one person — usually the office in-charge — owns launch-day decisions, with the principal as backup. Everyone knows who to call, and problems are logged in one list, not shouted across corridors. 24. First-week review scheduled: a 30-minute review meeting is already on the calendar for day five, to clear the issue log and decide what needs vendor support. 25. Success criteria agreed: the school has written down what "go-live success" means — for example, 95% attendance marked digitally, all fee receipts issued from the system, zero unresolved parent complaints by Friday. Without criteria, every launch feels like a failure.
Run this checklist honestly and your launch will still have surprises — but they will be small ones, handled calmly, instead of a week of chaos. After launch, the work continues: see our guide to measuring digital ROI for the 90-day checkup that makes the investment pay off.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app. It can help you turn this checklist into a one-page launch-day sheet for your school — with owners and deadlines filled in for your team — and draft the parent announcement message in clear Urdu and English.
Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code.
Disclosure: LTGSWD is the author's Muse invite code.