Home

Guide

AI usage policy for employees: what to include, plus a template

A good AI policy fits on two pages and makes sense on first read. Here is what it should cover, a template to adapt and how to get people to follow it. Practical guidance, not legal advice.

The problem: people already use AI, but nobody has said how

Without a policy, everyone makes it up. Someone pastes a client contract into a free chatbot to summarise it; someone else has AI draft a reply and sends it unread; a third person avoids AI entirely for fear of getting it wrong. All three are a problem.

An AI usage policy is not there to ban things. It tells people what they can do with confidence, what they must never do and who to ask. If it is long and vague, nobody reads it. If it is short and specific, it becomes the everyday reference.

How it works with Tessa

  1. 1

    One approved tool for daily work

    Tessa works on company email, Slack and meetings under a data processing agreement with data in the EU, instead of scattered personal accounts.

  2. 2

    Human review built in

    Anything leaving the company (emails, quotes, CRM notes) waits for approval by default. That policy rule is already enforced.

  3. 3

    Automatic minimisation

    Before text reaches the model, email addresses and phone numbers are replaced with placeholders. What she reads from each person stays private.

  4. 4

    Everything is logged

    The control panel shows each action Tessa took and why, so you can check compliance without monitoring anyone.

What you get

  • Less shadow AIWhen there is an approved tool that actually helps, people stop pasting data into personal accounts.
  • Rules that enforce themselvesPrior approval and data masking don’t depend on anyone remembering them.
  • Paperwork readyA published DPA, sub-processor list and security policy for your records of processing.
  • Team trustNo individual metrics for managers: the policy protects employees too.

What an AI usage policy should cover

Before drafting, answer these questions. Any you can’t answer is the conversation to have with leadership, IT and data protection:

  • Which AI tools are approved, and with which accounts (company, not personal)?
  • Which data must never go into AI, and which may go only into approved tools?
  • What must a person review before anything leaves the company?
  • When do you disclose that text or analysis was produced with AI?
  • Who approves a new tool, and how fast do they respond?
  • Who do you report a mistake to (data that shouldn’t have gone out, a wrong answer that was sent)?

Template (1/2): purpose, tools and data

Copy and adapt. Replace the text in brackets. It’s a starting point, not a finished legal document:

  • 1. Purpose. This policy explains how we use artificial intelligence at [Company] to work better without putting client, colleague or supplier data at risk. It applies to all staff, contractors and interns.
  • 2. Approved tools. For work, use only these tools with your company account: [list]. Free personal accounts are not used with company information. To propose a new tool, contact [person or channel]; we reply within [timeframe].
  • 3. Data that never goes into a non-approved AI tool: client, employee or candidate data; contracts, proposals and non-public pricing; credentials and keys; code or internal documents marked confidential.
  • 4. Special category data (health, union membership, beliefs, children’s data): never entered into any AI tool without explicit approval from [data protection lead].
  • 5. Minimisation. Even in an approved tool, enter only what the task needs. If a person’s name isn’t necessary, leave it out.

Template (2/2): human review, transparency and questions

  • 6. Human review. AI suggests, a person decides. Anything sent outside the company on behalf of [Company] is reviewed first by whoever sends it. Decisions about people (hiring, evaluating, disciplining, granting or refusing something) are never made by AI alone.
  • 7. Accountability. Whoever uses AI owns the result as if they had done it by hand: check figures, names, dates and quotes before using them.
  • 8. Transparency. Say that AI was used when the recipient could reasonably expect work done by a person, or when a client or regulation requires it.
  • 9. No surveillance. [Company] does not use AI to measure anyone’s individual activity or productivity.
  • 10. Incidents. If data leaks by mistake or AI produces something harmful, tell [person or channel] the same day. Reporting promptly is never penalised.
  • 11. Training and review. Everyone who uses AI gets a short training session. This policy is reviewed every [6 or 12] months. Owner: [name and role].

GDPR: what the policy can’t leave out

When an AI tool processes personal data on your company’s behalf, the provider is a processor, and Article 28 of the GDPR requires a data processing agreement. That’s why the list of approved tools is the heart of the policy: it should only include tools that offer one, with data stored in the EU or under valid transfer safeguards.

Add the processing to your records of processing activities, inform staff and check with your DPO or adviser whether you need an impact assessment. The EU AI Act also expects people who use these systems to have sufficient AI literacy, so the training in clause 11 is not decoration.

How to make it stick

A policy nobody knows about protects nobody. What actually helps:

  • Walk people through it in 15 minutes, with real examples from each team’s work.
  • Offer an approved alternative that is as convenient as a personal account.
  • Build rules into the tool where you can (prior approval, data masking) rather than relying on memory.
  • Publish an FAQ and update it with the questions that come in.

Where Tessa fits

Tessa can be one of the approved tools in your policy for daily work across email, Slack, meetings and documents. She comes with a published DPA, sub-processor list and security policy; stores data encrypted in the EU; masks email addresses and phone numbers before they reach the model; and, on request, runs analysis on a European AI model. Anything leaving the company waits for approval, and the control panel logs everything she does. This guide is still for information only: review your policy with your adviser.

What Tessa reads for each person stays private, your data is stored in the EU and nothing goes out without your approval.

Frequently asked questions

What should an AI usage policy include?

Approved tools, data that must not be entered, human review of anything going out, transparency, incident reporting and an owner. Ideally it fits on two pages.

Should we ban ChatGPT at work?

You can, but bans rarely work: people use it on their phones anyway. It’s usually more effective to approve a tool with a proper contract and clear rules, and ban only the use of personal accounts with company data.

Is an AI policy legally required?

No law requires a document with that name, but GDPR requires you to control who processes personal data and the EU AI Act expects AI literacy among users. A policy is the simplest way to cover both.

Do we have to tell clients we used AI?

It depends on context and contract. As a rule of thumb, say so when the client could expect work done by a person or explicitly asks.

How often should an AI policy be reviewed?

Every six to twelve months, or sooner if your approved tools or the rules change. Give it a named owner so it doesn’t gather dust.

What does your team look like?

Same AI for both. Where you start is what changes.

  • Companies

    30 to 250 people

    Best fit for this page

    What gets decided gets done

    Minutes and tasks from every meeting, commitments that get followed up and a pulse per team, without watching anyone.

  • Startups

    5 to 30 people

    Grow without losing the thread

    Tasks from email and Slack, follow-ups, sales and investors, without everything landing on the founders.

Add an AI with a DPA and EU data to your approved tools. Book a demo.

Start free

Free plan for teams of up to 3 people. Anything that leaves the company waits for your approval.