How to define a reporting hierarchy

Principles of a clear hierarchy

A few simple rules prevent most reporting problems. Write them down as company policy, so managers cannot quietly create exceptions for their own teams, and check new structures against them before they are announced. They matter most in fast-growing companies, where teams form quickly and reporting is often agreed in a corridor.

• Every employee has exactly one solid-line reporting manager
• The manager sees the person's work regularly, on the same site or shift where possible
• Leave, attendance and performance run through the solid line
• Each employee also has a named HR partner for policy and welfare questions
• Keep the number of levels between frontline staff and the top as low as practical

Span of control

Span of control is the number of direct reports a manager has. Routine, similar work supports wider spans: a team leader in an Indore BPO can manage around 15 agents doing the same process. Complex or varied work needs narrower spans: an engineering manager with eight senior engineers on different projects is already stretched. In a hospital, a ward sister might supervise the eight to ten nurses on her shift. Check spans against your own work, and look closely at anyone with more than 25 direct reports or fewer than three.

Dotted lines and matrix roles

A dotted line is a secondary relationship for functional guidance. A branch accountant might report to the branch manager on the solid line for daily work, leave and attendance, and to the CFO on a dotted line for accounting standards. Write down what each line covers: usually the solid line approves requests and owns the rating, while the dotted line gives input to the review. Keep dotted lines few; when everyone has two bosses, nobody is accountable.

When a manager leaves or moves

Reassign every direct report before the manager's last working day, not after. Name an acting manager if the replacement is not yet hired, and check for requests waiting on the departing manager, such as leave, attendance corrections and overtime. An employee without a manager in the system cannot get anything approved, and people notice within a day.

• Two solid-line managers for one employee
• Managers on another site who never see the team's work
• Reporting lines changed in conversation but not in the system
• Spans of 40 or more under one supervisor
• Nobody reassigned when a manager resigns

Step by step

1. Map reporting as it really works. Ask each team who gives them work, who approves their leave and who reviews them. Compare the answers with your records.
2. Fix one solid-line manager per person. Choose the person who sees the employee's work most closely, and record them as the reporting manager.
3. Check spans of control. Count direct reports for every manager, and split or merge teams where spans are far too wide or too narrow for the work.
4. Decide dotted lines and what they cover. Record the few dotted-line relationships you need and state in writing what they do and do not approve.
5. Name an HR partner for each group. Assign an HR partner to every employee or team. In ZeniaHR, every employee has both a reporting manager and an HR partner on their record.
6. Record reporting lines in your HRMS. In ZeniaHR, the reporting subtree drives each manager's My Team view and data access, and leave, attendance and other requests go to the reporting manager, then HR.
7. Set a rule for manager exits. Require HR to reassign direct reports and clear pending approvals before any manager's last working day.
8. Audit reporting lines monthly. Check for employees with missing or departed managers. ZeniaHR's org chart flags broken reporting lines for correction.

Frequently asked questions