Control over AI
Blog
Trust and proof 7 min read

How do you know your AI policy is actually followed?

A signed policy tells you what people have read. Whether they follow it shows in three numbers from everyday practice, and in what you do when those numbers disappoint.

Abstract winding path through soft hills
Quick answer

The document will not tell you whether an AI policy is followed. Three numbers about everyday practice will: what share of AI use goes through allowed tools and which way that share is moving; what happens after someone sees a notice on opening a tool that is not allowed; and how many tools in real use still have no decision, and whether that number is growing. All three can be measured without tracking individuals. And when the result disappoints, the question is not who is ignoring the policy but whether the policy gets in the way of the work, whether the alternative is good enough and whether the risk is smaller than you assumed.

01

A "read and understood" click 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 AI use that goes through allowed tools is the number that ties policy to practice

03

What people do after seeing a notice shows whether the designated alternative is a real alternative

04

Growing use of tools without a decision is the most honest sign that the policy has fallen behind

05

A disappointing number is a question for the policy, not a criticism of employees

The auditor asks a privacy officer at an insurer whether staff are complying with the AI policy. She has the policy, the acknowledgements (87 per cent clicked "read and understood") and the attendance list from the training. What she does not have is any idea whether someone is pasting a claims file into a chatbot this afternoon.

The document will not tell you whether an AI policy is followed. Three numbers about practice will. What share of AI use goes through allowed tools, and which way is it moving? What happens after someone sees a notice on opening a tool that is not allowed? And how many tools in real use still have no decision, and is that number growing? All three can be measured without tracking people, and when the result is poor, all three 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 chatbot is already open in another tab. An AI policy on paper describes what should happen; it is not there at the moment that matters.

Article 5(2) of the GDPR requires an organisation to be able to demonstrate that it complies with the principles. A document and a signature show that a policy exists. To show that it is applied, you have to observe practice. Three numbers do 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 someone in the organisation opens an AI tool, what proportion involve a tool with the status "Allowed" or "Limited use"? This is the number that ties policy to practice. The direction matters more than the level: 70 per cent is good news if it was 55 last quarter, and a warning sign if it was 85.

Notices and what happened next. When someone opens a tool that is not allowed and sees the decision there, there are two possible outcomes: "alternative opened" or "continued anyway". The ratio between them tells you whether the designated alternative is a real alternative. If almost nobody chooses it, the decision may be right but the alternative is not working.

Growing use of tools without a decision. Every organisation has tools nobody has decided on yet. That is an honest status. It becomes a warning sign when such a tool is opened more often every month: it means the policy has a gap exactly where the work is happening.

NumberWhat it tells youWhat it does not tell youIf it disappoints, look at
Share through allowed toolsWhether practice follows the policyWhy, or why notWhich tools account for the use outside the policy
Outcome after a noticeWhether people choose the alternativeWhat someone did afterwardsWhether the alternative can handle the task
Growing use of tools without a decisionWhere the policy lags behindWhether the tool is a riskThe decision still to be made

One thing missing here is the number of prompts. That tells you how busy things are, not whether the policy is followed. Measuring AI use covers which other numbers about AI use are worth tracking.

What about the rule on sensitive data?

Most policies contain two kinds of rule: which tools, and which data. The three numbers above cover the first kind. The second, "no customer data in a prompt", needs a different observation: how often a sensitive detail is highlighted while someone types, and what happens next. Was it changed before sending, or sent anyway?

That too is a count without people: by app, by data type, with the outcome. Here is what it looks like, with the trend over time and the share 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
Detected entity types
Name
4,212
Email address
2,930
Credit card number
1,486
Account number
1,104
Diagnosis
612
StandardCritical
The BeeSensible dashboard: detections in aggregate and where they occur most, without monitoring individuals.

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

What does that look like at the insurer?

The privacy officer sets a quarter's numbers alongside the policy. The policy says Copilot for writing tasks and no other chatbots. In practice, 58 per cent of AI use goes through Copilot, and that share is slowly rising. On ChatGPT the notice appeared 340 times: 190 times the person switched to Copilot and 150 times they carried on. A transcription tool for customer calls is still marked "No decision yet" and is opened more often every month.

None of this is an incident. It is a policy that works in one respect (Copilot is gaining ground), falters in another (carrying on 150 times is not disobedience; it points to tasks that Copilot apparently cannot handle) and lags in a third (a decision is needed on 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 one about 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 get in the way? A rule that forbids a task without offering another way to do it will not be followed. If the 150 times people carried on to ChatGPT mostly involved long texts and code, the policy is forbidding work people have to do. The fix is then to designate a business environment for that work, or to write down the condition under "Limited use".

Is the alternative good enough? If people rarely choose the alternative after a notice, the alternative is the problem. That tells you something about Copilot, not about the employee. Sometimes the answer is a different preferred tool for that task.

Is the risk smaller than assumed? A tool refused on the strength of its free version may carry a different risk when it is used 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 change what they do.

Only once you have answered those three questions is a stricter measure worth considering. 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.

For this, BeeSensible counts which AI tools are opened (only the domain, at most once a day per device). It shows for each decision how often a notice appeared and what the person did next, and it tracks the share of use through allowed tools over time. On the Compliance screen, the "Used, not allowed" card lists the tools that are not allowed and the tools without a decision that are still in use, with their share and visits; you record the decision itself in the Inbox or the AI register. The usage data contains no user ID and no content, and the dashboard has no breakdown by employee anywhere. The product page on AI tools covers what else the module does.

When is this evidence, and when is it not yet?

The three numbers are observations. They only become evidence when each one states which measure it supports and what it covers. The share through allowed tools covers browser use on devices with the extension installed, not an employee's phone. And no measurement can tell you whether a data processing agreement was signed with the vendor. Add that scope, honestly write "not substantiated" next to that last measure, and you have something an auditor can work with. Our article on why a dashboard is not evidence explains why that scope and the "not substantiated" row make the difference; the other pieces on the subject are collected under the AI governance topic.

For your next conversation with the auditor, take the three numbers with their direction and scope, and bring the one open decision. And for every number that disappoints, put the question to the policy 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 people: the share of AI use that goes through allowed tools; how often a notice appears when someone opens a tool that is not allowed, and how often the person then chooses the alternative; and how many tools in real use still have no decision. Together they show whether the policy holds up in the working day, and none of them needs a user ID.

Doesn't a signed acknowledgement of the policy count as evidence?

It proves that the policy was distributed and that employees confirmed they had seen it. It says nothing about what someone does under pressure, weeks later. Knowledge is no guarantee of behaviour. To meet the accountability principle, you need evidence from practice alongside the document.

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

Ask three questions before you tighten anything. Is the policy getting in the way, because it forbids a task without offering another way to do it? Is the designated alternative good enough for the work people do? And could the risk of the tool people use anyway be smaller than you assumed, making "Limited use" the better decision? Usually the answer is to adjust the policy, not to impose a sanction.

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

Yes. An observation such as "this domain was opened on this device today" and a count of notices and their outcomes show whether the policy is landing, without a single name. Once you measure per person, it becomes employee monitoring, with stricter GDPR requirements and a role for the works council. You do not need that to know whether the policy works.

Is a dashboard with these numbers enough for an auditor?

Not yet. For each number, an auditor wants to know 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 label any measure you have no data for "not substantiated". Then it is evidence.

Portrait of Rens Timmermans from BeeSensible

Prefer someone to walk you through it?

Rens, BeeSensible

I'm happy to give you a twenty-minute tour. Leave your details and I'll find a time that suits you. You're also welcome to call or email.

Prefer to talk to someone first?

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