Short answer
A dynamic job description is a job description that is reviewed when the work materially changes. It should not update itself from a conversation or infer a person's capability. Compare the documented purpose, tasks and accountabilities with evidence from the work, decide whether the change is temporary or shared, then have the accountable role owner approve, communicate and date any revision.
Separate drift from a temporary exception
People routinely cover absence, take on a project or adapt to a local constraint. Those accounts may be important, but they are not automatically a new role. The practical question is whether the difference is material, sustained and relevant to the role's approved purpose.
The US Department of Labor sponsored O*NET database distinguishes tasks, work activities and work context. That distinction helps a review team avoid a common mistake: changing a whole job description because one task moved temporarily, or leaving a role unchanged when its accountability and conditions have shifted together.
Use this role-drift review sheet
| Review field | What to record |
|---|---|
| Existing role statement | Purpose, main tasks, decision rights and required conditions |
| Reported difference | What work appears different, from whom and on what date |
| Evidence | Example work, customer or operational change, manager and employee context |
| Scope | One person, one site, a job family or a wider operating change |
| Duration | Temporary cover, project work, recurring practice or approved redesign |
| Decision | Keep the description, document a local exception, investigate or revise |
| Owner and record | Accountable role owner, approval date and next review trigger |
The US Office of Personnel Management's classification guidance treats a position description as a statement of major duties and responsibilities. It is a useful principle for any employer: a revision should be about the role's work and accountability, not a way to score an individual.
Work through a fictional example
This example is fictional. A retailer's stock coordinator description says the role receives deliveries, updates stock records and escalates discrepancies. During a new fulfilment process, several coordinators also sequence urgent orders and resolve supplier substitutions.
The review team checks shift records and interviews the coordinators and site manager. At one site, the extra activity was a two-week cover arrangement. At three other sites, it has become a recurring part of the planned workflow, with authority to prioritise orders. The team documents the first as a local exception. For the shared change, the role owner reviews the new accountability, training, grade implications and safety requirements before approving a revised description.
The useful output is not an instant update. It is a traceable decision about which work belongs in the role and what support, staffing or redesign follows.
Ask better review questions
- Which documented task, accountability or condition no longer matches the work?
- What evidence shows that the difference is recurring rather than a one-off exception?
- Is the change shared by a role group or specific to a site, project or person?
- What has to be checked before a revision: authority, workload, pay, training, safety, policy or employee consultation?
- Who approves the final description, and how will affected people see the change?
ACAS's job description templates identify the role's main duties and reporting line as core elements. Local employment, collective-agreement and consultation requirements vary, so organisations should use appropriate HR and legal review for their situation.
Where conversations help
Focused employee and manager accounts can show where a written role misses an exception, handoff or real working condition. Treat those accounts as inputs to job analysis. They do not prove a permanent change, justify a unilateral amendment or establish a capability rating.
For a broader evidence sheet on skills requirements, use the skills gap analysis worksheet. For a capability coverage decision, use the employee skills mapping guide. Lontra's product can help collect structured context for a bounded question, but role owners must review the material and managers receive briefs rather than raw conversations.