Outsourced EmploymentPowered by StealthAgents

Practical guide

Build a workplace accommodation request log with dated responses

A request log that records the accommodation ask, the interactive step, the decision owner, and every dated response without collecting unnecessary medical detail.

Published

Practical guide illustration for Build a workplace accommodation request log with dated responses
Table of contents

Record the request at the point of contact

Write down what the employee asked for and the date the request reached the company. Use the employee's own words for the limitation or the task that is difficult, and keep the summary short. A request does not need a medical diagnosis to enter the log. The log should accept a plain statement that the employee needs a change to do the job.

Record who received the request and whether the employee was told what happens next. A manager who hears the request informally should route it to the named contact the same day. Send a short acknowledgment that repeats the request and gives a target response date. The acknowledgment is the first dated entry in the record.

Separate a request for accommodation from a performance or conduct concern that happens to involve a health condition. If the two are mixed, create linked entries with different owners. Do not let a performance process answer an accommodation question by silence. The log should show which decision each record supports.

Name the decision owner and the interactive step

Name one role that owns the accommodation conversation and one backup who can act during leave. The owner should have authority to approve a change or to escalate a hard question to counsel. Record the owner on the day the request is logged. A queue without a named owner is only a folder.

Describe the interactive step that was taken, such as a meeting, a written exchange, or a request for limited supporting information. Record the date and the people involved. The step should explore whether a change would let the employee perform the essential duties. The record should show a real exchange rather than a single form letter.

Write the decision with the reason and the effective date, even when the answer is yes. A simple approval that is never documented becomes invisible when the manager changes. For a denial, record the specific duty or constraint that was considered and the alternatives that were discussed. The employee should receive the decision in writing with a route to respond.

Set response dates that survive a handoff

Choose a target for the first substantive response and a second target for the decision. The targets should reflect the urgency of the request and the availability of information. Put both dates in the log and show them to the employee. A target is not a legal deadline, but it makes delay visible.

When the case moves to another owner, copy the open question and the next date into the handoff note. The new owner should not have to reconstruct the history from messages. Record the handoff date and confirm the employee was told who now owns the case. A silent transfer is a common source of missed responses.

Pause the response clock only for a stated reason, such as a waiting period the employee requested or a missing piece of information the owner actually needs. Record the reason and the date the pause began. Do not pause the clock because the owner is busy. The log should distinguish a real wait from an internal delay.

Protect the medical detail the log does not need

Keep the log focused on the limitation, the task, and the change requested. A diagnosis, treatment history, or medication list usually does not help the decision and should stay out of the working record. If supporting information is needed, ask for a narrow statement about functional limits. Store it separately with restricted access.

Give the log a small access list and review it every quarter. Managers should see the accommodation in place, not the medical file behind it. A shared drive with open permissions defeats the purpose of a restricted record. Record every access event when the system allows it.

Tell the employee who can see the record and what will be shared with the manager. A clear statement reduces the fear that a private condition will circulate. The manager needs to know the change and the schedule, not the reason. The log should make that boundary easy to follow.

Review the log for stalled requests

Review open cases each week by age and owner, and read the oldest cases rather than only the count. A case may be waiting on a decision, a document, or a meeting that was never scheduled. Record the specific blocker and the next date. The review should end with an action for each stalled case.

Look for patterns by department, manager, and request type. A cluster of delays in one team may mean the first contact does not know how to route a request. A repeated question may mean the process needs a clearer template. Report the pattern to the people who can change it.

After a case closes, confirm that the change actually reached the schedule, the equipment order, or the workspace. Record the effective date and the employee's confirmation. A decision that was never implemented is still an open request. The final entry should show that the accommodation is in place.

Sources

References supplied with this guide.

Article source directory
SourcePublisherContext
U.S. Equal Employment Opportunity Commission, Accommodation and Disabilityeeoc.govPrimary reference supplied with this article.
Job Accommodation Network, Accommodation Information by Disabilityaskjan.orgPrimary reference supplied with this article.
National Institute of Standards and Technology, Privacy Frameworknist.govPrimary reference supplied with this article.
U.S. Department of Labor, Recordkeepingdol.govPrimary reference supplied with this article.