What you will learn
- How a shelter registry is built and kept current during a disaster
- What live capacity means, and how it is updated honestly
- What evacuees need to know: accessibility, pets, medical, and supplies
- How routing and transport information are presented
- How shelter data feeds the wider disaster coordination picture
What the project is
A shelter is a facility opened during a disaster: a school, a hall, a sports centre, staffed and stocked to receive evacuees. The finder holds a registry of potential shelters, with their capacity, accessibility, pet policy, medical facilities, and supplies. During a disaster, open shelters report their current occupancy, and the finder shows evacuees the open shelters near them, with capacity, facilities, and directions, updated as the situation changes.
Capacity honesty is the central problem. A shelter that reports space it does not have sends evacuees to a closed door; a shelter that under-reports leaves beds empty while another site overflows. The finder therefore needs a simple, fast capacity update path for shelter staff, ideally a single number updated regularly, and it must show when each shelter's capacity was last updated, so evacuees can judge whether the number is fresh.
Core features
Fresh capacity data is the feature. A finder with yesterday's capacity is a map of where shelters used to be, not where evacuees should go now.
- Shelter registry with location, capacity, accessibility, pet policy, medical facilities, and supplies per site.
- Live capacity updates from shelter staff, with a timestamp showing when each figure was last updated.
- Evacuee search by location, showing open shelters nearest first, with capacity and facilities filters.
- Routing and transport information: directions, road closures affecting routes, and transport assistance where offered.
- Registration and check-in support for shelter staff, so occupancy is counted from arrivals rather than estimated.
- Special needs flags: medical needs, accessibility, pets, and unaccompanied minors, handled per shelter's capability.
- Coordination integration: shelter status feeding the disaster coordination picture, so resource requests follow capacity.
How it is built
Build the shelter staff update path first, with shelter managers, not the evacuee search. If staff cannot update capacity in seconds, the finder will be stale within hours.
- Registry study: list potential shelters, their capacities, facilities, and activation criteria, with the agencies that run them.
- Staff tools: capacity updates, check-in, and status changes, tested with shelter managers in an exercise.
- Evacuee finder: search, filters, and routing, tested with members of the public on realistic scenarios.
- Coordination integration: shelter status feeding disaster coordination and resource requests.
- Readiness routine: annual registry review and exercise, because shelters change, close, and gain new facilities.
Tech considerations
The technical core is a simple staff update flow and a fast public search. Everything else supports those two.
- Simple capacity update tools for shelter staff, usable on a phone, with offline tolerance for sites with poor connectivity.
- Public search with location, filters, and routing, designed for stressed users on mobile connections.
- Capacity timestamps on every figure, so evacuees see freshness, not just a number.
- Road closure integration where available, so routes avoid closed roads.
- Role-based access for shelter staff, coordinators, and the public, with audit trails on status changes.
Challenges to plan for
Shelter finders fail on stale capacity and on shelters that open without the finder knowing. Both send evacuees to the wrong place at the worst time.
- Stale capacity: a shelter that stops updating looks available when it is full, and evacuees arrive to a closed door.
- Unregistered shelters: community shelters that open spontaneously will not be in the registry, and evacuees need a path to find them too.
- Transport gaps: an evacuee without a car cannot use directions alone, and transport assistance information must be part of the finder.
- Accessibility mismatches: a shelter listed as accessible that cannot actually receive a wheelchair user creates a second evacuation.
Who it is for, and honest limits
This fits emergency management agencies, local governments, and relief organisations that operate shelters. It fits less well for a single shelter operating alone, where a phone line and a sign at the door may honestly be enough.
It does not open shelters or staff them. It shows evacuees where to go and shows coordinators where capacity remains. If shelter capacity itself is insufficient, the finder will show that plainly, which is the evidence for opening more sites.
Frequently asked questions
How is shelter capacity updated?
By shelter staff, through a simple update tool, ideally from check-in counts. Each figure carries a timestamp, so evacuees can see whether it was updated minutes or hours ago.
What if a shelter is full?
The finder shows it as full and directs evacuees to the nearest open shelter with space. Full shelters should remain visible, so evacuees do not drive to them unknowingly, but clearly marked as full.
Can evacuees with pets find a suitable shelter?
Yes, through a pet policy filter. Pet policies vary by shelter, and the filter should reflect the shelter's actual policy, including any pet areas or restrictions, not a generic assumption.
What about people without transport?
Transport assistance information should be shown where it exists, such as pickup points or shuttle services. Where no transport exists, the finder should say so plainly rather than implying directions alone are sufficient.
How does it handle spontaneous community shelters?
Through a registration path for community shelters to join the registry during a disaster, with verification by coordinators. Unverified shelters should be marked as such, so evacuees can judge the information.