A developer can add sites faster than it can add experienced operators. The consequences appear in ordinary work: an unresolved alarm, a repeat journey for a missing part, a report waiting for reconciliation. The practical question is how much of that work the existing team can absorb before service suffers.
DARES makes that question urgent. The World Bank approved $750 million for a programme intended to improve electricity access for 17.5 million people through mini-grids and standalone solar. Those are programme-wide beneficiaries, not mini-grid connections. The REA programme target includes up to 1,350 isolated mini-grids. It is a deployment target, not a count of operating sites.
This article is for a developer planning the team behind its next group of sites. Start with the work that must be done, then decide what to hire, train, outsource or automate.
What the workforce figures tell us
Reporting on NAPTIN's assessment describes a shortage of half the skilled workforce needed across Nigeria's power sector. That is a warning about the wider talent pool. It is not a measured vacancy rate for mini-grid technicians or a staffing ratio for your fleet.
The same distinction matters for renewable-energy employment. The IRENA/ILO Annual Review 2025 reports roughly 344,000 African renewable-energy jobs against 16.6 million globally in 2024: about 2.1%, rather than the 3% stated in an earlier version of this article. These jobs span technologies and occupations; they cannot all be counted as available maintenance staff.
Training initiatives such as NextGen RESCO's 130-person cohort contribute to supply. One cohort does not establish national training capacity, and it cannot tell a developer how many experienced staff it can recruit in a particular state. Hiring plans need local evidence: qualifications, availability, supervision needs and retention.
Count work, not just sites
Two fleets with twenty sites can need very different teams. Travel distance, equipment diversity, site condition and customer support all matter. Separate the responsibilities before assigning headcount.
| Workstream | What to count | Who owns the result |
|---|---|---|
| Remote operations | Alarm reviews, escalation, shift coverage | Operations lead |
| Field maintenance | Planned visits, incidents, travel and repeat visits | Maintenance lead |
| Metering and customer support | Meter faults, payment investigations, community issues | Customer operations |
| Evidence and reporting | Reconciliation, review, submissions and follow-up | Compliance or finance lead |
| Parts and contractors | Stock checks, procurement, dispatch and acceptance | Maintenance or procurement lead |
A shared fleet view may reduce time spent opening portals. It does not remove the need for electrical competence, local access, spares or someone accountable for accepting a repair.
A staffing worksheet for the next twelve months
Use actual work-order and timesheet data where available. Mark estimates explicitly and replace them as the fleet operates.
| Input | Your planning value |
|---|---|
| Sites active each month | Commissioning schedule, including ramp-up |
| Routine visits per site | Equipment maintenance plan |
| Incidents per site per month | Observed rate, with a range for new sites |
| Hours per visit | Travel, diagnosis, repair and documentation |
| Repeat-visit rate | Share of incidents needing another journey |
| Remote and reporting hours | Measured separately from field hours |
| Productive hours per person | After leave, training, administration and standby |
For an illustrative fleet of twenty sites, assume one routine visit per site each month taking six hours including travel: 120 field hours. Assume 0.25 incidents per site per month, each taking eight hours for the first visit: another 40 hours. If 40% need one additional eight-hour visit, add 16 hours. Total: 176 field hours per month.
At an assumed 110 productive field hours per technician, this is 1.6 technician-equivalents of workload. It is not permission to staff the fleet with two people: simultaneous faults, specialist tasks, safe working arrangements, leave and response commitments can require more coverage. Remote operations and reporting are additional work.
If the repeat-visit assumption falls from 40% to 20%, the model saves eight hours a month. That is a useful improvement, but it is not a tripling of the workforce. A transparent calculation tells you which constraint is worth addressing.
Where software helps, and where it cannot
Give the team one prioritised work queue with site identity, symptoms, equipment history, an assigned owner and an escalation deadline. Link the task to parts availability and capture what the technician actually found. Measure whether this reduces missed faults and repeat visits.
For a fleet using several equipment portals, integration can save reconciliation effort. Keep the original source and its limitations visible. A missing signal should remain missing; an attractive fleet average must not hide a silent site.
The commercial reason is straightforward. Under the REA mini-grid grant structure, consumption evidence is part of the claim process. Plan reporting against the current award terms and the site's assigned amount. Faster report preparation can help the team meet its obligations; it cannot guarantee payment or replace the verifier's decision.
Before commissioning the next group of sites
Run the worksheet with a normal month and a difficult month. Assign responsibility for every workstream. Confirm contractor availability, travel assumptions and critical spares. Then agree which indicators will trigger another hire or a change in coverage: unresolved critical faults, repeat visits, overdue maintenance and reporting backlog.
Financing programmes expand what developers can build; they do not remove every financing constraint or provide an operating team. The useful question at the next expansion meeting is: which workload rises first, and who will own it?
For a closer look at preparing each field visit, read The Technician Bottleneck.
Editorial note
Revised 4 September 2026. Corrected the employment percentage, separated programme targets from operating counts, and replaced unsupported national staffing conclusions with an explicit planning example. The worksheet is illustrative, not a measured Gen318 productivity result.