To list duties in a job description effectively, group key responsibilities into 3 to 6 major functional categories, prioritize them in order of strategic importance, and begin each statement with a strong present-tense action verb. Focus on defining the specific action, method, and outcome for each item while specifying frequency and workload percentage where possible. Structuring job duties with clear, actionable bullet points avoids candidate confusion, supports legal compliance, and establishes a solid framework for performance management.
How to List Duties in a Job Description
Writing a well-structured job description is one of the most critical steps in the hiring process. The duties section forms the operational core of the document—it tells prospective candidates what they will actually do every day and provides current management with an objective baseline for performance evaluations. When duties are vague, inflated, or poorly organized, organizations risk attracting unqualified applicants, misaligning team expectations, and creating compliance issues down the line.
1. Why Structuring Job Duties Correctly Matters
Clear job duties serve multiple purposes across the entire employee lifecycle:
- Targeted Recruitment: Candidates can quickly determine whether their skill set aligns with the operational requirements of the position.
- Performance Management: Clear duties establish measurable Key Performance Indicators (KPIs) and accountability standards during probationary and annual reviews.
- Legal and Regulatory Compliance: Distinguishing between essential and non-essential duties ensures adherence to labor laws, compensation grading, and workplace accommodation requirements.
- Organizational Efficiency: Defining clear boundaries prevents task duplication across departments and ensures operational accountability.
2. Core Principles for Writing Clear Job Duties
To create an accurate and engaging list of duties, adhere to the following foundational rules:
Use Strong Present-Tense Action Verbs
Every bullet point should begin with an active, descriptive verb that illustrates what the employee does. Avoid weak or passive phrasing such as “responsible for,” “handles,” or “helps with.”
- Weak:Responsible for answering customer emails.
- Strong:Resolves customer inquiries via email within a 24-hour SLA to maintain high satisfaction scores.
Group Duties into Major Functional Areas
Instead of presenting a random list of 15 to 20 unrelated bullet points, organize tasks into 3 to 6 major operational categories (e.g., Client Account Management, Financial Reporting, Team Leadership).
The Action + Method + Purpose Framework
To write detailed, meaningful duty statements, apply the three-part formula:
- Action (What): What action is being taken?
- Method (How): What tools, systems, or procedures are used?
- Purpose (Why): What is the desired result or organizational impact?
| Component | Example |
| Action (What) | Analyzes weekly sales pipeline data… |
| Method (How) | …using Salesforce dashboards and custom CRM reports… |
| Purpose (Why) | …to identify revenue bottlenecks and optimize rep outreach strategies. |
Distinguish Essential vs. Non-Essential Duties
- Essential Duties: Core tasks that occupy a significant percentage of time (>5–10%) and are fundamental to why the position exists.
- Non-Essential Duties: Secondary or administrative tasks that could be reassigned or performed occasionally without changing the core nature of the role.
3. Step-by-Step Process for Drafting Duties
Step 1: Conduct a Brief Job Analysis
Gather input from team leads, department managers, or high-performing employees currently in the role. Focus on how the work is executed today, rather than outdated legacy expectations or an unrealistic wishlist.
Step 2: Identify and Prioritize Core Functions
List all routine activities, then cluster them into core functional pillars. Order these categories by strategic importance to the organization rather than chronological sequence.
Step 3: Write Concise Bullet Points
Draft 3 to 5 concise bullet points per category. Keep sentences direct and easy to scan, aiming for 15 to 25 words per bullet point.
Step 4: Add Frequency and Workload Allocations
Where applicable, indicate the approximate percentage of time dedicated to each primary function (ensuring the total equals 100%):
- 40% – Strategic Account Management
- 30% – Team Supervision & Coaching
- 20% – Budgeting & Financial Forecasting
- 10% – Administrative Compliance
4. Common Pitfalls to Avoid
- Creating a “Laundry List”: Listing dozens of micro-tasks (e.g., “opens office doors,” “orders pens”) overwhelms applicants. Focus on high-level deliverables.
- Combining Multiple Roles into One: Asking a single candidate to handle software development, graphic design, and human resources creates an unrealistic job profile and leads to high turnover.
- Using Internal Jargon or Acronyms: Avoid proprietary internal terminology, project codenames, or obscure software names that outside candidates will not recognize.
- Failing to Update Descriptions Regularly: Job duties evolve. Review position descriptions annually to remove obsolete responsibilities and add modern workflows.
5. Examples of Well-Written Job Duty Bullet Points
Marketing Manager
- Campaign Execution (35%): Designs and deploys multi-channel digital marketing campaigns across search, social, and email platforms to drive lead generation.
- Performance Analytics (25%): Evaluates conversion metrics and campaign ROI using Google Analytics to optimize monthly marketing spend.
- Content Management (25%): Oversees the editorial calendar, coordinating with freelance writers and graphic artists to maintain brand consistency.
- Team Supervision (15%): Mentors two junior marketing specialists, providing bi-weekly coaching and annual performance reviews.
Senior Software Engineer
- Core Development (50%): Writes, tests, and maintains clean, scalable Python code for high-throughput cloud infrastructure.
- System Architecture (20%): Partners with product managers to design microservices systems that meet security and performance benchmarks.
- Code Review & Quality Assurance (15%): Conducts rigorous peer code reviews to enforce software standards and prevent deployment bugs.
- Technical Documentation (15%): Maintains comprehensive API documentation and system specifications to streamline onboardings.
Frequently Asked Questions
How many duties should be listed in a job description?
A well-balanced job description typically includes 5 to 10 primary duties, grouped under 3 to 5 functional headings. Listing fewer than 5 duties may leave the role undefined, while listing more than 12 bullet points can overwhelm candidates and obscure the core responsibilities.
What is the difference between job duties and job responsibilities?
Job responsibilities define the overarching outcomes or operational areas an employee owns (e.g., “Ensuring financial reporting accuracy”). Job duties are the specific, actionable tasks executed to achieve those responsibilities (e.g., “Reconciles monthly bank statements using QuickBooks”).
Should job duties be listed by importance or frequency?
Job duties should always be prioritized by strategic importance first. Essential functions that directly impact key business goals should appear at the top of the list, even if they are performed weekly or monthly rather than daily.
Why should every duty start with an action verb?
Starting duty statements with present-tense action verbs eliminates ambiguity, establishes an active tone, and clearly describes what the candidate will do. Action verbs make the job description easier to scan and align directly with measurable performance criteria.
How do you draft duties for a newly created role?
When drafting duties for a new role, focus on the business problems the position is designed to solve. Map out the expected key deliverables, consult similar industry benchmarks, and outline 4 to 6 foundational functions, leaving room for adaptation as the role matures.
Is it necessary to include a catch-all duty like “performs other duties as assigned”?
Including a standard catch-all clause is a standard management practice that offers operational flexibility for unexpected tasks. However, it should not be used as a substitute for defining core responsibilities or to assign duties that drastically deviate from the role’s scope.