PBV Program Cap vs Project Cap: How the Limits Work
PBV program cap vs project cap refers to two different federal limits on Project-Based Voucher assistance. The program cap limits how much of a public housing agency's voucher portfolio may be committed to PBV, while the project cap limits how many PBV-assisted units may be concentrated in one project. Under current 24 CFR Part 983, the general PHA-wide limit is 20 percent of authorized voucher units, with additional authority and exclusions in qualifying circumstances. The general project limit is the greater of 25 units or 25 percent of dwelling units, again subject to higher limits, exceptions, and exclusions.
Those numbers cannot be applied in isolation. A PHA must determine which units count, whether an increased cap applies, whether any units are excepted or excluded, and whether sufficient voucher budget authority is actually available. For the national renter-facing framework, start with the complete Project-Based Voucher housing guide. This page focuses only on the cap calculations and how they constrain PHA and project design.
The Two PBV Caps Answer Different Questions
The federal rules use two separate controls because they address two different risks. The PHA-wide program cap controls how much of the housing authority's voucher platform can be committed to project-based assistance. The project cap, sometimes described as an income-mixing requirement, controls how much PBV assistance can be concentrated within an individual project.
- Program cap: How many of the PHA's authorized voucher units may be committed to PBV?
- Project cap: How many units in one project may receive PBV assistance?
A project can fit within the PHA's remaining program capacity but still exceed the project cap. The reverse can also happen: a proposed property might satisfy the project-level percentage, but the PHA may not have enough remaining program-cap authority or budget authority to commit the units.
The General PBV Program Cap Is 20 Percent
Under current 24 CFR § 983.6, a PHA generally may commit project-based assistance to no more than 20 percent of its authorized voucher units at the time of commitment, subject to the increased-cap and exclusion rules. This is a unit-based limit tied to authorized vouchers, not a simple percentage of annual HAP spending.
The rule looks at PBV units the PHA has selected as well as units already under an Agreement or HAP contract, except for units that qualify for exclusion under the federal rules. That means cap management begins before a property reaches ordinary occupancy.
The PHA is also responsible for determining how much budget authority is available. Having statutory room under the percentage limit does not itself create money for a new PBV commitment. The PBV program-design guide explains how cap capacity fits into the PHA's broader decision to use HCV resources for project-based assistance.
Authorized Voucher Units Are Not the Same as Occupied Vouchers
The 20 percent rule is based on the PHA's authorized voucher units as defined under the voucher regulations. It is not calculated by counting only families currently leasing units, only vouchers issued to applicants, or only vouchers being used successfully in the private market.
This distinction matters because a PHA's authorized voucher count is a program measure, while current utilization can rise and fall. The broader Housing Choice Voucher guide explains the tenant-based HCV framework that shares the same overall voucher platform with PBV.
The Additional 10 Percent Is an Increased Cap, Not a Universal 30 Percent Rule
Current Part 983 allows a PHA to project-base an additional 10 percent of its authorized voucher units when the additional units satisfy specified federal conditions. It is therefore misleading to state that every PHA simply has a 30 percent PBV cap.
The additional authority is tied to qualifying units. Under current § 983.6, eligible categories can include units specifically made available for households experiencing homelessness, families that include a veteran, qualifying supportive housing for persons with disabilities or elderly persons, units in areas where vouchers are difficult to use, certain replacement units on a different site, and qualifying units exclusively made available to eligible youth under the statutory youth authority.
The applicable HAP-contract timing and occupancy requirements also matter. Some categories require the contract to identify and set aside the qualifying units, and the household occupying the unit must satisfy the relevant category for the unit to retain that increased-cap status.
Homeless-Targeted Units Can Support the Increased Program Cap
Units specifically made available to households that meet the federal definition of homeless can qualify for the additional program-cap authority when the regulatory requirements are met. The category is not satisfied merely because a property sometimes rents to a household that has experienced housing instability.
The qualifying PBV units must be structured for the category required by § 983.6, and the occupancy rules in § 983.262 determine how the status is maintained. A PHA should therefore document the category rather than count a unit toward the increased cap based on an informal description of the resident population.
Veteran Units Can Qualify for Additional PBV Authority
The increased-cap rule also recognizes units specifically made available to families comprised of or including a veteran, using the veteran definition in the PBV rule. This authority is broader than simply labeling a project “veteran friendly.” The unit must qualify under the federal increased-cap requirements.
HUD-VASH can intersect with project-based assistance, but specialized HUD-VASH requirements should be checked separately when that program is involved. The cap rule by itself does not determine every eligibility, referral, or service requirement for a veteran household.
Supportive Housing Can Qualify Under the Increased Program Cap
Qualifying supportive housing for persons with disabilities or elderly persons can also support the additional 10 percent authority. Under current rules, supportive services must be reasonably available to assisted families in the project and tailored to resident needs, while the PHA's Administrative Plan must describe the type and availability of services it will recognize for this purpose.
The family is not simply required to accept any service management chooses to call supportive. The federal rule contains specific occupancy and service-related requirements, and changes in family composition can affect how the PHA treats an increased-cap unit.
Areas Where Vouchers Are Difficult to Use Can Qualify for More PBV Authority
One of the most important current HOTMA-related flexibilities is the “area where vouchers are difficult to use” category. HUD currently identifies these areas using federal criteria that can include low-poverty census tracts, ZIP codes with very low rental vacancy rates, and ZIP codes where the relationship between Small Area Fair Market Rents and metropolitan or county FMRs meets the regulatory threshold.
When a project is in a qualifying area, units can potentially use the additional 10 percent PHA-wide authority. The same geographic designation can also raise the project-level cap from the general 25 percent framework to the higher 40 percent framework. Those are separate effects of the same area designation.
The General Project Cap Is the Greater of 25 Units or 25 Percent
The second half of PBV program cap vs project cap is the project-level limit in § 983.54. Unless a higher cap, exception, or exclusion applies, a PHA may not select a proposal or enter into an Agreement or HAP contract if PBV-assisted units would exceed the greater of:
- 25 PBV-assisted units; or
- 25 percent of the dwelling units in the project.
The phrase “greater of” is crucial. In a small project, 25 units may be the controlling number even when that represents more than 25 percent of the property. In a large project, 25 percent may permit more than 25 assisted units.
A Simple Project-Cap Example
Suppose a project contains 60 dwelling units and no exception, exclusion, or higher-cap rule applies. Twenty-five percent of 60 is 15, so the greater number is 25. The general project cap would therefore allow up to 25 PBV-assisted units, assuming the PHA also has sufficient program-cap capacity and budget authority.
Now consider a 200-unit project. Twenty-five percent is 50 units, which is greater than 25. The general project cap could therefore be 50 PBV-assisted units, again before considering any exceptions, exclusions, or separate PHA-wide limitations.
These examples explain the math only. They do not determine whether a real project is eligible for PBV or whether a PHA may select it.
Qualifying Difficult-to-Use Areas Can Raise the Project Cap to 40 Percent
If the project is located in an area where vouchers are difficult to use under the current federal definition, the project cap can rise to the greater of 25 units or 40 percent of the project's dwelling units, subject to the remaining rules.
For a 200-unit qualifying project, 40 percent is 80 units, so the higher project cap could be 80 before adding any units that are separately excepted or excluded. This geographic flexibility is distinct from the additional 10 percent PHA-wide program authority even though the same “difficult to use” designation can affect both calculations.
Project-Cap Exceptions Can Allow More Assisted Units
Some PBV units are not counted toward the project cap because the units qualify for a federal exception. Under current § 983.54, the principal categories include units exclusively serving elderly families, units exclusively made available to qualifying eligible youth, and units exclusively made available to households eligible for qualifying supportive services.
A project is not limited to using only one exception category. It can contain different categories of excepted units when each category is properly supported. The HAP contract must specify the number of excepted units that are set aside for qualifying families, and an excepted unit must actually be occupied by a family that qualifies for the applicable exception.
Elderly Units Can Be Excepted From the Project Cap
Units exclusively serving elderly families as defined by federal rules do not count toward the ordinary project cap when the exception is properly used. This is a project-cap exception, not necessarily an exclusion from the PHA-wide program cap.
That difference is important. A unit can be outside the project-cap count while still affecting the PHA-wide program-cap calculation unless another rule separately changes its program-cap treatment.
Eligible Youth Units Can Receive Project-Cap Treatment
Units exclusively made available to eligible youth under the applicable statutory authority can also be excepted from the project cap. Where Family Unification Program assistance normally available to both eligible families and youth is limited to youth for this purpose, the PHA must make and document the required local-needs determination and reflect the policy in its Administrative Plan.
The youth category can also interact with the increased PHA-wide program cap under separate requirements. A PHA should therefore identify which cap rule it is applying instead of using “youth exception” as a generic label for both calculations.
Supportive-Services Units Can Be Excepted From the Project Cap
A project may also use the supportive-services exception for units exclusively made available to households eligible for services that meet the PBV requirements. Current regulations require qualifying services to be reasonably available and designed to help residents achieve self-sufficiency or live in the community as independently as possible.
The PHA must describe the qualifying services and related policies in its Administrative Plan. The resident generally cannot be required to participate in supportive services as a condition of living in the excepted unit, even though eligibility for the service structure is what supports the exception.
Excepted Units and Excluded Units Are Not the Same Thing
This terminology creates some of the most common cap mistakes. An excepted unit is generally a unit that remains within the PBV structure but is not counted toward the project cap because it qualifies under an exception such as elderly, youth, or supportive-services occupancy.
An excluded unit under § 983.59 is treated differently. Qualifying units do not count toward either the PHA-wide program cap or the project cap. The regulation also adjusts the relevant denominator when those units are excluded from the cap calculations.
Calling both categories simply “cap exempt” hides important differences in how the PHA must calculate and document them.
Some Previously Assisted or Rent-Restricted Units Can Be Excluded From Both Caps
Current § 983.59 provides a separate exclusion for qualifying units connected to specified forms of prior federal assistance or federally required rent restrictions, subject to detailed timing and conversion requirements. The listed categories can include former Public Housing assistance, PBRA or Moderate Rehabilitation assistance, Section 202 or 811 assistance, and certain other HUD programs.
The rule also identifies units previously subject to qualifying federally required rent restrictions, including Low-Income Housing Tax Credit restrictions and certain other federal programs. A past subsidy or rent restriction does not automatically create an exclusion; the exact § 983.59 requirements must be satisfied.
This is why program identity matters. The PBV versus PBRA comparison distinguishes the voucher and Multifamily platforms, while the PBV versus LIHTC guide explains why a tax-credit affordability layer is not itself a voucher subsidy.
Replacement Housing Can Also Receive Special Cap Treatment
Section 983.59 contains rules allowing certain newly constructed replacement units to be excluded from both caps when they replace qualifying assisted or rent-restricted units and satisfy the current federal location and redevelopment requirements. The 2025 amendment to Part 983 updated this replacement-housing provision, so older summaries should not be used without checking the current text.
Only the number of qualifying original units receives the exclusion. If the new PBV development creates more units than the number eligible for exclusion, the excess units remain subject to the ordinary program and project caps.
This issue often arises in properties moving away from older public-housing or project-based subsidy structures. The PBV versus Public Housing guide explains why a former or PHA-owned property should be classified by its current assistance platform rather than its name or history.
An Excluded Unit Cannot Also Double-Dip Into the Other Cap Exceptions
The current rule prevents a PHA from using the same excluded unit under § 983.59 to also claim the additional 10 percent program-cap authority or the ordinary project-cap exception. The exclusion already removes the unit from the relevant cap treatment.
This prevents stacking multiple cap benefits onto the same unit. The PHA must classify each unit correctly and apply the appropriate regulatory treatment once.
The Denominator Can Change When Units Are Excluded
Cap calculations are not always as simple as multiplying the PHA's headline voucher count or the project's advertised unit count by a percentage. Section 983.6 removes qualifying excluded units from the authorized-voucher-unit base for purposes of calculating the PHA-wide percentages, while § 983.54 removes excluded units from the project dwelling-unit count used for the project-cap percentages.
That adjustment is another reason a project-specific cap analysis should use the current regulatory calculation rather than a quick percentage taken from a property website or an old development memo.
Why a PHA Can Appear to Have More Than 30 Percent of Its Portfolio Project-Based
A simple 20 percent plus 10 percent explanation does not capture every lawful PBV portfolio. Units excluded under § 983.59 do not count toward the program cap, and historical transition rules can also affect existing contracts. Current § 983.6 additionally requires an impact analysis under § 983.58 when a PHA is project-basing 50 percent or more of its authorized voucher units.
Therefore, seeing a high apparent share of project-based units does not by itself prove the PHA violated the program cap. The correct analysis requires the unit classifications, contract history, exclusions, increased-cap categories, and current authorized-voucher calculation.
Cap Authority Does Not Guarantee Budget Authority
The percentage rules establish legal room to project-base units; they do not guarantee that the PHA has enough HCV funding to support the commitment. Section 983.6 separately makes the PHA responsible for determining available budget authority and keeping attached assistance within the amounts available under its ACC.
A project can therefore satisfy both the program cap and project cap and still be infeasible for the PHA because there is insufficient funding capacity. Cap compliance is necessary, but it is not the same as a funding commitment.
The Caps Do Not Decide Whether a Project May Be Selected
The cap calculations are one part of the PBV development process. A project must separately satisfy eligibility, site, environmental, selection, development, subsidy-layering, inspection, and contracting requirements as applicable.
This page deliberately does not decide whether a real project qualifies or explain the competitive selection process. Those are separate decisions. The PHA PBV program-design pillar shows where cap review sits in the overall process without replacing the dedicated project-selection pages.
The Caps Also Do Not Tell a Renter Whether a Particular Unit Has PBV
A renter cannot look at a 100-unit property, apply 25 percent, and conclude that exactly 25 apartments are PBV-assisted. The PHA may have chosen fewer contract units, a higher-cap rule may apply, some units may be excepted, or some may be excluded.
The actual assisted units are determined through the project's approved PBV structure and HAP contract. For renters comparing unit-linked assistance with ordinary portable voucher assistance, the PBV versus tenant-based Section 8 guide covers the practical difference.
Older HAP Contracts Can Require Separate Treatment
Current §§ 983.6 and 983.54 include transition provisions for contracts affected by earlier versions of the cap rules. For example, a PHA may not be required to reduce existing commitments merely because its authorized voucher count later decreases, and older HAP contracts can retain prior terms concerning certain excepted units.
This means a current development cannot always be analyzed by applying today's percentage to an old contract with no historical review. The contract execution date and any later amendments can matter.
HOTMA Changed the Cap Framework, So Old PBV Guides Can Be Wrong
HUD's 2024 HOTMA Voucher Final Rule comprehensively revised Part 983 and republished the modern program-cap and project-cap provisions. The rule became effective June 6, 2024, except for specifically delayed provisions unrelated to the core cap sections discussed here. Part 983 has also received later amendments, including changes affecting excluded replacement units.
HUD continues to maintain tools and guidance for current PBV implementation. A PHA, owner, developer, or housing researcher should therefore verify the current regulation before relying on an older handbook that describes the pre-HOTMA framework without the modern program-cap categories, geographic flexibilities, or revised exclusions.
How to Analyze PBV Cap Capacity in the Right Order
- Identify the PHA's current authorized voucher units. Do not substitute occupied vouchers or waiting-list size.
- Identify all PBV commitments that count toward the program cap. Include selected units and applicable Agreement or HAP contract units.
- Identify units qualifying for § 983.59 exclusion. Do not count them as ordinary capped units.
- Calculate the general 20 percent program authority. Use the regulatory adjusted base.
- Identify units eligible for the additional 10 percent authority. Match each unit to an actual qualifying category.
- Confirm budget authority. Cap room alone does not fund the project.
- Define the project and its dwelling-unit count. The project-level calculation depends on the correct project definition.
- Apply the general project cap. Start with the greater of 25 units or 25 percent.
- Check for the difficult-to-use-area 40 percent rule. Use current HUD geographic data.
- Identify project-cap excepted units. Elderly, eligible-youth, and qualifying supportive-services units may receive different treatment.
- Remove qualifying excluded units from the project calculation. Apply § 983.59 carefully.
- Review contract dates and transition rules. Older commitments may not be governed exactly like a new proposal.
Questions a PHA or Owner Should Resolve Before Relying on a Cap Exception
- What is the PHA's current authorized voucher-unit count?
- How many existing PBV commitments currently count toward the program cap?
- Which units, if any, qualify for the additional 10 percent authority?
- Does the PHA's Administrative Plan contain required policies for the category being used?
- Is the project in a HUD-identified area where vouchers are difficult to use?
- What is the correct number of dwelling units in the project?
- Which units qualify for a project-cap exception?
- Which units qualify for exclusion under § 983.59?
- Do replacement units satisfy the current location and redevelopment requirements?
- Does the HAP contract identify required set-aside or excepted units?
- Is sufficient HCV budget authority available?
- Does an older Agreement or HAP contract trigger a transition rule?
Common PBV Cap Mistakes
- Calling the PHA-wide cap and project cap the same thing. They limit different parts of the program.
- Saying every PHA may project-base 30 percent. The extra 10 percent requires qualifying units.
- Assuming the project cap is always 25 percent. The rule uses the greater of 25 units or 25 percent, with a possible 40 percent framework in qualifying areas.
- Counting excepted and excluded units the same way. They have different legal effects.
- Ignoring the denominator adjustment for excluded units. Section 983.59 can change the calculation base.
- Assuming a cap exception makes a project eligible. Other PBV requirements remain separate.
- Using an old HOTMA summary instead of current Part 983. Later amendments and implementation details matter.
- Assuming cap room equals funding. The PHA still needs sufficient budget authority.
PBV Caps Are Feasibility Limits, Not Promises of Assistance
The practical answer to PBV program cap vs project cap is that the first limit governs the PHA's voucher portfolio and the second governs concentration within an individual project. The general figures are 20 percent PHA-wide and the greater of 25 units or 25 percent at the project level, but qualifying increased authority, a 40 percent project framework in difficult-to-use areas, project-cap exceptions, and § 983.59 exclusions can materially change the calculation.
No single percentage proves that a project can receive PBV assistance. A defensible cap analysis has to classify the units, use the current authorized-voucher and project counts, apply the correct exceptions and exclusions, review contract history, and confirm available budget authority before the PHA treats the project as feasible.