The phrase “just looping you in” should come with a trigger warning in corporate environments. It’s corporate language for “I’m documenting this so you can’t later claim you didn’t know,” and everyone knows it.
The CC field is one of the most weaponised tools in modern workplace communication, and barely anyone talks about it directly. Instead, we’ve developed an entire pantomime around it. People send emails to someone, then add their manager to the CC line with the subject line “just looping you in on this.” Translation: “I want my boss to see that I’m doing good work,” or alternatively, “I want my boss to see that this other person is underperforming,” or most accurately, “I’m covering my arse.”
This isn’t communication. This is theatre dressed up as transparency.
There are actually legitimate reasons to CC people. If your manager needs to be aware of what you’re committing to, fair enough. If a stakeholder needs visibility into a decision, that’s reasonable. If you’re copying in someone who directly needs to be involved in the conversation, that’s just practical. But that’s not what most CC culture looks like.
Most CC culture is motivated by anxiety, politics, or defensiveness. Someone CCs their manager not because the manager needs to be in the conversation, but because they want protection. They want a witness. They want evidence. “See, boss? I told them this. I documented it. If it falls apart, it’s not on me.”
That’s not collaboration. That’s self-protection masquerading as transparency.
Then there’s the subspecies of CC that’s pure passive aggression: the FYI loop. Someone sends you an email with updates that you have no role in and no ability to influence, just so they can say later “well, I looped you in.” You didn’t need to be looped in. You can’t do anything about it. But now you’re responsible for reading and potentially responding to something that isn’t your problem. FYI emails are the corporate equivalent of someone leaving a mess in your kitchen and saying “I was just keeping you informed about the state of the dishes.”
And then there’s the territorial CC. Someone’s been moved into a new role, and suddenly emails they’d normally never be on are showing up in their inbox because the original manager can’t quite let go. “Just making sure you’re in the loop” on decisions that are now someone else’s job. It’s not transparency. It’s checking in on your territory.
None of these motivations are on the agenda. The email has a business purpose stated right there in the subject line. But the real agenda is social and political: covering yourself, protecting your position, documenting your involvement, preventing someone else from looking good without you knowing about it.
The problem with CC culture is that it’s fundamentally asymmetrical. The person doing the CCing has a clear motivation and clear benefit. They’re protected. The people being CCed inherit the burden of processing information they didn’t ask for and may not need. In a healthy organisation, that’s friction. In a dysfunctional one, it’s the default mode of operation.
I’ve seen teams where emails are so heavily CCed that people stop reading them. The signal-to-noise ratio becomes so terrible that important information gets buried in the assumption that if it’s really important, someone will escalate it. Which means the original communicator’s careful documentation now means nothing because nobody’s paying attention anyway.
The shift to remote work and async communication should have improved this. It didn’t. If anything, it got worse. People started using email as a liability prevention system rather than a tool for getting work done. “If it’s not in an email, it didn’t happen” is a sentence I’ve heard in too many organisations. It’s usually spoken by someone who’s been burned before, who’s learned to protect themselves through documentation rather than trust.
But here’s what actually works: healthy communication loops. This means being intentional about who needs to be involved in a conversation, at what stage, and why. It means using email for what it’s good at—documenting decisions, creating a record, informing people who need to know—and using other tools for what email is terrible at: actual collaboration, real-time problem-solving, and building trust.
It means that sometimes, you trust people enough to not need documentation. You make a decision together in a Slack conversation or a meeting, and you don’t need to send a follow-up email to your boss proving you were there. You do your job. Your work speaks for itself. If it doesn’t, an email won’t save you anyway.
The best teams I’ve worked in had a simple rule: only CC people who need to make a decision or who’d be blindsided by not knowing. Everyone else stays off the thread. It created discipline. People had to think about who actually needed to be involved. It reduced noise. And it created an environment where being included on an email meant something—it meant you had a role to play, not just that someone wanted a witness.
The shift away from CC culture is scary for people who’ve built their careers on documentation and protection. But the organisations that do it find they communicate faster, make decisions clearer, and ironically, have better records of what actually happened because they’re not drowning in defensive emails.
The real question to ask before you hit CC isn’t “could this person benefit from knowing this?” It’s “does this person need to know this right now, or am I using them as a shield?” If it’s the latter, you already know the answer.