Skip forward into hiring notes
RosterAcorn

EEOC ADA guidance: 3 dates and your own check date

Keep 1999, 03/01/99 and 2002 from the EEOC guidance in your file, alongside your team's own check date.

Key takeaways

  • Save dated copies of the guidance pages you use.
  • Record the historical dates separately from your own check date.
  • Keep medical information accessible only to named reviewers.
  • Preserve old versions when you update your process.

If you run hiring or manage a small staffing team, someone will eventually ask which disability guidance your accommodation process follows. It might be an applicant's advocate, an auditor, a new HR partner, or your own director who wants the answer on paper. A clear answer with dates you can point to saves a lot of scrambling.

This post covers the dates and document details worth keeping in your file. It is written for hiring managers and team leads rather than lawyers, and it sticks to what the official EEOC and related pages say. The filing suggestions below are general practice. This is not a substitute for advice from counsel about your own situation.

What EEOC guidance should our accommodation process follow?

The main document is the EEOC's Enforcement Guidance on Reasonable Accommodation and Undue Hardship under the ADA, which is the document to cite when someone asks how the agency treats reasonable accommodation requests. For the broader picture, the EEOC's employer publication on the ADA explains what the law asks of employers in general terms. Use the enforcement guidance as your reference for the accommodation process itself and the employer publication as background.

Before you cite either page, save a dated copy or screenshot and write down the date you pulled it. Pages change, and your file should show which version your process was built on.

Which four dates should go in the file?

Four dates cover the history and currency of the guidance: 1999, 03/01/99, 2002, and the date your team last checked the page. The first two describe the guidance it replaced. The third is the year attached to a decision the guidance discusses. The fourth is your own record, because the guidance does not carry an end date.

  1. 1999: the year of the earlier guidance that this document replaced.
  2. 03/01/99: the date the Commission issued the earlier guidance, as printed on the page.
  3. 2002: the year cited for the Barnett decision, which the guidance says prompted its major changes.
  4. Your check date: the day someone on your team checked the guidance and its links for changes.

Keep these four together on one page in the file. Nothing about this set of dates replaces reading the guidance itself, which is where the detail lives.

Where did the 1999 and 03/01/99 dates come from?

The guidance itself says it replaced an earlier document. It states that it replaced a 1999 guidance document by the same name, and its purpose statement says it "supersedes the enforcement guidance issued by the Commission on 03/01/99." Put both dates in your file so anyone reading your records can see the lineage: the older document, the date it was issued, and the newer guidance that took its place.

Record the current document's publication date if one appears on the page. Keep your own check date separate from it.

Why does a 2002 citation matter?

It matters because the guidance ties its update to two reasons, and those reasons tell you where to look for changes. The first is the Barnett decision, which the document cites with a 2002 year. The second is "the Commission's issuance of new regulations under section 501 of the Rehabilitation Act," as the guidance puts it.

The guidance names section 501 of the Rehabilitation Act alongside the ADA, so pull that reference into the file if your team relies on it. The same document also points to where the major changes sit: pages 4-5, 44-45, and 61-62. When someone asks what changed, start there rather than skimming the whole document.

Does the guidance have an expiration date?

No fixed one. The notice on the page says that this Notice will remain in effect until rescinded or superseded, so there is no end date to put on a calendar.

How do I check whether the ADA pages have changed?

Check the employer publication first, because it says the law makes several significant changes, including changes to the definition of the term "disability." It also says the EEOC "will be evaluating the impact of these changes on this document and other publications." Because the EEOC has said it is evaluating that impact, the publication belongs on your recheck list.

The same page points to a list of specific changes to the ADA made by the ADA Amendments Act. Print that list and attach it to the file, so a reviewer can see which version of the definition your process used. The list tells you what changed. It does not tell you how your process should respond, so that part is a decision your team needs to document.

Where do the question-by-question answers live?

The Job Accommodation Network's accommodation process page refers readers to question 9 in the EEOC enforcement guidance. That kind of pointer is worth copying into your file. Note the question number, the page, and the date you read it, so a reviewer can find the same passage later without searching the whole document.

If your internal process uses its own numbered steps, mirror the numbering where it matches the guidance so the two line up. A reviewer who sees "step 3 relies on question 9" can check both in a minute.

What steps should our written process cover?

Five steps cover most of a written process: log the request, talk with the person, list the options, record the decision, and set a follow-up. A new supervisor should be able to follow them without calling you. The steps below are a general way to organize the work. They are not quotations from the EEOC, so check your version against the enforcement guidance and note the page or question you relied on.

  1. Log the request. Record the date it came in, the form it arrived in, and the name and role of the person who received it.
  2. Talk with the applicant or employee. Ask what they need and which part of the job or hiring step is hard for them. Write down what they tell you, in their words where possible.
  3. List the options. Note each arrangement you considered, what it would involve, and why you chose or set aside each one.
  4. Make and record the decision. Put the decision and its date in the file, along with who approved it.
  5. Set a follow-up date. Pick a date to ask whether the arrangement is working, and record the answer.

Keep the steps short. A process that fits on one page gets used, while a binder nobody opens rarely helps when a question comes up. For related reading, see the accommodation request guide.

How should we answer an applicant's advocate or lawyer?

Answer in writing with the official link and your own dated copy, and leave applicant medical details out of the reply. Public pages are easy to share, so the link and your copy of it are the right things to send. Internal notes, medical information, and anything about a specific person's file belong in a separate channel.

If the question touches a specific request, say that you will review the file and reply, rather than sharing your notes. If the message involves a dispute, a demand letter, or a question about what the law requires, pass it to your counsel before you respond. A short, calm reply that points to the guidance tends to work better than a long explanation of your own reasoning.

Keep a copy of what you sent and the date you sent it, so the exchange sits in the same file as the request. That way, the next person who reads the file sees what was said and when.

What belongs in each accommodation file?

Each file has two layers: shared material that applies to every request, and a separate record for each request. Keep the file short enough that a reviewer can read it in about five minutes, and organize it the same way every time. Put the shared material in one place and the individual request records in their own folders.

The shared material should include:

  • Dated copies of the EEOC guidance pages you rely on, with the web address and the date you pulled each one.
  • The note explaining the 1999 and 03/01/99 dates and the 2002 citation.
  • The list of ADA Amendments Act changes, as you saved it.
  • Your check dates and the result of each check.

Each request record should include:

  • The date the request came in and what was asked.
  • Who reviewed it, and what they relied on in the guidance, such as the page or question number.
  • The options considered and the decision, with its date.
  • Any follow-up date and what happened at follow-up.

A common practice is to keep medical details apart from general hiring records and to limit who can see them. Check with counsel on what applies to your organization, because the details depend on your size and setting. See also the medical documentation request guide.

What do we do when a guidance page changes?

Keep the version you used and add a note about the change rather than replacing your old copy. The old copy shows what your process was built on when a past request was decided, and the new copy shows what you now use. Save the new page with its own date, compare the two, and write a short summary of anything that touches your process.

If a change affects a step in your written process, update the process with a new date and tell the people who review requests. Do not quietly edit the old version. A dated change note is worth more than a clean-looking document with no history, because it shows that you checked and responded.

Illustrative example: recording a review

A team sets aside 10 minutes to review its saved guidance pages. The reviewer compares the saved copies with the pages, finds no change, and records the check date and result. The historical dates stay as they were; the new check date records this review, rather than becoming a new publication date for the guidance.

Who on a small team should own the file?

One named person should own the file, with a backup who can answer questions when that person is away. In a small team, the owner is often the hiring manager or the lead who handles most requests, but ownership and day-to-day handling do not have to be the same person.

Store shared guidance where the team can open it, but restrict request records containing medical information to named reviewers, with an access list you can explain to someone else. A private folder on one person's laptop is hard to hand over when that person changes roles. Set a calendar reminder for the review dates, so the schedule does not depend on memory.

Where do teams usually lose track of dates?

Teams most often lose track of dates when they save a page without its web address or date, or when they overwrite an old file with a new one and keep only the new name. A screenshot with no address shows what someone saw on one day, but it cannot show where the text came from.

Another gap is the difference between a request date and a decision date. Keep both, because a file that shows only the decision date makes the timeline hard to reconstruct. Also keep the date someone checked the guidance, not just the date the file was saved.

Today, open your shared guidance file and check whether each saved page has its web address and check date. Add any missing details before reviewing individual request records.

How do we explain the four dates to a non-lawyer?

Explain them in the order they happened: what the guidance replaced, when the replaced guidance was issued, what year the decision it discusses carries, and when your team last checked the page. A plain paragraph works better than a list in a conversation. Here is one version you can adapt:

> Our accommodation process follows the EEOC's enforcement guidance on reasonable accommodation and undue hardship under the ADA. It replaced guidance from 1999, issued on 03/01/99. The guidance cites the 2002 Barnett decision as prompting its major changes. Our file records when we last checked the page.

How often should we recheck the guidance?

Recheck whenever you hear that the EEOC has changed or is reviewing an ADA publication, and on a regular schedule your team sets. Write down the review date and the result, even when nothing changed, because a dated "no change found" note shows that the check happened.

General information, not legal or tax advice.

Sources