<?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>The Harvard Law School Forum on Corporate Governance</title>
	<atom:link href="https://corpgov.law.harvard.edu/2026/09/30/court-of-chancery-enforces-earnout-procedural-protections/feed/" rel="self" type="application/rss+xml" />
	<link>https://corpgov.law.harvard.edu</link>
	<description>The leading online blog in the fields of corporate governance and financial regulation.</description>
	<lastBuildDate>Wed, 30 Sep 2026 11:32:16 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.11</generator>

<image>
	<url>https://corpgov.law.harvard.edu/wp-content/uploads/2024/02/cropped-photography-4-e1706898544564-1-32x32.png</url>
	<title>Court of Chancery Enforces Earnout Procedural Protections &#8211; The Harvard Law School Forum on Corporate Governance</title>
	<link>https://corpgov.law.harvard.edu</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Court of Chancery Enforces Earnout Procedural Protections</title>
		<link>https://corpgov.law.harvard.edu/2026/09/30/court-of-chancery-enforces-earnout-procedural-protections/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=court-of-chancery-enforces-earnout-procedural-protections</link>
		<comments>https://corpgov.law.harvard.edu/2026/09/30/court-of-chancery-enforces-earnout-procedural-protections/#respond</comments>
		<pubDate>Wed, 30 Sep 2026 11:30:17 +0000</pubDate>
<!-- 		<dc:creator><![CDATA[]]></dc:creator> -->
				<category><![CDATA[Delaware Law Series]]></category>
		<category><![CDATA[Practitioner Publications]]></category>
		<category><![CDATA[delaware]]></category>
		<category><![CDATA[Delaware cases]]></category>
		<category><![CDATA[Delaware Court of Chancery]]></category>
		<category><![CDATA[Earnout Procedural Protections]]></category>

		<guid isPermaLink="false">https://corpgov.law.harvard.edu/?p=184094?d=20260929141953EDT</guid>
		<description><![CDATA[The Delaware Court of Chancery recently ordered a buyer to provide information necessary for sellers to participate in a negotiated earnout process, while rejecting the buyer’s effort to impose unwritten limits on earnout credit. Winton v. The North Highland Co. LLC, C.A. No. 2026-0138-LWW (Del. Ch. Sept. 18, 2026). The decision illustrates how the implied [&#8230;]]]></description>
				<content:encoded><![CDATA[<hgroup><em>Posted by David A. Katz, Kevin S. Schwartz and Jenna E. Levine, Wachtell Lipton Rosen & Katz, on Wednesday, September 30, 2026 </em><div class='e_n' style='background:#F8F8F8;padding:10px;margin-top:5px;margin-bottom:10px;text-indent:2.5em;'><strong style='margin-left:-2.5em;'>Editor's Note: </strong> <p style="margin:0; display:inline;"><a title="https://www.wlrk.com/attorney/dakatz/" href="https://communications.wachtell.com/email_handler.aspx?sid=6f4bbc30-1773-4fe0-b553-17468b19aa62&amp;redirect=https%3a%2f%2fwww.wlrk.com%2fattorney%2fdakatz%2f&amp;checksum=8D9F0873" target="_blank" rel="noopener nofollow" data-saferedirecturl="https://www.google.com/url?q=https://communications.wachtell.com/email_handler.aspx?sid%3D6f4bbc30-1773-4fe0-b553-17468b19aa62%26redirect%3Dhttps%253a%252f%252fwww.wlrk.com%252fattorney%252fdakatz%252f%26checksum%3D8D9F0873&amp;source=gmail&amp;ust=1788450694230000&amp;usg=AOvVaw3orVGvtokR2hbowIPyR1Al">David A. Katz</a>, <a title="https://www.wlrk.com/attorney/ksschwartz/" href="https://communications.wachtell.com/email_handler.aspx?sid=6f4bbc30-1773-4fe0-b553-17468b19aa62&amp;redirect=https%3a%2f%2fwww.wlrk.com%2fattorney%2fksschwartz%2f&amp;checksum=C80F556B" target="_blank" rel="noopener nofollow" data-saferedirecturl="https://www.google.com/url?q=https://communications.wachtell.com/email_handler.aspx?sid%3D6f4bbc30-1773-4fe0-b553-17468b19aa62%26redirect%3Dhttps%253a%252f%252fwww.wlrk.com%252fattorney%252fksschwartz%252f%26checksum%3DC80F556B&amp;source=gmail&amp;ust=1788450694230000&amp;usg=AOvVaw3nZxDn6QO4oUKpjWXN0b1L">Kevin S. Schwartz</a>, and <a href="https://www.wlrk.com/attorney/jelevine/" target="_blank" rel="nofollow noopener">Jenna E. Levine</a> are Partners at Wachtell Lipton Rosen &amp; Katz. This post is based on a Wachtell Lipton memorandum by Mr. Katz, Mr. Schwartz, Ms. Levine, and <a href="https://www.wlrk.com/attorney/zmdavid/">Zachary David</a>, all at Wachtell Lipton.</p>
</div></hgroup><p>The Delaware Court of Chancery recently ordered a buyer to provide information necessary for sellers to participate in a negotiated earnout process, while rejecting the buyer’s effort to impose unwritten limits on earnout credit.<a href="https://courts.delaware.gov/opinions/download.aspx?id=401160"><em> Winton v. The North Highland Co. LLC</em>, C.A. No. 2026-0138-LWW (Del. Ch. Sept. 18, 2026)</a>. The decision illustrates how the implied covenant of good faith and fair dealing, though narrowly and carefully applied under Delaware law, can preserve a negotiated earnout procedure without expanding the parties’ substantive written bargain.</p>
<p>North Highland, the buyer, acquired technology consulting firm The Bridge for cash, rolled equity, and an earnout tied in part to profits from new buyer projects. The agreement required the seller representative to notify buyer of potential qualifying projects and the parties to agree on their classification before client proposals were submitted. But it didn’t specify how the representative would obtain the information to do so. After closing, the buyer withheld pricing data and provided curated reports that excluded projects it unilaterally deemed ineligible.</p>
<p>The Court held that the implied covenant of good faith and fair dealing required the buyer to furnish the information necessary to make the agreed process work. The buyer could not insist on compliance with a notification condition while withholding the means to satisfy it. Taking care to confine the remedy, however, the Court held that the seller representative was entitled solely to periodic reports and disclosures before proposal deadlines to ensure its ability to identify and thus benefit from eligible projects, but not unrestricted real-time access to the buyer’s systems. Specific performance was warranted because damages could not reliably compensate for the lost opportunity to participate in the project classification process.</p>
<p>The Court also rejected the buyer’s efforts to exclude projects based on factors outside the agreement, such as where the work was performed, whom it was for, or whether the seller company participated. The requirement that the parties mutually agree on whether a project qualified did not give the buyer a substantive veto; it required them to apply the contractual revenue-based test. Although the buyer retained discretion over which projects to pursue and how to operate the business, it could not deny earnout credit on extra-contractual grounds.</p>
<p>As we have <a href="https://www.wlrk.com/FirmMemos/WLRK/WLRK.30000.26.pdf">previously written</a>, precise drafting of earnout procedures can help avoid costly litigation. Parties should specify what information must be supplied and when, how disagreements will be resolved, and ensure that those implementing the agreement understand its terms. The implied covenant remains a narrow safeguard, not a substitute for negotiated protections. But buyers should expect Delaware courts to enforce the procedures they agreed to, continuing their tradition of faithfully interpreting contracts as written and only implying terms strictly necessary to give effect to the parties’ explicit contractual bargain.</p>
]]></content:encoded>
			<wfw:commentRss>https://corpgov.law.harvard.edu/2026/09/30/court-of-chancery-enforces-earnout-procedural-protections/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
