Stone v. Ritter (2006): what Delaware LLC founders should know

Case at a glance

• Case name: Stone v. Ritter
• Year: 2006
• Court: Delaware Supreme Court
• Citation: 911 A.2d 362 (Del. 2006)
• Category: Fiduciary Duty

The facts

AmSouth Bancorporation paid $40 million in penalties for Bank Secrecy Act violations. Shareholders sued directors for oversight failures.

The holding

Caremark-style oversight liability falls under the duty of loyalty (specifically, the duty of good faith), not the duty of care.

To establish liability, plaintiffs must show directors knew they were not discharging fiduciary duties.

Why this case matters

By placing oversight liability under loyalty rather than care, Stone v. Ritter ensured that § 102(b)(7) exculpation provisions do not protect against Caremark claims.

What this means for Delaware LLC founders

LLC manager oversight responsibilities cannot be eliminated by exculpation provisions in the Operating Agreement.

How Stone v. Ritter applies to your LLC

For solo single-member Delaware LLC founders, most fiduciary-duty cases have limited direct application: there is no co-member to owe duties to, and creditor-fiduciary-duty exposure arises only after actual insolvency. The cases become more relevant as the LLC grows:

• Adding co-founders or investors: multi-member LLCs face the full range of fiduciary-duty analysis, though Operating Agreements can modify duties under § 18-1101.
• Manager-managed structures: when non-member managers run the LLC, they owe fiduciary duties to members by default (§ 18-1104).
• Sale or merger transactions: Revlon and Unocal duties translate to LLC change-of-control transactions.
• Member disputes: Court of Chancery jurisdiction over Operating Agreement disputes applies the body of Delaware case law as guidance.

Primary source

The full text of Stone v. Ritter is available through Westlaw, LexisNexis, and Google Scholar. The Delaware Court of Chancery publishes opinions at courts.delaware.gov/chancery. The Delaware Supreme Court publishes opinions at courts.delaware.gov/supreme.

Related cases and concepts

For broader Delaware corporate and LLC case law context, see our coverage of the business judgment rule, fiduciary duties, Delaware Court of Chancery, and the Delaware LLC Act. The Delaware Limited Liability Company Act sections (6 Del. C. § 18-101 et seq.) interact with the body of Delaware case law to define LLC governance.

See all cases in the Delaware Case Law Library →

What facts brought Stone v. Ritter before the Delaware Supreme Court?

The dispute grew out of compliance failures at AmSouth Bancorporation. According to the record of this case, AmSouth paid roughly $40 million in penalties tied to Bank Secrecy Act violations. Those penalties became the trigger for shareholders, who argued that the directors had failed in their responsibility to keep watch over the company. The shareholders did not claim that the directors personally profited from the violations or that they signed off on the misconduct. Instead, the theory was about inattention, namely that the board allegedly did not maintain the kind of monitoring system that would have surfaced the problems before they grew into multimillion-dollar liabilities.

That framing matters because it set up a specific legal question rather than a generic complaint about bad results. A company can lose money, pay fines, and suffer reputational harm without its directors having breached any duty. The shareholders in this matter had to show something more than an unfortunate outcome. They had to connect the penalties to a failure of board oversight that the law would actually recognize as a breach. The Delaware Supreme Court, hearing the case in 2006, used these facts to clarify exactly when an oversight claim can succeed and which fiduciary duty such a claim belongs to. The factual backdrop of large regulatory penalties paired with an allegation of board inattention is what made the case a useful vehicle for that clarification.

What legal question did the court actually have to answer?

Stripped to its core, the case asked when directors can be held personally liable for failing to monitor a corporation, and under which fiduciary duty that failure should be analyzed. Before this decision, the controlling framework came from the earlier Caremark line of reasoning, which described oversight obligations but left some uncertainty about how those obligations fit within the traditional duties of care and loyalty. The shareholders wanted oversight liability treated as a freestanding category or as part of the duty of care. The directors wanted the bar set high enough that ordinary lapses would not expose them to personal liability.

The court therefore had to do two things at once. First, it had to decide whether a board's failure to install or heed a reporting system was the type of conduct that breaches fiduciary duty at all. Second, it had to locate that conduct within Delaware's structure of director duties, because the answer to where the duty sits determines how easy or hard it is to escape liability. Delaware law lets companies adopt provisions that shield directors from money damages for certain breaches, so the placement question was not academic. If oversight liability lived under the duty of care, those shields might apply. If it lived under loyalty, they would not. The court's task was to resolve that placement with a clear rule that lower courts and corporate planners could rely on going forward.

What did the court hold about oversight liability?

The Delaware Supreme Court held that Caremark-style oversight liability falls under the duty of loyalty, and more precisely under the obligation to act in good faith, rather than under the duty of care. This was the central move of the decision. Oversight failures are not treated as careless mistakes about business judgment. They are treated as a question of whether directors honored their fundamental obligation of loyalty to the company by maintaining and attending to a system for catching legal and operational problems.

The holding also set a demanding standard of proof. To establish liability, plaintiffs must show that the directors knew they were not discharging their fiduciary duties. That is a high bar. It is not enough to point to a bad outcome, a missed warning sign, or a compliance program that turned out to be imperfect. The claimants must demonstrate a conscious disregard of known responsibilities. In practical terms, the court described two ways an oversight claim can be made out, summarized below.

• The directors utterly failed to implement any reporting or information system or controls at all.
• Having implemented such a system, the directors consciously failed to monitor or oversee its operation, which prevented them from being informed of risks or problems requiring their attention.

Either route requires a showing that the board acted with scienter, meaning a knowing or conscious failure. By framing the test this way, the court kept oversight liability serious but rare, reserving it for genuine abdication rather than honest error.

Why did placing oversight under loyalty rather than care matter so much?

The distinction looks technical, but it carried real weight because of how Delaware lets corporations protect their directors. Under section 102(b)(7) of the Delaware corporate statute, a company may adopt a charter provision that eliminates director liability for money damages arising from breaches of the duty of care. That kind of exculpation provision is common, and it gives directors comfort that ordinary judgment calls will not bankrupt them. Critically, however, the statute does not allow exculpation for breaches of the duty of loyalty or for acts not taken in good faith.

By placing oversight liability under loyalty and good faith, the court ensured that section 102(b)(7) exculpation provisions do not shield directors from Caremark claims. That is the practical engine of the decision. A board cannot draft its way out of oversight responsibility by relying on a standard exculpation clause, because the conduct at issue sits in the one zone the statute refuses to let companies waive. The result is a careful balance. Directors are not on the hook for every compliance hiccup, since the standard requires conscious wrongdoing. At the same time, the duty to maintain meaningful oversight cannot simply be contracted away. This pairing of a high liability threshold with a non-waivable home in the duty of loyalty is what gives the case its lasting influence over how Delaware boards think about monitoring.

How did this decision shape Delaware corporate law?

The decision tidied up an area that had been somewhat unsettled. The earlier Caremark reasoning had introduced the idea that boards owe a duty to be reasonably informed, but it did not fully explain how that duty interacted with the established framework of care, loyalty, and good faith. By assigning oversight liability to the duty of loyalty through the lens of good faith, the 2006 ruling gave courts a stable doctrinal address for these claims. Later Delaware decisions could build on that placement rather than relitigate it.

The decision also reinforced a broader theme in Delaware law, which is that good faith is bound up with loyalty rather than standing as a separate, third fiduciary duty. That framing has shaped how plaintiffs plead oversight cases and how boards structure compliance functions. Directors and their advisers took the practical lesson that documenting the existence and operation of a monitoring system is valuable, because the recognized failures involve either having no system at all or consciously ignoring the one in place. The ruling did not invent new operational mandates, but it clarified the legal consequences of doing nothing, which in turn encouraged boards to be able to show that they were paying attention. For a jurisdiction that hosts a large share of the business entities formed in the United States, a clear and predictable rule on board monitoring carries influence well beyond the single company in the caption.

How does the principle carry over to a Delaware LLC?

Delaware limited liability companies are governed by their own statute and by the operating agreement the members adopt, not by the corporate code that produced this decision. Even so, the underlying principle has a natural counterpart in the LLC world. When an LLC is manager-managed, the managers occupy a role similar to that of directors, and they take on responsibility for keeping an eye on the entity's legal and operational risks. The record of this case frames the takeaway directly, namely that an LLC manager's oversight responsibilities cannot be eliminated by exculpation provisions in the operating agreement.

That carryover is the heart of why a corporate case appears on a page aimed at LLC founders. Operating agreements frequently include broad clauses that limit a manager's exposure, waive certain duties, or exculpate managers from liability. The lesson from this ruling is that there are limits to how far such clauses can push. Just as a corporate charter cannot exculpate a director for a loyalty or good-faith failure, an LLC operating agreement faces boundaries when it tries to erase the obligation to maintain genuine oversight. The exact contours depend on the LLC statute and the specific language drafted, but the conceptual point holds. A clause on paper does not automatically dissolve responsibility for conscious abdication of monitoring. Founders who treat an exculpation provision as a complete shield against any oversight claim may be reading more protection into it than the document can deliver.

What does this mean for an operating agreement's exculpation and indemnity clauses?

Many operating agreements pair an exculpation clause with an indemnification clause. The exculpation clause says managers are not liable for certain conduct, and the indemnification clause says the company will reimburse managers for losses or legal costs. Read against the spirit of this decision, those clauses are most reliable when they target ordinary business judgment and honest mistakes, and least reliable when stretched to cover knowing failures to act in good faith. The case treated conscious disregard of duty as the kind of conduct that sits outside the protected zone for corporate directors, and that framing informs how drafters think about parallel LLC provisions.

For drafting purposes, a few themes tend to follow from this reasoning, offered here as general information rather than as advice for any specific company:

• Distinguish clearly between protecting ordinary judgment and attempting to waive good-faith obligations, since the latter is where courts tend to push back.
• Describe whether the entity is manager-managed or member-managed, because that allocation determines who carries oversight responsibility.
• Consider whether the agreement says anything about maintaining records, controls, or reporting, since the recognized failures involve having no system or ignoring an existing one.
• Treat indemnification as a separate question from exculpation, because reimbursing a loss is not the same as eliminating the underlying duty.

These are structural considerations, not guarantees. The point is that the architecture of an operating agreement should reflect an awareness that some responsibilities resist being drafted away.

How does the case relate to fiduciary duties and contractual freedom under the LLC Act?

Delaware's LLC framework is known for honoring freedom of contract, which lets members shape their internal governance with considerable flexibility. That flexibility includes the ability to modify, and in many respects limit, fiduciary duties through the operating agreement. This decision does not override that flexibility, because it interprets the corporate code rather than the LLC statute. What it offers instead is a cautionary frame for how far contractual freedom realistically reaches when the subject is conscious bad faith.

In the corporate context, the court treated the good-faith component of loyalty as something that cannot be waived through an exculpation provision. The analogous instinct in the LLC setting is that even a regime built heavily on contract tends to preserve a floor against conduct that is knowing and disloyal. Members can expand or narrow many duties, allocate risk between managers and investors, and tailor the standard of conduct to their venture. The takeaway from this case is that drafting freedom and oversight responsibility are not perfect substitutes. A founder can use the operating agreement to set expectations, define the manager's role, and limit exposure for good-faith decisions, while recognizing that conscious disregard of clear responsibilities is the type of conduct courts have historically been reluctant to let any governing document fully excuse. Balancing that freedom against that floor is the practical art of LLC drafting in Delaware.

What is the difference between a bad outcome and a breach under this rule?

One of the most useful lessons from the decision is that losing money is not the same as breaching a duty. AmSouth paid substantial penalties, yet the existence of those penalties did not by itself establish that the directors had done anything legally wrong. The standard the court set requires a showing that the decision-makers knew they were not discharging their responsibilities. That keeps the focus on the state of mind and conduct of the board rather than on the size of the harm.

For an LLC, the same separation is worth internalizing. A venture can face a regulatory fine, a lawsuit, or a costly compliance gap without the manager having breached an oversight duty, provided the manager maintained a reasonable monitoring system and attended to it. Conversely, a manager who consciously ignores known red flags or never sets up any system at all is in a different and more exposed position, even if the eventual harm is modest. The dividing line is knowing abdication, not bad luck. This distinction can reassure founders who worry that any business setback will translate into personal liability, while also signaling that genuine inattention to legal and financial risk is the kind of thing the law treats seriously. Understanding where that line sits helps founders calibrate how much energy to put into documented oversight versus how much to spend insuring against ordinary commercial risk.

What should a non-resident founder take from this case in practical terms?

Many founders who form a Delaware LLC live outside the United States and manage the company remotely. For them, the practical message is that distance does not dilute the oversight role. A manager who lives abroad still carries the responsibility associated with monitoring the entity's compliance and financial health, and an operating agreement clause cannot quietly remove that responsibility for knowing failures. The decision is a reminder that picking Delaware for its flexibility and predictability comes with a recognized expectation that whoever runs the company pays attention to it.

In day-to-day terms, a non-resident founder can treat the case as encouragement to build simple, documented habits rather than to rely solely on protective language in the agreement. Helpful steps, framed as general information, include the following:

• Keep basic records that show the company has a system for tracking legal, tax, and financial obligations.
• Periodically review reports or updates rather than assuming silence means everything is fine.
• Understand which duties the operating agreement modifies and which obligations are harder to waive.
• Treat exculpation and indemnification clauses as useful but limited, not as a substitute for actually monitoring the business.

None of this requires a board or elaborate compliance department. It requires demonstrating that the person responsible for the company has not abandoned the oversight role, which is precisely the conduct the court treated as the dividing line.

Why does a 2006 corporate decision still inform Delaware LLC planning?

It is fair to ask why founders forming an LLC should care about a decision about corporate directors at a bank holding company. The answer lies in how Delaware law develops. The corporate case law is deep and well reasoned, and courts and drafters frequently borrow its concepts when thinking through analogous LLC questions, especially around loyalty, good faith, and the limits of waiver. This decision is one of the clearest statements of where oversight liability sits and why certain protections do not reach it, so it serves as a reference point even outside the corporate setting.

For an LLC founder, the value is conceptual rather than mechanical. The LLC statute and operating agreement govern the entity directly, but the reasoning here helps explain why a sweeping exculpation clause may not do everything a founder hopes, and why building a habit of oversight is sensible regardless of how the agreement is worded. The record summarizes the bridge to the LLC world by noting that manager oversight responsibilities cannot be eliminated through exculpation provisions in the operating agreement. That single sentence captures the practical inheritance of the case. Treated as general legal information rather than tailored advice, the decision encourages founders to combine Delaware's genuine contractual flexibility with a realistic understanding that some responsibilities are designed to endure. That blend of freedom and accountability is a recurring feature of Delaware entity law, and this case is one of the cleaner illustrations of it.