HUD narrows emotional-support-animal enforcement — and why Oregon providers can't change their workflows

The claim-precision ladder

This change is circulating under headlines like "HUD ends ESA protections." What the May 22, 2026 memorandum actually is — and is not:

• It is an enforcement memorandum, signed by Assistant Secretary for Fair Housing and Equal Opportunity Craig Trainor, titled Enforcement Guidance – Assessing Requests for the Use of an Animal as a Reasonable Accommodation Under the Fair Housing Act. It rescinds HUD's 2020 Assistance Animals Notice (FHEO-2020-01) and its 2013 predecessor (FHEO-2013-01).
• The new federal posture: FHEO states it will find reasonable cause of a Fair Housing Act violation only in cases involving animals individually trained to do disability-related work or perform tasks — borrowing the training component of the ADA's service-animal definition. HUD no longer expects housing providers to categorically extend trained-assistance-animal accommodations to untrained emotional-support animals.
• It is not a statute, and it is not a regulation. The Fair Housing Act's text is unchanged. HUD's reasonable-accommodation regulation, 24 CFR 100.204, is unchanged. The memo did not go through notice-and-comment rulemaking; it reflects how one federal office will prioritize its own enforcement.
• It does not govern Section 504 of the Rehabilitation Act or ADA complaints, and it does not prevent tenants from bringing private lawsuits under federal or state law.

What changed on May 22, 2026

For thirteen years, HUD guidance told housing providers that emotional-support animals — animals that provide disability-related support without individualized task training — generally qualified as assistance animals under the Fair Housing Act, and HUD investigated denials accordingly. The May 22 memorandum reverses that enforcement posture, effective immediately: complaints about untrained emotional-support animals are no longer expected to produce federal reasonable-cause findings or charge recommendations from FHEO.

Who feels this directly: federal fair-housing investigators, complainants choosing where to file, and housing providers calibrating federal exposure. Who should not change behavior because of it: providers in states with their own accommodation law — which includes Oregon.

The critical Oregon limitation

This memo does not safely authorize an Oregon housing provider to reject emotional-support animals or start charging pet deposits for them. Three independent layers of Oregon exposure remain:

1. ORS 90.300 prohibits a landlord from charging a pet security deposit for a service animal or companion animal that a tenant with a disability requires as a reasonable accommodation. That statute is untouched by anything HUD does.
2. ORS 659A.145 prohibits disability discrimination in real property transactions, including refusals of reasonable accommodation — and the Bureau of Labor and Industries continues to investigate and enforce it. A complaint that FHEO would now decline can still be filed with BOLI.
3. Private litigation under the Fair Housing Act and Oregon law remains available to tenants regardless of FHEO's enforcement priorities. Courts, not enforcement memos, decide what the statute means in a lawsuit.

The practical consequence: an Oregon denial that is "safe" under the new federal enforcement posture can still produce a BOLI complaint, a state-court claim, or a private federal claim. The memo changed one enforcement channel out of several.

Operational guidance for Oregon teams

1. Do not change accommodation workflows to auto-deny untrained emotional-support animals. The individualized process — verify disability, verify nexus between the disability and the animal, assess reasonableness, direct threat, and undue burden — continues exactly as before.
2. Keep the pet-deposit prohibition in place for qualifying service and companion animals under ORS 90.300.
3. Separate the layers in training and documentation. Staff should be able to say which standard they are applying: federal FHEO enforcement posture, HUD regulation, Oregon statute, or BOLI guidance. They differ now in a way they did not before May 22.
4. Label the change correctly in policies and knowledge bases: an enforcement-priority change by one federal office — not a repeal of the Fair Housing Act, not a change to 24 CFR 100.204, and not a change to Oregon protections.
5. Route disputed ESA denials to legal review. HUD, BOLI, state courts, and private litigants may now apply visibly different standards to the same fact pattern, which is precisely when counsel should be in the loop before a denial goes out.

Where FairSync fits

The risk this memo creates is a false green light: a manager reads "HUD no longer enforces ESA accommodations," updates a mental model, and denies a Vancouver-style request in Portland — where nothing about the applicable law actually changed. The gap between what one federal office will prosecute and what a landlord can lawfully do is exactly the kind of distinction that gets lost between a headline and a leasing desk.

FairSync's knowledge base stores this change the way compliance requires it to be stored: as a federal enforcement-priority entry, jurisdiction-tagged and cross-referenced against the Oregon statutes it does not displace. When a workflow touches an animal-accommodation request, the checks still run the individualized questions — disability, nexus, reasonableness, direct threat, undue burden — and a jurisdiction-aware warning fires before staff rely on the new HUD standard in a state with independent protections. Denials that would have been routine under the old federal guidance now return Escalate, because the channel that resolves them may be BOLI or a courtroom rather than FHEO. The memo changed who enforces; FairSync's job is making sure your team doesn't confuse that with what's lawful.

Coverage note: FairSync's compliance guidance is available for Oregon today, with additional jurisdictions expanding.