Why confidential client data changes the AI decision
Before putting client information into an AI tool, check the matter, vendor terms, security settings and lawyer review route. Apply the professional rules and client instructions that govern this matter in your jurisdiction.
Before use, record what the tool does, the data it receives, permitted vendor uses, who checks the output and the decision about client communication. Check those details for the particular matter; a general security statement does not answer them.
The safest review is tool, task, contract and supervision
Review the tool, task, contract and supervision arrangements before allowing AI to handle confidential client information. Do not enter that data in a public service without checking the terms, settings and security evidence. A legal or business product also needs a contract and privacy-term review; its marketing category does not settle the matter.
The review should ask whether the vendor stores prompts, uses client data for training, permits staff or subprocessors to inspect matter content, supports deletion, gives audit evidence and has controls that match the sensitivity of the work. The firm should also decide whether the client must be consulted or asked for informed consent, especially where the tool receives identifiable facts, privileged communications, litigation strategy or sensitive personal data.
Map AI data risks before rollout
What the source says about legal duties
The WSBA opinion links AI use to familiar duties. Competence means the lawyer must understand the technology well enough to use it consistently with professional obligations. Confidentiality means the lawyer must take reasonable steps to prevent client information reaching unintended recipients. Communication means the lawyer may need to explain AI use where the client’s objectives, preferences or data sensitivity make that necessary.
The opinion also points to supervision. Partners and managers cannot simply buy a tool, send a short email and hope the team uses it properly. Lawyers and nonlawyers need training on approved use cases, prohibited data, citation checking, output review and escalation. Vendors are part of the supervision problem too, because their contract terms and safeguards affect whether the firm can safely use the product.
A practical pre-use checklist
- Classify the matter data. Identify whether the tool would receive names, facts, privileged communications, litigation strategy, health data, financial data or other sensitive material.
- Classify the tool. Separate public AI tools, firm-approved legal AI tools, Copilot-style assistants and embedded AI features in existing software.
- Read the vendor terms. Check retention, training use, human review by the vendor, subprocessors, jurisdiction, deletion rights, breach notification and audit evidence.
- Set use-case boundaries. Define what the tool may do, such as summarising non-confidential material, and what it may not do, such as receiving privileged strategy in a public chat.
- Require human review. Record who checks legal accuracy, citations, factual claims, privilege risk and client-specific judgement before work leaves the firm.
- Record client communication. Decide when the engagement letter, matter plan or separate note should explain AI use, risks, alternatives and any consent obtained.
- Keep an audit trail. Save the approved tool, task, reviewer, date, data category, output check and final decision.
How to make the policy usable
A red, amber and green model can help staff apply the policy under pressure. Red means no client data in the tool. Amber means use only with matter partner approval and documented safeguards. Green means approved use cases with defined data limits and normal review.
Review vendor terms, features and retention settings on a recurring schedule. Check them again before extending low-risk internal use to confidential work on a matter.
Keep AI governance current as tools change
Common failure points
The first failure point is treating an AI tool like ordinary search. A prompt can disclose more than expected because it contains names, facts, strategy or a chain of client instructions. The second is accepting output without verification. The WSBA opinion highlights the risk of non-existent or inaccurate citations and makes clear that the lawyer remains responsible for the work.
Check billing and client communication when AI materially changes the work, charges or processing of confidential information; the client may need an explanation. Also check for personal tools used because the approved option is slow or confusing. Those tools may sit outside the firm's data and review controls.
Conclusion
Keep the reasons for approving the tool and data handling, the decision about client communication and the responsible lawyer's output checks. A later reviewer should be able to trace those decisions for the matter.
Build approved AI workflows with the right controls
Need a safer AI route for your firm?
If this article reflects a live decision in your practice, the useful next step is to map the workflows, confidentiality risks, supplier controls and governance gaps before tools spread informally.
