Org charts in Pitch N Hire HRMS

What org chart includes

How is the org chart built from employee data?

The chart is a view of data you already maintain. Each employee record carries a reporting manager, and those pointers together form the hierarchy, so there is no second structure to draw or keep in step. Adding a person with a manager places them under that manager straight away. Departments, locations and grades on the same records give the chart its grouping, so you can colour or filter by any of them. Because the source is the record rather than a diagram, the chart cannot quietly disagree with the system that routes approvals or builds team reports; when the chart looks wrong, the record is wrong, and fixing the record fixes both at once. Teams comparing tools for this usually start with our org chart software guide; this page describes the module inside the HRMS.

What happens to the chart when a reporting line changes?

Changing the reporting manager on an employee record moves that person and everyone beneath them in a single action, so a team transfer does not need each individual reassigned. Changes carry an effective date, which means a restructure can be entered ahead of time and take effect on the day it is meant to. The chart keeps the previous arrangement in history rather than discarding it, so you can still look at how the structure stood before the move. Because approval routing reads the same field, somebody who changes manager starts sending leave and regularisation requests to the new manager automatically from the effective date — a common failure point where the chart and the approval matrix are maintained separately. Both managers are notified that the move has happened.

Can the org chart show matrix and dotted-line reporting?

Yes. The primary reporting line is the one that drives approvals and team views, and it stays single so there is never ambiguity about who signs off. Alongside it, further relationships can be recorded — a functional lead, a project owner, a regional counterpart — and displayed as dotted connections. This matters where somebody sits in a country structure but works to a global function: the solid line describes accountability for leave, attendance and reviews, while the dotted line describes who they work with day to day. Filters let you look at either view on its own, so a functional head can see everybody in their discipline across departments without the primary hierarchy being redefined around them. Dotted relationships are displayed and reportable, but they never divert an approval.

How do you view headcount by department in the chart?

Every node rolls up the people beneath it, so a department head shows their direct reports and the total in their branch. Grouping switches to department, location, employment type or grade, which turns the same chart into a headcount view: how many people sit in each function, how permanent and contract staff split across sites, where a single manager carries an unusually wide span. Counts update as records change, so a figure in a board pack matches the system on the day it was taken. For movement over time — joiners against leavers, span-of-control shifts, growth by function — those numbers feed HR analytics rather than being retyped into a spreadsheet from a chart export somebody took last quarter and never refreshed.

Where do open roles and vacancies appear on the chart?

An open role can be placed in the structure it belongs to, under the manager who will own it, so a vacancy is visible where the work sits rather than only inside a recruitment report. Filled and open positions render differently, which makes gaps in a team readable during planning. Where the role is being recruited through the applicant tracking system, the position on the chart and the requisition describe the same job, so a hiring conversation and an organisation conversation do not drift apart. When the hire is made and the employee record is created under that manager, the person replaces the open position. Roles that are planned but not yet approved can be held separately from live vacancies, so a wish list never inflates the structure.

Who can see the company org chart?

The chart is usually one of the few company-wide views, because knowing who does what and who to ask is useful to everyone. Access is still governed by role: the shape of the organisation, names, designations and departments are typically visible to all employees, while anything sensitive on the underlying record — compensation, personal contact details, documents — stays restricted exactly as it is on the profile. Clicking a person opens what the viewer is allowed to see, not a fuller card. Some organisations narrow the chart during a restructure, showing a branch only to the managers involved until the change is announced. Because permissions are inherited from the record rather than configured separately for the chart, the two cannot fall out of alignment over time.

How do you use the org chart to plan a restructure?

Planning starts from the current structure rather than a blank canvas. You take a branch, model the moves under consideration, and see the resulting spans, headcount and reporting depth before anything is applied. Effective dating means the agreed version is entered once and released on the day it takes effect, instead of somebody editing records manually on the morning it starts. Comparing the point-in-time view before and after gives a record of what changed and when, which is what most internal reviews ask for afterwards. Where roles are disappearing rather than moving, exit dates recorded through offboarding remove those people from the live chart on their last working day, so nobody has to remember to prune a diagram after the fact.

How does the reporting structure drive approvals elsewhere?

The same reporting field the chart draws from decides where requests go. Leave applications, attendance regularisations, timesheet submissions, profile change requests and review sign-offs all route to the manager on the record, and climb the branch when they are not actioned. This is why maintaining the structure is not a cosmetic exercise: an out-of-date reporting line sends requests to somebody who no longer manages the person, and the request stalls quietly rather than failing loudly. Multi-level chains follow the branch upward, so an approval needing a second level finds it without a separate matrix being kept. Routes that must depart from the hierarchy — a finance sign-off, a legal review — are configured in HR workflows on top of it.