This should be an initiative page, not just a report page
The report is the proof point. The initiative is the story. Position Bay Area as the first visible example of a broader national need: communities need a survivor-centered coordination layer that works with existing systems while addressing the realities of GBV shelter access.
Shelter searches are same-day crises. The page should lead with urgency, not abstract systems language.
Referrers still cold-call shelters. Make manual workflow friction the problem statement buyers immediately understand.
Denials happen because no beds are available. Capacity matters, but visibility and fit still shape whether a placement is actually possible.
Providers want real-time availability. Make the solution feel practical, not theoretical.
“Right now, access to shelter often depends on who you know — relationships matter, but they shouldn’t be the only way to secure a placement.”
What this page should do
- Make the report easy to read and share without gating it.
- Convert high-intent visitors into community conversations.
- Give public agencies a procurement-ready overview of the model.
- Explain why collaborative entry is different from centralized bed control.
- Show that this is a repeatable national approach, not a Bay Area one-off.
One page, three audiences
Do not force every visitor through the same message. Give each audience a clear reason to stay on the page and a clear next step.
Cities, counties, states, and public buyers
Need to see implementation logic, governance, reporting value, procurement fit, and why this is not just another directory.
GBV shelters, referral partners, coalitions, and hotlines
Need to see that confidentiality comes first, provider judgment stays intact, and the workflow is easier than what exists now.
Funders, advocates, CoCs, HMIS leaders, and regional partners
Need to understand the gap, the model, and how to convene the right local stakeholders around a practical next step.
Lead with collaborative entry, not product features
The core job of the page is to name the model clearly. The Grove is the implementation layer. Collaborative entry is the idea that can travel across the country.
Traditional centralized bed control
- One central list
- One placement authority
- Best fit for systems where inventory can be centrally assigned
- Focuses on the next available bed
- Often struggles where confidentiality and nuanced fit matter most
Collaborative entry with The Grove
- Shared, non-PII visibility across participating programs
- Shelters retain acceptance authority and safety judgment
- Referrals are based on fit, confidentiality, and availability
- Works alongside coordinated entry instead of replacing it
- Builds aggregate system insight without exposing survivor information
The page should show the operational layer communities do not have today
Keep this section grounded in workflow improvement. Buyers care about reporting and governance. Providers care about speed, fit, and trust. This section should serve both.
Live availability
Single beds, family rooms, private versus congregate space, and after-hours status — the details that determine whether a placement is actually possible.
Fit and intake context
ADA access, pets, language, gender access, curfews, documentation expectations, and other details that shape safe, appropriate referrals.
Shelter-managed operations
Programs manage their own bed lists, queues, referral holds, and accept / decline decisions without giving up control to a centralized outside authority.
Aggregate system insight
Queue pressure, unmet demand, denial reasons, time-to-placement, and bed-type gaps that funders and governments can actually use for planning.
What to say plainly on the page
- This is not another static resource list.
- This is not HMIS replacement rhetoric.
- This is not centralized bed control.
- This is a shared visibility and coordination layer designed for survivor-serving systems.
What to avoid
- Overleading with product screenshots before the visitor understands the systems problem.
- Using “Bay Area” so heavily that the national use case disappears.
- Burying the public-agency value proposition at the bottom.
- Using generic “contact us” language where a stronger, intent-based CTA should exist.
Show the implementation path, not just the concept
This is the section that turns interest into action. Communities need to see a realistic path from conversation to pilot.
Convene the right mix of local stakeholders
Bring together GBV shelters, hotlines, referral partners, CoCs, HMIS leads, relevant public agencies, and funding stakeholders for a facilitated conversation grounded in local workflows.
Map the current referral process and points of friction
Document how same-day placement happens today, where information breaks down, how after-hours coverage works, and what prevents fast, safe matching.
Assess readiness for collaborative entry
Evaluate governance, trust, participation, data practices, update workflows, and appetite for a shared visibility layer that fits local confidentiality requirements.
Define the pilot, reporting, and procurement path
Turn findings into a practical implementation plan — who participates, what gets measured, how agencies are onboarded, and what the public-agency decision looks like.
The Bay Area report should feel like evidence, not the whole campaign
Make the report central and highly visible, but frame it as the first public example of a larger initiative to build collaborative entry in survivor-serving systems.
Across the Lines: Bay Area
Insights on shelter referrals, emergency housing coordination, and the case for shared shelter availability.
What visitors should take away
- The current process is deeply collaborative but still structurally fragmented.
- Urgent need collides with limited capacity, fragmented information, and manual search work.
- Providers want shared visibility, but only if updates are easy and maintenance is real.
- Technology alone is not enough; durable coordination needs funded operations and community buy-in.
Use this report to
Build credibility, create urgency, give funders a concrete evidence base, and open the door to community conversations in other regions.
Do not use it as
A passive PDF graveyard. Keep the report embedded in a live conversion page with repeated calls to action and cross-links to government-facing content.
Request a facilitated community conversation
This should be the page’s main CTA. It is more distinctive than “contact us,” more strategic than “book a demo,” and directly supports your community-readiness and government-sales motion.
What communities get
- A facilitated cross-system conversation about current shelter referral workflows.
- A needs and readiness assessment focused on collaborative entry.
- Recommendations on governance, participation, and update practices.
- A clearer path to pilot design, funding conversations, and public-agency adoption.
Recommended HubSpot form
Replace this mockup with a dedicated “Bring Collaborative Entry to Your Community” form.Give buyers a reason to stay on the page
Borrow the procurement-ready tone of your government page, but tailor it to collaborative entry. The buyer message is not “nice report.” It is “here is a practical coordination layer communities can actually adopt.”
Built for public safety and housing stability
Frame the page around safer placements, faster coordination, less manual searching, and better visibility into unmet demand.
Procurement and implementation ready
Use direct language about governance, onboarding, reporting, scope alignment, and the path from conversation to pilot launch.
Better aggregate data without exposing survivor data
Highlight vacancy trends, denial reasons, queue pressure, and time-to-placement as public-agency value, not just provider convenience.
Add a dedicated buyer CTA block
Public-sector visitors should not have to guess where to go next. Give them an immediate path to a strategy meeting and a secondary path to your government purchasers page.
Use the FAQ to remove the obvious objections
This is where the page earns trust. The goal is to reduce friction for provider networks, CoCs, and public agencies before they ever fill out a form.
Does collaborative entry replace coordinated entry?
No. Position it as a complementary coordination layer that can work alongside coordinated entry while reflecting the distinct confidentiality and safety needs of survivor-serving programs.
Is this the same as centralized bed control?
No. The point of collaborative entry is shared visibility and faster coordination while keeping acceptance authority and safety judgment with each participating shelter.
Does this require survivor data to be entered into HMIS?
No. The page should clearly say that confidentiality comes first and that communities can design the right connection points to existing coordinated entry or comparable-database workflows without flattening survivor privacy needs.
Is this only for the Bay Area?
No. The Bay Area report is the first public proof point. The initiative is meant for cities, counties, regions, and states that want a better collaborative process for survivor shelter coordination.
What happens if our community is not ready to adopt a platform yet?
That is exactly why the community-conversation CTA matters. The first step can be a facilitated conversation and readiness assessment, not a procurement decision.
Need immediate help?
Keep a compact support box on the page. Because this page may attract survivors directly, make it easy for people in crisis to find appropriate help fast.
- National Domestic Violence Hotline: 1-800-799-7233
- National Sexual Assault Hotline: 1-800-656-4673
- National Human Trafficking Hotline: 1-888-373-7888
- Bay Area support: link to your existing resource pages where appropriate
Bay Area is the proof point. Collaborative entry is the national story.
Build this page as a campaign-style landing page for the initiative, with the report as the proof, the community conversation as the primary conversion, and the buyer meeting as the secondary conversion. That gives you a page that informs, persuades, and sells.