11.07.2015 Views

RAD PIH Notice 2012-32 (.pdf, 1 MB) - National Low Income ...

RAD PIH Notice 2012-32 (.pdf, 1 MB) - National Low Income ...

RAD PIH Notice 2012-32 (.pdf, 1 MB) - National Low Income ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section III: Rent Supplement and Rental Assistance Payment ProjectsThe Public Housing field office staff will also provide the owner with contact information forPHAs with jurisdiction over the project. Prior to submission of the <strong>RAD</strong> request, the owner isrequired to contact a PHA to have a preliminary conversation about the <strong>RAD</strong> conversion. Theintent of this conversation is for the owner to determine: a) the PBV rents that are anticipatedfor the project (up to 110% of FMR, subject to rent reasonableness); and b) whether the PHAhas interest in administering the PBV contract at the project. The formal consent of the PHAwill occur at a later stage of the process, once HUD has determined the request meets all therequirements of this <strong>Notice</strong>. The owner is advised that HUD will make the final selection of thePHA. However, this initial discussion will help the owner determine the viability of theconversion request.After making contact with the HUD field office and the PHA with jurisdiction over theproperty, the owner must complete the following tenant briefing, tenant notification and tenantcomment activities prior to submission of the <strong>RAD</strong> conversion request: The owner is required tonotify all project households and legitimate tenant organizations (as defined in 24 CFR Part 245and Housing <strong>Notice</strong> 2011-29) of the owner’s request to provide PBV assistance in lieu of TPVassistance. The owner or owner’s representative is also required to schedule a residents’briefing, with participation from HUD field office staff in a manner that is feasible, in order tofully inform residents and legitimate tenant organizations of the features of TPV and PBVassistance and the impact of the proposed conversion on residents’ mobility options andanticipated rent payments. The briefing will include information on the anticipated contracttermination, the date of the termination, the units that are affected by the termination of the RentSupp or RAP contract, and the units that would receive PBV assistance in lieu of TPVassistance. The briefing will also provide residents with information on the features of TPVassistance and PBV assistance, including mobility options, rent levels, rent payments, provisionof supportive services, and any proposed repair or project improvements that may be planned aspart of the <strong>RAD</strong> conversion transaction. The owner or owner’s representative must attend thebriefing and be available to respond to residents’ questions and comments. In accordance with24 CFR § 8.6, Title VI, Executive Order 13166 and HUD’s Limited English ProficiencyGuidance, published in the Federal Register on February 16, 2007 (72 FR 27<strong>32</strong>), the briefingshould include accessible communications for persons with disabilities and language assistanceto persons with limited English proficiency.Residents of units where assistance is proposed for conversion must have the opportunity tocomment on the owner’s request and the owner must take these written and oral residentcomments into consideration and follow the requirements outlined below:1. The notification letter must offer the residents a description of the anticipated contracttermination, the date of the termination, the units that are affected by the termination ofthe Rent Supp or RAP contract, and the units that would receive PBV assistance in lieu ofTPV assistance. The notification letter must also include a description of the different<strong>PIH</strong>-<strong>2012</strong>-<strong>32</strong> (HA) Rental Assistance Demonstration – Final Implementation 130

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!