What you will learn
- How bed inventory and availability are managed across a shelter
- What intake needs to be fast, kind, and safe
- How stays, services, and case notes are tracked per resident
- What exit planning and housing referrals need
- How shelter data feeds funders and coordinators without exposing residents
What the project is
A shelter has beds of different types: dormitory beds, family rooms, accessible beds, and sometimes pet-friendly spaces. Residents arrive through referrals, walk-ins, or crisis calls, often at night, often distressed. Intake records who they are, what they need, any safety or medical considerations, and assigns a bed. During the stay, staff record services, case meetings, and incidents, and work with the resident toward an exit: housing, family reunification, or a longer-term program.
The intake moment defines the system. A long, bureaucratic intake at 11pm, for a person who has just lost their housing, is a failure of design, whatever the database behind it. The working systems capture the minimum needed for safety and a bed assignment at arrival, and complete the fuller assessment the next day, when the resident is rested and staff have time. That two-stage intake is a dignity decision as much as a workflow decision.
Core features
Two-stage intake is the feature. A shelter system that demands a full assessment before a bed is assigned will be hated by staff and harmful to residents.
- Bed inventory with types, accessibility, and availability, updated as residents check in and out.
- Fast intake: minimum safe data at arrival, bed assignment, and a fuller assessment the next day.
- Resident records with stay history, services received, case notes, and safety flags, access-controlled by role.
- Stay management: curfews, chores, and house rules tracked fairly, with warnings and incidents recorded consistently.
- Service tracking: meals, laundry, showers, medical referrals, and case meetings, per resident and in aggregate.
- Exit planning: housing referrals, move-out dates, and follow-up tasks, so a departure is a step forward, not a disappearance.
- Reporting: occupancy, length of stay, exits to housing, and funder reports, with resident privacy protected in aggregates.
How it is built
Build the intake and bed assignment flow with shelter staff, at night, not in a workshop. A shelter system designed for daytime office use will fail at the hour shelters actually fill.
- Shelter study: map beds, intake routes, and the resident journey from arrival to exit, and learn what staff currently record and where it breaks down.
- Bed and intake build: bed inventory, fast intake, and bed assignment, tested with staff on simulated night arrivals.
- Stay and service tools: resident records, service tracking, and case notes, tested during real stays.
- Exit planning: housing referrals and follow-up tasks, connected to the case management picture where one exists.
- Reporting: occupancy, stay, and exit reports validated against a past reporting period before funder use.
Tech considerations
The technical priorities are speed at intake, access control for sensitive resident data, and a bed calendar that cannot double-book.
- Bed availability logic that prevents double-booking, including holds for expected arrivals.
- Fast intake forms with minimal required fields at arrival and a fuller assessment deferred to the next day.
- Role-based access with sensitive flags, such as safety information, restricted to named roles.
- Offline-tolerant check-in for shelters with poor connectivity, with sync when connectivity returns.
- Reporting with aggregation and privacy controls, so funder reports never expose individual residents.
Challenges to plan for
Shelter systems fail on intake burden, bed conflicts, and exit data that never gets recorded. Each failure lands on a resident, not on a spreadsheet.
- Intake burden: a long intake delays a bed for a person in crisis, and staff will bypass the system to get them inside, losing the record.
- Bed conflicts: a bed assigned twice creates a confrontation at night, when staffing is thinnest.
- Exit invisibility: a resident who leaves without an exit record disappears from outcomes, and the shelter cannot show its housing results.
- Safety information handling: safety flags that are too broadly visible endanger residents, and flags that are too narrowly visible leave night staff uninformed.
Who it is for, and honest limits
This fits emergency shelters, family shelters, youth shelters, and shelter networks. It fits less well for a tiny shelter with a handful of beds and one staff member, where a whiteboard and a logbook may honestly be enough.
It does not house people or fund beds. It makes shelter operation visible, safe, and reportable, and connects residents to exit paths. If bed supply is far below demand, the system will show the waiting list plainly, which is the evidence for more capacity.
Frequently asked questions
How fast can intake be?
Minutes for the arrival stage: identity, immediate needs, safety considerations, and bed assignment. The fuller assessment happens the next day. A system that cannot check someone in within minutes at night is not fit for shelter use.
How are safety concerns handled?
Safety flags are recorded with restricted access, so only staff who need them see them, and night staff always see the flags relevant to their shift. Safety information handling should be agreed with safeguarding staff before launch.
Can families stay together?
Family rooms and bed grouping support families staying together, subject to the shelter's configuration and safety rules. The bed inventory should model family units, not just individual beds, where family shelter is offered.
What happens when a resident leaves?
An exit record captures the destination, such as housing, family, or another program, and any follow-up tasks. Exits to housing are the headline outcome for most shelters, and they depend on exit records being completed, not assumed.
How is resident privacy protected?
Through role-based access, restricted safety flags, and aggregated reporting. Individual resident data should never appear in funder or public reports, and access to resident records should be logged.