How to make a Job Description
This module provides a comprehensive overview of the process of creating effective job descriptions and conducting job analyses. It explains what a job description is, why it is important, and how it supports various organizational goals beyond recruitment, such as onboarding, performance management, and development. The module covers who can conduct a job analysis, key considerations during the process, and the essential parts of a job description. It also details the goals of job analysis, methods for collecting and interpreting data, techniques for asking the right questions, coding raw data, developing task statements, and setting evaluation criteria. Finally, it guides learners through writing and formatting job descriptions that are accurate, compliant, and aligned with organizational style, as well as understanding success criteria and evaluating the quality of the final output. The content is designed to provide a clear framework for producing structured, reliable, and actionable job descriptions for any organization.
Table of Content
A job description is a formal organizational document that clearly defines the scope and purpose of a specific job position, independent of the individual who occupies it. It communicates what the job exists to accomplish and how it contributes to the organization by describing the nature of the work, the level of responsibility involved, and the expectations associated with performing the role.
This document serves as an authoritative reference that establishes consistency in how a position is understood, managed, and evaluated across the organization. It provides a common framework for decision-making in areas such as recruitment, training, performance management, and workforce planning, while also helping ensure clarity, accountability, and alignment between organizational goals and job execution.
Job Description
Definition
Why a Job Description is Important?
There are many examples that demonstrate why a Job Description (JD) is important at every stage of an employee’s life cycle.
Before Hiring
Attracts the right candidates
Guides selection
Builds employer credibility
On the Job
Clarifies expectations
Supports fair pay
Guide career growth & internal recruitment
Improves performance management
When Leaving / Retiring
Enables knowledge transfer
Ensures continuity
Prevents operational gaps
Helps organizational transition
Who Can Conduct a Job Analysis?
Before conducting a job analysis and creating a job description, an organization must consider several factors. Resources are the primary consideration, encompassing budget, role complexity, and time constraints. In addition, the availability of other supporting resources should also be evaluated.
Who can conduct a job analysis?
-
Human Resources (HR) Professionals
-
Job Incumbents or Supervisors, Managers
-
Consultants
-
College Interns or Graduate Students
-
Automation / Job Analysis Software Tools
Key Considerations During Job Description Development
-
Alignment with legal registration and employment structure
Ensures the role fits the organization’s legal status and intended employment arrangement, influencing how the role is defined and documented. -
Maintain thorough documentation
Keep detailed records of the job analysis process, decisions made, and data collected. This provides legal protection, ensures transparency, and allows the organization to reference or update the role later if needed. -
Legal and compliance awareness
Keeps labor laws, equal opportunity principles, and internal policies in mind to avoid embedding risk or bias during job analysis and drafting. -
Consistency in organizational style, tone, and values
Aligns the role with how the organization actually operates, including communication norms, autonomy, and the degree of standardization or subjectivity in the work. -
Internal alignment during data collection
Confirms shared understanding of reporting lines, accountability, and decision-making while defining the role.
Parts of a Job Description
Many elements can be included in a job description, but deciding what belongs in the final document depends on two key considerations:
-
Relevance:
Information should be included only if it directly supports the purpose of the job description. -
Legal or Organizational Requirements:
Certain details may be required by law, internal policies, or safety regulations and must therefore be included.
Content That Should Always Be Included:
-
Job Title
-
Brief Position Summary
-
Work Activities
-
Job Competencies and Qualifications (SKAOs)
-
Work Performance
Content That Depends on the Situation:
-
Tools and Equipment
-
Work Setting
-
Compensation and Benefits Information
-
Environmental Conditions
-
Work Schedule and Hours
-
Work Intensity and Stress Levels
-
Physical, Psychological, and Social Demands
-
Special Conditions and Context
-
Organizational Career Path
Job Title – The name of the position that reflects its role and responsibilities.
Brief Position Summary – A short overview of the job’s main purpose and key responsibilities.
Work Activities – The specific tasks and duties the employee is expected to perform.
Tools & Equipment – Tools, technology, or equipment needed to perform the job.
Work Settings – The physical location or environment where the job is performed.
Job Competencies & Qualifications (SKAOs) – Required skills, knowledge, abilities, others and formal qualifications.
Compensation & Benefits Information – General details about pay structure, grade, or salary range.
Environmental Conditions – Physical or environmental factors affecting the work (e.g., noise, temperature, hazards).
Work Schedule & Hours – Expected working hours, shifts, and flexibility requirements.
Work Intensity & Stress Levels – Expected workload, pressure, and peak activity periods.
Physical & Psychological & Social Demands – Physical effort, mental requirements, and social interaction expectations.
Special Conditions & Context – Any unique or exceptional job requirements, such as legal or safety rules.
Work Performance – Criteria and standards for evaluating success and productivity in the role.
Organizational Career Path – Potential growth, advancement, or promotion opportunities within the company.
How to do a Job Analysis?
To develop an effective job description, we need to follow a structured process:
-
-
Identify the purpose of creating the job description
-
-
Select data collection methods
-
Choose appropriate methods based on the goal, available resources, and time constraints.
-
-
Gather and organize job information
-
Collect relevant data about the job and convert it into a clear, usable document.
-
-
-
Confirm that the information accurately reflects the job’s real tasks and requirements, and ensure the final document is practical and suitable for its intended purpose.
-
Select goal
Confirm suscess
Choose data collection methoods
Collect & Transform data
Possible Goals of a Job Description
Writing a job description can serve multiple goals, from attracting the right talent to supporting career development, guiding performance management, planning compensation and rewards, ensuring legal compliance, and preserving organizational knowledge. Understanding these potential goals helps you design a job description that effectively serves the organization and its employees
It is important to identify the intended purpose before job analysis, as this not only conserves time and resources but also increases the document’s overall usability.
As the table shows, the specific goal of the job description determines which sections should be included and emphasized to achieve the desired outcome.
Data collection methods
Data collection is the process of gathering information to accurately understand a job’s tasks, responsibilities, and requirements. Using multiple data sources helps ensure the information is complete, reliable, and reflects both current job performance and organizational needs.
Document-Based Methods
These methods rely on existing written or digital information.
-
Task Inventories – Structured lists that identify and organize the tasks performed in a job.
-
Existing Job Descriptions Within the Organization – Internal documents that outline expected duties and responsibilities.
-
Internet (+GAI) – Online sources and generative AI tools provide industry-wide role information and emerging trends.
-
Other Companies – External job information is used to benchmark roles against industry standards.
People-Based Methods
These methods collect information directly from individuals with knowledge of the job.
-
Job Incumbents – Employees performing the job describe their actual tasks and responsibilities.
-
Supervisors – Supervisors provide insight into performance expectations and job outcomes.
-
Customers – Customers offer feedback on service quality and role effectiveness.
-
Upper-Level Management – Senior leaders share strategic perspectives and future job needs.
Direct Methods
These methods involve firsthand examination of the job itself.
-
Observation – The analyst watches employees perform their work to understand real job behaviors.
-
Job Participation – The analyst performs the job to gain direct experience with its demands.
-
Workshops – Group sessions where stakeholders collaboratively identify and validate job tasks.
What questions should be asked for each part?
In job analysis, the goal is to ask questions that reveal the full scope of a role, what it involves, how it is performed, and what is required for success rather than collecting isolated facts. Effective questions help respondents describe the job clearly and consistently, providing information four our purpose of the job description.
Start by clarifying the identity and purpose of the position. Questions about the Job Title and a Brief Position Summary help define the role’s scope, distinguish it from similar positions, and capture its core objectives. These questions are usually directed to supervisors or managers, who understand the overall role and how it fits into the organization.
Example questions include: “What is the primary purpose of this position?” and “How does this role differ from other, similar positions in the department?”
Next, explore the work itself. Questions about Work Activities, Tools & Equipment, and Work Settings reveal how tasks are performed and under what conditions. These are best asked to employees currently performing the job, since they experience the day-to-day realities firsthand. To understand what is required for effective performance, ask about Job Competencies & Qualifications (SKAOs), which can be informed by both employees and supervisors.
For example: “What tasks take up most of your time during a typical workday?”
It’s also important to examine conditions and demands. Questions about Work Schedule & Hours, Work Intensity & Stress Levels, and Physical, Psychological & Social Demands are usually answered best by employees, as they experience the workload, pace, and social interactions directly. Questions on Environmental Conditions and Special Conditions & Context may be answered by both employees and supervisors, depending on whether the issue is operational (e.g., noise, temperature) or regulatory (e.g., safety rules).
An example question might be: “What physical or mental demands are most challenging in this role?
Finally, questions should address performance and organizational context. Asking about Work Performance standards, Compensation & Benefits Information, and Organizational Career Path is typically directed to supervisors or HR, since they have a broader perspective on evaluation criteria, pay structures, and advancement opportunities.
Raw Data & Coding
Raw Data
Raw data is the unprocessed information collected from any source. In its raw form, it is often messy, unstructured, and may include irrelevant information. This is normal; raw data simply captures everything as it exists, before you filter, summarize, categorize or interpret it.
Example of raw data coming from a questions:
-
What are the tasks you perform every day, and which take the most time?
-
Every day, I answer customer calls and emails, which takes up most of my time. I also log each interaction in the CRM system and follow up on unresolved issues. Weekly, I generate reports on ticket resolution times and trends.
-
Raw Data is messy and unfiltered. It may include irrelevant or redundant information. Its purpose is to capture everything.
Coding
Coding is the process of identifying the meaningful information within the raw data and assigning labels or tags to it. This is how analysts separate the relevant from the irrelevant. Coding helps structure messy, sentence-like raw data into clear, manageable concepts.
Example of codes (coming from raw data):
-
Answer customer - calls or email (every day)
-
log interaction - CRM system
-
Follow up with unresolved cases
-
Generates report (weekly)
Coding extracts meaningful information. Each code is a discrete label representing a task, skill, or requirement.
Categorizing Codes
After coding, you can group codes into broader categories to identify patterns, themes, and job dimensions. Categorization organizes information into higher-level areas that reflect the job as a whole.
Example of categories:
-
Customer Data Management:
-
(Log interaction - CRM system / Double checking customer account details before making changes)
-
-
Customer Communication:
-
(Answer customer - calls or email / Follow up with unresolved cases)
-
The process preserves the link to the original data. By starting from sentences, coding, and categorizing, analysts maintain traceability while creating a structured understanding of the job that can be used for .
The process preserves the link to the original data. By starting from sentences, coding, and categorizing, analysts maintain traceability while creating a structured understanding of the job that can be used for .
Raw Data Coding - Additional Examples
Raw Data
-
Are there recurring tasks that others might not notice but are critical?
"Yes, there are smaller but important tasks that aren’t obvious, such as double-checking customer account details before making changes, flagging trends in recurring issues for the team, and updating internal documentation to keep knowledge resources accurate. These tasks help prevent errors and improve overall efficiency, even if they’re not visible to supervisors or customers."
-
Which tasks are essential for this employee to achieve their performance goals and meet organizational expectations?
"The most essential tasks include responding to customer inquiries promptly, resolving issues on the first contact when possible, and accurately logging all interactions in the CRM system. Following up on unresolved cases and escalating complex problems ensures that service-level agreements are met and customer satisfaction targets are achieved."
-
Double checking customer account details before making changes
-
flagging trands in reuccuring issues for the team
-
updating internal documents to keep knowledge resources accurate
-
These tasks help prevent errors and improve overall efficiency
-
Responding customer, resolving issues
-
accurately logging all interactions in the CRM system
-
Follow up with unresolved cases
-
Ensure that service leads to satisfaction
Developing clear Task Statements for Work Activities
One of the most important parts of a job description is the task statement because it clearly defines what the job actually requires on a day-to-day basis. Knowing how to write effective task statements ensures roles are clearly understood, accurately evaluated, and fairly assessed for performance, training, and compensation purposes.
1. One Action Per Object
Each statement should describe only one action applied to one specific object to avoid confusion, though closely related actions may be included if they occur together or happen at the same time.
2. Appropriate Reading Level
Statements should be written in clear, simple language suitable for the intended audience.
-
Consistency in Tense (SP) - Use the same verb tense (simple present) throughout to ensure clarity and consistency.
-
Include relevant question parts
Clearly state what is done, to what or who, and what is being used. - (action/object/tool)
Include necessary context to explain how, when, where, why, with whom the action occurs. - (how/where/when/why/whom)
3. Avoid Competencies
Focus on observable tasks or actions rather than personal traits or abilities.
4. Avoid Policies
Describe what is done in practice, not organizational rules or formal policies.
5. Stand-Alone Statements
Each statement should be complete and understandable without additional context.
6. Include Clear Level of Decision-Making Authority
Specify whether the action involves making decisions, recommendations, or execution.
Example
Categorized code
Customer Communication:
Answer customer - calls or email
Headset for phone calls
Responding customer, resolving issues
Ensure that service leads to satisfaction
Action
Object
Tool (1)
Answers customer questions by email or phone using headset to ensure issues are resolved.
How
Tool (2)
Tool (3)
Why
Task Statements - Additional Examples
Code
-
“I create interactive table to show performance metrics.”
-
“The team needs a dashboard in EXCEL to monitor key performance in real time.”
-
“I set up tracking systems to help the team make faster, better decisions.”
Task Statement
"Develops interactive tables in Excel that display key performance metrics in real time, to help the team make better and faster decisions."
Code
-
“I analyze sales data to identify trends and patterns.”
-
“Understanding trends in sales data helps guide business decisions and strategy.”
-
“I use Tableau to summarize sales trends for management review.”
Task Statement
"Analyze (maybe + summarize) sales data in Tableau by understanding trends to identify trends and patterns for managers to guide business decisions and strategy."
Scale & Thresholds for Evaluation
After data have been collected and coded, scales are created to evaluate the relative importance of job-related information in a consistent and systematic way. Each type of information is evaluated subjectively using dimensions that best reflect its role in the job; for example, task statements are rated using frequency (how often the task is performed) and criticality (the impact of errors or failure to perform), while other job elements are rated using dimensions that capture their relevance and importance. Using clearly defined, job-appropriate scales ensures ratings are easy to understand, apply consistently, and defend analytically.
Tools & Equipment
Specialization & Safety Impact & Frequency
Criteria
Special Conditions & Context
Legal compliance & Hazard exposure & Confidentiality level
Task Statement
Frequency & Criticality
Environmental Conditions
Exposure + Frequency + Risk
Scale
Score Frequency
(0) – The task is never performed
(1) – Task is performed once a year.
(2) – Task is performed few times a year.
(3) – Task is performed once per month.
(4) – Task is performed several times per week
(5) – Task is performed every workday.
Once the scales are established, the collected job-related information is rated using these scales. Rating scales typically range from 1–5, though wider ranges (e.g., 1–10 or 0-6) may be used when greater differentiation is needed, depending on the level of detail required for the evaluation. Depending on the information, ratings may be collected from the employer, the employee, or both. For example, task statements are often rated for frequency on a scale where 0 indicates the task is never performed and 5 indicates it is performed daily by employees, while criticality is rated based on the impact of errors or failure to perform the task, typically as assessed by the employer.
After the evaluation criteria and rating scales have been developed and applied by appropriate subject-matter experts (SMEs), such as employees or employers with direct knowledge of the job, thresholds are established to determine which job-related information should be included. Thresholds define decision rules for inclusion or exclusion and may involve special conditions; for example, elements may be automatically excluded if any rating equals 0, or automatically included if any rating equals 5. Several threshold-setting methods may be used.
Trashold
Relative Threshold (Percentile Method): Based on their position relative to others (e.g., top 40%).
Absolute Threshold (Score Method): Based on whether they meet a predefined score cutoff (AVG 3.5+).
Tiered Approach: (Include 4< optional 3-4, exclude 3>) based on score ranges.
Conclusion of Scale & Threshold for Evaluation
-
Job-related information was collected and coded using input from employees and employers serving as subject-matter experts (SMEs) with direct knowledge of the job.
-
Appropriate evaluation criteria and rating scales were established based on the type of information being assessed, with task statements evaluated using frequency and criticality. A standardized numerical scale (e.g., 0–5) was applied, with the option to expand the range when greater differentiation is needed.
-
Each task statement was rated by SMEs, ensuring evaluations reflected both actual job performance and organizational impact.
-
A simple average score was calculated for each task to represent overall importance.
-
Inclusion thresholds were applied using an absolute cutoff (average ≥ 3.5), along with special conditions that automatically excluded tasks rated 0 and automatically included tasks with a rating of 5 on either evaluation criterion.
Writing and Formatting Job Descriptions
-
Follow regulations and inclusive language
Use gender-neutral, non-discriminatory, and accessible wording. Ensure the language complies with labor laws and internal policies while welcoming all potential candidates. -
Maintain organizational style and tone
Keep the description aligned with your organization’s voice, values, and communication norms, reflecting how responsibilities and expectations are usually expressed internally. -
Structure content for readability and usability
Organize the description logically, using clear headings, bullet points, and concise sentences, so that both candidates and internal stakeholders can easily understand the role. -
Ensure accuracy and clarity from analyzed data
Translate the coded and evaluated job information into precise, understandable wording that accurately reflects responsibilities and expectations without ambiguity or unnecessary jargon.
What Makes a Job Description Successful?
When evaluating a final job description, success can be measured by:
-
No overlaps – Clear and distinct sections with no repetition or confusion.
-
SME Validation – Verified and approved by Subject Matter Experts.
-
Added value – Provides meaningful guidance for employees and the organization.
-
Correct – Accurate information about responsibilities, requirements, and conditions.
-
Complete – Covers all necessary sections relevant to its goal.
-
Usability for goal – Designed to serve its intended purpose effectively (e.g., hiring, performance management, legal compliance).
-
Organizational fit – Uses appropriate language, tone, and style for the company context and culture.
If a job description cannot be used for its goal:
-
Check what the problem is.
-
Irrelevant parts may have been included.
-
Some information might be rated incorrectly.
-
Important details may be missing, or unimportant details may clutter the description.
-
Bad coding of raw data can make information confusing or unusable.
-
Adjustments are needed to make the document accurate, complete, and goal-oriented.
Summary
Definition:
A job description is an official document that defines a position’s purpose, responsibilities, and expectations, independent of the individual filling it. It provides a consistent reference for managing, evaluating, and aligning the role with organizational goals, supporting recruitment, training, performance management, and workforce planning.
Organizational Impact:
-
Before hiring: attract the right candidates, guide selection, and build credibility.
-
On the job: clarify expectations, support pay and career growth, and improve performance management.
-
When leaving/retiring: enable knowledge transfer, ensure continuity, and support smooth transitions.
Job Analysis (who):
-
When deciding who will conduct the job analysis, the key considerations are time constraints, role complexity, budget, and the availability of supporting resources.
-
Who can conduct job analysis:
-
HR professionals & Job incumbents; supervisors, or managers & Consultants & College interns or graduate students or can be done by Automation, job analysis software tools.
-
Considerations:
-
Legal, Compliance & Alignment
-
Ensuring Role Fit & Consistency
-
Key Development Considerations
-
Alignment & Compliance
-
Job Description Essentials
Parts
Job descriptions may include many elements, but the final content should be determined by relevance and legal or organizational requirements.
Job Analysis (how)
-
Define the objective
-
Select data collection methods
-
Gather and organize job information
-
Validate and review
Goals
The specific goal of the job description determines which sections should be included.
-
Attracting Possible & the Right Employees
-
Supporting Performance Management & Evaluation
-
Career Development & Organizational Planning
-
Legal & Safety Compliance
-
Organizational Documentation & Knowledge Conservation
-
Developing Compensation & Reward Systems
Data Collection
-
Document-based methods: Use existing internal and external job information (e.g., job descriptions, task inventories, online sources).
-
People-based methods: Gather input directly from employees, supervisors, customers, and leadership.
-
Direct methods: Rely on firsthand examination through observation, job participation, and collaborative workshops.
Questions for Data Collections
Effective job analysis focuses on asking purposeful questions that capture the full scope of a role, how the work is done, and what is required for success. Questions should cover role purpose, work activities, conditions and demands, required competencies, and performance expectations, and be directed to the most appropriate sources; employees, supervisors, or HR, to ensure accurate and consistent job description content.
Raw Data & Coding
Raw data captures all information but is often unstructured and redundant. Coding organizes this data by labeling key tasks, skills, and requirements, preserving links to the original sources while transforming information into a structured and usable understanding of the job.
Task Statement Development (Work Activities)
Task statements define a job’s day-to-day responsibilities
-
Describe one clear action per object
-
Use simple, consistent language and tense
-
Include necessary details (what, how, when, where, why, with whom)
-
Focus on observable tasks, not competencies or policies
-
Stand alone without additional context
-
Clearly state the level of decision-making authority
Scale & Thresholds for Evaluation
-
Creating Evaluation Scales
After data is collected and coded, job-related information is evaluated using clearly defined rating scales. Scales are tailored to the type of information being assessed, such as frequency and criticality for task statements, to ensure consistent, meaningful, and defensible evaluation.
-
Rating Job Information
Once scales are established, employees, employers, or both rate job elements using standardized numerical scales (commonly 0–5). These ratings reflect how often tasks are performed and the impact of errors or failure, capturing both actual work and organizational importance.
-
Applying Thresholds for Inclusion
After ratings are completed by subject-matter experts, thresholds are applied to determine which elements are included. Decision rules, such as minimum average scores or automatic inclusion/exclusion criteria, ensure only relevant and important job information appears in the final job description.
Writing & Formatting
-
Use compliant, inclusive, and accessible language
-
Align tone and style with organizational values
-
Structure content clearly for readability and usability
-
Ensure accuracy and clarity based on analyzed job data
Success?
-
A successful job description is clear, accurate, complete, and validated by SMEs
-
It adds value, fits the organization’s culture, and effectively supports its intended goal
-
If a job description does not work as intended:
-
Identify the underlying issue
-
Remove irrelevant or overlapping content
-
Correct rating or coding errors
-
Add missing critical information
-
Simplify or clarify confusing content
-
-
Revisions should focus on restoring accuracy, clarity, completeness, and purpose alignment
Check Your Knowledge
Raw Data (Example)
A project coordinator was asked: “Describe a typical day at work.”
“I start by reviewing emails from clients and colleagues. Then I update the project tracker with the latest progress. Sometimes I attend brief meetings to align with the team. In the afternoon, I prepare summary notes for the weekly status report. I also occasionally troubleshoot small issues in the project workflow.”