Skip to content

property management operations research

Auditing Reasonable Accommodation Request Records Without Judging the Request

A records audit design for reasonable accommodation requests in rental housing, separating intake completeness from the manager's decision, with privacy controls, routing states, and clear limits.

| 6 sources

Auditing Reasonable Accommodation Request Records Without Judging the Request
Table of contents

Research question and scope

This brief asks how a property management team can audit the records around a reasonable accommodation request without asking an administrative reviewer to judge the request itself. The distinction is the same one that separates a document check from an eligibility decision. Intake completeness is a record condition that a trained assistant can verify. Whether a requested accommodation is reasonable, whether it should be granted, and what conditions apply are decisions reserved for the manager and, where needed, qualified counsel.

The unit of analysis is one request episode at one property, from the first contact through the final recorded response. A request may arrive by phone, email, portal message, letter, or in person. It may be phrased as a question rather than a formal request. The audit checks whether the team captured it, routed it, protected it, and documented an answer. It does not score the merits.

The method is documentary and descriptive. It can show where a request sat without an owner, where medical information was stored in an unprotected folder, and where the response is missing. It cannot determine whether the manager's decision was legally correct. That requires a different review, with the applicable law, the property's policy, and the specific facts in front of the decision-maker.

Why intake records differ from decisions

An intake record answers factual questions. Who contacted the property, on what date, through what channel, and what did the resident ask for? Was the request acknowledged, and was it routed to the person authorized to decide? Those questions can be answered from a log without evaluating the resident's circumstances. They are administrative facts, and they are the proper scope of a records audit.

A decision record answers a different set of questions. Does the requested change relate to a disability, and is the supporting information sufficient? Is the request reasonable, and does it impose an undue burden or fundamentally alter the operation? Those questions require judgment, and the answer belongs to the manager or another authorized role. An assistant who starts answering them has stepped outside the process.

Mixing the two creates two problems. The resident may receive an informal opinion that the team cannot stand behind, and the file may lose the very evidence needed to review the decision. A clean separation gives the resident a clear path and gives the manager a complete record. It also makes the audit possible, because the reviewer knows which questions are in scope.

Define the request record

Start with a written intake standard that lists the fields every request record must contain. At minimum, record the resident and unit, the date and channel of first contact, the person who received it, the requested change in the resident's own words, and the name of the person to whom it was routed. Add the acknowledgment date and the current status. Keep the resident's own phrasing where possible, because a paraphrase can change the meaning.

The record should also show whether the request was linked to an existing file or opened as a new one. A resident may raise the same issue in a maintenance call and in a separate message, and the team should not create two unrelated records. A linking field prevents the manager from reviewing only half the history. It also prevents duplicate responses that contradict each other.

The standard should define what counts as a request. A resident who asks whether a policy allows a change may be making an inquiry rather than a formal request, but the safer practice is to capture the contact and let the manager decide. The intake reviewer should not screen out requests based on how they are worded. That judgment is exactly the kind of decision the audit is trying to keep in the right hands.

Keep medical information out of the general file

Requests often include medical information, and the general resident file is usually not the right place for it. Access should be limited to the roles that need the information to process the request. The intake record can state that supporting information was received and where it is stored without copying the details into a shared note. A separate reference keeps the general file useful without exposing sensitive material to every staff member.

A separate, access-controlled folder is easier to audit than a scattered set of attachments. The record should point to the folder or system reference, not to a personal drive or an email inbox. If the property uses a portal, the team should confirm who can see the upload before asking the resident to send sensitive records through it. A convenient channel that exposes information to the wrong staff member is not a control.

The audit table should use identifiers and redacted references rather than reproducing medical details. That practice keeps the working file small and reduces the chance that a copy circulates beyond the approved group. It also makes the audit itself safer to share with an owner or a compliance reviewer, because the evidence can be described without disclosing the resident's health information. A redacted reference is enough when the reviewer only needs to confirm that the source exists.

Design routing and response states

A small set of states keeps the process visible. A request can be received, acknowledged, routed, waiting on the resident, under review, answered, or closed. Each state should have an owner and a date. A state that does not change the next action is probably not worth tracking, and a status that stays open for months without a note is a signal that the process has stalled.

The routing state is often the weakest link. An assistant may forward a message to a manager and consider the request handled. Unless the manager acknowledges receipt, the request has no confirmed owner. The record should show the handoff and the acceptance separately. That distinction is the same one that matters in any maintenance escalation, and it is especially important here because the resident is waiting on a decision.

Response states should distinguish an interim reply from a final decision. Acknowledging a request is not the same as answering it. The record should show what the resident was told at each stage and who authorized the message. If the manager needs more information, the request to the resident should state what is needed and by when, without asking for more than the review requires.

Sample requests without selecting only easy files

A full review is appropriate when the volume is small. When sampling, stratify by property, channel, and outcome so the sample does not consist only of requests that were resolved quickly. Record the selection rule and the population size before drawing the sample. A sample chosen after the fact can accidentally exclude the stalled cases that most need attention.

Compare the request log against the resident message queue and the manager's calendar. Count requests that appear in one system but not the other. A message that was answered verbally may have no written record, which is a gap even when the resident was satisfied. The audit should note the gap rather than assume the conversation happened as described.

Repeat the check after the first repair cycle. If requests are still sitting in an unassigned state, the cause may be an unclear routing rule rather than a careless reviewer. The next repair should change the rule or the system, not add another reminder to the same queue. A control that depends on memory will fail again when the office is busy.

Privacy, retention, and access

Access to request records should be limited to the roles that need it, and the list of authorized roles should be reviewed when staff change. A temporary reviewer who leaves the team should not retain access to a folder of sensitive requests. The audit should confirm that access was removed and that any working copy was returned or destroyed under the manager's policy. That confirmation belongs in the audit file with a date and a named owner.

Retention should follow the property's written policy and qualified legal advice. The audit should record the schedule it applied rather than assume one. The Internal Revenue Service publishes general recordkeeping guidance at irs.gov, but housing records may also be shaped by fair housing, state, and local requirements. A schedule that cannot be stated is not a control.

The working table should not become a second archive. Keep source documents in the approved system and use references in the audit file. When the audit is complete, decide whether the working file is retained, redacted, or destroyed. That decision should be recorded, because an unmanaged working copy is a privacy risk even when the original record is well protected.

What the audit cannot prove

The audit cannot prove that the manager's decision was correct. It can show that the request was captured, routed, and answered within the team's process. Whether the answer met the legal standard depends on the Fair Housing Act, the Rehabilitation Act where it applies, state and local law, and the specific facts. HUD's fair housing guidance at hud.gov describes the framework, but an operational audit is not a legal opinion.

The audit also cannot prove that the resident understood the response. It can show that a message was sent and what it said. Clear language, a named contact, and a stated next step improve the chance of understanding, but they are not proof. A follow-up offer is a separate step that the manager may choose to document.

Finally, the audit cannot prove that no request was missed. It can only describe the requests that entered the record. A resident who never contacted the property, or whose message went to an unmonitored inbox, will not appear in the sample. That limit should be stated plainly whenever the results are shared.

Practical takeaways

  • Separate intake completeness from the manager's decision in the written process.
  • Record the resident's request in their own words and name the person it was routed to.
  • Store supporting medical information in an access-controlled location, not the general file.
  • Track received, acknowledged, routed, waiting, under review, answered, and closed with dates.
  • State the audit's legal limits and route every substantive decision to the authorized role.

Sources