An Org Chart That Matches Reality: Build It From Reporting Lines, Not Job Titles

The chart everyone screenshots and nobody trusts

Ask a growing company for its org chart and you will usually get one of two things: a slide that was accurate the week it was made, or a diagram generated by an HR tool that looks authoritative but quietly guesses. Both get screenshotted into onboarding decks and board packs. Neither can be relied on.

The fix is not a better drawing tool. It is deciding what the chart is drawn from — and making that one field the only source.

Two ways a chart goes wrong

Drawn by hand. A diagram in a slide deck or a whiteboard tool is disconnected from the people records. It is right on the day it is made and starts drifting the next morning: someone changes manager, someone leaves, a team is split. Nobody updates the slide, because nobody owns it.

Inferred from roles. Some systems draw the chart from job titles or permission roles: department heads report to an administrator, administrators report to an executive. It looks tidy, but the lines are invented. If a system hands department heads to administrators "in turn", the third person in a list reports to the first administrator purely because of their position in the list. Anyone reading that chart as a reporting structure is being misled — and the "Reports To" field people carefully filled in is ignored.

One source: the reporting line

Every person record has, or should have, one field that says who they report to. Draw the chart from that field and nothing else:

• Role affects order, not structure. An executive is not automatically at the top. If the CEO reports to a founder or a board, they appear beneath them.
• Anyone who reports to nobody is a top-level person. A chart can legitimately have more than one root — a founder and an independent board member, for example.
• Problems surface instead of vanishing. Three situations break a naive chart: a person whose manager has been deactivated, a person recorded as their own manager, and a reporting loop (A reports to B, B reports to A). A good chart shows each of these at the top level so the record that needs fixing is visible, rather than silently dropping the person.

That last point matters more than it sounds. An org chart that hides broken records looks clean and is wrong. One that shows them is a to-do list for whoever maintains people data.

Keep the chart and the records in agreement

If the chart is drawn from the reporting line, keeping it accurate becomes a data-entry habit rather than a design task:

• Change the manager on the record, not on the chart. The chart should have no data of its own.
• Handle leavers on the same day. When someone leaves, their direct reports need a new manager; otherwise they will float to the top of the chart, which is exactly the signal you want.
• Review the top level occasionally. Anyone at the top who should not be is almost always a missing or broken reporting line.

Exporting without forking

People will always need the chart outside the system: a slide for an all-hands, a page in a handbook, or a redrawn version in Visio or Lucidchart for a reorganization plan. The trap is that every export becomes a new, unmaintained copy.

Two rules keep exports honest:

1. Export from the same field the chart uses. A picture of the chart as drawn, a PDF of the same image, and a spreadsheet of people and their managers should all come from the reporting line, so a download can never disagree with the chart it came from.
2. Export only what the chart shows. A chart shows names, titles, departments and reporting lines. It should not quietly include employee numbers, salaries, or any other HR field just because they happen to be in the database.

Who should be able to download it?

Browsing the chart and downloading it are different things. An export is a roster in a file: it leaves the system, outlives the session, and forwards like any other attachment. Many organizations are happy for everyone to look at the chart, but prefer that only certain people can take a copy away.

That suggests two practices:

• Make download access its own setting, separate from who can view the chart — and make sure somebody who cannot view the chart can never download it.
• Record every download. Who exported the chart, when, and in what format should be answerable from an audit log, so an organization can see where its roster has gone.

A short checklist

• Draw the chart from each person's reporting line and from nothing else.
• Let role decide order at the top, never structure.
• Show orphaned, self-managed and looping records at the top so they get fixed.
• Export from the same source, and export only what the chart shows.
• Set download access separately from viewing, and log every download.

How BookYourPTO handles it

The BookYourPTO org chart is built from the Reports To field and nothing else. People who report to nobody, people whose manager is deactivated, people recorded as their own manager, and people caught in a reporting loop all surface at the top rather than disappearing. Export offers a PNG of the chart as drawn, the same image as a PDF, and a .csv shaped for Visio, for Lucidchart, or unformatted for a spreadsheet — all built from the same field, and carrying only what the chart shows. Who can download is set under Download Access in Company Directory settings, separately from who can browse, and every download in every format is recorded in the audit log.