Open Books, Closed Advice: Keeping Privilege Intact in Regulatory Cooperation Undertakings

Regulatory engagement is rarely improved by reticence. UK authorities expect regulated firms and counterparties to be candid, timely and organised. Contracts increasingly reflect that expectation through cooperation covenants, notification duties and information-sharing schedules. The difficulty is that the same language can be read as an instruction to hand over everything, including material that would otherwise be protected by legal professional privilege.

The risk is not limited to the most aggressive enforcement context. A commercial agreement may contain a cooperation clause designed for a joint venture, a public sector supply arrangement or a regulated outsourcing project. When a regulator later asks questions, one party may insist that the clause requires full disclosure. The other may discover that board-level risk assessments, internal investigation notes and advice from counsel have become part of the conversation. What began as a contractual promise of assistance can look, in hindsight, like a standing waiver.

Why privilege deserves a drafting decision, not an assumption

Legal advice privilege protects confidential communications between a client and its legal advisers for the purpose of seeking or giving legal advice. Litigation privilege can protect communications created for the dominant purpose of anticipated litigation. Both belong to the client, not to the lawyer, and both can be lost through disclosure. In a regulatory context, the precise boundaries are fact-sensitive. A document that looks like a routine risk summary may contain legal advice; an investigation note may attract litigation privilege if proceedings are reasonably contemplated.

The practical point is that privilege is easier to preserve at the drafting stage than to recover after a regulator has received a document. A cooperation clause that says a party must provide all information, documents and assistance in connection with a regulatory inquiry is not a model of precision. It creates pressure to disclose first and argue later. That is an uncomfortable position for any board, particularly where the material includes assessments of breach, remediation options or advice on penalties.

Three pressure points in cooperation clauses

The first is scope. Obligations framed around all relevant information tend to expand in dispute. What is relevant to a regulator may be wider than what is relevant to the commercial relationship. A clause should distinguish between assistance that is reasonable and proportionate and disclosure that amounts to a waiver of rights.

The second is timing. Notification duties often require a party to inform its counterparty promptly after receiving a regulatory request. If the notice obligation is too broad, it may require disclosure of the request itself before privileged material has been reviewed. Early notification can be useful, but it should not become an early disclosure mechanism.

The third is information-sharing. A party may be required to share information with a counterparty that is also dealing with the same regulator, or with several regulators. Sharing protected material with one recipient can create arguments about waiver as against others. Confidentiality obligations in the contract may help, but they do not automatically preserve privilege against the world.

Drafting cooperation as controlled assistance

A better approach is to define cooperation as assistance short of waiver. The clause should say expressly that nothing in the agreement obliges a party to disclose material protected by legal professional privilege or to waive any privilege. That sounds obvious, but it is often omitted because the parties assume the general law will fill the gap. Express preservation is more robust, particularly where the counterparty is not a lawyer and may treat a broad cooperation covenant as a complete answer.

The clause should also limit the categories of material. Rather than requiring all documents, it can require reasonable assistance, factual information and access to personnel, subject to appropriate confidentiality and privilege protections. If documents are to be provided, the parties should agree a redaction process and a privilege log. A log need not be elaborate, but it should identify the category of material withheld and the basis for the claim without disclosing the substance of the advice.

Costs and proportionality matter too. A cooperation clause that requires a party to incur substantial expense to collate material for a counterparty should say who bears that cost. It should also make clear that the obligation does not require the creation of new documents or the production of material that the party would not otherwise prepare.

Notification, consent and escalation

Notification mechanics should be separated from disclosure. A party can be required to notify its counterparty of a regulatory request within a defined period, while a separate consent mechanism governs any disclosure of privileged or confidential material. The consent should be specific, informed and capable of being withheld. A general consent to cooperation is not the same as consent to waive privilege.

Where a regulator is involved, the parties may need a meet-and-confer process. That can include an obligation to discuss the scope of any disclosure, the form of redactions and whether a protective order or confidentiality agreement is available. The clause should also allow a party to seek protective measures from the regulator or a court without being in breach of the cooperation covenant.

Common-interest arrangements are useful but not a cure-all

Where parties share a common legal interest in resisting or responding to regulatory action, a common-interest arrangement can support the preservation of privilege. Such arrangements are not automatic. They require a genuine common interest, appropriately documented, and they should not be used to shelter ordinary commercial disagreements. A written joint defence or common-interest agreement can set out the scope of shared material, the confidentiality obligations and the consequences of one party exiting the arrangement.

The limitation is that a common-interest arrangement binds the participants, not the regulator. It may strengthen the argument that disclosure was not a general waiver, but it does not guarantee that a regulator will accept the position. The drafting should therefore avoid overstating the protection. It should describe the arrangement as supportive of privilege preservation, not as a statutory shield.

Clawback protocols and inadvertent disclosure

Even careful parties make mistakes. A clawback protocol can reduce the damage. The protocol should require prompt notice after an inadvertent disclosure, return or destruction of copies, and an express statement that the disclosure does not constitute a waiver. It should also prohibit the recipient from using the material for any purpose other than the regulatory matter. In litigation, comparable protections exist under the procedural rules, but in a regulatory context the protection is often contractual and depends on the recipient's agreement. The clause should therefore be realistic about what can be achieved and should require the parties to cooperate in seeking appropriate treatment from the regulator.

When cooperation becomes capitulation

The most common dispute is not about a single document. It is about the meaning of cooperation. One party expects full transparency; the other expects a reasonable response. The contract should resolve that tension before a regulator arrives. A useful definition will state that cooperation does not require a party to abandon legal rights, breach confidentiality owed to a third party or disclose privileged material. It will also provide an escalation route short of termination or litigation.

A well-drafted clause does not make regulatory engagement easier by making it unconditional. It makes it easier by setting boundaries that both parties can explain to a regulator. Candour and privilege are not opposites. The task is to ensure that cooperation obligations are precise enough to command confidence and limited enough to survive scrutiny.