Job Description

A job description is the internal document that defines a role: its purpose, its core responsibilities, the qualifications and physical or environmental requirements involved, where it sits in the organization, and which of its duties are essential to the position.

It is not the same thing as a job posting. The posting is a marketing document written to attract a candidate. The job description is a document of record, and it is the version that gets read back in an accommodation discussion, a pay equity review, or a performance dispute.

What a usable job description contains

• Job title, department, reporting relationship, and location or work arrangement.
• A short statement of why the role exists and what outcome it owns.
• Essential functions, stated as duties with enough specificity that someone could judge whether a person is performing them.
• Non-essential or marginal duties, kept separate from the essential ones on purpose.
• Required qualifications, distinguished from preferred qualifications, and tied to what the job actually needs.
• Physical, cognitive, and environmental demands where they are real requirements of the work, such as lifting, driving, on-call availability, or exposure conditions.
• The wage and hour classification and the pay range or grade, if the organization maintains one.
• The date the description was last reviewed, and by whom.

Essential functions and why they carry the weight

Essential functions are the fundamental duties of a position, as opposed to the tasks that are merely incidental to it. Under United States disability law, an individual is qualified for a job if they can perform the essential functions with or without a reasonable accommodation. That single sentence is why the list matters.

A function is more likely to be essential when the position exists specifically to perform it, when few other employees are available to absorb it, or when it requires specialized expertise. A written job description prepared before a position is advertised or interviewed for is one of the kinds of evidence considered when there is a dispute about whether a function is essential. The amount of time spent on the function and the consequences of not performing it are also weighed.

The practical implication is directional. A description that lists everything as essential is not more protective. It is less useful, because it makes the essential list unbelievable and removes the ability to distinguish the duties that genuinely cannot be reassigned.

What the document is actually used for

Where teams get this wrong

Job descriptions fail quietly. They stay on file, they stop matching reality, and nobody notices until the moment they are needed.

• Copying a posting into the job description file, which imports marketing language and omits the physical and environmental requirements that matter later.
• Marking every duty essential, which weakens the credibility of the entire list.
• Inflating required qualifications past what the work needs, which narrows the candidate pool and invites questions about whether the requirement is job related.
• Ending with a catch-all duty and treating it as coverage for work that should have been written down.
• Letting descriptions go stale through reorganizations, so the document describes a job nobody currently does.
• Assuming the description determines exempt status. It supports the analysis only to the extent it accurately describes the work actually performed.
• Storing descriptions in scattered documents with no version history, so nobody can establish what the description said at the time a decision was made.

Keeping descriptions current

The maintenance loop is short and it works when it is attached to events that already happen.

1. 1Review the description at the start of every requisition, before the posting is written, rather than after the offer.
2. 2Have the manager and an incumbent confirm the essential functions in plain language, and cut what is no longer performed.
3. 3Confirm the requirements are job related, and drop credential requirements that no longer reflect what the work needs.
4. 4Re-confirm the wage and hour classification whenever the duties materially change.
5. 5Date and version the description, and keep the prior version rather than overwriting it.
6. 6Sweep the whole library on a set cadence, typically annually or after any reorganization.

Why it matters operationally

The job description is the smallest piece of documentation that touches the most decisions. Recruiting, leveling, pay, accommodation, and performance all resolve against it, and when it is missing or stale each of those conversations restarts from scratch and reaches an inconsistent answer.

It is also the artifact that turns individual roles into a job architecture. An organization that maintains accurate descriptions can compare roles, level them, benchmark them, and plan headcount against them. One that does not is negotiating each role independently, every time.