Pilot applications openWe’re listening to early-stage support needs.Start an application →
Apply for support

Community support

Technology shaped with the people who will live with it.

Community support begins with representation, consent, access and local ownership. A platform is only one possible response.

01Potential needs

Access, information and coordination

Possible work includes trusted information services, community directories, referral or support pathways, volunteer coordination, digital inclusion, youth learning, low-bandwidth communication and locally governed data collection.

02Representation

Who has the authority to speak for the need?

Discovery must identify affected groups, excluded voices, existing leaders and decision processes. A single applicant cannot automatically consent on behalf of an entire community.

03Access design

Mobile first does not mean mobile only

A response may need offline materials, assisted access, shared devices, SMS or messaging, accessible language, physical support points and alternatives for people with limited connectivity or literacy.

04Safety

Information can create risk as well as benefit

Location, identity, vulnerability and service-use data will not be made public simply because a platform can display it. Safety, consent, safeguarding and community governance determine what should be collected or shared.

05Sustainability

Every solution needs a local operating home

Before delivery, the project must identify who will manage content, accounts, moderation, support, costs, disputes and future changes. Where no viable owner exists, a lighter non-technical response may be more responsible.