Abe: A defensible JD clearly lists essential functions, measurable expectations, required skills, typical environment, supervisory relationships, and it matches what the employee actually does.
A: Be specific enough that you can point to a handful (3–8) of core tasks someone must perform, and note any physical or cognitive requirements. Save “other duties” for genuinely occasional tasks.
Why it matters: Specific essential functions are vital for ADA accommodation decisions and for demonstrating that a role’s core duties justify exempt status or not.
A: Titles alone don’t determine legal status; their duties do. Always document the actual duties and decision-making authority rather than relying on a title.
Why it matters: Regulators look at work performed, not job titles, when assessing misclassification or unpaid overtime claims.
A: Use the JD as the baseline for expectations in performance conversations and corrective actions; tie feedback to listed duties and measurable outcomes.
Why it matters: If expectations are documented, disciplinary steps are defensible and consistent across employees.
A: Update when duties materially change (ideally within 1–2 weeks of the change), and run a formal JD review at least annually.
Why it matters: Outdated JDs lead to classification errors and weaken your defense in disputes where “actual work” matters.
A: Avoid vague phrases like “other duties as assigned” without clarification, subjective descriptors (e.g., “fast learner”), or overly broad duties that permit constant scope creep.
Why it matters: Vague language creates ambiguity in expectations, which undermines performance documentation and classification.
A: Managers should propose changes when duties shift, but HR should own the review, approval, and the version-controlled master copy.
Why it matters: Shared ownership ensures updates happen quickly and consistently, keeping you compliant and defensible.
Leave A Comment