Buying a parent app is a procurement decision. Getting eight hundred parents to actually open it is a completely different kind of problem, and it is the one that decides whether the investment was worth anything. Here is what we have watched succeed and fail across a lot of rollouts.
The mistake almost everyone makes first
The standard launch is a circular in the school bag: we have a new app, please download it, here is the link. A few parents do. Most read it, mean to, and never do. Three weeks later adoption is at a fifth of the school and the office concludes that the parents are not interested.
The parents are perfectly interested. The circular just asked them to do unpaid administrative work for a benefit they cannot yet see. Nothing in it answered the only question they actually had, which was what does this get me?
Put something in it before you announce it
The single most effective thing we have seen: do not launch an empty app. For a fortnight before you tell parents it exists, have teachers use it internally — post the notices, set the homework, mark the attendance, upload the holiday list.
Then when a parent logs in for the first time, they land on two weeks of their own child’s real information rather than an empty screen with a welcome message. The difference in what happens next is not subtle.
Give one thing that only exists in the app
If everything on the app also goes home on paper and in the WhatsApp group, the app is strictly extra work and parents are right to ignore it. Something has to be exclusive to it, and it has to be something they want.
The ones that reliably work:
- Attendance notifications. A parent finding out at 9:20 a.m. that their child was marked absent is a genuinely new capability. Nothing drives installs faster.
- Marks, as soon as they are published. Not the printed report card three weeks later — the subject marks as the teacher finalises them.
- Homework with due dates. Particularly for younger classes, where the alternative is interpreting a diary entry written by a seven-year-old.
- Fee dues and receipts. Parents dislike unclear fee position more than they dislike fees.
Catch them when they are already in the building
Do not rely on parents installing an app at home. They are at your school several times a term, and that is when it takes ninety seconds instead of never.
What works: a table at the parent-teacher meeting with two staff, a printed sheet of credentials per class, and someone who installs it on the phone in front of them and watches them open it once. Schools that do this at a PTM routinely go from a fifth of parents to most of the school in a single afternoon.
The corollary: schedule your launch to land just before a PTM or an admission-season event. Launching in the second week of the session, when nobody is coming in, wastes the momentum.
Assume one phone, and assume it is shared
A meaningful share of families have one smartphone between them, often the father’s and often at work during school hours. Some parents read comfortably in English, some do not. Some will never install anything and will always want paper.
This is not a problem to be solved, it is a constraint to design around:
- Support more than one parent login per student, so both parents can have it.
- Keep SMS running in parallel for the things that genuinely matter — emergency closures, fee deadlines. SMS reaches a feature phone; an app does not.
- Never make the app the only route to something a family needs. A parent without a smartphone should not end up with a child at a disadvantage.
Teachers decide this, not parents
Here is the part institutions consistently underestimate. Parent adoption is downstream of teacher adoption. If teachers post notices and homework reliably, the app is useful and parents stay. If half the teachers post and half do not, parents learn that it cannot be trusted, and they go back to asking their child.
Which means the rollout that matters is the staff one. Train teachers before parents hear about it. Make sure entering homework from a phone genuinely takes under a minute — if it does not, they will stop, whatever the circular from the office says. And have someone senior look at the posting rate by class in the first month, while it is still fixable.
Then stop printing
Once the posting rate is steady and most families are on it, stop sending the paper version of what is now in the app. Not everything, and not all at once — but the routine circular that duplicates a notice on the app should go.
Two reasons. First, the printing and distribution cost was part of the case for buying the app, and it is not saved until you stop. Second, as long as paper is the reliable channel, the app remains optional — and optional things get ignored.
Keep paper for the genuinely important and for the families who need it. Everything else can move.
A realistic timeline
- Weeks 1–2: teachers only. Posting, attendance, marks. No parent hears about it.
- Week 3: announce to parents, ideally at a PTM with an install desk. Expect a large jump on the day and little after it.
- Weeks 4–8: chase the classes with low posting rates, not the parents with low installs. Catch stragglers at the next event.
- From week 8: start withdrawing the paper duplicates.
A term is a realistic horizon for an app being simply how the school communicates. Any vendor promising it in a fortnight has not done it in a real school.