# AI policy for employees: a usage policy template people follow

> What an AI policy for employees should contain, a usage policy template you can adapt, and how to roll it out so employees use the approved tools instead of their own accounts.

Language: en · Category: governance · Author: Nicolas Corod (Founder and chief executive officer) · Published: 2026-11-10

Most AI policy templates are correct. They list approved tools, ban confidential data in public chatbots and ask for a human check before anything leaves the building. What they rarely explain is why employees who have read the policy keep using their own accounts anyway.

The numbers suggest the gap is wide. In a Qualinsight survey of 1,030 professionals in French-speaking Switzerland, [reported by PME in July 2026](https://www.pme.ch/strategie/ia-au-travail-72-des-romands-lutilisent-souvent-en-secret/rl801nw), 27% of people who use AI at work do so without approval from their company or its IT department, and 49% of respondents say their employer has set no clear rules on AI. This article covers what an AI policy for employees should contain, a usage policy template you can adapt, and how to roll it out so people follow it.

## What is an AI policy for employees?

An AI policy for employees is a short internal document that states which AI tools staff may use, for which tasks, with which data, and who checks the result. It turns individual judgement calls into shared rules, so a sales manager and a payroll officer reach the same answer when they open an AI assistant.

It is not the same document as a governance framework, which sets how a company decides, approves and reviews AI use across the organisation; the guide to [enterprise AI governance for leaders](/en/blog/enterprise-ai-governance/) covers that layer. The employee policy is the part every person reads: one or two pages, written for the person at the keyboard, not for the board.

Different names cover the same document. An AI acceptable use policy, an AI usage policy and a company AI policy usually mean this one-page rulebook for staff.

## Why do employees ignore most company AI policies?

Employees mostly route around AI rules because the approved option is slower or missing, not because they want to break them. A policy that bans without offering an alternative tends to move usage out of sight, where it becomes [shadow AI](/en/blog/what-is-shadow-ai/): AI used for work through accounts the company does not provide or see.

The motive is usually efficiency. At a round table on AI in human resources at Salon RH 2026 in Lausanne, the panel described a presentation that took 30 minutes with Claude and three hours with the tool the company provided. Faced with that gap, a ban mostly teaches people to stop mentioning it.

The legal case for rules is still clear. David Raedler, lawyer and professor of employment law at the University of Lausanne, put it plainly in the same PME article: "The minimum is to set rules." Under the [General Data Protection Regulation (GDPR)](https://eur-lex.europa.eu/eli/reg/2016/679/oj), the company remains responsible for the personal data its staff paste into a tool. In Switzerland, the [Federal Act on Data Protection (FADP)](https://www.fedlex.admin.ch/eli/cc/2022/491/en) allows fines of up to CHF 250,000 for certain intentional violations, imposed on the responsible individual rather than on the company.

So the question is not whether to have a policy. It is whether the policy makes the approved path easier than the hidden one. The [shadow AI statistics for 2026](/en/blog/shadow-ai-statistics-2026/) show how far the hidden path already reaches.

## What should an AI acceptable use policy include?

An AI acceptable use policy needs seven sections: purpose and scope, approved tools, data rules, human review, prohibited uses, ownership and reporting, and review dates. Each one answers a question an employee will otherwise answer alone, usually in a hurry.

| Section | The question it answers | Common mistake |
| --- | --- | --- |
| Purpose and scope | Who does this apply to, contractors included? | Writing it for the IT team instead of every employee |
| Approved tools | Which assistants may I use, with which account? | Listing banned tools without naming an approved one |
| Data rules | What may I paste, and what never? | "No confidential data" with no example of what that means |
| Human review | Who checks AI output before it is used? | Assuming the author checks, without saying when |
| Prohibited uses | Which decisions stay fully human? | A long list nobody remembers |
| Ownership and reporting | Who answers questions, and how do I report a mistake? | No named owner, so every question goes to IT |
| Review | When does this change? | A policy written once and left for two years |

Two sections decide whether the rest works. The data rules need three concrete tiers that an employee can apply in five seconds. The ownership section needs a named person, so the policy has someone to improve it.

## AI usage policy template you can adapt

The template below is a starting point for a company of 50 to 1,000 people. Replace the bracketed parts, keep it to two pages, and remove any section that does not apply.

**1. Purpose and scope.** This policy sets how employees of [Company] use AI assistants for work. It applies to every employee, contractor and intern who uses an AI tool on [Company] tasks or data, on any device.

**2. Approved tools.** You may use [Claude / ChatGPT / Copilot, with the company account] for work. Do not use personal AI accounts for [Company] tasks. To request a new tool, write to [policy owner]; you will get an answer within [10 working days].

**3. Data rules.** Before you paste anything, check its tier:

1. **Public:** published material, your own drafts without client or employee names. Allowed in approved tools.
2. **Internal:** project documents, internal figures, client names. Allowed only in approved tools with the company account.
3. **Restricted:** health data, salaries, evaluations, passwords, client data covered by a confidentiality agreement. Never in an AI tool unless [policy owner] has approved that specific use in writing.

**4. Human review.** You are responsible for anything you send, publish or decide with AI help. Check facts, figures and names before use. Say when a client deliverable was prepared with AI if the client contract requires it.

**5. Prohibited uses.** Do not use AI to make or recommend decisions on hiring, dismissal, pay or performance without a human decision on record. Do not use AI to create content that impersonates a real person.

**6. Ownership and reporting.** [Name, function] owns this policy. Report a mistake, such as restricted data pasted by accident, to [policy owner] within [24 hours]. Reporting early is expected and is not a fault in itself.

**7. Existing use and review.** If you already use AI tools that this policy does not list, declare them to [policy owner] by [date]. Use declared in this period carries no sanction and helps decide which tools to approve. This policy is reviewed every [six months] and after any incident.

## How do you roll out a company AI policy that people follow?

Start from the use that already exists, write the rules with the people who use AI daily, and give them an approved path on day one. A policy announced from the top, with no alternative and no amnesty, mostly produces silence.

1. **Map current use without sanction.** Ask each team which AI tools they use and for what. The Salon RH 2026 round table recommended an amnesty first, then a clear charter.
2. **Write the policy with the heaviest users.** They know which rules are workable and which will be ignored by Thursday.
3. **Approve at least one tool before publishing.** A policy that only forbids leaves people where they were.
4. **Name an owner per area,** someone who answers questions and updates the rules as tools change.
5. **Explain the why in one paragraph.** People follow a data rule more readily when they know which law or client contract it protects.
6. **Review after six months** with the declared uses and reported incidents in hand.

## How do you check that the policy holds in practice?

A written policy states intentions; checking it requires a record of what actually happened. Without that record, the six-month review relies on surveys and memory.

This is where tooling helps. Skilder works inside the assistants employees already use (Claude, ChatGPT or Copilot) and gives them business skills through roles configured from blueprints. A role bounds which skills and connected tools a team can reach, guardrails (in beta) check tool calls against rules the company writes, and skilder keeps an execution trace per person with an exportable audit log. The [AI audit trail](/en/blog/ai-audit-trail-execution-logs/) article shows what that record contains. To map your own policy onto your teams' real use, [book a free 30-minute exchange with an expert](https://koalendar.com/e/meet-with-nicolas-9?utm_source=skilder.ai&utm_medium=blog_ai_policy).

**Takeaway:** an AI policy works when the approved path is easier than the hidden one. Declare existing use without sanction, approve a tool before you forbid one, and name the person who keeps the rules current.

To turn this template into a policy your teams actually follow, [book a free 30-minute exchange with an expert](https://koalendar.com/e/meet-with-nicolas-9?utm_source=skilder.ai&utm_medium=blog_ai_policy).
