A draft job description template gives you a structured starting point for explaining a role before you publish a vacancy or share it internally. Use the blank template below to capture the job’s purpose, responsibilities, requirements, and working arrangements, then tailor each field to the actual position.
What a job description does
A job description describes the work a position is responsible for and the context in which that work happens. It can support recruitment, help candidates assess whether a role fits their experience and interests, and give hiring teams a shared reference during interviews. Once someone is hired, it can also clarify expectations, although it should not be treated as a substitute for regular communication about changing priorities.
A job description is different from a job advertisement, even though the two often overlap. The description is the underlying account of the role; the advertisement is the public-facing message used to attract applicants. An advertisement may be shorter and more promotional, while the description typically records more detail about duties, reporting relationships, and requirements. Organizations sometimes use one document for both purposes, but should still make sure it is readable and suitable for candidates.
It is also different from a person specification. A job description focuses on the work; a person specification focuses on the qualifications, skills, and experience a candidate needs or may benefit from having. Combining them can be practical, as in the template here, provided the distinction remains clear.
What to decide before drafting
Do not begin by copying a list of duties from an old posting. First confirm what the role needs to accomplish now. A position may have changed because of new team priorities, revised processes, or work that has moved to another role. A fresh draft is an opportunity to describe the current job rather than preserve outdated assumptions.
- Purpose: State why the position exists and what useful result it contributes.
- Scope: Identify the work the role owns, supports, or performs in collaboration with others.
- Authority: Clarify decisions the employee can make and matters that require review or approval.
- Working arrangements: Confirm location, schedule, travel, employment type, and reporting line where those details are known and relevant.
- Requirements: Separate genuine necessities from preferences that could be learned on the job.
Ask the manager who understands the work to review the draft, and, where appropriate, invite input from people who collaborate with the position. Their perspectives can reveal missing responsibilities or unclear handoffs. Agree on the intended audience, too: an internal role profile may need operational detail that would distract in a public posting.
Draft Job Description Template
Copy the blank fields into a document and replace the underscores with role-specific information. Remove any section that does not apply, and do not leave guessed details in the final version.
| Field | Blank template |
|---|---|
| Job title | ____________________________ |
| Team or department | ____________________________ |
| Reports to | ____________________________ |
| Location and work arrangement | ____________________________ |
| Employment type and schedule | ____________________________ |
| Role purpose | ____________________________ |
| Key responsibilities | 1. ____________________________ 2. ____________________________ 3. ____________________________ |
| Regular collaborators | ____________________________ |
| Required qualifications or skills | ____________________________ |
| Preferred qualifications or skills | ____________________________ |
| Tools, equipment, or working conditions | ____________________________ |
| How success will be discussed | ____________________________ |
| Posting or review date | ____________________________ |
Sample — fictional details: The example below is illustrative only. Its details are invented and should not be copied as facts about a real opening.
| Field | Fictional sample |
|---|---|
| Job title | Community Events Coordinator |
| Team or department | Community Programs |
| Reports to | Programs Manager |
| Location and work arrangement | Riverton; primarily on-site, with occasional off-site events |
| Employment type and schedule | Full-time; some planned evening events |
| Role purpose | Coordinate practical arrangements for public workshops and help the team deliver a welcoming participant experience. |
| Key responsibilities | Maintain event schedules; coordinate room and materials setup; share confirmed event information with participants. |
| Regular collaborators | Programs staff, venue contacts, and event participants |
| Required qualifications or skills | Clear written communication and experience coordinating schedules or event details |
| Preferred qualifications or skills | Experience supporting community workshops |
| Tools, equipment, or working conditions | Standard office equipment and occasional event setup |
| How success will be discussed | Through regular check-ins about coordination, preparation, and participant communication |
| Posting or review date | Fictional sample date: 15 March 2026 |
How to write each section
Title and reporting line: Choose a title that accurately describes the level and kind of work. Avoid internal shorthand that a candidate is unlikely to recognize. Name the role’s manager or reporting function when known; if the structure is still being confirmed, verify it before publishing rather than presenting a guess as settled fact.
Role purpose: Aim for a short explanation of the position’s contribution. A useful pattern is: “This role [main contribution] for [people, team, or process] by [broad approach].” For example, “This role keeps customer orders moving by coordinating accurate handoffs between the service and fulfillment teams.” The sentence should describe the job, not make a sweeping promise about the organization.
Responsibilities: Use action verbs and name the work product or outcome. “Prepare a weekly inventory summary for the team” is more informative than “handle inventory.” Group related tasks, and put the central duties before occasional or supporting ones. A list should be representative, not an attempt to predict every task an employee might ever be asked to do.
Qualifications: Separate required qualifications from preferred ones. A requirement should have a clear connection to doing the work; a preference describes experience or knowledge that could help but is not essential. Describe the capability itself where possible. For instance, “can explain project updates clearly in writing” may be more useful than an unexplained list of credentials. Do not add a degree, length of experience, or specialized tool simply because it appeared in a previous description.
Practical details: Give candidates concrete information about location, schedule, travel, reporting, or work conditions when those details are known. If arrangements vary, state that plainly and explain what is expected. Do not imply flexibility or a particular arrangement unless the hiring team can support that description.
Turn vague duties into observable work
Specific wording helps both candidates and hiring teams understand what a responsibility means. Compare “support communications” with “draft a monthly update, check it with the program lead, and send the approved version to the subscriber list.” The second example identifies a task, a review step, and an output. It is not necessarily better for every job, but it is clearer when those details are genuinely part of the role.
Likewise, “be a team player” is a broad personal judgment, not a description of work. If collaboration matters, describe the behavior: “share project status at the weekly planning meeting and flag schedule risks to the project lead.” This wording makes the expectation easier to discuss and gives applicants a more concrete picture of daily work.
Be careful not to turn every duty into a numerical target. Measures can be useful when they already exist and are meaningful, but a draft should not invent quotas or performance guarantees. If outcomes are still being defined, describe the work and say that priorities will be agreed with the manager. The point is clarity, not artificial precision.
Make the draft clear and inclusive
Use plain language and explain necessary specialist terms. Candidates may understand the work but not an organization’s internal vocabulary. Prefer short sentences, active verbs, and a readable list over a dense block of text. A person should be able to scan the posting and quickly find the role’s purpose, main duties, and essential requirements.
Review requirements for relevance and avoid wording that implies a preferred background where the work does not require it. For example, specify the communication task or schedule requirement instead of using vague labels such as “culture fit.” Consider whether a requirement describes an essential outcome or merely the way the current team happens to complete it. A different candidate may be able to achieve the same outcome through another approach.
Accessibility also concerns the information provided. Explain work arrangements and essential working conditions as accurately as possible, and provide a clear way for candidates to ask process-related questions or request an accommodation if the organization offers that route. The exact wording and process should be checked against the organization’s policies and applicable requirements rather than copied from a generic template.
Review, approval, and maintenance
Before sharing the draft, read it from two viewpoints: someone who knows the job and someone who does not. The manager can check the accuracy of duties and decision authority; a colleague unfamiliar with the role can identify unexplained jargon or missing context. Confirm that the title, reporting line, schedule, location, and required qualifications match the opening.
A practical review sequence is:
- Ask the manager to confirm the role’s purpose, responsibilities, and boundaries.
- Check each requirement against an actual task or working condition.
- Ask a reviewer to flag unclear, redundant, or unsupported statements.
- Confirm operational details with the people responsible for approving them.
- Record who approved the final version and when it should next be reviewed.
Review the description when the role changes substantially, not only when a vacancy opens. A regular review can catch responsibilities that have moved, outdated tools, or working arrangements that no longer match reality. Keep a dated version so the team can distinguish the current description from an older draft. If using the same content for a public posting, check that the public version is still accurate and contains the details candidates need.
Common drafting mistakes
- Copying an old description without checking it: Duties, reporting relationships, or qualifications may have changed.
- Listing everything the employee might do: An exhaustive list obscures the role’s main purpose and can make ordinary collaboration sound limitless.
- Mixing essential and optional qualifications: Candidates may treat every bullet as a strict requirement unless the distinction is explicit.
- Using vague traits instead of work examples: Replace labels such as “high-energy” with relevant tasks, schedules, or collaboration expectations.
- Promising details that are not confirmed: Verify location, hours, travel, and flexibility before publication.
- Writing only for insiders: Translate abbreviations and internal process names into terms an external reader can understand.
A job description is a practical communication document, not a prediction that every day will follow the same script. It should set a useful baseline while leaving room for reasonable changes in priorities. If a hiring situation raises legal or regulatory questions, ask a qualified professional for advice rather than relying on this general template.
Frequently Asked Questions
What should a job description include?
A useful description generally includes the title, team, reporting line, role purpose, main responsibilities, relevant qualifications, and practical working details. Add information such as schedule, location, or travel when it is applicable and confirmed.
What is the difference between a job description and a job posting?
A job description explains the role and its work. A job posting is the message used to advertise an opening and invite applications. A posting may draw from the description but can be shorter and shaped for external readers.
How long should a job description be?
There is no single ideal length. Include enough detail for a reader to understand the position and assess the requirements, but remove repeated duties, irrelevant background, and internal jargon. A concise, specific description is more useful than a long list without priorities.
Should a job description list required and preferred qualifications separately?
Yes, when both kinds of criteria are used. Separating them helps candidates understand which qualifications are essential and which are additional advantages. Make sure each required item is genuinely connected to the work.
How often should a job description be updated?
Review it when the position’s responsibilities, reporting line, schedule, or working arrangements change, and before reusing it for a new opening. A dated review makes it easier to catch information that has become stale.