Home › Blog › Claude drafted a tax memo with an error and it went to the client. Who is responsible, and what does the file need to show?

Claude drafted a tax memo with an error and it went to the client. Who is responsible, and what does the file need to show?


Admin, rollout and governance

Short answer

The firm, the same way it would be if an associate drafted it. Anthropic’s commercial terms make the outputs yours; professional rules make the signer accountable; no vendor certification changes that. What the file needs to show is a review step that existed and was followed, or honestly, that it was not, plus the correction sent to the client and the policy change that follows. The useful question is not who is to blame but why the review step did not catch it. Strategized.ai’s Claude implementation builds the review step into the firm’s plugin workflows and the training so the memo cannot leave without a signature line being completed.

In one picture

When an AI-drafted memo goes out wrongCorrect the clientdocument itReconstruct thereviewgap is a findingFix the workflowchecklist in the pluginTrain on the errortypenext session

Diagram: When an AI-drafted memo goes out wrong

What Anthropic and the rules actually publish

Commercial Terms: the customer “owns its Outputs.” Ownership carries responsibility.Source: anthropic.com/legal/commercial-terms
ABA Opinion 512: competence includes reviewing AI output; lawyers remain responsible for the work product.Source: americanbar.org
AICPA standards: the CPA signing the deliverable is responsible for it regardless of the tool used to draft it; Circular 230 and SSTS apply to tax advice.Source: aicpa.org; IRS Circular 230
Anthropic’s ISO 42001 certification covers its AI management system, not the correctness of any specific output.Source: trust.anthropic.com/faq
Enterprise audit logs and the Compliance API can show the session; on Team the file and the review log are the record.Source: claude.com/pricing

The follow-up questions owners ask

Can we point at the vendor?

No, and it would not help with the client or the regulator. The vendor’s terms, certifications and no-training commitments are about data handling, not the accuracy of a memo you signed.

What goes in the file after the fact?

The original, the corrected memo, the date and method of correction, the review record (or the gap), and the policy or workflow change. Malpractice carriers want to see the last item most.

How do we prevent it?

A review step that is a workflow, not a reminder: the firm’s plugin ends every client deliverable with a checklist the signer completes, and the policy says nothing leaves without it. Then train on the two or three error types Claude actually produces in your work: stale figures, wrong citations, confident gaps.

What this means for your rollout

Correct the client first; document the correction.
Reconstruct the review record honestly; a gap is a finding, not a cover-up.
Change the workflow so the review step is structural (checklist in the plugin, signature line).
Add the error type to the next training session’s examples.

Related services and tools

Claude implementation for your firmreview steps built into the firm's workflows
Your firm's custom Claude pluginwhere the checklist lives
Role-based security and usage trainingthe error-type examples from your own work

Get the plan before you buy the seats

The plan choice is the easy part. Configuration, governance and training are where firms get it wrong. The Claude Build Plan is two working sessions with Michael Robichaud, then a written plan: architecture, plan choice with the reasons, your firm’s custom Claude plugin scoped, rollout timeline and cost. A fixed $2,500, and the plan is yours to keep.

Get the Claude Build Plan or book a 20-minute intro call.

Related questions

Sources

Not legal advice. Confirm regulatory items with your counsel. Anthropic pages change; every source above shows the date we checked it.
Strategized.ai is independent and not affiliated with or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.

Part of the Claude Security & Privacy Center for business owners: read the owner’s guide to the one-page Claude usage policy.
Michael Robichaud

Written by

Michael Robichaud

Founder of Strategized.ai, a Claude consultancy for owner-led businesses. Michael leads every Claude rollout himself, designs the custom Claude plugins his developers build, and runs his own five-site publishing network on Claude.

 ·  Connect on LinkedIn →

About the Author

Michael Robichaud

Founder of Strategized.ai. 30 years across enterprise sales, digital marketing, and building businesses. Practitioner-first AI strategy consulting — done-for-you workspace builds, GEO/AEO, and fractional advisory.

Free: the Claude Foundation Plugin

A 20-minute Guided Intake. Claude learns your business once and remembers it in every chat. No account, no card.

The Strategy Stack

Strategized.ai is the strategy layer. Where to go next.

Keep Exploring

More from the blog

Strategy, GEO/AEO, consulting perspectives.

Browse the Blog →

Prefer to learn it yourself?

Free written guides, from first day to confident.

Read the free guides →

Claude plugins by profession

Ready-made Claude plugins for your role, $99 each. Or start free with the Foundation plugin.

Browse the Claude plugins →