It currently supports two of the more substantial state programmes in the South East — Enugu Smart Green Schools and Anambra Smart Schools — alongside deployments across private and mission school networks.
What state-scale actually requires
A platform that works in one well-run private school in Lekki is not thereby ready for 260 schools across a state’s wards. The difference is not licensing. It is four things that determine whether the programme survives its second year.
1. Working where the infrastructure does not
The schools that most need the intervention are the ones with the least reliable power and connectivity. A system that requires both continuously will produce excellent data from urban schools and nothing from rural ones — which then produces state-level analysis that is systematically biased toward the schools that were already doing better.
Edves is built to hold work through interruption and sync afterwards, with SMS and voice as primary channels rather than fallbacks. This is a design constraint from the beginning rather than a rural adaptation added later.
2. Teacher capability, not just teacher training
Most state technology programmes budget for devices and for a training workshop. Very few budget for the eighteen months afterwards, which is when adoption is actually won or lost.
A teacher who attended a two-day workshop in September and has had no support since has not been trained; they have been informed. Continuous, job-embedded support — short observations, coaching prompts, help at the moment of use — is what converts a rollout into practice. See teacher development.
3. Data that ministries can act on
The point of state deployment is not that schools have software. It is that a commissioner can see, for the first time, enrolment by ward updated continuously, teacher deployment against actual need, which schools are losing pupils, and where learning outcomes diverge — without waiting for an annual census assembled upward from paper. See NEMIS and EMIS reporting.
4. Surviving a change of administration
This is the one nobody puts in the tender document and the one that ends most state education technology programmes. A programme identified entirely with one administration is at risk the moment that administration changes.
What protects a programme is that the data belongs to the state rather than the vendor, that civil service staff rather than political appointees hold the operational knowledge, and that the system is producing returns the ministry needs regardless of who is in office. Edves contracts on state data ownership with full export at any time, which is the minimum condition for that.
What a state deployment covers
| Layer | Detail |
|---|---|
| School operations | Enrolment, records, attendance, timetabling, results, terminal reports |
| Teaching | NERDC-aligned lesson planning, scheme of work coverage, instructional models |
| Assessment | Continuous assessment and CBT comparable across schools on the same basis |
| Teacher development | Observation, coaching, CPD records supporting TRCN renewal |
| Family engagement | SMS, voice and app contact with parents, in local languages |
| Ministry reporting | Enrolment, staffing, infrastructure, attendance, outcomes by school, ward and LGA |
| Out-of-school outreach | SMS micro-learning and radio-supported lessons for learners outside the system |
Measuring whether it worked
State education technology programmes are frequently evaluated on outputs — schools equipped, teachers trained, devices distributed — because those are countable and available quickly. They say almost nothing about whether learning changed.
The measures worth committing to at the outset, because they are much harder to introduce later:
- A genuine baseline. Learning outcomes measured before deployment, on the same instrument that will be used afterwards. Programmes that skip this can never demonstrate their effect and usually resort to asserting it.
- Comparison schools. Phased rollout gives a comparison group for free. Simultaneous rollout gives none.
- Usage, not just access. Whether teachers actually plan lessons in the system, weekly, six months in.
- Retention and attendance, which respond faster than attainment and are therefore an earlier signal.
- Attainment at ward level, disaggregated by sex, so equity effects are visible rather than averaged away.
Edves supports this measurement, and will say plainly where a programme’s design does not permit a defensible claim. A state that wants to demonstrate impact should build the evaluation into the procurement rather than commissioning it afterwards.
Out-of-school children
Nigeria carries one of the largest out-of-school populations in the world, though widely cited figures differ substantially depending on source, definition and methodology — estimates in circulation range from around ten million to well over eighteen million. States should work from their own verified data rather than a national headline figure, and be careful about which number a programme is designed around.
What technology can do here is narrower than it is often sold as. It cannot address the reasons children are out of school, which are economic, security-related and social. It can support SMS-based micro-learning and radio-supported lessons for learners outside the system, track reintegration where community programmes bring children back, and identify enrolled children whose attendance pattern predicts they are about to leave — which is the most tractable of the three.
Current programmes
- Enugu Smart Green Schools — ward-level school construction with an integrated digital learning platform.
- Anambra Smart Schools — smart classroom deployment across local government areas.
Programme scope, school counts and status change as rollouts progress. Confirm current figures with the relevant state ministry of education rather than with any vendor, including this one.
Procurement
For ministries preparing a tender, the evaluation criteria most likely to distinguish real capability from a good presentation are: demonstrated operation under intermittent power and connectivity; curriculum mapping depth; a costed teacher support model extending beyond initial training; state data ownership with unconditional export; and a named implementation team rather than subcontractors. See choosing school software.