An employee job description template is a reusable outline for recording a role’s purpose, main duties, reporting relationships, and requirements. Copy the blank template below, customize it for the position, and review it with the people who understand the work before sharing it.
What an Employee Job Description Does
A job description explains what a position exists to do and the general work associated with it. It gives an employee, manager, and hiring team a common reference point. A clear description can support recruitment, onboarding, delegation, and conversations about how a role may change. It should describe the position rather than promise a particular outcome for every person who holds it.
Descriptions are most useful when they reflect the work as it is actually organized. For example, a coordinator who schedules appointments, maintains records, and routes customer questions needs a description that says so—not a broad label such as “handles office tasks.” Specific language helps applicants understand the role and helps current employees distinguish their responsibilities from those of coworkers.
A job description is not necessarily a complete list of every task an employee might ever perform. Work changes, and teams sometimes need people to help with related duties. If the role may include additional tasks, describe that possibility plainly and reasonably rather than relying on vague wording to hide the nature of the work.
Employee Job Description Template
Blank template — copy and fill in the fields that apply.
| Field | Details |
|---|---|
| Job title | |
| Team or department | |
| Work location or arrangement | |
| Employment type or schedule | |
| Reports to | |
| Role purpose | |
| Main responsibilities | |
| Required qualifications or experience | |
| Preferred qualifications | |
| Tools, systems, or work conditions | |
| How success is understood | |
| Date reviewed |
Sample — fictional details for illustration.
| Field | Example |
|---|---|
| Job title | Customer Support Coordinator |
| Team or department | Customer Operations |
| Reports to | Support Team Lead |
| Role purpose | Help customers get clear answers and route complex requests to the right team. |
| Main responsibilities | Respond to routine questions, record request details, maintain help materials, and flag recurring issues. |
| Required qualifications or experience | Clear written communication and experience organizing customer or service requests. |
| How success is understood | Requests are documented accurately, responses are clear, and unresolved issues are escalated appropriately. |
What to Include in Each Section
Keep the opening details short and identifiable. Use the title employees and applicants will recognize, name the relevant team, and state who the role reports to. Note the work arrangement or schedule only when it is known and relevant. If an arrangement varies by location or is still being decided, say that it will be confirmed rather than presenting an uncertain detail as settled.
The role purpose is a brief summary of why the position exists and the value it contributes. One or two sentences are usually enough. For instance, “Maintain accurate inventory records and coordinate replenishment so operational teams can locate needed supplies” is more informative than “Support the inventory function.” It connects the work to its practical purpose without claiming that one employee controls every outcome.
Responsibilities should describe the important, recurring parts of the job. Requirements should distinguish what a person needs on arrival from qualities that are useful but not essential. Include tools, work conditions, or coordination duties only when they are genuinely part of the role. A success section can identify observable expectations, such as timely handoffs or accurate records, without inventing numerical targets that the organization has not set.
How to Write a Clear Description
- Gather current information. Ask the manager and, where appropriate, an employee familiar with the work to describe its regular activities, decisions, and working relationships. Check existing team documents, but treat them as starting points rather than proof that the role has not changed.
- Write the purpose first. Summarize the role’s central contribution. This makes it easier to decide which duties belong in the description and which are incidental.
- Choose the main responsibilities. Group related work into a manageable set of bullets. Start each bullet with an action verb—such as coordinate, review, prepare, maintain, or explain—and add the object or result. “Review incoming forms for missing information and request corrections” tells more than “review forms.”
- Separate requirements from preferences. Include a qualification as required only when it is genuinely necessary to perform the work. Put helpful but nonessential experience under preferred qualifications, or omit it. This prevents a wish list from making the role appear more restrictive than it is.
- Check the wording and details. Replace internal shorthand, unexplained acronyms, and broad claims with language an outside reader can understand. Confirm the reporting line, schedule, location, and examples of work with the appropriate manager.
- Review and date it. Ask a relevant reviewer to check accuracy and clarity, then record when the description was last reviewed. Share the approved version through the organization’s normal process.
Use plain language and active verbs. “Prepare a weekly status summary for the project lead” identifies an action, a deliverable, and its recipient. Avoid sentences that bundle unrelated tasks into a long string. If a responsibility requires several distinct activities, separate them into bullets so a reader can scan the list and discuss individual duties.
Describe Responsibilities Without Overpromising
Good responsibilities are specific enough to be useful but broad enough to cover normal variation. A description for a facilities assistant might say, “Inspect shared areas, log maintenance requests, and coordinate access for scheduled repairs.” It should not say the employee “ensures all facilities are always safe” if that person does not control every condition or decision. Describe the employee’s actions and role in a process, not outcomes beyond their control.
Consider the difference between a core duty and an occasional task. A recurring responsibility belongs in the main list. A rare task may be described as occasional or related work if it is a realistic part of the position. Avoid presenting an unusual assignment as a constant duty, and avoid leaving out a substantial responsibility merely because it is inconvenient to explain. Honest scope helps candidates assess fit and helps managers set expectations after hiring.
Where work is shared, state the relationship accurately. “Coordinates with the finance team to submit purchase records” is different from “approves department spending.” Terms such as leads, advises, approves, and owns can imply different authority. Choose them carefully and check that they match the role’s actual decision-making responsibilities.
Tailor It to the Role and Reader
A template should standardize the structure, not force every position into identical wording. A warehouse role may need practical details about shifts, equipment, or the work setting. A research role may need to explain the type of records, analysis, or collaboration involved. A supervisory description should clarify the scope of coordination or oversight without implying authority the role does not have.
Write for two audiences: people considering the job and people who will work with the employee. Applicants need a realistic picture of the day-to-day work and essential requirements. Coworkers and managers need to understand responsibilities, handoffs, and reporting relationships. If a phrase makes sense only to insiders, explain it or replace it with familiar wording.
Review requirements for relevance. For example, naming a particular credential, language, or amount of experience should reflect a genuine need for this position, not habit or a copied line from another role. Use equivalent wording when different backgrounds could prepare someone to do the work. The goal is an accurate description, not the longest possible list of qualifications.
Job Description, Job Posting, and Performance Goals
These documents are related, but they serve different purposes. A job description is an internal or shared reference about the role’s purpose, duties, and requirements. A job posting is recruitment material that invites applications and may add application instructions, benefits, or information about the hiring process. A posting can draw from a description, but it may be edited for a specific vacancy and audience.
Performance goals are also distinct. They describe expectations or outcomes for a particular period, often with measures agreed by the employee and manager. A job description can provide context for those goals, but it should not be treated as a complete performance review or as a substitute for a manager’s ongoing communication. A role’s recurring responsibilities may remain stable while priorities and time-limited goals change.
Another useful distinction is between a job description and an individual employee profile. The description concerns the position; a résumé or personnel record concerns a person’s experience and history. Keeping that distinction helps the organization update the role without implying that an employee’s personal record has changed.
Common Problems and How to Avoid Them
- Copying an outdated description: Old wording may not reflect current systems, responsibilities, or reporting lines. Compare it with how the work is currently done and revise any stale details.
- Using a vague title or purpose: Labels such as “specialist” can mean different things across teams. Add enough context in the purpose and responsibilities to explain the position.
- Listing every imaginable task: An exhaustive list becomes hard to scan and can obscure the core work. Prioritize recurring, significant duties and handle unusual assignments transparently.
- Mixing essential and preferred criteria: A long list of mandatory credentials may discourage qualified applicants if some are merely desirable. Separate the categories and verify the reason for each requirement.
- Using inflated or ambiguous language: Words like “always,” “all,” or “expert” can set unclear expectations. Prefer concrete actions, realistic scope, and terms that can be understood consistently.
- Leaving out practical context: A title alone may not tell readers about a schedule, work location, or important collaboration. Include relevant details that have been confirmed.
A further misconception is that a template makes a description automatically complete or suitable for every workplace. It does not. The template supplies a structure; managers still need to check the content, communicate changes, and follow their organization’s review process. If a situation requires legal interpretation or other professional guidance, ask a qualified professional.
Reviewing and Maintaining the Description
Review the description when the role is created and whenever a meaningful change affects its purpose, duties, reporting relationship, or working arrangement. A routine review can also uncover small inaccuracies that accumulate over time. There is no single review interval that suits every organization, so follow the organization’s process and the pace at which the work changes.
Keep a clear version or review date so readers can tell whether they have a current copy. When a manager proposes a change, identify what has changed and why, then ask the employee or team members closest to the work to check whether the draft is realistic. This does not mean every duty requires a formal rewrite; the effort should match the significance of the change.
Share the final description with the people who need it, such as the employee, manager, or recruitment team. A document that exists only in an inaccessible folder cannot serve as a useful reference. If the description is used during recruitment, make sure the version shown to candidates accurately reflects the role being offered.
Frequently Asked Questions
What should an employee job description include?
A useful description typically identifies the title, team, reporting relationship, role purpose, main responsibilities, relevant requirements, and practical details such as schedule or work arrangement when known. Add only information that helps readers understand the position.
How long should a job description be?
There is no required universal length. Aim for enough detail to explain the role clearly while keeping it easy to scan. A short description that leaves out core duties is not useful, but a long inventory of minor tasks can hide the important work.
Is a job description the same as a job posting?
No. A job description outlines the position and its work. A job posting is designed to recruit applicants and may include application instructions or other vacancy-specific information. The posting can be based on the description but is not always identical to it.
Should a job description list every possible duty?
No. It should cover the main and recurring responsibilities and explain realistic related work where appropriate. Trying to list every hypothetical task makes the document less readable and may misrepresent what the employee will usually do.
How often should a job description be updated?
Update it when significant changes affect the role, and review it according to the organization’s process. Check details such as duties, reporting lines, and work arrangements rather than changing the document merely to make it look new.
Can employees help write their own job description?
Yes. Employees can provide valuable detail about actual workflows, recurring tasks, and handoffs. A manager should still confirm the role’s scope and reporting expectations, then review the final wording with the people who rely on the description.