← All posts
Thought Leadership

Anatomy of a USD 787.5M settlement: the private messages that became the case

July 2, 2026 · 4 min read

A US cable-news network paid USD 787.5M to settle a defamation case. The evidence that decided it was not what aired. It was what the hosts and executives wrote to each other privately while the broadcasts continued. In one internal message a host said, about an on-air guest’s claim, “She is lying by the way. I caught her.” The network kept airing the claim anyway.

That is the whole anatomy of the case in two lines. The public statements were the alleged defamation. The private messages proved the speakers did not believe them. In a defamation claim, that internal contradiction is the most valuable evidence a plaintiff can find, because it speaks directly to state of mind.

Why internal messages become the case

Internal chat and email feel like backstage. They are written quickly, candidly, often with sarcasm, by people who assume the audience is a colleague. Three properties turn that candor into liability.

First, they are candid. People write things internally they would never put in a public statement, which is exactly what makes them persuasive to a court: they read as what the person actually thought.

Second, they are preserved and discoverable. Modern archiving captures every message and produces it on demand. The same recordkeeping that satisfies the regulator hands the plaintiff a complete, timestamped record.

Third, they reveal state of mind. Many of the most expensive standards in law turn on what someone knew or intended: actual malice in defamation, scienter in securities fraud, knowledge in many regulatory matters. A private “we know this is false” is direct proof of the element the plaintiff has to establish.

The five internal lines that become exhibits

Across cases, the damaging internal messages fall into a small number of patterns. This is the set worth training people to recognize before they write.

Pattern What it looks like Why it is dangerous
Admission of knowledge “We know this is not true” / “she is lying” Proves the falsity element directly
Admission of intent “Let’s run it anyway, the numbers are good” Shows willfulness or recklessness
Candid disparagement “Their product is a joke and unsafe” Becomes the defamation or the conduct issue
Secrecy request “Keep this between us for now” Reads as concealment or consciousness of guilt
Sarcasm read literally “Designed by clowns, I basically lied to the regulators” A joke in chat becomes a sworn-evidence quote

The last row is the trap people underestimate. Humor and venting do not survive the transition to a courtroom. The line is read flat, by a jury, years later.

Where a pre-send check fits

Almost none of these messages were written by a person plotting fraud. They were written by careful professionals venting in a channel they assumed was private. That is the gap a pre-send check closes. As the line is typed, it is surfaced (“keep this between us”, “she is lying”, an admission of wrongdoing) at the only moment when deleting it is free.

A pre-send check will not stop a determined bad actor who wants to evade it, and it is not meant to. The archive remains the system of record for that. What it changes is the volume of candid, careless, exhibit-grade lines that reach the record in the first place. The two work together: the archive captured these messages, which is how they became evidence, and a pre-send check is what would have caught them before they were ever sent. Compliance teams can see how that evidence layer works without storing message content or naming individuals.

The takeaway

Treat internal chat as a future exhibit, because that is what it is. Identify your highest-exposure channels (executive email, internal chat, anything touching a live dispute or a regulator) and look honestly at the candor in them. The most expensive sentence in a case is usually one someone wrote in thirty seconds, certain no one outside the room would ever read it.

See how VerbaPulse flags risk before an email is sent, right inside Gmail and Outlook.

See VerbaPulse in action →
← Pre-send vs post-send compliance: where each one actually catches the risk