Affordable Housing Waitlist Management: Keep the List Current Without Breaking the Rules

A unit opens up. You call the top five names on the waitlist. Two numbers are dead. One letter comes back stamped return to sender. One person moved a year ago and never said a word. Affordable housing waitlist management is supposed to prevent this, and most lists still aren't ready for it when the moment comes.

One thing surprises a lot of operators: HUD doesn't tell you how many times to call, or how long to wait for a reply, before you can take someone off the list. Your own written plan does. Get that plan right, and the rest of this gets a lot less stressful.

What Does Affordable Housing Waitlist Management Involve?

Affordable housing waitlist management means taking applications, recording the date and time each one arrives, placing applicants in the right order by unit size and preference, and keeping their contact information current. It also means removing a name only for a reason your written plan allows, and keeping a record clean enough that an auditor could follow it start to finish. It's a narrower job than people expect, and it's worth reading what AI leasing can and can't do in affordable housing before handing any part of it to software.

Every field on that list matters: application date and time, head of household, income level, whether an accessible unit is needed, preference status, and unit size. Together, those fields are the evidence that your selection order was fair.

The properties that struggle here are usually running a list built for 50 names that's now carrying 300, with no system tracking who's been contacted and when.

What Do HUD's Rules Say About Keeping a Waiting List?

HUD's rule is that your Handbook 4350.3 tenant selection plan has to describe how the list is maintained, and the list itself has to stay chronological, auditable, and current. The major pieces break down like this.

Notice what isn't on that list. HUD never names a required number of contact attempts or a required response window before removal. That decision belongs to you, and it has to live in writing.

What Must Your Tenant Selection Plan Say About the Waitlist?

Your tenant selection plan has to spell out how the waiting list is maintained and when a name comes off it. HUD requires an opening-and-closing policy and an application process in the plan, and it lists updating the list as recommended, not required, which makes it easy to leave out.

Don't skip it. A plan that doesn't say how often you'll check in, or what counts as no response, leaves every removal decision looking arbitrary later. A file review can go sideways over this gap even when the removal was right, because nothing in writing said it was allowed.

Automation, when you use it, follows the plan. It doesn't get to rewrite it. If your plan says a six-month check-in, that's the rule, whether a person or a text sends the reminder.

How Is a LIHTC Waitlist Different?

A LIHTC waitlist runs on rules from your state housing finance agency's compliance manual and your own tenant selection plan, not a federal LIHTC waitlist statute. Oregon's compliance manual, for example, requires a chronological list with a written eligibility notice for every applicant. Ohio's tenant selection plan guidelines require the plan to describe the application and waitlist process, though the state doesn't formally approve the plan itself.

If a property layers LIHTC with HUD or USDA financing, it has to satisfy every program it sits under, not only the strictest one. That's a lot to track by hand, and it's one reason layered properties lean on a compliance system built to hold each program's rules instead of a spreadsheet with too many tabs.

How Do USDA Rural Development Waiting Lists Work?

USDA Rural Development waiting lists run under 7 CFR 3560.154, and they work differently from HUD's. Every application goes on the list, complete or not. A complete application gets a written notice within 10 days telling the applicant they're selected, waitlisted, or rejected. An incomplete one gets a 10-day notice listing what's missing.

Selection order runs by income tier before it runs by date: very low-income applicants first, then low-income, then moderate-income. Purge procedures have to be written into the property's management plan and based on how long the list is or how long an applicant is expected to wait. It's a different order of operations than HUD's straight chronological list, and mixing the two up is an easy way to fail a review at an RD-financed property.

Why Do Waitlists Go Stale, and What Does It Cost?

Waitlists go stale because people move, change numbers, and stop checking mail long before your six-month check-in comes around. Across HUD-assisted housing broadly, the average wait for subsidized housing ran around two years and one month in 2025, according to USAFacts. That's a long time for a phone number to stay the same.

Most people do carry a working cellphone. Pew Research found 98% of US adults own a cellphone and 91% own a smartphone, even among lower-income households. That's why a text can reach people a letter misses, though no reliable data yet shows whether it gets more replies.

An unanswered offer, meanwhile, costs real vacancy days. In the broader rental market, Apartment List's national data put average time to lease at 32 days in August 2026, after a 41-day high in January. A waitlist that can't confirm interest fast when a unit opens bleeds the same kind of time, earlier in the process.

What Can You Automate on a Waitlist, and What Has to Stay With Staff?

Outreach can be automated. Decisions stay with staff, as the split below shows.

This is where Leslie, Fortress's AI leasing assistant, fits, and where it stops. Leslie checks in with people on the waitlist and passes their answers to your team. Every new prospect hears from it right away, and anyone who goes quiet gets follow-up texts over a few days. When someone writes in Spanish, Leslie answers in Spanish, which matters for language access in affordable housing. The list itself, the order, the preferences, who gets removed, lives with staff inside Fortress online applications, alongside the applications and income documents.

Before texting anyone, get consent, honor stop replies, and check current texting-consent rules with counsel, since the FCC rules in this area are still moving.

How Do You Run a Waitlist Update Without Losing Good Applicants?

You run it by putting the update rule in your tenant selection plan first, then following it the same way every time. A few things that hold up under review: use more than one way to reach people, since HUD's own removal examples include mail that simply comes back undeliverable. Log every attempt, not only the last one. Before you remove anyone, check whether the non-response might be your own error or tied to a disability, since both require reinstatement at the original spot. Accommodation duties under the Fair Housing Act apply to waitlists too.

Keep a copy of the list from before and after every removal. If a reviewer ever asks why someone came off the list, that pair of snapshots is the answer.

When Don't You Need Automation for This?

You probably don't need automation if your list is short, your manager already calls everyone personally, and the waits stay well under a year. HUD's own signal for an excessive wait is a year or more. Under that, a phone, a spreadsheet, and a manager who keeps it updated might be all a small property needs.

The math changes once the list runs into the hundreds and the wait stretches past a year. That's when a few missed calls turn into missed vacancy days, and when a system built to check in and log the record earns its keep. That's the job software made for income-restricted operations is supposed to do.

A waitlist is a legal record first and a lead list second. Automate the reaching-out. Keep the deciding with people, every time.