Law Firm AI Policy Document Upload Rules: A Template

A law firm AI policy should say which document upload tools staff may use, which client documents may go into each one, who approves a new tool, and what to do after a mistake. Keep it to a page or two, name the tools, and tie every rule to how sensitive the document is.

This post is a drafting aid and not legal advice. Ethics rules and opinions differ from one jurisdiction to the next, so check the rules of every bar your lawyers answer to before you adopt any of it.

Why does a firm need a written rule on document uploads?

A firm needs a written upload rule because uploading is the moment a client file leaves the firm, and it takes ten seconds. Without a rule, each person decides alone, late in the day, with a deadline coming. A written rule makes the decision once, calmly, for everyone.

Picture a paralegal at six in the evening with a 40-page scanned lease and a partner waiting for an editable copy. A search for a converter returns a dozen free sites. Nothing on the firm's computers stops the upload, and nobody has ever said which sites are acceptable. The paralegal is not careless. The firm has left a professional judgment to whoever happens to be holding the file.

Bar guidance points the same way. The State Bar of California's Practical Guidance for the Use of Generative Artificial Intelligence in the Practice of Law says managerial and supervisory lawyers "should establish clear policies regarding the uses of generative AI" and provide training on the tools. The D.C. Bar's Ethics Opinion 388 on generative AI in client matters suggests that firms could require lawyers and nonlawyers alike "to satisfy themselves that client confidentiality under Rule 1.6 will be protected before using a GAI product."

Both documents are written about generative AI and each speaks for one jurisdiction. Your own bar may say more, less, or nothing yet. The practical point holds anywhere: the supervising lawyers answer for what staff do with client files, so they should decide the rule and write it down.

What should the policy cover?

The policy should cover every tool that takes a document out of the firm's own systems, every person who handles client files, and every class of document the firm holds. Ten short answers do the work. If one is missing, staff will fill the gap with a guess.

Two points are easy to miss. First, define the scope by what happens to the file. A rule written only for "AI" gets argued around by anyone who thinks a PDF converter is something else. Second, deal with client instructions. The California guidance says a lawyer must follow client instructions or guidelines that restrict the use of AI in the representation, and a firm policy that ignores a client's guidelines will be broken on the first matter for that client.

Put the duty of competence on the person who approves a tool, and require that person to read the terms of service for the plan staff will actually use. Generative artificial intelligence and a plain converter can share one register if the columns are the same. Add a conflict of interest line for any login that would hold files from adverse clients at once.

Leave the analysis of privilege and waiver out of the policy itself. Staff need rules they can apply in a minute, and the post on attorney-client privilege and AI tools covers the reasoning.

A template clause set for document uploads

A workable clause set runs to about ten short clauses: scope, a default rule, the register of tools, accounts, client instructions, cleanup, verification, new tools, incidents and review. The wording below is a starting point. Replace the bracketed parts, cut what does not fit, and have the lawyer responsible for ethics at your firm approve the result.

1. Scope. This policy applies whenever anyone working for the firm uploads, pastes or sends a document, or any part of one, to a service the firm does not operate. It covers AI assistants, OCR and file converters, translation and transcription services, and browser extensions that read page content.
2. Default rule. No client document may be uploaded to a tool that is not on the firm's register of approved tools. When in doubt, do not upload. Ask [name or role].
3. The register. The firm keeps a register listing each tool as approved, restricted or banned, with the classes of document allowed in each. The register is at [location] and is the only authority on what is permitted.
4. Document classes. Every document belongs to one of four classes: public, internal, client confidential, or restricted. Restricted documents include [documents under a protective order, sealed filings, health records, records about minors, and anything a client has asked the firm to handle specially].
5. Accounts and devices. Approved tools are used only through an account the firm has set up, on a device the firm manages. Personal accounts are not used for firm documents, even with an approved tool.
6. Client instructions. Where a client's engagement letter or guidelines restrict the use of AI or outside services, the restriction applies to that client's documents in place of the register.
7. Cleanup. After the export is saved to the matter file, delete the uploaded document and its outputs from the tool unless the register gives a different retention period for that tool.
8. Verification. Text produced by any tool is checked against the original document by a person before it is filed, sent or relied on.
9. New tools. Anyone may propose a tool using the request form at [location]. No client document is uploaded to a proposed tool until it is on the register.
10. Incidents. If a client document reaches a tool that is not approved for it, tell [name or role] the same day. Reporting promptly is expected and will not by itself lead to discipline.
11. Review. [Name or role] reviews the register every [six] months and whenever an approved tool changes its terms.

Clause 7 depends on what each tool lets you do, which is why retention belongs in the register entry for every tool. The post on whether OCR software stores your documents explains what to look for.

Keep clause 10 strict on speed and gentle on blame. An upload reported within the hour can often be deleted and assessed. One that surfaces six months later cannot.

Sorting tools into approved, restricted and banned

Sort each tool into one of three tiers by what its written terms say about your files. Approved tools may take client confidential documents. Restricted tools may take only public or internal documents. Banned tools may take nothing from the firm. Give the tier, the reason and the review date in one register row per tool.

The tier belongs to the tool and the plan together. A consumer plan and a business plan from the same company can carry different terms, and the D.C. opinion notes that a confidentiality problem may sometimes be resolved by "an upgrade to a paid product with better terms". Record which plan the firm reviewed.

Here is how three ordinary requests come out under that table:

• A published appellate opinion that will not copy cleanly. The document is public. Any tool that is not banned will do.
• A scanned commercial lease from a client. Client confidential. Approved tools only, through the firm account, deleted from the tool once the Word file is in the matter folder.
• Medical records produced under a protective order. Restricted. Read the order first. Use an approved tool only if the register clears it for restricted documents and the order allows an outside vendor to handle the records.

A tool can also move down. If a provider changes its terms, drop it to restricted the same day and review it again.

Who approves a new tool and how

One named person or a small committee should approve tools, using the same short review every time and answering within a set number of days. Slow approval tempts staff to go around the policy, so the deadline matters as much as the checklist.

A review that fits a small firm has six steps:

1. Take the request. The requester names the tool, the plan, the task and the classes of document involved.
2. Read the terms. Open the terms of use and the privacy policy for that plan. The California guidance says a vendor's general marketing assurances are not enough.
3. Ask the two confidentiality questions. The D.C. opinion asks whether the provider or other outsiders can see what you send, and whether your use could reveal it to later users. Both are quoted in the section on what the confidentiality rules require of a lawyer.
4. Send written questions to the vendor. Cover access, reuse, retention, deletion and what changes on notice. The post on whether it is safe to upload client documents to an OCR tool lists the questions in full.
5. Test with a document that is not a client's. Use a public filing of the same kind. Check the output and practise deleting the file.
6. Record the decision. Enter the tier, the plan reviewed, the date, the reviewer and a saved copy of the terms as they stood.

Put Schema Law through the same six steps as anything else. Its security commitments are short enough to quote in a register entry: "Your documents are never used to train an AI model", "Documents stay inside your own account", "Encrypted in transit and at rest" and "Delete any document, at any time". Those are the company's own statements, so ask for them in writing with the detail your review needs. The Enterprise plan lists "Security questionnaire and contract review" for firms that run a formal process, and the pricing page shows what each plan includes.

Training staff and checking compliance

Train everyone who touches client files when they join and again whenever the register changes, then check a few simple signals each quarter. A policy that lives in a handbook and is never mentioned again will lose to a deadline. The California guidance calls for periodic training of lawyers and nonlawyer staff alike.

Thirty minutes is enough for the first session if it is concrete:

• Show where the register is and how to read a row.
• Walk through the three example requests above with documents from your own practice.
• Demonstrate an approved tool from upload to deletion.
• Explain what to do in the first ten minutes after a wrong upload.

For checking, pick signals you can gather without watching anyone's screen:

• Expense claims and card statements. A subscription nobody proposed is a tool nobody reviewed.
• The register against reality. Ask each team twice a year which tools they used in the last month and compare the answers with the register.
• Requests received. No requests in six months may mean people have stopped asking, not that nobody has found a new tool.

When an incident is reported, follow a fixed order. Stop using the tool for that matter. Delete the document from the tool if it allows deletion, and keep a screenshot of the confirmation. Write down what was uploaded, when, by whom and under which account. Save a copy of the tool's terms as they stand that day. Then the responsible lawyer decides whether the client must be told. That last question turns on your jurisdiction's rules and the facts, and it is one for the firm's ethics counsel. Afterwards, fix whatever the incident exposed, such as a register nobody could find or an approved tool that could not handle the file.