Most job descriptions are written once and forgotten. How to write job descriptions that support grading, hiring, performance and development.
In many organisations, job descriptions are written when a role is first created, filed away and rarely read again. Over time they drift from reality. Responsibilities are added, reporting lines change, and the document describes a job that no longer exists.
That matters more than it might seem. Job descriptions underpin grading, benchmarking, hiring, performance objectives and development plans. When they are out of date, every one of those processes rests on weak foundations.
| Section | What it should say |
|---|---|
| Job purpose | One or two sentences on why the role exists |
| Key accountabilities | Five to eight outcomes the role is responsible for, not a list of tasks |
| Scope | Budget, team size, geography, customers or other measures of scale |
| Decision-making | What the role can decide alone, and what it recommends or escalates |
| Key relationships | Main internal and external contacts and the nature of each |
| Requirements | Knowledge, experience and qualifications genuinely needed for the role |
| Competencies | The behaviours and technical competencies from your framework, with the expected level |
Describe outcomes, not tasks. "Ensures monthly accounts are closed accurately and on time" says more than "prepares journals, reconciles accounts, attends meetings".
Write for the role, not the person. Describe what the job requires, not what the current holder happens to do or can do.
Be specific about scope. Scope is what separates one level from the next. Two finance manager roles with very different budgets and teams are not the same job.
Keep requirements honest. Inflated requirements, such as a degree for a role that does not need one, narrow the pool of candidates and can create grading problems later.
Keep it short. Two pages is usually enough. Long documents are rarely read.
Build a review into the annual cycle. Ask managers to confirm each description is accurate during objective setting, and update it whenever a role changes significantly. A simple, standard template makes this far easier.
When many descriptions are out of date at once, often before a grading or benchmarking project, a structured refresh is worth the effort. Questionnaires completed by job holders and checked by managers, followed by a consistent rewrite, can update large numbers of roles in a short time.
Humatix refines and rewrites job descriptions for UAE and GCC organisations, using a consistent template that supports job evaluation, grading, benchmarking and competency-based development.