In many companies the job description has sat unchanged in the personnel file for years, while the work in the role has moved on. An up-to-date job description is a surprisingly useful document: it clarifies responsibilities, supports onboarding, answers the question about responsibilities and authorities in an ISO 9001 audit and is the basis for every job ad.
This guide shows which contents a job description needs and gives you a job description template to copy along with a filled-in example. The final part looks at the workflows behind the tasks, because even a well-kept job description describes what the role involves and leaves open how the work is done in detail.
What a job description is and how it differs from related documents
A job description describes a position, the role independent of whoever holds it. It defines why the position exists, which tasks and authorities belong to it, how it fits into the organization and which requirements someone has to meet to fill it. The job description should still be accurate when the person in the role changes.
Three documents are often confused with it:
- Job ad. The ad courts applicants and is correspondingly shorter and more promotional. It is derived from the job description.
- Person specification. It covers only the qualification side: training, experience, skills. In a complete job description it is one section among several.
- Employment contract. The contract usually contains a brief characterization of the work, because section 2 of the German Evidence Act (Nachweisgesetz) requires it as part of the statement of essential terms. Most companies keep the detailed job description as a separate document alongside the contract. The FAQ below explains why.
A fourth distinction matters later in this guide: the job description says which tasks belong to the position. How those tasks are done is described in a process description or, for individual activities, a work instruction.
Why you need a job description
There is no legal obligation to keep a detailed job description for every position. In day-to-day work it still helps in many places.
It clarifies responsibilities. Who decides on complaints up to 500 euros and who may switch suppliers is written down, and everyone involved can refer to it when a case comes up.
For onboarding, it is the frame from which the onboarding plan derives its learning objectives, because once you know what the position covers, you can plan what the new person should be able to do after 90 days.
When someone resigns, retires or is out for a longer time, the job description is the first document the manager reaches for. It shows what has to be covered and, in the deputy section, who can cover it.
In quality management, ISO 9001:2015 requires in clause 5.3 that top management assigns, communicates and ensures understanding of responsibilities and authorities for relevant roles, and in clause 7.2 that the necessary competence is determined. The standard does not prescribe job descriptions, but they are a common way to demonstrate both.
For the organization as a whole, the job descriptions together form the level of detail beneath the org chart: the org chart shows the boxes and lines, the job description what is inside a box.
The contents of a job description
The literature has long catalogs of twenty fields and more. In practice, seven building blocks carry almost everything, plus a header with administrative details.
1. Job title. The name of the position, gender-neutral and exactly as it appears in the org chart: "Purchasing Administrator", not "Mrs. Krause's buying job". Plus department, cost center if you use them, and the reporting line: who does the position report to, and which positions report to it?
2. Job purpose. Two or three sentences on why the position exists. It is the section most often left out and at the same time one of the most helpful, because it orders tasks that look equally important in a list. "Ensures production is supplied with material on time and at market terms" says more than ten bullet points.
3. Tasks. The main activities, five to ten of them, each phrased with a verb and with an approximate share of working time. The time share takes some thought and is revealing: if the shares add up to 160 percent, something is off. The list usually closes with "Other duties as assigned by the line manager within the scope of the qualification".
4. Authorities. What the position may decide, sign or approve on its own, each with limits: orders up to which amount, signing authority, authority to instruct other positions, access to which systems. Clear limits here save a lot of questions in everyday work.
5. Deputy. Two directions: who covers for this position, and whom does it cover for? Besides the name, what counts is whether the deputy can actually carry out the tasks. How to set up cover so it really works during holidays is covered in the guide vacation cover plan.
6. Requirements. The person specification: professional qualification (vocational training, degree), work experience, skills (systems, languages, standards), personal competencies. Separate "essential" from "desirable" so the profile stays realistic and applicants can recognize themselves in it. Whether your team covers these requirements today is shown by a skills matrix, which records for each person which tasks they master at which level.
7. Interfaces. Which positions, departments and external partners does the position work with regularly, and about what? "Production: requirement notices, date changes" is useful, "all departments" says too little.
The header also carries the date, version number, who drew up the job description and who approved it. With a date, anyone can see later how current the document is.
Job description template to copy
The following template contains all seven building blocks. Copy it into Word or your intranet and replace the placeholders in square brackets. The guiding questions in the right-hand column help you fill it in and can be dropped from the finished document.
| Building block | Content | Guiding question |
|---|---|---|
| Job title | [name of the position, gender-neutral] | What is the position called in the org chart? |
| Department / area | [department] | Where does the position sit in the organization? |
| Reports to | [title of the supervising position] | Who gives professional and disciplinary instructions? |
| Direct reports | [none / position titles] | Who reports to this position? |
| Job purpose | [two to three sentences] | What would be missing if the position didn't exist? |
| Tasks | 1. [activity with a verb] - approx. [x] % 2. [activity with a verb] - approx. [x] % 3. [...] Other duties as assigned within the scope of the qualification |
What does the position do in a normal week, month, year? |
| Authorities | [decisions, approvals, signatures, each with a limit] | What may the position decide without asking - up to what limit? |
| Deputy | Covered by: [position] Covers for: [position] |
Can the deputy actually carry out the main tasks? |
| Requirements | Essential: [training, experience, skills] Desirable: [...] |
What must someone bring on day one, and what can be learned on the job? |
| Interfaces | Internal: [position - subject] External: [partner - subject] |
Who does the position coordinate with regularly, and about what? |
| Status | Version [x], [date], drawn up by [name], approved by [name] | When was the description last checked against practice? |
Three tips for filling it in. First: phrase tasks as an activity with an outcome. "Requests quotes for new parts and prepares the award decision" says far more than the keyword "purchasing". Second: give every authority a limit. "May place orders" leaves open up to what amount, and in case of doubt every order ends up being checked. Third: fill in the template together with the person who holds the position today. The example shows why that helps so much.
Example: job description for a purchasing administrator in a metalworking company
A typified example: it summarizes tasks and structures as they commonly occur in companies of this size. Names and details are invented.
A metalworking company in Franconia, 95 employees, steel and sheet-metal structures made as one-offs and small batches. Purchasing consists of the head of purchasing and two administrators. Mrs. Krause, one of the two, retires in six months. As part of its succession planning, management wants to advertise the position in good time and pulls the job description out of the personnel file for that.
This is what it looks like after revision:
| Building block | Content |
|---|---|
| Job title | Purchasing Administrator (m/f/d) |
| Department / area | Purchasing, commercial administration |
| Reports to | Head of Purchasing |
| Direct reports | none |
| Job purpose | Ensures production is supplied with raw material, bought-in parts and consumables on time and at market terms, and keeps supplier master data up to date. |
| Tasks | 1. Orders raw material (sheet, sections) and standard parts based on requirement notices from the ERP - approx. 40 % 2. Requests quotes for new parts and special inquiries and prepares the award - approx. 20 % 3. Monitors delivery dates, chases overdue deliveries and reports delays to production planning - approx. 20 % 4. Resolves price and quantity discrepancies in invoice checking with accounting - approx. 10 % 5. Maintains supplier master data and framework agreements in the ERP - approx. 10 % Other duties as assigned within the scope of the qualification |
| Authorities | Orders from approved requirements up to 10,000 euros net per order; above that, approval by the head of purchasing. Call-offs from framework agreements without an amount limit. No authority to create new suppliers without approval. |
| Deputy | Covered by: second purchasing administrator position Covers for: second purchasing administrator position |
| Requirements | Essential: commercial vocational training (e.g. industrial clerk), at least two years' experience in purchasing or materials planning, confident use of an ERP system Desirable: basic knowledge of materials (steel grades, sheet thicknesses), English for supplier correspondence |
| Interfaces | Internal: production planning (requirements, dates), production (urgent requirements), goods receipt (quantity and quality discrepancies), accounting (invoice checking) External: steel stockholders, standard-parts suppliers, freight forwarders |
| Status | Version 3, September 2026, drawn up by the head of purchasing, approved by management |
This is a decent job description, with a clear purpose, tasks with time shares, authorities with a limit and cover arranged in both directions. The questions Mrs. Krause's successor will ask in her second week are still open, though.
Tasks and the workflows behind them
Take task 1: "Orders raw material based on requirement notices from the ERP". This one sentence stands for 40 percent of the working time, and a lot of experience sits behind it. For example, that steel stockholder A delivers 3-millimeter sheet cheaper, but only if you order by Tuesday noon. That the requirement notices for one particular assembly are systematically too low in the ERP because the offcut waste is not included, which is why Mrs. Krause has been adding ten percent for years. And that urgent requirements from production are called over by the foreman and still have to be entered in the system afterwards, or invoice checking won't reconcile.
None of that belongs in a job description, and rightly so. A job description containing every step would be thirty pages long and would need constant updating. This knowledge needs a place of its own. In many companies the job description names the tasks, and the workflows behind them are known mainly to the person who has done them for years, here Mrs. Krause. The guide on knowledge silos describes how common that is in organizations that have grown over time.
A second point doesn't show in the example, because it has already been revised: the job description often deviates from reality at the level of the tasks themselves. Mrs. Krause maintains the price list for cost estimating on the side, because she knows the current steel prices anyway. She is the only one who can fill in the customs papers for the one supplier from Switzerland. Neither appears in any version of the job description, and both usually become visible only when Mrs. Krause is away.
That is why you check the job description against practice, and the question you ask makes the difference. Ask Mrs. Krause "Is the job description still accurate?" and she will probably nod, because the extra tasks are so self-evident to her that she no longer perceives them as her own tasks. That is tacit knowledge in its purest form. You learn more with the questions you use for as-is process mapping: "What did you actually do last week? Who asked you something? What would have been left undone if you had been off sick?" The answers produce two things: a corrected task list for the job description, and the material for the process descriptions it should point to.
This division of labor gives you usable role documentation:
| Document | Answers | Example from purchasing |
|---|---|---|
| Org chart | Where does the position sit, who reports to whom? | Purchasing administrator reports to head of purchasing |
| Job description | Which tasks, authorities and requirements does the position have? | Orders raw material, up to 10,000 euros without approval |
| Process description | How does a workflow run across several positions? | From the requirement in the ERP to the checked invoice |
| Work instruction | How exactly is a single activity carried out? | Entering an urgent production requirement in the ERP afterwards |
If the job description points to the relevant process description for every main task, a personnel-file document becomes an entry point into the knowledge of the role. With those pointers, the successor gets to know the workflows in an orderly way and can look things up when a special case comes up for the first time.
This is where wissa.ai comes in, following the principle of AI process documentation: an AI interviews employees by chat, around 15 to 20 minutes per conversation, and asks about concrete cases: "What did you do on the last rush order, and when did it go differently?" If Mrs. Krause names the production foreman as the one who reports urgent requirements, wissa.ai suggests inviting him next. The conversations produce the process documentation with a source for every statement, which also records who actually handles which tasks, such as the price list maintenance once it comes up in conversation, and an org chart with the roles as they are actually distributed. That gives you both at hand: the material to check the job description against reality, and the workflows it can point to. If two people describe the same responsibility differently, wissa flags the contradiction so you can clarify it together. Try one interview for free
Step by step: writing a job description
Step 1: Clarify the occasion and scope. A job description for recruiting mainly needs purpose, tasks and requirements. One for the QM manual needs authorities and cover spelled out in full. Decide what the document is for.
Step 2: Interview the person in the role. Ask: "What have you done over the past two weeks?" Have them walk you through concrete cases and note the tasks that come up, especially the ones missing from the old version.
Step 3: Ask the manager and the interfaces. The manager adds what the position should deliver. The interfaces, that is production, accounting and goods receipt, add what they actually get from it. Where the three views differ, you find the most revealing clues.
Step 4: Fill in the template. Purpose first, then tasks with time shares, then authorities with limits. Check the sum of the time shares, and check in the deputy section whether the named position can really carry out the main tasks.
Step 5: Point to the workflows. For every main task, note where the corresponding workflow is documented. If documentation is missing, take it along as an action item, especially for tasks only one person has mastered. A bus factor of 1 can't be fixed in a job description, but it can be made visible.
Step 6: Approve and set a review date. Manager and position holder sign off together. Add a date for the next review, no later than one year out.
Keeping the job description current
A new task usually just gets done, and the job description stays as it is. Three occasions therefore work well as fixed review points: the annual appraisal, every reorganization or system change, and every change of holder. The change of holder is when the review is most valuable, and it pays twice: before the departure, with the outgoing person who still knows everything they do (the guide knowledge transfer when employees leave shows how to use the notice period for it), and after onboarding, with the new person who still remembers what was missing. The organizational side of the change is covered by the onboarding checklist.
wissa.ai is happy to take on finding out what actually happens in a role: the AI interviews your colleagues whenever it suits them and creates process documentation and an org chart from the conversations, with hosting in Germany, AI processing in the EU and a data processing agreement. A free trial package to start with (10 credits, once per company, terms) usually covers a first interview, and you can sign up right away. Try one interview for free
Conclusion
A good job description fits on two pages: job title and reporting line, a purpose in two sentences, five to ten tasks with time shares, authorities with limits, a deputy who can really do the work, an honest person specification and the interfaces. The template above gives you the skeleton. The job description comes to life through two things you add together with your team: a task list checked with the person in the role, and pointers to the documented workflows behind every task. That makes it a good starting point for understanding a role, for succession, for cover and for anyone who wants to know who is responsible for what.
FAQ
What goes into a job description?
Seven building blocks carry almost everything: job title with reporting line (department, supervisor), job purpose, tasks with an approximate time share, authorities with limits, deputy, requirements (essential and desirable kept separate) and interfaces. Plus a header with date, version and approval. How the individual tasks are carried out is described in process descriptions and work instructions the job description points to.
Is a job description mandatory?
A detailed job description is not required by law. In Germany, however, section 2 of the Evidence Act (Nachweisgesetz) requires employers to provide a statement of the essential terms of employment, including a brief characterization or description of the work to be performed. This can be done in writing or, since 2025 and under certain conditions, in text form such as email. Companies certified to ISO 9001 must also assign responsibilities and authorities and determine the necessary competence (clauses 5.3 and 7.2), and job descriptions are a common way to demonstrate this.
Should the job description be part of the employment contract?
Usually better not. Under German law, section 106 of the Trade Regulation Act (Gewerbeordnung) lets the employer specify the content, place and time of work in more detail, as far as the contract does not fix them. If a detailed job description becomes part of the contract, it narrows this right to give instructions, and any later change to the tasks may then require a contract amendment. That is why a brief description of the work in the contract plus the detailed job description as a separate document is common practice. In individual cases, an employment law review is worthwhile.
What is the difference between a job description and a job ad?
The job description is an internal organizational document: complete, matter-of-fact, with authorities, cover and interfaces. The job ad is promotional copy for applicants, shortened to tasks, requirements and what the company offers. A good job ad is built from a current job description and then shows applicants the role as it is today.
How often should a job description be updated?
At least once a year, conveniently during the annual appraisal, and additionally with every reorganization, system change and change of holder. The update works best when it happens with the person in the role and asks about concrete cases.
Does the works council have to be involved in job descriptions?
In Germany, drawing up job descriptions is, according to the prevailing view, not subject to co-determination. The works council does have to be informed as part of personnel planning (section 92 of the Works Constitution Act, BetrVG), and if job descriptions become the basis for appraisal principles or selection guidelines, the co-determination rights under sections 94 and 95 BetrVG can apply. Either way, it is advisable to involve the works council early.
Sources
- German Evidence Act (Nachweisgesetz, NachwG), section 2(1) - statement of the essential terms of employment (in writing, since 1 January 2025 under conditions also in text form), including a brief characterization or description of the work
- German Trade Regulation Act (Gewerbeordnung, GewO), section 106 - the employer's right to give instructions
- German Works Constitution Act (Betriebsverfassungsgesetz, BetrVG), sections 92, 94, 95 - personnel planning, appraisal principles, selection guidelines
- ISO 9001:2015, clause 5.3 "Organizational roles, responsibilities and authorities" and clause 7.2 "Competence"
- Michael Polanyi: The Tacit Dimension, Garden City (NY) 1966 - "we can know more than we can tell": why extra tasks go missing when the job description is checked