The most common failure in digital inclusion work is not delivery. Programmes hit their targets, produce excellent final reports, and are genuinely valued by participants. Then the funding ends and within eighteen months almost nothing remains.
This is a design failure, and it happens at the start rather than at the end.
Design the exit in the first month
Every programme we run has a written sustainability plan agreed before the first cohort starts. It answers:
- who owns this when we leave, by name and role
- what it costs annually to keep running, and who has committed to paying
- which capabilities must exist locally for it to continue
- what will be deliberately stopped, because nothing can all continue
Programmes without these answers are borrowing success from the future.
Devices are the easy part
Hardware distribution is visible, photographable and popular with funders. It is also the least durable component, because devices fail, get lost, become obsolete and need support nobody budgeted for.
If a programme's main deliverable is devices, ask what happens in year three when a third of them are broken. The honest answer is usually that the programme has ended and nobody is responsible.
Better sequencing puts capability and local support structure first, then devices where they genuinely unlock it.
Train the trainers, and pay them
A programme that depends on external facilitators stops when the contract stops. One that develops local facilitators can continue at a fraction of the cost.
This means:
- identifying local facilitators early, from the communities being served
- training them to deliver, not just to attend
- compensating them properly rather than relying on volunteering, which selects for people who can afford to work free
- giving them materials they can use without us present
- building in supervised delivery so quality does not collapse after handover
Volunteer-dependent models look cheap in the budget and fail quietly in year two.
Materials in the language people think in
Training delivered in a second language to people with limited literacy in it produces attendance statistics and very little learning.
Local-language materials cost more to produce and are frequently cut for budget reasons. They are also usually the single highest-return line item in the whole programme, because they determine whether anything is actually learned.
Where full translation is not affordable, at minimum translate the participant-facing materials and the assessment. Facilitator notes can stay in English.
Measure capability, not attendance
Attendance is the easiest thing to count and the least informative. Funders ask for it, so everybody reports it.
Better indicators:
- can the participant complete a defined task unaided, tested before and after
- are they still completing it three and six months later
- has anything changed in their income, time use or access to services
- is the local structure still meeting without external prompting
The three-month follow-up is where most programmes discover the truth. Build it into the budget from the start; it is cheap relative to delivery and it is the only data that shows whether the work mattered.
Budget for the unglamorous parts
Connectivity costs, venue hire, transport refunds for participants, facilitator stipends, replacement equipment, data for follow-up calls, and the local coordinator who keeps everything running — these rarely photograph well and are the first items cut.
They are also what determines whether anyone attends week six.
A useful test: if you removed everything that could not be photographed, would the programme still function? If not, the budget is built for the report rather than for the outcome.
Partner with institutions that will outlive the grant
Programmes anchored to a school, a hospital, a local government department, a cooperative or a faith institution have somewhere to go when the grant ends. Programmes anchored to a project office close when the project office closes.
Choose the anchor partner before designing the intervention, and make sure they have signed up to a specific continuing responsibility rather than general support.
Be honest in the final report
The sector would improve substantially if final reports described what stopped as well as what was achieved.
A report that says "forty of sixty programme components continued at eighteen months, and here is what distinguished those forty" is more useful to the next funder than one that reports only delivery against targets.
We write our close-out reports with a sustainability section that names what did not survive and why. It makes the document less flattering and considerably more credible.
Applying this to your own organisation?
We would rather diagnose your situation than sell you a product. Book a call and we will tell you honestly whether this is worth doing now, later, or not at all.