What a job description is for

A good job description answers one question clearly: why does this role exist, and what is it accountable for? Once that is clear, the same document supports five things at once:

  • Recruitment — a clear basis for the advertisement, the shortlist criteria and the interview questions.
  • Job evaluation and grading — evaluators can only grade what is written down. Vague descriptions produce inconsistent grades.
  • Performance management — objectives and KPIs should flow from the role's key accountabilities.
  • Learning and development — the gap between the required competencies and the jobholder's current level becomes visible.
  • Workforce planning and restructuring — you can see overlaps, gaps and unclear reporting lines across the structure.

What to include

Keep one standard template for the whole organization. The sections that matter most are:

  1. Job identification — title, department, grade, reporting line, and the roles that report to it.
  2. Job purpose — one or two sentences on why the role exists. If you cannot write this, the role itself may need rethinking.
  3. Key accountabilities — six to ten statements describing results, not daily tasks. A useful pattern is action + area + outcome: “Prepares the monthly payroll reconciliation to ensure accurate and on-time salary payment.”
  4. Scope and decision authority — budget responsibility, number of people managed, approvals the role can give, and decisions it must escalate.
  5. Key relationships — the internal teams and external parties the role works with, and the purpose of each relationship.
  6. Qualifications and experience — separate the true minimum from what is preferred, so you do not exclude good candidates without reason.
  7. Competencies — the technical and behavioural competencies the role needs, ideally drawn from your organization's competency framework.

Common mistakes we see

  • Copying a generic description from the internet. It rarely reflects your structure, your authority levels or your systems.
  • Listing tasks instead of accountabilities. Long task lists hide what the role is actually responsible for and make grading harder.
  • Writing for the person, not the role. The description should stay valid when the jobholder changes.
  • Inflated titles. A “manager” title with no people or budget creates grading and pay inconsistencies later.
  • Letting descriptions go out of date. After a restructuring, many descriptions no longer match how work is really done.
  • English and Arabic versions that say different things. In a bilingual organization both versions should come from the same source and match in substance.

A simple process that works

  1. Start from the organization structure, so every role sits in an agreed place with a clear reporting line.
  2. Analyse the job through a short questionnaire and an interview with the jobholder and the line manager.
  3. Draft in the standard template, focusing on purpose and accountabilities first.
  4. Validate with the line manager and resolve overlaps with neighbouring roles.
  5. Evaluate and grade the role using one consistent method across the organization.
  6. Approve, publish and use it — in recruitment, objective setting and development plans.
  7. Review it at least once a year, and whenever the structure or the role changes.

Where to begin

If your descriptions are outdated or inconsistent, you do not need to rewrite everything at once. Start with one department or one job family, agree the template, and use that first group to set the standard for the rest of the organization.

Brilyanz helps organizations in Qatar develop job descriptions, carry out job analysis and evaluation, and build grading structures that hold together. See our HR services or book a consultation to discuss your needs.