A one-page AI policy for your small business

Most small companies have no written AI rules. The tools arrived faster than anyone could write a policy, and long policy documents are made for companies with legal teams.
No rules has a cost. Some people avoid AI because they are not sure it is allowed. Others paste customer data into a personal chat account because nobody said not to. And an automation set up last spring may still be running and spending money, with nobody watching it.
This policy fits on one page. It covers eight things we think every company of 5 to 200 people should decide. You can download the fill-in-the-blanks version and edit it in any text editor. It is a starting point, not legal advice. If you work in a regulated sector, ask a lawyer to read it.
Key points in 30 seconds
- Keep it to one page. A short policy gets read. A long one does not.
- Cover eight things: approved tools, data rules, human review, an agent register, spend caps, customer disclosure, incident reporting and a review every three months.
- A person always decides. Whoever approves AI output is responsible for it.
- Every automation has an owner. If it is not in the register, it does not run.
- You can finish it in an afternoon. The register takes longest and is worth the most.
What is in a one-page AI policy?
Eight parts. Open each one to read the rule and the reason for it.
The eight parts of the policy. Tap a part to read the rule and the reason.
The rule
We use only the AI tools on the approved list for work, on company accounts. Anyone can ask to add a tool. The policy owner decides, usually within a week. The list records what each tool is approved for, which class of data may go into it, and who owns the account.
Why it is there
This is the easiest win. Most of the risk in small companies comes from personal accounts and unknown tools, not from approved ones. A short list with a fast way to add to it keeps people on checked tools. Check each tool’s business terms to see if your data is used to train its models. Business plans often differ from consumer plans.
The rule
All data is Green, Amber or Red. If you are unsure, treat it as Red. Never put passwords, keys or tokens into an AI tool.
Why it is there
People remember three colours. The rule that matters most is the default: unsure means Red. Try the checker below.
The rule
AI can draft. A named person decides. A person reads and approves AI output before it reaches a customer, a supplier or the public. The same goes for any AI action that spends money, changes a price or a contract, or changes customer data. Code written by AI is reviewed like any other code. The person who approves AI output is responsible for it.
Why it is there
This is where accountability lives. Whoever approves the output owns it, as if they had written it. So “the AI said so” is never an answer.
For software teams: our AI-native SDLC playbook. It goes further: nothing merges unless a person on the team can explain it.
The rule
Every AI agent or automation that runs by itself is in the register before it goes live. If it is not in the register, it does not run. If its owner leaves, it is paused until a new owner is named.
Why it is there
An agent that runs by itself can fail quietly and expensively. The register gives each one a person. The “paused if the owner leaves” rule sounds harsh, but it catches the automation everyone forgot. See the builder below.
The rule
Every agent has a per-run and a per-day spend cap, not only a monthly budget. Anything that loops has a limit on steps. Alerts go to the owner by name. Named people can stop any agent, at any time, without asking, in under a minute.
Why it is there
A monthly budget only trips after the money is gone. Per-run and per-day caps, and step limits on loops, are what stop a runaway.
How to pick the numbers: what a sane agent spend cap looks like
The rule
We tell people when they are talking to an AI. We tell customers when AI plays a meaningful part in a decision about them, and how to reach a person. We do not present AI-generated content as a person’s own words or experience.
Why it is there
This is about trust first and law second. Finding out later that you spoke to an AI feels like being misled, even when the answer was right. Some laws, including the EU AI Act, also require you to say when people deal with an AI system. Check which laws apply to you.
The rule
Anything where AI caused or nearly caused harm is reported to a named person or channel straight away. If it is still happening, stop the agent first. Nobody is blamed for reporting. Near misses count.
Why it is there
Reporting only works if people are not punished for it. You want to hear about the near miss while it is still small.
The rule
The policy owner reviews this policy and the agent register every three months, and after any serious incident. Changes are shared with everyone.
Why it is there
AI changes quickly. A policy written today will be partly wrong in six months: a new tool, a new model, a new use. Three months is often enough to keep up and rare enough that it really happens.
What data can go into an AI tool?
Sort every kind of data into three colours. People remember three. Pick an example to see its colour.
What kind of data do you want to use? Pick one.
Green
Public or low-risk data.
Any approved tool.
Amber
Internal documents, code, non-personal business data.
Approved tools marked for Amber, on company accounts.
Red
Customer personal data, health or financial records, passwords and keys, anything under NDA.
Not in any AI tool unless the policy owner has approved that specific use in writing.
What is an agent register?
An agent register is one list of every AI agent or automation that runs without a person starting it each time. An example is a scheduled job, a support bot or a workflow that updates your CRM. Each one is listed with what it does, what it can access, its limits, one owner, how to stop it and when it was last reviewed.
It is the part we would keep if we could keep only one. Try it below.
Build one register entry. Tick what you have written down.
This agent does not run yet
Missing: what it does, what it can access, spend and step limits, one named owner, how to stop it, last review date. If it is not in the register, it does not run.
How do you adopt it this week?
In a small company, most of this fits in an afternoon.
Your first week
0 of 6 done
What does a policy not do?
A policy says what is allowed. It does not decide where AI should be used in your business, which tools fit which job, or how to build the workflows that make AI worth it. An AI leader makes those decisions.
Without that person, a policy is often written once and then forgotten. A Fractional CAIO keeps the policy, the agent register and the decisions around them current as your business and tools change.
Working with us
The template is free to copy, change and use, with or without us: download the AI guidelines template. If you want someone senior to own the policy, the Fractional CAIO page explains how that works.
Frequently asked questions
Does a small business need an AI policy?
Yes, and a short one is better than a long one. Without written rules, people either avoid AI because they do not know what is allowed, or use it with customer data and personal accounts because nobody said not to. Both are expensive. A one-page policy that names the approved tools, the data that must never go into them, what a person must check and who owns each automation removes most of that risk in an afternoon.
What should an AI policy for an SME include?
Eight things: which tools are approved and for what; which data can go into which tools; what a person must review before AI output is used; a register of every agent or automation with a named owner; spend caps and a way to stop any agent quickly; what you tell customers about AI; how to report an AI incident; and how often the policy is reviewed. Anything longer than one page will not be read.
What is an agent register?
An agent register is a single list of every AI agent or automation that runs without a person starting it each time. For each one it records what it does, what systems and data it can access, its spend and step limits, the one person who owns it, how to stop it, and when it was last reviewed. It is the simplest control a company can have over AI that runs by itself, and the first thing to check when something goes wrong.
Who should own the AI policy in a small company?
One named senior person with the authority to approve new tools and stop a risky automation. In many small companies that is the founder or the head of operations. Where AI is being adopted across the whole business, it is often a Chief AI Officer or a fractional one. What matters is that it is a person, not a committee, and that everyone knows who it is.