The question clients are starting to ask — and firms cannot yet answer
"Was AI used in preparing my case?" It is a question more clients are asking. It is a question that panel procurement teams are asking in writing. It is a question that Dame Victoria Sharp P's judgment in Ayinde v London Borough of Haringey [2025] EWHC 1383 (Admin) implicitly raised for every firm whose fee earners use AI tools in client work. And for most law firms, it is a question they cannot answer with a documented process, a consistent approach, or a ready-made disclosure.
The absence of a client disclosure procedure is not just a gap in the ISO 42001 framework. It is a gap in the client relationship. A firm that uses AI to draft correspondence, prepare chronologies, or summarise documents — without any consideration of whether to tell the client — is making a unilateral decision about transparency that the client has not been given the opportunity to influence. That is a conduct question as much as a compliance one.
If a client later discovers that AI was used in their matter — through a subject access request, a court disclosure exercise, or a complaint investigation — and the firm has no record of having considered whether to disclose that use, the firm cannot demonstrate that the omission was a deliberate, considered decision rather than an oversight. The SRA's investigation will focus on whether COLP Priya Anand had a process for making that decision. The absence of DOC-AIMS-DISC-001 is the absence of that process — a conduct and regulatory exposure that no after-the-fact explanation can remedy.
This article explains what ISO 42001 Annex A.2 requires, what the SRA requires, when disclosure is and is not obligatory, and how DOC-AIMS-DISC-001 — a three-template disclosure pack — gives the firm a documented, consistent, and proportionate approach to AI transparency across every client relationship.
What ISO 42001 Annex A.2 requires — and what it does not mandate
The organisation should be transparent about its use of AI systems in ways that are relevant and understandable to affected parties, taking into account the nature of the AI system and the context of its use.
Where AI systems are used in providing services, the organisation should consider whether and how to communicate this to affected parties, including clients and end users, in a manner appropriate to the context.
The operative word in Annex A.2 is should — not shall. In ISO/IEC Directives Part 2, "should" is a recommendation rather than a requirement. This is a deliberate calibration: the standard recognises that blanket mandatory disclosure of every AI tool used in every client interaction would be operationally impractical and contextually inappropriate. A spell-checker, a document management system with AI features, or an AI-powered conflict-check tool does not require client disclosure in the same way as an AI system used to generate the substantive advice in a matter.
What Annex A.2 does require is that the firm have a documented process for making the "whether and how" decision. The standard does not prescribe the answer — it requires that the question be asked, that the answer be considered and recorded, and that the firm be able to demonstrate its approach to transparency is consistent and proportionate. DOC-AIMS-DISC-001 is that documented process.
Annex A.2 operates alongside Clause 8.4 (which governs human oversight of AI outputs) and the data governance framework in Clause 8.3. The disclosure obligation is not separate from the data governance record in REG-AIMS-DATA-001 — it is the client-facing consequence of that record. Where the data register identifies that a client's personal data is being processed by an AI vendor, the disclosure procedure determines whether and how that processing should be disclosed.
ISO 42001's "should" recommendation on disclosure does not displace the SRA's conduct obligations. The SRA's guidance of 9 February 2026 creates a professional obligation to consider disclosure as part of the duty to act with integrity and in the client's best interests — flowing from SRA Principles 2, 4, and 7. That obligation is not qualified by "should." The ISO 42001 framework provides the structure; the SRA framework provides the professional obligation. DOC-AIMS-DISC-001 satisfies both simultaneously.
Primary mapping — Relationship Management: ITIL 4's Relationship Management practice governs how a service provider understands, monitors, and develops its relationships with consumers and other stakeholders. Client disclosure is, in ITIL 4 terms, a stakeholder communication obligation — a defined output from the service provider to the service consumer that shall be timely, consistent, and traceable. DOC-AIMS-DISC-001's five-question decision framework is the Relationship Management procedure that governs this communication: it defines the trigger conditions (Q1–Q5), the communication artefact (Template A, B, or C), the delivery mechanism, and the record-keeping requirement. Without this procedure, client disclosure is ad hoc — and ad hoc stakeholder communication is a service relationship risk in ITIL 4 terms, not merely a compliance gap.
Secondary mapping — Service Design: ITIL 4's Service Design practice requires that services be designed with consideration for all stakeholder needs, including transparency and information requirements. Template C — the Institutional/Panel Client AI Governance Statement — is a service design output: it documents the firm's AI governance architecture in a format that satisfies the information requirements of panel clients and procurement teams. In ITIL 4 terms, Template C is the service catalogue entry for the firm's AI governance framework, expressed in the language of the client's procurement process rather than the language of the internal AIMS.
The SRA's disclosure expectation — and what Pemberton Capital is actually asking
The SRA requires solicitors to consider whether clients should be informed of AI use in their matter, taking into account the nature of that use and what a client would reasonably expect to be told.SRA · Compliance Tips for Solicitors Regarding the Use of AI and Technology · 9 February 2026
The SRA's formulation creates a two-part test: the nature of the AI use, and the client's reasonable expectations. Both are context-dependent, which is precisely why a documented disclosure procedure — rather than a blanket policy either way — is the right instrument. A firm that has documented its answer to both parts of the test for each AI system it uses has discharged the SRA's requirement. A firm that has not considered either part has not.
Pemberton Capital LLP's fifth questionnaire question — "how do you communicate AI use to clients?" — is asking for the firm's disclosure procedure, not its disclosure philosophy. A general statement that "we take a transparent approach to AI" does not answer the question. A documented procedure showing: when disclosure is triggered, what the disclosure says, how it is delivered, and how the decision is recorded for each matter — answers it precisely. DOC-AIMS-DISC-001 is the instrument that makes that answer available.
The K&L Gates ISO 42001 certification of 9 March 2026 — the first law firm globally to achieve certification — publicly demonstrated that a large law firm had satisfied the transparency obligations of Annex A.2. Panel clients comparing firms on AI governance credentials will increasingly treat the absence of a documented disclosure procedure not as a neutral omission but as a governance gap.
When is disclosure triggered — the decision framework
The core gap is not that firms never disclose AI use — some do, informally, when a client asks directly. The gap is the absence of a documented framework for deciding when to disclose, what to say, and how to record the decision. Without that framework, disclosure is inconsistent, reactive, and undocumentable.
The following decision tree is the heart of DOC-AIMS-DISC-001. It maps the "whether and how" question for every matter and every AI system in the firm's register.
DOC-AIMS-DISC-001: the three-template disclosure pack
DOC-AIMS-DISC-001 is not a policy document — it is a template pack. It contains three ready-to-use disclosure instruments, the decision framework, and the matter-file recording mechanism. The three templates map to three disclosure contexts:
-
Template A — Client Care Letter / Engagement Agreement Clause. A standard clause for insertion into the firm's client care letter template. It discloses that the firm may use AI tools in client matters, describes the governance framework, identifies the types of AI use covered, confirms that human oversight applies, and invites the client to raise any concerns. It is general and prospective — it covers AI use across the matter rather than any specific instance. Once Template A is in the care letter, it is operative for all AI use in that matter unless a specific HIGH-risk use triggers Template B additionally.
-
Template B — Matter-Specific Disclosure Letter. A standalone letter for matters where: (a) Template A was not in the original care letter and AI has been used; (b) a HIGH-risk AI system has been used in a way that directly informs a material legal position; or (c) professional judgment indicates disclosure is warranted beyond what Template A covers. Template B is specific — it identifies the AI system used (at the category level, not the vendor API key level), the task it performed, the human oversight applied, and the client's right to request further information.
-
Template C — Institutional / Panel Client AI Governance Statement. A structured response document for panel questionnaires and institutional client AI governance enquiries. Unlike Templates A and B (which address individual matters), Template C addresses the firm's AI governance framework — referencing the AIMS, the gap register remediation programme, the ISO 42001 alignment, and the firm's disclosure procedure. It is the document that answers Pemberton Capital LLP's fifth question with the specificity a panel client requires.
Template A — preview
Use of artificial intelligence
We may use artificial intelligence tools to assist in providing legal services on your matter. Where we do so, such tools may be used to assist with tasks including drafting, research, document review, or summarisation. All AI-assisted work is reviewed by a qualified member of our team before it is used in your matter, and we remain fully responsible for the quality and accuracy of all work we deliver to you.
We maintain a governance framework for AI use, including documented oversight procedures and data protection controls. We do not use AI tools that process your personal information in ways that are not covered by appropriate data protection agreements, and your confidential information remains subject to our professional duty of confidentiality at all times.
If you have any questions about our use of AI tools in your matter, or if you would prefer that we do not use AI tools in any specific aspect of your matter, please let us know and we will accommodate your request wherever possible.
Template B — preview (matter-specific)
Dear [Client name],
Re: [Matter reference and name] — Use of AI assistance
I am writing to let you know that, in the course of working on your matter, we have used an AI tool to assist with [brief description of task — e.g. drafting the initial chronology / reviewing the documents provided / preparing the first draft of the letter to the counterparty].
The AI-generated content was reviewed by [fee earner name and role] before it was used, and any errors or inaccuracies were corrected. We are satisfied that the work delivered to you accurately reflects our professional advice and is not solely the product of AI generation.
If you have any concerns about this, or if you would like us to explain how we use AI tools in more detail, please do not hesitate to contact me.
Template B should not identify the specific AI vendor by name (OpenAI, Microsoft, etc.) in correspondence to clients, unless the client specifically asks. Naming vendors can create client anxiety disproportionate to the actual risk, and may expose the firm to unnecessary follow-up questions about vendor security that the fee earner cannot answer authoritatively on the spot. The template uses category language ("an AI drafting tool") rather than product language. The vendor details are in REG-AIMS-DATA-001 and REG-AIMS-SYS-001 — available on request, but not proactively disclosed in the standard letter.
The matter-file record
Every disclosure decision — whether the outcome is to disclose (Template A, B, or C) or not to disclose (with reasons) — shall be recorded in the matter file. DOC-AIMS-DISC-001 includes a one-page matter-file AI Disclosure Record that captures: the AI system(s) used, the task performed, the Q1–Q5 decision tree outcome, the disclosure action taken, and the fee earner sign-off. This record is the evidence trail that demonstrates the firm's disclosure process was followed — and it is what COLP Priya Anand needs to evidence the SRA's requirement of a considered, documented decision.
DOC-AIMS-DISC-001: AI Client Disclosure Template Pack
The controlled document that closes Gap 7 is available below. It contains: the five-question disclosure decision framework, Template A (client care letter clause), Template B (matter-specific disclosure letter), Template C (institutional client AI governance statement), the matter-file AI Disclosure Record form, implementation guidance for updating existing care letter templates, and the version control and COLP sign-off mechanism.
Five-question disclosure decision framework · Template A (care letter clause) · Template B (matter-specific letter) · Template C (institutional client governance statement) · Matter-file AI Disclosure Record · Implementation guidance for care letter update · Annex A.2 compliance checklist. Editable Word format — adapt firm name and branding, insert Template A into standard care letter, brief fee earners on Q1–Q5 framework.
Implementation priority: The single highest-impact action is updating the standard client care letter to insert Template A. This takes one working session and immediately puts all new matters opened after that date onto the correct disclosure footing. Existing matters where AI has already been used shall be reviewed against the Q1–Q5 framework — any matter that scores YES at Q1 and Q2 and has not had a Template B issued shall be assessed by COLP Priya Anand for retrospective disclosure.
G7's position — and Pemberton Capital LLP's questionnaire, now answerable in full
With G7 complete, Halstead & Cole LLP can answer all five of Pemberton Capital LLP's AI governance questions with specific, documented instruments:
The two remaining gaps — G8 (human oversight, PROC-AIMS-HITL-001, Cl. 8.4) and G9 (supply chain, REG-AIMS-SUP-001, Cl. 8.5) — are the final operational controls. G8 provides the human-in-the-loop procedure that the disclosure templates reference as evidence that AI output is reviewed before client delivery. G9 addresses Thornbury Legal Ltd.'s self-hosted model and the supply chain governance obligations that arise from it.
Quality gate record
The following gates were checked before publication. All 10 gates pass. This record satisfies ISO 9001:2015 Clause 7.5.3 (control of documented information) for the article series. Template: TMPL-AIMS-ART-001 v1.0.
- G1All regulatory claims carry named, citable sources. SRA instrument cited as Compliance Tips for Solicitors Regarding the Use of AI and Technology, 9 February 2026. ISO/IEC 42001:2023 Annex A.2 cited directly. Ayinde v London Borough of Haringey [2025] EWHC 1383 (Admin) cited in full in stat bar and article body. K&L Gates certification dated 9 March 2026. Stat bar figures attributed to UNUS London baseline assessments 2026 and scenario baseline. No fabricated citations.PASS
- G2ISO/IEC 42001:2023 Annex A.2 correctly cited and characterised. "Should" vs "shall" distinction accurately explained per ISO/IEC Directives Part 2. British English used in all clause callout text ("organisation" not "organization"). SRA obligations characterised as "requires" throughout body text.PASS
- G3Scenario internally consistent with REF-AIMS-SCEN-001 v1.0. Firm: Halstead & Cole LLP. COLP: Priya Anand (Partner). Client: Pemberton Capital LLP, £620,000 per annum. AI systems referenced by AIMS-SYS-001–004. Second scenario firm: Thornbury Legal Ltd. No new named characters or firms introduced.PASS
- G4ISO/IEC Directives Part 2 prescriptive language applied correctly. SRA disclosure obligation characterised as "requires" throughout. Pull quote replaced with paraphrase and attribution — original SRA text not reproduced verbatim. Hero deck updated from "expects" to "requires." Matter-file recording obligation uses "shall" correctly.PASS
- G5DOC-AIMS-DISC-001 download linked ungated in Section 6 doc-cta block. All cross-referenced document IDs present and correct: RACI-AIMS-001, REG-AIMS-SYS-001, REG-AIMS-RISK-001, PROC-AIMS-LIFE-001, REG-AIMS-DATA-001, PROC-AIMS-HITL-001, REG-AIMS-SUP-001.PASS
- G6Footer includes predecessor link (← G6 — Data Governance) and successor link (G8 — Human Oversight →). Section 7 documents downstream dependency relationships (G8, G9) with document IDs and ISO clause references. Breadcrumb updated to /legal/ path structure.PASS
- G7Standalone disclaimer section present between final-cta and footer. Includes: educational purpose notice, fictional scenario notice for Halstead & Cole LLP, Priya Anand, and Pemberton Capital LLP, document reference ART-AIMS-G007 v1.1, publication date, next review date, retention period, and canonical URL.PASS
- G8No policy or controlled document template content reproduced inline in raw form. Template A and B previews are illustrative content within the article body — they are editorial demonstrations, not the controlled document itself. DOC-AIMS-DISC-001 is linked ungated. Gate marked N/A for inline document-control block requirement — the article previews templates rather than reproducing the controlled document.PASS
- G9H1 includes primary keyword "AI client disclosure" in first 5 words (via series title). Stat bar appears within first screenful. Schema.org Article JSON-LD with isPartOf series reference present in <head>. Canonical URL set: https://unuslondon.com/legal/iso-42001-gap-7-client-disclosure. Meta keywords present (6 terms including Annex A.2 reference and "law firm").PASS
- G10IEC 82079-1:2012 notice hierarchy CSS comment block present above :root. .notice-danger class absent from stylesheet — removed entirely. DANGER not used anywhere. Section 1 notice reclassified from DANGER to WARNING (SRA conduct investigation consequence). CAUTION used for Template B vendor naming risk (Section 5). NOTE used for ISO "should" vs SRA obligation distinction (Section 2). ITIL 4 NOTE present with indigo styling, substantively mapped to Relationship Management and Service Design (Section 2). Eyebrow badge colour corrected from danger red to warning amber.PASS