An AI acceptable use policy tells staff what they may do with AI tools at work. It should fit on one page, because a policy nobody reads protects nobody. Here is a structure you can adapt with your legal and IT teams.
1. Purpose and scope
Say who the policy covers (employees, contractors) and which tools it applies to, including personal accounts used for work.
2. Approved tools
List the tools and plans the company approves, who administers them, and how to request a new one. Everything else is not approved for company data.
3. Data rules
Define what may never be entered (personal data, client secrets, credentials, unpublished financials) and what is allowed in approved accounts. A simple green, amber and red scheme is easy to remember.
4. Human review
AI output must be checked by a person before it is sent to a customer, published, or used for a decision about people or money. The person who sends it is accountable for it.
5. Disclosure and intellectual property
State when AI use must be disclosed to clients, and how the company treats ownership of AI-assisted work. Confirm the position with legal counsel.
6. Incidents, ownership and review
Say who to tell if something goes wrong, who owns the policy, and review it at least twice a year because tools change quickly.
A policy works best with short training that walks through real examples from each team.
Frequently asked questions
How long should an AI policy be?
One page is a good target. A short policy that staff read and remember is more effective than a long one that sits in a folder.
Who should write the policy?
IT, legal and a business owner should draft it together, then test it with a pilot team before rolling it out.
How often should we update it?
At least twice a year, and whenever you approve a new tool or a provider changes its terms.