No specific laws identified for this ruling.
In an appeal from a judgment of the Court of Appeals reversing a jury verdict awarding over $2 billion in damages in favor of a software company against a competitor based on its claims for misappropriation of trade secrets under the Virginia Uniform Trade Secrets Act ("VUTSA"), Code § 59.1-336 et seq., the evidence presented at trial was sufficient to support the plaintiff's claim that the competitor misappropriated its trade secrets, and thus the Court of Appeals correctly concluded that the circuit court did not err by denying the competitor's motions to strike and set aside the verdict. However, the Court of Appeals correctly concluded that the circuit court erred by instructing the jury that the competitor bore any burden of proof regarding the plaintiff's damages claim and that the number of people with access to a purported trade secret is not relevant. The Court of Appeals also correctly determined that the circuit court abused its discretion in how it enforced its interpretation of the defendant's response to a particular interrogatory because certain information the defendant sought to introduce did not contradict that response and the circuit court's resolution effectively denied the defendant's ability to put on its damages defense; and erred in precluding the defendant from attempting to authenticate and possibly introduce as evidence relevant versions of its software at trial. The judgment of the Court of Appeals is affirmed, and the matter is remanded for further proceedings consistent with this opinion.
What Happened:
This case involved a dispute between two software companies, Appian Corporation and Pegasystems, over stolen trade secrets. Appian claimed that Pegasystems illegally took and used their confidential business information, which included valuable technical knowledge and processes. A jury originally awarded Appian over $2 billion in damages, but a higher court (Court of Appeals) overturned that massive verdict.
What the Court Decided:
The Virginia Supreme Court partially sided with both companies. The court agreed that there was enough evidence to prove Pegasystems did steal Appian's trade secrets, supporting that part of the original jury's decision. However, the court sent the case back to lower courts for further review, meaning the $2 billion damage award remains uncertain.
Why This Matters for Workers:
This case highlights the serious legal consequences of misusing confidential information from previous employers. Workers should understand that trade secrets are legally protected, and taking proprietary information when changing jobs can lead to costly lawsuits. Employees should be careful about what information they use from former employers and ensure they're not violating confidentiality agreements. Companies are willing to spend significant resources protecting their valuable business secrets.
This summary was generated to explain the ruling in plain English and is not legal advice.
The language of the Virginia wage theft statute, Code § 40.1-29, specifically lists wages and salaries, but it does not expressly apply to commissions, and its context does not support an interpretation that extends the statute's protections to commissions. Resting its contrary conclusion on the…
In an interlocutory appeal brought by medical staffing companies concerning a physician-plaintiff's claim against them under the Virginia Whistleblower Protection Act, Code § 40.1-27.3, the Court of Appeals erred in affirming the denial of their plea in bar to that claim because the alleged…
Court rulings like this one are useful, but every situation is different. Take 3 minutes to see which laws may protect you — it's free, private, and no account is required to start.
This ruling information is sourced from public court records via CourtListener.com. Case outcomes, claim types, and summaries are extracted using AI analysis and may be incomplete or inaccurate. It is provided for informational and educational purposes only and does not constitute legal advice.
See something wrong, or named in this ruling and want it corrected or redacted? Request a correction.