Article

Copied in on everything: cutting the CC traffic you never asked for

To reduce the CC mail you get at work, ask the two or three people who copy you most to leave you off, then filter what remains into a folder you read once a day. Do it in that order. Asking removes the mail; a filter only moves it out of sight. The order matters more than it sounds, because the research on email load counts what arrives rather than what you open. This article covers what that finding does and does not say about CC, how to make the ask, and what to do with the copies you cannot switch off.

Which emails actually create the load?

Not the ones you answer. In 2024 Kern and colleagues published two studies in Frontiers in Psychology that split the inbox along two lines nobody usually separates. One line is whether a message was received or processed; the other is whether its function was to communicate something or to hand you a task. The second study, covering 257 workers, tested which of those classes predicted a high email load. Only one did: the number of communication emails received. Not the task emails received, and not the number of emails processed.

That result points away from most of the usual advice. Getting quicker at replies, deciding each message once, clearing the inbox before five: all of it works on mail you process, and the count that predicted load was mail that merely arrived. On this evidence you can run your inbox well and still carry the same weight, because the weight came in with the delivery rather than with the answer.

The first study adds the direction. Across 444 workers surveyed twice, a fortnight apart, email load ran ahead of time pressure and interruptions rather than trailing behind them, and the reverse pattern did not appear. A crowded inbox is not only what a busy week looks like from the inside. It is part of what makes the week busy.

None of which names the CC field. The study measured what an email is for, not which line of the header you appear on.

That gap is worth stating plainly, because the rest of this page rests on it. Communication mail is the class the second study implicates, and mail you were copied into is mostly communication mail: the status update, the confirmation nobody needed, the thread where two colleagues settle something in front of an audience. The overlap is close enough to act on and it is not the same thing as a measurement, since nobody has yet run the study that counts CC lines specifically. So treat what follows as a reasonable reading of the evidence rather than a finding, and test it against your own week, where the check is cheap: go through yesterday and count how many messages named you in To.

How do you get people to stop copying you in?

Ask one person, about one kind of thread. A general request fails because it asks a colleague to hold a rule about you in mind for months, and nobody does that. A narrow one changes a default instead: leave me off the deployment thread, I will pick it up in the ticket. Name what you will follow instead, since most copying is somebody making sure a thing does not get dropped, and an alternative answers that worry where a bare request to stop does not.

From the sending end, copying you in usually reads as courtesy. Nobody has measured what it reads as from yours, but the reverse case has been studied closely. Haesevoets and colleagues ran six studies, published in the Journal of Business Ethics in 2021, on what happens when an employee's mail always carries the supervisor in copy. CC did raise perceived transparency, and it produced the experience of being controlled alongside it: the employees doing the copying felt trusted the least when the supervisor sat in copy consistently rather than occasionally. The authors conclude that transparency experienced as a control mechanism stops being received as ethical at all.

Which is why your ask lands better than it feels like it will. Somebody copying you for transparency is not trying to keep tabs on you, and has mostly never thought about the copy line at all. Telling them gives them information they did not have. Keep it about the thread rather than about them, which is also the difference between a request that gets adopted and one that gets remembered as a complaint.

One reply is worth heading off: put me in Bcc instead. An earlier study by the same group, in Computers in Human Behavior in 2020, tested how recipients judge senders who reach for the alternatives to Cc. Senders who used Bcc were rated less moral than senders who used Cc, and less fit to lead a team. Forwarding a message scored as badly. Rewriting one before passing it on came out more moral than Bcc and still cost the sender on that same leadership judgment. Ask to be left off, not to be hidden.

Both studies come from one research team. The pattern holds across them, and nobody else has checked it yet.

Some copies are not yours to stop, and knowing which ones saves you a conversation. A procurement trail, a regulated approval, anything where the copy is the record: that is filing, and the person copying you has no discretion to drop you from it. A manager who wants visibility of a project is a different case, worth one honest exchange about what they actually want to see and whether a weekly summary would serve them better. Going quiet and hoping does not work. In practice, people who stop seeing you on threads tend to copy you more, not less.

What do you do with the copies you cannot stop?

Move them out of the inbox before you read them, then read them on your own clock. A rule that catches messages where your address sits in CC and files them in one folder takes a couple of minutes to set up in any mail client, and it converts a stream of small interruptions into a single appointment. Pair it with the checking schedule on the email pillar and treat the folder as its own batch, which is Task Batching applied to the half of the inbox that was never addressed to you.

A caveat follows straight from the research above. What predicted load was mail received, and a rule does not stop anything arriving; it relocates it. Whether moving mail out of sight lowers the weight of it is not a question those studies asked, so the honest claim for a CC folder is narrower than the usual pitch. It reliably removes the interruption. It leaves the volume where it was, which is why the ask comes first and the filter second.

Reading the folder needs one question rather than a system. Being in CC means the sender decided you were not the person who has to act, so ask whether the message changes what you do, and archive it when the answer is no. It usually is. Whatever survives the question is either a task in disguise, which belongs on your task list rather than in a mail folder, or a thread you need to follow.

Copied mail is the clearest everyday case of the trap the Eisenhower Matrix exists to catch. It looks urgent, because it is new and somebody just sent it. It is usually not important, because nothing in it is yours to move. Asking those two questions separately is what stops arrival time from doing your sorting for you.

Then there is the traffic you generate. Reply all is the one lever on this page you control outright.

Before sending to everyone, check whether everyone has anything to do with the answer. Most reply-all volume is acknowledgement, and each thanks or noted lands in a dozen inboxes as exactly the class of mail this page has been about. Replying to the sender alone is not a slight; it is the same information, delivered to the person who needed it.

How does your working style change the answer?

The evidence above is about inboxes. Your working style decides which half of the fix you will actually do. In practice, readers closest to this site's Architect style build the filter first and enjoy building it, then never make the ask, which leaves the volume intact behind a tidy folder. Improvisers are the mirror image, happy to say something to a colleague in passing and unlikely to maintain a rule set, so one good conversation buys them more than any amount of configuration. Sprinters do best when the CC folder gets a single short pass at a fixed point in the day instead of a running trickle of attention. Visionary-leaning readers already ask whether a message moves anything, so the useful half for them is the ask, aimed at the two threads generating the most noise.

The limits are real, and one of them cuts against everything above. Being copied in is how some people learn what is happening in teams they depend on, and cutting it off buys a quieter inbox at the price of finding out late. If you are new, or work across teams whose decisions land on you afterwards, keep the folder and read it, because the cost you are managing is interruption rather than information. Junior roles carry a second version of this, where being off a thread reads to somebody else as being out of the loop. That one is a conversation with your manager, not a mail rule.

No version of this works quietly. Every part of it involves telling somebody what you now do.

Start by counting. Go through yesterday, mark which messages named you in To and which only copied you, then pick the single sender or recurring thread behind the largest share of the second group. Ask that one person this week and set the filter for the rest. If you want the shortlist matched to how you work rather than to the average inbox, the working style self-check is a faster read than another month of sorting.

Frequently asked questions

How do you stop being cc'd on so many emails at work?

Ask the people who copy you most to leave you off one specific kind of thread, and name what you will follow instead so nothing looks dropped. A narrow request beats a general policy, because it changes a default rather than asking somebody to remember a rule about you. Filter what remains into a folder you read once a day. Ask first: the filter hides the volume, and only the ask removes it.

What should you do with emails where you are only in CC?

Ask one question of each: does this change what I do? Archive it when the answer is no, which for most copied mail it is. Being in CC means the sender decided somebody else has to act. Anything surviving that question is either a task, which belongs on your task list rather than in a mail folder, or a thread you need to follow. Read the folder in one scheduled pass instead of as the messages land.

Is it rude to ask someone to stop copying you in?

No, and the sender rarely knows the copy line carries any weight: six studies published in 2021 found that employees whose mail always carried the supervisor in copy felt trusted the least. That research looked at the supervisor case specifically, not at colleagues copying each other, so treat it as a reason the copy line is worth raising rather than a finding about your inbox. Everyday copying is mostly habit. Keep the request about the thread rather than the person, and name the alternative you will follow, since much of it is somebody making sure a thing does not get dropped.

Does filtering CC emails out of your inbox actually work?

It works on interruptions and not on volume: a rule stops copied mail landing in front of you, and it does not stop any of it arriving. That distinction matters here. The 2024 study behind this page found high email load predicted by communication mail received, not by mail processed, so a folder relocates the count rather than lowering it. Use the filter for the traffic you could not get switched off, after you have asked.