Oregon's real estate regulator draws a line: pet-screening portals can't gatekeep assistance-animal requests

The claim-precision ladder

• This is state compliance guidance, not a new statute. The Oregon Real Estate Agency — the regulator that licenses Oregon property managers — published guidance in September 2026 addressing third-party pet-screening platforms. The underlying fair-housing obligations are not new; what's new is the regulator expressly applying them to an increasingly common software workflow.
• The line it draws: a tenant or applicant requesting a service animal or emotional-support animal cannot be required to submit that reasonable-accommodation request through a third-party pet-screening service. There must be a direct route to the housing provider.
• The liability point: relying on the platform's recommendation does not relieve the housing provider of responsibility for properly handling the request. The vendor's "approve" or "deny" is an input at most — the accommodation decision, and the liability for getting it wrong, stays with the provider.
• What the guidance does not say: it does not prohibit pet-screening software. Using a portal for ordinary pets — pet rent, pet agreements, vaccination records, breed policies — remains a business choice. The problem is making that portal the mandatory gate for disability-related requests.

Why the regulator stepped in

Pet-screening platforms have become default infrastructure in property management, and many are configured so that every animal — pet or assistance animal — goes through the same portal, the same profile, and sometimes the same fee structure. The Fair Housing Council of Oregon has raised the same concern: offering such a service as an option is acceptable, but making it mandatory for assistance-animal requests imposes an extra barrier borne exclusively by people with disabilities — the defining shape of a fair-housing problem. A reasonable-accommodation request is valid however it arrives: an email, a letter, a conversation reduced to writing, or a portal form, not only the vendor's workflow.

The timing also matters. After HUD's May 2026 enforcement memo narrowed federal ESA enforcement (covered in a separate brief), some Oregon providers may assume animal-accommodation compliance generally relaxed. OREA's guidance is a statewide reminder in the opposite direction: Oregon's obligations — ORS 659A.145's accommodation requirements, BOLI enforcement, and ORS 90.300's prohibition on pet security deposits for qualifying service and companion animals — operate independently of federal enforcement priorities, and the state regulator is actively watching this exact workflow.

The compliance mistake this prevents

The failure pattern is quiet and systematic: the portal is wired into the application flow, so a resident's ESA request gets the vendor's standardized review; the vendor returns "not validated"; staff treat that as the answer and deny — or charge pet fees because the animal sits in the portal's "pet" bucket. Each step feels like following the system. Together they can produce an unlawful denial, an unlawful fee, or both — with the provider, not the vendor, holding the liability.

Operational guidance for Oregon providers

1. Split the workflows at intake. Ordinary pet registration can live in the portal. A service-animal or ESA request is a reasonable-accommodation request and must have a direct path to the housing provider — accept it by email, written request, an accommodation form, or any other reasonable method.
2. Audit policy language now. Any lease clause, listing, or move-in packet saying all animals "must be registered through [vendor]" needs a carve-out for assistance-animal requests.
3. Never treat the vendor's determination as the decision. The provider's own reasonable-accommodation process — disability and nexus review where permitted, reasonableness, direct threat, undue burden — makes the call, with the vendor's input weighed, not obeyed.
4. Keep fees clean. No pet deposits, pet rent, or pet fees for a qualifying service or companion animal required as a reasonable accommodation — ORS 90.300 prohibits the deposit, and fair-housing law reaches the rest.
5. Escalate the hard cases. Questionable denials, documentation disputes, direct-threat assessments, and multiple-animal requests belong in the provider's accommodation process with legal review — not in a vendor's automated queue.

Where FairSync fits

This guidance validates a fork FairSync's workflow layer is built around: animal_request_type = pet | assistance_animal, resolved at intake. The pet path can flow through whatever screening software the property uses. The assistance_animal path bypasses any mandatory portal requirement, accepts the request in whatever reasonable form it arrived, and runs the accommodation analysis — where a third-party vendor's approval or denial is recorded as an input but never returned as the decision. Denials, nexus-documentation disputes, direct-threat questions, and multiple-animal requests come back Escalate into the property's reasonable-accommodation process, and the fee checks enforce ORS 90.300's deposit prohibition automatically. The answer a FairSync user gets is grounded in reasonable-accommodation law — not in whatever determination an integrated pet-screening vendor happens to return.

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