Third-party verifications are where affordable lease-up actually stalls
Employer, asset, benefit, and landlord verifications age in inboxes while the occupancy report still looks fine. Treat them as a tracked queue with stale dates, not as a side task.
Ask a leasing coordinator where a file is and you will often hear 'waiting on verification.' That phrase hides the whole operation. Waiting on which request, sent when, to whom, for which household member. Without those fields, leadership sees applications in progress and assumes lease-up is moving.
Third-party verifications are the slowest legal step in many LIHTC and HUD files. Employers ignore the first fax. Benefit letters lag. Prior landlords do not call back. The coordinator chases in email. The PMS still says pending. No one has a list ranked by age.
The unit of work is the request, not the application
An application can be 'almost done' and still have three open verifications. Track each request as its own ticket.
- Household and member the request belongs to.
- Type: employment, asset, benefit, or landlord.
- Date sent, channel, and a stale threshold (ten days is a common internal flag).
- Status: not sent, outstanding, received, insufficient, ready for staff review.
If you cannot name the oldest unanswered verification this morning, you do not have a verification process. You have hope.
What an agent should do here
Classify incoming documents against open requests. Age anything unanswered. Draft a follow-up from an approved template. Put 'received, needs a human' in the compliance queue. Never decide that income is enough. Never send a notice that sounds like a denial.
That is the same command-center logic as lease-up overall, pointed at the step that actually burns calendar days. If your team is hiring occupancy coordinators while files sit on employer letters, map the verification queue first.
Common questions
- What is third-party verification in affordable housing?
- A request to an employer, bank, benefit agency, or prior landlord to confirm information the household cannot self-certify alone. In LIHTC and HUD files these requests often sit unanswered while the application looks 'in progress.'
- How should operators track outstanding verifications?
- Each request needs a household, a type, a sent date, and an age. The Monday report is how many are over 10 days old, not a count of applications received.
- Can AI send verification follow-ups on its own?
- It can draft them against approved templates and flag stale items. Staff review and send. The agent does not determine whether the response is sufficient for eligibility.