Six Places Your Job Description Quietly Becomes Evidence
Most small employers write a job posting for a single purpose: filling a seat. The text goes up on a board or a careers page, draws a few dozen applications, and once an offer is accepted it is archived and forgotten. That document, however, does not stop working. It becomes the employer's own description of the job — the baseline a court, an agency investigator, or a plaintiff's attorney will use to test whether an accommodation was reasonable, whether a salaried employee was properly exempt, and whether a pay range should have been disclosed before the first conversation.
Few lean companies have a compliance specialist who reads postings before publication. The audit below is built for the person who wears that hat on a Tuesday afternoon. Six checkpoints, each with a rewrite example.
1. Essential functions, stated as duties rather than wishes
The Americans with Disabilities Act does not require an employer to hire someone who cannot perform the essential functions of a position, but it does require the employer to be able to say clearly what those functions are. A posting that lists forty bullet points and labels all of them essential undercuts that position. So does a posting that lists none.
Before: Fast-paced environment. Must be a team player and handle whatever comes up.
After: Processes 40–60 customer orders per shift using the order management system. Responds to chat and phone inquiries during posted service hours. Reconciles the daily deposit three times per week.
Descriptions that name frequency and volume do more than satisfy a statute. They give hiring managers a scoring rubric and give a returning employee's physician something concrete to work against.
2. Exemption language that describes duties, not just salary
In FLSA terms, paying a salary does not make a position exempt. The duties tests for the executive, administrative, and professional exemptions turn on what the employee actually does, and a posting that announces "Assistant Store Manager — exempt, $52,000" invites a mismatch if the role is largely stocking shelves and running a register.
Rewrite the summary around responsibility and discretion: supervises three to five associates, sets weekly schedules, and has authority to approve refunds up to $250. If the honest description is mostly task execution, the classification — not the posting — needs a second look.
3. Pay ranges and the transparency patchwork
A substantial and growing group of states and municipalities now require employers to disclose a pay range in the posting or upon request, and the thresholds often reach employers with as few as one to fifteen employees. The rules vary on whether the range must appear in the advertisement, how wide it may be, and whether it must be shared with internal candidates.
A practical response for a multi-state employer is a single national standard: publish a good-faith range in every posting, describe how it was determined, and confirm it against current incumbents' pay before publishing. A range that no current employee falls within is a difficult thing to explain later.
4. Physical and environmental requirements
Requirements such as lifting thresholds, standing duration, driving, shift work, and exposure to heat or chemicals belong in the posting when they are genuinely part of the job. Omitting them does not remove the requirement; it simply means the first time a candidate hears about it is after an offer, which is precisely when an accommodation request is most likely to arrive.
A useful discipline is to write physical requirements in plain measurements — lifts up to 35 pounds repeatedly during a four-hour shift — and to avoid blanket phrases like must be in good physical condition, which describe a status rather than a task.
5. Remote, hybrid, and location terms
Postings written before 2020 often carry assumptions that no longer hold. If a role is hybrid, say how many days and at which site. If the position is remote, identify whether the employer will hire in states where it is not yet registered to withhold taxes. If travel is expected, state the share of the month.
These details matter beyond recruiting. They shape whether a reasonable accommodation must be considered for remote work, and they determine whether an employee's physical work location is consistent with the payroll setup.
6. Retention: how long the file lives and who can retrieve it
Federal retention periods differ by statute and are often longer than employers assume. Payroll records generally must be kept for three years under the FLSA, and time and wage computation records for two. Employment records tied to Title VII and the ADA generally run one year from the date of the personnel action, while the Uniform Guidelines extend certain hiring records to two years for larger employers, as does OFCCP's rule for federal contractors. State human rights agencies frequently impose their own clocks.
In practice, that means a posting from 2024 may still need to be retrievable. Confirm that applicant data lives in one system rather than in a hiring manager's inbox, and that deleting a requisition does not delete the underlying record.
A rewrite routine that fits an afternoon
Start with the postings that are still live, then work backward through the last twelve months of hires. For each, run the six checks, save a dated copy of the original, and note the reason for any change. That short memo is worth more than a perfect template, because it shows the employer reviewed the language deliberately rather than copying it forward.
When the review is finished, hand the revised descriptions to the hiring managers who use them. A posting that compliance has polished but a supervisor never reads will drift back to its old form within two hiring cycles.
The underlying idea is simple: treat the job description as a record first and a recruitment ad second. It will be read that way by someone eventually, and it is far easier to correct the language now than to explain it later.