A records dispute becomes dangerous when the information problem starts changing legal options, commercial decisions or evidence quality. The warning sign is not simply that somebody said “no.” A reasonable refusal to an overbroad request can be part of an ordinary process. The more serious signals are the ones that shrink time, alter records, change explanations or make it harder to identify the correct entity and route.

Use the following eight signals as an escalation checklist. One signal rarely proves misconduct. Several together can justify faster local advice and tighter evidence preservation.

1. The reason for refusal keeps changing

Monday's answer is “we do not have it.” Thursday's answer is “you are not entitled to it.” The next week it becomes “the request is too broad.” Different objections can all be legitimate, but a moving explanation makes it difficult to know what issue actually needs to be fixed.

Why it matters: you cannot efficiently narrow a request if the target keeps moving.

Action: build a dated refusal log. Quote the reason, identify who gave it, note what category it applied to, and record your response. Ask the company to separate objections by category rather than giving one blanket answer.

2. Nobody will confirm which legal entity holds the records

The group uses one brand, but the transaction touches a parent, operating company and special-purpose vehicle. Repeated requests produce answers such as “not our file” without saying whose file it is.

Why it matters: rights generally attach to legal entities and legal capacities. Entity confusion can make an otherwise sensible request defective.

Action: obtain the corporate chart, exact company names and incorporation jurisdictions. Map each requested category to the entity most likely to create or control it.

3. Records appear to be disappearing, moving or becoming inaccessible

A board portal account is disabled, a shared drive changes, staff leave, a messaging channel is deleted, or a data room is closed while the dispute is developing. None of those events automatically proves spoliation; businesses routinely change systems and permissions.

Why it matters: the practical ability to reconstruct events can deteriorate quickly.

Action: preserve what you lawfully possess, keep original metadata where possible, and ask local counsel whether a preservation notice or other step is appropriate. Do not access systems without authorization or copy information you are not entitled to take.

4. A transaction or vote will happen before the information issue can be resolved

A shareholder vote, sale, financing, dividend decision or board approval is scheduled while the request is outstanding.

Why it matters: information that arrives after the decision may have much less practical value even if access is later established.

Action: put the business deadline next to the legal deadline. Ask which information is truly decision-critical and whether a narrower first tranche could be produced quickly. Local advice may be needed on any formal relief; do not assume an inspection request automatically pauses a transaction.

5. The company starts offering summaries instead of source records without explaining why

Management may provide a spreadsheet or narrative that answers some questions but not the underlying minutes, resolutions or register entries.

Why it matters: a summary can be useful, but it is not always a substitute for the record needed to test provenance, approval sequence or wording.

Action: identify exactly what decision the source record would change. Avoid demanding originals merely because they feel more authoritative; explain the evidentiary gap the summary leaves open.

6. Confidentiality becomes a blanket answer to every category

Confidentiality can be a real concern. Delaware §220, for example, expressly contemplates reasonable restrictions on confidentiality, use or distribution in the circumstances described by the statute. But “confidential” is not a universal explanation for every record in every jurisdiction.

Why it matters: the dispute may be capable of solution through a protocol rather than total refusal.

Action: separate categories by sensitivity. Offer to discuss redactions, limited recipients, secure review, undertakings or other locally appropriate controls without conceding rights you have not analyzed.

7. Your own stated purpose keeps changing

The first request says valuation. The second says suspected conflict. The third says litigation preparation. The record categories also change each time.

Why it matters: inconsistency weakens decision discipline and, in some regimes, purpose is legally important. Delaware §220 expressly links inspection to a proper purpose and requires reasonable particularity.

Action: write one purpose statement and a purpose-to-record map. If new facts legitimately change the purpose, document why rather than pretending the first request never existed.

8. Parallel proceedings begin to overlap

A shareholder inspection demand exists alongside employment claims, regulatory inquiries, arbitration or court litigation.

Why it matters: different procedures may have different disclosure rules, confidentiality obligations and strategic consequences. One team can accidentally make representations that undermine another process.

Action: create a single chronology and route matrix. Identify what each proceeding can seek, who controls it, and which statements or productions must be coordinated.

The escalation test: urgency × evidence risk × decision impact

Score the problem qualitatively on three axes:

  • Urgency: Is there a near-term vote, transaction, filing or limitation issue?
  • Evidence risk: Is access changing, are custodians leaving, or are systems being altered?
  • Decision impact: Will the missing record materially change what the requester does next?

If all three are low, disciplined negotiation may be better than immediate escalation. If two or three are high, faster jurisdiction-specific advice is sensible even before the parties agree on the ultimate merits.

What is not automatically a red flag

A company asking you to narrow a huge request is not, by itself, suspicious. A request for proof of status can be routine. Redactions can be appropriate. A reasonable confidentiality proposal is not the same as concealment. And a short delay caused by identifying old archives does not establish bad faith.

The purpose of a warning-sign checklist is to distinguish friction from deterioration. Escalate because time, evidence or decision quality is getting worse — not simply because the correspondence has become unpleasant.

A reusable next-step checklist

  • Exact entity and incorporation jurisdiction confirmed.
  • Current legal capacity of requester documented.
  • Purpose stated in one stable paragraph.
  • Each record category tied to that purpose.
  • Refusal reasons logged by date and category.
  • Business deadline and legal deadline tracked separately.
  • Evidence already lawfully held preserved with context.
  • Confidentiality issues separated from access issues.
  • Parallel proceedings mapped.
  • Local professional advice triggered when urgency, evidence risk or decision impact rises.

The point is not to manufacture drama. It is to notice when an information problem is becoming a process problem — before avoidable delay turns it into a much harder dispute.

How to document a warning sign without overstating it

Write observations, not conclusions. “Portal access was disabled on 3 October” is an observation. “The company destroyed evidence” is a conclusion that may require facts you do not have. “The company gave three different reasons for withholding the same category” is an observation. “The directors are covering up fraud” is a conclusion.

This distinction makes the file more useful to local advisers because they can test the facts against the applicable law without first untangling rhetoric. It also reduces the risk that an early, emotional statement becomes the most memorable document in a later dispute.

For each warning sign, preserve the source, date, exact wording and the practical consequence. Then add a separate column called what would disconfirm this concern? A good escalation file should be capable of becoming less alarming when new facts arrive, not only more alarming.

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.