PBV AHAP: What the Agreement Requires Before the HAP Contract
A PBV AHAP is the agreement that can govern new construction or rehabilitation before Project-Based Voucher units enter their initial Housing Assistance Payments contract. HUD's current regulation calls it the Agreement to Enter into a HAP Contract, or Development Agreement. It identifies the units, development work, deadlines and other conditions the owner must satisfy before the PHA accepts the completed housing.
The AHAP itself does not pay rental assistance. Housing Assistance Payments begin under the later HAP contract. The Agreement instead connects project selection and development to that future contract by spelling out what must be built or rehabilitated and what has to be verified before the units are accepted.
The AHAP Is the Default Development Agreement, but There Are Exceptions
For PBV development activity involving newly constructed or rehabilitated housing, the ordinary rule is that the PHA and owner enter into an Agreement governing the development work.
Under the standard path, the Agreement is executed before development activity begins. The owner agrees to develop the contract units so they comply with HUD's Housing Quality Standards and the other applicable development requirements. The PHA agrees that timely and compliant completion can lead to execution of the initial HAP contract.
Current regulations also give PHAs a significant HOTMA flexibility. A PHA may establish circumstances in its Administrative Plan in which it will:
- Enter into a PBV HAP contract for qualifying newly constructed or rehabilitated housing without first using an Agreement.
- Execute an Agreement after qualifying construction or rehabilitation has already begun.
That is PHA discretion, not an automatic right for an owner to start work first. The Administrative Plan must authorize the approach, and the owner must document compliance with the applicable PBV development requirements from the regulatory starting point.
Existing Housing Does Not Follow the Same Development Path
The AHAP is tied to PBV development activity. Existing housing follows a different path because it is not being developed through the new-construction or rehabilitation process before entering the HAP contract.
The distinction among existing, newly constructed and rehabilitated PBV housing therefore matters before anyone decides which contract sequence applies.
An older building is not automatically existing housing for PBV purposes. A property that already exists but requires development activity to qualify for the program may instead be treated as rehabilitated housing.
The Agreement Is Between the PHA and the Owner
The parties to the PBV Development Agreement are the public housing agency and the project owner.
The Agreement applies to a single project under the general rule. HUD currently permits one Agreement to cover multiple projects only in the specific circumstance where each project consists of a single-family building.
The document is not a lease between an owner and a tenant, and families do not become parties to the AHAP because they may eventually occupy PBV-assisted units.
The broader Project-Based Voucher program separates the PHA-owner HAP relationship from the owner-family lease and tenancy relationship.
The Unit Schedule Has to Be Specific
The Development Agreement must describe the housing that will eventually be assisted. At minimum, the current regulation requires information identifying:
- The project site.
- The location of the proposed contract units on the site.
- The number of contract units.
- The square footage of those units.
- The number of bedrooms and bathrooms.
- Services, maintenance or equipment the owner will supply without additional charges beyond rent to owner.
- Utilities available to the units.
- Which utilities the owner will pay.
- Which utilities the tenant will pay.
- Estimated initial rents to owner.
Those details matter because the future HAP contract is not simply a promise to attach an unspecified number of vouchers somewhere within a development.
Rehabilitation Requires a Work Write-Up
For rehabilitation, the Agreement must contain a description of the rehabilitation work.
The work description includes the rehabilitation work write-up. Specifications and plans must also be included when the PHA determines they are necessary.
The work write-up establishes what the owner is agreeing to complete before the proposed units can be accepted through the normal pre-HAP development route.
A general statement that the property will be renovated is not the regulatory equivalent of the required work description.
New Construction Requires Working Drawings and Specifications
New construction is documented differently because the units do not yet exist at the relevant project-selection point.
The Agreement's work description for new construction must include the working drawings and specifications for the development.
The PHA may also impose design, architecture or quality requirements beyond HQS if its Administrative Plan identifies the circumstances in which those additional standards will apply.
Those additional requirements become part of the development standard the PHA later checks when deciding whether to accept the completed units.
Accessibility Work Belongs in the Agreement
Applicable accessibility requirements are development requirements, not issues that should first be addressed when a tenant with a disability applies for a unit.
Where the Fair Housing Act, Section 504 or the Americans with Disabilities Act requires development work, the Agreement must describe the required accessibility items.
That can affect plans, unit design, common areas and other aspects of the development depending on which federal accessibility requirements apply to the particular project.
The owner and PHA should therefore resolve applicable accessibility work before treating the development scope as final.
Some Projects Must Address Broadband Infrastructure
Current PBV development rules can require broadband infrastructure when the development activity constitutes substantial rehabilitation of a building with more than four rental units and the regulatory conditions are met.
When that requirement applies, the necessary broadband work must be described in the Agreement.
The regulation recognizes documented exceptions where installation is infeasible because of the location, the structure, or because the cost would create the type of fundamental alteration or undue financial burden specified by the rule.
The Agreement Must Set a Completion Deadline
The AHAP is not open-ended. Current §983.154 requires the Agreement to state a deadline for completion of the development work.
HUD's currently listed Agreement form also provides space for the effective date, commencement date and the period allowed for completion. A project can be organized as a single-stage or multi-stage development.
Under the form's existing terms, the owner is expected to begin, diligently continue and finish the work according to the agreed schedule. The owner reports commencement and provides progress reports when required by the PHA.
Delays do not automatically rewrite the schedule. The currently listed form permits the PHA to extend completion time for an appropriate period when delay results from unforeseen factors beyond the owner's control, as determined by the PHA and in accordance with HUD requirements.
Changes to the Development Scope Need to Be Controlled
The owner cannot treat the Agreement's work description as a rough concept and later redesign the development without regard to the PHA.
Current regulations allow the PHA and owner to amend the contents of the Agreement through an addendum when the amendment remains consistent with Part 983.
An addendum affecting a unit must be executed before the PHA accepts that completed unit.
The currently listed HUD form also requires prior PHA approval for work changes that alter the design or quality of the rehabilitation or construction.
Starting Work Before the AHAP Can Be Risky Even Under the New Flexibility
HOTMA changed an important part of the old development sequence. A PHA may now allow qualifying development to begin before an Agreement is executed, or may proceed without an Agreement, when its Administrative Plan authorizes that approach.
The flexibility does not erase the PBV development requirements.
For competitively selected housing, the owner must be able to document compliance with applicable §983.153 requirements from the date of proposal submission. The PHA must make the required compliance confirmation before proposal selection.
For a project excepted from competition, the corresponding regulatory starting point is the PHA board resolution approving project-basing at that project. Required compliance must be documented from that date, and the PHA must make its confirmation before executing the Agreement or HAP contract, as applicable.
A developer therefore should not assume that work performed before an AHAP is outside PBV oversight. In some situations, exactly the opposite is true: the owner has to demonstrate that qualifying work complied with PBV requirements from an earlier date.
Labor Standards Can Apply Before the Agreement Is Signed
PBV development requirements include federal labor standards for qualifying projects.
When development involves nine or more contract units, the current regulation requires Davis-Bacon wages for covered laborers and mechanics and compliance with the other specified federal labor requirements. The PHA monitors labor-standard compliance.
If the PHA uses the flexibility allowing development before an Agreement, those labor obligations do not necessarily start only when the AHAP is eventually signed.
Section 983.153 requires the applicable parties to comply from the proposal-submission date for competitively selected housing or from the PHA board-resolution date for a project excepted from competitive selection.
The PHA's project-selection notice or applicable board resolution must also state the requirement to incorporate the applicable Davis-Bacon contract clause and current prevailing-wage determination when those labor standards apply.
Other Development Requirements Can Block the Agreement
The AHAP sits inside a larger PBV development process. Signing the document does not override requirements that must already have been satisfied.
Development activity is subject, as applicable, to environmental-review requirements, subsidy-layering review, accessibility rules, federal labor requirements, equal-employment requirements, broadband requirements and federal exclusion/debarment rules.
When subsidy layering review is required because PBV assistance is combined with other governmental housing assistance, the PHA cannot execute the Agreement or HAP contract until the required review determines that the assistance complies with HUD's subsidy-layering requirements.
The owner also has an ongoing duty to disclose qualifying changes in the assistance or development information used in that review before all contract units are placed under the HAP contract.
The Owner Makes Federal Eligibility and Conflict Certifications
The Agreement is more than a construction schedule.
Current §983.153 requires both the Agreement, when applicable, and the HAP contract to contain an owner certification concerning the owner's and project principals' eligibility to participate in federal programs.
An owner or project principal who is debarred, suspended, subject to an applicable limited denial of participation or otherwise federally excluded cannot participate in the covered development activity.
The owner must also disclose possible conflicts of interest that would violate the Agreement, HAP contract or HUD regulations.
Completion Requires Evidence, Not Just an Owner's Notice
Finishing physical construction does not by itself complete the PBV development process.
After the development activity is finished, the owner must submit evidence and certify to the PHA that the work was completed in accordance with the applicable requirements. The form and manner of that submission are established through the PHA's Administrative Plan.
The PHA must review the evidence and determine whether the development activity was completed in accordance with the applicable requirements.
Depending on the project and the PHA's requirements, completion documentation may include evidence involving local occupancy approval, design or development certification, the approved work description and other records necessary to establish that the required work was actually completed.
The Completed Units Must Be Inspected Before Acceptance
After receiving the required completion evidence and owner certification, the PHA inspects the completed units.
The inspection determines whether the units comply with HUD's HQS and any additional design, architecture or quality requirements the PHA validly imposed for the project.
Completion of the contractor's work and PBV acceptance are therefore separate events.
If the project is PHA-owned, the applicable completion review and inspection functions are handled through the independent-entity requirements rather than having the PHA make the specified determinations about its own property.
Failed Completion Review Means No Standard HAP Contract Yet
The HAP contract does not automatically follow simply because the AHAP deadline arrived.
If the required development was not completed in accordance with the applicable requirements, or the units do not satisfy the required inspection and quality standards, the normal conditions for PHA acceptance have not been met.
The currently listed HUD Agreement form provides that when the PHA does not accept the work, it notifies the owner and gives the reasons for non-acceptance. The parties do not execute the HAP contract for those units at that point.
The applicable project documents and PHA determine what correction or other contractual action follows.
Successful Acceptance Leads to the HAP Contract
Once the PHA determines that the development was completed in accordance with the applicable requirements and the completed units satisfy HQS and any additional approved standards, the project reaches the next contractual stage.
The PHA submits the HAP contract for execution by the owner and executes the HAP contract for the accepted units.
This distinction is fundamental:
- AHAP or Development Agreement: governs qualifying development before the ordinary initial HAP contract.
- Completion review: establishes whether the agreed development requirements were actually satisfied.
- Inspection and PHA acceptance: establishes whether the completed units meet the required housing standards.
- HAP contract: establishes the contractual basis for PBV housing assistance payments for accepted contract units.
The Agreement is therefore a bridge to the HAP contract, not the HAP contract itself.
Projects Can Reach the HAP Contract in Stages
A large development does not necessarily have to wait until every proposed contract unit is completed before any qualifying units can enter the HAP contract.
Current §983.156 permits staged completion for qualifying newly constructed and rehabilitated projects that are following the ordinary pre-HAP development route.
The PHA separately determines whether each stage has satisfied the development and inspection requirements.
After the first accepted stage, the PHA and owner execute the HAP contract. As later stages satisfy the requirements, the HAP contract is amended to add those units.
The Post-HAP Rehabilitation Rider Is Still Delayed
The current CFR contains a separate HOTMA option that would allow certain rehabilitated housing to conduct development activity after HAP contract execution using a required rider.
HUD has delayed that flexibility indefinitely while it develops the required rider.
As of August 2026, PHAs cannot treat the delayed option as operational simply because §§983.154(g) and 983.157 appear in the regulatory text.
This is different from §983.154(f), the already-effective flexibility that can allow a PHA to proceed without a prior AHAP or to execute the Agreement after compliant development has commenced.
HUD Is Still Updating the PBV Agreement Forms
HUD's current PBV forms page continues to list HUD-52531-A and HUD-52531-B for the Agreement to Enter Into a Housing Assistance Payments Contract for new construction or rehabilitation.
At the same time, HUD states that it is updating PBV forms to reflect the HOTMA Voucher Final Rule.
HUD's implementation guidance directs PHAs to continue using existing program forms until updated forms are published unless HUD gives different written instructions.
Where wording in an existing form conflicts with a HOTMA regulatory provision whose effective and compliance dates have passed, the current regulation controls.
That rule is particularly important for the AHAP because the current regulation now contains development-without-a-prior-Agreement flexibility that older form language was not designed around.
Do Not Confuse Project Selection, AHAP and HAP Execution
Three project milestones can sound similar but have different legal functions.
Project selection means the PHA has selected the project for PBV development under an authorized selection method. It does not itself establish Housing Assistance Payments.
The AHAP, when used, establishes the development agreement between the PHA and owner and sets the requirements the development must satisfy.
The HAP contract comes later under the normal development path, after the required work, completion review, inspection and acceptance have been successfully completed.
For a project already operating under an AHAP, the relevant question is therefore not simply whether construction is physically finished. The project record must show that the required development work was completed under the applicable PBV requirements and that the PHA accepted the units before they move into the HAP contract stage.