Research: Separating Pet Policy Records from Assistance Animal Requests

Many rental teams keep one folder called pets and put everything animal-related inside it. That habit creates a specific problem. A reasonable accommodation request made by a resident with a disability can end up recorded and priced as if it were an ordinary pet approval, which obscures whether the correct process was followed. This research note proposes a simple separation model and explains how to record each path without collecting unnecessary information.

The note is about records, not about legal conclusions. Whether a particular assistance animal must be permitted is a legal and factual question for a qualified decision maker. The goal here is to make the difference visible in the file.

Methodology and scope

On September 18, 2026, we reviewed ten public sources from federal housing, disability rights, and information governance authorities. We used the HUD assistance animals page, the ADA service animal guidance, the ADA service animal topic page, the Fair Housing Act text at Cornell Law, the HUD Fair Housing Act overview, the DOJ Fair Housing Act overview, the eCFR Part 100 fair housing regulations, the HUD fair housing office page, NIST privacy framework, and NIST information quality standards. We then modeled two intake paths and applied them to hypothetical files.

No applicant, resident, animal, medical document, or property record was reviewed.

Why the separation matters

An ordinary pet policy is a business rule. It can set allowed species, size, number limits, pet rent, and deposits, subject to applicable law. An assistance animal request is an accommodation process under fair housing law. When the two are merged, several failures become likely. A pet fee may be applied to an animal that should not carry one. A species or breed restriction may be applied without evaluating the request. Or, in the opposite direction, an ordinary pet may be granted an accommodation label that was never requested, which makes the record inaccurate in a different way.

Separating the paths does not require two buildings' worth of overhead. It requires two clearly named queues and a rule that each has its own decision record.

The pet intake path

A pet record can reasonably capture the species, the number of animals, the applicable fees or deposits, the policy version, and the approval date. It answers a leasing and risk question: which animals are living in the unit under the standard policy. That is a legitimate operational record, and it should stay simple.

The pet record should not be used to store accommodation reasoning, and it should not be the evidence that an accommodation request was handled.

The assistance animal intake path

An assistance animal record should capture when the request was received, who received it, what was asked, what information the provider already had, what additional information was requested, who decided, when, how the resident was told, and when any approved accommodation took effect. A request may arrive in conversation, by phone, by email, or in writing. The HUD assistance animals page makes clear that formal paperwork is not the trigger; the request is.

Because the process can involve disability-related information, the file should record that the review happened without cataloguing medical detail. NIST privacy framework supports limiting collection and retention to the purpose at hand. A short note that a supporting document was reviewed, and by whom, is usually enough for the operational record.

Service animals and assistance animals are not the same label

The ADA service animal guidance and the HUD assistance animals page serve different legal settings, and teams that collapse them create reviewable errors. The file should name which framework the request was evaluated under and should avoid importing definitions from the other. The eCFR Part 100 regulations and the DOJ Fair Housing Act overview provide the housing-side framework.

Analysis: three predictable gaps

The first gap is the silent accommodation. The resident asked, the team agreed, and nothing was recorded. The animal is in the unit and there is no evidence of the process. This is hard to reconstruct later.

The second gap is the mislabeled pet. The animal was processed through the pet path, fees were charged, and the accommodation question was never asked. Whether this matters depends on the facts, but the record itself is wrong because it does not show that the correct question was considered.

The third gap is the undecided request. A request was received and possibly discussed, but no decision date or decision maker is recorded. From an operations standpoint, this is an open item that can age indefinitely.

A minimal intake practice

The operational goal is to make sure an assistance animal request never disappears into the pet queue. A short intake practice helps. When any team member hears a request, they open an accommodation record the same day, even if the only entry is that a request was made and needs review. The record then travels through review, decision, and implementation like any other tracked item.

The practice should also make clear that the resident does not need the right words. A request can be phrased as a question about a rule. The intake step is triggered by the substance of the ask, not by a specific phrase or a completed form. Recording the ask in the requester's own words preserves the ability to review it later.

Serving both paths without confusion

Separate records do not require separate service. A team can still greet every resident the same way and process animals through one front door. What changes is the routing after intake. The pet path continues to capture policy details. The accommodation path captures the review. The two records can live in the same system as long as each is labeled and each carries its own decision.

A simple quarterly check can confirm the separation is holding. Pull a sample of animal records and verify that each one is labeled as pet or accommodation, that accommodation records have a decision date, and that no pet fee appears on an approved accommodation where it should not. The check is quick, and it surfaces routing drift before it becomes a pattern.

Retention and access

An accommodation record may contain sensitive information, so limiting who can open it and how long it is kept matters as much as the intake itself. NIST privacy framework supports purpose-limited collection and controlled access. A team should be able to answer who can see the record, what happens when the tenancy ends, and how a resident request to review the file would be handled.

Inference boundaries

A clean file does not prove correct treatment, and a messy file does not prove a violation. The presence of a separate accommodation record shows that a process existed, which is useful for consistency review. It cannot establish that the outcome would survive a legal challenge. That determination belongs to a qualified decision maker and, if disputed, to an adjudicator.

Limitations

This model is administrative and does not decide whether a specific animal qualifies, whether documentation may be requested in a specific case, or how state and local rules modify the federal framework. It was not tested against live files. Urgent safety concerns should never wait on record reconciliation.

Practical measurement

A portfolio can audit a sample of animal-related records and count how many were routed to the correct path, how many have a recorded decision date, and how many show implementation. Reporting those three counts, with the sampling window fixed in advance, gives owners a reviewable picture. Readers who want to go deeper into the underlying process can read the companion note on reasonable accommodation request records, browse the wider research archive, or ask for a portfolio review.