There is no universal ladder that says “email first, statutory demand second, court third.” The better choice depends on the record, the requester's legal capacity, the jurisdiction, the urgency and the decision the information is meant to support. A low-friction route can be smarter than a formal one; a formal route can be essential when timing, preservation or repeated refusal changes the risk.

Think of the problem as a decision tree rather than an escalation script.

Branch A — use an ordinary governance or business request when cooperation is realistic

Start here when the relationship is functioning, the requested material is ordinary, the recipient is identifiable and there is no immediate reason to preserve a formal legal position.

Examples include asking the company secretary for the current articles, requesting access to a board portal as an authorized director, or asking finance for a defined transaction approval package where the requester's role clearly supports the request.

Advantages: speed, low cost, flexible format and the ability to clarify misunderstandings quickly.

Risks: the request may not preserve a statutory position; the recipient may treat it as optional; a vague email can create a poor record of what was asked and why.

Do not use this branch blindly when: a legal deadline is close, evidence may disappear, the relationship has already broken down, or local law requires a particular form of demand.

Branch B — negotiate a scoped production protocol when the real dispute is about breadth

Sometimes both sides accept that some information should be provided but disagree about volume, date range, confidentiality or custodians. In that situation, the most valuable negotiation is not over abstract rights; it is over a production design.

A useful protocol can specify categories, date windows, sequencing, search terms where appropriate, redaction principles, confidentiality restrictions, file format and a process for raising missing-record issues.

Advantages: turns a binary “yes/no” dispute into manageable work; can reduce collection and review cost; may surface the records that answer the question before anyone fights over the rest.

Risks: an informal compromise may accidentally narrow rights if documented carelessly; endless negotiation can consume the deadline it was supposed to save.

Decision checkpoint: put an expiry date on negotiation. If the parties cannot resolve the defined issues by that date, move to the route local counsel has identified rather than negotiating indefinitely.

Branch C — use a formal statutory inspection route when the statute fits the person, purpose and records

A statutory route can be powerful precisely because it is not a general request for fairness. It has elements. Delaware §220, for example, requires attention to stockholder status, form of demand, proper purpose and the relationship between requested books and that purpose. The UK sections cited below concern the register of members and contain their own request-and-response structure. Canada's federal CBCA sets out categories of corporate records and access mechanisms in sections 20 and 21.

Advantages: defined legal framework, clearer duties and remedies, and a record of compliance or non-compliance.

Risks: technical defects can matter; the route may reach only particular records; using the wrong statute or importing a rule from another jurisdiction can waste time.

Best fit: when local counsel can answer four questions cleanly: Who has the right? Which records are covered? What form and purpose are required? What remedy exists if the company does not comply?

Branch D — use contractual information rights when the agreement is the real source of access

Shareholders' agreements, investment agreements, financing documents and joint-venture agreements can contain information rights that are broader, narrower or simply different from statutory rights. Those rights may include management accounts, budgets, board packs, inspection opportunities or reporting covenants.

The contractual route is often overlooked because teams jump directly to company law. But if the contract says what must be delivered, when and to whom, it may offer a more precise starting point.

Advantages: tailored to the relationship; sometimes clearer about timing and format.

Risks: conditions, notice provisions, confidentiality clauses, dispute-resolution clauses and amendment history matter. A contractual right does not automatically displace statutory law, and the two should not be blended without analysis.

Do not use this branch when: the person asserting access is not a party or beneficiary, the agreement has expired, or the requested category is outside the clause.

Branch E — use litigation discovery only when there is actual litigation and the procedural route fits

Inspection rights and litigation discovery are not synonyms. Delaware §220 itself makes clear that it does not erase a stockholder's discovery rights as a litigant. Other jurisdictions similarly separate pre-suit corporate access mechanisms from procedural disclosure in a live case.

If litigation already exists, counsel may decide that the procedural rules of the case are the correct route for some information. That decision depends on forum, pleadings, relevance, proportionality, privilege and case-management orders.

Advantages: court-supervised process and tools designed for disputed evidence.

Risks: litigation is expensive, slow and strategically consequential. Filing a claim merely to obtain documents can create issues far beyond document access.

When not to choose it: when there is no viable substantive claim, when a narrower inspection or contractual route is available, or when the information is needed before litigation decisions can responsibly be made.

Branch F — seek court enforcement of an inspection right when the dispute is mature enough

A formal inspection route can end in court if the company refuses, narrows, delays or challenges the request and the applicable law provides a remedy. At that stage, the question is no longer “Would you please send this?” It becomes whether the legal elements have been met and what relief the court can grant.

Advantages: a decision-maker can resolve standing, purpose, scope and compliance disputes.

Risks: proof matters. Weak demand wording, unclear purpose, poor entity identification or an overbroad record list can become part of the court record.

Before filing, audit the request as if you were opposing it. Can you prove status? Can you explain why each category matters? Is the purpose lawful and accurate? Did you comply with form and service requirements? Is there a simpler remedy for the urgent question?

A practical choice matrix

Path Best when Cost profile Main control risk
Ordinary request relationship works, ordinary records low treated as optional or too vague
Negotiated protocol right partly accepted, scope disputed low to medium negotiation drifts past deadlines
Statutory demand statute clearly fits capacity and records medium technical or scope defects
Contractual route agreement contains usable information rights low to medium clause conditions or dispute forum missed
Litigation discovery live case already exists high proportionality, privilege, case strategy
Court enforcement mature refusal under applicable inspection law high burden of proof and procedural error

The rows are not a ranking. They describe different legal and commercial tools.

The decision tree in plain language

Question 1: Is there a clear cooperative route that can deliver the needed information in time? If yes, use it but document scope and purpose.

Question 2: Is the disagreement really about how much, rather than whether any access exists? If yes, negotiate a staged protocol with a deadline.

Question 3: Is there a statute or contract that clearly matches the requester's current capacity and the record category? If yes, have local counsel check the formal elements before invoking it.

Question 4: Is there already litigation? If yes, coordinate any inspection request with discovery strategy; do not run two processes that contradict each other.

Question 5: Has a formal right been refused or frustrated? If yes, assess the enforcement remedy, evidence and economics rather than sending an endless series of increasingly angry letters.

Three mistakes that make every branch worse

The first is mixing entities: asking a parent for records held by a subsidiary without analyzing control or the applicable route. The second is mixing legal capacities: switching between “shareholder,” “director” and “investor” as if they were interchangeable. The third is mixing purposes: one paragraph says valuation, another says suspected misconduct, and a third says preparation for litigation, without explaining what records serve which purpose.

A good route is therefore not the most aggressive route. It is the route whose legal source, scope, timing and decision value can all be explained on one page.

One more branch people miss: pause and verify before choosing any route

Sometimes the correct next move is not another request at all. It is a short verification phase. That is especially true where the requester has inherited old cap-table information, where a former director may no longer hold office, where a shareholder agreement has been amended, or where the business uses a trading name that differs from the incorporated entity.

A verification phase can be deliberately narrow: obtain the current corporate extract, confirm the governing law, locate the executed investment or shareholder agreement, identify the present company secretary or records contact, and create a chronology of earlier requests. This work may feel slower than sending a formal demand immediately, but it prevents an expensive category error.

There is also a negotiation advantage. A requester who can say, “We have confirmed the entity, our capacity, the governing agreement and the three record categories in issue,” is easier to engage with than someone whose position changes with each email.

Use a stop rule for verification as well. Once the essential identity and route questions are answered, move forward. Research can become another form of delay if nobody defines what fact is needed before action. Record that stop rule in the file so everyone knows when verification is complete and drafting must begin. That simple discipline also makes later QA easier because the team can see which assumptions were verified before the request was sent.

Related Reading

Sources and Scope Notes

These statutes illustrate how sharply access rules can differ by jurisdiction, legal capacity, record category and purpose. They do not create a single global inspection right. Always confirm the current statute, case law, governing documents, entity type, procedural rules and deadlines in the relevant jurisdiction.

General corporate-governance information only, not legal advice. Inspection rights, procedures, confidentiality duties and remedies vary materially by jurisdiction, entity type, legal capacity and facts. Qualified local professionals should confirm current law, governing documents and deadlines before action.