top of page
Search
Corporate Arbitration Evidence Guide for Boards

Corporate Arbitration Evidence Guide for Boards

Writer: RXM Advisory
RXM Advisory
Oct 6
7 min read

A corporate arbitration evidence guide is not a filing checklist to be opened after a notice of dispute arrives. For boards, executives, investors, and project leaders, it is a discipline of preserving the records that explain how a decision was made, what was agreed, who knew what, and how a financial or technical outcome should be measured.

In corporate disputes, the decisive evidence is often created long before counsel is engaged. A board minute may establish the rationale for a transaction. A cap table, valuation model, or management forecast may determine whether an investor’s claim has a credible economic foundation. In a construction or engineering dispute, a site instruction, design revision, soil investigation, or contemporaneous project diary may carry more weight than later recollections of what occurred.

Start with the issues, not the document pile

Arbitration can generate vast collections of emails, spreadsheets, messaging records, contracts, and technical files. More material does not necessarily produce a stronger case. The first task is to define the questions the tribunal will need to decide.

For a shareholder or M&A dispute, those questions may concern whether disclosure was adequate, whether a seller breached a warranty, whether a board followed the agreed approval process, or what a business was worth at a specified date. In an executive compensation matter, the focus may be whether incentive terms were approved, communicated, and applied consistently. In fraud-related proceedings, the issues may include authority, control failures, movement of funds, and the reliability of management representations.

Construction and professional liability cases require equal precision. Where a geotechnical or underground works claim arises, the dispute may turn on baseline ground conditions, the scope of the professional engineer’s appointment, design assumptions, inspection records, change notifications, or causation between an alleged failure and the claimed loss.

An evidence plan should link each contested issue to the records, witnesses, and expert analysis capable of proving or challenging it. This prevents a common failure: collecting documents without identifying their evidentiary purpose.

Preserve evidence before ordinary business processes erase it

The most damaging evidence failures are usually operational rather than deliberate. Employees leave. Mailboxes are closed. Messaging applications auto-delete conversations. Financial models are overwritten. Physical samples, site photographs, and field notes are misplaced as a project moves forward.

Once a dispute is reasonably anticipated, management should work with legal advisers to implement a proportionate preservation process. The scope depends on the claim, the people involved, the jurisdictions, and contractual or regulatory requirements. It should normally identify relevant custodians, data sources, date ranges, and document categories, while pausing routine deletion for material that may be relevant.

For a corporate matter, relevant sources may include board papers, committee minutes, investment memoranda, draft and final transaction documents, due diligence reports, shareholder communications, accounting records, banking data, and versions of financial models. It is particularly important to retain native spreadsheet files where valuation, earn-out, working capital, or damages calculations are in issue. A PDF may show the final numbers but not the formulas, assumptions, changes, or embedded data that explain them.

For engineering matters, preserve the original technical record alongside correspondence. This can include design calculations, drawings and revision histories, borehole logs, inspection and test plans, monitoring data, requests for information, nonconformance reports, site instructions, daily reports, photographs with metadata, and records of meetings where design or construction risks were discussed.

A preservation instruction should be clear enough for staff to follow. It should also be practical. Overly broad directions that require every employee to retain everything are difficult to administer and can obscure genuinely relevant material.

Maintain a defensible chain of custody

Evidence is more persuasive when its source and handling can be explained. Forensic images of devices, exported communications, financial data extracts, and site records should be logged with their source, collection date, custodian, and any processing performed. This is especially relevant in fraud investigations and technical disputes, where allegations of alteration or incomplete production can become a dispute of their own.

Boards should expect periodic confirmation that preservation measures remain active, particularly during leadership changes, restructurings, insolvency risk, or project handovers. A record that cannot be located at the critical moment may be treated very differently from a record that was never created.

Build the corporate narrative from contemporaneous records

A tribunal will assess credibility through the evidence available at the time, not merely through a party’s current position. The strongest corporate narrative is therefore chronological and document-led.

Consider a founder dispute over dilution. The relevant evidence is rarely limited to the shareholders’ agreement. Board resolutions, financing decks, investor term sheets, capitalization tables, email exchanges, and records of conflicts disclosures may show whether the parties understood the transaction and whether governance procedures were followed. If a director abstained, objected, or approved a transaction subject to conditions, the minutes should say so with sufficient specificity.

The same principle applies to executive disputes. A claim that a chief operating officer was promised a different incentive outcome cannot be assessed solely by reference to employment correspondence. The tribunal may examine approved remuneration policies, compensation committee materials, performance metrics, delegated authorities, communications on role scope, and evidence of how comparable arrangements were handled. Informal assurances can matter, but they must be tested against the company’s documented authority structure.

Contemporaneous documentation does not mean producing self-serving paper after a concern is raised. It means recording decisions while facts are fresh, alternatives are still visible, and the commercial rationale can be accurately stated. Board minutes should reflect material deliberations and conflicts without becoming a transcript. Project records should state observations, instructions, and unresolved risks without editorializing for a future claim.

Test financial evidence as rigorously as legal evidence

In many corporate arbitrations, liability and quantum are inseparable. A party may establish a contractual breach but still fail to prove loss with an appropriate valuation methodology or reliable underlying data.

Valuation evidence should begin with the correct valuation date, the applicable contractual definition, and the information that was available or reasonably foreseeable at that time. Forecasts require careful scrutiny. Were they prepared in the ordinary course? Did management revise them after the dispute emerged? Were key assumptions supported by customer contracts, market data, operating capacity, financing availability, or comparable performance?

A disciplined review compares management accounts to audited financial statements, tests model formulas, traces material inputs to source documents, and identifies post-date information that may improperly influence a historical valuation. The appropriate method may depend on the business and the claim. Discounted cash flow analysis can be useful for a business with credible forecasts, while market multiples, prior transaction pricing, asset-based approaches, or scenario analysis may be more suitable in other circumstances.

Damages claims also require a clear causation bridge. A decline in revenue after a disputed acquisition, for example, may reflect the alleged breach, but it may also reflect lost customers, execution failures, market shifts, or financing constraints. Evidence should distinguish assertion from analysis.

Technical disputes require records that connect duty, breach, and loss

Professional liability claims against a practicing professional engineer or qualified person are rarely resolved by asking whether a project encountered difficulty. Underground construction and geotechnical works carry inherent uncertainty. The material questions are whether the scope of duty was properly defined, whether reasonable professional judgment was exercised, whether assumptions and risks were communicated, and whether the alleged failure caused the loss claimed.

This is why the record of professional decision-making matters. A design basis memorandum, risk register, ground investigation report, review comment, site observation, or escalation email can show what information was available and how it was evaluated. Conversely, undocumented departures from design criteria or ignored warning signs can materially weaken a defense.

Where multiple parties are involved, allocate responsibility carefully. The employer, designer, contractor, specialist subcontractor, and independent reviewer may each have distinct obligations. An evidence strategy should avoid assuming that a technical defect proves liability by one party alone. Sequence, access to information, contractual allocation of risk, and intervening acts frequently matter.

Independent experts can assist the tribunal, but their work is only as reliable as the records and assumptions supplied. Management should ensure that experts receive a complete and balanced factual record, including documents that may not assist the company’s preferred position. Selective instructions create credibility risk and can expose an expert opinion to serious challenge.

A board-level evidence protocol worth adopting

The following controls are practical across transactions, governance disputes, investigations, and technical claims:

  • Record material decisions, conflicts, approvals, and conditions in timely board and committee minutes.

  • Retain controlled versions of transaction documents, valuation models, due diligence findings, and key management forecasts.

  • Establish clear retention ownership for project records, including technical data held by consultants and subcontractors.

  • Escalate credible disputes early so preservation, privilege, and communications protocols can be addressed with counsel.

  • Separate factual investigation from advocacy, and document the basis for remedial decisions without compromising legal advice.

These controls should be calibrated to the organization. A growth-stage company should not attempt to replicate the records department of a multinational group. It should, however, be able to identify its key decisions, approvals, contracts, financial assumptions, and operational evidence without relying on individual memory.

Prepare witnesses without rewriting the facts

Witness evidence can explain context that documents cannot capture, but it should not be used to repair weak records. Identify likely witnesses early, preserve their relevant communications, and obtain a structured account while recollection is still reasonably fresh. Their evidence should be tested against contemporaneous documents, including documents that create difficulty.

Senior witnesses need particular care. A director, CEO, CFO, or project lead may have broad knowledge but limited direct involvement in a specific event. Statements should distinguish personal knowledge from information received from others. Overstatement may damage the credibility of the witness and the organization.

The practical objective is not perfect documentation. It is a credible record: one that allows a tribunal, expert, investor, or board to understand what was known, what was decided, and why. When that discipline becomes part of ordinary governance and project management, disputes become easier to assess, negotiate, and, where necessary, defend.

 
 
 

Comments


bottom of page