<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Kang Haggerty News</title>
	<atom:link href="https://www.khflaw.com/news/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.khflaw.com/news/</link>
	<description>Published By Kang Haggerty LLC</description>
	<lastBuildDate>Wed, 17 Jun 2026 19:14:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>
	<item>
		<title>Legal Intelligencer: Metadata Attorneys Are Not Asking for (but Should Be)</title>
		<link>https://www.khflaw.com/news/metadata-attorneys-are-not-asking-for-but-should-be/</link>
		
		<dc:creator><![CDATA[Kelly Lavelle]]></dc:creator>
		<pubDate>Wed, 17 Jun 2026 19:14:04 +0000</pubDate>
				<category><![CDATA[Publications]]></category>
		<category><![CDATA[ediscovery]]></category>
		<category><![CDATA[Legal Intelligencer]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7338</guid>

					<description><![CDATA[Metadata can reveal information about a document&#8217;s origin, authorship, transmission, modification, and use that may not be apparent from the document itself. This broader understanding of metadata illustrates why limiting requests to a handful of standard load-file fields may overlook metadata that is far more significant to the claims and defenses at issue. In the [&#8230;]]]></description>
										<content:encoded><![CDATA[<div class="mb-4">
<div class="article-font-size">
<p><em>Metadata can reveal information about a document&#8217;s origin, authorship, transmission, modification, and use that may not be apparent from the document itself. This broader understanding of metadata illustrates why limiting requests to a handful of standard load-file fields may overlook metadata that is far more significant to the claims and defenses at issue.</em></p>
<p>In the June 11, 2026 edition of <a href="https://www.law.com/thelegalintelligencer">The Legal Intelligencer</a>, Kelly Lavelle writes, &#8220;<a href="https://www.law.com/thelegalintelligencer/2026/06/11/metadata-attorneys-are-not-asking-for-but-should-be/">Metadata Attorneys Are Not Asking for (but Should Be)</a>.&#8221;<span id="more-7338"></span>Most attorneys recognize the importance of metadata and routinely request standard fields such as creation dates, modification dates, authors and email transmission details. But those fields are not always the metadata that matters most. In a wrongful termination case, for example, counsel may request an employee’s personnel file and metadata showing when a disciplinary memo was created.</p>
<div class="mb-4">
<div class="article-font-size">
<p>The document may be produced with those standard fields, yet the more important evidence could be the version history, which might show that the memo was substantially revised after the employee complained of discrimination.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Likewise, in a trade secret case, counsel may obtain emails and their metadata but fail to request audit logs showing who downloaded files before leaving the company. The strongest evidence may be in those logs, but it remains undiscovered because no one asked for it. The real issue is often not whether metadata was requested, but whether the right metadata was requested.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Part of the problem is that metadata is often discussed as though it consists solely of creation dates, modification dates, and author information. In reality, metadata encompasses a much broader range of information about a document&#8217;s history, characteristics and use. Electronic files may contain hundreds or even thousands of metadata fields. For example, email metadata can include information regarding transmission, receipt, forwarding, bcc recipients, and address-book data, while word-processing documents may contain edit histories, comments, formatting information, and other embedded data not visible on the face of the document.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Metadata can reveal information about a document&#8217;s origin, authorship, transmission, modification, and use that may not be apparent from the document itself. This broader understanding of metadata illustrates why limiting requests to a handful of standard load-file fields may overlook metadata that is far more significant to the claims and defenses at issue.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>As organizations increasingly conduct business through cloud-based collaboration platforms, messaging applications, and enterprise systems, some of the most significant metadata may reside in sources that rarely appear in standard discovery requests, including version histories, audit logs, access records, edit histories, and communication metadata.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Collaboration platforms<b> </b>such as<b> </b>Microsoft SharePoint, Google Workspace and similar systems illustrate this point.<b> </b>When a document is produced in litigation, counsel often receives only the final version of the document. What is frequently missing, however, is metadata showing how the document evolved over time.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Prior versions may reveal significant edits, identify additional custodians, establish when information was added or removed, and provide insight into the decision-making process. In cases involving contract negotiations, employment decisions, or internal investigations, version histories may tell a far different story than the final document ultimately produced.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Version histories can be particularly important because they may be lost when information is exported, converted, or produced in static formats. By the time discovery begins, the metadata that reveals how a document evolved may already be gone unless counsel identifies and preserves it early in the case.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Comments and tracked changes present a similar issue. Although attorneys routinely request final documents, they often fail to specifically address embedded comments, suggestions, and revision histories. These materials can identify individuals involved in drafting, reveal concerns later omitted from the final document, and provide contemporaneous evidence regarding a party&#8217;s knowledge or intent. Once documents are exported or converted for production, much of this information may be lost unless it is specifically preserved and requested.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Another frequently overlooked source of metadata is audit log data. Many organizations maintain logs showing when users accessed documents, modified files, downloaded information, or changed permissions. These logs can become particularly important when claims involve alleged document destruction, misuse of confidential information, trade secret disputes, or questions regarding the authenticity of evidence.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>In some cases, audit logs provide the only reliable record showing who interacted with a document and when those interactions occurred. They may also identify individuals who never appear as authors, recipients, or custodians in the documents themselves but nevertheless played a significant role in the underlying events.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Communication platforms present a similar issue. Messages from Microsoft Teams, Slack, and similar applications are frequently produced as screenshots, PDFs, or other static images. While those productions may capture the visible content of a communication, they often omit metadata that may show whether a message was edited or deleted, identify all participants in a conversation, establish the precise timing of communications, or place individual messages within the context of a larger conversation thread. As a result, a screenshot may reveal what was ultimately said while hiding important information about the circumstances surrounding the communication.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Metadata can also reveal relationships that are not apparent from reviewing individual documents in isolation. Email and messaging metadata may identify communication patterns among key actors, reveal previously unknown participants in a discussion, and help reconstruct how information moved through an organization.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>In some matters, understanding who communicated with whom, when, and how frequently may be as important as the content of the communications themselves. Such information can assist counsel in identifying additional custodians, evaluating witness credibility, and developing more targeted discovery strategies.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>As organizations continue to rely upon cloud-based collaboration tools, the gap between the information that attorneys request and the information that actually exists will continue to grow. The Sedona Principles likewise recognize that the &#8220;special characteristics&#8221; of ESI, including metadata and other non-apparent information, may be pertinent to the form in which ESI should be preserved and produced. See &#8220;The Sedona Principles, Third Edition: Best Practices, Recommendations &amp; Principles for Addressing Electronic Document Production,&#8221; Principle 12, Comment 12.a, 19 Sedona Conf. J. 169 (2018).</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>For that reason, counsel should consider metadata issues at the outset of a matter and identify the metadata most likely to prove or disprove the claims at issue, before relevant information is altered, lost, or produced in a form that no longer contains the information necessary to tell the complete story.<b> </b>In many cases, standard metadata fields will be sufficient. In others, version histories, audit logs, collaboration platform metadata, and document revision records may contain some of the most significant evidence in the case.</p>
</div>
</div>
<p><b>Kelly A. Lavelle</b> <i>is Senior Counsel at Kang Haggerty. She focuses on e-discovery and information management, from preservation and collection to review and production of large volumes of electronically stored information. Contact her at <a href="mailto:klavelle@kanghaggerty.com">klavelle@kanghaggerty.com</a>.</i></p>
<p><strong><em>Reprinted with permission from the June 11, 2026 edition of “The Legal Intelligencer” © 2026 ALM Global, LLC. All rights reserved. Further duplication without permission is prohibited. Request academic re-use from <a class="text-blue-800 underline hover:no-underline" href="https://www.copyright.com/">www.copyright.com.</a> All other uses, submit a request to <a class="text-blue-800 underline hover:no-underline" href="mailto: asset-and-logo-licensing@alm.com">asset-and-logo-licensing@alm.com.</a> For more information visit <a class="text-blue-800 underline hover:no-underline" href="https://www.law.com/asset-and-logo-licensing/">Asset &amp; Logo Licensing</a>.</em></strong></p>
</div>
</div>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7338</post-id>	</item>
		<item>
		<title>Chambers USA Recognizes Kang Haggerty’s Litigation Practice and Two Attorneys in 2026 Edition</title>
		<link>https://www.khflaw.com/news/chambers-usa-recognizes-kang-haggertys-litigation-practice-and-two-attorneys-in-2026-edition/</link>
		
		<dc:creator><![CDATA[Kang Haggerty LLC]]></dc:creator>
		<pubDate>Mon, 08 Jun 2026 03:44:20 +0000</pubDate>
				<category><![CDATA[Firm News]]></category>
		<category><![CDATA[Chambers USA]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7336</guid>

					<description><![CDATA[PHILADELPHIA, PA — Kang Haggerty LLC is pleased to announce that the firm has been recognized in the 2026 edition of Chambers USA, the world’s leading legal data and analytics provider, earning its first-ever departmental ranking alongside two ranked attorneys. The firm’s Litigation: Mainly Plaintiffs practice debuts in Band 2 for Pennsylvania, and Managing Member [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><strong>PHILADELPHIA, PA</strong> — Kang Haggerty LLC is pleased to announce that the firm has been recognized in the 2026 edition of <em>Chambers USA</em>, the world’s leading legal data and analytics provider, earning its first-ever departmental ranking alongside two ranked attorneys. The firm’s Litigation: Mainly Plaintiffs practice debuts in Band 2 for Pennsylvania, and Managing Member Edward T. Kang advances to Band 1, while Of Counsel Henry J. Donner continues his longstanding recognition as a Senior Statesperson for Construction.</p>
<h1>Practice Area Ranking</h1>
<h2>Litigation: Mainly Plaintiffs (Pennsylvania) — Band 2</h2>
<div class="read_more_link"><a href="https://www.khflaw.com/news/chambers-usa-recognizes-kang-haggertys-litigation-practice-and-two-attorneys-in-2026-edition/"  title="Continue Reading Chambers USA Recognizes Kang Haggerty’s Litigation Practice and Two Attorneys in 2026 Edition" class="more-link">Continue reading ›</a></div>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7336</post-id>	</item>
		<item>
		<title>Kang Haggerty Sponsors AAPI Heritage Month Gala Hosted by the Asian American Business Alliance of Greater Philadelphia</title>
		<link>https://www.khflaw.com/news/kang-haggerty-sponsors-aapi-heritage-month-gala-hosted-by-the-asian-american-business-alliance-of-greater-philadelphia/</link>
		
		<dc:creator><![CDATA[Kang Haggerty LLC]]></dc:creator>
		<pubDate>Mon, 25 May 2026 17:42:40 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[AABAGP]]></category>
		<category><![CDATA[Diversity]]></category>
		<category><![CDATA[Philadelphia]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7327</guid>

					<description><![CDATA[Kang Haggerty was proud to sponsor the Asian American Business Alliance of Greater Philadelphia’s (AABAGP) AAPI Heritage Month Gala, a landmark celebration of Asian American and Pacific Islander leadership, entrepreneurship, and community impact across the region. The event brought together more than 420 attendees, including business and community leaders representing the full breadth of the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Kang Haggerty was proud to sponsor the Asian American Business Alliance of Greater Philadelphia’s (AABAGP) AAPI Heritage Month Gala, a landmark celebration of Asian American and Pacific Islander leadership, entrepreneurship, and community impact across the region. The event brought together more than 420 attendees, including business and community leaders representing the full breadth of the AAPI diaspora in South Jersey, Southeastern Pennsylvania, and Delaware—spanning Central Asia, East Asia, South Asia, Southeast Asia, the Middle East, and the Pacific Islands.<span id="more-7327"></span></p>
<p>Firm Managing Member <a href="https://www.khflaw.com/edward-t-kang.html">Edward Kang,</a> who serves on the AABAGP Board of Directors, participated in the evening’s program and joined fellow board members in recognizing the extraordinary contributions of local nonprofit organizations.</p>
<p>The Gala also featured a special AAPI history video, produced by AABAGP and presented during the program. The video highlights the rich and diverse history of AAPI communities and their contributions to the region.</p>
<p>Watch the video here: <a href="https://youtu.be/jzWxQPrBV_o">https://youtu.be/jzWxQPrBV_o</a></p>
<p>The evening served not only as a celebration of heritage and achievement but also as a reminder of the importance of supporting AAPI‑owned businesses, advancing economic opportunity, and strengthening community networks across the tri‑state area. Kang Haggerty is honored to support AABAGP’s mission and looks forward to continuing its partnership in uplifting and empowering the region’s AAPI business community.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7327</post-id>	</item>
		<item>
		<title>Legal Intelligencer: When the American Dream Stalls: Litigation Strategies for EB-5 Investors Seeking the Return of Their Capital</title>
		<link>https://www.khflaw.com/news/legal-intelligencer-when-the-american-dream-stalls-litigation-strategies-for-eb-5-investors-seeking-the-return-of-their-capital/</link>
		
		<dc:creator><![CDATA[Edward T. Kang]]></dc:creator>
		<pubDate>Thu, 14 May 2026 13:32:59 +0000</pubDate>
				<category><![CDATA[Publications]]></category>
		<category><![CDATA[Legal Intelligencer]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7332</guid>

					<description><![CDATA[For practitioners advising EB-5 investors, capital recovery is rarely as simple as filing a breach-of-contract claim against a regional center or a new commercial enterprise (NCE). EB-5 disputes sit at the intersection of federal immigration law, federal and state securities regulation, partnership and LLC governance, and, increasingly, fraud-based statutory regimes. In the May 14, 2026 [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><em>For practitioners advising EB-5 investors, capital recovery is rarely as simple as filing a breach-of-contract claim against a regional center or a new commercial enterprise (NCE). EB-5 disputes sit at the intersection of federal immigration law, federal and state securities regulation, partnership and LLC governance, and, increasingly, fraud-based statutory regimes.</em></p>
<p>In the May 14, 2026 edition of <a href="https://www.law.com/thelegalintelligencer">The Legal Intelligencer</a>, Edward Kang writes, “<a href="https://www.law.com/thelegalintelligencer/2026/05/14/when-the-american-dream-stalls-litigation-strategies-for-eb-5-investors-seeking-the-return-of-their-capital/">When the American Dream Stalls: Litigation Strategies for EB-5 Investors Seeking the Return of Their Capital.</a>&#8220;<span id="more-7332"></span></p>
<div class="mb-4">
<div class="article-font-size">
<p>For decades, the EB-5 immigrant investor program has been marketed to foreign nationals as a straightforward exchange: invest the required capital in a qualifying U.S. enterprise, create or preserve at least 10 qualifying U.S. jobs per investor, and receive lawful permanent residence. The reality, particularly over the last several years, has proven far more complicated. A growing number of EB-5 investors—many of whom committed their life savings—are discovering that the path to both a green card and the return of their capital can be derailed by failed projects, mismanaged regional centers, and, in some cases, outright fraud. As the EB-5 Reform and Integrity Act of 2022 (the RIA) continues to reshape the program, litigation by aggrieved investors has surged, and the strategic landscape for plaintiffs counsel is evolving rapidly.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>For practitioners advising EB-5 investors, capital recovery is rarely as simple as filing a breach-of-contract claim against a regional center or a new commercial enterprise (NCE). EB-5 disputes sit at the intersection of federal immigration law, federal and state securities regulation, partnership and LLC governance, and, increasingly, fraud-based statutory regimes. Understanding how these areas of law interact—and where recent litigation trends are emerging—is essential to building a viable case.</p>
<h2>The Structural Problem: Capital &#8216;At Risk&#8217; by Design</h2>
<div class="mb-4">
<div class="article-font-size">
<p>The starting point for any EB-5 dispute is a feature, not a bug, of the program: investor capital must remain “at risk” throughout the sustainment period for the investor to qualify for, and ultimately retain, lawful permanent residence. U.S. Citizenship and Immigration Services (USCIS) has long interpreted this requirement strictly, and the RIA codified and refined it. The practical consequence is that EB-5 offering documents—typically a limited partnership agreement or LLC operating agreement, paired with a private placement memorandum and subscription agreement—are deliberately structured to avoid guarantees of repayment.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>This structural reality is the first hurdle plaintiffs counsel must navigate. Defendants routinely invoke the “at risk” requirement as a shield, arguing that investors knowingly accepted the possibility of total loss. But the “at risk” requirement does not immunize sponsors from liability for misrepresentations, self-dealing, breaches of fiduciary duty, or violations of the securities laws. The distinction—between legitimate investment risk and actionable misconduct—is where most EB-5 litigation now arises.</p>
<h2>The Recent Trend: From Immigration Frustration to Securities Fraud</h2>
<div class="mb-4">
<div class="article-font-size">
<p>The most significant trend over the past few years has been the migration of EB-5 disputes away from purely contractual or immigration-adjacent claims and toward federal and state securities fraud theories. This shift is driven by several factors.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>First, EB-5 interests are securities. The Securities and Exchange Commission confirmed this years ago, and federal courts have consistently agreed. That means the full arsenal of Section 10(b), Rule 10b-5, and Section 12(a)(2) of the Securities Act of 1933 is available to investors who can plead misrepresentation or omission with the requisite particularity. State blue-sky statutes—including in Pennsylvania, New Jersey, Delaware, and New York, where many EB-5 sponsors operate or solicit—provide additional, and sometimes more forgiving, avenues.</p>
<p>Second, the SEC has been increasingly active in EB-5 enforcement, and its filings frequently provide a roadmap for private litigation. Recent enforcement actions have targeted regional center principals for misappropriating investor funds, commingling capital across unrelated projects, paying undisclosed commissions to unregistered finders abroad, and inflating job-creation projections in private placement memoranda (PPMs). When the SEC files, private plaintiffs often follow—and the SEC’s complaint, while not admissible as proof, can supply the factual scaffolding needed to clear the heightened pleading bar of the Private Securities Litigation Reform Act.</p>
<p>Third, courts have grown more receptive to claims that sponsors and their affiliates owe fiduciary duties to investors notwithstanding contractual disclaimers. Delaware courts, in particular, have been willing to permit breach of fiduciary duty claims to proceed against general partners and managing members of EB-5 NCEs where self-dealing or gross mismanagement is plausibly alleged. Given that a substantial share of EB-5 entities is organized under Delaware law, this trend in case law has outsized practical importance.</p>
<h2>Where the Money Goes—and How to Follow It</h2>
<p>A defining feature of EB-5 disputes is the structural distance between the investor and the actual use of capital. In a typical structure, the investor’s funds flow into the NCE, which, in turn, loans or contributes capital to a job-creating entity (JCE). The JCE may be controlled by entirely different principals, may pledge collateral to senior lenders who stand ahead of EB-5 capital, and may be a single entity in a sprawling web of affiliates. When the project fails, investors often discover that the NCE’s only meaningful asset is an unsecured or deeply subordinated claim against a JCE that is already in bankruptcy or has no recoverable assets.</p>
<p>For plaintiffs counsel, this means that suing only the NCE is rarely sufficient. The most effective recent cases have named, where the facts support it, the regional center and its principals, the JCE and its developers, affiliated management companies that collected fees, migration agents who received undisclosed commissions, and, in appropriate cases, escrow agents and broker-dealers who facilitated the offering. The goal is to identify every actor who participated in the alleged misconduct and who has the financial capacity to satisfy a judgment.</p>
<p>This is where the strategic considerations regarding <a href="https://www.khflaw.com/news/legal-intelligencer-taking-a-plaintiffs-case-to-the-next-level-holding-individuals-liable-under-pennsylvania-law/">when to name individuals as defendants </a>come into play. In EB-5 cases involving egregious or systemic fraud, naming individual principals is often essential. Investors are typically sophisticated enough to understand that they were not dealing with an impersonal corporate machine but with specific individuals who solicited their investment, often face-to-face or through carefully orchestrated overseas presentations. Where those individuals diverted capital, paid themselves undisclosed fees, or knowingly misrepresented the project’s prospects, juries (and judges) are far more receptive to imposing personal liability than in a routine commercial dispute.</p>
<h2>The Immigration Overlay: A Strategic Complication</h2>
<p>Perhaps the most distinctive feature of EB-5 litigation is the immigration overlay. Many investors are caught in a difficult position: they want their money back, but they also want to preserve their immigration status or that of their family members. Filing suit can complicate both objectives. If the litigation is framed as an attempt to extract capital prematurely, USCIS may take the position that the capital is no longer “at risk” and deny or revoke the underlying petition. Conversely, if the project has demonstrably failed and the investor’s I-829 petition has already been denied, the immigration calculus changes dramatically, and recovery of capital becomes the paramount concern.</p>
<p>Counsel must therefore coordinate closely with immigration counsel from the outset. The timing of filing, the relief sought, and even the choice of forum can have direct immigration consequences. The RIA’s provisions concerning material change, project failure, and investor protection in the event of regional center termination have created new pathways for investors to preserve their petitions even when projects collapse—but these pathways must be navigated carefully and in parallel with a civil litigation strategy.</p>
<h2>Class Actions, Mass Arbitrations and the Forum Question</h2>
<p>EB-5 offerings frequently include mandatory arbitration provisions, class action waivers, and forum selection clauses pointing to Delaware, New York, or the sponsor’s home jurisdiction. The enforceability of these provisions has become a contested battleground. Some courts have enforced arbitration clauses in EB-5 subscription agreements; others have declined to do so where the clause was buried in voluminous offering materials presented to non-English-speaking investors with limited opportunity for negotiation or independent review.</p>
<p>The recent trend has been toward consolidated proceedings—whether as class actions, mass actions, or coordinated individual suits—because EB-5 investors in a given project are typically similarly situated, having received the same PPM and signed substantially identical subscription documents. Common questions of misrepresentation, breach of fiduciary duty, and damages predominate. For plaintiffs counsel evaluating an EB-5 matter, the question of whether to pursue an individual action, a class action, or coordinated mass arbitration is a critical early decision that will shape every later step.</p>
<h2>Practical Guidance for Plaintiffs Counsel</h2>
<p>For practitioners evaluating potential EB-5 cases, several principles emerge from recent experience. First, conduct rigorous early diligence on the capital flow. Obtain and analyze the PPM, subscription agreement, escrow agreement, loan documents between the NCE and JCE, and any available financial statements. The story of where the money actually went is usually the heart of the case.</p>
<div class="mb-4">
<div class="article-font-size">
<p>Second, identify and pursue all potentially liable parties early. Limitations periods under federal and state securities laws are unforgiving, and EB-5 frauds are often discovered years after the initial investment.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Third, plead with particularity. Rule 9(b) and the PSLRA demand specificity, and EB-5 cases live or die on the quality of the factual allegations regarding what was said, by whom, when, and why it was false or misleading.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Fourth, coordinate with immigration counsel and, where relevant, with parallel SEC or criminal proceedings. The interplay among civil, regulatory, and immigration tracks is complex but often presents strategic opportunities.</p>
<h2>Conclusion</h2>
<div class="mb-4">
<div class="article-font-size">
<p>EB-5 litigation has matured from a niche corner of immigration-adjacent commercial disputes into a substantial and rapidly developing field of securities and fraud litigation. For investors who entrusted their capital—and their families’ futures—to sponsors who failed to deliver, the path to recovery is rarely simple, but it is increasingly viable. The investors who secure the best outcomes are those whose counsel approach these cases with the rigor of securities litigators, the strategic discipline of complex commercial litigators, and an appreciation for the immigration stakes that make EB-5 disputes uniquely consequential for the individuals on the other side of the caption.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p><b>Edward T. Kang</b> <i>is the managing member of Kang Haggerty. He devotes the majority of his practice to business litigation and other litigation involving business entities. Contact him at <a href="mailto:ekang@kanghaggerty.com">ekang@kanghaggerty.com</a>.</i></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7332</post-id>	</item>
		<item>
		<title>Legal Intelligencer: No Private Right? No Problem: Ninth Circuit Lets 340B Pricing Claims Proceed Under the False Claims Act</title>
		<link>https://www.khflaw.com/news/legal-intelligencer-no-private-right-no-problem-ninth-circuit-lets-340b-pricing-claims-proceed-under-the-false-claims-act/</link>
		
		<dc:creator><![CDATA[Edward T. Kang]]></dc:creator>
		<pubDate>Thu, 16 Apr 2026 13:25:35 +0000</pubDate>
				<category><![CDATA[Publications]]></category>
		<category><![CDATA[Legal Intelligencer]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7330</guid>

					<description><![CDATA[The U.S. Court of Appeals for the Ninth Circuit just disrupted that assumption. In Adventist Health System of West v. AbbVie, the court revived a qui tam action alleging systemic overcharges under 340B and, in doing so, made a critical point: the absence of a private right of action under 340B does not insulate manufacturers [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><em>The U.S. Court of Appeals for the Ninth Circuit just disrupted that assumption. In Adventist Health System of West v. AbbVie, the court revived a qui tam action alleging systemic overcharges under 340B and, in doing so, made a critical point: the absence of a private right of action under 340B does not insulate manufacturers from liability under the False Claims Act (FCA).</em></p>
<p>In the April 16, 2026 edition of <a href="https://www.law.com/thelegalintelligencer">The Legal Intelligencer</a>, Edward Kang writes, &#8220;<a href="https://www.law.com/thelegalintelligencer/2026/04/16/no-private-right-no-problem-ninth-circuit-lets-340b-pricing-claims-proceed-under-the-false-claims-act/">No Private Right? No Problem: Ninth Circuit Lets 340B Pricing Claims Proceed Under the False Claims Act.</a>&#8220;<span id="more-7330"></span></p>
<div class="mb-4">
<div class="article-font-size">
<p>For years, pharmaceutical manufacturers have treated disputes under the 340B Drug Pricing Program (i.e., a U.S. federal program that requires drug manufacturers to provide significant discounts on outpatient prescription drugs to certain health care organizations that serve uninsured or low-income patients) as regulatory matters—issues to be handled through agency processes, not through high-stakes fraud litigation. The U.S. Court of Appeals for the Ninth Circuit just disrupted that assumption. In <i>Adventist Health System of West v. AbbVie, </i>24-2180, (9th Cir. Mar. 17, 2026), the court revived a qui tam action alleging systemic overcharges under 340B and, in doing so, made a critical point: the absence of a private right of action under 340B does not insulate manufacturers from liability under the False Claims Act (FCA).</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>For practitioners, the takeaway is immediate and practical. If the facts support it, a 340B pricing case is no longer just a regulatory dispute—it may be a viable FCA case.</p>
<p><b>The Defense Playbook—and Why It Failed</b></p>
<div class="mb-4">
<div class="article-font-size">
<p>The defendants advanced what, until now, has been a powerful threshold argument: <i>Astra USA v. Santa Clara County, </i>563 U.S. 110 (2011) forecloses private enforcement of 340B. Rather, a covered entity must file a claim through the Section 340B administrative dispute resolution process if it alleges a direct pricing violation against a drug manufacturer.<i> </i>That is, a covered entity cannot sue manufacturers directly for overcharges; it must proceed through the administrative dispute resolution process.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>In the case before the U.S. district court, Adventist alleged that the defendants harmed the government in many ways. In particular, it alleged that the defendants sold drugs at inflated prices to covered entities, and then federal and state governments paid higher prices for the drugs through their Medicaid payments to the covered entities. Relying on <i>Astra</i>, the defendants argued that Adventist—a covered entity—cannot sue the defendants directly for violating the FCA. Interestingly, the defendants admitted that Adventist’s claims are based on alleged violations of the FCA, not direct violations of Section 340B as in <i>Astra</i>, but they nevertheless argue that <i>Astra’s</i> reasoning bars all claims arising from “purported violations of the 340B statute.” The district court agreed and dismissed the case.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>The Ninth Circuit did not.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>The Ninth Circuit saw the claims differently. The flaw in the defense argument—and the lesson for practitioners—is straightforward: not every case that involves a 340B violation is a 340B enforcement action. It could be an action under the FCA.</p>
</div>
<p><b>The Critical Distinction: FCA Liability Is Different</b></p>
<div class="mb-4">
<div class="article-font-size">
<p>The Ninth Circuit’s decision turns on a distinction that should now be at the front of the mind for any practitioner evaluating these cases under the FCA:</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p><i>An FCA Claim Is Not a 340B Claim</i></p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>That is not semantics—it is strategy. The relator is not seeking reimbursement for overcharges. It is seeking remedies under the FCA: treble damages and statutory penalties on behalf of the government. The injury is not to the covered entity; it is to the government. That framing changes everything. Courts have long recognized that the FCA operates independently of the statutes whose violations give rise to false claims. The Ninth Circuit simply applied that principle here. The lack of a private right of action under 340B is irrelevant where the cause of action arises under the FCA.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p><i>Repackaging vs. Reframing: Getting the Theory Right</i></p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>The defendants’ second argument—that the case is merely a “repackaged” 340B claim—also failed, and the reason matters. In <i>Astra</i>, the plaintiffs sought to recover their own overcharges. That is classic 340B enforcement. In <i>Adventist</i>, the relator was seeking to recover for the government based on allegedly false claims submitted for payment. That is an FCA case.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>This is more than a pleading distinction. It is a structural one:</p>
<ul id="rte-68117810-3751-11f1-a094-dd91e4c7689b" class="rte2-style-ul">
<li><b>340B ADR process</b> → reimbursement to covered entities.</li>
<li><b>FCA action</b> → penalties and damages paid to the government.</li>
</ul>
<div class="mb-4">
<div class="article-font-size">
<p>If you are building one of these cases, the theory must be clear from the outset. If it looks like a reimbursement claim, it risks dismissal. If it is framed as fraud on the government, it survives.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p><b>The Real Risk for Manufacturers: FCA Exposure</b></p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>The practical consequence of the decision is significant: 340B compliance is now a potential FCA minefield.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Consider the exposure:</p>
<div class="mb-4">
<div class="article-font-size">
<ul id="rte-68119f20-3751-11f1-a094-dd91e4c7689b" class="rte2-style-ul">
<li>Thousands of transactions</li>
<li>Across multiple years</li>
<li>With per-claim penalties and treble damages</li>
</ul>
<p>Even modest pricing deviations, if systemic and intentional, can produce staggering liability.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>Manufacturers will argue—as they generally do—that pricing under 340B is complex, technical, and subject to reasonable interpretation. That defense may ultimately carry weight. But it is no longer a basis for early dismissal. The case will proceed to discovery.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p><b>Pleading the Case: Falsity Still Matters</b></p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>The Ninth Circuit did not lower the bar for FCA claims—it simply allowed this one to proceed. The relator still must prove falsity, and the court’s discussion provides a roadmap. Defendants argued that “penny pricing” obligations did not apply before the 2019 rule of The Health Resources and Services Administration, a unit of the Health and Human Services that manages and oversees the Section 340B program. The court rejected that position, emphasizing that the statutory framework—not just the regulation—can establish the pricing requirement.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>For practitioners, the lesson is clear:</p>
<div class="mb-4">
<div class="article-font-size">
<ul id="rte-6811c630-3751-11f1-a094-dd91e4c7689b" class="rte2-style-ul">
<li>Do not anchor your case solely to post-2019 conduct</li>
<li>Use statutory text, guidance, and pricing behavior to establish falsity</li>
<li>Expect a fight over interpretation, not just facts</li>
</ul>
<p>Equally important, the court refused to resolve disputes about HRSA oversight at the motion to dismiss stage. Those arguments may resurface—but only after discovery.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p><b>Strategic Takeaways for Plaintiffs Counsel</b></p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>This decision is not just doctrinal—it is tactical. For those evaluating potential cases, several points stand out.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>First, access to data is leverage. Covered entities are uniquely positioned. They see pricing patterns over time. That visibility is the foundation of a viable FCA case. Second, the theory must be disciplined. Do not plead a grievance about overcharges. Plead a fraud case tied to claims for government payment. Third, scale matters. Isolated errors are unlikely to justify FCA exposure. Patterns, repetition, and internal knowledge are what transform a pricing issue into a fraud case. Fourth, expect a scienter battle. Manufacturers will argue ambiguity and good-faith interpretation. Internal documents, guidance, and post-2019 conduct will be critical.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p><b>Strategic Takeaways for Defense Counsel</b></p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>The ruling also reshapes the defense approach. Early dismissal on <i>Astra</i> grounds is no longer reliable—at least in the Ninth Circuit. The focus will shift to:</p>
<ul id="rte-6811ed40-3751-11f1-a094-dd91e4c7689b" class="rte2-style-ul">
<li>Challenging falsity based on statutory interpretation</li>
<li>Undermining scienter through complexity and ambiguity</li>
<li>Attacking materiality (did pricing actually affect government payment decisions?)</li>
</ul>
<p>In other words, these cases will be fought on the merits, not disposed of at the threshold.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p><b>What Comes Next</b></p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>While the Ninth Circuit answered one question, it left many important ones unresolved:</p>
<ul id="rte-68121450-3751-11f1-a094-dd91e4c7689b" class="rte2-style-ul">
<li>Were false claims actually submitted?</li>
<li>Did the defendants act knowingly?</li>
<li>Were any misstatements material to payment?</li>
</ul>
<p>Those are fact-intensive inquiries. This case now becomes a discovery-driven battle involving pricing data, internal communications, and expert analysis.</p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p><b>Conclusion</b></p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>The Ninth Circuit’s decision is a shift in posture, not just precedent. It confirms that 340B disputes can, under the right circumstances, be litigated as FCA fraud cases. For plaintiffs, it opens a path that did not meaningfully exist before. For manufacturers, it introduces a level of risk that cannot be managed through regulatory compliance alone. And for practitioners on both sides, it reinforces a familiar principle: when government money is involved, statutory complexity does not preclude fraud liability—it often invites it. The FCA is indeed the most effective tool for combating fraud against the government and the waste of taxpayer money.</p>
<p><b>Edward T. Kang</b> <i>is the managing member of Kang Haggerty. He devotes the majority of his practice to business litigation and other litigation involving business entities. Contact him at <a href="mailto:ekang@kanghaggerty.com">ekang@kanghaggerty.com</a>.</i></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7330</post-id>	</item>
		<item>
		<title>Legal Intelligencer: Taking a Plaintiff’s Case to the Next Level, Part II: It Does Not Always Take Two—Why Naming Individuals as Defendants Is Not Always the Best Strategy</title>
		<link>https://www.khflaw.com/news/legal-intelligencer-taking-a-plaintiffs-case-to-the-next-level-part-ii-it-does-not-always-take-two-why-naming-individuals-as-defendants-is-not-always-the-best-strategy/</link>
		
		<dc:creator><![CDATA[Edward T. Kang and Kandis Kovalsky]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 23:32:11 +0000</pubDate>
				<category><![CDATA[Publications]]></category>
		<category><![CDATA[Legal Intelligencer]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7309</guid>

					<description><![CDATA[While suing individual owners, officers, or directors alongside their corporate entities can work to a plaintiff’s advantage, this strategy carries a distinct risk: juries may personalize the corporate defendants, leading to smaller verdicts. In the March 26, 2026 edition of The Legal Intelligencer, Edward Kang and Kandis Kovalsky co-authored, &#8220;Taking a Plaintiff’s Case to the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><em>While suing individual owners, officers, or directors alongside their corporate entities can work to a plaintiff’s advantage, this strategy carries a distinct risk: juries may personalize the corporate defendants, leading to smaller verdicts.</em></p>
<p>In the March 26, 2026 edition of <a href="https://www.law.com/thelegalintelligencer/">The Legal Intelligencer</a>, Edward Kang and Kandis Kovalsky co-authored, &#8220;<a href="https://www.law.com/thelegalintelligencer/2026/03/26/taking-a-plaintiffs-case-to-the-next-level-part-ii-it-does-not-always-take-twowhy-naming-individuals-as-defendants-is-not-always-the-best-strategy/">Taking a Plaintiff’s Case to the Next Level, Part II: It Does Not Always Take Two—Why Naming Individuals as Defendants Is Not Always the Best Strategy</a>.&#8221;<span id="more-7309"></span></p>
<div class="mb-4">
<div class="article-font-size">
<p>A month ago, we published a <a href="https://www.khflaw.com/news/legal-intelligencer-taking-a-plaintiffs-case-to-the-next-level-holding-individuals-liable-under-pennsylvania-law/">column</a> about a topic we are passionate about, particularly in our qui tam practice: holding individuals liable for their misconduct alongside corporate defendants. But naming individuals alongside corporate entities is not always the optimal strategy for achieving the result your plaintiff-client deserves. Knowing when to name an individual as a defendant—and when not to—is essential, especially in matters destined for a jury rather than a bench trial. While suing individual owners, officers, or directors alongside their corporate entities can work to a plaintiff’s advantage, this strategy carries a distinct risk: juries may personalize the corporate defendants, leading to smaller verdicts.</p>
<p>As we discussed in our recent <a href="https://www.khflaw.com/news/legal-intelligencer-taking-a-plaintiffs-case-to-the-next-level-holding-individuals-liable-under-pennsylvania-law/">column</a>, if a plaintiff names an individual defendant under Pennsylvania’s participation theory, a necessary prerequisite is that the individual actually participated in the wrongful conduct. See <i>Wicks v. Milzoco Builders,</i> 470 A.2d 86 (Pa. 1983). But beyond that threshold requirement lie critical strategic considerations about case presentation at trial—particularly jury trials—that determine whether naming an individual is wise.</p>
<p><b>The Juror Psychology of Corporate versus Individual Defendants</b></p>
</div>
</div>
<div class="mb-4">
<div class="article-font-size">
<p>It is no secret that jurors, particularly those in Philadelphia, often view corporations with skepticism and are willing to return substantial verdicts against them, especially when those corporations have deep pockets. In October 2019, a Philadelphia jury awarded $8 billion in punitive damages against a Johnson &amp; Johnson subsidiary for illegally marketing the antipsychotic drug Risperdal, exposing young boys to the risk of developing gynecomastia. No comparable award against an individual defendant comes close. (The Risperdal award was later reduced by a judge to $6.8 million, but the initial verdict underscored juror sentiment toward large corporations.)</p>
<p>Empirical data support this intuition. In 1989, Valerie P. Hans and David M. Ermann conducted a landmark study presenting mock jurors with identical factual scenarios involving toxic exposure at a workplace. The only variable was whether the defendant was an individual or a corporation. The sample jury awarded $151,584 against the individual and $247,610 against the corporate defendant—a differential of more than 60%.</p>
<p>Similarly, in 2013, Chris Denove conducted a study for Plaintiff Magazine using three mock trials based on the same trip-and-fall fact pattern. The sole variable was the defendant’s identity: an individual, a local store, or a national retail chain. Perhaps unsurprisingly, the jurors awarded $100,000 against the national chain, $70,000 against the local store, and only $22,000 against the individual.</p>
<p>These studies confirm what experienced trial lawyers suspect: jurors calibrate damages not only to harm suffered but also to their perception of who should bear the loss and who can afford to pay.</p>
<p><b>Calibrating the Decision: Key Factors to Consider</b></p>
<p>Before adding an individual defendant, practitioners should assess three intersecting factors: the level and nature of the individual’s involvement, the egregiousness of the conduct, and whether the individual is likely to be seen as likable or sympathetic. These factors exist on a spectrum.</p>
<p>The faces behind Purdue Pharma’s manufactured opioid crisis—which injured hundreds of thousands for financial gain—bear little resemblance to the owner of a mom-and-pop corner shop where a customer slipped on a wet floor. The former involves masterminds who engaged in a pattern of intentional, systematic misconduct over many years; the latter involves an unintentional, isolated incident arising from potentially negligent conduct. These contrasting scenarios highlight two crucial distinctions: systematic pattern versus isolated incident, and intentional misconduct versus negligence.</p>
<p>A systematic pattern need not span years; it can simply involve an individual engaging in a repeated pattern of misconduct. Egregiousness matters, and egregious misconduct often involves multiple acts and repetition over time. Regarding the distinction between intentional misconduct and negligence, juries—as collections of human beings—are naturally more forgiving of individuals who made a single mistake, even if that negligence caused significant harm, than of individuals who engaged in repeated intentional wrongdoing. That said, the analysis is not straightforward even with negligence claims. Significant verdicts against individuals for medical malpractice, for example, are common, but there, plaintiffs often have no choice but to name the individual responsible if they are to obtain compensation.</p>
<p>Because jurors naturally resist ruining or punishing an individual for a simple mistake, naming an individual defendant in a scenario where negligence produced an unfortunate, isolated incident can easily backfire, particularly if the individual is likable and sympathetic. Adding an individual defendant allows the corporate defendant to be humanized (something defense counsel will attempt anyway) and may cause juries to hesitate before returning a larger verdict that will be joint and several against both individual and corporate defendants. In these scenarios, if the jury is likely to want to make the injured plaintiff “whole” and the corporate defendant has sufficient funds, foregoing the individual defendant may be the wiser course.</p>
<p><b>When Individual Liability Serves the Case</b></p>
<p>Conversely, in situations resembling Purdue’s OxyContin distribution, the calculus shifts. While the Sackler family was never held civilly or criminally liable by a jury, public sentiment strongly favored holding them responsible. The Purdue scenario exhibits all the hallmarks of a case where individual liability is appropriate: the individuals directed the misconduct, the misconduct was egregious, and the individuals involved are unsympathetic, perceived as having acted for financial gain. In such cases, naming individuals can be powerful. Jurors are weary of corporations—which are run by and can act only through humans—hiding behind the corporate veil when their misconduct is exposed, and paying damages that amount to little more than a slap on the wrist. We explored this concept in our recent column, discussing the 2015 Yates Memorandum and what inspired it. Without humans, corporations cannot act, and where repeated corporate misconduct occurs, people want to see individuals held accountable.</p>
<p><b>The Role of Corporate Size and Type</b></p>
<p>Another important consideration is the size and financial wherewithal of corporate defendants. Denove’s 2013 study demonstrated that juries are more likely to return larger verdicts against national companies than smaller regional ones. This reflects a perception that large companies have deep pockets and the ability to pay. Individuals often lack the same capacity, so juries may be less inclined to issue large joint-and-several verdicts unless the individual is unlikable or engaged in egregious misconduct. Conversely, if your case involves a smaller company that may not be able to satisfy a full verdict, adding an individual may have strategic benefit—or it may not.</p>
<p>The type of company also matters. While juries may inherently distrust large pharmaceutical companies like Johnson &amp; Johnson, other entities—nonprofits, for example, or retailers like Trader Joe’s—enjoy greater public goodwill. In those situations, it may be preferable to name the individual defendant actually responsible for the plaintiff’s injuries, rather than rely on the corporate defendant’s favorable reputation.</p>
<p>Practitioners should keep in mind whether adding an individual is an option that is only available when the facts support adding the individual as a defendant. In many situations, this option may not exist.</p>
<p><b>Conclusion</b></p>
<p>Determining whether to add an individual as a defendant is a complex strategic decision requiring analysis of multiple factors. When preparing a case for initial filing, it may be tempting to name every involved individual as a way to maximize recovery. But before doing so, take a step back and analyze whether that approach will actually produce the result you want. Just because you can name an individual as a defendant under the facts does not mean you should. Sometimes the best way to hold a corporation accountable is to let the corporation stand alone—and let the jury decide what justice requires.</p>
<p><b>Edward T. Kang</b> <i>is the managing member of Kang Haggerty. He devotes the majority of his practice to business litigation and other litigation involving business entities. Contact him at <a href="mailto:ekang@kanghaggerty.com">ekang@kanghaggerty.com</a>.</i></p>
<p><b>Kandis L. Kovalsky</b><i>, a member with the firm, focuses her practice on a broad range of high stakes business-related civil litigation in Pennsylvania, New Jersey, and New York state and federal courts and arbitral tribunals, and representing relators in high stakes qui tam actions filed under the federal and state False Claims Acts. <em>Contact her at <a href="mailto:kkovalsky@kanghaggerty.com">kkovalsky@kanghaggerty.com</a>. </em></i></p>
<div class="content">
<div class="entry-content">
<p><strong><em>Reprinted with permission from the March 26, 2026 edition of “The Legal Intelligencer” © 2026 ALM Global, LLC. All rights reserved. Further duplication without permission is prohibited. Request academic re-use from <a class="text-blue-800 underline hover:no-underline" href="https://www.copyright.com/">www.copyright.com.</a> All other uses, submit a request to <a class="text-blue-800 underline hover:no-underline" href="mailto: asset-and-logo-licensing@alm.com">asset-and-logo-licensing@alm.com.</a> For more information visit <a class="text-blue-800 underline hover:no-underline" href="https://www.law.com/asset-and-logo-licensing/">Asset &amp; Logo Licensing</a>.</em></strong></p>
</div>
</div>
</div>
</div>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7309</post-id>	</item>
		<item>
		<title>Legal Intelligencer: AI Systems and the Question of Confidentiality</title>
		<link>https://www.khflaw.com/news/legal-intelligencer-ai-systems-and-the-question-of-confidentiality/</link>
		
		<dc:creator><![CDATA[Kelly Lavelle]]></dc:creator>
		<pubDate>Thu, 19 Mar 2026 14:44:18 +0000</pubDate>
				<category><![CDATA[Publications]]></category>
		<category><![CDATA[ediscovery]]></category>
		<category><![CDATA[Legal Intelligencer]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7304</guid>

					<description><![CDATA[Before privilege or production issues arise, the more basic inquiry is whether the information was ever confidential in the first place. This question is particularly significant in e-discovery, where electronically stored information generated by AI systems may later become discoverable. In the March 19, 2026 edition of The Legal Intelligencer, Kelly Lavelle writes, &#8220;AI Systems [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><em>Before privilege or production issues arise, the more basic inquiry is whether the information was ever confidential in the first place. This question is particularly significant in e-discovery, where electronically stored information generated by AI systems may later become discoverable.</em></p>
<p>In the March 19, 2026 edition of <a href="https://www.law.com/thelegalintelligencer">The Legal Intelligencer</a>, Kelly Lavelle writes, &#8220;<a href="https://www.law.com/thelegalintelligencer/2026/03/19/ai-systems-and-the-question-of-confidentiality/?slreturn=20260319103703">AI Systems and the Question of Confidentiality</a>.&#8221;<span id="more-7304"></span>Much of the attention surrounding generative AI in litigation has focused on hallucinated authorities and AI-generated filings. But a different litigation risk arises when lawyers, or even clients themselves, enter client information into an AI platform. Before privilege or production issues arise, the more basic inquiry is whether the information was ever confidential in the first place. This question is particularly significant in e-discovery, where electronically stored information generated by AI systems may later become discoverable.</p>
<p>The U.S. District Court for the Southern District of New York’s decision in <i>United States v. Heppner</i> brings that issue into focus. Although the case has been described as a privilege ruling, the court’s analysis turned on a more basic issue: whether the information was confidential when it was entered into the AI platform. If client information is submitted to a system under terms that allow the provider to access, retain, or disclose it, the protections that depend on confidentiality, including attorney-client privilege and work product, may never attach.</p>
<p>In <i>Heppner,</i> a corporate executive under criminal investigation used the publicly available generative AI platform “Claude” to generate written analyses of potential defenses after receiving a grand jury subpoena. He later shared those documents with counsel. Following his arrest, FBI agents executed a search warrant at Bradley Heppner&#8217;s home and seized numerous documents and electronic devices. Heppner&#8217;s counsel later informed the government that among the seized materials were approximately thirty-one documents memorializing Heppner’s communications with the AI platform.</p>
<p>Through his counsel, Heppner asserted privilege over these documents, arguing that the information entered into the AI platform was learned, that he created the documents to facilitate discussions with counsel and obtain legal advice, and that he subsequently shared the AI outputs with his attorneys. His counsel acknowledged, however, that they did not direct Heppner to conduct the AI searches. The court rejected those claims. It held that the documents were not communications with an attorney, were not prepared by or at the direction of counsel, and, critically, were not confidential in light of the platform’s privacy policy.</p>
<p>The court’s analysis centered on the conditions under which the information was entered into the system. The provider’s terms stated that user inputs and outputs were collected and retained and that the company reserved the right to disclose data to third parties, including governmental authorities. Under those conditions, the court concluded that Heppner lacked a reasonable expectation of confidentiality at the moment of disclosure.</p>
<p>The court also rejected Heppner’s contention that he communicated with Claude for the “express purpose of talking to counsel.” In doing so, the court looked to the platform’s own representations. Claude expressly disclaimed providing legal advice. When asked whether it could provide such advice, the system responded that it was not a lawyer, could not offer formal legal recommendations, and advised users to consult a qualified attorney.</p>
<p>The court acknowledged that the implications of artificial intelligence for the law are only beginning to be explored. The court emphasized that AI’s novelty does not place it outside established legal principles, including those governing attorney-client privilege and the work-product doctrine. AI does not change the basic rules.</p>
<p>The opinion highlights a familiar but often underemphasized principle that privilege attaches only when communications are intended to be confidential and were, in fact, kept confidential. In the AI context, if a platform’s terms allow provider use beyond delivering the requested service, such as model training, analytics, affiliate sharing, or extended retention, the user may be acting inconsistently with the intent to preserve confidentiality at the moment of disclosure. The issue is not a subsequent waiver. It is that the platform itself may defeat confidentiality at inception.</p>
<p>This reasoning extends beyond generative AI. Courts have consistently held that employees may waive attorney-client privilege when using employer email systems to communicate with counsel, with the analysis turning on whether the employee had an objectively reasonable expectation of confidentiality. In those cases, the inquiry focuses on whether the intent to communicate in confidence was objectively reasonable under the circumstances. <i>Heppner</i> suggests that AI platforms may be subject to similar scrutiny. The terms governing data retention and disclosure may determine whether any protection exists at all.</p>
<p>The court also reaffirmed that privilege remains grounded in professional accountability. Recognized privileges depend on a relationship with a licensed professional who owes fiduciary duties and is subject to discipline. Generative AI does not occupy that role. Even if an output resembles legal advice, it is not a communication with counsel.</p>
<p>However, the court suggested that if counsel had directed the use of the AI tool within a structured framework, the analysis might have been different. That distinction highlights the importance of control. When AI use is integrated into a counsel-directed process under defined terms, protection arguments may be stronger. When it is independent and unsupervised, confidentiality may fail at the start.</p>
<p>Platform terms of service are therefore central. Many providers claim licenses to user inputs and outputs broader than a confidentiality-preserving relationship would tolerate, sometimes including rights to use content for service improvement, analytics or model training. However, this concern does not apply in the same way to all AI tools. Paid legal research platforms or firm-licensed systems are often governed by professional services agreements that include confidentiality obligations and defined data controls. In those contexts, the vendor functions more like a traditional litigation support provider than a public AI service. Even there, however, the analysis may turn on the contract. Courts will look at the terms to determine what they permit and how the provider handles user content.</p>
<p>These issues directly affect attorney-client privilege. Privilege protects confidential communications made for the purpose of obtaining or providing legal advice. The problem is not simply waiver. It is that the basic requirements for privilege may never have been satisfied. The work-product doctrine raises a similar issue. Work product protects materials prepared in anticipation of litigation. If those materials are created on a public nonconfidential platform, it weakens the argument that they reflect protected legal strategy shielded from disclosure.</p>
<p><i>Heppner</i> reinforces the basic rule that privilege depends on confidentiality at the time the communication is made. It does not arise simply because a document is later shared with counsel. In the AI context, that means platform terms, data handling practices, and professional controls must align with confidentiality requirements before client information is entered. The focus should be less on whether AI interactions are discoverable and more on whether confidentiality ever attached. As <i>Heppner</i> shows, confidentiality is not assumed simply because a document resembles legal analysis. It depends on the conditions under which the information was created and maintained.</p>
<p><b>Kelly A. Lavelle</b> <i>is Senior Counsel at Kang Haggerty. She focuses on e-discovery and information management, from preservation and collection to review and production of large volumes of electronically stored information. Contact her at <a href="mailto:klavelle@kanghaggerty.com">klavelle@kanghaggerty.com</a>.</i></p>
<p><strong><em>Reprinted with permission from the March 19, 2026 edition of “The Legal Intelligencer” © 2026 ALM Global, LLC. All rights reserved. Further duplication without permission is prohibited. Request academic re-use from <a class="text-blue-800 underline hover:no-underline" href="https://www.copyright.com/">www.copyright.com.</a> All other uses, submit a request to <a class="text-blue-800 underline hover:no-underline" href="mailto: asset-and-logo-licensing@alm.com">asset-and-logo-licensing@alm.com.</a> For more information visit <a class="text-blue-800 underline hover:no-underline" href="https://www.law.com/asset-and-logo-licensing/">Asset &amp; Logo Licensing</a>.</em></strong></p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7304</post-id>	</item>
		<item>
		<title>Kang Haggerty Hosts Post EDPA Roundtable Happy Hour for TAF at Kiddo</title>
		<link>https://www.khflaw.com/news/kang-haggerty-hosts-post-edpa-roundtable-happy-hour-for-taf-at-kiddo/</link>
		
		<dc:creator><![CDATA[Kang Haggerty LLC]]></dc:creator>
		<pubDate>Thu, 12 Mar 2026 16:22:06 +0000</pubDate>
				<category><![CDATA[Events]]></category>
		<category><![CDATA[TAF]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7306</guid>

					<description><![CDATA[Kang Haggerty was pleased to host a post‑Eastern District of Pennsylvania Roundtable Happy Hour for TAF – The Anti‑Fraud Coalition last night at Kiddo in Philadelphia. The gathering brought together whistleblower practitioners, government colleagues, and members of the broader anti‑fraud community to continue the conversations sparked during the EDPA roundtable. We’re grateful to everyone who [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Kang Haggerty was pleased to host a post‑Eastern District of Pennsylvania Roundtable Happy Hour for <strong>TAF – The Anti‑Fraud Coalition</strong> last night at <strong>Kiddo</strong> in Philadelphia. The gathering brought together whistleblower practitioners, government colleagues, and members of the broader anti‑fraud community to continue the conversations sparked during the EDPA roundtable.<span id="more-7306"></span></p>
<p>We’re grateful to everyone who joined us to strengthen the relationships that drive effective False Claims Act enforcement and support the mission of TAF. A special thank‑you to Kiddo for the warm hospitality and to all who helped make the evening a success.</p>
<p>We look forward to continuing to support TAF’s work and to creating more opportunities for connection across our community.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7306</post-id>	</item>
		<item>
		<title>Kang Haggerty Welcomes Three New Associates to Its Growing Litigation Team</title>
		<link>https://www.khflaw.com/news/kang-haggerty-welcomes-three-new-associates-to-its-growing-litigation-team/</link>
		
		<dc:creator><![CDATA[Kang Haggerty LLC]]></dc:creator>
		<pubDate>Wed, 04 Mar 2026 05:08:14 +0000</pubDate>
				<category><![CDATA[Firm News]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7302</guid>

					<description><![CDATA[Philadelphia, PA (March 4, 2026):  Kang Haggerty LLC is pleased to announce the addition of Walter O. Bourdaghs, Kyle Hannigan, and Nicholas Cardoso as Associates, further strengthening the firm’s capabilities across complex commercial litigation, business disputes, employment matters, whistleblower matters, and related practice areas. Each brings a strong academic background, diverse professional experience, and a [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><strong>Philadelphia, PA (March 4, 2026):</strong>  <a href="https://www.khflaw.com/">Kang Haggerty LLC</a> is pleased to announce the addition of Walter O. Bourdaghs, Kyle Hannigan, and Nicholas Cardoso as Associates, further strengthening the firm’s capabilities across complex commercial litigation, business disputes, employment matters, whistleblower matters, and related practice areas. <span id="more-7302"></span>Each brings a strong academic background, diverse professional experience, and a commitment to client-focused advocacy that aligns with the firm’s values and strategic growth.</p>
<p><a href="https://www.khflaw.com/walter-ogura-bourdaghs.html"><strong>Walter O. Bourdaghs</strong></a> focuses his practice on complex commercial litigation, construction law, and civil rights matters, drawing on experience representing individuals, small businesses, and international companies. He earned his J.D. from Boston University School of Law and holds a B.A. from Beloit College. Walter is admitted to practice in Massachusetts, Connecticut, New Jersey, and Pennsylvania, and recently relocated to Philadelphia after working at MG+M law firm in Boston, following six years as Center Coordinator at the University of Chicago’s Center for East Asian Studies.</p>
<p><a href="https://www.khflaw.com/kyle-j-hannigan.html"><strong>Kyle Hannigan</strong></a> focuses his practice on complex civil litigation, contract disputes, whistleblower claims, and creditors’ rights, bringing experience helping clients navigate a wide range of legal challenges. He earned his J.D. from Rutgers Law School and holds a B.A. in Law &amp; Justice from Rowan University. Kyle is admitted to practice in Delaware and began his career at Kang Haggerty as a law clerk during law school; before entering the legal profession, he spent eight years in the automotive industry as a vehicle technician and service and parts coordinator.</p>
<p><a href="https://www.khflaw.com/nicholas-j-cardoso.html"><strong>Nicholas Cardoso</strong></a> focuses his practice on business disputes and employment law, representing clients on both the plaintiff and defense sides in matters involving complex commercial litigation, contract disputes, and workplace claims. He earned his J.D. from the University of Virginia School of Law and holds a B.A. in Criminology from The College of New Jersey. Nick is admitted to practice in New Jersey and Pennsylvania and previously practiced at an Am Law 200 firm, where he gained valuable insight into defense strategies that inform his work today.</p>
<p>“We are thrilled to welcome Walter, Kyle, and Nick to the firm,” said Edward T. Kang, Managing Member of Kang Haggerty. “Each of them brings strong litigation skills, intellectual rigor, and a client centered approach that enhances our ability to serve businesses and individuals across the region.”</p>
<hr />
<p><strong>Kang Haggerty LLC</strong> is a boutique business litigation firm with offices in Philadelphia, PA and Marlton, NJ. The firm was formed by lawyers with a wide range of professional, cultural, social, and political backgrounds.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7302</post-id>	</item>
		<item>
		<title>Legal Intelligencer: Taking a Plaintiff’s Case to the Next Level: Holding Individuals Liable Under Pennsylvania Law</title>
		<link>https://www.khflaw.com/news/legal-intelligencer-taking-a-plaintiffs-case-to-the-next-level-holding-individuals-liable-under-pennsylvania-law/</link>
		
		<dc:creator><![CDATA[Edward T. Kang and Kandis Kovalsky]]></dc:creator>
		<pubDate>Thu, 19 Feb 2026 22:24:12 +0000</pubDate>
				<category><![CDATA[Publications]]></category>
		<category><![CDATA[Legal Intelligencer]]></category>
		<guid isPermaLink="false">https://www.khflaw.com/news/?p=7298</guid>

					<description><![CDATA[Strategic practitioners do not need to treat entity liability as the finish line; they may treat it as a starting point. Holding individual owners or officers personally liable—whether as partners, corporate actors, alter egos, or signatories—fundamentally alters the litigation landscape. In the February 19, 2026 edition of The Legal Intelligencer, Edward Kang and Kandis Kovalsky [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><em>Strategic practitioners do not need to treat entity liability as the finish line; they may treat it as a starting point. Holding individual owners or officers personally liable—whether as partners, corporate actors, alter egos, or signatories—fundamentally alters the litigation landscape.</em></p>
<p>In the February 19, 2026 edition of <a href="https://www.law.com/thelegalintelligencer/">The Legal Intelligencer</a>, Edward Kang and Kandis Kovalsky co-authored, &#8220;<a href="https://www.law.com/thelegalintelligencer/2026/02/19/taking-a-plaintiffs-case-to-the-next-level-holding-individuals-liable-under-pennsylvania-law/?slreturn=20260219170528">Taking a Plaintiff’s Case to the Next Level: Holding Individuals Liable Under Pennsylvania Law</a>.&#8221;<span id="more-7298"></span></p>
<p>For plaintiffs counsel, winning a verdict against a corporate entity is often only the opening act. The real contest begins post-judgment, when the defendant reveals itself to be a shell: a defunct LLC, a dissolved partnership, or a corporation with nominal assets. The plaintiff, having prevailed on liability, is left holding a judgment that is legally pristine but could be practically worthless.</p>
<p>This outcome is avoidable. Strategic practitioners do not need to treat entity liability as the finish line; they may treat it as a starting point. Holding individual owners or officers personally liable—whether as partners, corporate actors, alter egos, or signatories—fundamentally alters the litigation landscape. It expands the pool of recoverable assets, concentrates the minds of defense counsel, and aligns the case with the core purpose of civil liability: meaningful accountability against wrongdoers.</p>
<h3>Why Individual Liability Matters</h3>
<p>The pursuit of individual liability is not a secondary consideration; it is a force multiplier for three distinct reasons.</p>
<p>First, individual exposure changes behavior. A corporate entity, insulated by limited liability and defense counsel, often litigates with strategic detachment. An individual whose personal assets, reputation, and future earnings are at risk does not. Cases involving individual defendants often settle differently—earlier, at higher values, and with fewer procedural hurdles. Personal risk concentrates attention in ways that corporate liability rarely does.</p>
<p>Second, the assets often reside with the individuals. Commercial general liability policies carry limits and exclusions. Directors and officers (D&amp;O) policies, by contrast, frequently provide broader coverage that follows the individual, not the entity. A dissolved corporation cannot respond to a judgment; a former officer with a D&amp;O tail policy can. General partners remain personally liable for partnership obligations—a fact often forfeited when plaintiffs name only the partnership in the complaint.</p>
<p>Third, accountability is the product. The Department of Justice’s 2015 Yates Memo recognized that corporate enforcement is incomplete when it stops at the entity level. Civil plaintiffs experience this reality firsthand. A family suing a nursing home chain is not made whole by a judgment against a corporate shell. They seek accountability from the individuals who made the decisions that caused the harm. That impulse is not merely human—it is legally and strategically sound.</p>
<h3>Direct Liability Under Pennsylvania Statutes</h3>
<p>It is well known that general partners are jointly liable for the debts of a partnership. This most straightforward path to individual liability is often statutory—and frequently overlooked at the pleading stage. Under the Pennsylvania Uniform Partnership Act, a judgment against a partnership is not, by itself, a judgment against any individual partner. See 15 Pa.C.S. Section 8437. Pennsylvania Rule of Civil Procedure 2132 reinforces this principle: a judgment entered against a partnership sued only in its firm name supports execution only against partnership property. To reach a partner’s individual assets, the partner must be named and served in the lawsuit.</p>
<p>The same logic applies to limited partnerships, under 15 Pa.C.S. Section 8645. General partners are jointly and severally liable for partnership obligations, but only if they are properly joined. A judgment against the limited partnership alone does not reach them. This is not a substantive limitation on liability; it is a pleading requirement. Plaintiffs who fail to name individual partners at the outset may forfeit the ability to collect from them entirely.</p>
<p>The lesson is elementary: name the partners when warranted. The cost of doing so is negligible; the cost of failing to do so can be fatal to recovery.</p>
<h3>Participation Theory: Liability Through Conduct</h3>
<p>Beyond statutory partnership liability, Pennsylvania recognizes a common-law doctrine that imposes individual liability on corporate officers and directors based on their personal involvement in tortious conduct. This is the participation theory, articulated most clearly in the Pennsylvania Supreme Court case <em>Wicks v. Milzoco Builders</em>, 470 A.2d 86 (Pa. 1983). Under Wicks, a corporate officer is individually liable for torts committed in the course of employment if the officer personally participated in the wrongful conduct or directed it to occur. See our earlier article on this topic, <a href="https://www.khflaw.com/news/legal-intelligencer-a-primer-on-pennsylvanias-participation-theory/">here</a>.</p>
<p>Participation theory is not veil-piercing. It does not require proof of fraud, undercapitalization, or disregard of corporate formalities. It does not attack the corporate structure. Instead, it reflects a bedrock principle: individuals remain liable for their own torts, even when acting on behalf of a corporation.</p>
<p>But the doctrine has limits. Alleging that a defendant held a corporate title or signed a document is insufficient. Plaintiffs must plead specific facts demonstrating personal involvement: directing the conduct, approving the scheme, making the misrepresentation, or physically engaging in the wrongful act. Courts are skeptical of boilerplate allegations of “participation.” Overreaching invites dismissal and damages credibility.</p>
<p>Participation theory applies only to individuals, not affiliated entities. To reach parent companies or sister corporations, plaintiffs must turn to other doctrines, such as alter ego or enterprise liability.</p>
<h3>Contractual Liability: The Signatory Problem</h3>
<p>In contract cases, the path to individual liability is narrower and more nuanced. The general rule is familiar: an agent who signs a contract on behalf of a disclosed principal is not personally liable on that contract (unless the agent specifically agrees to assume liability). See <em>Vernon D. Cox &amp; Co. v. Giles</em>, 406 A.2d 1107, 1110 (Pa. Super. 1979). But the exceptions are where cases are won or lost.</p>
<p>One common exception arises from ambiguity. If a contract does not clearly indicate the signatory’s representative capacity, parol evidence may be admissible to determine whether the parties intended individual liability. See <em>Trenton Trust v. Klausman</em>, 296 A.2d 275, 277 (Pa. Super. 1972). Ambiguous signature blocks, inconsistent use of letterhead, or vague agency language can expose individuals to personal liability. See <em>Hazer v. Zabala</em>, 26 A.3d 1166, 1170 (Pa. Super. 2011).</p>
<p>Another fertile theory is misrepresentation of authority. An agent who warrants they have authority to bind a principal—but does not—may be personally liable for breach of warranty of authority. See <em>Kribbs v. Jackson</em>, 129 A.2d 490, 496 (Pa. 1957) Similarly, an individual who makes material misrepresentations to induce a contract may face tort liability for fraudulent inducement, even if the contract itself binds only the entity. See <em>Felix v. Fraternal Order of Police</em>, Philadelphia Lodge No. 5, 759 A.2d 34, 39 (Pa. Commw. Ct. 2000).</p>
<p>These theories should be explored early. Discovery into the signatory’s knowledge, the entity’s financial condition at the time of contracting, and the parties’ communications can reveal evidence of individual intent and responsibility. In the right case, contractual individual liability is not ancillary; it is central.</p>
<h3>Alter Ego and Piercing the Corporate Veil</h3>
<p>The most demanding—and most powerful—path to individual liability is veil piercing. Pennsylvania law requires a showing that the corporation was a mere alter ego or business conduit of the individual and that respecting the corporate form would sanction fraud, illegality, or fundamental unfairness. Put simply, veil-piercing is most viable when someone uses a corporate form to perpetrate fraud.</p>
<p>Unlike participation theory, veil piercing attacks the corporate structure itself. It can also extend beyond individuals to affiliated entities under enterprise liability theories. In <em>Mortimer v. McCool</em>, 255 A.3d 261 (Pa. 2021), the Pennsylvania Supreme Court recognized the viability of enterprise liability while declining to apply it on the facts. More recently, in <em>Dewberry Group v. Dewberry Engineers</em>, 604 U.S. 321 (2025), the U.S. Supreme Court reaffirmed the presumption of corporate separateness but left room for traditional veil piercing and equitable adjustments where corporate forms obscure economic reality. See our latest article on this topic, <a href="https://www.khflaw.com/news/legal-intelligencer-no-end-run-piercing-lessons-from-mortimer-and-dewberry/">here</a>.</p>
<p>These decisions offer both caution and opportunity. Courts will not disregard corporate form lightly, but they remain receptive to well-supported claims involving commingling, asset shifting, undercapitalization, and artificial inter-company transactions. Discovery into inter-company transfers, pricing practices, and the use of shell entities can provide the factual foundation necessary to overcome the presumption of separateness.</p>
<p>As a practical matter, veil piercing should rarely be pled in an initial complaint. The necessary facts are almost never available pre-discovery, and premature allegations risk early dismissal under Pennsylvania’s fact-pleading standards, and potentially, a loss of credibility with the court. A more effective strategy is to plead viable individual claims under participation theory and statutory liability, then develop the evidentiary record to support alter ego claims as the case progresses.</p>
<h3>Choosing the Right Theory</h3>
<p>Each individual liability doctrine serves a distinct function, and understanding their interplay is critical to effective case management.</p>
<ul>
<li>Partnership liability is mandatory, not discretionary. Name the partners.</li>
<li>Participation theory is the primary tool for holding officers and managers accountable for their own tortious conduct.</li>
<li>Contractual liability theories apply where ambiguity, misrepresentation, or extra-contractual conduct creates individual exposure.</li>
<li>Veil piercing and enterprise liability are reserved for cases involving manipulation of corporate form to evade responsibility or to perpetuate fraud.</li>
</ul>
<p>Used together, these doctrines transform litigation strategy. They expand the defendant pool, increase settlement leverage, and protect plaintiffs from the all-too-common scenario of winning on liability but losing on collectability.</p>
<h3>Conclusion</h3>
<p>The shift from entity liability to individual accountability is not merely tactical; it reflects the economic realities of modern commerce. Corporate entities can be created, dissolved, and restructured with ease. Individuals endure. They hold assets, carry insurance and bear responsibility for their conduct. On many occasions, individuals are the wrongdoers.</p>
<p>Plaintiffs who treat the corporate defendant as the endpoint of litigation will continue to obtain judgments against shell companies and wonder why their clients remain uncompensated. Plaintiffs who integrate individual liability into their strategy from the outset—by naming partners, pleading participation, scrutinizing contractual authority, and preserving alter ego theories—are likely to recover more. They will fulfill the fundamental promise of civil law: that wrongdoing leads to meaningful accountability, not empty judgments.</p>
<p><strong>Edward T. Kang</strong> <em>is the managing member of Kang Haggerty. He devotes the majority of his practice to business litigation and other litigation involving business entities. Contact him at <a href="mailto:ekang@kanghaggerty.com">ekang@kanghaggerty.com</a>. </em></p>
<p><strong>Kandis L. Kovalsky</strong><em>, a member with the firm, focuses her practice on a broad range of high stakes business-related civil litigation in Pennsylvania, New Jersey, and New York state and federal courts and arbitral tribunals, and representing relators in high stakes qui tam actions filed under the federal and state False Claims Acts. Contact her at <a href="mailto:kkovalsky@kanghaggerty.com">kkovalsky@kanghaggerty.com</a>. </em></p>
<p><strong><em>Reprinted with permission from the February 19, 2026 edition of “The Legal Intelligencer” © 2026 ALM Global, LLC. All rights reserved. Further duplication without permission is prohibited. Request academic re-use from <a class="text-blue-800 underline hover:no-underline" href="https://www.copyright.com/">www.copyright.com.</a> All other uses, submit a request to <a class="text-blue-800 underline hover:no-underline" href="mailto: asset-and-logo-licensing@alm.com">asset-and-logo-licensing@alm.com.</a> For more information visit <a class="text-blue-800 underline hover:no-underline" href="https://www.law.com/asset-and-logo-licensing/">Asset &amp; Logo Licensing</a>.</em></strong></p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">7298</post-id>	</item>
	</channel>
</rss>
