Organisation chart template for Word (free download)

Organisation chart template for Word (free download)

An organisation chart is not wall decoration: it is the quickest way to answer a question that comes up every day in any company, "who decides this". When the answer is not written down, every area invents its own version, approvals get duplicated and tasks end up falling between two chairs. This organisation chart template for Word solves that with a functional format by levels: five shaded blocks that represent the structure, a detail table position by position and a summary of headcount per area.

The file is meant for small and medium businesses that do not yet run a personnel management system and need to put in writing, on one printable sheet, who reports to whom. You download it, replace the company name in the footer and the document code in the control table, and fill it in with your real positions. There is no need to know how to draw or to handle diagramming tools: the blocks already come shaded and the tables already carry their headings.

One useful warning before you continue. This blog already covers the functions manual and the job description, and it is very common for all three templates to end up holding the same copied text. They are not the same thing: the organisation chart answers who reports to whom, the functions manual explains how a whole area works and the job description details one specific post. Later in this article we will look at the difference with examples, because using all three documents without distinguishing them is the surest way to make none of them useful.

What this organisation chart is and what it is for

The template is a Word document that you fill in by hand or on a computer and then sign. Its core is the structure by levels: level 0 is the decision-making body, which may be the partners' meeting or the owner; level 1 is general management; level 2 groups the functional directors; level 3 brings together coordination and supervisory roles; and level 4 holds the operational posts. Each level occupies a shaded block, so the hierarchy is visible at a glance and needs no extra explanation.

Underneath the blocks sits a detail table that answers the fine-grained questions: position by position, who it reports to, which positions depend on it and how many people it is responsible for. That table is what prevents arguments, because the exceptions are written down instead of living in somebody's memory: the coordinator who also covers a second site, the position shared between two departments, the vacancy filled only for part of the year.

Keep one limit in mind. An organisation chart is not a decorative diagram. If the blocks do not match reality, the document becomes a source of conflict instead of a working tool. That is why the format includes a version number, a date, a validity period and the signatures of whoever prepares it and whoever approves it: what is written governs, and whatever changes shows up in the next version. That discipline is what keeps the document useful six months after it was signed.

What it is used for in practice

• Knowing who a new position reports to before you publish the vacancy, so you avoid giving one person two managers.
• Settling quickly who approves an expense, a purchase or a stock issue, without walking half the building asking.
• Structuring induction for a new hire: on a single sheet they see where their post fits and who they need to talk to each week.
• Spotting duplication before it costs money, such as two positions doing the same work in different areas or a process with no clear owner.
• Holding growth conversations with evidence: if the coordination layer grew, it shows on paper and not in each manager's impression.
• Handing over an orderly record when a client, a bank or an auditor asks how the company is organised.
• Agreeing who is contacted first when something urgent happens and there is no time to climb the whole chain.

What the template includes

The file brings seven sections with their headings already built. This table summarises what goes in each one.

How to use it, step by step

1. Download the file and save it under the name of the version that will govern, not as a working copy. Record that version and its date in the control table.
2. Replace the company name in the footer and change the document code in the control table to the one your company uses, keeping the shape of the original code.
3. Complete the general details: legal name, approval date, version, validity period, who prepares it and who approves it.
4. Write the positions inside each level block, using the post title and not a person's name. Personal names belong in the detail table, never in the blocks.
5. Fill the detail table row by row: level, area or process, position, who it reports to, positions that depend on it and people under its responsibility. This is the step that takes longest and prevents the most arguments.
6. Complete the headcount per area and the type of contract, and reconcile the total against the payroll for the month before signing.
7. Write the real exceptions in the notes: shared positions, people covering several sites, vacancies and roles filled by season.
8. Sign it with whoever prepares it and whoever approves it, file the document in the area folder and leave a copy for each party. Update it every time a position or a reporting line changes, bumping the version.

Chart, functions manual and job description are not the same thing

All three documents talk about work, but they answer different questions. Confusing them is the error that wastes the most time, because it forces you to keep three files holding repeated information, and all three go out of date at the same moment.

The test is simple. If the chart starts filling up with paragraphs about how a task is performed, that text belongs in the functions manual. If it starts filling up with study or experience requirements, that text belongs in the job description. And if a sentence works equally well for two different positions, it has no place in the chart: the chart names the post, not the task.

The practical order of work is this: the chart first, because it fixes the structure and the levels; then the manuals for the areas that genuinely need them; finally the descriptions of each position. Done the other way round, you end up writing the profile of a post that does not yet exist in the structure, and when somebody reviews it they discover there is nobody for it to report to.

Common mistakes

• Putting people's names in the blocks. The chart is about positions; names change and the document should not change with every resignation.
• Leaving out the two extreme levels: the decision-making body at the top and the operational posts at the bottom. Without them the structure is half-built and never explains how the work actually gets done.
• Not writing down the exceptions. Almost every company has at least one person working for two managers; if that is not in the notes, the detail table is lying.
• Updating the content without bumping the version, so three different charts end up circulating and nobody knows which one governs.
• Turning the chart into a manual: a long document nobody reads and that goes stale within a month.
• Approving it without reconciling headcount against payroll; a chart whose numbers do not add up loses credibility in the very first meeting.
• Printing it without checking the page break. If the blocks split across two sheets, the structure stops being readable at a glance and the document loses its only advantage.

When it is worth moving to a system

A Word chart works while the structure is stable and the number of positions can be reviewed in one sitting. Once the company starts moving people often, opens new sites or runs several warehouses, the document falls short: it says who reports to whom, but not how much each area moved, what left the warehouse under each manager, or what changed since the last version.

At that point it is worth moving it into a system where the structure is connected to the operation. Kardex Tauro is inventory and control software that keeps areas, owners and movements in one place, so the chart stops being a loose file and becomes one more view of the system. Kardex Tauro does not replace the document you sign: it keeps it current and cuts the manual work of reconciling figures every time someone joins or leaves. Start with the Word version, with the structure properly balanced, and make the jump when changes happen faster than you can update the file.

This template is a general guide for internal use: review it with your adviser before adopting it as a company standard, and adjust the levels to the way your team really makes decisions.