EMERGENCY TRANSFER PLAN Sample Clauses

EMERGENCY TRANSFER PLAN. See the CoC Emergency Transfer Plan. § 576.500 RECORDKEEPING AND REPORTING REQUIREMENTS
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
EMERGENCY TRANSFER PLAN. Owner must comply with the terms of ADFA’s VAWA Emergency Transfer Plan, as may be updated from time to time, which among other items will: Allow for an internal emergency transfer to another available and safe unit in the development by any tenant or other lawful resident of a HOME unit who is or has been a victim of domestic violence, dating violence, sexual assault, or stalking. In such cases, the transferring tenant(s) may transfer to the new unit without having to undergo an application process and will, in all other respects, be treated as an in-place tenant. In cases where an immediately available and safe unit is not available for internal transfer, require Owner to notify ADFA of the tenant’s request for an external emergency transfer, to cooperate and assist in providing information to the tenant about other units potentially available in ADFA’s portfolio of HOME units, and waive any early termination or other similar fee(s) for tenants requiring an emergency transfer that results in the breaking of the lease.
Sample 1
EMERGENCY TRANSFER PLAN. SMHA has adopted an Emergency Transfer Plan, included as part of this policy. To request an emergency transfer the tenant must submit a written request in accordance with the Emergency Transfer Plan. HUD-5383 may be used to request an emergency transfer. 5.1 A Section 8 recipient who moves out of an assisted dwelling unit to protect their health or safety and who: a) is a victim under this Policy; b) reasonably believes he or she was imminently threatened by harm from further violence if she/he remains in the unit; and c) has complied with all other obligations of the Section 8 program may receive a voucher and/or move to another Section 8 jurisdiction. 5.2 A public housing tenant who is a victim under this policy may be allowed to transfer to another available and safe dwelling unit pursuant to SMHA’s Emergency Transfer Plan.
Sample 1
EMERGENCY TRANSFER PLAN. (1) The participating jurisdiction must develop and implement an emergency transfer plan and must make the determination of whether a tenant qualifies under the plan. The plan must meet the requirements in 24 CFR 5.2005(e), as supplemented by this section. (2) For the purposes of § 5.2005(e)(7), the required policies must specify that for tenants who qualify for an emergency transfer and who wish to make an external emergency transfer when a safe unit is not immediately available, the participating jurisdiction must provide a list of properties in the jurisdiction that include HOME-assisted units. The list must include the following information for each property: The property's address, contact information, the unit sizes (number of bedrooms) for the HOME-assisted units, and, to the extent known, any tenant preferences or eligibility restrictions for the HOME-assisted units. In addition, the participating jurisdiction may: (i) Establish a preference under the participating jurisdiction's HOME program for tenants who qualify for emergency transfers under 24 CFR 5.2005(e); (ii) Provide HOME tenant-based rental assistance to tenants who qualify for emergency transfers under 24 CFR 5.2005(e); or (iii) Coordinate with victim service providers and advocates to develop the emergency transfer plan, make referrals, and facilitate emergency transfers to safe and available units.
Sample 1
EMERGENCY TRANSFER PLAN. Each covered housing provider, as identified in the program- specific regulations for the covered housing program, shall adopt an emergency transfer plan, no later than June 14, 2017 based on HUD's model emergency transfer plan, in accordance with the following: (1) For purposes of this section, the following definitions apply: (i) Internal emergency transfer refers to an emergency relocation of a tenant to another unit where the tenant would not be categorized as a new applicant; that is, the tenant may reside in the new unit without having to undergo an application process. (ii) External emergency transfer refers to an emergency relocation of a tenant to another unit where the tenant would be categorized as a new applicant; that is the tenant must undergo an application process in order to reside in the new unit. (iii) Safe unit refers to a unit that the victim of domestic violence, dating violence, sexual assault, or stalking believes is safe. (2) The emergency transfer plan must provide that a tenant receiving rental assistance through, or residing in a unit subsidized under, a covered housing program who is a victim of domestic violence, dating violence, sexual assault, or stalking qualifies for an emergency transfer if: (i) The tenant expressly requests the transfer; and (ii) (A) The tenant reasonably believes there is a threat of imminent harm from further violence if the tenant remains within the same dwelling unit that the tenant is currently occupying; or (B) In the case of a tenant who is a victim of sexual assault, either the tenant reasonably believes there is a threat of imminent harm from further violence if the tenant remains within the same dwelling unit that the tenant is currently occupying, or the sexual assault occurred on the premises during the 90-calendar-day period preceding the date of the request for transfer.
Sample 1

Related to EMERGENCY TRANSFER PLAN

  • Emergency Transition Registry Operator agrees that, in the event that any of the emergency thresholds for registry functions set forth in Section 6 of Specification 10 is reached, ICANN may designate an emergency interim registry operator of the registry for the TLD (an “Emergency Operator”) in accordance with ICANN’s registry transition process (available at <xxxx://xxx.xxxxx.xxx/en/resources/registries/transition-­‐processes>) (as the same may be amended from time to time, the “Registry Transition Process”) until such time as Registry Operator has demonstrated to ICANN’s reasonable satisfaction that it can resume operation of the registry for the TLD without the reoccurrence of such failure. Following such demonstration, Registry Operator may transition back into operation of the registry for the TLD pursuant to the procedures set out in the Registry Transition Process, provided that Registry Operator pays all reasonable costs incurred (i) by ICANN as a result of the designation of the Emergency Operator and (ii) by the Emergency Operator in connection with the operation of the registry for the TLD, which costs shall be documented in reasonable detail in records that shall be made available to Registry Operator. In the event ICANN designates an Emergency Operator pursuant to this Section 2.13 and the Registry Transition Process, Registry Operator shall provide ICANN or any such Emergency Operator with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such Emergency Operator. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event that an Emergency Operator is designated pursuant to this Section 2.13. In addition, in the event of such failure, ICANN shall retain and may enforce its rights under the Continued Operations Instrument.

  • Emergency Thresholds The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement as described in Specification 2, Part B, Section 6.

  • Deviation from Grievance Procedure The Employer agrees that, after a grievance has been discussed at Step 2 of the grievance procedure the Employer or his representatives shall not initiate any discussion or negotiations with respect to the grievance, either directly or indirectly with the aggrieved employee without the consent of the xxxxxxx or the Union.

  • Retainage for Unacceptable Corrective Action Plan or Plan Failure If the corrective action plan is unacceptable to the Department or Customer, or implementation of the plan fails to remedy the performance deficiencies, the Department or Customer will retain ten percent (10%) of the total invoice amount. The retainage will be withheld until the Contractor resolves the performance deficiencies. If the performance deficiencies are resolved, the Contractor may invoice the Department or Customer for the retained amount. If the Contractor fails to resolve the performance deficiencies, the retained amount will be forfeited to compensate the Department or Customer for the performance deficiencies.

  • CERTIFICATION REGARDING DEBARMENT, SUSPENSION, INELIGIBILITY AND VOLUNTARY EXCLUSION

  • CERTIFICATION REGARDING DEBARMENT AND SUSPENSION The undersigned (authorized official signing for the contracting organization) certifies to the best of his or her knowledge and belief, that the contractor, defined as the primary participant in accordance with 45 CFR Part 76, and its principals: are not presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from covered transactions by any Federal Department or agency have not within a 3-year period preceding this contract been convicted of or had a civil judgment rendered against them for commission of fraud or a criminal offense in connection with obtaining, attempting to obtain, or performing a public (Federal, State, or local) transaction or contract under a public transaction; violation of Federal or State antitrust statutes or commission of embezzlement, theft, forgery, bribery, falsification or destruction of records, making false statements, or receiving stolen property; are not presently indicted or otherwise criminally or civilly charged by a governmental entity (Federal, State, or local) with commission of any of the offenses enumerated in Section 2 of this certification; and have not within a 3-year period preceding this contract had one or more public transactions (Federal, State, or local) terminated for cause or default. Should the Contractor or Subrecipient not be able to provide this certification, an explanation as to why should be placed after the assurances page in the contract. The contractor agrees by signing this contract that it will include, without modification, the clause above certification in all lower tier covered transactions (i.e., transactions with sub-grantees and/or contractors) and in all solicitations for lower tier covered transactions in accordance with 45 CFR Part 76.

  • Reportable Events Involving the Xxxxx Law Notwithstanding the reporting requirements outlined above, any Reportable Event that involves solely a probable violation of section 1877 of the Social Security Act, 42 U.S.C. §1395nn (the Xxxxx Law) should be submitted by Practitioner to CMS through the self-referral disclosure protocol (SRDP), with a copy to the OIG. If Practitioner identifies a probable violation of the Xxxxx Law and repays the applicable Overpayment directly to the CMS contractor, then Practitioner is not required by this Section III.G to submit the Reportable Event to CMS through the SRDP.

  • Certification Regarding Debarment Party certifies under pains and penalties of perjury that, as of the date that this Agreement is signed, neither Party nor Party’s principals (officers, directors, owners, or partners) are presently debarred, suspended, proposed for debarment, declared ineligible or excluded from participation in Federal programs, or programs supported in whole or in part by Federal funds.

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the Funder has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Transfer or Deletion of Student Data The Provider shall review, on an annual basis, whether the Student Data it has received pursuant to the DPA continues to be needed for the purpose(s) of the Service Agreement and this DPA. If any of the Student Data is no longer needed for purposes of the Service Agreement and this DPA, the Provider will provide written notice to the LEA as to what Student Data is no longer needed. The Provider will delete or transfer Student Data in readable form to the LEA, as directed by the LEA (which may be effectuated through Exhibit D of the DPA), within 30 calendar days if the LEA requests deletion or transfer of the Student Data and shall provide written confirmation to the LEA of such deletion or transfer. Upon termination of the Service Agreement between the Provider and LEA, Provider shall conduct a final review of Student Data within 60 calendar days. If the LEA receives a request from a parent, as that term is defined in 105 ILCS 10/2(g), that Student Data being held by the Provider be deleted, the LEA shall determine whether the requested deletion would violate State and/or federal records laws. In the event such deletion would not violate State or federal records laws, the LEA shall forward the request for deletion to the Provider. The Provider shall comply with the request and delete the Student Data within a reasonable time period after receiving the request. Any provision of Student Data to the LEA from the Provider shall be transmitted in a format readable by the LEA.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!