In October 2025, reporting on remarks by Nigeria's power minister described more than 400,000 imported electricity meters awaiting installation because of an installer shortage. That is a dated report about grid-side metering, not a verified inventory today or a count of vacancies in mini-grid maintenance.
It nevertheless raises a useful question for mini-grid operators: when qualified technicians are hard to recruit, how much of their time is being lost to work that could have been prepared better?
Training and retention remain essential. The immediate opportunity is to improve the information, parts and access arrangements behind each journey.
One fault, two visits
Consider an illustrative site four hours from the maintenance base. A technician receives a message that the power is out, travels to the site and finds a damaged component. The correct spare is not available. Diagnosis takes two hours; a return trip and a second visit follow.
With four hours of travel each way, the two visits consume sixteen travel hours before counting diagnosis, repair or documentation. Even if the repair is straightforward, most of the technician's time has been spent reaching the equipment.
Better information cannot eliminate every second visit. Some diagnoses need an on-site test, and carrying every possible spare would be expensive. But an equipment list, recent fault history and parts check can distinguish a necessary diagnostic trip from an avoidable unprepared one.
Prepare the work before dispatch
A work order should be useful to the person travelling, including when their phone has no signal. It should separate an observed symptom from a suspected cause.
| Before departure | What to include |
|---|---|
| Identify the asset | Site, location, equipment model, serial number and installation history |
| Describe the symptom | Fault messages, recent trends, time first observed and service impact |
| State uncertainty | Checks completed, candidate causes and what remains unknown |
| Confirm the visit | Site contact, access, authorisation and required competence |
| Prepare equipment | Verified part compatibility, stock availability, tools and test instruments |
| Plan the record | Offline work order, required observations and restoration checks |
A useful example is: “Inverter output has stopped; repeated fault events are attached. Inspect the protection circuit and confirm the cause before replacing equipment.” It is not an unverified error-code interpretation paired with a fictional manufacturer part number.
Route planning also needs local judgement. A map estimate is not confirmation of current road access, safe travel or availability of the person who holds the site key.
Measure the value without promising a workforce multiplier
The previous version suggested one technician could move from 8–12 sites to 20–30. Without workload and travel evidence, those ratios are not a reliable staffing model.
Use visits and hours instead. For an illustrative ten incidents, suppose four need one repeat visit. At eight travel hours per visit, fourteen visits consume 112 travel hours. If preparation reduces repeat visits to two, twelve visits consume 96 travel hours: sixteen hours saved before accounting for the extra preparation work.
That is not a measured outcome. It shows which inputs a pilot must collect. At a nearby site, the saving would be smaller; for faults requiring specialist diagnosis, the repeat visit may remain necessary.
Track first-visit resolution only among jobs eligible to be completed in one visit. Otherwise a team can appear to improve by avoiding difficult work or closing tasks prematurely. Record total resolution time and reopening rates alongside the headline metric.
The visit is not complete when the task is closed
The technician's record should state what was found, what was done, which parts were used and whether the asset was left operating. Attach measurements and photographs where they help someone review the work.
Keep the event time separate from the upload time when records are captured offline. A phone syncing in the evening should not make a morning visit appear to have occurred hours later. Missing location or telemetry evidence should be declared rather than silently filled in.
Someone then needs to accept the outcome. Did service return? Did the original symptom recur? Was the component actually faulty? A closed ticket without that check can conceal repeat work.
These records also make experience reusable. They let a supervisor compare faults across similar equipment and improve future preparation. Better predictions require reviewed outcomes and evaluation; a completed form does not automatically train a reliable model.
Training and preparation reinforce each other
NAPTIN's reported workforce assessment concerns the wider power sector. It supports investment in skills, but cannot establish the number of mini-grid sites one technician should cover. Likewise, a training cohort is only one part of the labour pipeline.
An inexperienced technician with a detailed work order still needs supervision. Software should help match the task to the person's competence and escalate uncertainty, not encourage work outside their training.
For a developer expanding under DARES, the operational plan needs both a staffing model and a field workflow. The fleet staffing worksheet covers the first. This article covers the second.
Start with the last ten repeat visits
Review why each return journey happened: missing information, incompatible parts, unavailable access, incomplete diagnosis or a repair that did not hold. Choose the most frequent avoidable cause and change the dispatch checklist around it.
Then compare a defined set of subsequent jobs. Include preparation time, travel, on-site work and reopened tasks. The useful result is fewer wasted journeys and faster restoration, with the same standard of safe and competent work.
Editorial note
Revised 4 September 2026. Dated the meter-backlog report, removed unsupported productivity ratios and unverified hardware identifiers, and replaced cross-industry analogies with a field preparation checklist and an explicit travel example.
Programme context: the World Bank's DARES announcement and IRENA's Renewable Energy and Jobs review. Neither source supplies a mini-grid technician staffing ratio.