community.solutions Open in urlscan Pro
2620:12a:8001::3  Public Scan

Form analysis
2 forms found in the DOM

GET /

<form method="get" action="/">
  <div class="input"><label for="s">Search</label><input type="text" name="s" id="s" placeholder="Search" class="noclear">
    <div class="close"></div>
  </div>
  <button type="submit"><span class="icon fa fa-search "></span></button>
</form>

<form>
  <div>
    <div class="nf-before-form-content"><nf-section>
        <div class="nf-form-fields-required"></div>
      </nf-section></div>
    <div class="nf-form-content "><nf-rows-wrap>
        <div class="nf-row">
          <nf-cells>
            <div class="nf-cell" style="width: 25%;">
              <nf-fields><nf-field>
                  <div id="nf-field-6-container" class="nf-field-container firstname-container  label-hidden ">
                    <div class="nf-before-field"><nf-section>
                      </nf-section></div>
                    <div class="nf-field">
                      <div id="nf-field-6-wrap" class="field-wrap firstname-wrap" data-field-id="6">
                        <div class="nf-field-label"><label for="nf-field-6" id="nf-label-field-6" class="">First Name </label></div>
                        <div class="nf-field-element">
                          <input type="text" value="" class="ninja-forms-field nf-element" id="nf-field-6" name="fname" autocomplete="given-name" placeholder="First Name" aria-invalid="false" aria-describedby="nf-error-6"
                            aria-labelledby="nf-label-field-6">
                        </div>
                      </div>
                    </div>
                    <div class="nf-after-field"><nf-section>
                        <div class="nf-input-limit"></div>
                        <div id="nf-error-6" class="nf-error-wrap nf-error" role="alert"></div>
                      </nf-section></div>
                  </div>
                </nf-field></nf-fields>
            </div>
            <div class="nf-cell" style="width: 25%;">
              <nf-fields><nf-field>
                  <div id="nf-field-8-container" class="nf-field-container lastname-container  label-hidden ">
                    <div class="nf-before-field"><nf-section>
                      </nf-section></div>
                    <div class="nf-field">
                      <div id="nf-field-8-wrap" class="field-wrap lastname-wrap" data-field-id="8">
                        <div class="nf-field-label"><label for="nf-field-8" id="nf-label-field-8" class="">Last Name </label></div>
                        <div class="nf-field-element">
                          <input type="text" value="" class="ninja-forms-field nf-element" id="nf-field-8" name="lname" autocomplete="family-name" placeholder="Last Name" aria-invalid="false" aria-describedby="nf-error-8"
                            aria-labelledby="nf-label-field-8">
                        </div>
                      </div>
                    </div>
                    <div class="nf-after-field"><nf-section>
                        <div class="nf-input-limit"></div>
                        <div id="nf-error-8" class="nf-error-wrap nf-error" role="alert"></div>
                      </nf-section></div>
                  </div>
                </nf-field></nf-fields>
            </div>
            <div class="nf-cell" style="width: 25%;">
              <nf-fields><nf-field>
                  <div id="nf-field-7-container" class="nf-field-container email-container  label-hidden ">
                    <div class="nf-before-field"><nf-section>
                      </nf-section></div>
                    <div class="nf-field">
                      <div id="nf-field-7-wrap" class="field-wrap email-wrap" data-field-id="7">
                        <div class="nf-field-label"><label for="nf-field-7" id="nf-label-field-7" class="">Email </label></div>
                        <div class="nf-field-element">
                          <input type="email" value="" class="ninja-forms-field nf-element" id="nf-field-7" name="email" autocomplete="email" placeholder="Email" aria-invalid="false" aria-describedby="nf-error-7" aria-labelledby="nf-label-field-7">
                        </div>
                      </div>
                    </div>
                    <div class="nf-after-field"><nf-section>
                        <div class="nf-input-limit"></div>
                        <div id="nf-error-7" class="nf-error-wrap nf-error" role="alert"></div>
                      </nf-section></div>
                  </div>
                </nf-field></nf-fields>
            </div>
            <div class="nf-cell" style="width: 25%;">
              <nf-fields><nf-field>
                  <div id="nf-field-5-container" class="nf-field-container submit-container  label-hidden  textbox-container">
                    <div class="nf-before-field"><nf-section>
                      </nf-section></div>
                    <div class="nf-field">
                      <div id="nf-field-5-wrap" class="field-wrap submit-wrap textbox-wrap" data-field-id="5">
                        <div class="nf-field-label"></div>
                        <div class="nf-field-element">
                          <input id="nf-field-5" class="ninja-forms-field nf-element " type="button" value="Subscribe">
                        </div>
                        <div class="nf-error-wrap"></div>
                      </div>
                    </div>
                    <div class="nf-after-field"><nf-section>
                        <div class="nf-input-limit"></div>
                        <div id="nf-error-5" class="nf-error-wrap nf-error" role="alert"></div>
                      </nf-section></div>
                  </div>
                </nf-field></nf-fields>
            </div>
          </nf-cells>
        </div>
      </nf-rows-wrap></div>
    <div class="nf-after-form-content"><nf-section>
        <div id="nf-form-errors-2" class="nf-form-errors" role="alert"><nf-errors></nf-errors></div>
        <div class="nf-form-hp"><nf-section>
            <label for="nf-field-hp-2" aria-hidden="true"> If you are a human seeing this field, please leave it empty. <input id="nf-field-hp-2" name="nf-field-hp" class="nf-element nf-field-hp" type="text" value="">
            </label>
          </nf-section></div>
      </nf-section></div>
  </div>
</form>

Text Content

 * The Challenge
 * Built For Zero
   * Overview
   * The Movement
   * Functional Zero
   * By-Name Data
 * Real Estate
 * News
 * About Us
   * Our Mission
   * Our Story
   * Our Team
   * Partners
   * Careers
 * Get Involved
   * Take action
   * Support our work
   * Visit community portals

Visit community portals
Search

Donate Visit community portals

 * Overview
 * The Movement
 * Functional Zero
 * By-Name Data

 * Our Mission
 * Our Story
 * Our Team
 * Partners
 * Careers

 * Take action
 * Support our work
 * Visit community portals


FUNCTIONAL ZERO

A definition for ending homelessness for a population


BUILT FOR ZERO USES FUNCTIONAL ZERO TO MEASURE WHETHER A COMMUNITY HAS
MEASURABLY ENDED HOMELESSNESS FOR A POPULATION.




WHAT IS FUNCTIONAL ZERO?

Functional zero is a milestone, which must be sustained, that indicates a
community has measurably ended homelessness for a population. When it’s
achieved, homelessness is rare and brief for that population.

Communities in Built for Zero are confirmed for achieving functional zero using
their quality, by-name data, which is updated at least monthly. 


Video: What Is functional zero?



WHAT DOES FUNCTIONAL ZERO MEAN?


1. HOMELESSNESS IS RARE AND BRIEF.

Every community has a functional zero threshold — the average number of people
exiting homelessness in a month. When a community achieves functional zero for a
population, it is keeping the number of people experiencing homelessness below
this threshold. This means that the number of people experiencing homelessness
at any time does not exceed the community’s proven record of housing at least
that many people.

This requires systems that are preventing homelessness, quickly detecting
homelessness when it occurs, and permanently and promptly resolving those
incidents of homelessness.






2. CITIES AND COUNTIES ARE OPERATING OFF OF A FULL ACCOUNTING OF HOMELESSNESS AT
ALL TIMES.

They do this by maintaining quality, real-time, comprehensive data on who is
experiencing it.




3. THE COMMUNITY IS WORKING TOWARD EQUITABLE SYSTEMS, STARTING WITH A FOCUS ON
RACE AND ETHNICITY.

Any system that is not designed to identify and respond to disparities risks
perpetuating them. Read more about the indicators communities track.




4. FINALLY, ALL OF THESE ACHIEVEMENTS ARE SUSTAINED OVER TIME, EVEN AS LOCAL
CONDITIONS CHANGE.

Communities reach functional zero once, and they must keep sustaining it. The
numbers of people at risk of or experiencing homelessness may rise, due to any
number of external factors. Functional zero tracks whether systems can
continuously drive those numbers down.




HOW IS FUNCTIONAL ZERO MEASURED FOR CHRONIC AND VETERAN HOMELESSNESS?

Communities in Built for Zero focus on achieving functional zero for one
population, as a step on the way toward ending homelessness for all populations.
A study by the Urban Institute found that this focused approach can accelerate a
community’s progress on subsequent populations.




FUNCTIONAL ZERO FOR VETERAN HOMELESSNESS

Functional zero for veteran homelessness means that fewer veterans are
experiencing homelessness than can be routinely housed in a month, with a
minimum threshold of 3 veterans.




FUNCTIONAL ZERO FOR CHRONIC HOMELESSNESS

The definition for ending chronic homelessness accounts for the long-lasting
nature of chronic homelessness, which can be more readily anticipated and
prevented. As a result, functional zero for chronic homelessness means there are
fewer than 3 people experiencing chronic homelessness at any given time (or .1%
of the total number of individuals reported in the most recent point-in-time
count, whichever is greater).




HOW DOES BUILT FOR ZERO CONFIRM COMMUNITIES ARE AT, AND SUSTAINING, FUNCTIONAL
ZERO?

Built for Zero confirms whether communities are at functional zero in three
steps:

 1. Making sure the community has shared at least six months of complete,
    quality, reliable data with Built for Zero
 2. Verifying that the community’s data reflects that they meet the functional
    zero definition
 3. Working with the community team to account for any flags in the community’s
    data

All communities at functional zero will be reviewed annually to ensure they are
sustaining this dynamic end state for ending homelessness. 

Bakersfield/Kern County, California, reached functional zero for chronic
homelessness in January 2020, and they have continued to sustain it. Learn more
about how communities track and visualize this data.



WHY DO WE NEED A DEFINITION FOR ENDING HOMELESSNESS?

We use functional zero because communities need a definition for ending
homelessness that is clear, measurable, and can be tracked over time. We cannot
compromise on the rigor of a definition for ending homelessness, because lives,
communities, and the equity of our society is at stake.


LEARN MORE

Solving homelessness across an entire community is complex. It is virtually
impossible if everyone is not clear on the end state they are trying to achieve,
and able to objectively measure if they are moving closer to it. Despite this
fact, policymakers and practitioners often define an end to homelessness
differently, or don’t have a shared definition at all.

Communities need a definition that creates accountability for the reality we
want: fewer people experiencing homelessness, equitable outcomes, and for
homelessness to be continuously rare and brief. This requires a standard that
recognizes that ending homelessness isn’t crossing a finish line, but sustaining
a new reality, even as new people experience housing instability.




--------------------------------------------------------------------------------


DOES FUNCTIONAL ZERO MEAN ZERO HOMELESSNESS?

Nope. Functional zero does not mean nobody is experiencing homelessness, or that
no one will experience homelessness. It does mean that a community has driven
that number down toward zero, and is keeping it below the community’s capacity
to ensure positive exits from homelessness.

Imagine if the homeless system operated like a well-functioning hospital. That
hospital will not necessarily prevent people from ever becoming sick. But it
will ensure people are triaged appropriately, promptly receive the services they
need, and address the illness, preventing further harm.



--------------------------------------------------------------------------------


HOW IS FUNCTIONAL ZERO DIFFERENT FROM THE FEDERAL GOVERNMENT’S BENCHMARKS AND
CRITERIA FOR ENDING HOMELESSNESS?

The federal government and Built for Zero use the same definition for confirming
that communities have ended chronic homelessness. The two entities differ on
their definitions of ending veteran homelessness. 

The Federal Criteria and Benchmarks for Achieving the Goal of Ending Veteran
Homelessness and the functional zero standard for veteran homelessness represent
different approaches to measurement, but they are not exclusive.

We believe that achieving the Federal Criteria and Benchmarks and/or Mayor’s
Challenge criteria for ending veteran homelessness is an important milestone on
the path to reaching functional zero, and a major accomplishment for a
community.

The Federal Criteria and Benchmarks are complex and affirm whether a community
has met valuable outcomes and system behaviors at the time that it was
certified.

Built for Zero’s definition of success, known as functional zero, lays out a
standard that allows a community to measure objectively and in real time whether
it has ended veteran homelessness and also whether it is sustaining this outcome
over time.

To achieve functional zero, a community must have fewer veterans experiencing
homelessness than routinely exit homelessness. This measures whether communities
have built systems that can achieve and sustain functional zero, even if new
veterans experience housing crises over time.



--------------------------------------------------------------------------------




WHAT COMMUNITIES HAVE REACHED FUNCTIONAL ZERO?




14 COMMUNITIES HAVE ACHIEVED FUNCTIONAL ZERO FOR AT LEAST ONE POPULATION




12 COMMUNITIES HAVE ENDED VETERAN HOMELESSNESS

 1.  Gulf Coast region, MS
 2.  Arlington County, VA 
 3.  Montgomery County, MD
 4.  Rockford, Winnebago & Boone Counties, IL
 5.  Bergen County, NJ
 6.  Abilene, TX
 7.  Lake County, IL
 8.  Norman, Cleveland County, OK
 9.  Chattanooga, TN
 10. Lynchburg Region, VA
 11. Crater Region, VA
 12. Fremont County, CO


5 COMMUNITIES HAVE ENDED CHRONIC HOMELESSNESS

 1. Rockford, Winnebago & Boone Counties, IL
 2. Lancaster City & County, PA
 3. Bergen County, NJ
 4. Abilene, TX
 5. Bakersfield, Kern County, CA


3 COMMUNITIES HAVE ENDED BOTH

 1. Rockford, Winnebago & Boone Counties, IL
 2. Bergen County, NJ
 3. Abilene, TX

--------------------------------------------------------------------------------


ABILENE, TX

ENDED VETERAN AND CHRONIC HOMELESSNESS

--------------------------------------------------------------------------------


BERGEN COUNTY, NJ

ENDED VETERAN AND CHRONIC HOMELESSNESS

--------------------------------------------------------------------------------


FREMONT COUNTY, CO

ENDED VETERAN HOMELESSNESS

--------------------------------------------------------------------------------


GULF COAST REGION, MS

ENDED VETERAN HOMELESSNESS

--------------------------------------------------------------------------------


NORMAN, CLEVELAND COUNTY, OK

ENDED VETERAN HOMELESSNESS

--------------------------------------------------------------------------------


ARLINGTON COUNTY, VA

ENDED VETERAN HOMELESSNESS

--------------------------------------------------------------------------------


CRATER REGION, VA

ENDED VETERAN HOMELESSNESS

--------------------------------------------------------------------------------


LANCASTER CITY & COUNTY, PA

ENDED CHRONIC HOMELESSNESS

--------------------------------------------------------------------------------


LAKE COUNTY, IL

ENDED VETERAN HOMELESSNESS

--------------------------------------------------------------------------------


ROCKFORD, WINNEBAGO & BOONE COUNTIES, IL

ENDED VETERAN AND CHRONIC HOMELESSNESS

--------------------------------------------------------------------------------


BAKERSFIELD, KERN COUNTY, CA

ENDED CHRONIC HOMELESSNESS

--------------------------------------------------------------------------------


CHATTANOOGA, TN

ENDED VETERAN HOMELESSNESS

--------------------------------------------------------------------------------


MONTGOMERY COUNTY, MD

ENDED VETERAN AND CHRONIC HOMELESSNESS

--------------------------------------------------------------------------------


LYNCHBURG REGION, VA

ENDED VETERAN HOMELESSNESS

--------------------------------------------------------------------------------

ALL COMMUNITIES AT FUNCTIONAL ZERO WILL BE REVIEWED ANNUALLY TO ENSURE THEY ARE
SUSTAINING THIS DYNAMIC END STATE FOR ENDING HOMELESSNESS.





QUESTIONS?

Reach out to comms@community.solutions.


YOU CAN HELP MORE COMMUNITIES REACH FUNCTIONAL ZERO.

Take action

Share
 * 
 * 
 * 
 * 
 * 

Sign up for our email newsletter: Email Subscribe
 * 
 * 
 * 

powers

Community Solutions is a non-profit organization that works to achieve a lasting
end to homelessness that leaves no one behind.
Our initiative Built for Zero is a movement of 90+ communities working to
measurably end homelessness.

 * Contact Us
 * Media Kit
 * Financials & Annual Reports
 * FAQs

PO Box 3524 | Church St. Station | New York, NY 10008

© Copyright 2022 Community Solutions — All Rights Reserved. Privacy Policy |
Non-profit design by openbox9

CLOSE
Join our mailing list

Sign up for the latest news on Built for Zero’s efforts to end homelessness and
more!

Notice: JavaScript is required for this content.
First Name


Last Name


Email



If you are a human seeing this field, please leave it empty.

X