Tenth Circuit Upholds Trade Secret Dismissal, Reverses Damages Ru

Note: This article is for informational and editorial purposes only and is not legal advice.

In trade secret litigation, the word “secret” does not mean “I meant to keep it secret in my heart.” Courts tend to prefer more visible evidence: passwords, confidentiality labels, access controls, nondisclosure obligations, claw-back efforts, and a paper trail that says, in effect, “please do not treat this like office birthday cake.” That is the lesson at the center of Snyder v. Beam Technologies, Inc., a 2025 published decision from the U.S. Court of Appeals for the Tenth Circuit.

The case produced a split result. The Tenth Circuit affirmed summary judgment dismissing the plaintiff’s federal and Colorado trade secret claims because he failed to take reasonable measures to protect a broker list. At the same time, the court reversed a damages-related Rule 702 order because the district court went too far: it excluded not only an expert witness, but also blocked the plaintiff from presenting any evidence or fact witnesses on lost wages. In plain English, the trade secret claim stayed dismissed, but the damages door was not allowed to be slammed shut with the wrong procedural tool.

What Happened in Snyder v. Beam Technologies?

The dispute involved John Snyder, a former employee of Guardian Life Insurance Company who later joined Beam Technologies, Inc. While at Guardian, Snyder obtained a large national broker list. According to the court record, the list contained more than 40,000 insurance broker names and was downloaded from Guardian’s customer relationship management system into an Excel spreadsheet. Snyder later sent the list from his Guardian email account to his personal Hotmail account.

After joining Beam in 2018 as a Regional Director of Broker Success, Snyder created state-specific broker spreadsheets for Texas, Utah, and Colorado. The problem, legally speaking, was not just that he used the old list as a template. The problem was that he accidentally included the full national Guardian Broker List as a separate tab in those spreadsheets and sent them to Beam employees.

That accidental disclosure became the engine of the case. Snyder claimed Beam induced him to join the company and disclose the broker information, including alleged promises to pay him “off the books” for the spreadsheets. Beam denied liability and argued that Snyder did not own the list, did not protect it as a trade secret, and voluntarily sent it to Beam personnel.

The Core Legal Issue: Trade Secrets Need Real Protection

Trade secret law rewards secrecy, but not secrecy by wishful thinking. Under the federal Defend Trade Secrets Act, a plaintiff must show the existence of a trade secret, misappropriation, and a connection to interstate or foreign commerce. The federal statute also requires that the owner take reasonable measures to keep the information secret and that the information derive independent economic value from not being generally known.

Colorado’s Uniform Trade Secrets Act follows a similar idea. The Colorado definition focuses on information that is secret and valuable, and it requires measures to prevent the secret from becoming available to people other than those selected to access it for limited purposes. That phrase “limited purposes” matters. If a spreadsheet is passed around like a fantasy football draft board, it becomes much harder to persuade a court that it was treated as protected business treasure.

Ownership vs. Possession: The Tenth Circuit’s Important Distinction

One of the most useful parts of the decision is the court’s discussion of ownership and possession. The district court granted summary judgment on both trade secret claims because Snyder had not shown he owned the broker list. The Tenth Circuit agreed that ownership matters under the federal Defend Trade Secrets Act because the DTSA says that an “owner” of a misappropriated trade secret may bring a civil action.

But the court saw the Colorado statute differently. Under Colorado law, the first element of a trade secret misappropriation claim may be possession of a valid trade secret, not necessarily ownership. That means a lawful possessor may have standing under Colorado law even when ownership is disputed. For businesses, employees, and litigators, this is a big reminder: federal and state trade secret claims often travel together, but they are not identical twins wearing matching suits.

Still, this distinction did not save Snyder’s trade secret claims. Even though the Tenth Circuit declined to affirm the Colorado claim based solely on lack of ownership, it affirmed dismissal on another ground: Snyder did not take reasonable measures to maintain secrecy.

Why the Trade Secret Claim Failed

The court pointed to several practical failures. Snyder did not mark the spreadsheets as confidential. He did not password-protect the documents. He did not limit Beam employees’ access. He did not require the recipients to sign confidentiality agreements for the lists. He did not tell Beam that the documents were confidential or trade secrets. After learning that the full broker list had been distributed, he did not object, claw back the materials, or demand their return.

In other words, the list may have been valuable, but Snyder’s handling of it was not consistent with trade secret protection. A business list can be a trade secret, but only when the facts show that the claimant treated it like one. A list kept on a laptop is not automatically protected. A spreadsheet in an email attachment is not automatically protected. A customer list becomes legally stronger when the company or person claiming protection can show a system of care around it.

The Court’s Practical Message

The Tenth Circuit’s message was direct: “reasonable measures” require more than normal business precautions. A party does not need a fortress, a moat, and a dragon named Compliance. But it does need meaningful steps that match the value and sensitivity of the information. That can include confidentiality notices, restricted access, secure storage, password protection, internal policies, employee training, nondisclosure agreements, and quick corrective action after accidental disclosure.

The Rule 702 Damages Ruling: Why the Tenth Circuit Reversed

The second major issue involved damages evidence. The district court excluded Snyder’s damages expert under Federal Rule of Evidence 702. Rule 702 governs expert testimony, including whether an expert is qualified and whether the testimony is reliable and helpful to the factfinder.

The Tenth Circuit did not object to the idea that expert testimony can be excluded when it fails Rule 702. The problem was scope. The district court’s order did more than exclude Snyder’s expert. It also precluded Snyder from offering any evidence or fact witnesses on lost wages. That move, the appellate court explained, operated like a summary judgment ruling on damages, but without the procedural protections that come with summary judgment.

That is a procedural no-no. Summary judgment requires notice and a fair chance for the nonmoving party to present evidence. Rule 702 is about expert admissibility; it is not a shortcut for disposing of a damages theory altogether. The Tenth Circuit therefore reversed the Rule 702 order and remanded for further proceedings on that issue.

Why This Case Matters for Employers

For employers, Snyder v. Beam Technologies is a reminder that trade secret protection is built before litigation, not after it. The best time to protect a customer list is before someone emails it to ten coworkers with no restrictions. The second-best time is immediately after the mistake, when the company can send notices, request deletion or return, preserve evidence, and document corrective action.

Employers should treat sensitive customer data, pricing models, sales strategies, source code, formulas, and vendor lists with a consistent protection program. That program should not live only in a dusty employee handbook last updated when flip phones were aspirational technology. It should be visible in onboarding, contracts, file permissions, IT controls, exit interviews, and daily business practices.

Practical Employer Checklist

Companies should classify confidential information, label sensitive files, restrict access based on job need, use secure storage systems, require NDAs where appropriate, and train employees on what can and cannot be shared. They should also create incident-response procedures for accidental disclosures. A fast claw-back request may not solve everything, but silence after disclosure can look like consent, carelessness, or both.

Why This Case Matters for Employees

Employees and executives should also pay attention. Taking a customer list from a prior employer, even for “reference,” can create ownership, confidentiality, and misappropriation issues. The fact that someone helped build a list does not always mean they own it. A salesperson may know customers, relationships, and industry patterns, but downloading a CRM database and sending it to a personal email account is a different animal.

Before bringing business information to a new employer, employees should review employment agreements, confidentiality policies, and applicable law. The safer path is usually to rely on general experience, memory, and publicly available information rather than importing old spreadsheets. In trade secret law, “I was just being efficient” is not the legal equivalent of a magic shield.

Customer Lists Can Be Trade Secrets, But Not Always

Customer lists are among the most common assets in trade secret lawsuits. A list may qualify when it contains nonpublic information, such as purchasing history, pricing preferences, contacts, renewal dates, decision-makers, or strategic notes that competitors could not easily compile. But a list of names that is publicly available, broadly shared, or poorly guarded may not survive judicial scrutiny.

The key question is not simply whether the information is useful. Many things are useful. Coffee is useful. A stapler is useful. That does not make them trade secrets. The question is whether the information has economic value because it is secret and whether the claimant took reasonable steps to preserve that secrecy.

The Bigger Litigation Lesson: Procedure Matters

The reversal of the damages ruling is just as important as the trade secret holding. Courts have different procedural tools for different tasks. Rule 702 is a gatekeeping rule for expert testimony. Summary judgment is a merits tool for deciding whether a claim or issue can proceed based on the evidence. Mixing the two can deprive a party of notice and an opportunity to respond.

For trial lawyers, the lesson is clear: when challenging an expert, be precise about whether the target is the expert’s opinion or the entire damages claim. For judges, the opinion reinforces the need to use the correct procedural framework. For litigants, it shows why preserving alternative evidence matters. Even if an expert is excluded, fact witnesses, documents, pay records, and other non-expert proof may still be relevant.

How Businesses Can Avoid the Snyder Problem

The easiest way to lose a trade secret case is to treat confidential information casually and then ask a court to treat it reverently. A better strategy is to build a record of protection long before anything goes wrong.

1. Label Important Files Clearly

Documents containing customer lists, pricing data, strategic plans, and proprietary methods should be labeled “Confidential” or “Trade Secret” where appropriate. Labels are not conclusive, but they help show intent and put recipients on notice.

2. Restrict Access

Not every employee needs access to every sensitive file. Role-based permissions are one of the most practical ways to demonstrate reasonable secrecy measures.

3. Use Passwords and Secure Systems

Password protection alone may not be enough, but the absence of password protection can be damaging. Sensitive spreadsheets should not float around unprotected inboxes like digital confetti.

4. Train Employees

Employees should understand what information the company considers confidential and what to do if they accidentally send it to the wrong person. Training turns policy from decorative wallpaper into actual business practice.

5. Respond Quickly to Mistakes

If confidential information is accidentally disclosed, act quickly. Request deletion or return, document the mistake, notify legal counsel, preserve evidence, and reinforce confidentiality obligations.

Analysis: The Tenth Circuit’s Balanced Approach

The Tenth Circuit’s decision is balanced because it separates substantive trade secret weakness from procedural overreach. On the trade secret side, the court refused to rescue a claimant who failed to guard the alleged secret. On the damages side, it refused to let Rule 702 become a backdoor summary judgment device.

That balance is healthy for litigation. Trade secret law should protect businesses that make serious efforts to protect valuable information. It should not reward carelessness. At the same time, procedural rules should not be stretched so far that parties lose claims or damages theories without the notice and protections required by law.

Experiences and Practical Lessons from Similar Trade Secret Disputes

In real-world business disputes, the facts often look much messier than the polished version that appears in a complaint. A sales director saves an old contact list because “everyone does it.” A manager exports CRM data before switching companies because “it is just my book of business.” A startup founder shares a pitch deck with potential partners but forgets to mark it confidential. Six months later, everyone is in litigation, and the spreadsheet that once seemed harmless has become Exhibit A with a bad haircut.

One practical experience from trade secret counseling is that companies frequently overestimate how protected their information is. They assume that because a file is important, the law will treat it as secret. But courts look for behavior, not vibes. Did the company restrict access? Did it train employees? Did it use NDAs? Did it label files? Did it respond when information was exposed? These small acts become big evidence.

Another common experience is that businesses wait too long to clean up data practices. A company may have a beautiful confidentiality policy, but if employees routinely email sensitive lists to personal accounts, store files on unsecured drives, or share passwords in chat messages, the policy may look more ceremonial than operational. Trade secret protection works best when legal, HR, sales, and IT teams coordinate. The legal team writes the rules. IT builds the gates. Managers enforce the habits. Employees learn where not to click, copy, upload, or casually “just send it.”

The Snyder case also offers a useful lesson about accidental disclosure. Mistakes happen. Someone attaches the wrong file. Someone forgets that a hidden spreadsheet tab contains the crown jewels. Someone replies-all to an email chain that suddenly includes an outside consultant. The mistake itself may not always destroy trade secret protection, but the response matters. A quick claw-back demand, deletion confirmation, reminder of confidentiality obligations, and internal incident report can help show that the owner still treated the information as secret. Doing nothing is rarely charming in court.

For employees, the experience-based takeaway is equally simple: do not bring old employer data into a new workplace unless counsel has cleared it. Your personal relationships, general industry knowledge, and professional skills usually travel with you. Your former employer’s CRM export, pricing formulas, nonpublic client notes, and internal strategy files usually do not. A new employer should also avoid accepting questionable files from incoming hires. “Where did this come from?” is not rude; it is risk management wearing sensible shoes.

Finally, the damages ruling teaches litigators to be careful with procedural tools. Expert challenges are powerful, especially after modern Rule 702 amendments, but they are not universal remote controls for every evidentiary problem. If a party wants to eliminate a damages theory entirely, summary judgment is usually the cleaner vehicle. If the issue is expert reliability, Rule 702 is the correct lane. Switching lanes without signaling can lead to reversal, and appellate courts are not known for handing out participation trophies.

Conclusion

Snyder v. Beam Technologies is a sharp reminder that trade secret protection depends on conduct. A customer list may be valuable, but value alone is not enough. The party claiming protection must show reasonable measures to maintain secrecy. The Tenth Circuit affirmed the dismissal of Snyder’s trade secret claims because the record showed no meaningful safeguards around the broker list, especially after it was shared with Beam employees without labels, restrictions, passwords, or claw-back efforts.

At the same time, the court reversed the damages order because Rule 702 should not be used to eliminate all damages evidence or fact witnesses without the protections of summary judgment. The result is a practical, business-friendly, procedure-conscious ruling: protect secrets like secrets, challenge experts like experts, and do not ask one rule to do another rule’s job.