What a company AI policy covers
A company AI policy sets out which AI tools staff may use and for what, which data never goes into them, who checks the output and who is accountable for what. An AI policy template needs eight sections for that, and a ninth with separate rules as soon as AI agents act in your systems.
A chat tool produces a draft that a person reads before using it. An AI agent, by contrast, reads a complaint from the service inbox, pulls order data from the ERP and creates a draft credit note there, so what happens depends on permissions and checkpoints rather than on one person's diligence.
Keep the policy short enough for staff to go through it in full during induction training. Anything that changes often, such as the list of approved tools, belongs in a register maintained by IT that the policy refers to.
Is a company AI policy a legal requirement?
No law requires a document called an AI policy. Several duties are hard to meet demonstrably without written rules, though, and the policy is where they come together. This overview is not legal advice; the assessment for your company belongs with data protection, compliance or counsel.
Since 2 February 2025, Article 4 of the EU AI Act has required providers and deployers to take measures to support the AI literacy of their staff and of others using AI systems on their behalf, which covers any company using AI tools in its business. Since the amendment by Regulation (EU) 2026/1744 they need not guarantee any specific level of literacy, and neither Article 99 of the Regulation nor Germany's implementing act, the KI-MIG, sets a separate fine for it.
The European Commission's Q&A on AI literacy states that no certificate is needed and that organisations can keep an internal record of training. Germany's market surveillance authority, the Bundesnetzagentur, adds that a lack of AI literacy can be regarded as a breach of the duty of care, particularly where damage occurs.
Since 2 August 2026 the transparency duties of Article 50 have applied too. Deployers who use AI for deep fakes, or for text published to inform the public on matters of public interest, must disclose that the content is artificially generated or manipulated, unless such text has undergone human review or editorial control and a natural or legal person holds editorial responsibility. Four further sets of rules make a written policy sensible even without an explicit duty.
- 01
Entering personal data into a cloud tool usually requires a data processing agreement under Article 28 GDPR, and Article 22 GDPR limits solely automated decisions about people.
- 02
Under Article 2(1)(c) of the Trade Secrets Directive (EU) 2016/943, information only counts as a trade secret if it has been subject to reasonable steps to keep it secret, and a rule on which data may go into which tool is one of those steps.
- 03
In Germany, section 90(1) no. 3 of the Works Constitution Act (BetrVG) requires employers to inform the works council in due time about plans for working procedures, including the use of artificial intelligence.
- 04
Under section 130 of the German Administrative Offences Act (OWiG), a business owner who omits the supervisory measures needed to prevent violations commits an offence if a violation occurs that proper supervision would have prevented or made much harder; policy, training and sampling are part of documented supervision.
AI policy template: eight sections with sample wording
The template has eight sections that you fill in with your own roles, tools and deadlines; replace the names in square brackets with the responsible function in your company.
Word the third section on data classes with particular care. A tool can be replaced, but an entered design drawing or price list cannot be retrieved if the provider stores inputs or uses them for training, which is why IT checks these two points before approving a tool for confidential data.
| Section | What it governs | Sample wording |
|---|---|---|
| 1. Scope | Who and which systems are covered | This policy applies to all employees, agency workers and external service providers who use or operate AI systems on behalf of [Company], including AI features in existing software such as the office suite, CRM or ERP. |
| 2. Approved tools | Which tools are permitted and how a new one is added | Only tools in the register of approved AI tools may be used. [Head of IT] adds a tool once the contract, data processing terms, storage location and use of inputs for training are clarified. Private accounts may not be used for work. |
| 3. Data classes | Which data may go into which tool, and which never may | Public information may go into any approved tool, internal information only into tools with a company account, and confidential information such as customer data, prices, design data and contracts only into tools approved for that class. Never enter passwords or access keys, data whose disclosure an NDA rules out, or special categories of personal data under Article 9 GDPR, unless [Data Protection] has approved a system for them. |
| 4. Review and labelling | Who checks AI output and when it is labelled | Anyone using AI output checks it first and answers for it as for their own work; figures, quotations, standards and legal statements are checked against the source. Content covered by Article 50(4) of the AI Act, such as deep fakes, is labelled unless an exception applies. |
| 5. Responsibilities | Who owns the policy, the tool register and new use cases | [Management] owns this policy, [Head of IT] the tool register and [Data Protection Officer] the review of new use cases involving personal data. Every manager makes sure their team knows this policy. |
| 6. Training under Article 4 | How AI literacy is built and recorded | Before first use, staff complete an introduction to how the tools work, their limits and this policy. Anyone releasing output in an AI workflow is also trained on that workflow. [HR] records content, duration and participation. |
| 7. Incident reporting | What is reported, to whom and how fast; Article 33 GDPR sets 72 hours, where feasible, for notifying personal data breaches to the authority | Anyone who notices that confidential data has been entered into an unapproved tool, that AI output has caused harm or that an agent has acted outside its permissions reports it to [Function] immediately. A report is not treated as misconduct. |
| 8. Review | When and by whom the policy is updated | [Role] reviews this policy at least once a year and after every material change in law or tools, and agrees changes with data protection and the works council. |
Section 9: an AI policy for AI agents that act in your systems
AI agents need a section of their own because they do not just generate text but act with write access in the ERP, CRM, ticket system or DMS. Rules about what staff type into a chat window do not reach them, because the agent works without anyone seeing each step.
Two risks explain rules 9.2 and 9.5. An agent reading emails or PDFs can follow instructions hidden in them (prompt injection), and draft-only write access contains the damage. A model change by the provider can shift behaviour across thousands of cases without any change in the workflow, which a test set run before every release exposes.
Section 9 does not set details per workflow; it sets the conditions under which an agent may go live at all. The details sit in the control set of each workflow, described in governance inside the workflow, and the roles behind them in the operating model for AI in operations. The glossary of AI agent terms defines control set, shadow mode and confidence threshold.
| Rule | Sample wording |
|---|---|
| 9.1 Deployment only after approval | An AI agent that reads or writes in company systems goes live only after approval by [Head of IT], [Data Protection] and the responsible department head. Staff do not set up their own agents with access to company systems. |
| 9.2 Write access only through a control set | Every agent has a written control set covering permissions, thresholds, checkpoints, logging and escalation. It gets write access only as defined there, for example in draft status only. |
| 9.3 A named workflow owner | Every agent has a named person in the business who is measured on the workflow's outcome and co-decides on widening and withdrawing release rights. |
| 9.4 Shadow mode before release | An agent acts without individual release in a case category only once shadow mode has met the acceptance criteria agreed in advance for that category. Refusals and payments stay with people. |
| 9.5 Change control | Changes to prompts, rules, thresholds and model versions run against a test set before release, are versioned and are approved by [Risk Owner]. A model change announced by the provider counts as a change. |
| 9.6 Logging | Input, sources used, the agent's output and the release are logged per case and kept as long as the business record, for high-risk systems at least six months under Article 26(6) of the AI Act. |
| 9.7 Shutdown | [Operations] can stop any agent at any time, and manual operation can be restored within one hour. |
Policy for people, control set for each agent
The policy governs what people may and must do, and the control set governs what one particular agent may do in one particular workflow. The policy requires a control set for every agent and names who approves it; the workflow defines its content.
The policy might say, for example, that an agent writes in draft status only until shadow mode meets the acceptance criteria. The control set for claims handling then says that the agent may create draft credit notes in the ERP, that cases above the threshold go to quality management and that refusals never go out without a claims handler.
The two stay separate because a policy is revised once a year and agreed with employee representatives, while a control set changes with every new threshold and model version. If the details sat in the policy, every recalibration would have to go through the same approval round.
The Workflow Assessment determines, among other things, the risk class and owners for the top candidates and sets the first workflow's checkpoints in the build scope. The AI Act check gives a first classification under the AI Act beforehand.
Rolling out the policy: employee representatives, training and review
Where there is a works council or other employee representation, roll the policy out together with it. In Germany, the works council co-determines the introduction and use of technical devices designed to monitor employees' behaviour or performance under section 87(1) no. 6 BetrVG, and the Federal Labour Court treats a device as designed for this when it is objectively suitable (order of 13 December 2016, 1 ABR 7/15). An AI tool that links inputs to user accounts collects that kind of information.
Where the works council has to assess the introduction or use of AI, section 80(3) BetrVG deems calling in an expert necessary. Allow time for that and present the tool register, data classes and agent rules together before the first go-live, so that tools are not negotiated one by one; whether such a framework suffices in a given case is for your employment lawyers. Outside Germany, check the local rules on informing and consulting employee representatives.
For training under Article 4, the Bundesnetzagentur suggests three building blocks, namely identifying needs, designing measures, and documenting, evaluating and refreshing them. Its guidance lists type, content and duration of measures and the participants as what to record. Review the policy itself at least once a year and after every change in law or tools.
Sources
- 01Regulation (EU) 2024/1689 (AI Act), EUR-Lex
- 02Regulation (EU) 2026/1744 (Digital Omnibus on AI), EUR-Lex
- 03AI Act, Article 4 AI literacy, consolidated text on the European Commission's AI Act Service Desk
- 04AI Act, Article 50 Transparency obligations, AI Act Service Desk
- 05European Commission, AI literacy: questions and answers
- 06Bundesnetzagentur, AI Service Desk: AI literacy (in German)
- 07German act on AI market surveillance and innovation (KI-MIG), gesetze-im-internet.de (in German)
- 08Regulation (EU) 2016/679 (GDPR), EUR-Lex
- 09Directive (EU) 2016/943 on the protection of trade secrets, EUR-Lex
- 10Works Constitution Act (BetrVG), English translation, gesetze-im-internet.de
- 11Section 130 Administrative Offences Act (OWiG), gesetze-im-internet.de (in German)
- 12Federal Labour Court (BAG), order of 13 December 2016, 1 ABR 7/15 (in German)