Performance & metrics · Updated October 2026
Organisational structure is the way a company divides work and decides who reports to whom: the departments, the layers of management and the lines of authority between them. In an HRMS it becomes the reporting hierarchy that drives approvals, org charts and access.
Real companies mix these. A manufacturer might be functional at the plant and divisional across product lines.
Whatever shape you choose, the system needs it expressed as data: legal entities, locations, departments, cost centres and a reporting manager for every employee. Leave and expense approvals typically follow the reporting line, so does manager self-service visibility, and so do headcount reports. Get the hierarchy wrong and requests go to the wrong person or to nobody.
A quick sizing check: with an average span of 8, one head can have 8 direct reports, those 8 can have 64 between them, and the next layer has room for 512. So a 200-person company needs about three layers below the top. If your chart shows six layers for 200 people, spans are narrow somewhere. The span of control calculator does this arithmetic for your own numbers.
Plan structure changes around payroll. A reorganisation that moves 40 people between cost centres mid-month needs an effective date and a clean cost-centre mapping, or the salary cost lands in the wrong place.
At least yearly, and whenever you add a business line, open a new location or lose a layer of management. In the system, keep it current as changes happen, not in batches.
No. The chart is a picture of reporting lines. The structure also covers decision rights, grouping logic and how roles are defined, such as through job families.
Departments, locations, entities, cost centres and reporting manager per employee, with a history of changes. Check whether it also models vacant seats through position management.
Check how your own teams stack up by working through the span of control calculator.