What Your Job Posting Will Say in Court: A Compliance Review Before Publication

A job description serves two audiences. The first is the candidate scanning a posting on a phone. The second is the investigator, auditor, or judge who may read the same document years later. Employers tend to draft for the first audience and forget the second. As of 2026, with pay transparency rules expanding and accommodation claims remaining steady, that oversight is harder to defend.

This article offers a practical pre-posting review framework. It is general information, not legal advice; employment counsel should review final documents where risk is material.

The Document Has a Second Life

A job description is not usually required by federal law, but it is frequently consulted. Under the Americans with Disabilities Act, the essential functions of a position shape the accommodation analysis. Under the Fair Labor Standards Act, duties language can support or undermine an exemption decision. State and local pay transparency laws increasingly require employers to disclose a range that should correspond to the work described.

No single document decides these questions. But a posting written carelessly can create unnecessary ambiguity. If the description says the role requires occasional lifting of fifty pounds, but the actual job involves lifting ten, the employer may later have to explain the discrepancy. If it labels a position exempt while listing primarily routine tasks, the exemption becomes harder to sustain.

The goal of pre-posting review is not to make the document litigation-proof. It is to make it accurate, internally consistent, and defensible.

Begin with the Work, Not the Worker

A common mistake is to start by updating an old description. That approach tends to preserve outdated duties, inflated qualifications, and language copied from a template. A more reliable method is to ask supervisors and employees what the job actually involves: which tasks are performed, how often, with what tools, and what happens if they are not performed.

This task inventory should be completed before the posting is written. It gives the employer a factual basis for distinguishing essential functions from marginal ones. It also exposes duties that have quietly disappeared or been absorbed by other roles.

Separate Essential Functions from Wish-List Duties

Essential functions are the fundamental duties of the position. In assessing them, the ADA directs attention to the employer's judgment, written descriptions prepared before a dispute, the amount of time spent performing the function, the consequences of not requiring it, and the experience of current employees in similar roles.

The review should test each listed duty against that standard. A requirement to speak at industry conferences may be a preference unless the role is fundamentally public-facing. A requirement to use a particular software platform may be legitimate if the work cannot be performed without it. A vague line such as "ability to work in a fast-paced environment" rarely helps and can invite dispute because it describes a working condition rather than a task.

Where possible, describe duties with observable detail. "Prepares weekly accounts payable reports in Excel and reconciles discrepancies with the finance team" is more useful than "strong analytical skills." The former can be verified; the latter cannot.

Pressure-Test Physical and Scheduling Requirements

Physical demands deserve particular scrutiny. If the posting lists lifting, standing, driving, or repetitive motion requirements, those requirements should correspond to actual job tasks. Listing them defensively, without a factual basis, can complicate the accommodation process and may deter qualified applicants.

Scheduling requirements warrant the same treatment. A requirement that an employee be available nights and weekends should reflect operational necessity, not habit. If the role can be performed during standard business hours with occasional exceptions, the posting should say so. Attendance requirements should likewise be defined. "Regular and predictable attendance" can be an essential function in many roles, but it should be tied to the nature of the work rather than used as a catch-all.

Clean Up Qualifications Language

The qualifications section is where compliance risk often hides in plain sight. Education requirements should be genuinely required for the role. A bachelor's degree listed for a position that does not need one can unnecessarily narrow the applicant pool and create disparate impact concerns. Years-of-experience requirements should be examined with the same skepticism.

Language that is age-coded, disability-coded, or otherwise exclusionary should be removed. Terms such as "digital native," "recent graduate," or "must be energetic" are imprecise and can suggest preferences unrelated to the job. So can requirements for a valid driver's license when driving is not an essential function.

Criminal history and credit check requirements should be reviewed against applicable federal, state, and local rules. Where background checks are permitted, the posting should describe them accurately and avoid overbroad disqualifiers.

Align the Posting with Pay and Exemption Decisions

Pay transparency has changed the job description from a recruiting document into a public compliance statement. Where a range is required, the range should be consistent with the duties, location, and exemption status described. A posting that lists an annual salary range for a role classified as exempt should reflect a salary basis that satisfies the FLSA. A posting that describes primarily routine tasks should not imply an exemption that the duties cannot support.

Exemption review should happen before the posting goes live, not after an employee is hired. The duties test examines what the employee actually does, but the job description is often the first document an agency or plaintiff will request. Inconsistency between the posting and the reality of the role creates avoidable exposure.

Build a Review Record

A pre-posting review is only useful if the employer can show it happened. Version control matters. Keep the draft that was reviewed, note who approved it, and retain the final posting. If the role changes, update the description rather than allowing the original to drift out of date.

This record does not guarantee a favorable outcome in a dispute. It does demonstrate that the employer treated the document as a compliance instrument rather than a marketing afterthought. In accommodation matters especially, evidence of a good-faith review before the posting can be more persuasive than a reconstructed explanation afterward.

A Short Checklist Before Publication

The posting goes live only after the following questions have been answered:

• Does the title and FLSA classification match the duties actually performed?
• Are essential functions listed with enough specificity to be verified?
• Do physical requirements reflect real tasks rather than defensive boilerplate?
• Are scheduling and attendance requirements tied to operational need?
• Are qualifications job-related, narrowly tailored, and free of coded language?
• Is the pay range consistent with the role, location, and required disclosures?
• Has the document been reviewed and versioned before publication?

A job posting is not a contract, but it is a statement. It tells candidates what the employer expects and tells later readers what the employer understood the job to be. A modest review before publication keeps those two messages aligned.