Kaufman Ops

AI settings for a small law firm in Utah

Checked against the source documents on October 26, 2026

The Utah State Bar's own AI piece pointed lawyers to the warning in ChatGPT's terms of use that inputs are shared. That warning is about the personal plan. The settings that answer that are on the main checklist. This page says which ones Utah points at, and why.

What Utah has said

Utah State Bar: Using ChatGPT in Our Practices: Ethical Considerations, 2023-05-31.

  1. Confidentiality. Rule 1.6: revealing client information to AI is revealing it; share only what you would share with anyone, omitting names and identifiers (section 2).
  2. Competence. Rule 1.1: check your work; AI fabricates plausible citations even when asked to verify (section 4).
  3. Supervision. Rule 5.3 applies to nonlawyer assistance including AI services; treat output like a law clerk's draft (section 4).
  4. Fees. Rule 1.5: charge only for time actually spent using AI, not time it would have taken by hand (section 3).
  5. Disclosure. Client disclosure recommended (section 1); court disclosure not addressed.
  6. Verification. Check any proposition or citation you are not completely sure about (section 4).

The line about the tool itself. Points to ChatGPT's own warnings in its terms of use paragraph 3(c), its FAQ number 8, and a first-use pop-up that inputs are shared (section 2). (p. 1-2, section 2 (Duty of Confidentiality))

One line from it: "Treat AI-generated results like a draft from a law clerk" (p. 2, section 4 (Duty of Competence and Supervision)).

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. Put the vendor's written terms on training, retention, subprocessors and breach notice in the file. On the checklist
  7. Write the one-page staff instruction and a note for each new hire. On the checklist
  8. Keep a verification step before anything is filed. That is a procedure, not a setting, and no vendor sells it. On the checklist
  9. 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. Utah Rules of Prof'l Conduct Rule 1.1 cmt. [8] (benefits and risks associated with relevant technology), adopted March 3, 2015, effective May 1, 2015 per.

In motion: Utah Supreme Court Ad Hoc Committee on Regulatory Reform, AI/Legal Tech workgroup draft report (dated 2026-08-26) proposing a Rule 4-802 UPL exclusion for AI legal tools with required disclaimers; to be vetted with Bar enforcement staff before any public comment; no comment deadline yet 2026-09-02 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.