A commercial dispute often begins quietly: an unpaid invoice, a disputed deliverable, a termination email, or a board note that says the counterparty is becoming difficult. By the time a formal notice arrives, the company may already have scattered records across email, shared drives, messaging tools, finance systems, and personal devices. A legal hold protocol is the board's way of making sure the evidence trail does not depend on memory and good intentions.
The board need not manage every file. Its job is to ensure that preservation is triggered early, responsibility is assigned, and the response is documented. The practical test is simple: if the company had to explain six months later what was preserved, by whom, and when, could it do so without improvising?
The first step is a clear trigger standard. A legal hold should not wait for a plaint, statement of claim, or arbitral notice. It should begin when dispute risk is reasonably foreseeable: a credible demand, a material breach allegation, a termination threat, a warranty claim, or an internal finding that may lead to proceedings. Waiting for perfect certainty is tidy in theory and hazardous in practice.
The second step is custodian mapping. The response team should identify people who hold relevant records: project heads, contract managers, finance staff, sales teams, procurement, technical teams, and directors who received board papers. Custodian lists should include role, record source, device or system, preservation instruction date, and acknowledgement. A legal hold email that nobody acknowledges is a polite wish, not a control.
The protocol should also name the first reviewer. Without that role, documents may be collected in bulk but left unread until deadlines arrive. Early triage helps separate core evidence from background material and identifies missing records while custodians still remember where to look.
Digital channels deserve specific treatment. Business records may sit in enterprise email, collaboration platforms, shared drives, messaging applications, call recordings, customer tickets, and accounting tools. Auto-deletion rules may need to be paused. Access logs and metadata may be relevant. If a company preserves only the final contract but loses the negotiation trail, approval notes, and performance correspondence, the dispute record becomes thin.
Privilege should be handled with care. Factual collection, internal review, and legal advice should not be mixed in a single loose document chain. Counsel should guide privilege-sensitive steps, especially where internal investigation notes, settlement communications, or board advice are involved. The aim is not secrecy for its own sake. It is disciplined separation between business facts and protected legal advice.
Board minutes should record oversight without overloading the record. They may note that the board reviewed the dispute risk, directed preservation, assigned responsibility, sought legal input where appropriate, and asked for periodic updates. The minutes should avoid speculative conclusions about liability. Directors supervise the system; they do not need to draft the statement of defence from the boardroom.
A preservation tracker is useful. It should show custodians, systems, document categories, status, gaps, deadlines, and owner names. The tracker can later support evidence preparation, settlement evaluation, and cost management. It also prevents the common problem of rediscovering the same documents every time a new counsel, officer, or auditor asks a question.
AGS Consulting assists companies in building legal hold protocols, document maps, and board reporting templates for commercial disputes. For a focused preservation review, contact AGS Consulting through /#contact.
FAQs
When should a company issue a legal hold?
A legal hold should be issued when dispute risk is reasonably foreseeable, including after a demand, breach allegation, termination threat, or significant internal finding.
Who should receive the preservation instruction?
It should go to relevant custodians across legal, finance, procurement, project, sales, technical, and leadership teams, depending on where records are held.
Should board minutes mention the dispute?
Yes, but carefully. Minutes should record oversight, preservation directions, and reporting cadence without speculating on liability or reproducing legal advice unnecessarily.
What records are commonly missed?
Messaging channels, shared-drive drafts, approval notes, finance system exports, call records, and archived project files are often missed unless the hold protocol names them specifically.