An AI Usage Policy Template for Small Teams

A short, practical AI usage policy template for small teams: approved tools, what never to share, human review and who to ask. Adapt it to your needs.

Most small teams already use AI tools every day, often without any agreed rules. That works until someone pastes a customer list into a chatbot or publishes an AI-written claim nobody checked.

An AI usage policy fixes that. It does not need to be long. Below is a template you can adapt, followed by tips for rolling it out.

Before you use it: treat this as a starting point, not a finished policy. Adapt it to your tools, data and industry, and have your legal and security advisers review it.

The template

1. Purpose

We encourage everyone to use AI tools to work faster and better. This policy explains how to do that safely, protecting our customers, our colleagues and our company.

2. Approved tools

Use only the AI tools on our approved list for work: [list tools and plans]. Use your work account, not a personal one. To request a new tool, contact [owner].

Keep the list short and prefer plans with clear terms on data retention and model training.

3. Never share

Never enter the following into any AI tool, unless the tool has been specifically approved for that data:

  • Personal data about customers, candidates or colleagues, such as names with contact details, identity numbers or financial details
  • Passwords, API keys, tokens or other credentials
  • Confidential company information, such as unreleased financials or contracts
  • Information a customer or partner has shared with us in confidence

Add examples from your own work. They make the rule real.

4. Good uses

AI tools are well suited to drafting and editing text, summarising non-confidential documents, brainstorming, explaining concepts, and help with code that contains no secrets or customer data.

5. Check before you use it

You are responsible for anything you use or share, whether you wrote it or an AI tool did. Check AI output for accuracy, especially facts, figures, names and code. Do not publish or send AI-generated content to customers without reading it carefully.

6. Decisions about people

Do not use AI tools to make decisions about people, such as hiring, performance or pay, without human review. AI output can be one input, never the final say.

7. Be open about it

If AI tools contributed significantly to work you share with customers or the public, follow our guidance on disclosure: [your guidance].

8. Customer and product AI features

Any AI feature in our product, or any use of AI on customer data, needs approval from [owner] before launch.

9. If something goes wrong

If you think you have shared something you should not have, tell [contact] straight away. Reporting quickly matters more than blame.

10. Ownership and review

[Owner] maintains this policy and reviews it at least twice a year. Questions go to [contact].

Rolling it out

  1. Fill in the blanks with your tools, owners and contacts.
  2. Get it reviewed by your legal and security advisers.
  3. Walk the team through it in a short session with real examples. Ask what tools people already use; the answers are useful.
  4. Make it easy to find, linked from your handbook or intranet.
  5. Back it with controls where the risk is highest. A policy sets expectations; technical checks on prompts catch the mistakes people still make. See using AI tools at work without leaking personal data.
  6. Keep a register of the AI tools and features in use, what data each touches and who owns it.

Keep it alive

Revisit the policy whenever you adopt a new tool or a new use of AI. A short policy that stays current is far more useful than a long one that is out of date.

Where Arborworld fits

Arbor Govern keeps one register of every AI system you build, buy or deploy, with evidence an auditor can verify.

Explore Arbor Govern

Questions people ask

Does a small team really need an AI policy?

Yes, but it can be short. A one-page policy that people actually read does more than a long one that nobody opens. It gives staff clear answers and gives you a basis for consistent decisions.

Can we use this template as it is?

Use it as a starting point. Adapt it to the tools you use, the data you hold and your industry, and have it reviewed by your legal and security advisers before you adopt it.

How often should we update it?

Review it at least twice a year, and whenever you adopt a new AI tool or start using AI for a new kind of work. AI tools change quickly.

Vinod Keshav
Written by

Vinod Keshav

Vinod Keshav is a founder of Arborworld, which builds software for hiring, HR, and personal data protection. Arborworld's two founders bring over 45 years of shipping products at scale across travel, e-commerce, fintech, gaming, and mobile.

More from Arborworld resources