In this guide
- The short answer
- What an AI acceptable use policy for law firms should cover
- Run the permission checks before you launch
- A four week rollout
- Write rules people can follow
- Keep it alive
- Quick answers
- Where this leaves your firm
1. The short answer
An AI acceptable use policy for law firms works when the groundwork happens before anyone is told to follow it. The firm decides which tools are approved and checks what those tools can reach. Then it trains people on real examples from their own practice. The document is the easy part.
With one named owner, plan on about four weeks. The sections below cover what the guidance says a policy should contain, the permission checks to run first, and a rollout plan. If you want a starting document, begin with our AI acceptable use policy template.
2. What an AI acceptable use policy for law firms should cover
Two sources are worth reading before you draft.
ABA Formal Opinion 512. The ABA’s ethics committee issued it on July 29, 2024, as its first formal opinion on generative AI. The ABA’s announcement says the Model Rules on competence, informed consent, confidentiality and fees principally apply. For policy purposes, three points matter most. Managerial lawyers must establish clear policies on permissible use (Model Rule 5.1). Supervising lawyers must make sure nonlawyers, including outside providers, are trained in the ethical and practical use of these tools (Model Rule 5.3).
Third, the opinion says a client’s informed consent is required before information relating to the representation goes into a self-learning generative AI tool. It says general boilerplate in an engagement letter is not sufficient, a point the ABA Business Law Today summary also makes. Consent is not needed when no client information is input. Opinion 512 isn’t binding, and your state’s rules and ethics opinions control.
The New Jersey Courts starter template. On March 30, 2026, the New Jersey Supreme Court published a Notice to the Bar encouraging firms to adopt and update AI policies, with a sample starter policy attached. You don’t need a New Jersey license to learn from it. It’s short and practical, and it says openly that adopting a policy isn’t a safe harbor. What reduces risk is the work behind the document: implementation, training, supervision and verification.
What the template asks a policy to cover works well as a checklist:
- An effective date, a named owner and a review schedule.
- A scope that covers lawyers, staff, contractors, law clerks and interns.
- A statement that lawyers stay responsible for AI-assisted work.
- A confidentiality rule where the firm picks one of four options. The strictest is no AI tools at all. Next is no client information in public AI, then public AI only for de-identified material. The fourth allows client information only in approved vendor tools, after diligence on retention, security and data use.
- Required human review before anything reaches a client, opposing counsel or a court.
- Verification of every case citation, quotation and pinpoint against an official source, with unverifiable citations removed.
- A requirement to check privacy and sharing settings before using any AI feature, including AI built into email, document platforms, meeting tools, browsers and phone apps.
- Rules for AI transcription, for supervised staff, and for what clients are told.
That settings requirement is the one most firms underestimate. It leads straight into the next section.
3. Run the permission checks before you launch
A policy that says “do not put client data into unapproved tools” says nothing about the approved ones. If your approved tool is Microsoft 365 Copilot or a connected Claude deployment, it works inside whatever permissions your people already have. Overshared client folders become part of what the tool can use. So test the environment before you tell people they may use it.
Run these checks first:
- Find broad sharing on client and matter sites. Look for Everyone Except External Users grants and organization-wide or “anyone” links. Remove them from anything privileged.
- Confirm ethical walls are enforced in permissions. A wall that exists only in a policy memo doesn’t constrain an AI tool.
- List the AI features already switched on. Meeting recording and transcription, email summaries, browser assistants and phone apps often arrive by default. The NJ template tells firms to review these settings, including features built into everyday systems.
- Confirm which account tier people use. A personal AI account and a firm-managed one carry different terms on data use and retention. The policy should name the allowed tier along with the vendor.
- Check labels and data loss prevention. If you rely on Microsoft Purview, confirm that your sensitivity labels cover privileged material and that a DLP policy exists for Copilot where your license allows it.
- Decide who can approve a new tool. One named person, with a short written record of each decision.
The first two take the longest. Our guide to shadow AI explains why unapproved tools appear, and how to detect shadow AI shows how to find what’s already in use. Discovery belongs in week one, because the policy has to describe reality.
Policy permission still is not workflow approval; record owners and evidence with an AI workflow approval process before a new path scales.
4. A four week rollout
Week 1: Draft and discover. Name the owner. Pick the confidentiality option from the template that matches how the firm really works. Run the discovery from section 3, and list approved tools with the account tier for each.
Week 2: Check permissions and settings. Fix the sharing problems that matter most, starting with the sites that hold the most sensitive matters. Turn off the settings you decided against. Write down what you changed and what’s still open, because that record is part of your evidence if anyone asks.
Week 3: Train on examples. Hold one session per group instead of one for the whole firm. Use real situations, like a summary of a client email thread or a citation check on an AI-drafted brief. Show the approved tool, the rule and the reason behind it. Give staff and contractors the same session, since Rule 5.3 reaches them.
Week 4: Launch and set the review. Publish the policy with its effective date, owner and review date. Tell people where to ask questions and how to request a new tool. Put the first review on the calendar. The NJ template offers every six months or annually; I’d start at six months, and sooner if a tool or vendor term changes.
5. Write rules people can follow
Keep the policy to two pages. People follow rules they can remember.
Name what’s allowed instead of listing everything that isn’t. A short approved tools table with the account tier and permitted data types does more than a page of warnings.
Say what happens before output leaves the firm. Name a reviewer, require a citation check against an official source, and remove unverifiable cites. Ideally the person verifying isn’t the only person who touched the draft.
Give people a safe path for requests. If a lawyer wants a new tool, the answer should come back in days. Slow approvals create the shadow AI problem you’re trying to prevent.
Decide how clients hear about AI. The NJ template offers options, from telling clients when they ask to telling them before material use. Pick one and build it into your engagement process, with counsel’s advice on what your jurisdiction requires.
6. Keep it alive
Review on a schedule and after any change in tools. Check the settings again, since vendors add features and defaults shift. Track exceptions in one place. Once a quarter, sample a few AI-assisted work products to see whether the review steps happened. A policy nobody audits turns into a document nobody reads.
Once users are working under the policy, enforce the AI acceptable use policy with post-launch monitoring, exception expiry, and an agreed response to repeated bypasses.
7. Quick answers
What should a law firm AI acceptable use policy include?
Scope, a named owner and review date, a confidentiality rule, mandatory human review, citation verification, a check of tool settings, rules for transcription and supervised staff, and a client communication approach. The NJ Courts starter template covers each.
Is a written policy enough to satisfy ethics rules?
No. The NJ Courts say plainly that adopting a policy isn’t a safe harbor. The risk comes down through supervision and training, and through verifying the work. Ask your ethics counsel how your state’s rules apply.
How long does a rollout take?
With one owner, four weeks is realistic for the policy, the checks and the training. Cleaning up sharing on older matters can take longer and can continue after launch.
Do we need client consent to use AI?
It depends on the tool, the data and your jurisdiction. ABA Opinion 512 says informed consent is required before information relating to the representation is input into a self-learning generative AI tool, and that boilerplate engagement letter language is not enough. Whether a given tool is self-learning, and what your state requires, is a question for your ethics counsel.
Who should own the policy?
One named person with authority to approve tools and pause a rollout. That’s usually a partner or the firm administrator, working with IT.
How often should we update it?
The NJ template offers every six months or annually. Review sooner any time a tool, vendor term or rule changes.
8. Where this leaves your firm
Write the policy, but spend more of the four weeks on the checks and the training than on the wording. For a second set of eyes on what your approved tools can reach, start with the free AI Readiness Snapshot. No changes to your environment. No software to install. Our page on AI governance for law firms covers the wider program.
This isn’t legal advice. Whether and how ABA or state guidance applies to your firm is a question for your ethics counsel.




