How a Housing Authority Creates and Operates a PBV Program
A Project-Based Voucher program begins with a decision by a public housing agency (PHA) to use part of its existing Housing Choice Voucher resources for rental assistance tied to specific units. HUD does not give a PHA a separate PBV funding award simply because it chooses to project-base vouchers. The PHA must design the local program, put required policies in its Administrative Plan, stay within federal program and project caps, select eligible projects, execute owner contracts, and operate waiting-list and occupancy procedures.
Not every housing authority uses this option. Participation is voluntary, and a PHA that chooses to use project-based vouchers remains responsible for complying with 24 CFR Part 983, applicable HCV rules, its own published policies, and current HUD implementation guidance. For the renter-facing national journey, use the complete Project-Based Voucher housing guide. This page focuses instead on how the PHA builds and administers the program itself.
A PHA Must Already Administer the Housing Choice Voucher Program
This is not a stand-alone grant program that a housing authority operates independently from HCV. Federal rules place project-basing inside the Housing Choice Voucher framework. The PHA already administers tenant-based vouchers under its consolidated Annual Contributions Contract with HUD, then chooses whether to attach some of that voucher assistance to specific housing.
That relationship is why many HCV rules continue to apply unless Part 983 says otherwise. The broader tenant-based program is explained in the Section 8 Housing Choice Voucher guide, while the PBV versus tenant-based Section 8 comparison shows how the two assistance models differ once a family is seeking housing.
Participation Is a Local PHA Choice
A PHA has discretion to operate a Project-Based Voucher program. HUD approval is not generally required merely for the PHA to decide to project-base vouchers, but the PHA must notify HUD of its intent and must make required notifications when it executes, amends, or extends a PBV HAP contract.
The PHA also must state in its Administrative Plan that it will engage in project-basing. That prevents project-basing from being treated as an informal side arrangement between a housing authority and a property owner. The local policy structure has to be visible in the PHA's governing program documents.
The Same HCV Budget Authority Funds Both Models
A housing authority does not receive an automatic additional pool of rental-assistance money when it creates this structure. The project-based assistance is funded from the appropriated budget authority available under the PHA's voucher ACC. The same overall voucher funding platform supports both tenant-based and project-based voucher assistance.
The PHA therefore has to consider more than the number of units it would like to project-base. Before making a commitment, it must determine that sufficient budget authority is available and that the proposed assistance fits within the federal limits on how much voucher authority can be attached to projects.
Project-Basing Changes How Part of the Voucher Portfolio Is Used
Tenant-based HCV generally gives an eligible household a voucher to search for a qualifying rental. Project-basing commits assistance to selected contract units instead. From a portfolio-management perspective, the PHA is deciding how much of its voucher platform should support portable tenant-based assistance and how much should support long-term affordability at identified properties.
That tradeoff can affect local housing strategy. A PHA may use this authority to support development, preserve affordable units, create housing in locations where vouchers are difficult to use, or serve populations connected to qualifying supportive-housing strategies. But the PHA cannot simply convert its entire voucher portfolio into project-based assistance without observing the federal cap framework.
The Administrative Plan Is the Local Operating Rulebook
Once a PHA chooses to operate a Project-Based Voucher program, its Administrative Plan must include the local policies over which the agency exercises discretion. Current Part 983 requires coverage of numerous subjects rather than a single sentence saying that the PHA offers project-based vouchers.
Depending on the PHA's choices, the Administrative Plan can address how a “project” is defined, qualifying supportive services, competitive and noncompetitive selection methods, project-cap policies, site-selection standards, inspection options, development procedures, HAP-contract amendments, waiting lists, owner-maintained lists, tenant screening, mobility procedures, and other locally determined policies.
For a renter or owner trying to understand why one PHA operates differently from another, the Administrative Plan is often the most important local document after federal regulations and the specific project contract.
The PHA Plan and the Administrative Plan Do Different Jobs
The PHA Plan is the housing authority's broader planning document for policies, programs, operations, local needs and strategic goals. HUD's current PHA Plan system includes a Five-Year Plan and, depending on the PHA category, an Annual Plan or annual planning requirements.
The Administrative Plan is more operational. It contains the PHA's detailed voucher policies. The two documents interact, but they should not be confused. For example, certain noncompetitive project selections require public notice of the PHA's intent through the Five-Year Plan, while the Administrative Plan must describe the procedures and circumstances for competitive and noncompetitive project selection.
The 2026 PHA Plan Process Is More Automated
HUD has modernized PHA Plan submissions through the Public Housing Portal. For PHAs with fiscal years beginning January 1, 2026, HUD requires use of the automated PHA Plan templates under current PIH guidance. That administrative change does not alter the underlying rule that local project-based policies must be consistent with current federal requirements.
For readers reviewing a housing authority's current program, the practical point is to use the latest PHA Plan and Administrative Plan rather than an archived policy manual that predates current federal implementation.
A PHA Cannot Project-Base an Unlimited Share of Its Vouchers
The general federal program cap permits a PHA to commit project-based assistance to no more than 20 percent of its authorized voucher units at the time of commitment, subject to current exclusions and adjustments. The rule also permits an additional 10 percent for qualifying units, including specified housing for people experiencing homelessness, veterans, certain supportive housing, units in areas where vouchers are difficult to use, and qualifying youth or replacement-housing circumstances.
Some units can also be excluded from the cap calculation under separate federal rules. Because those calculations depend on unit category, contract timing and local facts, the PHA must calculate its available capacity before issuing a request for proposals, making certain selections, adding contract units, or committing assistance.
Project Caps Are Separate From the PHA-Wide Program Cap
The PHA-wide cap answers how much of the housing authority's voucher portfolio can be project-based. The project cap answers how much assistance can be concentrated in one project.
Under current federal rules, the general project cap is the greater of 25 assisted units or 25 percent of the dwelling units in the project. In an area where vouchers are difficult to use, the higher cap is generally the greater of 25 units or 40 percent of the project's dwelling units. Federal exceptions and excluded units can change the result for qualifying projects.
These numbers are a design constraint, not an applicant eligibility rule. A renter cannot determine that a particular apartment is assisted simply by calculating a percentage of units in the building.
A PHA Must Check Capacity Before Selecting a Project
Current regulations require the PHA to calculate both the number of authorized voucher units it is permitted to project-base and the available budget authority before it takes key commitment actions. That sequencing matters. A project should not be selected first and treated as though funding and cap compliance can be solved later.
The PHA also must determine before selection that the proposed housing is eligible, complies with the applicable project cap, and satisfies federal site-selection standards.
Most Projects Must Be Selected Through an Approved Competitive Method
The PHA's Administrative Plan must describe its proposal-selection procedures. One common method is a PHA request for proposals (RFP) in which owners compete for project-based voucher assistance under published selection criteria.
Federal rules do not allow an RFP to be written so narrowly that it effectively limits proposals to one site or prevents owners from proposing different eligible sites. The selection process must remain consistent with Part 983 and the PHA's adopted Administrative Plan.
A Previous Government Competition Can Sometimes Support Selection
Current regulations also allow a PHA, under specified conditions, to select a proposal that was already chosen through a competitive Federal, State, or local housing, community-development, or supportive-services process. The prior competition generally must have occurred within three years of the PBV proposal-selection date, and that competition cannot have considered the future receipt of PBV assistance.
This option can allow a PHA to coordinate project-basing with other affordable-housing resources without duplicating an entire competition. It does not eliminate the PHA's responsibility to determine that the project satisfies the federal rules.
Some Projects Can Be Selected Noncompetitively
Part 983 contains exceptions that allow qualifying projects to be selected without the ordinary competitive process. Those exceptions are specific; they are not a general permission for a PHA to choose any favored property.
Before using a qualifying noncompetitive route, the PHA must give required public notice through its Five-Year Plan. Certain public-housing improvement, replacement, preservation, or other qualifying circumstances can support a noncompetitive selection when the regulatory conditions are met.
This is one reason PBV and traditional Public Housing should not be treated as the same program. A PHA may use PBV in a repositioning or replacement strategy while the resulting units operate under the voucher platform. The PBV versus Public Housing comparison explains that distinction, and the Public Housing guide covers the separate traditional program.
PHA-Owned PBV Projects Require Additional Safeguards
A housing authority can have an ownership interest in a PBV project, but the agency cannot simply evaluate itself as though no conflict existed. Current rules require independent review or HUD field-office involvement for specified PHA-owned functions.
For project selection, the HUD field office or an approved independent entity must review the selection process and determine that the project was appropriately selected under the procedures in the PHA Administrative Plan. Other independent-entity functions can include rent and inspection determinations.
The purpose is to preserve program integrity where the PHA is both administrator and an owner or ownership participant. The dedicated PHA-owned project rules deserve separate analysis and should not be reduced to the statement that “the housing authority owns the building.”
Site Selection Is Part of Program Design
A PBV project must satisfy federal site-selection requirements before the PHA can proceed. The housing authority must consider whether project-based assistance at the site is consistent with deconcentrating poverty and expanding housing and economic opportunities, along with applicable civil-rights and site-and-neighborhood standards.
The PHA's local standard has to be consistent with its PHA Plan and Administrative Plan. This makes location a program-design question, not merely a real-estate preference of the property owner.
Existing, Newly Constructed and Rehabilitated Housing Follow Different Development Paths
A PHA may project-base assistance in eligible existing housing or in housing that will be newly constructed or rehabilitated. The development path affects the steps required before the HAP contract becomes effective.
New construction and rehabilitation can involve an Agreement to Enter Into a HAP Contract (AHAP), development requirements, environmental review, inspections, evidence of completion, and other federal conditions. Current rules also provide specific alternatives in certain circumstances for development without an Agreement or for rehabilitation activity after HAP execution.
This program-design pillar only maps those choices. The exact construction, rehabilitation and contract sequence belongs to the development-stage pages.
The HAP Contract Turns the Selected Units Into PBV Contract Units
The core operating relationship is the Housing Assistance Payments contract between the PHA and the owner. The HAP contract identifies the assisted units and establishes the conditions under which the PHA makes housing assistance payments for eligible families occupying those units.
Current rules require the contract to identify matters such as the number and bedroom sizes of contract units, the project location, specific unit information, owner-provided services and utilities, accessibility features, the contract term, qualifying cap-exception units, and initial rent to owner.
A PBV HAP contract may have an initial term of up to 20 years for a contract unit, subject to current requirements, and extensions can be used within federal limits. Long-term contracts are one reason PHAs may use PBV as a preservation or development tool rather than relying entirely on individual tenant-based leasing transactions.
PBV Is Not HUD Multifamily PBRA
A PHA designing PBV remains inside the HCV platform. The owner contracts with the PHA, not directly through the ordinary HUD Multifamily PBRA contract structure.
That distinction becomes important when an affordable development uses several federal resources. The PBV versus PBRA comparison explains the administrator, contract, recertification and mobility differences between the two forms of project-based Section 8 assistance.
PBV Can Be Layered With LIHTC and Other Financing
A housing authority can use PBV in a property that also receives Low-Income Housing Tax Credits or other eligible public financing. The programs remain separate compliance layers. PBV provides voucher rental assistance to contract units, while LIHTC imposes tax-credit affordability requirements on qualifying units.
The PHA must also consider subsidy-layering requirements when other governmental assistance reaches applicable thresholds. The purpose is to prevent the project from receiving more public assistance than necessary to provide the affordable housing.
For the renter-facing distinction, the PBV versus LIHTC comparison explains why voucher subsidy, tax-credit rent limits and utility rules should not be merged.
The PHA Must Design a Waiting-List Structure
Operating a Project-Based Voucher program requires more than selecting properties. The PHA must decide how eligible families will reach those contract units and must describe its waiting-list policies in the Administrative Plan.
Current federal rules permit several structures. A PHA may use a separate central PBV list covering multiple projects, use the same waiting list for tenant-based assistance and some or all PBV projects, or use separate project- or building-specific lists. The PHA can also permit an owner to maintain an approved project-specific waiting list under the federal requirements.
This flexibility is why two PHAs can operate PBV very differently while both comply with federal law. The Public Housing versus PBV waiting-list comparison also shows why a PHA-run property list should not automatically be treated as a traditional public housing list.
Owner-Maintained Lists Do Not Transfer Final Eligibility to the Owner
If the PHA permits an owner-maintained PBV waiting list, the owner must follow a waiting-list policy approved by the PHA and incorporated into the PHA's Administrative Plan. Project preferences also require PHA approval.
The owner may select and refer a household from the approved list, but the PHA still makes the final federal program-eligibility determination before the family can receive PBV assistance. This preserves the distinction between owner tenant selection and PHA voucher administration.
The PHA Controls Federal Program Eligibility and Occupancy Administration
Applicants for PBV units must come through the applicable PBV waiting-list structure, and the PHA determines federal eligibility at the required point before assistance begins. Once units are occupied, the PHA continues to perform the program-side functions assigned to it under HCV and PBV rules.
The owner remains responsible for the landlord side of the tenancy, including lawful tenant screening, leasing, property management and maintenance. Program design therefore has to define a working relationship among the PHA, owner, management agent and family rather than treating one party as responsible for everything.
A PHA Must Plan for Vacancies, Referrals and Occupancy
PBV works only when vacant contract units are matched with eligible households efficiently. If a PHA-maintained list is used, the owner must notify the PHA of vacancies and the PHA must make reasonable efforts to refer enough eligible families. If an owner-maintained list is used, the owner refers the selected household to the PHA for final eligibility determination.
The program therefore needs procedures for vacancies, referrals, applicant contact, project preferences, unit size, final eligibility and owner screening. Weak coordination can leave contract units vacant even where the community has substantial demand for affordable housing.
Local PBV Policy Must Stay Current as Federal Rules Change
HUD's 2024 HOTMA Voucher Final Rule substantially revised HCV and PBV regulations, and HUD has continued to update implementation materials. HUD also warns that some older PBV notices and forms predate the final rule and may contain provisions that are outdated or awaiting replacement forms.
PHAs should therefore administer the program from current regulations and current HUD implementation guidance rather than copying an older PBV Administrative Plan section indefinitely. A local policy that was accurate several years ago can become inconsistent with current Part 983 after federal amendments.
How to Review Whether a PHA Has Built a Real PBV Program
- Confirm that the PHA actually operates PBV. Not every HCV agency does.
- Review the current Administrative Plan. It should state that the PHA engages in project-basing and contain the required local PBV policies.
- Review the current PHA Plan where relevant. Look for strategic goals and any required notice connected to qualifying noncompetitive selections.
- Confirm available voucher authority and budget capacity. The PHA must stay within both financial and program-cap limits.
- Review the project-selection method. Determine whether the project was selected competitively or under a valid exception.
- Check the project cap and site standards. Selection must comply with the rules applicable to the specific project.
- Identify any independent review. PHA-owned units trigger additional safeguards.
- Confirm the development path. Existing, newly constructed and rehabilitated housing have different pre-HAP steps.
- Review the HAP contract structure. The contract identifies the actual assisted units and owner-PHA obligations.
- Review waiting-list and occupancy policies. A functioning Project-Based Voucher program needs a lawful route for families to reach vacancies.
Questions Owners and Community Partners Should Ask the PHA
- Does the PHA currently operate a PBV program?
- How much PBV capacity and budget authority is currently available?
- Which competitive and noncompetitive selection methods are authorized in the Administrative Plan?
- What types of projects and local housing needs does the PHA prioritize?
- How does the PHA define a project for cap purposes?
- What site-selection standards apply?
- Which waiting-list structure will be used?
- Does the PHA permit approved owner-maintained waiting lists?
- What development path applies to existing, rehabilitated or newly constructed housing?
- What independent-entity functions apply if the project is PHA-owned?
- What documentation will be required before HAP contract execution?
- How will PBV interact with LIHTC or other public financing?
PBV Program Design Is a Portfolio Decision, Not a Separate HUD Application for Renters
A private renter does not create a local Project-Based Voucher program by applying directly to HUD. The housing authority first decides whether to project-base part of its HCV resources and creates the local structure under federal rules. Applicants then use the waiting-list or project process established by that PHA.
That distinction also helps explain why PBV availability varies so widely by location. One PHA may use project-based assistance extensively for preservation, supportive housing or development, while another may rely primarily on tenant-based HCV. Neither outcome proves that PBV is automatically available in every jurisdiction.
A Strong PBV Program Connects Funding, Projects and Families
The core job of a Project-Based Voucher program is to connect limited HCV resources to eligible projects in a way that complies with federal caps, local planning, project-selection rules and long-term contract requirements while still creating a workable path for eligible families to occupy the assisted units.
For the PHA, the sequence is deliberate: decide to project-base, establish current policies, confirm budget and cap capacity, select eligible projects, satisfy development and site requirements, execute the HAP contract, and operate lawful waiting-list and occupancy procedures. Skipping one of those layers can turn a housing-development idea into a PBV compliance problem rather than a functioning rental-assistance program.