We fund technology only where it serves a clearly stated need and can be maintained after the grant. These are the questions we will ask, so you can answer them before you apply.
Key points
- Justify the technology against the simplest alternative.
- Design for the lowest-specification device and the weakest connection.
- Plan for maintenance, moderation and shutdown from the outset.
- Accessibility and safety are build requirements, not later additions.
Necessity
Answer plainly why software is the right response here.
- What problem does the tool solve that a process change would not?
- Does an existing open tool already do this?
- Who asked for it, and were they involved in designing it?
Access and accessibility
Assume older devices, intermittent connectivity, limited data allowances and shared handsets. Meet recognised accessibility standards, and test with people who use assistive technology.
- Works on low-specification phones and offline where possible.
- Screen-reader compatible, keyboard navigable, sufficient contrast.
- Available in the languages of the intended users.
Data governance
Collect the minimum, store it in a defined jurisdiction, encrypt it in transit and at rest, and define retention and deletion. State who can access records and how that access is logged.
Safety and moderation
Any tool that connects people needs a reporting route, a named responder, and an escalation path to statutory services. Budget the human time this requires.
Maintenance and exit
Software has running costs forever. Tell us the hosting, security patching and support cost per year, who owns the code and the data, the licence, and what happens to users if the project closes.