Guides
How Landlords Document Assistance Animal Denials
A landlord's fair housing file for an assistance animal denial should connect individual evidence to a recognized ground, assess alternatives.
When a landlord considers denying an assistance animal request, a useful fair housing record does more than state a conclusion. It connects facts about the individual request to a recognized legal ground, records whether an effective alternative was considered, and explains the decision. The focus here is documenting that analysis, not checking the animal category or verifying a tenant's letter.
Name the governing standard
The federal starting point is the Fair Housing Act (FHA), which requires reasonable accommodations for people with disabilities. HUD's assistance-animal guidance provides guidance for applying that standard.
The Fair Housing Act also operates alongside state and local fair housing laws, so identify any additional protections that apply to the property.
HUD's FHEO Notice 2020-01, Assessing a Person's Request to Have an Animal as a Reasonable Accommodation Under the Fair Housing Act, is a named federal reference for evaluating these requests.
Section 504 of the Rehabilitation Act may also apply to housing that receives federal financial assistance. Keep the analysis tied to the law that applies to the property; do not treat a general policy or lease clause as a substitute for that analysis.
Connect each potential ground to evidence
Under the FHA, a proposed denial needs an individualized basis. The original file should identify which potential ground is under consideration and what facts support it. These are not automatic outcomes, and merely naming a ground does not establish that it applies.
| Potential ground | What the record should connect |
|---|---|
| Direct threat | Evidence about the specific animal and the safety risk it presents, rather than a general concern about animals. |
| Substantial property damage | Facts supporting a substantial damage concern tied to this request, rather than a prediction without specific support. |
| Undue financial or administrative burden | The actual financial or administrative impact on the housing provider. |
| Fundamental alteration | How granting the request would fundamentally change the nature of the provider's operations. |
For a direct-threat or damage concern, document what is known about the specific animal and whether the concern can be reduced. Photographs from a move-out inspection can show what existing damage looks like. A concern that can be addressed should not be written up as though it were an established, unavoidable risk.
For a burden or fundamental-alteration concern, state the operational impact rather than relying on labels such as "too difficult." Records kept as in property management bookkeeping basics are one source for the actual financial impact.
Build a fact-to-ground record
Keep the material that supports the decision together and make its purpose clear. A request file might include the request, relevant communications, the information considered, the ground assessed, and a short explanation connecting the evidence to that ground.
Use dates and identify the source of each fact so another staff member can reconstruct the reasoning later.
ESA Letter Verification Checklist
- Provider name, license type, number, state
- Date recent enough for current need
- Tenant name matches lease application
- Need statement describes how animal helps
- Signature and date from provider
The letter checklist shown above is an input to the file, not a denial test, and verifying an ESA letter is a separate task. A missing preferred detail, a suspicion, or a disagreement with a document does not by itself establish one of the grounds in the table. Keep any concern specific and verifiable, and avoid adding medical detail that is not needed to explain the decision.
Accommodation Request Workflow
- Log request with date and channel
- Ask one written question if needed
- Set review window, e.g. five days
- Answer in writing with reason
- Apply same terms, no pet fee
A request file should distinguish facts from conclusions. For example, record an observed event as an event, then separately explain why it matters to the ground being assessed. If the evidence is uncertain or incomplete, say so; do not present an inference as a proven fact.
Record alternatives before refusing as unreasonable
If the concern is that the requested accommodation is unreasonable, the provider must enter an interactive process before denying on that basis. Discuss with the requestor whether an alternative accommodation would effectively address the disability-related need.
A reasonable-accommodation guidance summary describes this requirement.
Record the alternative considered, the discussion, and why it would or would not address the need or the identified concern.
A reasonable accommodation must be granted unless it would impose an undue financial and administrative burden or fundamentally alter the nature of the provider's operations. Do not treat the word "unreasonable" as a finding; show the analysis behind it.
Write a decision that follows the record
A written denial should state the specific ground relied on, summarize the relevant facts, and explain how those facts support that ground.
If an alternative was discussed, briefly record its outcome. Keep the explanation limited to information needed to communicate the decision, and make sure it matches the case file rather than introducing a new reason at the last moment.
If the evidence does not support a ground, the record should not manufacture one from inconvenience or a general policy. A consistent file helps the property manager explain what was considered and why, while leaving room to reassess if the facts or request change.
