The cheapest liability control in your firm costs nothing to produce and most firms still skip it. Now it needs a paragraph it has never had.
56% of the tax claims asserted against CPA firms in the AICPA Professional Liability Insurance Program in 2024 had no engagement letter for the service underlying the claim. That number comes from the CNA claim database that underwrites the AICPA program, and it has barely moved in years. Tax work drove 77% of claims. The single document that defines scope, responsibilities, and limits — the one that costs a firm nothing but a signature — is missing from more than half the files when the claim lands.
If you run the firm's operations, this is your problem before it is anyone else's. And in 2026 it got one layer harder: the engagement letter now needs a section it has never contained.
Here is the shift. Your staff are already using AI to do client work: drafting memos, summarizing documents, triaging research. Your professional liability carrier knows it. Carriers are adding AI questions to renewal applications and treating ungoverned AI as a risk they price. The engagement letter is where that risk gets disclosed and bounded. A letter that is silent on AI in 2026 is a letter that assumes a 2022 firm.
The fix is not complicated, and AI itself does most of the work. Two moves for the firm admin who owns the template.
Move one: stop having missing or stale letters. The reason firms skip engagement letters is friction — a partner means to send one, busy season hits, the work starts on a handshake. That friction is now solvable. A tool like Ignition turns scope into a signed letter and a billing schedule in one flow, so "no letter on file" stops being a thing that happens to you 56% of the time. Even without new software, Claude will take your existing template and tailor it per service line in minutes. The excuse is gone.
Move two: add the AI section — as its own clause, not buried in confidentiality. Liability counsel and carriers are converging on the same shape: an affirmative, standalone "Use of Artificial Intelligence" section. Four elements inside it: a plain statement that the firm may use AI tools to assist in delivering the engagement; a human-review commitment, naming that a licensed professional reviews all AI-assisted work before it goes out; a client opt-out mechanism; and a subprocessor list available on request. The opt-out is the part that matters most: it turns a disclosure the client skims into informed consent the client chose. That distinction is what a carrier wants to see if a claim ever turns on whether the client had meaningful notice.
What you do not need: an AI-specific mandate from the AICPA Code before you act. The Code's existing duties — competence, due care, confidentiality — already cover AI-assisted work today. Waiting for a named rule is not a strategy. Your carrier is not waiting, and neither is your renewal date.
This is a firm-admin win that takes an afternoon: current letters, signed every time, with a clause that reflects how the firm actually works now.
Accounting Today reports professional liability carriers increasingly treat ungoverned AI as a controllable risk — and renewal questionnaires are starting to ask about written AI policy, data handling, and incident response. A firm with no answer pays more or gets a harder renewal. Find your renewal date before it finds you.
If CAMICO is your carrier, its Loss Prevention Specialists will read and comment on your drafted engagement letters at no charge, and the members' site holds 150+ sample letters. When you draft an AI clause, send it to them before you adopt it firm-wide. Free legal eyes are free legal eyes.
The AICPA program offers 30+ sample engagement letters plus a terms-and-conditions addendum to policyholders. None ship a turnkey AI clause yet — so the AI section is the one paragraph you still build yourself. Start from their template; add the clause on top.
The Texas State Bar's Ethics Opinion 690 spells out a duty to review AI-generated work in another licensed profession. Accounting carriers are converging on the same expectation. Put the human-review commitment in writing now, before it stops being optional.
More than half of the tax claims asserted against CPA firms in the AICPA Professional Liability Insurance Program in 2024 lacked an engagement letter for the underlying service (CNA claim data, via the Journal of Accountancy, November 2025). In a profession built on documentation, the single cheapest piece of documentation is missing exactly when it would have helped. AI removes the last excuse for that gap.
What it is: A client-engagement platform that turns a scope of work into a signed engagement letter, a proposal, and a billing schedule in one connected flow. Built for accounting and advisory firms; integrates with practice-management tools like TaxDome.
What it does well: It kills the "no letter on file" problem at scale. Standardized templates, e-signature, and automatic tie-in to billing mean every engagement starts with a signed letter instead of a handshake — which is the exact failure behind that 56% number. For a firm admin standardizing across partners, that consistency is the whole value.
What it doesn't do well: It automates sending, not judgment. Ignition will route and sign whatever clause you put in the template; it will not write your AI-disclosure language, weigh your liability exposure, or decide how the opt-out should work. That drafting is Claude's job; the sign-off is your carrier's. Templates are workflow, not legal review.
Pricing: Subscription, tiered by proposal and client volume. Confirm current plans at ignitionapp.com before you budget — pricing shifts, and the tier that fits a 3-partner firm is not the one a 30-seat firm needs.
Firm admins: this is the issue where the Security Desk earns its name. You are about to paste engagement-letter language — including client scope and sometimes client identifiers — into an AI tool to draft the AI clause. Here is how to do that without creating the exact exposure you are trying to close.
What to paste, and where. Drafting engagement letters in Claude is fine. The standing rule holds: Team or Enterprise only when any client-identifying detail is in the prompt. That is tax-software parity: you already trust your tax software and client portal with this data under their business terms, and Claude Team or Enterprise sits in the same posture. Credentials are the only true bright line; never paste portal logins, EFINs tied to passwords, or banking credentials. Free and Pro tiers are for de-identified template work only.
The clause, as a prompt. "Draft a standalone 'Use of Artificial Intelligence' section for a CPA firm engagement letter. Include four elements: (1) a plain statement that the firm may use AI tools to assist in delivering services; (2) a human-review commitment that a licensed professional reviews all AI-assisted work before delivery; (3) a client opt-out mechanism; (4) a statement that a list of AI subprocessors is available on request. Plain English, affirmative tone, no legalese padding. Do not bury it in the confidentiality section."
The rule. Claude drafts; your carrier blesses; you adopt. Never skip the middle step. A clause that reads well is not a clause your insurer has agreed to stand behind.
Open your firm's standard engagement letter template today. Paste it into Claude (Team or Enterprise) with the four-element prompt above and generate a standalone "Use of Artificial Intelligence" section. Then send that draft clause to your professional liability carrier's loss-prevention line — CAMICO and the AICPA/CNA program both review engagement language at no cost — before you roll it out. Thirty minutes to a draft, one email to validate, and your firm stops being the one whose letter is silent on the thing every carrier is now asking about.
P.S. Firm admins: reply with your carrier name. If I get enough, the next Security Desk will be a side-by-side of what each one is actually asking for on AI at renewal.
