Home
Reports
Each year, the Big Bend Continuum of Care publishes a suite of HMIS reports that shine a light on who we serve, where we fall short, and how we can do better. Below you’ll find our core HMIS publications — Point-in-Time, Housing Inventory Count, and System Performance Measures — plus links to interactive dashboards, archived reports, and guidance on interpreting the data.
Select a report below to get started.
What it is: A federally-mandated, one-night snapshot of individuals and families experiencing homelessness—both sheltered and unsheltered—conducted every January.
Key Insights:
Breakdown by household type (individuals vs. families) and subpopulations (veterans, youth, survivors of domestic violence).
Trends in unsheltered homelessness hotspots across counties.
Year-over-year shifts that guide outreach and resource deployment.
Why it matters: Helps funders, policymakers, and service providers understand the scale and characteristics of homelessness in our region—and measure the impact of interventions over time.
What it is: An annual inventory of every bed and housing unit dedicated to those at risk of or experiencing homelessness—categorized by project type (emergency shelter, rapid-rehousing, permanent supportive housing).
Key Insights:
Total capacity versus utilization for each intervention type.
Seasonal swings in bed availability.
Identification of service deserts where demand consistently exceeds supply.
Why it matters:
Shapes HUD’s national HIC dashboard and helps set nationwide capacity targets.
Drives local decisions on where to expand or repurpose housing stock.
What it is: HUD-required, system-level metrics that assess how well Continuums of Care prevent and end homelessness.
Applicable Measures:
Length of Time Persons Remain Homeless
Returns to Homelessness
Number of Persons Experiencing Homelessness
Employment & Income Growth for CoC-Funded Projects
Number of Persons Who Become Homeless for the First Time
Successful Placement in or Retention of Permanent Housing
Key Insights:
Tracks whether people move quickly into stable housing and avoid returning to homelessness.
Monitors first-time homelessness to gauge effectiveness of prevention efforts.
Measures income gains to ensure people can maintain housing post-placement.
Why it matters:
Feeds into HUD’s national Performance Dashboard and guides competitive CoC funding.
Drives continuous improvement by pinpointing where our system excels—and where we need to strengthen supports.
Interested in more data? Check out our Data Dashboards page.
Interested in using data to help end homelessness? Join our bi-monthly HMIS & Data Committee to review trends and help define how our data and systems should work—shaping policy and improving impact across the CoC.
Your perspective helps turn raw data into better decisions.
A one-night snapshot (late January) of people experiencing homelessness in our CoC—sheltered and, through surveys/outreach, unsheltered.
How it’s used:
A census of beds and units dedicated to people experiencing homelessness on the same night as the PIT (e.g., Emergency Shelter, Transitional Housing, Rapid Re-Housing, Permanent Supportive Housing).
How it’s used:
Shows local capacity and where gaps exist (e.g., family vs. single-adult beds).
Tracks changes from project openings/closures or funding shifts.
Pairs with PIT to assess “demand vs. capacity.”
HUD-required, HMIS-based metrics that show how well our local homelessness response system—from street outreach and shelters to housing programs—works.
In plain English, SPMs answer:
How long people stay homeless before they move into permanent housing. (Shorter is better.)
How often people return to homelessness after exiting to permanent housing (checked 6–24 months later). (Fewer is better.)
How many people are entering homelessness for the first time—are we preventing new inflow?
Whether participants’ income goes up (jobs and benefits) while they’re in programs.
Whether people exit to permanent housing and keep it (placement and retention).
How they’re used: to set targets, fund what works, and drive system-level improvements.