The double-entry trap
A school office already runs on paper: the attendance register, the fee receipt book, the admission file. When new software arrives without replacing any of that, somebody has to enter everything twice, once in the register because that is what the correspondent trusts, and once in the software because that is what was bought. The person doing the second entry is usually the class teacher or the fee accountant, squeezed in after the actual work of the day is done.
Double entry does not fail loudly. It fails by adding a small, permanent tax on everybody's time until the software becomes the thing that gets skipped when the day runs long, and the register quietly becomes the record again.
Attendance that counts the wrong list
A class of forty children has, on an ordinary day, two or three absentees. Software that asks a teacher to tap every present child's name is asking for thirty-eight taps to record the two names that actually mattered. Software that asks only for the absentees is asking for two. That difference decides whether attendance gets taken from the classroom in the time it takes to look up and down the rows, or gets postponed to the staff room at lunch, where it competes with everything else a teacher is behind on.
It is not a small usability detail. It is the difference between a habit a teacher keeps and one they resent. What each role actually does day to day starts from this: attendance defaults to present, and marking is only ever the exception.
Marks grids that surface a typo at report-card time
Marks entry in most systems is a plain number field. Type 45 into a field with a maximum of 20, the mark for an FA1 under a Telangana State pattern, and the field accepts it without comment, because it does not know any better. Nobody notices until report cards are being generated weeks later, when a subject teacher's single mistyped mark either breaks the print run or, worse, prints wrong on a document a parent keeps.
Fixing it then means finding the original mark sheet, tracking down the teacher, and reprinting a card that may already have gone out to the section. The cost of a typo should be paid the moment it is typed, by the person who typed it, not weeks later by whoever is running report cards under a printing deadline.
Report cards that do not look like the school's
A report card is not an internal document. It goes home, it gets kept, and a correspondent has opinions about the logo placement that predate the software by a decade. When a system ships one fixed template, the school's actual format gets recreated separately in Word or Excel just before results, so the official mark sheet and the printed report card can drift apart, and somebody has to reconcile the two by eye.
That workaround costs time twice over: once to rebuild the document parents actually see, and again to check that the two versions still agree before a correspondent signs off on either of them. A format the system cannot reproduce is a format the school ends up maintaining by hand, forever, alongside the software that was supposed to remove that work.
Onboarding that hands teachers a data-entry job
A common rollout pattern hands a school an empty system and a login, and leaves the staff to type in years of admission records, fee history and student data on top of their actual jobs. Teachers did not ask for a data-entry project; they asked for something to replace the register. Software that starts by adding work, before it has removed any, loses the argument for itself before a single class has been marked present in it.
This is also where adoption gets decided, well before anyone judges the attendance screen or the marks grid on its own terms. A teacher's first weeks with a new system set how much benefit of the doubt it gets afterwards, and a data-entry backlog is a poor first impression to hand anyone who is already busy running a classroom.
The retreat to paper once one term goes wrong
It usually only takes one incident: a mark that printed wrong, an exam scheme set up incorrectly two weeks before results, a report-card run that failed the night before distribution. After that, staff stop trusting the system for anything that matters and go back to the register just for this one term. That term rarely ends, because nobody wants to be the person who reintroduces the software after it embarrassed the school in front of parents.
The failure itself is rarely the expensive part. What is expensive is the trust it burns, because a class teacher who has been caught out once by a wrong mark or a botched report card will keep a paper backup quietly for years afterwards, whether or not anyone ever asks them to.
What a design that survives looks like
Default present, not default nothing
Attendance for a class teacher starts from everybody present. Marking is only ever the absentees, and it is built to be finished from a phone in well under a minute per section. A principal can see which sections have not taken attendance yet today, rather than finding out at the end of the week.
A grid that refuses the impossible mark
Marks entry behaves like a spreadsheet, but it refuses a mark typed above the maximum at the moment it is typed, and names the child and the part it belongs to. The subject teacher corrects it there, before it is anyone else's problem, and can save partway through a section and come back to finish it.
We put the data in, not the school
Admission numbers, attendance history and fee records come from our team during onboarding, not from a teacher typing after hours. Every class teacher then checks their own section against a printed list, line by line, because they are the only person who will notice a name is missing. The same approach sits behind moving a school off paper registers without losing a name.
A full term with the registers still in charge
A school runs both the registers and the new system side by side for a full term. The registers stay the authority for that term. The switch happens at a term boundary, once a full term has reconciled clean, never in the middle of one, because that is when trust actually gets tested.
A report card in the school's own format
The school's actual report card format, its logo, its layout, is built during onboarding. It comes out as a PDF and prints for a whole section in one action, so there is nothing to recreate separately in Word the week before results.
What Ecole does not do, and why that is deliberate
Ecole has no offline mode. It needs an internet connection, full stop. On a phone with mobile data, a power cut at the office does not stop a teacher from marking attendance, but nothing is recorded without a connection of some kind. We would rather say that plainly than ship a sync that quietly loses a day of attendance the one time it fails, which is the failure mode an offline mode is actually prone to.
Ecole is staff-only for now. There is no parent or student app and no messages to parents in this version; that is planned later, as a paid add-on, not fitted in now as a half-feature a school discovers does not quite work. Saying no to a feature is sometimes the more honest answer than shipping it early, and the same honesty applies to how access to your own data is logged and time-limited.
A checklist for your next ERP demo
Every claim in a sales demo is testable in the room, if you ask for it directly. A correspondent or principal can run through this list on any vendor's own laptop, not just ours.
- Ask them to type a mark above the maximum, live, in the demo. Watch what happens and when.
- Ask whether attendance defaults to present or to nothing, and count the taps for a class of forty.
- Ask to see your own school's report card format rendered, not a sample from another school.
- Ask who enters your historical admission and fee data: you, or them.
- Ask what happens to a wrong fee entry: can it be edited, or only reversed and recorded again.
- Ask whether receipt numbers can ever skip, and what happens when two accountants take money at once.
- Ask what happens if the internet goes down mid-class, and listen for the honest answer, not the hopeful one.
- Ask how CBSE and Telangana State grading are set up, and whether you can change a weightage yourself.
- Ask for a written answer on price, on the same call, rather than a promise to follow up.
- Ask who has access to your data today, and how you would find out if that changed.