In re Marvell Technology Group Ltd. Stockholder Litigation (2017): what Delaware LLC founders should know

Case at a glance

• Case name: In re Marvell Technology Group Ltd. Stockholder Litigation
• Year: 2017
• Court: Delaware Court of Chancery
• Citation: (unpublished)
• Category: Books & Records

The facts

Stockholder demanded books and records.

The holding

§ 220 demand framework applied.

Why this case matters

Books-and-records demand practice.

What this means for Delaware LLC founders

LLC § 18-305 information rights parallel § 220.

How In re Marvell 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 In re Marvell Technology Group Ltd. Stockholder Litigation 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 dispute brought this matter before the Court of Chancery?

In re Marvell Technology Group Ltd. Stockholder Litigation arose in the Delaware Court of Chancery in 2017 and sits in the books-and-records category of Delaware corporate disputes. At its core, the matter involved a stockholder who asked the company to hand over internal documents. That request, often called a demand, is the practical starting point for an investor who suspects something has gone wrong but does not yet have enough information to file a substantive lawsuit. The record here is unpublished, which is common for procedural and document-access rulings, and it means the value of the decision lies in how it applied an existing framework rather than in any sweeping new pronouncement.

The framework at issue traces to Section 220 of the Delaware General Corporation Law, the statute that lets a stockholder inspect certain corporate books and records when the request is made for a proper purpose. The dispute was not about whether the underlying business decisions were right or wrong. It was about access: which records a stockholder may see, what the stockholder must show to earn that access, and how narrowly a court will draw the boundaries of an inspection. Reading the case this way keeps it grounded in what the record actually supports, namely the application of the Section 220 demand standards to a real stockholder request rather than a verdict on management conduct.

What legal question did the demand actually raise?

The central question was procedural but consequential. When a stockholder serves a demand under Section 220, the company can either comply, comply in part, or refuse. If it refuses or limits the production, the stockholder may bring the dispute to the Court of Chancery, and the court must decide whether the statutory conditions for inspection have been met. Those conditions are not a formality. The stockholder has to be an actual record or beneficial holder, the demand has to follow the form and manner the statute prescribes, and, most importantly, the stockholder has to state a proper purpose reasonably related to that person's interest as a stockholder.

In this matter the court worked through that demand framework rather than reinventing it. The practical question becomes whether the stated purpose, such as investigating possible mismanagement or wrongdoing, rests on a credible basis or whether it is merely a fishing expedition. Delaware courts have long required some evidence, not proof, that something warrants a closer look. The court also had to weigh scope: even where inspection is allowed, the documents produced should be those that are essential and sufficient to the stated purpose, not every file the company holds. The decision is useful precisely because it shows these familiar standards being applied to concrete facts, which is how doctrine stays alive and predictable for the next investor who serves a demand.

What did the court hold, and what doctrine did it apply?

The holding, as reflected in the record, applied the Section 220 demand framework to the stockholder's request. Rather than announcing a brand new rule, the court measured the demand against the settled elements: standing as a stockholder, compliance with statutory form, and a proper purpose backed by a credible basis. The doctrine being applied is the long-standing Delaware approach to inspection rights, which treats access to records as a qualified right rather than an unconditional one. A stockholder is not entitled to roam freely through corporate files, but a stockholder who clears the threshold is entitled to the records that genuinely serve the approved purpose.

Several principles sit underneath that approach and are worth naming plainly:

• The burden generally rests on the stockholder to show a proper purpose and, where the purpose is investigating wrongdoing, a credible basis to suspect it.
• The scope of any inspection is tailored to the purpose, so the court limits production to documents that are essential and sufficient.
• Books-and-records actions are meant to be summary in nature, resolved quickly rather than turned into full-blown litigation about the merits.
• The remedy is access to information, not damages, which keeps the proceeding focused on a narrow factual question.

Why does a books-and-records ruling matter so much in Delaware?

Books-and-records demands occupy a special place in Delaware practice because they are often the first step before any larger fiduciary claim. Delaware courts have repeatedly encouraged stockholders to use the tools at hand, meaning Section 220, before filing a derivative or class action that alleges breaches of duty. The reasoning is that a well-informed complaint, built on actual documents, is more likely to survive early dismissal and less likely to waste the court's time. A decision like this one reinforces that pathway by showing how the threshold works in practice and how scope is policed.

For the broader system, predictability is the point. Companies need to know what they are obligated to produce so they can respond without overreacting, and investors need to know what they must demonstrate so they can frame a demand that will not be dismissed. When the Court of Chancery applies the demand standards consistently, both sides can plan. That consistency is part of why Delaware remains a default home for entity formation. The law is not just written down, it is applied in a steady stream of cases that fill in the contours, and inspection disputes are a recurring and well-mapped corner of that body of law.

How does the corporate principle translate to a Delaware LLC?

The corporation statute and the limited liability company statute are different texts, but they share a family resemblance on information rights. Section 220 governs stockholders of a corporation, while Section 18-305 of the Delaware Limited Liability Company Act governs the information rights of members and managers in an LLC. As the case record itself notes, the LLC provision parallels the corporate one. A member who has a purpose reasonably related to membership can generally seek information and records about the company, subject to conditions and reasonable standards.

The translation is not perfect, and the differences matter. The LLC Act gives the operating agreement substantial room to define, expand, or restrict information rights, which the corporate statute does not allow to the same degree. That means the lessons from a Section 220 dispute carry over in spirit, namely that information access is a qualified right tied to a legitimate purpose, while the precise mechanics for an LLC depend heavily on what the operating agreement says. A founder reading this case for LLC guidance should treat it as a map of how courts think about access, then check that map against the contract that actually governs the company.

What should the operating agreement say about information rights?

Because Section 18-305 lets the operating agreement shape information rights, the agreement is where the real decisions get made. A thoughtfully drafted agreement does not leave members guessing about what they can request, when, and in what form. It can also protect the company from disruptive or competitively dangerous requests by setting reasonable conditions. The contractual flexibility that Delaware grants is a feature, but it only helps if the drafters use it deliberately rather than relying on silence.

Common items an operating agreement may address include the following:

• Which records the company will maintain, such as the member ledger, tax filings, and financial statements.
• The purposes for which a member may inspect, and any requirement to state that purpose in writing.
• Reasonable notice periods, the place and time of inspection, and who bears copying costs.
• Confidentiality undertakings that protect sensitive information once it is produced.
• Any agreed limits on the rights of members who also compete with the company, where permitted.

These provisions do not eliminate disputes, but they reduce the chance that a disagreement turns into expensive litigation over basics that the parties could have settled in advance.

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

A founder who lives outside the United States and forms a Delaware LLC inherits the same statutory backdrop as anyone else, including the information rights in Section 18-305 and the broad contractual freedom of the LLC Act. The practical takeaway from a books-and-records case is that information flow inside a company is governed by rules, and those rules become most visible when trust breaks down. Planning for that moment while relationships are still good is far easier than improvising during a conflict.

For a non-resident in particular, a few points tend to be worth attention. Records should be kept in good order and in a form that can be shared if a legitimate request arrives, because distance and time zones make scrambling for documents painful. The operating agreement should be clear about who can see what, so a co-founder in another country is not left wondering whether a request is proper. And it helps to understand that Delaware treats inspection as a qualified right tied to purpose, which means both demanding members and responding managers have obligations. None of this is a substitute for advice on a specific situation, but it frames the questions a founder can usefully raise with counsel before problems appear.

How does this connect to fiduciary duties inside an LLC?

Information rights and fiduciary duties are closely linked. In the corporate world, a Section 220 demand is often the gateway to a later claim that directors or controllers breached their duties of care or loyalty, because the records reveal what actually happened. In an LLC, the connection can be similar, since a member who suspects that a manager has acted disloyally may first want the documents that show how decisions were made and whether conflicts were handled properly. Access to information is, in that sense, the practical engine behind accountability.

Delaware's LLC Act takes a distinctive position on duties. It permits the operating agreement to expand, restrict, or even eliminate fiduciary duties, with the notable exception that the implied contractual covenant of good faith and fair dealing cannot be eliminated. This matters when reading a books-and-records case through an LLC lens, because the scope of a member's legitimate purpose may depend on what duties survive in the agreement. If duties have been narrowed by contract, the universe of wrongdoing a member can credibly investigate may narrow with them. The interplay between what records reveal and what duties exist is part of why drafting and information rights should be considered together rather than in isolation.

How does contractual freedom under the LLC Act change the analysis?

Delaware describes its LLC statute as built on the policy of giving maximum effect to the principle of freedom of contract and to the enforceability of operating agreements. That policy is more than a slogan. It tells courts to honor what the parties agreed unless a specific statutory limit or the implied covenant of good faith and fair dealing requires otherwise. For information rights, this means the analysis often begins with the contract rather than the default rule, which is the reverse of how a pure Section 220 corporate analysis tends to start.

The consequence is that two LLCs can have very different information regimes even though they operate under the same statute. One operating agreement might grant generous, almost automatic access to financial records, while another might condition access on stated purposes and confidentiality terms. A founder who understands this can decide deliberately where to land on that spectrum. The discipline that a books-and-records case models, namely tying access to a legitimate purpose and a reasonable scope, is a sensible baseline to carry into the drafting conversation even when the statute would let the parties choose something quite different.

How should a member frame a request for company records?

Whether the entity is a corporation or an LLC, a well-framed request tends to move faster and meet less resistance than a vague one. The lesson from inspection practice is that purpose and scope drive the outcome. A request that names a specific, legitimate reason and asks for the records that actually serve that reason is far stronger than a sweeping demand for everything. Courts in Delaware have rewarded the former approach and trimmed the latter, which is exactly the kind of scope discipline a books-and-records decision illustrates.

A member preparing a request might think through several questions in advance:

• What is the concrete purpose, and how does it relate to membership rather than an outside interest?
• Which specific records are essential and sufficient to address that purpose?
• Does the operating agreement set a process, a notice period, or a form for the demand?
• Are there confidentiality expectations that should be acknowledged up front?
• Is the request narrow enough that a court would view it as reasonable rather than a fishing expedition?

Framing a request this way does not guarantee any particular result, but it aligns the demand with how Delaware courts evaluate access, which tends to reduce friction for everyone involved.

What are the limits of reading a single unpublished decision?

It is worth being candid about how far a single, unpublished ruling can be pushed. An unpublished decision applies established law to particular facts and does not carry the same precedential weight as a published Supreme Court opinion. Reading too much into it would be a mistake. The honest description of this matter is that it applied the Section 220 demand framework to a stockholder request, and its usefulness lies in showing those standards in action rather than in any new rule it created.

That modesty is actually helpful for a founder. The takeaways here are general and durable because they rest on the broader framework, not on the specific outcome of one dispute. The idea that information access is a qualified right, that purpose and scope matter, and that the LLC analog in Section 18-305 runs through the operating agreement are all points that hold regardless of how any single case came out. Treating the decision as one data point in a large and consistent body of Delaware law, rather than as a controlling authority on its own, is the accurate way to use it.

Where does this leave a founder thinking about Delaware formation?

Pulling the threads together, a books-and-records dispute is a window into how Delaware balances the interests of those who run a company and those who invest in it. The corporate rule under Section 220 and the LLC rule under Section 18-305 both recognize that owners need a way to see inside the entity, while companies need protection from open-ended intrusions. The balance is struck through purpose and scope, and the LLC version of that balance is largely set by the operating agreement under Delaware's strong contractual freedom policy.

For a founder, the constructive response is to plan information rights and duties together, early, and in writing. This is general legal information rather than advice for any particular company, and the right structure depends on facts that vary from one venture to the next. Still, the direction is clear enough to be useful: keep good records, define access in the operating agreement, understand how duties can be shaped by contract, and remember that the same logic Delaware applies to corporate inspection demands informs how a court is likely to think about an LLC member's request for information.