Over-labeling documents as privileged can backfire in discovery. Five lessons for in-house teams from this week's Meta privilege re-review order.

Every legal department has a colleague who treats "Privileged & Confidential" like an email signature. Every message, every slide, every lunch order. It feels protective. It is not.
This week gave us the most memorable illustration yet. Law360 reported on September 22 that a California federal judge ordered Meta to re-review privilege designations on 300 documents in the social media addiction litigation. The plaintiffs' lawyers had argued there was a "culture of privilege abuse," and their exhibit A was, of all things, a baseball cap. According to the plaintiffs' filing, as covered by the New York Post on September 25, members of Instagram's Teen Accounts team had hats embroidered with "a/c priv," the shorthand that shows up on privilege logs. The plaintiffs also claimed Instagram legal signed off on the merch. Meta declined to comment, and none of these allegations has been decided on the merits.
We are not here to pile on one company. We are here because almost every in-house team has some version of this habit, even if it never made it onto a hat.
Privilege protects communications made to get or give legal advice. A label is evidence of intent. It is not a force field. When a label shows up on everything, it stops being evidence of anything, and it can start to look like evidence of something worse.
Teach employees the question that matters: Am I asking a lawyer for legal advice? If the honest answer is "no, I'm updating the project tracker," the label won't save it. Put a one-paragraph explainer in your intake form and your onboarding deck.
Copying legal on business chatter is the office equivalent of wearing a seatbelt in the parking lot. Ask business teams to open a request through your intake channel when they actually need advice, so the legal question lives in its own clean record.
Look for email footers, slide masters, and document templates that stamp "privileged" automatically. Those are privilege-log time bombs. Remove the auto-labels and keep a short list of when a label is appropriate.
The time to decide how you'll review for privilege is not the week a court sets a deadline. Modern eDiscovery and early case assessment tools can flag likely-privileged material, group near-duplicates, and keep consistent coding decisions across reviewers. Pair them with good legal hold management so you know what you're holding and why.
Jokes, merch, and Slack emojis about privilege feel harmless. In discovery, they're exhibits. If your team has an inside joke about "just slap a priv label on it," retire it this quarter.
Privilege is a legal conclusion, not a font. The fewer places it appears by default, the more weight it carries when it really counts.
Grab a random sample of 25 emails your department labeled privileged in the last six months. For each one, ask: was legal advice sought or given? If fewer than 20 pass, you've found your next training topic. If fewer than 10 pass, you've found your next budget line.
Nobody wants to be the case study in someone else's blog post. The good news is that the fix is mostly habits, a few template changes, and a review process that treats privilege as a decision instead of a decoration.
This article is general information, not legal advice.