How to Build a Rent Reasonableness Case for a PHA

Pricing · 11 min read · Reviewed by the Section8Max Editorial Team · Last updated 2026-08-12

A rent reasonableness case is a market-matching file, not a sales pitch. The strongest submissions make it easy for the PHA to compare your unit with unassisted units in the same submarket and see why the requested rent fits the evidence.

What reasonableness means

Reasonableness in the Housing Choice Voucher program means the contract rent cannot be above the rent for comparable unassisted units in the private market, and it cannot be above what the same owner charges for comparable unassisted units on the premises.
PHAs are required to compare the unit against comparable unassisted units and consider location, quality, size, unit type, age, amenities, services, maintenance, and utilities provided under the lease.
The review is not a general opinion about whether the rent feels fair. It is a file-based comparison against the local market evidence the PHA accepts.

In practice, the PHA is asking a narrow question: would a private, unassisted tenant pay this much for a similar unit in this market? HUD guidance says the rent must not exceed comparable unassisted rents, and the owner’s own unassisted rents on the property also matter. That means your packet should not argue value in the abstract; it should prove market comparability.

The reviewer also considers whether the comparison should be made on gross rent, meaning rent plus tenant-paid utilities when those utilities are tenant responsibility under the lease. If you do not identify utilities clearly, the reviewer can discount the packet or make its own gross-rent comparison from incomplete assumptions.

What the reviewer actually compares

A PHA reviewer usually starts with bedroom count, then checks whether the comparables are in the same submarket and are truly unassisted.
After that, the reviewer looks at the physical match: age, size, condition, unit type, amenities, and utilities arrangement.
The reviewer is trying to isolate whether the subject unit is meaningfully better or worse than the comps, not whether the asking rent is popular with tenants.

Bedroom count is the first filter because it is the most reliable way to avoid comparing unlike units. A 2-bedroom should be compared to other 2-bedroom units unless the PHA’s method explicitly allows a narrower substitute and the file explains why. If you submit a 1-bedroom or 3-bedroom comp without a strong reason, the reviewer can set it aside as non-comparable.

Same submarket matters because rents can change sharply across neighborhood boundaries, school zones, transit sheds, or rent clusters within the same zip code. HUD’s guidance allows PHAs to use market-area comparisons, and many agencies use database tools or local market files that are organized by location and bedroom size. Your packet should therefore define the submarket in plain terms: within roughly the same trade area, not merely the same city.

Age and condition should be described with observable facts. A recently renovated unit with updated kitchen, baths, flooring, and systems is not the same as a dated unit with original finishes. Amenities and utilities also matter because a unit with parking, in-unit laundry, central air, or owner-paid utilities may support a higher rent than a bare-bones comp if the evidence is documented.

How to choose five to seven comparables

Use five to seven comparables when possible so the reviewer can see a range rather than a cherry-picked single point.
Prefer unassisted leased units first, then current market listings only if your PHA accepts them or if you clearly label them as listing evidence rather than closed-rent proof.
Keep every comp in the same bedroom size, same or adjacent submarket, and close in condition and age whenever possible.

Five to seven comps is a practical target because it gives the reviewer enough density to confirm a pattern without burying the file. HUD’s webinar material recommends organized comparable sheets and side-by-side comparison data, which is exactly what a small, disciplined comp set provides. A packet with two comps often looks selective; a packet with fifteen comps often looks unfocused.

Start by building a universe of unassisted units in the same submarket and bedroom size, then remove obvious mismatches. Exclude subsidized units, senior-restricted units unless the subject is similarly restricted, and units that are materially farther away or in a different rent pocket. Then keep the closest matches on age, condition, and amenity profile, even if one or two of them are slightly lower-rent than your subject.

If you have to choose between a perfect address match and a better physical match, prioritize the physical match only when the submarket is still the same. The point is not to find identical twins; it is to find enough similar units that the PHA can reasonably conclude the subject rent sits within the market band.

How to apply and document adjustments

Document square footage by source, because size is one of the easiest factors for a reviewer to verify and the easiest to misunderstand.
Use simple dollar adjustments when possible and explain the logic in a sentence under the grid.
Do not apply every possible adjustment if it does not change the conclusion. Over-adjusting can make the packet look manufactured rather than market-based.

Square footage should be adjusted only when the difference is meaningful and the source is reliable. If the subject unit is larger than a comp, the comp usually receives an upward adjustment to reflect the extra size the subject offers; if the comp is larger, the comp usually receives a downward adjustment. The adjustment amount should be consistent across the packet, tied to a per-square-foot logic or to a local standard your PHA accepts, and clearly labeled as your working assumption rather than a universal rule.

Parking is usually a discrete amenity adjustment. If the subject includes reserved parking and a comparable does not, note whether parking is covered, assigned, or off-street, and give the adjustment only if the local market commonly values it separately. In-unit laundry and central air are often treated similarly: they are easy-to-understand amenities, but they only help if your packet shows that nearby unassisted renters pay more for them or if your PHA’s review method recognizes them.

Renovation recency is more subjective, so document it carefully. Instead of saying the unit is simply ‘renovated,’ state what was updated and when: kitchen cabinets, counters, appliances, bath fixtures, flooring, paint, HVAC, windows, or electrical/plumbing systems. If possible, include dated photos or invoices so the reviewer can see why a newer renovation should out-rank a dated comp.

Do not hide weaker adjustments inside vague language. If a unit has central air but the comp does not, say so. If the comp has an extra half-bath, say so. A good adjustment grid is transparent enough that another person could reproduce the logic from the page alone.

How to lay out a one-page packet

Use a one-page cover sheet, not a binder, unless the PHA asks for more. HUD materials emphasize organized files and one-page comparable data sheets.
Put the subject unit at the top, then the comparable grid, then a short note on utilities and sources.
If the PHA has a portal or form, mirror its headings exactly so the reviewer can transfer your data without retyping.

A one-page packet works best when it looks like a review tool, not a marketing flyer. The top of the page should identify the subject unit address or internal reference, bedroom count, square footage, list rent, utilities paid by owner versus tenant, parking, laundry, air conditioning, renovation date, and the date of the request. That gives the reviewer the basic facts before the comparison begins.

The middle of the page should be the adjustment grid with five to seven comparables, each on its own line. Include address or comp ID, bedroom count, square footage, distance or neighborhood, condition notes, amenity differences, unassisted status, reported rent, adjustments, and adjusted rent. Keep the columns clean and avoid explanatory paragraphs inside the grid.

The bottom of the page should contain a short source note and a short certification-style statement that the comps are unassisted to the best of your knowledge and were selected from the same market area. If you used listings, lease records, or public records, identify them. If utility data is estimated, say so and show the assumption.

Worked adjustment grid: one 2-bedroom unit

Subject: 2-bedroom apartment, 1,050 square feet, one reserved parking space, in-unit laundry, central air, renovated in 2024, tenant pays electric and gas, owner pays water/sewer/trash.
Assumed local adjustment logic for this example: $1.25 per square foot difference, $50 for reserved parking, $40 for in-unit laundry, $35 for central air, and $60 for a renovation completed within the last 24 months versus a dated interior.
Target support is the adjusted rent from the comp set, not the highest line item in the set.

Assumptions stated explicitly: the subject is a 2-bedroom unit in the same submarket as the comps; all five comparables are unassisted; all are treated as comparable market units by the owner or listing source; and the adjustment values are the landlord’s documented working assumptions for the packet, not a universal HUD formula. The subject is larger than most comps and has stronger amenity value, so the packet needs positive support to justify the requested rent.

Comp 1: 2BR, 1,000 sf, no reserved parking, no in-unit laundry, wall A/C, last dated update over 10 years ago, unassisted rent $1,720. Size adjustment: +$62.50 for 50 fewer sf than subject. Parking: +$50. Laundry: +$40. Central air: +$35. Renovation recency: +$60. Adjusted rent: $1,967.50.

Comp 2: 2BR, 1,030 sf, reserved parking included, in-unit laundry, central air, modest 2021 renovation, unassisted rent $1,810. Size adjustment: +$25. Parking: $0. Laundry: $0. Central air: $0. Renovation recency: +$20. Adjusted rent: $1,855. Comp 3: 2BR, 1,080 sf, no parking, no laundry, central air, dated interior, unassisted rent $1,760. Size adjustment: -$37.50 because the comp is larger by 30 sf. Parking: +$50. Laundry: +$40. Central air: $0. Renovation recency: +$60. Adjusted rent: $1,872.50.

Comp 4: 2BR, 980 sf, reserved parking, no laundry, no central air, 2023 renovation, unassisted rent $1,790. Size adjustment: +$87.50. Parking: $0. Laundry: +$40. Central air: +$35. Renovation recency: +$20. Adjusted rent: $1,972.50. Comp 5: 2BR, 1,060 sf, no parking, in-unit laundry, central air, 2024 renovation, unassisted rent $1,885. Size adjustment: -$12.50. Parking: +$50. Laundry: $0. Central air: $0. Renovation recency: $0. Adjusted rent: $1,922.50.

The adjusted range in this worked example is $1,855 to $1,972.50, with a midpoint around $1,918. Landlord-requested rent at $1,925 is supported by the cluster of adjusted comparables, especially because three of the five adjusted results sit at or above the proposed level and all five are within a tight band. If the PHA uses a more conservative method, the packet can still support a figure near the midpoint, but the file should not overstate the case beyond the evidence shown.

The key to this grid is transparency. Every adjustment is visible, every assumption is named, and the final supported rent comes from the comparable set rather than from a round-number ask. That makes it easier for the reviewer to accept the file, modify it slightly, or explain a counterfigure without rejecting the packet outright.

What gets a packet rejected

Rejected packets often have assisted comparables, including tax-credit or voucher units that are not truly unassisted.
Packets also fail when the comps are in a different submarket, have the wrong bedroom count, or do not explain utility responsibility.
Missing dates, missing sources, unexplained adjustments, and oversized rent gaps are common process reasons for denial.
If the owner’s own unassisted units at the property rent lower than the requested voucher rent, the PHA can use that as a ceiling or warning sign.

A packet is easiest to reject when it asks the reviewer to do the work that the owner should have done. If a comp is subsidized, stale, outside the rent pocket, or not actually comparable on bedroom count, the reviewer may simply discard it. HUD guidance is explicit that the comparison must be against comparable unassisted units, and some agencies also exclude units with restricted rents until those restrictions are shown to have expired.

Even good comps can fail if the file does not document utilities, because gross rent changes when the tenant pays more of the monthly housing cost. Likewise, if your packet says a comp has central air or renovation but gives no proof or date, the reviewer may treat the adjustment as unsupported. A packet that is mathematically neat but factually thin usually loses to a less polished file with better documentation.

Another common failure point is asking for a rent that is outside the observed range without a strong explanation. If the adjusted comp cluster supports roughly $1,850 to $1,975 and the requested rent is $2,100, the reviewer may either lower the rent or reject the file as unsupported. The more the ask depends on one outlier comp, the more fragile the case becomes.

How to act on it

Prepare the packet before lease-up or before a rent increase, because HUD requires reasonableness determinations before approval and before increases.
Match the PHA’s own portal fields and use the same words the reviewer will use: unassisted, bedroom size, submarket, utilities, amenities, condition.
Bring a backup version with the raw data and photos in case the reviewer asks for more detail.
Always confirm local procedures and utility standards with the PHA because each agency can apply its own administrative plan and review workflow.

Use the packet as a negotiation tool, not a confrontation tool. Submit the request with the clean one-page grid, a short cover note, and any backing documents the PHA wants. If the agency has a rent reasonableness database or a standardized certification form, fill it in exactly and keep your own copy of the source materials in case the reviewer asks for clarification.

If the PHA comes back with a lower supported rent, revise the packet instead of arguing from first principles. Often the fix is one better comp, a cleaner utility statement, or a more defensible adjustment for renovation or parking. If the local figure still does not support your target, you may need to reprice the unit for voucher leasing in that market.

For landlords and small investors, the operational goal is to build a repeatable file process. Keep a local comp sheet by bedroom count and submarket, update it regularly, and save photos, utility setups, and renovation dates so the next packet takes minutes, not hours. That discipline is especially important because PHAs re-determine reasonableness at lease-up and before rent increases, and they can revisit the file when FMR conditions change or HUD directs a review.

Frequently asked questions

What does rent reasonableness mean in the voucher program?

Reasonableness means the proposed voucher rent cannot exceed the rent for comparable unassisted units in the private market, and it also cannot exceed what the owner charges for comparable unassisted units on the premises. PHAs must compare the contract unit to comparable unassisted units using location, quality, size, unit type, age, amenities, services, maintenance, and utilities.

What should a one-page packet contain?

A strong packet usually includes the subject unit summary, five to seven comparable listings or leased units, a one-page adjustment grid, utility notes, and short market evidence showing why the requested rent is supported. The goal is to make the reviewer’s comparison simple, consistent, and easy to verify.

What causes a packet to be rejected?

Packets are often rejected when the comps are assisted units, too far away, from a different submarket, mismatched on bedroom count, or not documented well enough to support the adjustments. Weak packets also fail when the comparable set is too small, the utility responsibility is unclear, or the proposed rent is higher than the adjusted comp range.

Can I use a worked example as proof of approval?

Yes, but only as an illustration. The PHA still decides reasonableness based on its own method and local market evidence, so the numbers in any example should be treated as a model, not a guarantee.

How should a landlord act on this guidance?

Use the packet to show that the subject unit sits in the same market as unassisted, similar units, then ask the PHA to review the evidence before lease signing or a rent increase. Confirm local figures and utility treatment with your PHA, because procedures and databases differ by agency.