Org chart guide · Part 1

How to build an org chart that stays accurate

Start from the people list, not from the drawing. Six fields, seven steps and three errors to catch before anyone sees the chart.

Updated 31 October 2026 · By the EcosAgile HR experts

Get a DemoAll guide parts
People listIDNameManagerE-104AnaE-101E-101MarcoE-100E-118LeaE-101E-120JonE-104MarcoAnaLeaJon

Start from the data, not from the drawing

Most org charts fail the same way. Someone draws one, it looks right for a month, then a team moves and nobody opens the file again. The fix is to treat the chart as the output of a list of people and reporting lines, and to draw it last.

The minimum data you need

Six fields are enough for a first chart. Everything else can wait.

FieldWhat it doesCommon trap
Unique IDLinks each record to the HR system.Using names or emails as IDs. They change; IDs should not.
NameShows who the box is.Two people with the same name and no way to tell them apart.
Job titleSays what the person does.Five spellings of the same title.
Manager IDBuilds the reporting line.A manager who has left, still listed as someone’s boss.
Unit or departmentGroups boxes into teams.Free-text unit names with typos.
LocationLets you filter by site or country.Mixing city and country in one column.

Seven steps, in order

  1. Decide the question. Who reports to whom? Who sits where? What does each unit cost? The question decides which fields you need.
  2. Export from the source of truth. Take the list from the HR system, not from last year’s slide.
  3. Clean IDs and titles. One ID per person, one spelling per title.
  4. Check the reporting lines. Look for the three errors below before you draw anything.
  5. Choose one top. The chart needs a single starting point, even if it is a board or a managing director.
  6. Let a few managers review it. Five people who know their teams find more mistakes than any script.
  7. Name an owner and a rhythm. Decide who updates it, and what event triggers an update: a hire, an exit, a transfer.

Three data errors that break a chart

These show up in almost every first import. Find them before your colleagues do.

Orphan recordAnaLeaJonmanager ID E-999not in the listReporting loopAnaMarcoAna reports to Marco,Marco reports to AnaSeveral topsCEOHead of OpsTeamTeamtwo records with no manager:one is probably a mistake
Figure 1. The three errors to look for in the reporting lines.
  • Orphan. A person whose manager ID does not exist in the list, because the manager left or the ID has a typo.
  • Loop. Two people who report to each other, directly or through a chain.
  • Several tops. More than one record with no manager. Unless you really have several top positions, one of them is a mistake.

Who keeps it current

A chart stays accurate when updating it is nobody’s extra job. Name one owner, usually in HR operations, and give them a trigger rather than a calendar: every hire, exit and transfer in the HR system should reach the chart without retyping. If it cannot, the process is the problem, not the person.

How this looks in OrgChart Agile

  • You can load the list from a CSV file or an Excel template, or connect your HR data (see Up-to-date org chart).
  • After a load, a badge on the chart shows how many people are not attached to the hierarchy because their manager is not in the data. Open the list and fix the reporting line.
  • Duplicate IDs found during an import are listed in the import log.

This week

  • Export your people list and count the records with no manager ID.
  • Check that every manager ID appears as an ID in the same list.
  • Write down who owns the chart and what triggers an update.

Questions people ask

Can I build an org chart in Excel?

Yes, to start. Keep the list as the master and draw from it. The problems begin when the drawing and the list drift apart, which is why the list should feed the drawing automatically.

What is the difference between a position and a person?

A position is a box in the structure; a person occupies it. When a position is vacant the box stays and the person is missing. Keeping the two apart makes vacancies visible.

How many levels should the chart show?

Show as many as the question needs. A chart for managers can stop two levels below the top; the full chart should still exist so that nobody has to guess where a team sits.

See it on your own people list

Request a free trial and load a file to see where the data needs attention.

Request a free trial