The Available Unit Rule, in practice

Every LIHTC compliance professional can recite the Available Unit Rule from memory: when a qualified household's income rises above 140 percent of the applicable limit, the unit keeps its low-income status as long as the next available unit of comparable or smaller size in the same building is rented to a qualified household. Reciting it is easy. Operating it, across a real property with real leasing pressure and real vacancy timing, is where credit risk actually lives.

The mechanics, precisely

The rule comes from Section 42(g)(2)(D)(ii) of the Code. A unit occupied by a household whose income has risen above 140 percent of the applicable income limitation (170 percent for deep rent skewed projects) does not immediately lose its status as a low-income unit. It continues to count, provided two conditions hold: the unit remains rent restricted, and each next available unit of comparable or smaller size in that building is leased to an income-qualified household until the applicable fraction is restored.

Three words in that sentence carry most of the operational weight: building, available, and comparable.

Building means building. The rule operates at the building level, identified by BIN, not at the property level. A property-wide over-income tracker that ignores which building a unit sits in is not tracking the rule at all, and this is the most common structural error we encounter in the field.

Available means the moment a unit could be leased, not the moment someone gets around to classifying it. The chronology of vacancy, application, and lease execution is exactly what a state agency reconstructs when it tests the rule.

Comparable or smaller means the obligation is not limited to identical floor plans. A two-bedroom over-income event can be cured or violated by what happens with the next one-bedroom vacancy in that building.

What a violation actually costs

If a next available unit in the building is rented to a nonqualified household while an over-income unit is relying on the rule, the over-income unit loses its low-income status. In a 100 percent low-income building the day-to-day risk is muted, since every unit is being leased to qualified households anyway. In a mixed-income building the rule has teeth: a single market lease executed in the wrong sequence can strip credits from a unit the owner believed was safe, and the applicable fraction moves with it. For average income test properties the analysis layers designated imputed income limitations onto the same machinery, which raises the tracking burden rather than lowering it.

What monitors look for

State agencies test the rule with three documents side by side: the recertification data that establishes when a household crossed 140 percent, the rent roll and vacancy history that establishes which units became available afterward, and the lease files that establish who those units went to and when. If a market-rate move-in postdates an over-income event in the same building, the burden is on the owner's documentation to show the sequence was compliant. Files that cannot demonstrate the chronology lose that argument by default.

Where owners trip up

The recurring failure points are consistent across portfolios. Tracking at the property level instead of the building level. Treating the rule as a year-end reporting exercise rather than a live leasing constraint. Losing the thread during acquisitions and management transitions, when over-income flags do not transfer with the files. Leasing teams that were never told a building is in next-available-unit status, because the compliance tracker and the leasing pipeline live in different systems. And thin documentation: a property can be substantively compliant and still generate findings because nobody recorded why each leasing decision was made.

Running it well

The properties that never have Available Unit Rule findings share a short list of habits. Over-income status is flagged at recertification and mapped to the building, not the property. Leasing staff see the flag inside their own workflow before a unit is offered. Every lease-up decision in an affected building is documented against the rule at the time it is made. And the tracker is reconciled after every acquisition and every staffing change, because the rule does not pause for transitions. A periodic independent LIHTC file review is the most reliable way to catch drift before a state monitor does.

The Available Unit Rule rewards operations that treat it as a standing constraint on leasing, and punishes operations that treat it as a compliance report. The difference between the two is rarely knowledge. It is plumbing.