Before demanding company records, build the request as if an independent reviewer will ask two questions: Why do you need this category, and what legal route gives you access to it? A disciplined request is faster to assess, easier to negotiate, and less likely to confuse one statutory register with every internal company document.

This checklist is a preparation tool, not a universal statement of inspection rights.

Step 1 — identify the company whose records you want

Write the exact legal entity name, incorporation jurisdiction and, if known, registration number.

If the transaction involved a group, do not write “the group’s records.” List ParentCo, Subsidiary A, Subsidiary B and any relevant vehicle separately. Rights and obligations usually attach to legal entities, not branding families.

Step 2 — state your current legal capacity

Write one line: “I am a current stockholder,” “I am a director,” “I am a creditor,” or another accurate status.

Do not assume a former status continues. Do not combine several roles without explaining which one supports the request.

If capacity is disputed, flag that as the first local-law question.

Step 3 — list the exact record categories

Use a table rather than “all books and records.”

Possible categories include constitutional documents, bylaws, shareholder register, shareholder resolutions, board minutes, committee records, accounting records, transaction agreements, valuations and communications.

The category list matters because statutory access can be narrower than the company’s total record universe.

Step 4 — match every category to a purpose

For each requested category, write what question it answers.

Example: “Board minutes for 1–31 August — to determine whether the 14 August asset sale was authorized and what resolutions were passed.”

If you cannot explain why a category matters, remove it for now or place it in a secondary list.

Step 5 — identify the legal mechanism before sending the demand

Ask local counsel whether the route is a corporate statute, director governance right, contract, shareholder agreement, court disclosure, regulatory process or another mechanism.

Do not blend different mechanisms. A statutory inspection demand may require elements that an informal board request does not; litigation disclosure may have a different scope again.

Step 6 — if relying on Delaware §220, check the current statute carefully

Current DGCL §220 defines specified books-and-records categories and a stockholder demand framework subject to statutory conditions.

Confirm current standing, purpose requirements, form, scope and procedure with Delaware counsel. Do not copy an old demand template without checking amendments and current case law.

Most importantly, do not describe §220 as an automatic right to every email and file.

Step 7 — if relying on UK Companies Act §116, keep the category narrow

Section 116 is about inspection/copies of the register of members and requires specified request information, including purpose. Section 117 addresses the company’s response route; sections 118–119 address consequences and misuse-related issues.

Do not cite section 116 as a general statutory right to all corporate books.

If you need another UK record category, identify the separate legal basis.

Step 8 — for a federal Canadian corporation, distinguish §20 record classes

CBCA section 20(1) lists specified corporate records. Section 20(2) separately requires accounting records and directors/committee minutes and resolutions.

Section 21(1), subject to its terms, concerns access to records described in section 20(1). Do not silently extend that language to all section 20(2) records.

Ask Canadian counsel what other rights or procedures may apply to the requester and desired category.

Step 9 — set a defensible date range

A request for ten years of material about a transaction approved last month may be broader than necessary.

Start from the event chronology: negotiation, board circulation, meeting, approval, closing and immediate follow-up. Expand if earlier decisions or patterns become relevant.

A defined range reduces review cost and makes refusal harder to justify on pure burden grounds, though legal entitlement remains a separate question.

Step 10 — create a preservation track separate from the access track

If you reasonably fear records may be lost, address preservation without pretending preservation equals entitlement.

Identify systems, custodians and device turnover. Use lawful, proportionate measures. Privacy, privilege, employment and data rules may constrain how preservation is implemented.

The company can preserve a record while the parties still dispute whether it should be produced.

Step 11 — identify privilege, privacy and confidentiality issues early

Do not wait until production day to discover that requested material contains legal advice, personal data, trade secrets or third-party restrictions.

Mark likely protected categories and ask how local law handles them. The answer may involve exclusion, redaction, undertakings, confidentiality agreements or court directions.

“Confidential” does not automatically mean “never accessible,” but it does require a protection plan.

Step 12 — preserve provenance

Request native records or reliable copies in a way that does not erase useful metadata where provenance matters.

For minutes and resolutions, identify draft, approved and signed versions. For board portals, preserve distribution history if available. For a spreadsheet, note creation/modification history where relevant.

The evidentiary question is often not only what the document says, but when it existed and who had it.

Step 13 — set the response clock using the actual legal route

Do not invent a universal “seven-day” deadline.

Some statutes prescribe response periods; contracts may set their own; court procedures differ. UK section 117, for example, contains a specific response framework for requests under section 116. Other access routes have different clocks.

Use the correct local timetable and separately mark any transaction closing or litigation deadline.

Step 14 — decide what an acceptable partial response looks like

Not every dispute requires an all-or-nothing response.

A company might provide uncontested records while reserving objections to other categories. The requester may accept a staged production if high-priority materials come first. Protective terms may solve confidentiality concerns.

Define the minimum information needed for the next decision so negotiations do not stall over lower-priority material.

Step 15 — build a refusal matrix before escalation

If access is refused, classify the reason:

  • requester lacks status;
  • purpose disputed;
  • category outside cited statute;
  • request too broad;
  • record not held by this entity;
  • confidentiality/privilege issue;
  • procedural defect;
  • company simply refuses without a clear basis.

Different refusals call for different responses. Correct a curable defect before turning it into a litigation issue.

Step 16 — keep the merits dispute separate

The record-access dispute may be connected to a suspected conflicted transaction, but the two questions are not identical.

Winning access does not prove the transaction was wrongful. Losing a particular access request does not prove the transaction was proper.

Maintain separate files: one for entitlement/access, one for the underlying governance issue.

Step 17 — document what was actually produced

Create a production index with category, date range, source, format, production date and any stated withholding basis.

This prevents repeated demands for the same material and exposes genuine gaps. It also helps an independent adviser see whether the production actually answers the stated purpose.

Step 18 — decide the next move from the gap, not from frustration

After production, ask: what key question remains unanswered?

If the missing item is central and the legal entitlement is strong, escalation may be rational. If the missing material is peripheral, the better move may be to proceed with the evidence already available.

Do not litigate merely because the production was irritating.

A pre-send checklist

Before sending any formal records request, confirm:

  • correct entity;
  • correct requester status;
  • exact legal mechanism;
  • record categories defined;
  • purpose stated honestly;
  • date range justified;
  • category-to-purpose link documented;
  • preservation addressed separately;
  • privilege/privacy/confidentiality considered;
  • current statute and amendments checked;
  • response timetable verified;
  • next irreversible event marked;
  • acceptable staged production considered;
  • escalation route confirmed with local counsel.

If several boxes remain blank, the request is probably not ready.

What a high-quality request sounds like

It is specific without pretending certainty where local advice is still needed. It names the entity, status, purpose, records and date range. It avoids global claims such as “shareholders have a right to all records.” It cites only the mechanism that actually applies and reserves the right to refine scope as evidence develops.

That combination — narrow facts, accurate legal basis, preserved evidence and a clear next decision — makes record access a useful governance tool rather than a sprawling document war.

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

Related Reading

Sources and Scope Notes