Skip to content
Cortaris

Governance

AI policy template: rules for staff and for AI agents

Whether a company AI policy is a legal requirement, which eight sections it needs and which extra rules apply to AI agents that write to your systems. With sample wording to adapt.

10 min readUpdated 11 October 2026

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.

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.

SectionWhat it governsSample wording
1. ScopeWho and which systems are coveredThis 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 toolsWhich tools are permitted and how a new one is addedOnly 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 classesWhich data may go into which tool, and which never mayPublic 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 labellingWho checks AI output and when it is labelledAnyone 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. ResponsibilitiesWho 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 4How AI literacy is built and recordedBefore 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 reportingWhat is reported, to whom and how fast; Article 33 GDPR sets 72 hours, where feasible, for notifying personal data breaches to the authorityAnyone 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. ReviewWhen 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.
Sample wording to adapt. Replace the names in square brackets with the responsible function.

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.

RuleSample wording
9.1 Deployment only after approvalAn 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 setEvery 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 ownerEvery 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 releaseAn 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 controlChanges 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 LoggingInput, 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.
Section 9 of the policy. The values for each workflow sit in its control set.

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.

Questions

Common questions

Is a company AI policy mandatory?
No law requires a document with that name. Article 4 of the EU AI Act does require AI literacy measures, though, and GDPR, trade secret law and, in Germany, works council rights set rules that a policy brings together in a form you can demonstrate. The assessment for your company is for your counsel.
What should an AI usage policy for employees include?
At a minimum the approved tools, the data classes with a clear list of what never goes into a tool, how output is checked and labelled, training and incident reporting. Responsibilities and a review date keep it maintained. If AI agents act in your systems, add a separate section with rules for them.
Do we need an AI officer?
No. The European Commission's AI literacy Q&A states that no specific governance structure is mandated for Article 4, and the Bundesnetzagentur lists an AI officer among the things Article 4 does not require. A named owner for the tool register and a workflow owner for each AI agent are still worth having.
How does an AI policy apply to AI agents?
Only through a section written for them. Rules about what staff type into chat tools do not reach an agent with write access to the ERP; it needs deployment approval, a control set, shadow mode, change control and logging. The guide to human in the loop AI shows how release levels are set per case category.

Next step

Start with one workflow.

Bring the process that costs you the most time. In 30 minutes we tell you whether it is worth automating, roughly what it would take, and which step comes first.