Arizona: AI Ethics Guidance for Law Firms

Bottom line for a 5-50 attorney Arizona firm: No formal AEAC ethics opinion governs attorney AI use today. But State Bar practice guidance and the Supreme Court-sponsored AISC “Ethical Best Practices for Lawyers and Judges” (Nov 2024) together establish a clear standard of care. That standard covers confidentiality vetting, output verification, conditional client disclosure, and fee reasonableness. Firms that cannot document confidentiality vetting, citation verification, and supervision are exposed on ER 1.1, 1.6, 3.3, and 5.1 today. Arizona’s Alternative Business Structures program also means AI-native competitors can already operate as licensed providers in the state.

Start with: a written AI use policy, a citation verification log for court filings, and training records covering AI limitations and firm policy.

State Bar of Arizona Guidance for the Use of Generative AI in the Practice of Law

Citation: State Bar of Arizona, Guidance for the Use of Generative AI in the Practice of Law (Practice 2.0 program, published alongside November 2024 AISC guidance). Primary source page.

Status: Practice guidance issued by the State Bar of Arizona. Non-binding. Not a formal AEAC ethics opinion. The State Bar no longer issues formal ethics opinions; those are now issued by the Arizona Supreme Court’s Attorney Ethics Advisory Committee (AEAC), which has not issued an AI opinion. The published page does not carry an explicit date.

What it requires (mandatory language)

• Confidential client information must not be entered into generative AI platforms unless adequate safeguards are in place (ER 1.6).
• A lawyer must understand AI functionality and limitations, and all AI-generated content must be independently verified for accuracy and bias (ER 1.1).
• A lawyer cannot copy and paste AI results without confirming facts and law, and must verify all citations before submission (ER 1.3).
• A lawyer must independently verify all AI-generated citations, arguments, and factual statements, and must disclose AI use per jurisdiction-specific rules (ER 3.3).
• A lawyer must inform clients about AI use in representation, obtain consent before recording client meetings, and allow client opt-out from AI-generated summaries (ER 1.4).
• Fees charged for services provided with AI work must be reasonable; hourly fees cannot exceed actual time expended; AI-related costs must be disclosed in fee agreements (ER 1.5).
• A lawyer must implement detection and mitigation mechanisms for AI bias, with regular audits (ER 8.4).

Rules cited

Rule 42, ER 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.8(b), 3.1, 3.3, 5.1, 5.2, 5.3, 8.4; Arizona Supreme Court Rule 41(c); A.R.S. § 12-2234.

Notable gaps

The guidance carries no formal opinion number and is not binding. The published page is undated. It does not specify which court filings require AI disclosure, deferring to individual court rules.

AISC Generative AI: Ethical Best Practices for Lawyers and Judges

Citation: Arizona Steering Committee on Artificial Intelligence and the Courts, Generative AI: Ethical Best Practices for Lawyers and Judges (Nov 14, 2024), issued pursuant to Administrative Order 2024-33. Primary source PDF.

Status: Practice guidance issued by a Supreme Court-appointed committee. Non-binding. Not a formal AEAC ethics opinion. Carries significant persuasive weight as Supreme Court-sponsored guidance.

What it requires

• A lawyer must understand the benefits and risks of using generative AI.
• A lawyer must check all work product for accuracy and must not defer to the judgment of generative AI.
• When in doubt, a lawyer should not enter confidential or non-public information into a generative AI tool.
• A lawyer using hourly billing cannot bill clients for time saved by using AI.
• A lawyer must inform prospective clients that they are communicating with an AI program and not with a lawyer or firm employee, when AI is used for client intake.
• Reliance on AI output without appropriate independent verification could violate the duty to provide competent representation.

Conditional client disclosure standard

Disclosure to clients is required when the client “would need to know about its use to make an informed decision.” The standard is conditional, not blanket, and is undefined and untested.

Rules cited

Rule 42, ER 1.1, 1.4, 1.6, 3.3.

What federal courts in Arizona require for AI use in filings

No district-wide AI standing order is documented in the District of Arizona. Firms should review the assigned judge’s standing orders at the opening of each federal matter. The operative federal default is Fed. R. Civ. P. 11.

What Arizona state courts require for AI use in filings

ACJA § 1-509 (Use of Generative AI Technology and LLMs). Adopted by Administrative Order 2024-207, effective October 30, 2024; amended by Administrative Order 2025-24, effective January 29, 2025. Primary source PDF. The rule binds Arizona court employees and court-administered systems, not private attorneys directly. Under the rule, the Administrative Director maintains a tiered approval list for AI tools (approved for all purposes; approved for public content only; approved for non-production use only; or prohibited). Court personnel preparing work for a judicial officer must obtain that officer’s approval before using any generative AI material. Attorney implication: AI-generated work submitted to Arizona courts enters a system where AI content is subject to scrutiny.

Code of Judicial Conduct Rule 2.5, Comment 1. Adopted by the Arizona Supreme Court on August 27, 2025; effective January 1, 2026. Primary source PDF. First-in-the-nation explicit judicial technology competence rule. Per Comment 1, judges must maintain “the legal knowledge, skill, thoroughness, and preparation reasonably necessary to perform a judge’s responsibilities of judicial office, including the use of, and knowledge of the benefits and risks associated with, technology relevant to service as a judicial officer.” Attorney implication: judges documenting their own technology competence will apply heightened scrutiny to AI-related attorney conduct. The rule parallels the existing attorney duty under Rule 42, ER 1.1, Comment 6.

No statewide AI disclosure rule applies to attorneys in Arizona state court. Individual judges may have preferences; firms should check chambers rules before filing.

What AI-related rules are pending in Arizona?

HB 2410 (Confidentiality for AI Communications). Arizona 57th Legislature, 2nd Regular Session (2026). The bill passed the Arizona House 53-4. As of March 2026, it is held in the Senate Judiciary and Elections Committee with no action taken. If enacted, the bill would establish that communications between a person and an AI system are privileged where the communication would be confidential if made to a human professional, referencing A.R.S. §§ 12-2234, 12-2238, and 32-3283. If enacted, it could expand privilege protection for client use of AI-assisted intake tools and affect privilege logs and e-discovery in matters where clients used AI legal tools.

Alternative Business Structures

Arizona’s Alternative Business Structures program, governed by Arizona Supreme Court Rules 31 and 31.1(c) and ACJA § 7-209 (amended August 29, 2024), eliminated the rule against non-lawyer ownership for qualifying legal services entities. AI-native legal services companies can hold ABS licenses to provide legal services in Arizona. Program page. Every ABS must designate a Compliance Lawyer, an active Arizona Bar member responsible for ensuring ethical compliance, and client data through any tools, including AI, remains subject to ER 1.6 confidentiality obligations. Implication for traditional firms: where an external AI legal services vendor performs legal service functions, confirm whether that vendor holds an Arizona ABS license. Using an unlicensed vendor for legal service functions creates unauthorized practice of law exposure.

How do malpractice carriers in Arizona treat AI use?

No Arizona malpractice carrier has published explicit AI-specific underwriting guidance in materials reviewed for this entry. Together, State Bar guidance and AISC best practices establish the de facto standard of care under ER 1.1, 1.6, 3.3, and 1.5. State Bar guidance expressly warns that relying on AI without independent verification “could result in discipline.” Fee-reasonableness and client consent requirements create documented obligations that map directly to E&O coverage questions.

What does my Arizona malpractice carrier ask about AI at renewal?

No Arizona malpractice carrier has published AI-specific application items in materials reviewed for this entry. State Bar guidance and AISC best practices are the substantive standards a carrier or broker will reference at renewal. Plan on producing a written AI use policy, vendor review records (terms of service, retention, security), and documentation that confidential client data is not entered into public AI tools. Add engagement letter language addressing AI disclosure under the AISC conditional standard, billing-practice documentation showing AI time savings are not billed at hourly rates, and a citation-verification protocol. Confirm application items directly with your broker.

What documentation should a Arizona firm keep on file?

Month one (foundational)

1. (Owner: managing partner + firm administrator) Written AI use policy covering approved tools, prohibited uses, confidentiality handling, and employee training expectations. Responds to ER 1.1, 5.1, 5.3, and the State Bar and AISC guidance.
2. (Owner: litigation lead) Citation verification protocol requiring attorney review of all AI-generated citations, arguments, and factual statements before filing. Tracks ER 3.3, ER 3.1, and the State Bar guidance.
3. (Owner: firm administrator) Attorney and staff training records covering hallucination risks, confidentiality handling, and bias detection. Tracks ER 1.1 Comment 6 and ER 5.3.

Months two and three (operational documentation)

1. (Owner: firm administrator + outside IT) Vendor review records for each AI tool: terms of service, data retention and third-party sharing, and security posture. Tracks ER 1.6 and ER 1.8(b).
2. (Owner: outside IT vendor) Documentation that confidential client data is not entered into public AI tools. When enterprise or private-deployment tools are used, document the safeguards in place.
3. (Owner: managing partner) Supervision protocol covering associate and staff AI use under ER 5.1 and 5.3.

Months four to six (per-matter discipline)

These are recurring practices, not one-time projects: each new matter exercises them.

1. (Owner: managing partner + billing partner) Engagement letter language that discloses AI use under the AISC conditional standard (“would need to know to make an informed decision”), at minimum for document drafting, legal research, and client communications where AI is material.
2. (Owner: matter lead attorney) Client confidentiality consent procedure for any AI tool that records, transcribes, or summarizes client meetings, plus an opt-out mechanism for AI-generated summaries. Tracks ER 1.4.
3. (Owner: billing partner) Billing-practice documentation stating that AI time savings are not billed at hourly rates, with fee agreement language addressing AI-related cost disclosure. Tracks ER 1.5 and AISC guidance.
4. (Owner: matter lead attorney) Judge-specific AI order check and an ABS vendor check for any external AI legal services vendor in use, confirming ABS licensure or that the vendor provides only software tools.

We are building practitioner resources for firms working through this list. The monthly update covers new resources as they ship.