Guide
Org chart best practices for growing teams (30–500 people)
Between 30 and 500 people, the org chart stops being decoration and starts being infrastructure — new hires use it to find who to ask, and managers use it to spot gaps. These are the choices that decide whether people trust it.
Put on what people actually look up
Name, title, department, location, and a way to reach them. That covers almost every real reason someone opens the chart: "who runs this?", "who do I ask about that?", "who is at the Dallas site?".
Leave off compensation, performance ratings, and employee IDs. The moment sensitive fields live on the chart, access has to be locked down, and a chart nobody can open is a chart nobody uses.
One manager per person, always
A person with two managers breaks the tree and every downstream count — headcount by department, span of control, who is affected by a reorg. Pick the manager who owns the person's employment relationship. Everything else is a dotted line.
Represent dotted lines in the title or department field ("Safety Coordinator — reports to Ops, supports HR") rather than in the reporting structure itself.
Watch span of control, in both directions
Five to nine direct reports is the comfortable range for most managers of knowledge work; field and shift-based teams run much wider without trouble. The chart makes two problems visible at a glance:
- A manager with 20 direct reports — usually a missing layer, or a title that says manager but means senior individual contributor.
- A manager with one direct report — usually a legacy of a departure, or a layer that exists for a title rather than for the work.
Keep it shallow enough to fit on a screen
Below about 500 people, four to six levels from top to front line is normal. If you are at eight, someone is being managed by someone who is managed by someone doing the same job. Depth is the quiet cost of promoting people into layers instead of into scope.
Decide how you show contractors, open roles and vacancies
Pick one convention and apply it everywhere. The common ones that work: contractors get their agency in the department field; open roles are listed with the title and "Open" as the name so the gap is visible in headcount conversations; people who have resigned stay until their last day, then come off.
Inconsistency here is what makes people stop trusting the chart — one phantom employee is enough.
Give it one owner and one update trigger
Charts rot when everyone can edit and nobody is responsible. Name a single owner — normally HR ops or the office manager — and tie updates to an event you cannot miss: payroll runs, onboarding, and the day a reorg is announced.
Everyone else should get a read-only link, not an editable copy. The update habit matters more than the tool.
Publish views, not one giant diagram
A 400-person chart printed on one page is unreadable. Publish a department view for each team and a leadership view for the top three levels, and let people expand from there. On phones, a collapsible outline beats a pinch-and-zoom canvas every time.
Build the chart while the file is still open
Import your roster, fix the odd manager line, share a link. Free for up to 25 people — no card, no sales call.