HeatSafe Neighbourhood Circles

Inspiration

Heat kills more people than any other weather event. It also kills quietly — no dramatic footage, no breaking news alerts. A 74-year-old in a top-floor apartment dies three days into a heat wave and it gets logged as cardiac arrest. We started looking at what cities actually have in place and found something strange: most of them have cooling centres, emergency plans, and public alert systems. The infrastructure exists. What's missing is the last mile — someone telling Mrs. Patel down the street that the library is open and will drive her there. That's not a technology problem. It's a coordination problem, and it's one that neighbours can solve. That's where HeatSafe came from.

What it does

Four things, working together: Cool Room Partners — libraries, schools, faith centres, community halls — identified in advance as cooling spaces during heat alerts. Most of these places are already willing. Nobody's asked them formally. Buddy Check Circles — volunteers matched with specific high-risk residents, checking in by phone or door knock during alerts. Not a hotline. A person who knows your name. Heat Safety Kits — water, electrolyte packets, multilingual information — distributed before summer to residents already flagged as high-risk. The goal is that no one is scrambling for supplies when it's 40 degrees. Shade Restoration Events — native planting in the blocks with the highest heat exposure. This is the slow work. A tree planted this year provides meaningful shade in five. We think that's worth starting.

How we built it

This was a 3-day hackathon, so we weren't going to ship anything. We tried to be honest about that from the start rather than pretend otherwise. What we actually did: researched where existing heat emergency systems break down (usually at the point where a vulnerable person needs to take action themselves), mapped what assets most neighbourhoods already have, and designed a 90-day pilot that could launch without new infrastructure or major funding. The hardest design question was sequencing. Weeks 1–2 go toward locking in cooling spaces and mapping high-risk residents through local health and community organizations. Weeks 3–4 are volunteer recruitment, training, and kit distribution. Month 2 is a simulation drill and first planting event — find the gaps before they matter. Month 3 is live deployment during actual alerts. We wrote the timeline to be tight on purpose. 90 days is fast enough that momentum doesn't die, slow enough that you can do it properly.

Challenges

We almost built an app. Spent probably four hours going down that road before someone said: the people most at risk during heat waves are often the least likely to have a smartphone, a data plan, or the bandwidth to download something new when they're already struggling. We scrapped it. The trickier ongoing challenge is identification — how do you find high-risk residents without creating a surveillance system or making people feel like they're being flagged as problems? Our answer is to route through organizations that already have trust: local clinics, tenant associations, community health workers. They know who needs checking on. They just haven't had a structure to do it through. We also had to think carefully about how to involve Indigenous knowledge in plant selection without it being performative. Our current answer is: only where genuine relationships exist, only where knowledge holders want to participate, and never as a design checkbox.

What we're proud of

Honestly? That we resisted the urge to make it complicated. There's a version of this project with an app, a dashboard, real-time heat mapping, and a machine learning model predicting vulnerability scores. That version would have looked impressive in a demo and helped fewer people. The version we built can be started by a neighbourhood association with a spreadsheet and a group chat.

What we learned

We came in thinking the gap was physical — not enough cooling centres, not enough shade. That's partly true. But the deeper gap is relational. Cities have spaces. They don't have systems for connecting those spaces to the specific people who need them on a 38-degree Tuesday. The other thing: low-tech isn't the same as low-effort. A volunteer program that actually works requires recruitment, training, retention, and someone whose job it is to hold the whole thing together. We tried to build that into the design rather than assume it would happen on its own.

What's next

A real pilot, ideally before next summer. The immediate next step is a printable organizer guide and volunteer training materials — something a neighbourhood association could pick up and use without us. After that, a train-the-trainer toolkit for other cities. If it runs, we'd want to track: how many high-risk residents got enrolled, how many were actually checked on during alerts, how many volunteers stayed active past the first event (retention is the real number — recruitment is easy), and how much shade canopy was added in priority blocks. Long-term goal is a model that any neighbourhood can adapt annually, updated each year based on what worked.

Built With

  • climate-resilience-planning
  • community-partnership-planning
  • community-systems-design
  • coordination
  • heat-vulnerability-mapping
  • indigenous-land-stewardship-principles
  • multilingual-accessibility-planning
  • native-planting-strategy
  • no-software-stack-or-digital-platform-was-used-because-heatsafe-neighbourhood-circles-was-designed-as-a-non-technical
  • public-health-research
  • service-design
  • volunteer
Share this project:

Updates