Good Will · Initiative 02 · Product Requirements
Bridge
Coordination infrastructure for the people and facilities that respond to homelessness. Assess a person once. See real-time availability across providers. Carry a consented record through a warm handoff instead of rebuilding it at the next door.
This is a planning document, not a binding commitment. Bridge is being designed with shelter operators in Los Angeles and San Bernardino counties, not for them. We build the validated workflow first, measure it honestly, and publish real numbers starting at zero.
The barrier is information, not effort
Staff give extraordinary care with limited resources. The gap is the infrastructure underneath them.
Southern California faces one of the most urgent homelessness crises in the United States. The people responding give extraordinary care with limited resources. The barrier is rarely will or effort — it is information infrastructure.
- Intake is duplicated. A person re-tells the same traumatic history at every facility. Each intake is 20–60 minutes of staff time and re-traumatizing for the client.
- Availability is invisible. A case manager works a phone tree to find an open bed or slot. There is no shared, real-time view of what is open right now.
- Records don't travel. When someone moves between an outreach team, a shelter, and a bridge-housing provider, the receiving staff start from zero. Continuity breaks at every handoff.
- Matching is manual. Connecting a person to the right resource depends on individual staff knowledge and phone calls, not a shared system.
- Reporting is a tax. HMIS data entry is experienced as compliance overhead that pulls staff away from people.
What V1 commits to — and what it won't touch
Goals
- Cut duplicate intake by letting a person be assessed once and reused across the network, with consent.
- Give staff a real-time, shared view of bed and resource availability.
- Make referrals a warm, tracked handoff with the client record attached.
- Interoperate with HMIS so Bridge reduces reporting burden instead of adding a second system.
- Earn trust: privacy-first, consent-driven, useful to front-line staff on day one.
Non-Goals (V1)
- Does not allocate housing or override Coordinated Entry prioritization policy.
- Does not replace HMIS, clinical EHRs, or benefits systems — it integrates with them.
- Does not make eligibility or benefits determinations.
- No public-facing client app in V1. First users are staff; a client surface is a later phase gated on trust.
Built for the front line
The first users are staff. The client benefits indirectly — by never having to repeat their story.
Intake / Front-desk Staff
Fast, dignified intake; pull an existing assessment instead of re-keying; flag urgent needs.
Case Manager
A single timeline per client; see availability; make and track referrals; document once.
Outreach Worker
Mobile, offline-tolerant intake in the field; warm handoff to a shelter or service.
Shelter / Program Operator
Keep bed and slot counts current with minimal effort; see inbound referrals; manage capacity.
CoC / Coordinated Entry Coordinator
Network-level visibility; matching support; clean data that rolls up to required reporting.
Client (indirect in V1)
Not repeating their story at every door; consent respected; faster connection to help.
Five modules, built and rolled out together
Full-platform V1. Each module is validated with the design partner before it expands across the network.
Module 01
Unified Intake & Assessment
Structured digital intake captured once. With consent, an existing assessment is retrieved at the next provider instead of redone. Mobile and offline-capable; trauma-informed; maps to HMIS Universal Data Elements.
Module 02
Real-Time Resource & Bed Availability
A shared, live inventory of beds and program slots across providers. One-tap updates, filter by eligibility and population, with visible "last updated" so trust is earned, not assumed.
Module 03
Cross-Provider Client Record
A consented single record and timeline of touchpoints across the network. Granular, revocable consent the client controls. Identity resolution to stop duplicate records; full access audit trail.
Module 04
Referral & Warm Handoff
Referrals carry the consented record. The receiver can accept, hold, or decline with reason — visible to the sender. SLA timers and closed-loop outcome capture: did the person actually connect?
Module 05
Reporting & HMIS Interoperability
Map to HUD HMIS Data Standards and sync to the CoC's HMIS to cut double entry. Front-line dashboards plus de-identified network metrics — an honest scoreboard, starting at zero.
Cross-cutting
Privacy, Security & Low-Tech Reality
Granular, revocable consent; encryption and role-based access; HMIS privacy alignment and CCPA/CPRA. Works on older devices and weak connectivity; Spanish at minimum; WCAG-aligned.
An honest scoreboard, starting at zero
North-star: time from first contact to connected service.
Duplicate-intake time saved
Direct staff-time and client-burden reduction (minutes per client).
% referrals with closed-loop outcome
Are warm handoffs actually connecting people?
Median time-to-bed / time-to-service
The thing a person in crisis can least afford to lose.
% records reused across providers
Is "assess once" real?
Staff time: paperwork vs. people
The whole point — more time with people.
HMIS reporting completeness
Does Bridge reduce, not add, reporting burden?
Go deep with one partner, prove it, replicate
The same playbook behind Feynman: find the real workflow gap, build a validated tool, measure, then point it at the next provider.
Discovery
Structured outreach in LA and San Bernardino counties. Map intake, triage, referral, and HMIS reporting as they actually operate — before writing a line of code.
Design-partner build
Build V1 with one operator. Start with their single highest-pain module — likely intake reuse or availability — and expand as each module is validated.
Pilot & measure
Run with real caseloads. Publish the scoreboard. Fix what the numbers and staff tell us is wrong.
Transparent report
What we set out to do, what the numbers say, what changed, and what we got wrong.
Replicate
Extend to additional providers within the CoC, contingent on resources and mutual agreement on terms.
What could go wrong, said plainly
- Trust & adoption. Staff are overworked and have seen tools that added work. Bridge must save time in week one. Mitigation: build with staff; start with their highest-pain workflow.
- Consent & privacy. In a vulnerable population, data governance is existential, not a feature. Mitigation: privacy-first design, legal review, client-advocacy input.
- HMIS interoperability. Vendors and CoC governance vary; integration may be constrained. Open: which HMIS does the partner CoC run?
- Availability accuracy. A wrong bed count is worse than none. Mitigation: effortless updates, visible staleness, outcome feedback.
- Scope discipline. "Full-platform V1" still ships one validated module at a time, sequenced by partner pain.
Open questions: Which CoC and HMIS is the first partner on? What is their Coordinated Entry assessment tool? Where is the biggest measured time sink — intake, availability, or referral follow-up? What does the client-advocacy community want us not to build?
See the homelessness data & initiative →