Skip forward into hiring notes
RosterAcorn

EEOC ADA examples: 5 essential duty standards

EEOC ADA examples show how to define essential duties and performance standards for investigations, travel, deadlines, equipment repair, and meetings.

Key takeaways

  • Tie essential duties to results you can check.
  • Base counts and deadlines on records of the work.
  • Explain the purpose of travel and meeting requirements.
  • Separate required results from methods of doing the work.

Hiring managers usually think about performance after the hire. Before the interview, the job posting gets copied from an old posting, a few skills get added, and the expectations stay vague. Months later, when someone is missing targets or struggling in a meeting, the manager has to work out whether the problem is performance, and whether a disability is involved. A clear definition written before the interview makes that decision much easier.

The Equal Employment Opportunity Commission (EEOC) has published guidance on applying performance and conduct standards to employees with disabilities. The guidance works through examples, and they are useful for hiring managers because they show where standards go wrong. This post covers five of them. Each one points to a part of the job you can define before you hire: a fixed count of work, required travel, deadlines, equipment repair, and participation in meetings.

Nothing here is legal advice. The examples are a starting point for your own review of the job. Your HR team or employment counsel should check any standard that could affect a current employee or an applicant.

What makes a duty essential

Most job descriptions list too many duties with equal weight. A better list separates the core work from the supporting tasks. The core work is what the role exists to do. Supporting tasks matter, but a person can still do the job well without doing every one of them the same way.

When you draft your list, ask a few plain questions about each duty:

  • Why does this role exist, and does this duty serve that purpose?
  • How much of the working time does this duty take?
  • What happens if no one does it, or if it is done late?
  • Was this duty a real part of past work in this role, or was it copied from an old posting?

These questions do not replace a formal analysis, and they are not a legal test. They are a way to stop the list from filling up with tasks that sound important but are rarely done. A short list of essential duties is easier to defend, easier to explain to an applicant, and easier to measure later.

Write each duty as a result when you can. "Repairs and maintains equipment" names an outcome. "Uses a wrench and climbs ladders" names a method. The outcome is what you measure. The method is where you should ask whether there is another way to get the result, and that question matters later if an employee needs a different approach.

Use the job description sections to organize the posting around these duties.

Two rules from the guidance

Before the examples, two points from the same guidance shape how every standard should be written.

The first concerns methods. The guidance says: "An employee who must use an alternative method of performance because of a disability must be evaluated accordingly." It adds a limit: "However, an employer is not required to allow use of an alternate method that would impose an undue hardship." ( EEOC guidance) In practice, this means that when you write a standard, you should separate the result you need from the way it has to be produced.

The second concerns timing. The guidance says: "The ADA does not compel employees to ask for accommodations at a certain time. Employees may ask for reasonable accommodation before or after being told of performance problems." ( EEOC guidance) That is why your job-description work should make the standard clear. A clear standard keeps later conversations focused on facts rather than guesses.

1. Investigators and a fixed annual count

The first example is the easiest to picture. The guidance describes the setup this way: "A federal agency requires all of its investigators to complete 30 investigations per year in addition to other responsibilities." ( EEOC guidance)

A standard like this is concrete. Anyone reading the job description knows the expectation, and a manager can check it against records. That is the strength of the example. The weakness is that a number on its own tells you little. Before you put a count into a posting, ask:

  • Does the count come from a real analysis of the work, such as past caseloads, time for each case, or the team's actual needs?
  • Are the "other responsibilities" listed, so the applicant can see the whole job and not only the headline number?
  • Would the count still make sense if the role changed next year?

Your number has to come from your own work. If your investigators carry a count, write it into the posting the way this example does, with the other duties beside it. Then keep the record that shows where the count came from.

Common mistakes with counts include copying a number from another employer, setting a count that no one has tested against real caseloads, and forgetting that the other duties take time too. If a count is hard to reach because of other work the manager assigned, the standard is not measuring the employee. It is measuring the workload.

2. A territory with three trips to each state

The second example describes a role with regular travel. The guidance says: "His territory covers a 3-state region and he must travel to each state three times a year." ( EEOC guidance)

Travel is a common essential function, and it is often stated loosely. A posting that says "some travel" leaves applicants guessing. A manager who later decides the travel is not required has no written basis for that decision. The example is more useful because it names the region, the number of states, and the frequency. Those details let an applicant decide whether the job fits, and they give the manager something to check.

For your own roles, write travel the same way. Name the geography, how often trips happen, and how long they last. Then say whether the travel must be in person. If you cannot explain why an in-person visit is required, the requirement may be a preference rather than an essential function. Be ready to tell the difference, because you may have to defend it.

Travel also needs a plan for the employee who asks to meet it in another way. Treat that request as something to evaluate, not an automatic no. ( EEOC guidance) Your job is to understand the purpose of the travel, what is lost without it, and whether the purpose can be met another way. Write that analysis down.

3. A programmer who misses deadlines

The third example describes a common problem. It reads: "A computer programmer with a known disability has missed deadlines for projects, necessitating that other employees finish his work." ( EEOC guidance)

This example shows why deadlines need to be defined before the work starts. A deadline is a usable standard only if the team knows when work is due, who sets the date, and what happens when a date slips. In software work, that usually means the project plan and the release schedule, not a manager's sense of urgency. If the due dates are invented on the spot, a missed date tells you little about the person.

Before a hire, write down:

  • How deadlines get set for this role, and who agrees to them.
  • What counts as a missed deadline. Is it a date missed by a day, or a milestone that blocks other people?
  • The effect on the team when work slips. The example points to other employees finishing the work as an impact, so the standard should say how the team's work is affected when a deadline slips.
  • Whether the role includes estimating, or whether the team estimates for the role. The answer changes who owns the deadline.

The example also shows why records matter. If a manager has to address missed deadlines, the notes should show the project, the agreed due date, the date the work was done, and what support was offered. Vague statements such as "he is slow" do not hold up when someone reviews them. Specific notes protect the employee and the manager, because they show what the standard was and how it was applied.

Your response should be the same either way: listen to the request, look at the deadline standard and the method the employee uses, and document what you learn. ( EEOC guidance) For a practical sequence, see handling an accommodation request.

4. A millwright and equipment repair

The fourth example is short and direct. It reads: "Daniel works as a millwright, and an essential function of his job is repairing and maintaining equipment." ( EEOC guidance)

Here the essential function is named plainly, and that is the model for your own posting. Name the core work in words an applicant can understand. For a millwright role, that means repairing and maintaining equipment. A stronger posting also says which equipment is covered, which tasks are included (diagnosing faults, replacing parts, carrying out scheduled maintenance), and where the work happens.

Performance standards for this kind of work should come from the operation itself. Possible measures include the time it takes to respond to a breakdown, the share of scheduled maintenance completed on time, and the share of safety checks completed. The targets must come from your site's records and your operating needs, not from a generic figure you found online. If your records do not exist yet, say so in the hiring plan and set a review date for the standard.

Physical requirements need the same care. A millwright job may involve lifting, climbing, or working in tight spaces. Before you list any of these as essential, decide whether the task is truly needed for the outcome, and write down how you reached that decision. A requirement written because "that is how it was always done" is hard to justify when someone asks about it later.

Finally, think about the employee who is already in the role. If a current millwright needs a different method for part of the work, the question is whether the result still gets done, safely and on schedule. ( EEOC guidance)

5. Following conversations in meetings

The fifth example is about a different kind of standard. It describes the situation this way: "Nasser, an employee at a nonprofit organization, recognizes soon after he begins working that he is having difficulty following conversations at meetings because of his deteriorating hearing." ( EEOC guidance)

The lesson is in the word "meetings." Many job descriptions list participation in meetings, but few define it. Is the requirement to attend? To speak? To take action items? To follow the discussion as it happens? Each one points to a different standard, and each can be met in different ways. A vague requirement leaves a manager with no clear test, and it leaves an employee with no clear target.

When you write the job description, separate the purpose from the method. If the purpose is to make decisions, track commitments, and contribute ideas, say that. If the requirement is to follow verbal discussion in real time, ask whether that is the only way the information can reach the employee. Notes, written follow-ups, a shared agenda, or a summary after the meeting may serve the same purpose. This is where a method-based requirement may be more than the job actually needs.

Ask the same questions about any meeting-based standard. How many meetings does the role attend? Which of them require a decision from this person? What does a good contribution look like? Write the answers before the interview, so the applicant knows what participation means in this role.

The example also shows early recognition. Nasser notices the problem soon after he starts. That is a good moment for a manager to ask an open question, rather than assume a conclusion about the employee's abilities. ( EEOC guidance) Keep the conversation about the standard, the purpose, and the options, and record what was agreed.

A pre-interview checklist

Use this list before you post or interview for a role. It works for any job, and it applies the lessons from the five examples.

  • Write three to six essential duties in plain words, and tie each one to a result.
  • For each duty, write how you will measure it, and name the records or sources the measure comes from.
  • Separate the result from the method. Note which methods you would consider different if an applicant or employee asked.
  • Check every count, travel schedule, deadline, physical task, and meeting requirement. Write down why each one is essential.
  • Keep a short note on how each standard was set, who approved it, and when it was last reviewed.
  • Plan for change. When the job changes, review the standards and update the posting.

Illustrative example: checking a workload count

An illustrative hiring plan lists 30 investigations per year. The manager checks past caseloads and the time needed for other responsibilities before using that count. If the records do not support it, the manager reviews the standard rather than copying it into the posting. The next task is to record where the count came from and which other duties must fit alongside it.

Closing thought

The five examples share one habit. They state the work clearly enough that someone can check whether it is being done. The count of investigations, the travel schedule, the deadlines, the equipment work, and the meeting participation all become easier to evaluate when they are written down before the first interview. That early work also protects you. It gives applicants a clear picture of the job, gives managers a standard to apply, and gives everyone a basis for the conversations that follow.

Take an hour today to review one open role. Write its essential duties, then read each one out loud and ask whether a manager could check it with records. If the answer is no, the standard needs more work before anyone is hired.

A few questions

What should a performance record include?

Record the project, agreed due date, completion date, and support offered. Keep the notes specific enough to show how the standard was applied.

What should a travel requirement include?

Name the geography, trip frequency, duration, and whether visits must be in person. Write down the purpose of the travel so you can evaluate another approach.

Sources