The Field Guide

AI & Workflows

Building an AI policy your team will actually follow

How to write an AI usage policy that protects the business without strangling the productivity gains.

Read

8 min

Sections

7

Words

~586

Most company AI policies are written by lawyers, read by nobody, and ignored by everyone. The result is the worst of both worlds: real risk exposure and no productivity gain, because employees use AI tools anyway but in the shadows. A good AI policy is short, opinionated, and treats employees like adults. It draws clear lines around the things that actually matter and leaves room for everything else.

Section 01

Start by accepting that AI is already in use

Whether you have a policy or not, your team is already using ChatGPT, Claude and Copilot for work. The choice isn't 'AI or no AI' — it's 'AI inside a policy or AI outside one.' Starting from that reality produces a much more useful document than starting from 'should we allow this.'

Section 02

Be specific about data, not vague about ethics

The clauses people actually follow are the specific ones. 'Don't paste customer PII, source code, or unannounced financials into public LLMs' is enforceable. 'Use AI responsibly' is decoration. List the categories of data that are off-limits in plain language, and provide an approved alternative for each one.

Section 03

Distinguish between drafts and decisions

Most policies fail because they try to ban AI use entirely or allow it entirely. The useful distinction is between drafts (anything AI produces that a human will review and edit before it leaves the company) and decisions (AI outputs that take action or reach customers without human review). Drafts can be permissive; decisions need explicit approval.

Section 04

Name the approved tools

Pick two or three tools your company has actually evaluated — data handling, retention policy, security posture — and bless them. List them in the policy. This gives employees a clear path to compliance and prevents the proliferation of fifteen different AI tools with no oversight.

Section 05

Require disclosure for customer-facing AI

If AI is generating something a customer will read — an email, a chat response, a piece of marketing copy — the policy should require human review and, in some cases, disclosure. Customers increasingly notice when they're being addressed by a machine, and trust evaporates quickly when they feel deceived.

Section 06

Build a fast path for new tools

AI is moving fast enough that an annual policy review is too slow. Set up a lightweight process — a Slack channel, a one-page request form — for employees to propose new tools. Decisions in days, not months. This keeps the policy a living document instead of a fossil.

Section 07

Train, don't just publish

A PDF in the employee handbook isn't a policy — it's a liability shield nobody reads. Run a 30-minute training when the policy launches, refresh it twice a year, and use real examples from your business. Adoption follows attention, and attention requires more than an email.

The takeaway

A good AI policy is short, specific, names approved tools, distinguishes drafts from decisions, and gets refreshed often enough to stay useful. Treat your team like adults and they'll behave like ones.

More from the field.

All articles