{"id":517,"date":"2026-07-07T12:00:00","date_gmt":"2026-07-07T16:00:00","guid":{"rendered":"https:\/\/ipmanagement.harnessip.com\/?p=517"},"modified":"2026-07-11T20:25:07","modified_gmt":"2026-07-12T00:25:07","slug":"inability-to-identify-trade-secrets-dooms-misappropriation-claim","status":"publish","type":"post","link":"https:\/\/ipmanagement.harnessip.com\/?p=517","title":{"rendered":"Inability to Identify Trade Secrets Dooms Misappropriation Claim"},"content":{"rendered":"\n<p>In <em>Wilbur-Ellis Co. v. Gompert<\/em>, No. 25-1577 (8th Cir. July 7, 2026), the Eighth Circuit affirmed the district court&#8217;s grant of summary judgment in favor of Wilbur-Ellis&#8217;s former employees, concluding that Wilbur-Ellis failed to adequately identify its trade secrets.<\/p>\n\n\n\n<p>Wilbur-Ellis must have felt it had a good case. Several  of its employees quit in August 2024, and within three days they were working for a competitor while still drawing their salaries from Wilbur-Ellis. A total of eleven employees left.  At least two of the departing employees downloaded and accessed files stored on Wilber-Ellis devices during their last weeks of employment.  The departing employees reset their devices before returning them to Wilbur-Ellis.  Wilbur-Ellis acted without delay, suing two of the employees four days after they left the company alleging breach of the duty of loyalty, misappropriation of trade secrets under the federal Defend Trade Secrets Act (DTSA) and the Nebraska Trade Secrets Act (NTSA), and tortious interference with its business relationships, and adding two more employees within two weeks.<\/p>\n\n\n\n<p>When ordered to disclose with specificity the trade secrets that were misappropriated, Wilbur-Ellis produced a six-page document that described its alleged trade secrets with phrases like \u201c[d]ocuments and information regarding Wilbur-Ellis\u2019s business and market strategy,\u201d \u201c[d]ocuments and information relating to Wilbur-Ellis\u2019s customers,\u201d and \u201cnonpublic customer proposals, pricing and rebate data.\u201d<\/p>\n\n\n\n<p>The Eighth Circuit agreed with the district court&#8217;s observation that that Wilbur-Ellis \u201cpaint[ed] with a broad brush, never clearly and adequately identifying the \u2018trade secrets\u2019 at issue, let alone how they were used or misused or the damages reasonably attributable to each defendant.\u201d The district court also stated that \u201cWilbur-Ellis\u2019s reliance on broad terms, general descriptions, and repeated, non-specific references . . . do not suffice. Without more, much of the information it designates as trade secrets also appears to be public or unprotected.\u201d  The Eighth Circuit said that because we agree with the district court\u2019s finding that Wilbur-Ellis \u201cnever clearly and adequately identif[ied] the \u2018trade secrets\u2019 at issue, let alone how they were used or misused,\u201d we hold that it did not err in granting summary judgment on Wilbur-Ellis\u2019s trade secrets claims.<\/p>\n\n\n\n<p>Eliis-Wilbur certainly had trade secrets, and they very well may have been misappropriated.  But, like many trade secret owners they simply were not prepared for the level of detail neccessary to adequately identify their trade secrets.  Here is a ten-point plan for being prepared to successfully make a trade secret claim:<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">1. Maintain a Formal Trade Secret Inventory<\/h1>\n\n\n\n<p>The single most valuable thing a company can do is maintain a living trade secret inventory.  The inventory should identify each trade secret, rather than merely categories of confidential information.  For example, instead of &#8220;manufacturing process&#8221; the inventory should identify &#8220;Multi-stage catalytized reduction process for reducing sulfur impurities below 5 ppm using catalyst sequence A-B-C, operating temperatures of 180-195,  . . .&#8221;.<\/p>\n\n\n\n<p>The inventory should include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Name of trade secret<\/li>\n\n\n\n<li>Description<\/li>\n\n\n\n<li>Business purpose<\/li>\n\n\n\n<li>Why it is valuable<\/li>\n\n\n\n<li>Why competitors do not know it<\/li>\n\n\n\n<li>Persons with access<\/li>\n\n\n\n<li>Documents containing it<\/li>\n\n\n\n<li>Date created<\/li>\n\n\n\n<li>Updates<\/li>\n\n\n\n<li>Owner\/business unit<\/li>\n\n\n\n<li>Security measures<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">2. Divide Trade Secrets into Individual Assets<\/h2>\n\n\n\n<p>Many companies identify trade secrets too broadly.  Courts dislike descriptions like: &#8220;Our customer relationships.&#8221;  Instead identify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>pricing model<\/li>\n\n\n\n<li>discount formulas<\/li>\n\n\n\n<li>customer purchasing histories<\/li>\n\n\n\n<li>purchasing forecasts<\/li>\n\n\n\n<li>customer-specific technical requirements<\/li>\n\n\n\n<li>supplier cost information<\/li>\n\n\n\n<li>margin calculations<\/li>\n\n\n\n<li>manufacturing tolerances<\/li>\n\n\n\n<li>production scheduling algorithms<\/li>\n<\/ul>\n\n\n\n<p>Each may be a separate trade secret.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Map Trade Secrets to Documents<\/h2>\n\n\n\n<p>Every trade secret should be tied to specific documents.  For example, Trade Secret 1 is reflected in:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Engineering Specification ENG-12<\/li>\n\n\n\n<li>CAD Assembly 3.1<\/li>\n\n\n\n<li>Laboratory Notebook 5. p. 45<\/li>\n\n\n\n<li>Git repository revision<\/li>\n\n\n\n<li>Manufacturing SOP 3<\/li>\n<\/ul>\n\n\n\n<p>This later makes identification dramatically faster and easier.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Classify Information<\/h2>\n\n\n\n<p>Implement levels such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Public<\/li>\n\n\n\n<li>Internal<\/li>\n\n\n\n<li>Confidential<\/li>\n\n\n\n<li>Highly Confidential<\/li>\n\n\n\n<li>Trade Secret<\/li>\n<\/ul>\n\n\n\n<p>Employees should know what qualifies as merely confidential and what qualifies as a trade secret.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5. Mark Trade Secret Documents<\/h2>\n\n\n\n<p>Whenever practical, documents should be marked &#8220;CONFIDENTIAL&#8221; or CONFIDENTIAL &#8211; TRADE SECRET.&#8221;  Although not legally required, consistent marking supports the argument that reasonable secrecy measures were employed.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6. Record Why Information is Secret<\/h2>\n\n\n\n<p>For each trade secret document, record:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>not publicly known<\/li>\n\n\n\n<li>independently developed over years<\/li>\n\n\n\n<li>cost to develop<\/li>\n\n\n\n<li>competitive advantage<\/li>\n\n\n\n<li>inability to reverse engineer<\/li>\n\n\n\n<li>limited employee access<\/li>\n<\/ul>\n\n\n\n<p>Later these become litigation evidence.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7. Maintain Development Histories<\/h2>\n\n\n\n<p>Keep (securely):<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>laboratory notebooks<\/li>\n\n\n\n<li>engineering notebooks<\/li>\n\n\n\n<li>Git history<\/li>\n\n\n\n<li>version histories<\/li>\n\n\n\n<li>project timelines<\/li>\n\n\n\n<li>design reviews<\/li>\n\n\n\n<li>invention disclosures<\/li>\n<\/ul>\n\n\n\n<p>These establish originality and value.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">8. Document Security Measures<\/h2>\n\n\n\n<p>Maintain records showing:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>NDAs<\/li>\n\n\n\n<li>employee confidentiality agreements<\/li>\n\n\n\n<li>vendor agreements<\/li>\n\n\n\n<li>password restrictions<\/li>\n\n\n\n<li>VPN controls<\/li>\n\n\n\n<li>encryption<\/li>\n\n\n\n<li>badge access<\/li>\n\n\n\n<li>visitor logs<\/li>\n\n\n\n<li>clean desk policies<\/li>\n\n\n\n<li>information security policies<\/li>\n\n\n\n<li>annual employee training<\/li>\n<\/ul>\n\n\n\n<p>Reasonable secrecy measures are an essential element of a trade secret claim under both the federal and most state trade secret statutes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9. Conduct Regular Trade Secret Audits<\/h2>\n\n\n\n<p>Periodically ask: &#8220;What information would hurt us if our largest competitor obtained it tomorrow?&#8221; and update the trade secret inventory.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">10. Prepare Employee Departure Files<\/h2>\n\n\n\n<p>For employees with significant confidential access, maintain records of:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>systems accessed<\/li>\n\n\n\n<li>projects<\/li>\n\n\n\n<li>customer responsibilities<\/li>\n\n\n\n<li>confidential files used<\/li>\n\n\n\n<li>inventions worked on<\/li>\n\n\n\n<li>exit interview certifications<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>In Wilbur-Ellis Co. v. Gompert, No. 25-1577 (8th Cir. July 7, 2026), the Eighth Circuit affirmed the district court&#8217;s grant of summary judgment in favor of Wilbur-Ellis&#8217;s former employees, concluding that Wilbur-Ellis failed to adequately identify its trade secrets. Wilbur-Ellis &hellip; <a href=\"https:\/\/ipmanagement.harnessip.com\/?p=517\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,11],"tags":[],"class_list":["post-517","post","type-post","status-publish","format-standard","hentry","category-employees","category-trade-secrets"],"_links":{"self":[{"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/517","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=517"}],"version-history":[{"count":1,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/517\/revisions"}],"predecessor-version":[{"id":518,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/517\/revisions\/518"}],"wp:attachment":[{"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=517"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=517"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=517"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}