TAC HRTAC HR
Organizational chart
Platform and administration

Organizational chart

الهيكل التنظيمي

An organizational chart shows departments and who reports to whom. Definition, a span-of-control example for a 48-person company, and the TAC HR screen.

Last updated3 min read

An organizational chart shows a company's departments and levels, and who reports to whom: every employee has a department and a direct manager. It is not only a diagram for presentations: approval routes and viewing permissions are built from it, and it decides who approves whose leave.

Span of control and number of levels

A chart is read with two figures. Span of control is how many people report directly to one manager. Number of levels is how many layers there are from the general manager to the most junior employee. A very narrow span with many levels means a decision passes through many hands before it lands. Building a chart by company size is covered in An org chart for a company of 10 to 100 employees.

Worked example

A company of 48: a general manager, 5 department heads, and 42 employees across the departments.

  1. The general manager's span: 5 department heads.
  2. A department head's average span: 42 ÷ 5 = 8.4 employees.
  3. Levels: 3 (general manager, department heads, employees).
  4. Add two supervisors in each department: 10 supervisors, so a department head's span becomes 2, a supervisor's (42 − 10) ÷ 10 = 3.2, and there are 4 levels.
  5. A leave request that needed one approval now needs two before HR, without anyone more doing the work.

Organizational chart in TAC HR

The organizational chart screen has three views: a department chart, a reporting line that the system builds from each employee's direct manager, and a list. At the top it shows figures: number of departments, number of levels, active employees, department heads, employees with no department, and employees with no direct manager. From the employee file, the "employee's direct manager" approver in request approval routes is resolved, and user permissions are scoped by branch and department. See the platform and the employee requests service.

Common mistakes

  • Employees with no direct manager: their requests find no approver at the first step, which is why the screen shows how many there are at the top.
  • A new level for every promotion: narrows the span and lengthens the route, as in step 4. For approval routes across branches, see Leave approval in a multi-branch company.
  • A chart that does not match permissions: someone seeing another department's data for no reason, as in User permissions by branch and department. For a role with no backup, see A simple succession plan for a branch manager.

Show us how you work, and we'll show you the difference.

In the demo we walk through a full day in your company: the morning punch, a request, the month's payroll, and the rep in the field, on data like yours.