24 C.F.R. § 887.107
§ 887.107 Cooperative Agreements. (24 CFR Part 887)
Operative Text
(a) An owner may enter into a Cooperative Agreement with: (1) A local PHA that operates an FSS program, pursuant to § 984.106 of this title; or (2) Another owner that operates an FSS program, pursuant to this section. (b) Owners that enter into a Cooperative Agreement pursuant to this part, must: (1) Open any FSS waiting lists to all eligible families residing in the properties covered by the Cooperative Agreement. (2) Provide periodic escrow amounts to the FSS Program Coordinator for FSS families covered by the Cooperative Agreement under this part. The Cooperative Agreement must provide that each owner is responsible for managing the escrow accounts of their participating families, including calculating and tracking of escrow in accordance with § 984.305 of this title, and set forth the procedures for the sharing of escrow information between the PHA and the owner. (3) The Cooperative Agreement must clearly specify the terms and conditions of such agreement, including the requirements of this section, and it must include a process for PHAs and owners to communicate with each other about changes in their Action Plan.
Under 24 CFR Part 887 § 887.107, housing owners participating in a Family Self-Sufficiency (FSS) program have the option to form Cooperative Agreements either with a local Public Housing Authority (PHA) that runs an FSS program or with another owner who does the same. When such an agreement is in place, all eligible families living in the covered properties must have access to any FSS waiting lists, and each owner retains responsibility for managing and tracking escrow accounts for their participating families in line with the broader FSS escrow rules. The agreement itself must be clearly written, spelling out all terms, conditions, and a communication process for sharing updates to Action Plans between the parties involved.
Plain English — not legal advice.
Property owners and managers operating under 24 CFR Part 887 § 887.107 who enter into a Cooperative Agreement generally ensure that FSS waiting lists are opened to all eligible families across every property covered by the agreement, without restricting access to residents of a single building or portfolio. Compliant operators maintain accurate escrow records for each participating family, calculate and track escrow contributions in accordance with § 984.305, and transmit periodic escrow amounts to the FSS Program Coordinator as required. The written Cooperative Agreement itself should clearly define each party's responsibilities, establish procedures for sharing escrow information, and include a structured process for communicating any changes to the Action Plan with the partnering PHA or owner.
General guidance for property managers — not legal advice for your specific situation. Consult an attorney for advice on your case.
Under 24 CFR Part 887 § 887.107, tenants who live in properties covered by a Cooperative Agreement have a right to access FSS waiting lists on equal footing with eligible families in all other properties under that same agreement — an owner cannot limit waiting list access to only their own building's residents. Tenants also have an interest in the proper management of their FSS escrow accounts, which owners are required to calculate and track according to established federal rules. Tenants who believe these requirements are not being followed may raise the issue with their local PHA's FSS Program Coordinator, consult a tenant-rights organization familiar with HUD programs, or explore whether a formal complaint process is available through the relevant housing authority.
General guidance for tenants — not legal advice for your specific situation. Consult a tenant-rights organization or attorney for advice on your case.
Generated September 4, 2026 — auto-generated, not yet human-reviewed. See /transparency for methodology.
Effective Timeline
References Out
No outbound references recorded yet for this provision.
References In
No inbound references recorded yet for this provision.