“Please Don’t Tell Anyone”: A Manager’s Guide to Handling an Employee Complaint

It’s 4:45 pm on a Friday. Someone on your team asks if you have a minute, closes the door and says: "I need to tell you something, and please don’t tell anyone."

What do you say?

Most managers have signed a policy about what they're supposed to do. But very few have been taught - or practiced. So this is a guide: the words, the steps, the questions you’ll have and a five-minute audit you can do this week. And I’ll make the case for why organizations should train every manager on this, not just the ones in places where the law forces them to.

Note: This blog and video cover a lawsuit involving an allegation of inappropriate conduct by a manager toward an employee. I don't go into detail, but I want to flag it upfront in case it's one you'd rather skip. Employment law also varies by state and country, and none of this is legal advice. For your own situation, your Legal and HR teams are who to ask.

This isn’t only about harassment

An employee complaint can show up in many ways. It could be an employee telling you a coworker is making the team miserable. Or someone says a safety rule is being skipped to hit a deadline. Someone found out what a colleague gets paid. Someone thinks they were passed over because of their age or race.

The details change - but what you do doesn't need to. So even if you've never had a harassment complaint, as a manager, you'll have some version of this conversation, and knowing what to do and say matters.

What to say in the first 60 seconds

When someone tells you they need to tell you something, you're probably not going to think about whether this meets the legal definition of a "hostile work environment." Your heart might be pounding, and your brain is trying to think of what to say next.

Here are example words:

“Thank you for telling me. I’m taking this seriously. I’m not able to keep it just between us, because the organization needs to look into it - but we’ll do everything we can to make sure it’s handled appropriately, and either I or HR will reach out about what's next.”

As a manager, you usually aren't going to be the investigator. That means you're not responsible for figuring out whether it’s true, whether it meets a legal standard or whether the other person meant it that way. Your job in that conversation is to receive it well and route it correctly. That’s it.

The one thing you can’t promise

The instinct to say “of course, this stays between us” comes from a caring place. It's also the single most damaging thing you can say here. Here's why.

Because, once you know, that can mean that "the organization" is on notice. Most policies require any manager who becomes aware of a possible policy or conduct violation to report it, which means the promise you just made is one you were never able to keep. And if you break it later, the employee doesn’t see that as you following policy. They experience it as you breaking their trust.

What you can promise:

- You’ll share it only with the people who need to know

- Retaliation for raising it isn’t allowed, and they should tell you immediately if they feel in any way like that's happening

- They'll hear from someone about next steps (and ideally you'll tell them exactly who will reach out as soon as you confirm it)

What you can’t promise: silence, a specific outcome or that the other person will never learn a complaint was made.

What to do in the first 24 hours

1. Write it down the same day. What you were told, when and exactly in their words. Not your interpretation, not your conclusion about whether it’s valid. Memory gets contested later, and notes written the same day can matter when it does.

2. Report it to HR or whoever your policy names. Promptly means promptly. It doesn't mean after you’ve looked into it yourself, nor after you’ve decided whether it’s serious enough, nor after you find out it happened again.

3. Don’t investigate it yourself. Don’t go get the other person’s side, poll the team or go looking through anyone’s messages. Well-meaning manager fact-finding is how evidence gets contaminated and how the person who the complaint is about finds out before they were supposed to.

4. Don’t change the employee’s situation without asking. Moving them off a project or a team to protect them can look like retaliation even when your intent was kind. Always ask HR first.

5. Close the loop. Go back to them within a few days, or confirm the team handling it will, even if there’s nothing new to share. Silence always gets filled with the worst-case scenario - usually that the organization isn't taking it seriously.

That last one is the step that often gets skipped. Remember this, because it’s about to show up in a court record.

Questions managers actually ask

Do I have to report it if they specifically asked me not to?

Almost certainly yes. Check your own policy, but most require any manager who becomes aware of possible misconduct to report it. That obligation doesn’t change because someone asked you to keep it quiet. What you control is how they find out it's getting reported - from you in that conversation, not from someone else three days later.

What if they said it was “off the record”?

There’s no off the record with a manager. That isn’t a rule you invented and it isn’t personal. Say it early: “Before you go further, I want you to know I’m not able to keep something like this to myself if it’s about how someone's being treated - even if it's just a rumor that needs to get looked into. I’d still really like to hear it.” Giving them that choice upfront is more respectful than taking it away afterward.

What if the complaint is about my own boss?

Go to HR or to whoever else your policy names. Most policies list multiple channels precisely for this situation. If your organization is small enough that there’s no clean path, that usually means going to the most senior person who isn’t involved.

What if I’m not sure it even counts as a policy issue?

That’s not your call, and deciding it wasn’t one is exactly the judgment call that can read very badly in a deposition. Report it and let HR sort out whether it falls under the policy. “I wasn’t sure, so I asked” has never been the problem in any case I’ve seen. Instead, it's been an assumption of "I didn't think it was my place to say anything" - and that assumption turns out to be wrong.

What if they tell me and then say they don’t want anything done?

You still report it. You can absolutely pass along what the employee wants, and a good HR team will consider and handle that. But the organization’s obligation exists independently of what the employee prefers, and that’s worth explaining to them kindly rather than pretending otherwise.

Your five-minute exercise as a manager

Pro tip: Do this before you need it. Go to your organization's handbook and answer four questions:

1. Who does the policy say complaints can go to? If it says “any member of management,” that likely includes you - and possibly others who don’t think of themselves as management at all.

2. What does it require you to do once you know? Most say report to HR promptly. Do you know who that is by name?

3. Are there timelines in it? Some policies specify how quickly you have to escalate.

4. Have you or your team ever been trained on it, or just handed it to sign?

If you're not 100% positive on any of these questions - definitely ask HR.

And if the last answer is “just handed it to sign,” you're not alone. But that's what brings me to the part for HR.

Where this breaks at scale

Training requirements vary globally - from what needs to be covered to who needs to be trained. For example, in the United States, harassment training is only required in a handful of states, including California, Illinois, Connecticut, New York, Maine, Delaware and Washington for certain roles, plus cities like Chicago and New York City.

So most organizations do the rational-seeming thing. They train where they’re required to and distribute the handbook everywhere else.

That's common, but it also creates problematic inconsistencies. Because a manager in Ohio can get that exact same Friday afternoon conversation as a manager in California, with none of the same preparation. The policy might have been clear about what to do - but the manager doesn't remember it.

I don't have to give a hypothetical about how that plays out - a U.S. federal judge has already looked at that arrangement and had something to say about it.

How this actually happened in a court case

The case is Graham v. Phillips Feed Service, Inc., No. 4:20-cv-00020 (N.D. Ohio Dec. 27, 2021).

A national pet food distributor had an anti-harassment policy, and it was pretty clear. Complaints could go to a supervisor, HR or any member of management, and any manager who became aware of possible misconduct was required to advise HR immediately.

A territory sales manager alleged that her direct boss assaulted her in his hotel room during a work trip. She told a coworker, another territory sales manager, that same day. The advice she got, according to the lawsuit, was keep your head down. Months later she told a more senior employee that her manager was treating her unfairly and that she believed it was connected to the trip. He escalated it to his own boss, who said he’d handle it and never called HR.

She kept working alongside her original manager. At one point he mentioned the complaint had almost cost him his job, which tells you somebody had talked to him. Nobody had talked to her. No investigation, no here’s-what-happens-next. Remember step five.

It took eight months and three managers before HR investigated. The accused manager was then fired for violating the policy. About a year later she lost her job in a layoff, and she sued.

In court, the employer raised the Faragher-Ellerth defense. In plain English, this affirmative defense lets an employer argue: we had a policy, we took reasonable steps to prevent and correct this, and the employee didn’t use the process we gave her. When it works, it can end a case like this entirely.

But it only works if the policy was effective. And in this case, the court laid out what "effective" means, quoting the standard directly: a policy should at least require supervisors to report incidents, permit both informal and formal complaints, provide a way to bypass a harassing supervisor and provide for training regarding the policy.

Then came the finding that should get HR's attention. The organization, the court noted, "other than in California, [the organization] does not provide training on its harassment policy." That, the court said, arguably rendered the policy “ineffective.”

The harassment and retaliation claims survived summary judgment and were headed for a jury trial. The case settled shortly before trial. While the exact settlement amount was confidential, the total amount of legal fees plus settlement was no doubt significant.

Why you train everywhere, not just where you’re required to

If you’re in HR and your training map matches your legal obligations (i.e., where the law explicitly requires it), here’s the argument for changing it.

1. The defense you’re counting on might require it. Training isn’t a nice-to-have sitting next to your policy. In this case, it was one of four things that make a policy effective. An untrained policy is a policy you can’t point to in the moment you most need to.

2. The patchwork itself becomes evidence. “We trained in California because California made us” is a sentence that gets read out loud in a deposition. It doesn’t say you couldn’t train. It says you knew how, knew it mattered and decided where to do it based on what you were forced to do rather than where your people were. The judge didn't like it, and a jury might not have, either.

3. Complaints don’t care about state lines. You have a manager in Texas supervising someone in Illinois, a remote team across nine states and three countries, a regional leader who covers four. Who do you train and how? You might need additional training in some places, but not having a consistent foundation can make it all seem like a check-the-box exercise.

4. The state minimum is a floor, and often the wrong shape. Most mandated training is built around legal definitions and compliance. Very little of it teaches anyone what to say. You can be perfectly compliant in California and still have a manager who says keep this between us, because nobody ever focused on the practical aspects of being a manager. Compliance and capability are not the same purchase.

5. The math genuinely isn’t close. The cost of training every manager is a number you can put in a budget. The cost of one case that survives summary judgment is not - outside counsel, depositions, leadership hours, a public record with your organization’s name on it and a settlement you’re not allowed to discuss. Let alone an award decided by a jury.

And then there’s the part that has indirect costs - including real human ones. Eight months of an employee asking for help and getting the wrong answer from people who may well have meant well. That shows up in your attrition number, your engagement scores and your Glassdoor page, and nobody ever traces it back to a training decision made three years earlier.

What “training everywhere” actually means

Not a two-hour compliance module for all 400 managers. The version that works is shorter than what you’re already doing in California, and it’s three things.

Tell them why. Not “because Legal says so.” Because this is a complaint by a person who's likely terrified to report it. And in the moment someone reports something to you, you are the organization. What you do next is what the organization did. When managers get that, calling HR stops feeling like tattling and starts feeling like the job.

Give them the actual words. A definition of the federal law for hostile work environment doesn't help that manager on a Friday afternoon. A sentence they can say out loud does - especially if it's short enough to remember under pressure.

Let them practice. Reading a script on paper isn’t the same as saying it to a real person whose voice is shaking. Managers need to run the scenarios before they’re real.

The real cost

Think about every failure in just that one example case. The coworker who said keep your head down. The supervisor who said he’d handle it and never called HR. They probably had no idea this could end up in federal court. They likely did whatever their gut said - protect your own job, keep it quiet, don’t get involved.

A signature tells you someone received a policy. It doesn’t tell you they read it or understood it. And it definitely doesn’t tell you they’ll know what to say in a real moment when someone is sitting in front of them asking them not to tell anyone.

The best organizations don’t hand out policies and call it a day. They train for the moment before it happens, because plenty of others have learned that lesson the other way.

If you’re in HR: Training only where the law requires it is the norm, not the exception. But this case is an example of what it can cost. Our leadership platform is a blended program where managers learn the why, get the words and practice the scenarios with your own HR team leading the sessions - in every location you operate in, not just the few that make you. Book a call here to see how it works at scale.

If you’re a manager: At some point, someone is going to tell you something you don’t know what to do with. If you wouldn’t know what to say, you’re not alone - it’s one of the most common training gaps there is. Manager 101 exists to close it, so you know what to say and do in the moment instead of months later.