AI Informed Consent Form (Client)
A standalone, signable, revocable client-consent form. Use it when AI tools assist on a specific matter. Mapped to ABA Formal Opinion 512 and to Section 6 of our Policy Template.
On this page
When consent is required
Consent under this form is required before client information is input into any AI tool that:
- Retains submitted content beyond the immediate session, or
- Uses submitted content to train the model or improve the service, or
- Provides the firm with no contractual confidentiality assurance equivalent to the protection required under RPC 1.6.
Consent is also required when the firm's policy classifies the information as Highly Sensitive: privileged communications, settlement strategy, third-party PHI or PII, sealed material. Engagement terms or outside-counsel guidelines that require AI-specific consent likewise trigger this form.
Engagement-letter language describing the firm's AI practices generally is not a substitute for this form. Engagement language gives the client notice; this form documents matter-specific informed consent for a specific tool and use case.
What makes consent informed
Under ABA Formal Opinion 512, informed consent for AI use requires that the client understand, in plain language:
- Why the tool is being used and what it will do.
- Which specific categories of client information will be input.
- What disclosure risks attend the use, including how disclosed information could be turned against the client's interests.
- Which benefits the proposed use produces.
The form below tracks each of these. Adapt the bracketed sections ([like this]) to the specific matter and tool. Consent is most defensible when the client has the form in writing, has had time to ask questions, and has signed contemporaneously with the use.
The consent form
The form below is the consent itself. Adapt to the matter and tool, then have the client sign and date. File with the matter.
How to file the consent
- File with the matter. The signed consent is retained in the matter file. Cross-reference the consent in the verification log for any document the consented use produced.
- Document the discussion. If the client asked questions before signing, summarize the discussion in a contemporaneous file note. The note becomes part of the same consent record.
- Honor revocation immediately. A client's revocation applies prospectively from the date of receipt. Stop using the tool on the matter; document the revocation; and confirm to the client in writing.
- Re-consent on material change. If the tool changes, the use case expands, or the categories of information change in a material way, obtain a fresh consent. A consent for one tool and one use case is not a standing consent for that client.
- Pair with engagement-letter notice. The firm's general engagement letter language puts the client on notice that AI tools may be used; this form documents matter-specific consent for a specific use. Together they address the Opinion 512 framework, where engagement notice is necessary but not sufficient.
Form mapped to Policy Template Section 6 and ABA Formal Opinion 512 (July 2024). Last verified 2026-04-29.