Every school monitoring programme depends on data that teachers and principals enter. Most programmes ask for that data first and offer something back later. We think the order should be reversed.
A state or district wants to see every school on one screen. That is a reasonable goal. But the screen is only as good as what arrives on it, and what arrives on it is typed, ticked or spoken by people who already feel buried. Teachers describe themselves as clerks for half the day. Principals spend hours a week on registers, returns and forms. Adding a new portal on top of that is, from their side, one more form.
When the people producing the data see only cost, the data gets filled in late, filled in from memory, or filled in to look right. No dashboard can fix that downstream.
Many monitoring systems are designed from the top: decide what the minister needs to see, then work out who must enter it. Each layer adds a field. The teacher, at the bottom, inherits all of them. The system works on paper and fails in the classroom, and the usual response is to add compliance checks, which adds more fields.
We would argue the design should start at the bottom instead: what does the teacher stop doing on day one?
In EduWatch, the teacher’s screen is built around removing work rather than adding it:
The figures EduWatch states for this are pilot targets, not results: about 18 more minutes of teaching a day for teachers, and principal admin falling from 18 to 6 hours a week, to be measured by an external evaluator. We mention them because they set the right yardstick. A rollout should be judged first on whether it gives time back, not on how many fields are filled.
This is not just kindness to teachers. It is how the top of the system gets usable data. Attendance spoken at the start of a class is more accurate than attendance reconstructed at the end of a week. Meals checked on camera produce a quality score per school without anyone filling a form. When the record is produced as a side effect of doing the job, it is both cheaper and harder to fake.
| Design choice | Data-first rollout | Time-back-first rollout |
|---|---|---|
| What teachers see first | A new portal to fill | A task that disappears |
| Language and format | Forms in one language | Voice-first, in their language |
| During the pilot | Penalties for gaps | No penalties; time handed back first |
| Connectivity | Assumed | Offline first, with SMS and IVR fallbacks |
EduWatch’s 120-day pilot plan covers three districts and about 600 schools, with each phase moving on only when the last is green. Two choices in it are worth copying whatever system you use: no penalties during the pilot, and teacher learning centres set up in the first month, before schools go live. Both say to teachers that the system is there to help them before it is there to watch them.
If you are planning a rollout, we would suggest one simple test before launch:
For the department’s side of the system, see our guide to a school monitoring system for education departments, and for how field officers can use the data well, how to prioritise school inspection visits. Everything else is on the EduWatch guides page.
Because teachers and principals produce the data. If the system only adds work for them, data arrives late or reconstructed, and no dashboard can correct that later.
Attendance is taken by voice, parents of absent learners are told by SMS, learners at risk are flagged each morning, lesson plans work offline and principals’ returns are filed automatically.
No. The figures on the product page, such as 18 more minutes of teaching a day, are pilot targets to be measured by an external evaluator, not results from a live deployment.
See it on your own data. EduWatch — Every school on one screen. Book a 30-minute working session with an engineer.
