Job description, role description and functional chart: a practical guide with template

On one side, the company that prescribes every detail ends up with passive team members who hide behind the phrase "that's not my job." On the other, the company that leaves everything implicit sees the business owner buried in daily micro-decisions: every doubt goes up to the top, every newcomer learns by osmosis, and every departure leaves dozens of orphaned tasks that nobody knew existed.

The job description, or role description, is the document that describes what a single person does in the company: the purpose of the role, responsibilities, performance indicators, decision-making boundaries. It differs from the job posting (a short version used for job ads) and from the functional chart (a map of the functions of the whole company, not of a single role).

In Italy, 99.3% of companies in industry and market services have fewer than 50 employees and 94.9% have fewer than ten (2022 data) [1]: a scale at which informal job descriptions "in people's heads" hold up until roughly 7-15 team members, and then start costing more than they deliver.

This practical guide sets out the difference between job description, role description, job posting and functional chart, shows how to write a role description in practice, points out the legal boundaries to respect, and offers a Word template ready to fill in.

How job descriptions, role descriptions, job postings and functional charts differ

The confusion between job description, role description, job posting and functional chart is not just a matter of vocabulary: it leads to documents that do not answer the right questions. A three-line job posting is not enough for someone already in the company; a ten-page job description confuses an external candidate. Making the distinction helps you choose the right tool for the problem. This section disambiguates the four terms with an operational table and indicates when to produce one or the other.

How many different documents do you really need to describe a role? Often just one is enough, but it has to be the right one: using the job posting in place of the job description is the first organizational mistake many companies make.

The following table summarizes the operational distinctions between the four terms, based on the methodological definitions established in the HR literature [4] and in reference dictionary entries [6]:

scroll the table →

The most important operational difference is between the job description and the job posting: the job description is an extended internal document, complete with KPIs and decision-making boundaries, designed for the person who already holds the role; the job posting is the short version used to communicate the role externally, during recruitment [4]. In many companies the two documents are treated as synonyms, with the result that neither the candidate nor the team member gets the information they need.

The job description also differs from the standard operating procedure (SOP): the job description describes what the role must achieve, while the procedure defines how to carry out a specific activity. In smaller organizations this distinction tends to blur, with job descriptions that include detailed work instructions: a habit that produces hybrid documents, neither strategic enough to guide the role nor operational enough to guide execution. To explore the difference between the two tools, read the guide to standard operating procedures (SOPs).

Finally, the separation between the job description and the organizational chart is conceptual as well as formal: the organizational chart shows where the role sits in the hierarchy [6], while the job description describes what that role produces and how its success is measured. The two documents complement each other (they do not replace each other) and must be kept in sync every time the structure changes. For a guide to building the organizational chart, see the dedicated resource on the organizational chart.

Learn to recognize when you need a formal job description (and when you don't)

Not every company needs a formal job description, and introducing one too early creates rigidity. There is, however, a threshold beyond which not having the document costs more than writing it: the moment when the business owner spends a significant part of the day answering questions like "is this my job or Mario's?" This section gives 4 concrete signals to tell whether your company has crossed that threshold, based on verifiable evidence rather than gut feeling.

At what company size does the job description become indispensable? It is not a question of headcount, but of how many "boundary questions" reach the business owner every day. If you do not measure that number, the need for a job description remains a feeling.

In a company with fewer than 7-10 team members, roles overlap out of necessity and knowledge flows through direct contact. The founder knows every activity, every assignment, every priority. The cost of formalizing roles often exceeds the benefit. As the number of team members grows, however, this balance shifts, and European data show where the jump occurs: in 2023, value added per employee in Italian companies with fewer than ten employees was €38.8 thousand, compared with €42.1 thousand for the EU-27 average, while from the 10-19 employee size class upward the comparison flips in favor of Italian companies, which stay above the European average in every larger size class [2]. Italy's productivity gap is therefore concentrated in the size range where the organization still lives entirely in the head of the person running it.

The 4 signals that a formal job description has become necessary are the following:

1. Decision overload at the top. The business owner receives daily requests for authorization or clarification on tasks that team members should already be able to handle on their own. When these questions pass a threshold that feels like "too many," the problem is not the staff: it is the absence of written decision-making boundaries.

2. Tasks that fall through the cracks. Regular activities are forgotten or done late because nobody knows for sure who they belong to. The most common mistake is discovering this only when something does not get done, not before. In smaller companies, this gets worse at moments of transition: a team member leaving, a change of department, a new team member joining.

3. Onboarding that requires prolonged shadowing. If every newcomer needs 3-6 months of intensive shadowing to understand what is expected of them, the problem is that expectations were never written down. The job description shortens this time by providing a written reference from day one, and its usefulness is directly tied to the employee onboarding process.

4. Performance reviews based on impressions. When, at the time of the annual review, there is no shared reference document on what the role was supposed to deliver, the review meeting becomes a comparison of perceptions rather than a comparison of evidence. The team member is evaluated on criteria they did not know; the business owner evaluates against expectations they never formally communicated.

These four signals do not require sophisticated measurement tools: it is enough to keep an informal log of the questions you receive in a typical week, map the "orphan" tasks during an operational meeting, and look at how the last onboarding was structured. If three of the four signals are present, the formal job description is already overdue.

The 6-step process for writing an effective role description

Most job descriptions fail not for lack of goodwill, but because of a writing method that produces unreadable documents: endless lists of tasks, vague verbs ("supervise," "coordinate"), no KPIs attached. This section proposes a 6-step process, each step with a well-written and a poorly written example, based on established HR literature and adapted to smaller organizations. The Word template at the end of the article follows exactly these 6 steps.

Why do job descriptions written by the business owner alone produce documents the employee does not recognize? Because part of the real tasks of every role stays hidden and only surfaces when you interview the person who has held that role for a while.

The HR literature identifies five canonical elements in the structure of a job description/role description [4]. In the practice of smaller companies, a sixth one is added (relationships and internal communication flows), which the Anglo-American literature tends to overlook but which, in flat organizations where reporting lines are short and communication channels are many, is decisive for operational clarity.

Step 1: role details and reporting line State the role title, the functional area it belongs to, who it reports to directly and (if any) how many people it coordinates. This step seems trivial, but it produces the most important boundary: the reporting line defines who evaluates, who authorizes, and who needs to be consulted when an exception comes up.

Poorly written: "Sales Associate, Sales Area." Well written: "Customer Care Specialist, Sales Area. Reports to the Sales Manager. No direct reports."

Step 2: purpose of the role One or two sentences that describe why the role exists in the company, not what it does in detail. The purpose answers the question: "If this role disappeared tomorrow, what would no longer happen?"

Poorly written: "Handles customer support and ticket management." Well written: "Ensures customer requests are resolved within the agreed response times, contributing to retention and post-sale satisfaction."

Step 3: key responsibilities (5-7 items) A list of the main responsibilities, not the operational activities. The distinction is fundamental: the responsibility is the expected result, the activity is the means. More than 7 main responsibilities almost always signals a problem in how the role is defined, not a problem with the list.

Poorly written: "Answers emails / Manages tickets / Calls customers / Updates the CRM / Writes weekly reports / Handles complaints / Attends team meetings / Supports the manager with extraordinary activities..." Well written:

• Ensures customer requests are answered within the defined SLA times.
• Manages the escalation of critical cases to the Sales Manager.
• Updates the CRM after every interaction, ensuring contacts are traceable.
• Produces the weekly report on service quality metrics.
• Proposes improvements to the ticket management process on a quarterly basis.

Step 4: linked KPIs For each key responsibility, at least one measurable indicator. The next section (H2-4) goes into the checklist for building them. The basic principle is that a valid KPI must be measurable on a regular basis (monthly or quarterly), within the influence of the person in the role, and balanced between quantity and quality.

Step 5: decision-making boundaries The decisions the person in the role can make on their own (without authorization) and those that require approval. This step is the least intuitive to fill in but the one with the greatest operational impact: every "boundary question" eliminated means one less micro-interruption for the top.

Example for the Customer Care Specialist:

• Autonomy: approving refunds up to 100 euros; assigning ticket priority within the defined categories; responding directly to the customer in standard cases.
• Requires authorization: refunds over 100 euros; non-standard communications to the customer; exceptions to SLA times.

Step 6: hard and soft skills + internal relationships A list of the technical (hard) and behavioral (soft) skills required for the role, plus a map of the main internal relationships: who the person works with regularly, who they receive input from, who they deliver output to. This sixth step is especially relevant in smaller companies, where workflows cross different functions in a less formalized way than in large organizations.

The 6-step process should be built with the person in the role, not for them. Interviewing the person who already holds the role (or the manager who will fill it) is the only way to bring out the share of "hidden" tasks that the team's leader does not know in detail but that take up a significant part of the actual time [4].

The checklist for linking every job description to measurable indicators

A job description that describes what the role must do but not how success is measured is an incomplete document. This section proposes a 5-point checklist for linking every responsibility to a measurable indicator, avoiding two opposite mistakes: KPIs that are too generic ("increase sales") and KPIs that are so specific they encourage gaming the system ("answer 50 tickets a day," whatever the quality). The reference is the pillar article on business KPIs.

How many KPIs does each role need? Between 3 and 5: fewer than 3 leaves too many tasks unevaluated; more than 5 creates confusion and fragmented attention.

The Bank of Italy measured structured management practices in about 3,200 Italian companies with at least twenty employees (how many performance indicators are monitored, how targets are designed, what criteria are used for promotions) and found a positive association with productivity, while stating that the analysis is purely descriptive [3]. No Italian survey measures whether a written job description exists, but the operational link is direct: without a role document, the evaluation has no shared reference and comes down to impressions rather than measurement.

The 5-point checklist for building KPIs firmly anchored to the job description:

1. Every key responsibility has at least one KPI. If a responsibility has no associated KPI, it is because nobody knows how to measure it, and that is already a sign that the responsibility was worded too vaguely. The fix is to go back to Step 3 and rewrite the responsibility in terms of the expected result, not the activity performed.

2. The KPI can be measured monthly or quarterly. Annual KPIs come too late to correct course; weekly ones create operational anxiety rather than strategic direction. A monthly or quarterly window is what lets you step in on time without overloading the measurement system.

3. The KPI is within the influence of the person in the role. A KPI that depends on factors outside the control of the person being evaluated (market swings, decisions by other departments, extraordinary events) does not guide behavior: it creates frustration. The influence criterion requires you to ask: "Does this person really have leverage over this number?"

4. The KPI is balanced between quantity and quality. Every quantitative KPI (number of tickets closed, sales volume) should be paired with at least one qualitative indicator (customer satisfaction, complaint rate, quality of output). Without this balance, evaluation systems based on job descriptions tend to reward quantity at the expense of quality.

5. The KPI is shared with the person in the role before it takes effect. This is the step most often skipped: the job description is written "from the top" and handed over without discussion. A team member who receives KPIs without having taken part in defining them rarely sees them as fair, even when they are. Sharing them in advance does not require a formal negotiation: a conversation before the document takes effect is enough.

How to respect labor law and collective agreements without making the job description rigid

The job description is a management tool, not a contractual document, but it directly affects the employment relationship. This section sets out three criteria for writing it consistently with the employment contract and any collective agreement that applies in your company (consistency with the job level, limited enforceability of "other duties," explicit reference to the applicable agreement) without turning it into a straitjacket. Consulting an employment law advisor remains the basic precaution before distributing it internally.

Is it a good idea to include the clause "and any other duties required by management"? It is common, but courts tolerate it only as marginal and temporary: used badly, it exposes the company more than it protects it.

In Italy, the reference legal framework is Article 2103 of the Civil Code, as amended by Legislative Decree 81/2015 (the Jobs Act): it governs the possibility of assigning an employee duties different from those agreed, distinguishing between an equivalent change, a change for the worse (demotion) and a change for the better. National collective labor agreements operate within this legal framework, defining by category and level which duties are compatible and which require a new job classification [5]. Outside Italy, check how your local labor law and any applicable collective agreement handle the same questions.

The three criteria for writing a job description consistent with the applicable collective agreement:

Criterion 1: consistency with the contractual job level. The responsibilities described in the job description must be consistent with the employee's contractual level. If the job description assigns responsibilities typical of a higher level, the team member may request a reclassification. If it assigns responsibilities of a lower level, the company is exposed to the risk of demotion claims. Before finalizing the job description, check that it matches the applicable collective agreement, identifying the relevant level descriptions.

Criterion 2: limited enforceability of "other duties." The catch-all clause ("and any other activity required by management") is very common and not illegal in itself, but in Italy the boundary within which it can be enforced is the one set by Article 2103 of the Civil Code [5]: duties that fall within the employee's job classification. A job description that uses this clause to cover the systematic assignment of different tasks loses its function as a boundary and can lead to disputes, on which you should consult an employment law advisor. The practical solution is to limit the catch-all clause to exceptional cases, always documenting the temporary assignment when it happens.

Criterion 3: explicit reference to the collective agreement. The job description should include an explicit reference to the applicable collective agreement and to the team member's contractual level. This reference is not just good practice: it shows that the document was built with awareness of the legal framework and reduces the risk of disputes over a mismatch between assigned responsibilities and contractual level.

Consulting an employment law advisor before distributing the job description internally remains the basic precaution, especially for companies that apply complex collective agreements or are going through a reorganization. A well-written job description does not replace the individual employment contract: it complements it and makes it clearer in operational terms.

The most common mistakes in writing job descriptions (and how to fix them)

Even job descriptions written with a method can lose effectiveness because of four recurring mistakes. This section lists them in order of how often they occur, with the operational remedy for each: from the "vacuum-sealed" job description written without interviewing the person in the role, to excessive prescriptive detail that turns it into a procedure, to the lack of an annual review date.

How many of the job descriptions filed away in an average company still describe roles that actually exist? Often fewer than you think, and the gap between the document and reality grows month by month if there is no review mechanism.

scroll the table →

The fourth mistake is structurally the most dangerous because it tends to become invisible: the job description exists, it was written carefully, it is shown to new hires, but it describes a company that no longer exists. The solution is not to write job descriptions "for life," but to design the moment and mechanism of review from the start.

Limitations and conditions

This practical guide describes a systematic approach to writing job descriptions, but some conditions limit how directly it can be applied.

Variability of collective agreements. Employment law constraints vary significantly between collective agreements (and between countries): the guidance in section H2-5 is general and indicative, not a substitute for specific advice on the agreement that applies in your company. Involve an employment law advisor before distributing any job description internally.

Minimum size. The 6-step process is designed for companies with at least 5-7 team members. For professional practices and micro-businesses with 1-3 team members, a simplified version (purpose of the role + 3-5 responsibilities + 2-3 KPIs) is often enough and easier to keep up to date.

High-variability sectors. In highly uncertain environments (startups pivoting, companies in restructuring, strong seasonality), the job description risks becoming obsolete sooner than expected. In these contexts, short job descriptions reviewed every 6 months are preferable to complete documents reviewed annually.

Correlation, not causation. The data cited describe the size structure of Italian companies (ISTAT [1]), value added per employee by size class (Eurostat [2]) and the spread of structured management practices (Bank of Italy [3]): none of the three surveys measures whether a written job description exists, and the Bank of Italy states that its analysis is purely descriptive. Adopting a job description is a necessary but not sufficient condition for improving company productivity.

Frequently asked questions

Does a job description have legal value? The job description is a management tool, not a contractual document. It does not replace the individual employment contract or the collective agreement. However, it can be used as evidence in disputes over the content of the employment relationship, which is why it is important that it be consistent with the team member's contractual classification.

Does every employee need a job description? There is no general legal obligation, but it is good practice for every role with defined responsibilities. For team members on very short or seasonal contracts, a simplified version is enough.

How often should it be updated? An annual review is the minimum recommended cadence. Bring it forward in the event of reorganizations, promotions, a change of collective agreement, or the introduction of new processes that change the role's responsibilities.

Can the job description be used in performance reviews? That is exactly one of its main uses: providing a shared, written reference on which to base the evaluation. For it to work, the KPIs in the job description must have been shared with the team member before the start of the period being evaluated.

Operational summary

The job description, or role description, is the internal document that describes the purpose, responsibilities, KPIs and decision-making boundaries of a single role. It differs from the job posting (the short version for job ads), from the functional chart (a map of all the company's functions) and from the organizational chart (a visual representation of the hierarchy). In a business landscape like Italy's, where 99.3% of companies have fewer than 50 employees [1], it becomes necessary when four signals appear: decision overload at the top, tasks falling through the cracks, prolonged onboarding, evaluations based on impressions.

The writing process has 6 steps (role details and reporting line / purpose of the role / 5-7 key responsibilities / linked KPIs / decision-making boundaries / skills and relationships), to be built with the person in the role, not without them. KPIs must be checked against five criteria: one for every responsibility, measurable monthly or quarterly, within the role's influence, balanced between quantity and quality, shared in advance. Labor law and collective agreement constraints require consistency with the job level, marginal use of the catch-all clause and an explicit reference to the collective agreement. The four mistakes to avoid: writing without an interview, excessive prescriptive detail, lack of co-creation, no review date.

Conclusion

The principle running through this guide is that the job description is neither a legal document nor an administrative label: it is a living tool that translates organizational strategy into operational boundaries visible to the person in the role, to the person who coordinates it and to whoever will one day replace them. It differs from the functional chart in scale (a single role, not the whole company), from the job posting in length and from the organizational chart in content. When it is written following the 6 steps described, linked to measurable indicators and reviewed every year, the job description produces an organization in which tasks stop "falling through the cracks" and team members stop asking the top for unnecessary permission.

Once roles are defined, the next step is to design the overall structure: the guide to the organizational chart shows how to fit job descriptions into a coherent map, while the pillar article on business organization lays out the big picture. If you want to go deeper into how to then hand operational decisions over to the people in each role, also read the guide to effective delegation in your team.

When every role has its job description, the employee knows what they are evaluated on, the business owner stops being the decision-making bottleneck, the incoming candidate signs a clear agreement, and the company becomes truly scalable. Taking a wider view: in 2023, value added per employee in Italian companies was €63.2 thousand compared with €74.5 thousand in German companies, and the gap is concentrated in the smallest companies, because from twenty employees upward Italian companies outperform German ones in every size class [2]. Part of that distance comes down to role clarity within companies, and a well-made role description is one of the operational tools that narrow it, one role at a time.

Sources and references

[1] ISTAT, Annuario statistico italiano 2025 — Capitolo 14: Imprese, Table 14.2 (percentage breakdown by employee size class, 2022 data). URL: https://www.istat.it/storage/ASI/2025/capitoli/C14.pdf

[2] Eurostat, Enterprise statistics by size class and NACE Rev. 2 activity (from 2021 onwards) — dataset sbs_sc_ovw, indicator Apparent labour productivity (gross value added per person employed, thousands of euros), industry, construction and market services (NACE B-S excluding O and S94), year 2023. URL: https://ec.europa.eu/eurostat/databrowser/view/sbs_sc_ovw/default/table

[3] Baltrunaite A., Formai S., Linarello A., Mocetti S., Ownership, governance, management and firm performance: evidence from Italian firms, Banca d'Italia, Questioni di Economia e Finanza no. 678, March 2022 — section on structured management practices (MOPS) from the 2019 wave of the Invind survey, about 3,200 manufacturing and service companies with at least 20 employees. URL: https://www.bancaditalia.it/pubblicazioni/qef/2022-0678/QEF_678_22.pdf

[4] Bratton J., Gold J., Human Resource Management: Theory and Practice, 7th ed., Bloomsbury, 2022 — chapters "Job Analysis" and "Job Description Design".

[5] Codice civile, art. 2103 (Prestazione del lavoro), as replaced by art. 3 of D.Lgs. 15 giugno 2015, n. 81, Disciplina organica dei contratti di lavoro e revisione della normativa in tema di mansioni, GU Serie Generale n. 144 del 24 giugno 2015, S.O. n. 34. URL: https://www.gazzettaufficiale.it/eli/id/2015/06/24/15G00095/sg

[6] Treccani, entry organigramma («grafico rappresentante l'articolazione gerarchica e funzionale dei varî organi di un ufficio, servizio o amministrazione») and entry mansióne, sense 3 («ufficio, compito esplicato nell'adempimento di una prestazione di lavoro»), Vocabolario on line, Istituto della Enciclopedia Italiana. URL: https://www.treccani.it/vocabolario/organigramma/ — https://www.treccani.it/vocabolario/mansione/

{
  "tipo": "immagine-interna",
  "posizione": "dopo H2-1 (tabella disambiguazione)",
  "descrizione": "Infografica comparativa a quattro colonne che mostra le differenze operative tra mansionario, job description, funzionigramma e organigramma. Ogni colonna riporta: scala di applicazione (singolo ruolo / intera azienda), destinatario principale, contenuto tipico. Stile: minimal, palette navy #090A3A e coral #FF5137, font Montserrat. Sfondo bianco. Dimensione: 1200x630px.",
  "alt": "Tabella comparativa mansionario job description funzionigramma organigramma",
  "formato": "PNG",
  "priorità": "alta"
}

{
  "tipo": "immagine-interna",
  "posizione": "dopo H2-3 (processo 6 passi)",
  "descrizione": "Diagramma a flusso verticale in 6 step del processo di redazione della role description. Ogni box numerato (1-6) contiene il nome del passo e una riga descrittiva sintetica. I box sono collegati da frecce verso il basso. Stile: minimal, palette navy e coral, font Montserrat. Evidenziare visivamente che il Passo 6 (relazioni interne) è l'elemento aggiuntivo rispetto alla struttura standard. Dimensione: 800x1200px.",
  "alt": "Processo in 6 passi per scrivere una role description efficace",
  "formato": "PNG",
  "priorità": "alta"
}

Redazione Prodability — blog.prodability.com Article produced following the 5-step editorial workflow (Step 3 — Body). Guidelines applied: v1.4.