This is a fictional composite scenario created for decision practice. “Northbridge Holdings,” its people, transaction and correspondence are invented. The scenario is not a client story, a reported case, a prediction of legal outcome or a statement that any particular jurisdiction would grant access on these facts.

The point is to show how a weak demand can become more usable when the requester separates entity, capacity, purpose, record category and deadline.

Background: a minority investor sees one number that does not make sense

Northbridge Holdings owns three operating subsidiaries. Elena holds 8% of Northbridge. She is not a director. Two years earlier, investors were told that any acquisition above a stated internal threshold would receive board review, although the exact legal effect of that statement has never been analyzed.

In September, Northbridge announces that one subsidiary has acquired a small logistics company from a seller connected to a director's former business partner. The announcement gives a purchase price but no detail about valuation, conflicts or approval.

Elena compares the price with figures in the prior investor update and thinks it looks high. That is a reason to ask questions. It is not proof of a breach, conflict or overpayment.

The first move is emotionally satisfying and strategically weak

Elena emails the CEO:

Please send me all board minutes, emails, WhatsApp messages, financial models, valuations and contracts relating to the acquisition and every communication with the seller for the last three years.

She adds that refusal will “prove the board has something to hide.”

The company replies that the request is overbroad, includes confidential material and does not identify a legal basis. It offers a call with the CFO instead.

Elena reads the response as stonewalling. Her adviser sees three separate problems in her own email.

First, it does not identify which entity's records matter. Northbridge is the shareholder, but the operating subsidiary signed the acquisition agreement. Second, it does not state Elena's legal capacity with precision beyond the fact that she is an investor. Third, “everything for three years” is not mapped to a defined purpose.

Correction 1: draw the entity and decision map before arguing about documents

The team creates a one-page diagram:

  • Northbridge Holdings — Elena owns 8%; parent board received an investment paper.
  • Northbridge Logistics Inc. — wholly owned subsidiary; signed the acquisition agreement.
  • TargetCo — acquired company.
  • Seller — external entity connected socially, but not yet shown to be legally affiliated with a Northbridge director.

They then list the decisions they actually need to understand:

  1. Who approved the acquisition at parent and subsidiary level?
  2. What conflict information, if any, was disclosed to the relevant decision-makers?
  3. What valuation or financial analysis was presented when price was approved?
  4. Which governing document, agreement or statute — if any — gives Elena access to which record category?

This changes the problem. The team is no longer asking for “the acquisition file.” It is identifying decision nodes.

Correction 2: separate the information question from the accusation

The second draft removes language saying refusal proves wrongdoing. That sentence was rhetorically strong but analytically useless.

Instead, Elena states that she wants to understand the approval process and whether the disclosed relationship was considered. Her adviser flags that the precise formulation of purpose matters differently across jurisdictions and legal routes. If a Delaware §220 route were relevant, for example, proper purpose and reasonable particularity would require careful attention. If the company were governed by another jurisdiction, the rules could be materially different.

The team therefore does not paste a Delaware form onto a non-Delaware company. It asks local counsel to identify the applicable source of any inspection right.

Correction 3: stage the records by probative value

Rather than starting with messages, the revised internal list uses three tiers.

Tier 1 — structure and approval

  • governing documents relevant to approval authority;
  • board or shareholder resolutions approving the acquisition, if any;
  • the board paper or written decision record used for approval;
  • records identifying the directors or officers participating in the decision.

Tier 2 — price and conflict context

  • the valuation summary or financial model actually presented to decision-makers;
  • conflict disclosures or declarations provided for the meeting, if any;
  • final acquisition agreement and amendments, subject to the legal route and confidentiality issues.

Tier 3 — communications

  • only the communications needed to answer a specific gap that remains after Tier 1 and Tier 2.

This staged approach does not assume Elena is legally entitled to every item. It helps her adviser test necessity before turning each category into a formal request.

The company's second response changes the shape of the dispute

After a structured request is sent through the route local counsel considers appropriate, the company agrees to provide the parent board resolution and a redacted investment paper. It says the subsidiary board minutes are held by the subsidiary and objects to producing internal messages. It also proposes a confidentiality undertaking for the investment paper.

This is not a “win” or “loss.” It is new information.

The parent resolution shows that the board approved the investment subject to subsidiary execution. The investment paper contains a short paragraph saying one director disclosed a prior commercial relationship with the seller's principal and did not participate in a portion of the discussion. The redaction obscures the detailed valuation appendix.

Elena now knows more, but still cannot responsibly conclude whether the process was adequate, whether local conflict rules were satisfied or whether the price was fair.

Decision node: what would the valuation appendix actually change?

This is where many requests expand automatically: one redaction appears, so the next letter demands every underlying spreadsheet and email.

Instead, the team writes the decision question first: Would seeing the valuation analysis change whether Elena seeks further governance action, negotiates information access, or considers a formal claim?

They identify two narrower gaps:

  • Which valuation method supported the price?
  • Did the decision-makers receive material assumptions that differ from the assumptions in the earlier investor update?

Those questions point to a defined appendix or model, not three years of communications.

A deadline appears: the company plans a new financing

Two weeks later, Northbridge announces a financing round. Elena must decide whether to participate. The financing does not automatically create a legal right to acquisition records, but it changes the business clock: she now needs enough information to make an investment decision.

The team separates that commercial deadline from any legal deadline. It asks whether a targeted valuation extract can be produced under the proposed confidentiality arrangement while the broader access dispute continues.

The company offers a secure review of the valuation summary but not an unrestricted copy. Local advisers are asked to assess whether that condition is acceptable under the governing route and whether agreeing to it would affect any other rights.

Again, the useful move is not “accept” or “reject” in the abstract. It is to ask what the condition costs and what information it unlocks.

What the scenario teaches about escalation

At this point Elena has several possible paths, none of which can be selected globally without jurisdiction-specific advice:

  • accept a limited review and make the financing decision with the available information;
  • negotiate for a defined additional category;
  • invoke a contractual information right if one actually applies;
  • use a statutory inspection route if the governing law, capacity, purpose and records fit;
  • if a formal right is refused, assess enforcement;
  • if litigation later exists, coordinate any inspection strategy with procedural discovery.

The right choice depends on law, economics, urgency and what each missing record could prove.

The five mistakes avoided on the second pass

Mistake 1: treating a corporate group as one entity. The entity map made clear which board and which records mattered.

Mistake 2: turning suspicion into a conclusion. The revised request described the information problem without declaring a breach before the evidence existed.

Mistake 3: asking for communications before governance records. Structural records narrowed the factual gap first.

Mistake 4: ignoring confidentiality as if it were always a pretext. The team assessed whether controls could unlock information without conceding the underlying legal position.

Mistake 5: letting the request expand because one record was redacted. Each additional category had to answer a stated decision question.

Transferable rule: build a request from the decision backward

The scenario can be reduced to a reusable sequence:

  1. Decision: What will you do differently if the record confirms or disproves the concern?
  2. Entity: Which legal entity made the relevant decision or holds the record?
  3. Capacity: What is your current legal status in relation to that entity?
  4. Purpose: What legitimate, accurately stated reason supports the request under the applicable route?
  5. Record: Which smallest category directly answers that purpose?
  6. Constraint: What confidentiality, privilege, privacy, timing or preservation issue needs separate handling?
  7. Escalation threshold: What refusal or new fact would justify the next route?

If the team cannot answer step 1, it is usually too early to demand step 5.

What could change the analysis entirely

The scenario would look different if Elena were also a director; if an investment agreement contained explicit information rights; if Northbridge were incorporated in a jurisdiction with a different inspection regime; if litigation were already pending; if the relevant record were a statutory shareholder register rather than internal board material; or if there were credible evidence that records were being destroyed.

Those variables are why examples should be used as thinking tools, not copied as demand templates.

The most defensible records request is not the one with the longest list. It is the one in which the entity, capacity, purpose, record and next decision line up — and where the team knows exactly what fact would make it change course.

A second fictional fork: what if the first records weaken the concern?

Assume the secure valuation review shows that the board received two independent price indications and negotiated the purchase price down. It also shows that the director with the prior relationship disclosed it early and did not vote. Those invented facts would not automatically prove the process was flawless, but they would change the information value of a sweeping communications request.

Elena's team should then ask whether any remaining factual gap is material enough to justify more cost. Perhaps the answer becomes “no”: the available records may be sufficient for the financing decision even though Elena still dislikes the transaction. A disciplined records strategy must allow the scope to contract when evidence weakens the original concern.

Now take the opposite fictional fork. Suppose the valuation paper refers to a “conflict memo” that has not been produced, and the approval chronology contains a two-week gap during which the seller and one director renegotiated a material term. Those invented facts could justify a new, specific request for the referenced memo and the communication needed to explain that gap. The request expands because a concrete record created a concrete question — not because the requester became more suspicious in the abstract.

That is the core discipline: every expansion should have an evidentiary trigger and a decision consequence.

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.