Kaufman Ops

AI settings for a small law firm in Arizona

Checked against the source documents on October 26, 2026

The State Bar of Arizona's AI guidance says to review the terms of any generative AI tool so it doesn't share your inputs or use them for training. The settings that answer that are on the main checklist. This page says which ones Arizona points at, and why.

What Arizona has said

State Bar of Arizona: Guidance for the Use of Generative Artificial Intelligence in the Practice of Law in Arizona (Practical Guidance), undated on its face; docx posted..

  1. Confidentiality. Must not enter confidential client information unless adequate safeguards exist; use encrypted, access-controlled platforms; treat the tool as any third party and anonymize inputs (Duty of Confidentiality section).
  2. Competence. ER 1.1 and 1.3: understand functionality, limits and risks before use; AI output is no substitute for the lawyer's judgment; competence requires active analysis, not just error detection (Competence section).
  3. Supervision. ER 5.1-5.3: establish clear AI policies, train, and monitor usage of attorneys and staff; subordinates may not violate duties even if directed (Supervision section).
  4. Fees. ER 1.5: may charge for crafting prompts and reviewing outputs, structured like legal research tools; fees must be reasonable; AI-related costs must be clearly disclosed in fee agreements (Charging section). AISC: no billing for time saved.
  5. Disclosure. Review jurisdiction-specific AI disclosure rules and individual judges' requirements before filing (Candor section); client communication covered above.
  6. Verification. All AI content must be independently verified for accuracy and bias; verify every citation, argument and factual statement before submission (Competence and Candor sections).

The line about the tool itself. Direct line: lawyer must review applicable terms governing any generative AI tool to ensure it does not share input data with third parties or use it for training; consult IT experts on security, confidentiality and data retention protocols (Confidentiality section, bullets 4-5). (Practical Guidance, Duty of Confidentiality section, final bullet (docx p. 1-2))

One line from it: "must not enter any confidential client information into generative AI platforms" (Practical Guidance, Duty of Confidentiality section, first bullet).

The settings that answer it

  1. Use the business plan, not a personal one. On Claude Pro, Claude Max and ChatGPT Plus, training on chats is each user's own setting. On Claude Team, ChatGPT Business and Microsoft 365 Copilot with a work sign-in, business data is not used for training by default. On the checklist
  2. Turn off the training and feedback exceptions an admin can still turn off (Claude feedback, ChatGPT personal accounts that are still in use). On the checklist
  3. Set retention on purpose instead of taking the default. On the checklist
  4. Turn on single sign-on so a lawyer who leaves loses access the same day. On the checklist
  5. Decide on connectors, apps and agents before staff add them. On the checklist
  6. Pick a rule on memory, and teach temporary or incognito chats for one-off matter questions. On the checklist
  7. Put the vendor's written terms on training, retention, subprocessors and breach notice in the file. On the checklist
  8. Write the one-page staff instruction and a note for each new hire. On the checklist
  9. Keep a verification step before anything is filed. That is a procedure, not a setting, and no vendor sells it. On the checklist
  10. Decide what the engagement letter says about AI use and billing. That is yours to write; I only flag that the opinion raises it. On the checklist

Rules around it

Technology competence: Yes. Ariz. Rules of Prof'l Conduct ER 1.1 cmt. 6 (benefits and risks associated with relevant technology), effective Jan. 1, 2015; quoted in AISC best practices fn.

In motion: No proposed rule or pending ethics opinion on AI found: the Attorney Ethics Advisory Committee Proposed Ethics Opinions page lists nothing open for comment (checked 2026-10-26); next committee meeting November 19. 2026-10-26 (check date) source

What this page is not

This is a tech settings page, not legal advice. The state document above is the ethics half and it is yours to read and decide on. I am not a lawyer. I link the source so you can check me.

Send me one screenshot

Crop out client names, send me a screenshot of your Claude, ChatGPT or Microsoft 365 admin settings page, and I'll write back what I'd change. Free. I never need a login.

If you want this kept current for your firm, that is the monthly desk: I watch these settings as the vendors change them and as your state changes its guidance, answer staff questions in writing, usually within one business day, and write up setup notes for each new hire. $500 a month, cancel any month.

Email [email protected]

Who wrote this

Nick Kaufman

I'm Nick Kaufman. I've spent six years in customer-facing technical support for SaaS, payments and CRM software, including three years at Tier 2 on a CRM built for financial advisors, whose firms work under SEC and FINRA rules. I'm not a lawyer and I don't give legal advice. I set up software so it does what the people responsible for it decided it should do.

Other states: the full list.