FY 2017 HUD Income Limits

HUDUSER Header logo
background icon
Facebook icon
Twitter icon
Linked in icon
background icon
More Share Options
background icon
Like This on Facebook
April 25, 2017  

FY 2017 HUD Income Limits
HUD has released the estimated median family incomes (MFIs) and income limits for Fiscal Year (FY) 2017. MFIs are used as the basis for income limits in several HUD programs, including the Public Housing, Section 8 Housing Choice Voucher, Section 202 housing for the elderly, and Section 811 housing for persons with disabilities programs, as well as in programs run by agencies such as the Department of the Treasury, the Department of Agriculture, and the Federal Housing Finance Agency.
FY 2017 MFI estimates are calculated for 625 metropolitan areas and 1,974 nonmetropolitan counties in the U.S. and Puerto Rico using 2010–2014 5-year American Community Survey (ACS) and Puerto Rico Community Survey (PRCS) data, augmented by 2014 1-year ACS and PRCS data and brought forward to the midpoint of FY 2017 using a Consumer Price Index (CPI) forecast. For the non-Puerto Rico Insular Areas of the United States, 2010 Decennial Census data were used, augmented by national ACS income changes and a CPI forecast trend factor. The FY 2017 MFI data use the Section 8 program's Fair Market Rent area definitions.
Income limits are calculated in relation to MFIs for each FMR area with adjustments for family size and for areas with unusually high or low family income or housing-cost-to-income relationships.
Visit the FY 2017 Income Limits page on HUD User to access the data and documentation.
Learn More
New on HUD User
Whats New bar
HUD USER | P.O. Box 23268, Washington, DC 20026-3268
Toll Free: 1-800-245-2691 | TDD: 1-800-927-7589
Local: 1-202-708-3178 | Fax: 1-202-708-9981 

HUD Code of Conduct

SNAPS is working with staff from Office of Strategic Planning & Management, in the Grants Management & Oversight (GMO) Division to bring our recipients into compliance with 2 CFR Part 200.  Federal regulations (2 CFR part 200) and HUD's Notices of Funding Availability (NOFA) for discretionary funds require non-Federal entities receiving Federal assistance awards, excluding States, to develop and maintain written standards/codes of conduct covering conflicts of interest and governing the actions of its employees engaged in the selection, award and administration of contracts. No employee, officer, or agent may participate in the selection, award, or administration of a contract supported by a Federal award if he or she has a real or apparent conflict of interest (2 CFR 200.318(c)(1)).

With the implementation of 2 CFR Part 200, we found that a majority of CoC Program recipients Codes of Conduct are not in compliance, which will require a new Code of Conduct submission that will undergo an extensive review. The Grants Management Office maintains a library of these documents and updates HUD’ Code of Conduct page at www.hud.gov on a quarterly basis.  Submitting the document is only the first step to our recipients being compliant.  HUD must review and certify that the Code of Conduct meets minimum standards set forth in 2 CFR Part 200.

Specifically, Codes of Conduct must:
·       Be written on company letterhead that provides the name and title of the responsible official, mailing address, business telephone number and email address;
·       Prohibit real and apparent conflicts of interest that may arise among officers, employees or agents, or any member of his or her immediate family, his or her partner or an organization that employs any of the indicated parties;
·       If applicable, the standards must also cover organizational conflicts of interest;
·       Prohibit the solicitation and acceptance by employees, of gifts or gratuities in excess of minimum value; and
·       Provide for administrative and disciplinary actions to be applied for violations of such standards.
All CoC Program recipients and potential applicants intending to submit a project application in the FY 2017 CoC Program Competition MUST have a compliant Code of Conduct on file with HUDFailure to provide a copy of the organizations Code of Conduct and/or notify HUD of potential conflicts of interest may prevent applicants from receiving HUD funds.  SNAPS is working to address this NOW, rather than during the end of the application process to allow CoC Program recipients and applicants to update their Codes if necessary.  All Collaborative Applicants and project applicants recently received an email from GMO asking them to submit their Code of Conduct to  askGMO@hud.gov mailbox. 

We understand this has led to confusion in our communities, so we want to assure recipients they should submit their Codes of Conduct to the mailbox.  HQ SNAPs is also sending a message to all Collaborative Applicants and project applicants to let them know the request is legitimate and they should respond now to prevent issues during the CoC Program Competition award process. ​

CoC APR Resources and Reminders

Beginning on April 1, 2017, Continuum of Care (CoC) homeless assistance grant recipients must submit their Annual Performance Report (APR) data through a new online database – the Sage HMIS Reporting Repository (Sage). Communities will no longer submit APRs in e-snaps. This change in systems applies to all CoC homeless assistance grants (e.g., Supportive Housing Program, Shelter Plus Care, Section 8 Moderate Rehabilitation Single Room Occupancy Program, CoC Program) administered by the Office of Special Needs Assistance Programs (SNAPS) – regardless of when they were initially funded.

Access to Sage

To receive access to Sage, recipient staff need to access the Sage portal (www.sagehmis.info) and enter the contact information and the recipient affiliation (i.e., CoC). The CoC Primary Contact, who is the person identified by the Collaborative Applicant in the FY2016 CoC Program Registration as the Primary Contact, will then need to approve all users. The CoC Primary Contact will be notified when a user requests access and the user will be notified when the CoC authorizes that user’s access. The CoC Primary Contact should regularly access Sage and approve user access. HUD recommends that recipients provide CoC Primary Contacts a list of users they want approved for Sage access.
HUD prepopulated Sage with the contact information of all the CoC Primary Contacts. If the Primary Contact information submitted to HUD via e-snaps is out of date, CoCs need to notify HUD immediately via the Ask A Question (AAQ) portal and also update the Applicant Profile in e-snaps

Uploading Aggregate Client Data

A key feature of Sage is that recipients will upload a CSV-APR report file, with aggregate data on persons served by their project. It is critically important that the CSV-APR report file only include aggregate data on persons served. Recipients must not upload client-level, personally identifiable information, such as client name, date of birth, or Social Security Number, in Sage. Victim services providers must also be able to generate the CSV-APR report file, using the data that you have collected in your comparable database.
HMIS Leads should work with their local HMIS and comparable database vendors to access necessary reports and materials in preparation for the changes to the APR. In a previous listserv message, HUD stated that HMIS vendors should have the new CSV-APR report programmed into their software by April 1, 2017. If you do not have access to the new CSV-APR report, then you must follow-up with your HMIS Lead and your CoC to ensure that they are both working with the HMIS vendor to identify the reason for the delay and the expectation for a rollout of the new CSV-APR report.

CoC APR Resources

Sage CoC APR Guidebook: For information about HUD’s CoC APR reporting requirements, users should refer to the CoC APR Guidebook. HUD has revised the guidebook to include all APR types in a single document, so recipients will have one source of information for all APRs (CoC Full APR, HMIS APR, CoC Planning Grant APR, and the SRO APR).
Sage CoC APR Templates: HUD has published the CoC APR templates for the various types of APRs that recipients must submit.
Create an Account in Sage Video: To further assist communities in preparing for Sage, HUD recently released a brief “how-to” video that demonstrates how users can set up accounts in Sage.
Overview of the Sage HMIS Repository Webinar: On March 16th, HUD hosted a live webinar that reviewed the process of setting up an account in Sage and provided guidance on HUD’s expectations for the transition from e-snaps to Sage.
HUD hosted other webinars on submitting APR data in Sage the week of April 17, 2017: The webinars covered: how to access Sage, including a brief overview of the various user levels; how to complete the CoC Program APR in Sage; and how to access additional resources and guidance on the CoC Program APR and Sage. HUD anticipates posting these by May 1, 2017.


If you have questions about these reporting requirements, please submit them through the HUD Exchange Ask A Question (AAQ) portal. On Step 2 of the question submission process, select the appropriate report or reporting system in the “My question is related to” dropdown.
Visit the HUD Exchange at https://www.hudexchange.info

Take Action! Join Advocates for Wednesday’s National Call-In Day to Urge Congress to Fund Affordable Housing Investments for the Remainder of Fiscal Year 2017

Take Action! Join Advocates for Wednesday’s National Call-In Day to Urge Congress to Fund Affordable Housing Investments for the Remainder of Fiscal Year 2017
Tell your members of Congress to pass final spending bills for fiscal year 2017 before the April 28 deadline and to protect affordable housing investments
Lawmakers must pass spending bills by April 28 to avoid a government shutdown. Failure to pass full spending bills puts vital investments in affordable housing and community development at risk. By participating in a national call-in day tomorrow, Wednesday, April 26, you can urge Congress to pass a clean budget and protect critical investments.
National Call-In Day: Tomorrow, Wednesday, April 26
NCHV and the Campaign for Housing and Community Development Funding will hold a national call-in day, tomorrow, Wednesday, April 26. Tell your Members of Congress to pass a final spending bill for fiscal year FY17 before the April 28 deadline and to protect affordable housing investments. Share any impacts you have on how the current budget uncertainty has hurt your community. To contact your Members of Congress, call the congressional switchboard toll free at 202-224-3121.
Sample Script:
Please work with your colleagues to pass a final spending bill for fiscal year 2017 that protects affordable housing investments at HUD and USDA. These resources keep roofs over the heads of low income, at-risk, and formerly homeless veterans, and other vulnerable people. Affordable housing is a smart investment that leads to better health and education outcomes and boosts economic mobility and the local economy. Please do not put veterans at risk by failing to pass full-year HUD and USDA spending bills by the April 28 deadline.

Temporary Discontinuation of SOAR Consent Form


Temporary Discontinuation of SOAR Consent Form

and Alternative Steps

Based on recent conversations with the Social Security Administration, we are temporarily discontinuing use of the SOAR Consent for Release of Information Form (SOAR Consent) while we revise the form to make it more compliant with SSA's privacy guidelines. Communities who do not currently use this form as part of their SOAR Process will be unaffected by this change; however, the information below will still be helpful as you complete applications using the SOAR model.
The SOAR TA Center recommends the following steps in lieu of using the SOAR Consent:
Gathering Information on Previous or Pending Claims
If you use the SOAR Consent to request information on pending or previously filed SSI/SSDI applications, you can utilize the SSA-3288: Consent for Release of Information for this purpose.
  1. Download the SSA-3288 from the SSA website
  2. Follow the instructions on the form, along with guidance provided in the SOARWorks article, "Prior or Pending Applications"
  3. Be sure to specify on Question 8 the exact information you are looking for, such as "information related to pending SSI/SSDI claims, claim level and file dates; information related to denied claims, claim level, denial dates and reasons for denial; SSI/SSDI allowances and eligibility dates"
Setting the Protective Filing Date
Some communities may be using the SOAR Consent to set an applicant's protective filing date (PFD). Instead, we recommend setting the PFD via one of the following methods:
  1. Initiate the Online Disability Benefit Application, which can establish the PFD for both SSI and SSDI.
     -- If you are not ready to submit the complete SSI/SSDI application, press "save and exit" when you reach the re-entry number screen and print out the re-entry number.
  2. Call SSA to establish a date for an in-person or telephone interview.
Obtaining Additional Information
Assisting the applicant to create a free "my Social Security" account is an effective way to obtain other information previously requested using the SOAR Consent such as:
  • Verifying an applicant's date of birth
  • Checking on the status of an application or appeal
  • Getting a benefits verification letter
  • Reviewing contributions to Social Security and Medicare taxes
Sign up for a free account at: https://www.ssa.gov/myaccount
If you experience any issues as a result of this change and would like to speak further about it, please contact Jen Elder, National Policy and Partnerships Coordinator, at: jelder@prainc.com