Job Description Compliance

Last updated: November 01, 2026

Job description compliance starts with one goal: write a job description that can support hiring, accommodations, and performance management without drifting into policy language or vague marketing copy. In Job Description Compliance: How to Write Duties, Qualifications, and Essential Functions, the point is to make the role clear, job-related, and current.

What a compliant job description has to do

A compliant job description has to describe the job, not the person you hope to find. That means separating essential functions from nice-to-have tasks, stating qualifications that match the work, and using equal employment opportunity language where appropriate without turning the document into a policy manual.

The job description is not the place for rules about attendance, discipline, dress code, leave, or harassment reporting. Those belong in other documents. Here, the document should help three decisions: who to hire, how to evaluate performance, and what accommodations might be considered if a qualified employee needs them.

A useful job description also does one thing most generic templates miss: it shows why a duty matters. If a task is rare but central to the role, it belongs in the essential functions section. If a task is common but can be reassigned, it may belong in a duties or responsibilities list instead.

The compliance stakes are real. Under the ADA, the way a duty is written can affect whether it is treated as an essential function, so employers should consult a professional and review EEOC guidance before finalizing the wording. Under equal employment opportunity rules, the language can also affect whether a qualification screens people out for the wrong reason. The point is not to write a legal brief. The point is to write a job description that can stand up to scrutiny because it is clear, job-related, and current.

If this page is part of a broader hiring process, the Hiring and Employment Classification hub belongs next to it, but the job description itself should stay focused on the position.

How to write duties that hold up in hiring and review

Write duties as concrete actions, grouped by what the role actually produces in a normal week or month. A strong duties section often works best with 5 to 10 bullets, each starting with an action verb and ending with the result, tool, or work setting.

Use this procedure:

1. List the work the role performs in a typical 40-hour week, then sort the items by frequency or business impact. The result should be a short list that reflects the job as it exists, not a wish list.
2. Turn each item into a duty statement with one verb and one object. “Maintain customer records in Salesforce” is usable; “handle various administrative tasks” is not.
3. Separate core work from occasional work. If a task happens once a quarter, label it as occasional instead of burying it in the middle of the list.
4. Delete duties that belong to every employee in the company, such as “follow company policies,” because they do not explain the job and can crowd out real work.
5. Check that the duties could be measured or observed in a review period of 3 to 12 months. If no supervisor could tell whether the duty was done, rewrite it.

A good duty is written at the right level of detail. “Respond to customer emails within one business day” is precise enough to guide work. “Provide excellent service” is not. The first can be evaluated. The second cannot.

One trade-off matters here: the more detailed the duties list, the more likely it is to go stale when the process changes. A 15-item list sounds thorough, but it ages badly. A shorter list, written around stable work outputs, survives reorganizations and software changes better. That is why many job descriptions work better with 6 to 8 duties than with a page of every possible task.

Essential functions in a job description: what counts and why it matters

Essential functions are the duties that define the job, not the duties that merely happen to appear in it. In ADA terms, they are the functions the role exists to perform, and they deserve their own section because they affect both hiring and accommodation analysis.

The essential functions section should be written in plain English, often with 4 to 8 bullets. Each one should describe a core duty and, when useful, the reason it matters. For example, “Lift and move product cartons up to 40 pounds to restock shelves” tells the reader more than “must be able to lift 40 pounds.” The task is what matters; the number is the support detail.

A generic article often gets this wrong by copying a “physical requirements” list into essential functions. That creates problems. If you say “stand for 8 hours” but the real job is operating a scanner and supervising a line, the description may overstate what is truly essential. A better approach is to identify the work outcome first, then note the physical demand only if it is tied to the duty.

Common signals that a duty is essential:

• It is a primary reason the position exists.
• Only a few employees can do it.
• The role would lose its value if the duty were removed.
• The duty requires a specific credential, clearance, or on-site presence.

A limitation is worth stating plainly: essential functions are not the same as “everything the employee does.” If a task is secondary, easy to reassign, or performed only occasionally, it should usually not be raised to essential status. Overcalling duties as essential can narrow the applicant pool without improving the job.

For compliance work, that distinction matters because essential functions are the bridge between the job description and accommodation decisions. The U.S. Equal Employment Opportunity Commission’s guidance on essential functions is the kind of source that should anchor this section. The document does not need citations inside every bullet, but it should be written with that standard in mind.

What qualifications belong in the job description?

Qualifications belong in the job description only when they are truly job-related and tied to the duties, not because they sound impressive. A compliant qualifications section distinguishes required qualifications from preferred qualifications and avoids asking for more education or experience than the role needs.

Start with the minimum. That usually includes education, experience, licenses, certifications, and job-related technical skills. If the job can be done with a high school diploma plus 2 years of experience, say that. Do not write “bachelor’s degree preferred” unless the degree is truly a preference, not a hidden requirement.

Then separate preferred qualifications into a second list. This keeps the screening line honest. A required qualification should be something you would reject an otherwise strong candidate for if they lacked it. A preferred qualification should improve a candidate’s ranking without disqualifying them.

Here is the simple test: if you would waive a requirement for the right candidate, it is probably not a requirement. That matters for equal employment opportunity because overbuilt qualifications can screen out qualified people for reasons that do not track the work.

Avoid vague traits like “self-starter,” “team player,” or “strong communication skills” unless you define what those mean in the role. “Writes client emails with minimal editing” is a qualification you can assess. “Excellent communication” is a slogan.

The qualifications section usually covers about 3 to 6 items, and each item should be tied to a real duty. If the job uses a specific system, name it. If it requires a state license, state that clearly. If the role needs the ability to travel about 10% of the time, say so if that travel requirement is real for the job. That sort of specificity helps applicants self-select and helps the employer explain why the qualification exists.

How to handle physical requirements and ADA-related wording

Physical requirements should describe the actual conditions of the work, not a blanket fitness test. That means naming the movement, weight, environment, or schedule component only when it relates to an essential function.

A compliant physical requirements section often includes items such as standing, walking, lifting, reaching, typing, driving, noise exposure, or use of personal protective equipment. The key is to be specific enough to matter. “Must be able to lift boxes” is weak. “Must be able to lift 25-pound boxes from floor to shelf several times per shift” is clearer and more defensible.

A common mistake is to use broad language like “must be able to perform all duties without accommodation.” That phrase is overreaching and can scare off applicants while creating avoidable ADA issues. Better wording focuses on the essential function and leaves room for an interactive accommodation process if one is needed later.

Useful language sounds like this:

• “Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions of this role.”
• “This position requires regular use of stairs and occasional lifting of up to 30 pounds.”
• “On-site presence is required for core duties performed at the production line.”

That last point matters because some roles do require physical presence. A job description can say so if the requirement is tied to the job, such as direct supervision of equipment, access to confidential materials, or face-to-face service in a fixed location.

Do not turn the physical requirements section into a medical screen. It should describe the job’s demands, not predict who will struggle. If the list reads like a pre-employment exam, it is too broad. If it reads like the workday, it is closer to compliant.

The Americans with Disabilities Act is the standard to keep in view here, and the strongest job descriptions use it as a drafting lens: essential function first, physical demand second, accommodation language third.

What should EEO language and accommodation wording say?

EEO language should be short, neutral, and placed where applicants expect to find it, while accommodation wording should invite requests without promising a specific outcome. The job description is a practical document, so the wording should be plain and restrained.

An EEO statement usually tells applicants that the employer considers candidates without regard to protected characteristics and welcomes qualified applicants. If your organization uses a standard equal employment opportunity statement, keep it consistent across roles. Do not improvise a new version for every posting unless there is a legal or branding reason to do so.

Accommodation wording should be even more careful. It should tell candidates how to ask for help with the application process or with job performance later, but it should not suggest that accommodations are guaranteed or that all requests will be granted. The sentence should open the door, not make a promise the employer may not be able to keep.

A practical pattern is:

• “Applicants who need assistance with the application process may contact [appropriate contact].”
• “Reasonable accommodations may be available to enable individuals to perform the essential functions of the position.”

That kind of wording works because it is specific about the process and avoids diagnosing anyone’s needs. It also keeps the job description separate from policy details. The accommodation note belongs in the description; the full process belongs elsewhere.

One thing not to do: bury the EEO or accommodation language in a 2,000-word corporate paragraph. Readers skip it, applicants miss it, and the document becomes harder to use. A short statement near the end is usually enough.

If the role is heavily regulated or the employer uses a formal template, the exact wording should be reviewed internally before publication. That is not because every job description needs a legal memo. It is because EEO and ADA language is one place where a sentence written too loosely can create avoidable confusion.

The job description compliance checklist I would use before publishing

A compliant job description is ready when the duties, essential functions, and qualifications all point to the same job and nothing in the document overreaches. Before publishing, I would run a quick 7-point check and fix anything that fails.

1. Read the title and confirm it names the actual job, not a department, personality type, or future promotion path.
2. Count the duties. If there are more than 10, cut or combine items until the list shows the real work.
3. Mark the essential functions and ask whether the job would still make sense if one of them disappeared.
4. Separate required qualifications from preferred ones. If the required list has 8 items, it is probably too long.
5. Review physical requirements and tie each one to a duty, a setting, or a tool.
6. Check for policy language, discipline language, or handbook language and move those sentences out.
7. Make sure the EEO and accommodation wording is present, short, and consistent with the company’s standard language.

A useful rule is that every line should do one job. If a sentence explains the task and the policy and the performance standard at once, it is doing too much. Split it.

The biggest mistake here is writing for legal fear instead of operational clarity. That usually produces bloated descriptions with broad language, excessive qualifications, and generic phrases that no manager can use. The fix is not more words. It is better choices: concrete duties, honest requirements, and an essential functions section that reflects the work as it is actually done.

The result is a job description that helps hiring, supports accommodation requests, and gives managers a usable reference point for performance management without pretending to be a policy manual.

When should the description be reviewed or updated?

A job description should be reviewed whenever the work changes in a meaningful way, and in many organizations that means at least once a year. A yearly review is not a legal magic number; it is a practical one. If the role has a new system, a new reporting line, a new location, or a new physical demand, the description should be updated sooner.

Review it after:

• a reorganization,
• a significant change in software or equipment,
• a shift from onsite to hybrid work, or the reverse,
• a change in licensing or certification requirements,
• a new accommodation issue that reveals the old wording is too broad or too narrow.

Do not wait for a lawsuit or a hiring crisis to discover that the document no longer matches the job. A stale description can harm recruiting, muddle performance reviews, and make accommodation analysis harder than it needs to be.

The downside of frequent rewriting is inconsistency. If every manager drafts from scratch, titles drift, qualifications bloat, and the same role can look different across departments. The better approach is to use one template, one review cycle, and one owner for final approval. That keeps the document stable without freezing it in time.

Key Takeaways

• A compliant job description describes the work first, then the qualifications, then the physical demands that matter.
• Essential functions should be limited to the duties that define the role under the ADA, not every task the employee may touch.
• Required qualifications need a real connection to the job; preferred qualifications belong in a separate list.
• External guidance from the EEOC and the ADA can help keep wording defensible and practical.

Drafted with AI; not yet reviewed by a person.