Getting your preschool off spreadsheets and WhatsApp groups

Almost every preschool in India runs on some combination of an Excel fee sheet, a paper attendance register and a WhatsApp group per class. This is usually described by software companies as a problem. It is not — it is a reasonable system that costs nothing, that everyone already knows how to use, and that has carried a great many schools a long way.

It is worth being honest about that before talking about replacing it, because the real question is not whether spreadsheets are bad. It is whether yours have reached the point where they cost more than they save.

The break rarely announces itself. It shows up as a handful of recurring symptoms, and if several of these are familiar you are probably past the point:

• Nobody is certain what is owed. The fee sheet and the receipt book disagree, and settling which is right takes an afternoon.
• The register exists in two places. A paper roll call in the classroom and a typed-up version, which drift apart by the end of a month.
• Something important is lost in a WhatsApp group. A parent’s message about a medication change, scrolled past during a busy morning.
• One person is the system. When your office administrator takes leave, nobody else can answer a fee query, because the working knowledge is in their head and their filenames.
• A second branch doubles the work rather than sharing it. Two sets of everything, reconciled by hand into a third.
• A parent asks a question you cannot answer quickly. “What did my child eat on Tuesday?” or “Can you delete our photos?”

The instinct is to move everything at once, over a holiday. That mostly produces a half-finished migration and a staff room that has lost confidence in the new system. Move one thing, get it genuinely working, then move the next.

Start with fees. It is the area where errors cost real money, where the current pain is sharpest, and where the benefit is visible to the person who signs off the purchase within a single billing cycle. It is also the cleanest to migrate, because a fee ledger is structured data already.

Then attendance. It is a small daily habit rather than a big change, and it is what makes daily reports possible later.

Then parent communication. Leave this until staff are comfortable, and expect it to be the one parents notice. Moving off WhatsApp groups is a change for families, not just for you, and it needs to be announced rather than sprung.

Curriculum records, progress cards and transport can wait for the second term. Nothing breaks if they do.

For a single-branch preschool with a reasonably tidy spreadsheet, moving the student list and fee structure is roughly a day of work — most of it spent on the things a spreadsheet let you be vague about.

• Duplicates and near-duplicates. The same child entered twice with two spellings. Every school has these and nobody knows until the import complains.
• Inconsistent columns. Dates entered five different ways; a fee column that is a number for some rows and text with a rupee sign for others.
• Children who left but were never removed.
• Fee structures that only exist in someone’s head — the sibling discount that gets applied by memory, the family paying a special rate agreed three years ago.

None of this is difficult, but it is the actual work, and it is worth doing before the import rather than discovering it afterwards. A good vendor will do this cleanup with you rather than handing you a template and wishing you luck.

The most common reason these projects fail has nothing to do with software. Teachers quietly keep the paper register because it is faster, and within a month you are running both systems — which is worse than either.

Three things that help:

• Pick a hard switch-over date for each thing you move, and retire the old version on that date. Running both “for a while” means running both forever.
• Make the new way faster than the old way for the person doing it. If marking attendance on a phone takes longer than a tick on paper, the paper wins and it should.
• Train on their actual data. A demo with sample children does not stick; a teacher marking their own class on Monday morning does.

If you run a fifteen-child playgroup with one teacher and a tidy spreadsheet, you may genuinely not need any of this yet, and we would rather say so than sell you something that adds a login to a problem you do not have.

Where it starts to pay is around the point where more than one person needs the same information, or where a second branch appears, or where compliance requires you to produce records rather than remember them. If you are there, a short demo using your own fee sheet is the fastest way to find out whether it would help — and our pricing page will tell you what it would cost before you speak to anyone.