A reporting structure defines the formal relationships between employees and their managers - who each person reports to, who approves their work, and how issues are escalated. The org chart is the picture; the reporting structure is the set of relationships it represents.
When reporting lines are clear, people know whose priorities come first and where to take a problem. When they aren't, you get duplicated work, conflicting instructions and employees caught between two managers.
What a reporting line actually means
Saying "Priya reports to Arjun" usually implies that Arjun:
- Sets or approves Priya's priorities
- Reviews her performance and has input on pay and promotion
- Approves leave and expenses
- Is her first point of escalation
- Is responsible for her development
If those responsibilities are split across different people, the reporting line is unclear - even if the org chart looks tidy.
Types of reporting relationships
Solid-line (direct) reporting
The primary manager relationship described above. Every employee should have exactly one solid line.
Dotted-line (indirect) reporting
A secondary relationship where someone gives day-to-day direction or subject-matter oversight, but isn't the primary manager.
Examples:
- A regional finance executive reports to the regional manager (solid line) but follows standards set by the head of finance (dotted line).
- A designer in a product team reports to the design lead (solid line) and takes project priorities from the product manager (dotted line).
Dotted lines are useful, but only when both managers agree who decides what.
Functional vs operational reporting
In multi-site businesses, people often have an operational manager (the site or outlet manager who runs their day) and a functional manager (the head of their discipline who sets standards). Decide which is the solid line and write it down.
Common reporting structure problems
- Two bosses, no rules. Someone receives conflicting instructions and nobody has agreed whose wins.
- Skip-level shortcuts. Senior leaders regularly bypass managers and give instructions directly to their team, undermining the manager.
- Orphan roles. Freelancers, new functions or roles left behind after someone leaves, with no clear manager.
- Founder as default manager. On paper everyone reports to a lead, but real approvals still go to the founder.
- Reporting to the wrong function. For example, quality reporting to production, where output pressure can override quality decisions.
How to define a clear reporting structure
Step 1: Map the current reality
List every employee with their formal manager, then ask managers and employees separately: "Who actually sets your priorities? Who approves your leave? Who do you escalate to?" Differences between the answers show where the structure is unclear.
Step 2: Assign one solid line per person
For each employee, choose the one manager who owns priorities, performance and development. If that's hard to decide, the role itself may be unclear - clarify the role's responsibilities first.
Step 3: Limit and define dotted lines
Keep dotted lines to the relationships that genuinely need them. For each one, write a sentence covering what the dotted-line manager decides (for example, "sets design standards") and what stays with the solid-line manager (for example, "priorities, leave, performance").
Step 4: Check spans of control
A reporting structure can be clear and still unworkable if one manager has too many people. Review span of control for each manager as you redraw the lines.
Step 5: Protect independent functions
Some functions work best when they don't report into the teams they check - quality, internal audit, and health and safety are common examples. Give them a line to senior leadership.
Step 6: Draw it and communicate it
Build the updated org chart and walk through changes with every affected employee before sharing it widely. People should hear about a new manager from a conversation, not from a diagram.
Example: fixing a restaurant's reporting lines
Before: servers took instructions from the owner, the manager and the head chef, depending on who was nearby.
After:
- Servers → Floor manager (solid line)
- Floor manager → Restaurant manager (solid line)
- Head chef → Restaurant manager for operations; owner for menu decisions (defined dotted line)
- Kitchen staff → Sous chef → Head chef
The result: one person in charge of each part of service, and conflicts between floor and kitchen going to the restaurant manager rather than being argued out during service. See the full restaurant org chart template.
Keep reporting lines visible
Reporting structures slowly change as companies grow, people leave and new roles appear. Keep an up-to-date org chart where everyone can see it, review it quarterly, and update it the same day any reporting line changes. The free org chart maker makes this a five-minute job.
