The most useful records file is not the thickest one. It is the one that lets a reviewer answer, in order: which entity is involved, what capacity the requester has, what question is being investigated, which record category can answer it, what was actually requested, and how the company responded. If those links are missing, even a large document collection can be difficult to use.

The examples below are organized as short file “autopsies”: what went wrong, what corrected the file, what the correction revealed, and the rule that can be reused. They are not statements that every shareholder, director, creditor, employee, or litigant has the same inspection rights.

File autopsy 1: the request targeted a brand, not the legal entity

Background. A requester has a dispute involving a business known publicly by one brand name. The demand, invoices, cap table, and board materials actually refer to several legal entities.

What went wrong. Everything was saved in one folder labeled with the brand. No one recorded which corporation owned the shares, which corporation signed the transaction, or which board approved it.

Correction. Build a one-page entity sheet: exact legal name, incorporation jurisdiction, registration number where available, relationship to the requester, and the record custodian. Attach the constitutional documents and a simple group chart.

What the correction reveals. A record that looks “missing” may belong to another entity. It also becomes possible to identify which legal regime must be checked.

Reusable rule. Before collecting disputed records, prove the identity of the entity that should possess them.

File autopsy 2: status was asserted but not evidenced

Background. The request says “I am a shareholder” or “I am authorized to act,” but the file contains only an old email or a screenshot.

What went wrong. The legal capacity of the requester was treated as background rather than evidence.

Correction. Preserve current status material that fits the actual route: securities-register entry, share certificate, brokerage or nominee evidence, director appointment record, creditor instrument, estate authority, or written agency authorization. Keep the date and source of each item.

What the correction reveals. Some routes impose specific proof or authorization requirements. Delaware’s current DGCL §220, for example, contains requirements addressing beneficial owners and demands made through an attorney or other agent.

Reusable rule. A records file should prove not only what is requested, but also why this requester is using this route.

File autopsy 3: the purpose and the document list did not connect

Background. The stated concern is one transaction, but the document list asks for “all emails, all financial records, all contracts and all board materials.”

What went wrong. The file never explains how a category would answer the investigation question.

Correction. Add a purpose-to-record matrix before expanding the list.

Investigation question Record category to test first What the file should preserve
Who approved a transaction? board minutes, resolutions, written consents final version, meeting date, approval status
What did owners receive? shareholder notices and general communications complete notice, attachments, send date
Who was recorded as holding shares? securities or members register dated extract, source, certification if any
What terms were finally approved? executed agreement and approval materials signed version, amendments, approval trail
Was a request narrowed or rejected? demand and response correspondence every version, delivery proof, response date

In Delaware, current §220 expressly ties a stockholder demand to good faith, a proper purpose, reasonable particularity, and records specifically related to that purpose. That is a jurisdiction-specific statutory example, not a universal formula.

What the correction reveals. Some categories can often be removed because they add volume without answering the question. Others need a narrower date range or clearer custodian.

Reusable rule. Every requested category should have a sentence explaining the question it is meant to answer.

File autopsy 4: a clean PDF hid the record’s provenance

Background. The file contains polished PDF exports but no native messages, board-pack distribution record, version history, or explanation of how the PDF was created.

What went wrong. Readability was preserved; provenance was not.

Correction. Where lawful and proportionate, retain the original or native source alongside the working copy. For board materials, keep the distribution email or portal entry, the version used for the meeting, final minutes, and any formal correction trail. For communications, keep complete threads and their attachments rather than isolated screenshots.

What the correction reveals. A draft can be distinguished from an approved record, and a later compilation can be distinguished from what decision-makers actually had at the time.

Reusable rule. A usable evidence file should answer “where did this come from, when did it exist, and which version was operative?”

File autopsy 5: a register was treated as if it were the whole corporate record

Background. A members or securities register is obtained, and the file is labeled “company records.”

What went wrong. A specific statutory record category was confused with a general right to inspect everything.

Correction. Label the category precisely and keep the legal route beside it. Under the UK Companies Act 2006, sections 116–119 concern the register of members: section 116 requires specified information in a request, section 117 provides a five-working-day comply-or-apply-to-court mechanism, and section 119 addresses misconduct connected with requests or disclosure. Those provisions do not become a general gateway to every board or accounting file.

For a corporation governed by the federal Canada Business Corporations Act, section 20(1) lists specified corporate records, while section 20(2) separately addresses accounting and director or committee records. Section 21 gives access mechanisms for records described in section 20(1) and contains separate conditions for securities-register and shareholder-list information.

What the correction reveals. The record category, requester, entity statute, and permitted use may all matter independently.

Reusable rule. Never name a statutory route without naming the record category it actually covers.

File autopsy 6: production arrived, but nobody could prove what was produced

Background. A shared folder appears after weeks of correspondence. The team downloads it and marks the request “complete.”

What went wrong. There is no production log, no reconciliation against the request, and no record of restrictions or redactions.

Correction. Create a production index with date, producing party, file or folder, format, date range, stated redaction, restriction, and unresolved gap. Reconcile it against each requested category.

Delaware’s current §220 text expressly contemplates reasonable restrictions on confidentiality, use, or distribution and allows redaction of portions not specifically related to the stockholder’s purpose. That makes it especially important to preserve restrictions beside the material rather than separating the documents from the conditions under which they were delivered.

What the correction reveals. “Some documents were produced” is different from “the requested category was fully addressed.”

Reusable rule. Treat production as an event that must be logged and reconciled, not as a folder that ends the inquiry.

The minimum evidence pack worth handing to local counsel

A compact review pack can often be organized in nine items:

  1. entity sheet and group chart;
  2. proof of requester status and authority;
  3. one-sentence investigation purpose;
  4. purpose-to-record matrix;
  5. every version of the demand;
  6. proof of delivery and a dated response log;
  7. key records in original or reliably sourced form where lawful;
  8. production index, redaction notes, and use or confidentiality restrictions;
  9. a short gap list identifying what remains unanswered and why it matters.

This is more useful than a large folder with no chronology or category map.

What can change the answer

Inspection and access rules can turn on incorporation jurisdiction, entity type, requester status, the precise record category, purpose, timing, amendments, court decisions, contract terms, litigation posture, privilege, privacy, and confidentiality. The Delaware, UK, and Canadian federal provisions cited here illustrate different systems and should not be blended into one global rule.

As of October 4, 2026, the UK legislation site states that section 116 is up to date with changes known to be in force through October 3, 2026; Canada’s Justice Laws site states that the CBCA is current to September 21, 2026 and last amended March 26, 2026. A specific demand, deadline, entitlement, or enforcement step should still be checked by a qualified professional in the relevant jurisdiction.

Sources

Related Reading