Org Chart Software: Build Structure From Employee Data
Org chart software generates your reporting structure directly from employee records, so each person appears once, positioned by the manager field on their own row, and the chart redraws when that field changes. The same structure drives approval routing, data visibility and department rollups, and it exposes span of control, layer counts and unfilled positions.
Last updated
Free 1-user plan · No credit card · Talk to a real recruiter
What does org chart software do?
It draws your reporting structure from employee data instead of from a drawing tool, so the chart is a view of the record rather than a separate document. Each person appears once, positioned by the manager field on their own record. Change a reporting line in the system and the picture redraws. That single property is the whole value, because a chart maintained by hand goes out of date the week after it is published and everybody quietly stops trusting it. Beyond the picture, the structure powers other things: approval routing, who may see whose data, department rollups for budget, and the layer counts that reveal whether the organisation has quietly grown a middle. The terminology is covered in our glossary entry. Structure is data, not decoration.
- One node per person, positioned by the manager field
- Redraws automatically when a reporting line changes
- Feeds approval routing and data visibility rules
- Exposes span, layers and unfilled positions
Why is a slide deck version not good enough?
Because it decays, and because nothing reads from it. A chart drawn in a slide or a diagramming tool is accurate on the day it is exported and wrong after the next joiner, exit or team move, with no mechanism to tell you which. Several versions circulate, each confidently labelled final. Nobody can answer basic questions from it: how many people report to this manager, how many steps sit between the founder and a new joiner, which roles are vacant. Worse, the drawing has no relationship to your systems, so approvals, permissions and reports carry on using a different structure entirely, and the two disagree without anyone noticing for months. A chart generated from the employee record cannot drift, because there is nothing separate to drift from.
Want this priced against your own hiring volume?
Free forever for 1 user · no credit card
How does the chart stay current?
It stays current when exactly one field owns each relationship and updating it forms part of a process somebody already follows. The manager field on the employee record is that field. If a promotion, transfer or exit updates it as part of the standard change, the picture is correct by construction. Problems appear when the reporting line lives in three places, so a transfer updates payroll but not the record, and the chart still shows the old team. Give the update a home in your joiner, mover and leaver process rather than a quarterly clean-up. Let managers see their own subtree, since they will spot a wrong line faster than HR ever will. Then watch for people with no manager assigned and anyone reporting to a leaver, because those two checks catch most structural errors.
What is span of control, and what should you do with it?
Span of control is how many people report directly to one manager, and layers are how many steps separate the top of the organisation from an individual contributor. Both fall out of the picture automatically once reporting lines are accurate. There is no universally correct number, and be sceptical of anyone quoting one: the right span depends on how similar the work is, how experienced the team is and how much coaching the role demands, so a support team and a research team legitimately differ. What these numbers are good for is spotting outliers and asking questions. A manager with sixteen direct reports probably cannot hold proper one-to-ones. A manager with one direct report may hold a title rather than a job. Find those cases, then decide with context rather than a rule.
How do you handle dotted lines, contractors and open roles?
Real structures are messier than a tree, so agree the conventions before the questions arrive. Dotted-line relationships, where somebody works to a second leader without reporting to them, should be visible but visually distinct, otherwise the picture implies two managers and approvals become ambiguous. Contractors and agency staff usually belong on the chart for coverage and coordination but should be marked clearly, because they typically sit outside payroll and outside some policies. Open roles are the most useful addition and the most often missed: showing an approved but unfilled position reveals where pressure sits and links structure to the hiring plan. Interim and acting arrangements need an end date attached, or they silently become permanent. Write these conventions down once, because otherwise three people will represent the same situation three different ways.
How does the chart support headcount planning?
Planning gets much easier when the structure is the plan. Start from what exists today, add the roles you intend to open with their target start dates, and you have something finance and the hiring team can argue about concretely rather than through a spreadsheet of titles. Because each position sits under a manager, cost rolls up by team and department without a separate mapping exercise, and you can see whose span doubles if every planned role lands. Sequencing becomes visible too, since a team lead usually needs to arrive before the people reporting to them. Keep planned positions clearly separated from filled ones so nobody mistakes intent for reality, then review the plan against actual joiners monthly. Pair the structure with HR analytics to see growth and attrition in the same shape.
Who should be able to see the full structure?
Most organisations benefit from making the shape broadly visible and the data on it narrowly visible, which are two separate settings. Everyone seeing who reports to whom removes real friction for new joiners and cross-team work, and there is rarely a good reason to hide the shape of a company from the people inside it. What should be restricted is what hangs off each node. Salary, personal contact details, performance information and documents belong to defined roles, not to anyone who opens the picture. Sensitive situations need care too: unannounced hires, roles created for a restructure and confidential open positions should stay in a planning view until they are real. Default to open on structure and closed on detail, then check that permissions in your HRIS match what is actually exposed.
What types of org chart are there, and which one fits your company?
Four shapes cover most organisations, and the right one describes how decisions are actually made rather than how you would like them to be. A hierarchical or functional chart groups people by discipline, each under a single manager, which is what most companies below a few hundred people genuinely have. A flat chart removes middle layers and holds only while one leader can still be in every conversation. A divisional chart groups by product, region or customer segment, with each division carrying its own functions. A matrix chart shows people working to both a function and a project at once, which is honest for the companies that operate that way and confusing everywhere else. Choose the shape that matches your approval routing, because the structure drives who signs what. When the picture and the approvals disagree, the picture is wrong. Write the convention down, since a different shape per department makes every rollup unreliable.
How do you build a company org chart from scratch?
Start from the list of people, not from a drawing. Export everyone currently employed, then check the one field the whole picture depends on: does each person have exactly one manager recorded, and does that manager still work here? Those two questions usually surface more errors than anyone expects, and they are far cheaper to fix in a list than in a diagram. Next, settle the conventions before anybody sees a draft, covering how contractors appear, how dotted lines are drawn, and whether approved but unfilled roles are shown. Then generate the chart, send each manager their own branch and ask them to confirm it, because they will correct a wrong line within a day. Publish only after that pass. Finally decide who maintains it and when, which should be your joiner, mover and leaver process rather than a reminder in somebody's calendar. Structure lives in the employee record.
How do you share the chart outside the system?
People will ask for the chart in a board pack, an induction deck or a supplier form, and that is a different job from the live view. What you want is a snapshot: the structure as it stood on a stated date, exported to a file and clearly labelled with that date so nobody circulates it a year later as current. Ask a vendor three things before relying on this. Can you export a chosen branch rather than the whole company, since a department head rarely needs everybody? Does the export carry only the fields you intend, because a picture that quietly includes salary becomes a data problem the moment it is forwarded. And can somebody outside the system be given a read-only view instead of a file, which stays accurate and can be withdrawn. Files cannot be recalled once sent, so prefer a link wherever the audience allows one.
What the chart answers, and what it depends on
| Question | Field it reads | Who keeps it current | What a stale value causes |
|---|---|---|---|
| Who does this person report to? | Manager on the employee record | HR, as part of every transfer or promotion | Approvals routed to the wrong manager |
| How many layers do we have? | The manager chain | Nobody directly; it is derived | Structure decisions made on guesswork |
| How wide is this manager's span? | Count of direct reports | Derived from the same field | Overloaded managers stay invisible |
| Is this role filled or open? | Position status | Hiring and finance together | Plans that count people who do not exist |
| Which department owns this cost? | Department or cost centre | HR with finance | Reports that never reconcile with the budget |
Keeping the structure trustworthy
- Make the manager field on the employee record the single source of reporting lines.
- Add the reporting line update to your joiner, mover and leaver process.
- Run a check for anyone with no manager assigned or a manager who has left.
- Agree how dotted lines, contractors and interim arrangements are shown before anyone asks.
- Mark planned and unfilled positions distinctly so intent is never read as reality.
- Let managers view their own subtree so they can flag a wrong line quickly.
- Separate visibility of the structure from visibility of salary and personal data.
- Review span and layer outliers each quarter and decide with context, not a target.
Related solutions
In Pitch N Hire HRMS
Terms on this page
Related questions
Related roles to hire
ATS for your industry
Free tools for this
Org chart software — FAQs
What is org chart software?
Why not just draw it in a slide?
How does the chart stay accurate?
What is span of control?
How do you show dotted-line reporting?
Can you plan headcount in the chart?
Who should see the full org chart?
How do you handle contractors and vacant roles?
What breaks during a reorganisation?
Should the chart match how finance sees the company?
What are the main types of org chart?
How do you create a company org chart?
The applicant tracking system for recruiters and hiring teams
Pitch N Hire is an applicant tracking system. Post roles, screen applicants, run structured interviews, and make offers from a single pipeline — free for 1 user.
Free for 1 user · No credit card · Talk to a real hiring expert
A chart that updates itself
Book a demo to see structure, span and planned roles in one view, or start free and map your first team today.
Prefer to talk? Book a demo Talk to sales View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
