Your designer formally reports to the Head of Marketing. But every Monday, the Product Lead sits down with them and sets their priorities for the week. Nobody wrote that down anywhere. Nobody calls it a reporting structure. It just happened because the work needed doing.
That is dotted line reporting. As companies grow and work starts crossing functional boundaries, these relationships often appear well before anyone formally documents them.
In this guide, I want to walk through what dotted line reporting actually is, how authority gets split between two managers, where it quietly breaks your HR processes, and how to write it down so everyone knows where they stand.
Dotted line reporting is a reporting structure where an employee has a primary manager plus a secondary reporting relationship to another manager, team, or function. The name comes from the org chart, where the primary relationship is drawn as a solid line and the secondary one as a dotted line.
In a normal setup, an employee has one manager. That person handles their day-to-day work, their priorities, their performance review, and their career. On an organizational chart, a solid line connects the two of them. That is solid line reporting.
In a dotted line relationship, the employee keeps that solid-line manager and also reports to a secondary manager for part of their work. The dotted line shows the second connection. It is usually narrower in scope, often tied to a specific project, function, or region.
You will also see dotted line relationships described inside a matrix or dual reporting structures, and the secondary manager is called a dotted line manager, a secondary supervisor, or a functional manager. Terminology varies between companies, which is one reason it helps to define what you mean in your own documentation.
Here is the part that trips people up. A dotted line is a description, not a rulebook. It tells you that a secondary reporting relationship exists. It does not tell you what that manager can and cannot decide. That part is something your organization has to define on its own, and most of the confusion around dotted line management comes from skipping that step.
The main differences between solid line and dotted line reporting come down to authority, who owns the performance evaluation, and who sets priorities when work piles up. A solid line usually carries formal management authority. A dotted line usually carries influence over a defined area of work.
This table covers how the two commonly differ. I say commonly on purpose, because none of this is fixed by law or by any standard. It reflects widespread practice, and your company can define it differently as long as you define it clearly.
| Solid line reporting | Dotted line reporting | |
|---|---|---|
| Authority | Formal management authority over the employee | Limited authority, usually scoped to a project or function |
| Performance review | Commonly owns the formal performance evaluation | Commonly gives structured input into it |
| Priority setting | Usually, the final decision-maker | Usually negotiated or advisory |
| Employment relationship | Usually sits here | Usually does not sit here |
| Typical use | Functional ownership of a role | Cross-functional coordination |
| Main risk if unclear | Bottlenecks, because everything routes through one person | Conflicting priorities and confusion about who decides |
A dotted line should not be mistaken for an unimportant relationship. Its formal authority is usually narrower, but its practical influence can still cover a significant part of someone’s week.
A dotted line manager typically directs work within a defined scope, such as a project or a function, and gives input on performance. They typically do not hold authority over the employment relationship, set overall priorities alone, or make the final call on pay and promotion. The exact split has to be decided and written down by each organization.
This is where most confusion is, so I want to break it into three parts.
None of this is automatic. If you set up a dotted line relationship and never say which of these the secondary manager has, both managers will assume different answers, and your employee will find out the hard way.
The short answer is that somebody has to be named in advance. Not in the moment, when everyone is annoyed, and a deadline is approaching. In advance, when you set the relationship up.
A workable default looks like this. The solid line manager holds the employment relationship and has the final say on overall priorities and workload. The dotted line manager leads decisions inside their defined domain, meaning that within the project or function they own, their call stands. Anything that cannot be settled between them goes to a named person, usually a department head or HR.
One rule matters more than the rest: your employee should never be the one arbitrating between two managers. If they are regularly deciding which of their bosses to disappoint this week, that is not a personality problem or a time management problem. It is a sign that decision rights were never defined. Fix the structure, not the person.
| The quick testAsk both managers separately: Who decides what this person works on next week, and who approves their time off? If you get two different answers, you have found a gap in your reporting structure. It takes five minutes, and it is a fast way to spot a dotted line relationship that is going to cause trouble. |
Many growing companies have informal dotted line relationships before they ever design one. They appear when work crosses departments faster than the org chart gets updated. The problem is not the relationship itself; it is that nobody wrote it down, so nobody agreed on how it works.
Formal matrix organizations design dotted lines on purpose. Growing companies often do not. Yours may have appeared like this: somebody needed help, somebody else had the skills, and a working arrangement formed. Six months later, that arrangement is load-bearing, and it exists nowhere except in people’s heads.
Here is how to spot them. Look for anyone who:
If you find one, you have an informal dotted line reporting relationship. That is not a failure. It usually means your people are working across silos, which is what you wanted. It just needs naming before it turns into a problem.
These are common ways dotted line relationships appear in growing companies. If any look familiar, you already have a dotted line reporting structure.
| Pattern | Solid line to | Dotted line to |
|---|---|---|
| HR Business Partner | Head of HR | The business unit leaders they support |
| Regional finance controller | Head of Finance | The regional or country manager |
| Security or compliance officer | CTO or Head of Legal | Every engineering or ops team they oversee |
| Shared designer or copywriter | Head of Marketing | The product or project lead using their time |
| Operations lead across locations | Head of Operations | Each site or store manager |
| Product manager and engineering | Head of Product | Engineering lead for delivery decisions |
In every one of these, the same tension shows up. The solid line manager holds the person’s career. The dotted line manager directs a big chunk of their actual work. That works fine right up until the two want different things in the same week.
Dotted line reporting works well when you need coordination across departments without moving someone to a new team. It works badly in fast decision environments, when it is used to avoid a hiring decision, or when it is layered on someone who is already overloaded.
Remote work does not change the logic of dotted line reporting, but it does raise the cost of getting it wrong. When one manager sits in the same room as the employee, and the other is three time zones away, the nearby manager gets more visibility and more influence without anyone deciding that should happen.
Async communication adds to it, because two managers writing instructions in different channels at different hours can easily produce contradictory priorities that would have been sorted out in a shared office.
The fix is not more meetings. It is writing decision rights down and making sure both managers can see the same picture of what the employee is working on.
Dotted line reporting rarely fails in an obvious way. It fails inside routine HR processes that assume every employee has exactly one manager. Time-off approval, goal setting, performance reviews, promotions, expenses, and onboarding all need an explicit answer about who does what.
In practice, the trouble shows up in specific processes because almost every HR system and workflow you have was built on the assumption of one employee, one manager. Here is where that assumption breaks.
This is an easy place for friction to appear, and one of the simplest to solve in advance.
Your employee requests a week off. The request goes to their solid line manager because that is how your HR system is configured. That manager approves it. Nobody tells the dotted line manager, who had them scheduled for a launch that week.
Decide two things:
Does your employee have one set of goals or two? If two, who makes sure they add up to a realistic week?
A clean approach is to use one set of goals, with the dotted line manager contributing the ones inside their area and the solid line manager owning the total. That keeps one person accountable for whether the workload is achievable. Two separate goal lists, each written without knowledge of the other, can quietly create more work than one person can realistically carry.
Agreeing on a rough split of time up front helps too, even if it is imprecise. Something like 70 percent to the home team and 30 percent to the project gives everyone a shared reference point when new work appears.
In many companies, the solid line manager runs the formal performance review, and the dotted line manager provides structured input. That is common practice rather than a rule, and some organizations split it differently. What matters is that you pick one and say so.
The risk if you do not: your employee spends a third of their time on work their reviewing manager never sees. Come review season, that work is invisible, and the rating reflects only part of what they did.
Ask the dotted line manager for input in a structured way, not a casual chat in a hallway. Give them something specific to answer:
Collect it before the review is written. Input that arrives after the rating is decided is not input.
Promotion decisions usually involve the solid line manager, the department head, and HR. But a dotted line manager often has a clear view of the person’s ceiling because they have seen them handle work outside their comfort zone.
Decide whether the dotted line manager is consulted, recommends, or has no formal role. Any of those is defensible. What is not defensible is leaving it vague and then having the decision made by people who saw half the work.
Whose budget pays when your employee needs a tool, a course, or a flight for the project?
This is a small question that creates a surprising amount of friction because both managers can reasonably say it belongs to the other. Agree at the start: home team budget for anything related to the role, project budget for anything specific to the project. Or pick a different rule. Just pick one.
When someone joins a dotted line role, onboarding often covers the home team and stops. The second relationship gets explained in a passing comment, if at all.
Build both relationships into onboarding instead. Introduce both managers in the first week, explain the split and the time allocation, and put it in the onboarding checklist so it does not depend on someone remembering.
Offboarding has the same gap in reverse. When a person with two reporting lines leaves, the handover often covers their home team responsibilities, while the project work and context they held for the other team walk out with them. Make sure the dotted line manager is part of the offboarding process, not an afterthought who finds out on the last day.
To document a dotted line relationship properly, write it into the job description, record it in your HR system, agree on a written split of decision rights, and tell the team. Most dotted line problems come from the relationship existing in conversation but nowhere in writing.
This is the part almost nobody covers, and the part that actually prevents problems. Four things to do.
If the role has a dotted line built into it, say so before you hire. Something like: “Reports to the Head of Marketing, with a secondary reporting relationship to the Product Lead for product design work, expected to be around 30 percent of the role.”
Candidates deserve to know they will have two managers before they accept, and writing it forces you to be specific about the split.
A reporting relationship that lives only in someone’s memory disappears the moment that person leaves. Record the secondary manager alongside the primary one in your employee records, so it survives staff changes and anyone looking at the structure can see it.
This also matters for anything downstream that reads reporting data, including your org chart, approval workflows, and any directory synced from your HR system.
This is the single most useful thing you can produce. A short table, agreed by both managers and shared with the employee, covering the decisions that actually come up.
Here is an example. This is one possible allocation, not a standard. Your company might split these differently, and that is fine, as long as it is written down and everyone has seen it.
| Decision | Solid line manager | Dotted line manager | Employee | Escalates to |
|---|---|---|---|---|
| Time off | Approves | Notified | Requests | HR |
| Performance rating | Accountable | Provides input | Discusses with both | HR |
| Weekly priorities | Final say overall | Leads within project scope | Executes | Department head |
| Project deadlines | Notified | Sets | Delivers | Both managers |
| Promotion | Accountable | Recommends | n/a | Department head |
| Expenses | Approves role costs | Approves project costs | Requests | Finance |
| Training and development | Owns | Suggests | Requests | Solid line manager |
Fill this in once, at the start. It takes about twenty minutes and prevents most of the arguments that would otherwise happen six months later.
Announce the relationship to both teams. Not a big formal thing, just clarity: this person works with us on X; they report to Y, and here is roughly how their time is split. Without that, the second team assumes the person is fully available and gets frustrated when they are not, while the home team wonders where they went.
On an organizational chart, a solid line connects an employee to their primary manager, and a dotted or dashed line connects them to a secondary manager. The convention is widely understood, but not every org chart tool supports it, which is why some dotted line relationships never make it onto the chart at all.
The visual convention is simple and nearly universal. Solid line for the primary reporting relationship. Dotted or dashed line for the secondary one. Some charts also use colour or a label on the line to show what the relationship covers.
A few conventions worth following so your chart stays readable:
Here is the honest issue. Some org chart tools build the chart from a single manager field per person. Where that is the case, a second reporting relationship has nowhere to live, so the dotted lines simply cannot be drawn, and they stay invisible.
The same applies to org charts built in slide decks or spreadsheets, where every change is manual and dotted lines are usually the first thing to go stale.
If your org chart cannot show secondary relationships, you are looking at a simplified version of your organization, and the parts that are missing are often the ones most likely to cause confusion. Before you decide how to document dotted lines, it is worth checking what your current tool can actually display.
Remove a dotted line relationship when it consistently produces conflict, stalls decisions, or no longer matches the work someone actually does. The main thing to get right is the framing, because ending a reporting relationship can easily be misread as a demotion.
Dotted lines are not permanent. They exist to solve a coordination problem, and when that problem changes, the structure should change too. Watch for these signs.
If you remove a dotted line badly, the employee hears “you are no longer needed on that team”, and the second manager hears “you are losing a resource”.
A few things help. Explain the reason in terms of structure rather than performance, and be specific: the project ended, the workload shifted, the split stopped being realistic. Do it in a conversation before it shows up on the org chart, so nobody finds out from a diagram. Acknowledge the work done in that relationship and make sure it is reflected in the next performance review rather than quietly dropped.
If the change is happening because the arrangement was not working, say that honestly, while making clear it was a structural problem rather than the employee’s failure. In most cases, that is simply true. The structure asked one person to serve two sets of expectations without giving anyone a way to resolve conflicts between them.
Dotted line reporting is a structural choice about how authority gets split, and growing companies often end up making that choice by accident rather than on purpose.
The relationship itself is rarely the problem. What causes trouble is leaving it undefined: no agreement on who decides, no record in your HR system, no line on the org chart, and no answer for what happens when the two managers want different things.
So if you take one thing from this, make it the decision table. Sit both managers down, agree who handles time off, priorities, reviews, promotions, and budget, write it on one page, and share it with the person it affects.
| TRY IT FREEThrivea’s Core HR is free forever, including employee records, org charts, documents, and workflow automation. [CTA formulaciju uskladiti sa potvrđenim org chart funkcionalnostima.] |
It depends on what your organization decides. There is no standard definition. In common practice, a dotted line manager directs work within a specific project or function and gives input on performance, while the solid line manager keeps authority over the employment relationship. Write down the split for each relationship rather than assuming everyone shares the same understanding.
Usually, the solid line manager, because they hold the employment relationship, and your HR system is probably set up that way. The more useful question is who gets notified. The dotted line manager needs visibility of planned absence even if they do not approve it.
In many companies, no. The solid line manager runs the formal performance evaluation, and the dotted line manager contributes structured input on the work they oversaw. Some organizations split this differently, so decide in advance and collect the input before the rating is written.
Whatever you decided in advance. A common default gives the solid line manager the final say on overall priorities and workload, the dotted line manager the decisions inside their own project scope, and a named escalation owner, such as a department head or HR, for anything unresolved. The one thing to avoid is leaving your employee to arbitrate.
Yes, and it is common for shared specialists such as an HR business partner or a security officer. Each additional reporting relationship adds coordination overhead, though. If one person has several dotted line managers, treat that as a signal to review whether the role and the decision rights are still workable.
State both relationships and the rough split. For example: “Reports to the Head of Operations, with a secondary reporting relationship to each site manager for local scheduling, expected to be around 40 percent of the role.”
People use these terms loosely and sometimes interchangeably. Most commonly, a dotted line reporting relationship means a secondary manager who directs part of your work, while indirect reporting more often refers to your manager’s manager, someone above you in the chain who does not manage you day-to-day. Because usage varies, define which one you mean in your own documentation.
45 areas of improvement at work, with the exact wording for performance reviews, job references, and development plans. Because naming the gap is the ...
A manager is staffing a new project and needs someone who knows a specific tool inside out. They scroll through old performance reviews, message a few...
Most managers walk into a one-on-one meeting with no plan and walk out wondering why it felt like a status update. The right one-on-one meeting questi...
