The launch party is over, the registers are gone, and everyone has moved on. Three months later, nobody can say whether the new software is actually helping — attendance is still marked, fees are still collected, but is anything measurably better? Without a school software implementation review, schools keep paying for systems that are half-used, half-understood, and quietly failing to deliver the value they were bought for.
A post-implementation review is a structured 90-day checkup: a half-day exercise that compares what was promised with what actually happened, listens to the staff who use the system daily, checks the real costs, and produces a short fix list. This guide shows exactly how to run one.
Why Most Schools Skip the Review (And Pay for It)
Schools skip reviews for understandable reasons: launch fatigue, the belief that "it is working because nobody is complaining", and the fear that a review will reveal the investment was a mistake. But silence is not satisfaction. In most schools, two or three staff members quietly work around the system — keeping a parallel Excel sheet, marking attendance on paper first, collecting fees in cash and entering them later — and management never hears about it because the work still gets done. The workaround becomes the real system, and the software becomes an expensive reporting shell.
A review also protects the school's negotiating position. If the vendor promised features that do not work, the 90-day mark is the right time to demand fixes — while the contract is fresh and the vendor is still attentive. Wait a year, and the same complaints become "the way it is". Schedule the review before launch, on the go-live calendar, so it happens whether or not anyone feels like it. Our software implementation timeline recommends scheduling this review as a launch-week task.
The 10 Metrics That Prove Value
Measure these ten numbers at day 90 and compare each with the pre-software baseline. You do not need exact historical data for all of them — honest estimates from the office team are enough to show direction.
1. Attendance completion rate: what percentage of classes have attendance marked digitally by 10am? Target: above 95%. 2. Fee collection timeliness: what percentage of monthly fees arrive by the due date, and how many days earlier than before? 3. Defaulter rate: has the share of overdue accounts fallen? 4. Receipt turnaround: how long does a parent wait for a fee receipt — seconds, or the next day?
5. Report generation time: how long does it take to produce a class-wise fee report or a monthly attendance summary — minutes or days? 6. Parent message delivery: what share of SMS/WhatsApp messages are delivered, and are parents responding faster? 7. Marks entry completion: are results finalised days earlier than in the paper era? 8. Login activity: how many staff log in daily, and which modules are actually used? 9. Error rate: how many corrections, re-issued receipts, or re-printed report cards per month? 10. Help requests: how many support tickets or internal "how do I..." questions per week — and are they falling?
If eight of ten metrics moved in the right direction, the system is working and the fix list can focus on the two laggards. If fewer than five moved, something structural is wrong — usually training, not technology. For the full measurement framework, see our guide on measuring digital ROI.
Staff Feedback: What the Numbers Miss
Numbers show what happened; staff tell you why. Run a short, anonymous feedback round — a one-page form or a 20-minute group conversation per department — with four questions: What does the system make easier? What does it make harder? What do you still do on paper or in Excel, and why? What one change would help you most?
Listen for specific patterns. "The fee module is fine but the attendance app is slow on my phone" is a solvable technical issue. "I enter marks in Excel because the marks screen is confusing" is a training and usability issue. "I keep a paper register because I do not trust the system" is a data-quality and trust issue — and the most serious one, because it means the school now runs two systems and trusts neither. Take every workaround seriously: each one is a staff member telling you where the system fails them. The review meeting should include the department champions who helped during training, because they know which complaints are real and which are resistance to change.
Review Principle
The Honest Cost Check
The review must confront the money. List the full annual cost: subscription, any per-student fees, SMS/WhatsApp charges, hardware, training time, and vendor support. Then list the savings: staff hours freed (convert to salary cost), reduced printing and register purchases, faster fee collection (earlier cash improves the school's position), and fewer errors that previously cost money — re-issued receipts, written-off disputed fees, late board registrations.
Be honest about the gaps. If the school still pays for SMS bundles it no longer uses, cancel them. If a module was bought but never used — say, transport tracking for a school with no buses — either deploy it or stop paying for it at renewal. Many schools discover at review time that they are paying for features nobody switched on. Our guide to software switching costs and hidden costs helps frame this conversation before renewal.
From Findings to a Fix List
A review without a fix list is just a complaint session. End the review by producing a one-page action list with five columns: issue, owner, action, deadline, and how success will be checked. Cap it at ten items and rank them by impact. Typical fix lists include: retrain one department on the module they avoid, clean a specific dataset (duplicate guardians, missing phone numbers), switch on one unused feature, request two vendor fixes, and cancel one unused cost.
Then schedule the next check. A light 30-minute review at day 180, and a full review at the one-year renewal point, keep the system honest. Software value is not delivered at launch — it is delivered by the steady cycle of measuring, listening, and fixing. The schools that review are the schools whose systems still feel new in year three; the schools that do not are the ones shopping for replacement software in year two.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app. It can help you turn your review findings into a clean one-page action list — issues, owners, and deadlines — and draft the staff feedback questions in plain Urdu and English so every teacher can answer honestly.
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.