When two employees say, “That is not my responsibility,” the problem is not always the people. The role may be unclear, the structure may have changed, or the manager’s expectations may never have been documented.
A useful job description connects the role to its business purpose and defines outcomes, responsibilities, authority, relationships, requirements, and success measures. It supports integrated HR operations, not recruitment alone.
Start With the Structure
Before drafting, clarify the department’s purpose, owned processes, decision boundaries, and dependencies with finance, sales, and operations. Distribute business outcomes across roles. Design the role around the work, not around the current employee.
Essential Components
- Job title, department, and reporting line.
- Concise role purpose.
- Prioritized outcomes and responsibilities.
- Authority limits and approval points.
- Key internal and external relationships.
- Required knowledge, experience, and skills.
- Performance indicators linked to results.
- Issue date, document owner, and review cycle.
Short Example: Customer Service Officer
Purpose: Handle enquiries and follow cases through resolution while protecting customer experience.
Responsibilities: Receive and classify cases, respond through approved channels, document interactions, escalate according to the matrix, and follow through to closure.
Authority: Resolve standard cases within policy and escalate compensation or exceptions.
Indicators: Response time, cases closed within the agreed level, reopening rate, and documentation quality.
“Respond to customers” is an activity. A performance indicator shows the speed or quality of the result.
Test Before Approval
Ask the manager and employee separately for the role’s top three outcomes, decision rights, and overlap points. Walk through a real case to identify who initiates, approves, supports, and receives information.
A document with dozens of equal tasks or open-ended wording will not improve hiring or performance. Focus on essential accountability and define flexibility responsibly.
Connect It to Hiring and Performance
The description should inform selection criteria, interview questions, onboarding, and probation goals. Later, performance outcomes can be derived from it, but every task should not become a KPI. Review the description when structure, technology, or scope changes.
Analyze the Job Before Writing
Collect information from multiple sources: the manager, job holder, process owner, and the systems or documents used by the role. Ask about expected outcomes, recurring decisions, internal customers, risks, and situations that create delay or conflict.
Do not document current activity blindly. Some tasks may be outdated habits or workarounds for a gap elsewhere. Compare the current role with the organization’s next-stage need and state whether the document describes today’s role or a target design.
Add a Responsibility Matrix
When several roles participate in one process, use a matrix such as RACI to identify who performs, remains accountable, advises, and receives information. In recruitment, a manager may raise the request, HR validates the description, leadership approves budget, and a technical specialist assesses capability.
The matrix does not replace job descriptions. It exposes the spaces between roles, where work commonly stalls. Each step should have one final accountable owner even when several people contribute.
Define Job Levels and Career Paths
Two employees may share a title but operate at different levels of complexity, independence, and impact. Differentiate junior, intermediate, and senior levels through decision scope, case complexity, responsibility, and required knowledge—not years of experience alone.
Clear levels support fairer hiring, development, and promotion discussions and prevent title changes without meaningful role change. They should not be presented as automatic promotion promises; movement depends on business need, demonstrated criteria, and approval.
Quality Checklist
Before approval, verify that the title is understandable, the purpose differs from a task list, responsibilities use clear verbs, authority matches reality, requirements are necessary, and indicators are measurable. Review for unjustified discriminatory criteria and ensure Arabic and English versions remain consistent where both are used.
After implementation, monitor questions from candidates, employees, and managers. Repeated uncertainty about one responsibility usually signals that the description, responsibility matrix, or underlying workflow needs improvement.
Manage a Large Description Project
When many roles require documentation, begin with leadership, critical, and highly overlapping roles. Use one template and shared definitions. Conduct structured manager interviews rather than sending blank forms that every department completes differently.
Track each description through discovery, draft, review, approval, and required update. Set review deadlines and identify stalled approvals. After approval, align the document with the job register, HR system, recruitment material, onboarding plan, and performance framework.
Do not change one description in isolation when the change transfers accountability to another role. Update the structure and responsibility matrix together and communicate the revised boundary to affected employees.
Evidence for Better Workforce Decisions
Consistent descriptions make workforce planning more reliable. Management can see duplicated accountability, missing capability, excessive approval layers, and roles whose workload no longer matches their design. The result may be a hiring need, a process redesign, training, or redistribution—not automatically a new position.
MHRSD’s contract-management information refers to job-title and work details, while official Labor Relations content explains core employment-contract elements. Descriptions, offers, and contracts should therefore be coordinated, without treating a job description as a substitute for a contract or legal reference.
Deliverables may include a job map, descriptions, responsibility matrix, authority matrix, KPI library, and gap report. Quantity and timing depend on structural complexity and manager approvals.
Rikaz by HighSource can interview role owners, draft and test descriptions, resolve overlap, and connect roles to hiring and performance.
FAQs
How is a job description different from a job advertisement?
The description is a comprehensive internal role document; the advertisement is a shorter candidate-facing version.
When should descriptions be reviewed?
When structure, scope, or technology changes, and within a defined periodic review cycle.
Should employees write their own descriptions?
They can explain current work, but managers, process owners, and HR should validate the design and authority before approval.
