Organisational Chart: What It Is, the Types, How to Build One and How to Generate It From Your Team Data (2026 Guide)

Short answer: an organisational chart (org chart) is a diagram of how a company is structured: who reports to whom, which departments exist and who leads them. The most common type is the hierarchical chart, a tree with the top role at the top; functional, divisional, matrix, flat and circular charts answer different needs. The best way to build one in a small company is not to draw it at all, but to generate it from the people data you already keep: names, roles, departments and reporting lines. Bueggio HR does exactly that, in four layouts, with downloads and a shareable link.

Somebody new joins on a Monday. By Tuesday they have a laptop, an email address and a list of names they cannot place: who signs off their expenses, who runs the team next to theirs, whom to ask when the manager is away. An org chart answers all of that in one glance, which is why it is the single most useful document in onboarding and one of the most neglected: drawn once in a slide, printed for an audit, then left to rot. This guide explains what an org chart is, what belongs on it, the types that exist, how to build one in seven steps, what the law says in the UK and the US, and how the new org chart inside Bueggio HR removes the drawing entirely.

What an organisational chart is

An organisational chart is a visual map of a company's structure. In its simplest form it is a tree: one box per person or role, a line between each person and their manager, and a grouping by department. Read from the top, it tells you how authority flows; read from a single box, it tells you who that person depends on and who depends on them. It is sometimes called an organogram or organigram, especially in Europe, and a staff hierarchy chart in older HR material.

Three things an org chart is not. It is not a directory, although a good one links to contact details. It is not a job description: it shows where a role sits, not what it does. And it is not the informal network of who actually talks to whom; that network matters, but no diagram captures it, and pretending the chart does is how companies fool themselves about how work gets done.

One distinction matters more than it seems in a leave-management context: the reporting line (who is your manager) and the approval line (who signs off your holiday) are usually the same person but not always. A department may have a dedicated approver while its people report to several team leads, or an assistant may approve the leave of a whole floor. A chart drawn from the approval data alone will therefore be slightly wrong, which is why Bueggio HR keeps the two as separate fields and uses the approver only as a first draft for the reporting line.

What to include, and what to leave off

The useful minimum per box: full name, job title, department and the reporting line. Add a photo and the chart becomes a face book for new hires, which is where most of its value for onboarding comes from. Add a contact button (email, Teams, Slack) and it becomes a working tool rather than a poster. Beyond that, restraint pays:

• Leave off salaries, grades, start dates, birthdays, home phone numbers and anything else that is not needed to understand the structure. Under UK GDPR the principle is data minimisation (Article 5(1)(c)): collect and show what the purpose requires, no more.
• Photos are personal data. Using the profile photo a person uploaded for an internal chart is reasonable; publishing it on a public web page is a different purpose and deserves a sentence in your staff privacy notice and, in practice, a heads-up to the team. Give people without a photo a generated face rather than an empty circle.
• Decide who sees what. An internal chart can show mobile numbers; a chart shared with a client or printed for a trade fair should not. The easiest way to get this right is a tool that lets you choose a different set of contact buttons for the internal view and the public link.
• Vacancies are optional. Large companies draw open positions as dashed boxes; in a company of forty people this creates more questions than it answers. Draw the people you have.

Why it matters, with data

An org chart is not a vanity document; it is a tool for the three moments when structure decides whether work flows or stalls. Onboarding: a new hire who can place every name in the first week asks better questions and escalates to the right person. Communication: when a request lands in the wrong inbox three times, the cost is not the minutes but the trust lost each time. Growth: at twenty people everyone knows everyone; at forty, the founders are surprised to discover that two teams have been doing the same work for a month. Drawing the chart is often the moment that surprise surfaces.

The wider context is sobering. In Gallup's State of the Global Workplace 2026 report (2025 data), 20% of employees worldwide are engaged at work; the figure is 10% in the UK and 31% in the US. Clarity of role and of expectations is one of Gallup's twelve engagement elements, and it is the one an org chart serves most directly: knowing where you sit, who decides and whom to ask. No diagram fixes engagement on its own, but an outdated or missing one makes every other effort harder.

The types of organisational chart

Most guides, including Personio's glossary entry, settle on four main types; in practice small companies use the first and the fourth, and the others appear as the company grows. The table adds the layouts that work well on a screen rather than on paper.

A practical rule: pick the type by the question the reader will ask. "Who is my manager's manager?" wants a hierarchy. "Who works in Kitchen?" wants the departmental view. "Who is in charge here?" on a wall or a slide wants flat or circular. The same company can legitimately keep more than one chart, which is cheap when they are generated from the same data and expensive when each is a file.

How to build an org chart in seven steps

1. Decide what it is for and who will see it

Onboarding, an audit, a client deck, the intranet: each wants a different scope and a different level of detail. Write it down in one line; it decides steps 2 and 6.

2. Collect the data, and fix it at the source

Names, job titles, departments and reporting lines. Half the job titles will be missing or out of date, and the chart is the moment you find out. Fix them where the data lives (the HR record, the leave tool), not in the drawing, or you will fix them again next quarter.

3. Choose the type

Hierarchical by default; departmental if the question is "who is where"; flat under thirty people. If you cannot choose, generate two and ask a new hire which one helped.

4. Draw it, or better, generate it

A slide or a diagramming tool is fine for a one-off; it is the maintenance that kills it. If your people data already lives in a tool that knows departments and managers, let that tool draw the chart. The section on tools below compares the options.

5. Validate with the managers

Send each manager their own branch and ask one question: is this who reports to you? Expect surprises. This is also where you catch the loop (A reports to B, B reports to A) that spreadsheets allow and good tools refuse.

6. Share it in the right place, with the right details

Inside the app for the team, a download for the deck, a public link for the intranet or a partner, each with the contact details that audience should see. Tell people the chart exists and where to find it; the best chart is the one new hires open on day one without being told.

7. Give it an owner and a trigger

Not a date, a trigger: every join, leave and change of manager updates the chart. If the chart is generated, the trigger is already wired; the owner only reviews new reporting lines.

What the law says in the UK and the US

Neither country makes an org chart mandatory for a private employer. The rules that touch it are indirect, and they are about the data on it rather than the diagram.

The tools: draw, diagram or generate

The org chart in Bueggio HR: generated, not drawn

Bueggio HR is a leave tracker, and it stays one. But a leave tracker already knows your people, their departments, who approves whom and, since October 2026, who reports to whom. The org chart feature turns that data into a chart in a few seconds, so the structure your team sees is always the structure you actually have.

• Four layouts: hierarchy (top-down or left to right), by department with the approver on top of each panel, flat, or circular. Pick the whole company, one department or one person's team, and fold deeper levels into a "+N" badge.
• Twenty-four looks, or your own picture: brand looks in the product's palette, the alpine illustrations of this website, or an image you upload, with your logo in the header. Download as PNG, JPEG or SVG at print quality.
• Faces for everyone: profile photos where they exist; for everyone else, a face from the open-source DiceBear collection, rendered inside the app from vendored style files, so no name or photo is sent to any service. Or switch to faces for everyone for one consistent style.
• Fix it where you see it: an admin clicks a card to correct a job title, add a phone number, set the reporting line or upload a photo; the change goes to the person's profile, so every chart and the team page stay in step. A missing job title shows up immediately, which is the fastest data clean-up you will ever run.
• Share with control: every employee finds the chart in the app; admins can publish a public link for new hires, partners or the intranet, choose which contact buttons that link shows (email by default, phone and WhatsApp only if switched on) and revoke it at any time. The page is not indexed by search engines.

What it does not do, on purpose: no vacancy boxes, no scenario planning, no dotted-line matrix. Those belong to org-design tools, and a leave tracker that grew them would stop being simple. The guide Generate and share your org chart walks through every option.

Common mistakes

• Drawing the chart you wish you had. The chart must show current reality; the target structure belongs in a separate, dated document.
• Letting the slide become the source. If the chart is where job titles get corrected, the HR record is wrong within a quarter. Correct the record and regenerate.
• Publishing everything to everyone. Mobile numbers on a public page, photos of people who asked not to be shown, a client seeing the whole company when they needed one team.
• Matrix lines on a chart nobody can read. If every box has two or three lines, the chart has stopped communicating; show the solid line and explain the rest in words.
• No owner. A chart without an owner is a chart from last year.

Frequently asked questions

Is an organisational chart a legal requirement?

Not in the UK or the US: no statute obliges a private company to draw or publish one. It becomes expected in three situations: management-system certifications such as ISO 9001, where clause 5.3 asks you to assign and communicate roles, responsibilities and authorities; security and compliance audits such as SOC 2, where auditors ask for the current chart to understand who approves what; and due diligence in a fundraise or acquisition. What the law does regulate is the personal data on the chart: under UK GDPR and the ICO's employment guidance, photos and contact details are personal data, so publish only what the purpose needs and tell employees where the chart goes.

What is the difference between an org chart and a staff directory?

A directory lists people and how to reach them; an org chart shows how they are connected: who reports to whom, which department each person belongs to and where decisions are escalated. A good tool gives you both at once: the chart for the structure, a click on a card for the contact details. That is also why a chart drawn in a slide goes stale within weeks, while one generated from the same data you already keep for leave and departments is right every time it is opened.

How often should an org chart be updated?

Every time a person joins, leaves or changes manager or department, which in a company of fifty people happens roughly once a month. If the chart is a file, assign an owner and a monthly check at the very least; if it is generated from your people data, it updates itself and the only thing to review is new reporting lines. A chart that is three months old is worse than none: new hires trust it, and it teaches them the wrong structure.

The bottom line

An org chart is a map of who reports to whom, and its value is proportional to how current it is. Choose the type by the question your readers ask, put on it only what that question needs, validate it with the managers, and give it an owner. Then stop drawing it: if your people data already lives in a tool, let the tool draw the chart. In Bueggio HR that takes a click, and the result is downloadable, shareable and right every time someone opens it.