HUD's 2026 ESA Shift: How Boards Should Respond

The board email that started the panic

The message lands in a community manager's inbox within a week of the May 2026 memo: "HUD changed the ESA rules. We can finally deny these. Draft a blanket policy." It usually comes from a board member who forwarded a headline, not the memo.

That instinct is the most expensive mistake a board can make right now. The enforcement posture shifted. The Fair Housing Act did not. An emotional support animal remains a reasonable accommodation, not a pet, and a board's duty to evaluate each request individually is exactly what it was in April 2026.

The boards getting sued in the back half of 2026 will not be the ones who granted too many requests. They will be the ones who read a memo as a green light, changed behavior overnight, and denied a 2026 request that looks identical to one they approved in 2023.

What actually changed vs. what didn't

Read the memo as a signal that HUD will scrutinize documentation more closely on both sides. That cuts against fraudulent letters, yes. It also means your denial file gets read with the same rigor. A denial with no individualized reasoning is now more exposed, not less.

The three ways a board manufactures its own liability

Fair housing exposure in ESA cases almost never comes from the substance of a decision. It comes from how the decision was handled. Three failures do the damage.

1. 01

   Delay

   A request sits in a board president's personal email for three weeks while the manager waits for the next meeting. There is no formal denial, but a functional one. Unreasonable delay in responding to an accommodation request is itself treated as a denial under fair housing principles.

2. 02

   Inconsistency

   The community approved a golden retriever ESA for Unit 214 in 2023 with a one-page letter. In 2026, emboldened by the memo, the board demands three forms and denies Unit 118 for an identical animal and identical documentation. That gap is the selective-enforcement claim writing itself.

3. 03

   Undocumented denial

   The board denies, but the file contains no record of what was requested, what documentation arrived, what reason applied, or when. When HUD or an owner's attorney asks for the record, there isn't one. An undocumented denial is nearly impossible to defend, regardless of whether the decision was correct.

“In an ESA case, boards lose on the calendar and the paper trail far more often than on the merits. The decision was usually defensible. Nobody could prove when it happened, why, or that the same standard applied to the last five owners.”

Todd Paton, Partner, One Home Agent

Where the human decides and where the agent absorbs the paper

The accommodation decision is a human judgment, full stop. No AI agent should grant, deny, or evaluate whether a disability-related need is credible. That is the board's call, on the record, ideally with counsel in the loop.

What breaks down in practice is not the decision. It is everything around it: the intake, the acknowledgment, the clock, the reason code, the consistency check against prior requests. That is documented, deadline-driven busywork, and it is exactly what an agent handles well.

This is the pattern behind a resident-facing agent like Riley Resident: it captures the request, logs it, acknowledges the resident neutrally, and routes it to the manager and board with the clock already running. The agent never says yes or no. It makes sure a human's yes or no is timely, consistent, and provable.

What the accommodation log actually looks like

The defense in an ESA complaint is a clean, timestamped, reason-coded log of every request the community has ever received and how each was handled. Here is a simplified version of what a well-kept log holds.

Notice what the log does. It shows Unit 118 in 2026 got the same treatment as Unit 214 in 2023. That single row of consistency is worth more in a HUD file than any policy document, because it proves the standard did not move when the memo dropped.

It also shows the board is not rubber-stamping. Unit 422 is pending pending documentation. Unit 509 triggered a legitimate direct-threat review. Both are individualized, both are documented, both are defensible. The log makes good-faith review visible instead of asking an investigator to take the board's word for it.

The 30-day clock is the silent failure point

Delay rarely happens on purpose. It happens because the request landed in a volunteer board member's inbox during hurricane prep, or the manager was on vacation, or it needed the next board meeting and the meeting got pushed. Nobody decided to stall. The calendar just ran out.

That is precisely the failure an agent is built to prevent. It does not decide anything. It refuses to let a request go silent. Day one it acknowledges. Day three it nudges the manager. Day seven it escalates to the board with the file attached. Day nine it flags that the reasonable-response window is closing. The human still makes every call, but the human is never the reason a delay became a discrimination finding.

What your attorney still signs off on

An agent absorbing the paperwork does not shrink your attorney's role. It sharpens it. Your counsel still owns the parts that require legal judgment, and no automation should touch them.