A job description explains why a role exists, what it is responsible for and the capabilities needed to perform it. It supports recruitment, onboarding and performance discussions when it reflects the actual work. A polished list of duties is less useful if it leaves authority, priorities and working relationships unclear. This guide shows how to build a description that managers and candidates can use.
A research indicator
The World Economic Forum’s Future of Jobs Report 2025 estimates that 39% of workers’ existing skill sets will change or become outdated during 2025–2030. The report reflects more than 1,000 employers across 55 economies. This is a forward-looking estimate, not a measurement of skills already lost; it supports reviewing role requirements as work changes. Source
Begin with job analysis
Before writing, examine the work with the people who understand it. Speak with the manager, current role holders where appropriate and teams that depend on its outputs. Review recurring tasks, important decisions, handovers and problems. A job title alone may conceal substantial differences between roles in different organisations.
The U.S. Office of Personnel Management describes job analysis as examining tasks, competencies and their relationship. That methodological distinction is useful beyond its original administrative setting: first understand the work, then identify the capabilities it requires. It does not mean U.S. employment rules apply to a UAE organisation.
Write a clear purpose statement
Explain the role’s contribution in a short paragraph. For example, a fictional service coordinator might organise incoming requests and maintain clear handovers so that customers receive an agreed next step. This is more informative than saying the role supports excellence or performs duties as required.
Use a recognisable title that matches the scope. Inflated titles may attract the wrong expectations, while internal abbreviations can confuse candidates. Identify the department and reporting relationship, and distinguish line management from project coordination where both are involved.
Describe responsibilities as meaningful outputs
Group related duties into a manageable set of responsibilities. Use an action and an object, then explain the purpose or expected output where helpful. “Maintain the service request log and flag overdue actions” tells the reader more than “Handle administration.” Avoid an exhaustive record of every minor activity.
Prioritise the work that defines the role. If responsibilities are likely to change, explain the relevant scope without using an unlimited catch-all clause as a substitute for clarity. A description should remain useful when ordinary tasks vary, while still revealing the boundaries of the job.
Specify authority and interfaces
Responsibility without authority creates confusion. State which decisions the role can make, which require approval and when an issue should be escalated. A coordinator who schedules approved work is not necessarily authorised to promise a new delivery date or waive a fee.
Identify important working relationships. Explain who supplies information, who receives outputs and where the role must coordinate with others. This helps prevent duplicate work and gaps between departments. Connect the description to the actual process rather than designing it as an isolated HR document.
Separate essential criteria from preferences
For each requirement, ask how it connects to a responsibility and how it will be assessed. Distinguish capabilities needed on entry from those that can reasonably be learned. Avoid adding qualifications, years of experience or language requirements simply because they appeared in a previous advertisement.
| Requirement type | Practical question | Example of clearer wording |
|---|---|---|
| Knowledge | What must the person understand? | Knowledge of the workflow relevant to the assigned service |
| Skill | What must the person be able to do? | Organise requests and maintain accurate records |
| Behaviour | What observable conduct matters? | Escalate conflicting commitments promptly |
| Qualification | Is a credential necessary for the work? | Name the required credential and the reason where applicable |
Use inclusive, job-related language. Review criteria that may unnecessarily exclude suitable applicants and obtain appropriate HR or legal input where needed. A fair description focuses on the work and the evidence of capability rather than assumptions about the kind of person who normally holds the role.
Connect the description to selection
Decide how essential criteria will be checked. A structured interview can explore relevant experience, while a proportionate work sample can show how a candidate approaches a realistic task. Use consistent criteria and explain the assessment appropriately. Do not ask candidates to provide substantial unpaid work disguised as a test.
Keep the job description distinct from the recruitment advertisement. The advertisement can summarise the opportunity and application process, but it should not contradict the underlying role. Candidates need an accurate account of the work, location and relevant conditions, not only attractive language about culture.
Test the draft with a realistic situation
For the fictional service coordinator, imagine that two departments request the same limited resource. Does the description make clear whether the coordinator decides priority, seeks approval or escalates the conflict? If not, the responsibilities may sound complete while leaving a common decision unresolved.
A clearer responsibility could read: “Record competing requests, check the approved priority rules and refer unresolved conflicts to the operations manager before confirming a commitment.” The coordinator prepares the information and communicates the approved decision; the manager resolves exceptions outside the coordinator’s authority. Name the actual decision owner and escalation route in your organisation rather than copying this example unchanged.
To test the related selection criterion, give candidates the same short fictional scenario and ask them to explain their next steps. Agree the assessment criteria beforehand: accuracy of the request record, use of the priority rules, recognition of authority limits and clarity of the proposed communication. Assess the reasoning against those criteria rather than rewarding confidence alone. This connects the role to observable evidence of capability. The example is illustrative, not an ATMACSS client case or a universal template.
Approve, use and maintain the document
Describe the role rather than the strengths or habits of its current holder. Keep relatively stable responsibilities in the job description, and record period-specific targets in the performance plan. For example, responsibility for maintaining accurate request records can remain stable while the agreed quality target changes. Keep the two documents linked so that changing a target does not silently change the job’s authority or scope.
Have the responsible manager and appropriate HR reviewer confirm the scope. Record the owner, approval date and version. Share the description during onboarding and use it to explain priorities and interfaces. A document stored without discussion rarely resolves conflicting expectations by itself.
Review it when responsibilities, systems or reporting relationships materially change. Do not wait for the next vacancy if the role has already become different. Keep changes consistent with the relevant employment arrangements and organisational processes, and avoid silently expanding responsibilities through an outdated document.
Clarify your operating roles with ATMACSS
Bring your organisation structure, process maps and examples of overlapping responsibilities to a discussion about Business & Operations Modelling with ATMACSS. The performance management guide explains how a clear role can then support expectations, evidence and useful review conversations.