Control over AI
Blog
Trust and proof 7 min read

How do you know your AI policy is actually followed?

A signed policy and a training log tell you what people have read. Whether the policy is followed you read from three numbers about everyday practice, and from what you do when those numbers disappoint.

Abstract winding path through soft hills
Quick answer

Whether an AI policy is followed you do not read from the document but from three numbers about everyday practice: what share of AI use runs through allowed tools and which way that is moving, what happens after someone sees a notice at a tool that is not allowed, and how many tools with real use still have no decision and whether that number is growing. All three can be measured without tracking people. And when the outcome disappoints, the question is not who ignores the policy, but whether the policy pinches, whether the alternative is good enough, and whether the risk is smaller than assumed.

01

Read and understood tells you what people knew on the day of the email, not what they did on the day of the deadline

02

The share of use through allowed tools is the number that ties policy and practice together

03

What happens after a notice shows whether the designated alternative is really an alternative

04

Tools without a decision that keep growing are the most honest signal that the policy is behind

05

A disappointing number is a question for the policy, not a reproach to employees

A privacy officer at an insurer is asked by the auditor whether the AI policy is being complied with. She has the policy, the acknowledgements (87 percent clicked "read and understood") and the attendance list from the training. What she does not have: any idea whether someone is pasting a claims file into a chatbot this afternoon.

Whether an AI policy is followed you do not read from the document but from three numbers about practice. What share of AI use runs through allowed tools, and which way is that moving. What happens after someone sees a notice at a tool that is not allowed. And how many tools with real use still have no decision, and is that number growing. All three can be measured without tracking people, and all three, when the outcome is poor, put a question to the policy rather than to the employee.

Why does "read and understood" say so little?

Because it measures what someone knew on the day of the email. The policy is followed or ignored on a different day: the day of the deadline, when a colleague needs a quick summary and the tab with the chatbot is already open. An AI policy on paper describes what should happen; it does not turn up at the moment that matters.

The GDPR asks in Article 5(2) that an organisation can demonstrate that it complies with the principles. A document and a signature demonstrate that there is a policy. Whether it is applied takes an observation of practice. There are three numbers for that, and none of them needs a name.

Which three numbers show it?

The share of AI use through allowed tools. Of all the times an AI tool is opened in the organisation, what part is a tool with the status allowed or limited use. This is the number that ties policy and practice together. The direction counts more than the level: 70 percent is good news if it was 55 last quarter, and a signal if it was 85.

Notices and what happened next. When someone opens a tool that is not allowed and the decision appears there, two outcomes are possible: the alternative opened, or continued anyway. The ratio between those two says whether the designated alternative is really an alternative. If almost nobody picks it, the decision may be right, but the route is not.

Tools without a decision that keep growing. Every organisation has tools nobody has decided on yet. That is an honest status. It becomes a signal when such a tool is opened more often every month: then the policy has a gap right where the work is.

NumberWhat it saysWhat it does not sayWhen it disappoints, look at
Share through allowed toolsWhether practice follows the policyWhy, or why notWhich tools carry the use outside the policy
Outcome after a noticeWhether the alternative gets chosenWhat someone did afterwardsWhether the alternative can handle the task
Growing tools without a decisionWhere the policy is behindWhether the tool is a riskThe decision still to be taken

What is missing here is the number of prompts. It says how busy things are, not whether the policy is followed. Which other numbers about AI use are worth having is in measuring AI use.

And the rule about sensitive data?

Most policies contain two kinds of rules: which tools, and which data. The three numbers above cover the first kind. The second kind, "no customer data in a prompt", takes a different observation: how often a sensitive item gets a marking while someone types, and what happens next. Changed before sending, or sent anyway.

That too is a count without people: per app, per data type, with the outcome. This is what it looks like, with the trend over time and the share that was changed before sending.

Detections over timeLast 30 days
12,438+18% vs the previous period
Detections by platform
ChatGPT
ChatGPT
78% adjusted
8,124
Gmail
81% adjusted
3,210
Gemini
74% adjusted
812
Most encountered data types
Name
4,212
Email address
2,930
Credit card
1,486
Account number
1,104
Diagnosis
612
SensitiveHighly sensitive
BeeSensible dashboard: aggregated detections and top sources, without monitoring individuals.

If the line of red markings drops after a training, the training worked. If the share "sent anyway" stays high in one app, that is a conversation about that app, not about a person.

What does that look like at the insurer?

The privacy officer puts a quarter's numbers next to the policy. The policy says: Copilot for text work, other chatbots no. The practice: 58 percent of AI use runs through Copilot, and that share is slowly rising. At ChatGPT the notice was shown 340 times; 190 times someone opened Copilot, 150 times someone continued. A transcription tool for customer calls sits on "no decision yet" and is opened more often every month.

None of this is an incident. It is a policy that works on one point (Copilot is gaining ground), falters on one point (150 times continuing is not disobedience, it is tasks for which Copilot apparently is not enough) and lags on one point (something has to be decided about the transcription tool, because customer calls go through it). The auditor gets three numbers with a direction and one open decision. That is a different conversation from an attendance list.

What do you do when the policy is not followed?

Three questions, in this order, before you tighten anything.

Does the policy pinch? A rule that forbids a task without offering a route does not get followed. If the 150 times continuing at ChatGPT are mostly long texts and code, the policy forbids work people have to do. Then the adjustment is: designate a business environment for that work, or write down the condition under "limited use".

Is the alternative good enough? If the alternative is rarely chosen after a notice, the route is the problem. That is information about Copilot, not about the employee. Sometimes the answer is a different preferred route for that task.

Is the risk smaller than assumed? A tool that is not allowed because a free account was once used can carry a different risk through a business account with a data processing agreement. Then limited use is the better decision, and the share through allowed tools rises without anyone having to do anything differently.

Only when those three questions are answered is a stricter measure on the table. Usually it turns out not to be needed. The policy was written for last year's tools, and the numbers show where practice has moved since.

BeeSensible counts for this which AI tools are opened (only the domain, at most once a day per device), shows per decision how often a notice was shown and what someone did next, and keeps the share of use through allowed tools with its trend. The Risk screen puts tools that are not allowed but still in use, tools without a decision that have real use, and fast growers at the top; the decision can be recorded right there. The usage data contains no user ID and no content, and nowhere in the dashboard is there a breakdown per employee. What else the module does is on the product page on AI tools.

When is this evidence, and when not yet?

The three numbers are an observation. They become evidence only when each number states which measure it supports and what it covers. The share through allowed tools covers browser use on devices where the extension is installed, not an employee's phone. Whether a data processing agreement was signed with the vendor, no measurement knows. Whoever adds that, and honestly writes "not substantiated" next to that last measure, has something an auditor can work with. Why that scope and that red row make the difference is in why a dashboard is not evidence; the other pieces on this subject are collected in the AI governance topic.

For the next conversation with the auditor, pick the three numbers, add the direction and the scope, and bring the one open decision. And for every number that disappoints, put the question to the policy first, before you put it to the organisation.

FAQ

Common questions

How do you measure whether employees follow the AI policy?

With numbers about tools, not about people. What share of AI use runs through allowed tools, how often a notice at a tool that is not allowed is shown and how often someone then picks the alternative, and how many tools with real use still have no decision. Together those three show whether the policy holds up in the working day, and they need no user ID.

Is a signed acknowledgement of the policy not evidence?

It proves the policy was distributed and that employees confirmed they saw it. It says nothing about what someone does under pressure, weeks later. Knowledge is no guarantee of behaviour. For the accountability principle you need, next to the document, an observation of practice.

What do you do when the AI policy is not followed?

Ask three questions before tightening anything. Does the policy pinch, because it forbids a task without offering a route? Is the designated alternative good enough for the work people do? And is the risk of the tool people use anyway perhaps smaller than assumed, so that limited use is the better decision? Usually the answer is an adjustment to the policy, not a sanction.

Can you measure compliance with an AI policy without tracking employees?

Yes. An observation like "this domain was opened on this device today" and a count of notices with their outcome need no name to show whether the policy lands. As soon as you measure per person it becomes employee monitoring, with heavier GDPR requirements and a role for the works council. To answer whether the policy works, that is not needed.

Is a dashboard with these numbers enough for an auditor?

Not yet. An auditor wants to know, per number, which measure it supports, what it covers and where it stops. The share through allowed tools covers browser use on managed devices, not phones. Add that scope, and mark measures that no measurement supports honestly as "not substantiated". Then it is evidence.

Portrait of Rens Timmermans of BeeSensible

Would you rather someone showed you?

Rens, BeeSensible

I am happy to give you a twenty-minute tour. Leave your details and I will find a moment that suits you. Calling or emailing works just as well.

Rather talk to someone first? Book a call.

Want a live demo, or a quote for 100+ users? Leave your details and we'll be in touch within one business day.