The neighbourhood response network that stopped waiting for permission
Sarah's group was spread across three WhatsApp chats, two Facebook groups, and a spreadsheet. When the flooding hit, she couldn't reach half her volunteers in time. This is the story of how a 200-member neighbourhood network rebuilt itself on ETC — and what happened next.
A community that was already doing the work
Sarah had been running a neighbourhood response network for three years before she found ETC. The network existed because it had to — a combination of local incidents, a council that was slow to respond, and a community that had decided to look after itself.
The network was real and it worked, after a fashion. But it was held together with string. Three WhatsApp groups that overlapped in membership but not in purpose. A Facebook group for announcements that not everyone trusted to keep their personal details private. A second Facebook group for a subgroup that had split off over a disagreement about tone. A shared Google spreadsheet of contacts and rota assignments that nobody could agree on who should update. And email — always email — for anything sensitive.
The flooding happened on a Tuesday in November. It wasn't catastrophic — four properties affected, one elderly resident who needed help getting out — but it was the kind of situation the network existed to handle. Sarah tried to reach her volunteers. She posted in the WhatsApp groups. She sent the email. Half her volunteers didn't see the messages in time because they'd muted the groups months ago after one too many false alarms.
"That was the moment I thought: this isn't good enough," Sarah said. "If this had been something serious, we would have failed."
Finding something built for this kind of community
Sarah had looked at other platforms. Most were built for businesses, not community networks. They had the wrong assumptions — about who was in charge, about how decisions got made, about what "security" meant for a group that sometimes needed to discuss sensitive incidents involving identifiable individuals.
ETC was different in one specific way that mattered immediately: the vouch system. Every member traces their place in the network back through a chain of personal vouches. In a neighbourhood response context, that matters enormously — you need to know that the man or woman you're sharing an incident report with is who they say they are, and that someone you trust has personally vouched for them.
"In our old setup, anyone could join the Facebook group. We had members we didn't know. We had members who turned out to be related to the men and women we were reporting on. That's a serious problem when you're documenting incidents." The vouch system made that structurally impossible.
One platform. Everything in one place.
The migration took six weeks. Sarah vouched in her core team first — the eight men and women who had been running the network since the beginning. Each of them vouched in the next layer, and so on. The vouch chain meant that by the time the 200th member joined, every single member of the network had been personally vouched for by someone who knew them.
The WhatsApp groups were retired. The Facebook groups were archived. The spreadsheet was replaced by the community map and the scheduling tools. And the email threads — the sensitive ones, the incident reports, the legal correspondence — moved into Community Action case files, encrypted and access-controlled.
The emergency alert zones were the first thing Sarah set up. She created three zones — the full neighbourhood, a smaller inner zone covering the most active area, and a zone for the street with the most elderly residents. Members opted into the zones relevant to them. When the next incident happened — a suspicious vehicle that had been parked outside three different homes on consecutive nights — Sarah sent a local alert in under two minutes. Forty-three members saw it within ten minutes.
"The difference was immediate. In the old system I would have been copying and pasting into three groups, waiting to see who'd seen it. Now I sent one alert and it reached everyone who needed to know, and only them."
Documentation that actually held up
The Community Action tools changed how the network documented incidents. Previously, incident reports lived in email inboxes or (worse) in text message threads. There was no consistent format, no way to link related incidents, and no audit trail that would be persuasive to a council or a solicitor.
Over the four months following their move to ETC, the network documented 23 incidents using the structured case file system. Each report included: timestamped description, location (pinned on the map), photographs where relevant, witness statements from members who had seen the same thing, and a categorisation that linked related incidents into a single case thread.
When they presented the documented pattern of antisocial behaviour to the local council, the council's response was different to previous approaches. "They couldn't dismiss it," Sarah said. "Every incident was timestamped, every witness statement was signed, and the geographic pattern was visible on the map. We looked like we knew what we were doing — because we did."
When we had an incident at the school, our response group had already coordinated and had men and women in place before the police arrived. All of it was documented in real time. The case file was built before the evening was over.— Sarah, neighbourhood response coordinator
What changed — concretely
What this network runs on
Encrypted messaging, emergency alerts & case files
Community Action case files, emergency alert zones, the community map, governance, volunteering and secure storage — all composed on one membership. Modular pricing means you switch on only what your community needs, starting from £4/month.
Other communities using ETC
Ready to build something like this?
The closed beta is live now. Back the build to become a numbered founding member, or join the waitlist. See what membership includes.