Org Chart

A drawn chart is a picture of what somebody believed the structure was on the day they made it. A generated chart is a view of live data, rebuilt each time it opens from the manager and position fields in the HR record. The difference appears within weeks. Slide-based charts go stale after the first reorganization, then get copied forward with old names on them, which is how a departed employee turns up in a board pack. Generated charts fail differently: they expose bad data immediately. A person with no manager, a circular reporting loop, or a team appearing under the wrong leader becomes visible the moment the chart renders. That is uncomfortable and useful, because it converts an invisible data problem into something a manager will report the same day.

It makes two structural measures legible without any analysis: how many people report directly to each manager, and how many levels sit between the top of the company and the front line. Wide spans can indicate managers stretched past the point where they can coach anyone. Narrow spans across many levels usually mean slow decisions and expensive coordination. Neither figure has a universally correct value, and sensible ranges differ by function, since a support operation and a research team are not comparable. What the chart does well is prompt the right question. A manager with a very small team invites a look at whether the layer exists for a real reason or as a promotion mechanism. Clusters of single-report managers are worth reviewing before the next planning round, not during a cost exercise.

Sparingly, and separately from the solid line. Every employee needs one unambiguous reporting relationship for approvals, pay and accountability, and the chart should make that line obvious at a glance. Secondary relationships, such as a functional lead in another region, a project owner, or a professional line for someone embedded in a business unit, belong as an additional attribute rather than woven into the main tree. Trouble starts when matrix relationships are encoded as real reporting lines, because approval routing then follows a path nobody intended and headcount gets counted twice in different views. If the structure genuinely runs on dual reporting, define in writing which line owns each decision type: performance, pay, leave approval, priorities. The chart can then reflect that rule instead of implying an equality that does not exist.

Because both read the structure rather than a list of names. Approval routing sends a leave request, an expense claim or a requisition to whoever occupies the parent position, so a wrong line delivers the decision to the wrong person and delays it. Access reviews work the same way. For planning, the chart carries the seats: filled positions, approved but vacant ones, and the cost centers attached to each. That is what lets a plan be expressed as structure instead of a spreadsheet of headcount totals, and it connects straight to hiring, since a requisition should exist against a position the structure already recognizes. Teams doing this properly reconcile open roles in their applicant tracking system against vacant positions in the HR record and see immediately where the two disagree.