How the Educare project put Kozhikode's government schools on one system

In 2019 the Kozhikode District Panchayat set out to fix a gap it could see in its own schools: parents were not being told what was happening with their children. The Educare project, run with Edumia, put the region's government schools onto one school management system — records, examinations, attendance and reporting in one place, with a separate login for every parent. It started as a pilot in six schools and was later extended to 122.

That is the short version. What follows is the working detail: the problems the schools had before, what was actually installed, and what the district reported afterwards. Every figure below is taken from the account Edumia published of the project at the time. Nothing has been added that the project did not itself state.

The problem was transparency, not teaching

The schools in the cluster were not failing at instruction. They were failing at keeping everyone on the same page. Parents, teachers, students and school management were not working from the same information, and parents regularly missed updates about their own children. A parent notices that kind of gap long before they see an exam result.

Underneath the visibility problem were three operational ones, as the project itself described them:

• Examinations and the reporting that followed were tedious to manage, even in schools that already had the option of conducting them online.
• Co-ordinating several government schools under one administration was the biggest hurdle the governing bodies faced.
• Recording school data and then tracking it consumed time in every department, because the same information was being written down more than once.

Read those three together and the shape of the fix becomes clear. If reporting is the bottleneck, the answer is not a faster set of registers. It is a system in which reporting is a by-product of work the staff have already done.

What Edumia actually installed

Edumia implemented a school management system into the schools' existing setup. In practice that meant one application doing three jobs: a learning and knowledge platform for students, an admission and administration system for the school office, and an information platform for parents.

Two pieces were specific to this project. A virtual classroom was integrated into the platform, and light board technology was used to bring Physics, Chemistry, Social Science, Biology and English to students. Mr. Babu Parasseri unveiled the virtual class functionality, and it brought more attention to the app.

Examinations sat inside the same system rather than beside it, which is what let the office stop rebuilding exam records by hand.

The day-to-day working was deliberately ordinary, and that was the point. Each student received a unique student ID, and parents were notified when their child was registered. Attendance was recorded quickly by the teacher, with room for a remark, and the attendance report was then shared with parents and reachable by them. Parents had their own login to follow their child's progress and take part in it.

• The platform was accessible at any time, from any device.
• The app and software could be customised to each school's preferences.
• Teachers could upload notes and learning resources, and students could download them and study at their own pace.
• Student and school information sat in the platform alongside different reports.
• Parents could contact the admin staff and teachers directly, from home.

The messaging side matters more than it sounds. Because every message was recorded rather than spoken, the school ended up with a log it could return to instead of a memory of a phone call.

How the office's work changed

The clearest way to see the change is department by department. Before, each desk kept its own version of the same facts — a register here, a book of enquiries there, an examination sheet somewhere else. The same child appeared in several of them, written by different hands, and the numbers only agreed once someone sat down to reconcile them.

After the move, the child is entered once and read everywhere. The office does not retype a name to print a report, and a parent does not have to ask the office to confirm something the office already knows. That is what the project means when it says departments stopped repeating work: the work did not become easier, it stopped being done twice.

The second change is what happens to the paper trail. A record that lives only on paper cannot be summarised, and a school that cannot summarise its own data discovers problems at the end of the year, when nothing can be done about them. Once attendance, examinations and reporting share a system, the summary exists while there is still time to act on it.

How the parent experience changed

For a parent in Kozhikode, the visible change was that the school stopped being a place they heard from once a term. They had a login. They could see their child's attendance and remarks, follow progress, and message the office or a teacher without making a trip to the school.

That is worth being precise about, because "engagement" is an easy word to overuse. What the platform gave a parent was not a stream of notifications. It was the ability to answer their own question — how is my child doing — without asking the school and waiting for a reply.

What the district reported afterwards

The project's own account lists the outcomes. Parents became well informed about their child's progress, and the communication gap between school and home closed. Syllabus and study material became available to students online. Data storage became more secure, reporting more accurate, and departments stopped repeating the same work by hand.

It also claims a first: at the time, these were the first government schools in India to run on this kind of infrastructure. Attendance across the schools in Kozhikode rose, a discipline module helped hold standards, and teachers grew more comfortable with technology by using it every day rather than being trained on it once.

The account adds that paper use fell and departmental productivity rose. Both follow from the same cause: information entered once and read wherever it is needed, instead of copied by hand between desks. A school that stops copying is a school that has given its staff back the hours that copying used to take.

Why the pilot-then-expand sequence matters

The project did not begin with 122 schools. It began with six, and it grew because the first six worked. That order is not incidental. A government cluster under one administration has to prove the system on a small number of schools before committing the rest, because a rollout that fails across a whole district is far harder to undo than one that fails in a pilot.

For the schools themselves, the pilot was also a form of training. Staff in the first six learned the system while the stakes were low, and those habits travelled with the rollout. By the time the remaining schools came on, the questions they asked were about their own data, not about how to use the software.

What it takes to repeat this

The work that made this project possible is unglamorous, and it happens before anyone logs in. A school has to define its own structure in the system first: the school profile that appears on every printed document, the academic year and the terms inside it, the classes and sections, the subjects and streams, the grade bands and pass mark, and the holiday calendar that attendance and timetabling then respect.

Get that right and every other module reports against it. Get it wrong and every module inherits the mistake. This is the whole argument for deciding a school's structure once, in one place, rather than differently in each department. It is also why a rollout that starts small and grows is usually the one that lasts.

Why one system, and not several

A school in this position has a choice. It can buy a separate tool for each problem — one for attendance, one for examinations, one for messages home — and hope the tools will agree with each other. Or it can put the child record at the centre and let every other function read from it.

The Kozhikode project took the second route, and the reason is easy to miss until something goes wrong. When attendance, examination marks and parent messages live in separate places, the same child has three partial stories and no single one. Reconciling them is a job nobody was hired to do, so it happens late or not at all.

When they share one system, the reconciliation stops being a task. A teacher marking attendance is not feeding a spreadsheet; they are updating the record the report will later read from. That is the difference the districts felt, and it is why the project talks about departments rather than features. The unit of change was the school's working day, not a button on a screen.

The award, and the client's own words

Educare received the Kerala Government's best education project award for 2017–18.

We are very happy with Edumia; very serious and consistent in their work. Fawaz and his team have always been there for us all the time. This is a company I can recommend to anyone.

Mr. Babu Parasseri, President, Kozhikode District Panchayat (2015–2020)