Control over AI
Blog
AI governance 6 min read

Four statuses for AI tools: from allowed to no decision yet

A yes/no list leaves most tools unnamed. What the four statuses mean, when to choose which and why every tool starts as "No decision yet".

Abstract route with nodes through soft shapes
Quick answer

An AI tool gets one of four statuses: allowed, limited use, not allowed or no decision yet. Every tool starts as "No decision yet" until the organisation records something else. Allowed means people can use it freely. Limited use means use under one condition the organisation sets itself, such as business account only. Not allowed means the organisation would rather people use something else, and names that alternative. Two statuses are not enough: everyone reads a tool that is not on the list differently. A risk score is information for the decision, not the decision itself.

01

Yes and no leave the largest group of tools unnamed, and that is where people guess

02

"No decision yet" is where every tool starts, and it says exactly what is true

03

"Limited use" comes with a one-sentence condition set by the organisation

04

A risk band is information; the decision stays with the organisation

05

A spreadsheet with eight columns is enough to start with, as long as it is fed by observed use

An IT admin at an accounting firm keeps a spreadsheet of which AI tools are allowed. Two columns: the tool, and yes or no. A colleague asks whether she can use Claude to rewrite a draft letter. Claude is not on the list. Does that mean no? Not looked at yet? Or yes, because it is not banned? The admin knows and the colleague does not. Two desks away, someone reads it differently again.

That is why two statuses do not work. Four do: allowed, limited use, not allowed and no decision yet. The last one is where every tool starts, and that is not a weakness of the list but the most honest thing in it.

Why do yes and no fall short?

A yes-or-no list only covers the tools someone has thought about. That is usually a dozen or so, while people open several dozen, and new ones appear faster than an organisation can assess them. The largest group of tools therefore sits in neither column, and that is the group people guess about.

The second problem is in the yes. Many decisions are not yes or no but yes with a condition: ChatGPT, but only on the business account. A transcription tool, but not for customer calls. In a two-column list that condition disappears into a comment nobody reads, or the tool ends up as a no because a qualified yes does not fit.

And a no with nothing behind it simply moves the use to a personal account on someone's own phone. Blocking makes the risk invisible; it does not make it smaller. So a no needs to come with an alternative, and that does not fit in two columns either.

What does each status mean, and when do you pick it?

StatusWhat it meansWhen you pick itWhat you record with it
AllowedFree to use within the general rules on dataThe tool has been assessed, the vendor's terms are acceptable and there is a business account or an equivalent agreementThe account type the decision applies to
Limited useUsable under one condition set by the organisationThe tool suits part of the work, or is acceptable only on terms people would not assume by defaultThe condition, in one sentence someone can follow
No decision yetThe organisation has not recorded anything about this toolAlways, as the starting point. Every tool begins here, including one nobody requestedDate first seen, and who does the assessment
Not allowedThe organisation would rather people use something elseThe assessment produces a reason that outweighs the convenience, and there is an alternativeThe alternative, and the reason in one sentence

The right-hand column is what matters. A status without its details is just a colour; with the condition, the alternative or the date attached, it is a decision someone can act on. For "Not allowed", the reason is often a fact you can point to. Take the consumer version of Grok: shared chats ended up in Google search results, and it comes without a data processing agreement.

Why is "No decision yet" an honest status?

Because it is true. Nothing has been decided about most tools, and a list that hides that pretends the organisation has assessed more than it has. "No decision yet" tells the colleague in the opening exactly what she wanted to know: nobody has looked at this yet, and this is what you do in the meantime.

It is also useful, because it doubles as a backlog. Every tool marked "No decision yet" that is actually in use is an assessment still to be done. This is the model known as default-deny: nothing is allowed merely because it happens not to be banned, and every decision is a deliberate act by the organisation. The questions for that assessment are in our article on what to ask the vendor when approving an AI tool.

"No decision yet" is not a ban. The status comes with an instruction someone can follow at once: public information only, and this is where you request the assessment. In the meantime the organisation remains the controller for everything that does go in, decision or not; a status does not change that.

What does "Limited use" have that the others do not?

A condition, and the organisation writes it itself. "Business account only." "No client personal data." "Code only, no customer data in the prompt." One sentence, because nobody reads a paragraph in the middle of a task.

This is the status that lets an organisation be generous without becoming careless. A ban on ChatGPT is strict and gets worked around. "Limited use" with the condition "business account" is exactly as strict as it needs to be, and most people follow a condition they understand.

Is a risk score the same as a decision?

No, and that distinction is the reason the statuses exist. A risk score summarises what is known about a vendor: where processing runs, whether input is used for training, which certifications exist, which incidents are known. That is information. The decision belongs to the organisation, because only the organisation knows what the tool is used for.

Two tools in the same band can therefore rightly get different statuses. A tool with a high score that is used only for public text can reasonably be set to "Limited use". A tool with a low score that is allowed to read the entire personnel file deserves a harder look than the score suggests.

BeeSensible works the same way: every tool in the catalogue of over 1,000 AI tools carries a risk score across six dimensions, shown as information next to the four statuses. Every tool starts as "No decision yet", no option is pre-selected and an administrator records the decision. This is what that overview looks like, with the observed use next to it:

AI register
AllowedUnder reviewNot allowedAll tools
Search by tool, vendor, domain or former name…
1,012 tools
DeepSeek
Critical · 90/100
Not allowed
Otter.aiNew
High · 68/100
No decision yet
Grok
High · 67/100
Not allowed
ChatGPT
High · 62/100
Allowed
Perplexity
Medium · 55/100
No decision yet
HeyGen
Medium · 53/100
No decision yet

Every tool, scored for risk

Over 1,000 AI tools, each scored from Low to Critical. Nothing is approved or blocked until someone decides.

More about AI Governance

How do you keep track of this without software?

With a spreadsheet. Eight columns: the tool, the domain, the status, the condition (limited use only), the alternative (not allowed only), the date of the decision, who took it and when it is reviewed. Every new row starts as "No decision yet".

The hard part is not the list but the intake. A municipality allows Copilot and records it neatly in its register. An inventory six months later finds Perplexity, ChatGPT and three specialist tools in use alongside Copilot, two of which appear nowhere in the register. That is not an incident; it shows that a list built from a survey is out of date as soon as it is finished. A list built from observation (which domains are opened in the organisation, in counts, without names) fills itself, and every new row automatically starts with the right status.

How the statuses fit into a wider policy is covered in our guide to writing an AI policy. The other articles on this subject are collected under AI governance.

So if you open the spreadsheet tomorrow, add two statuses and set everything that has not been assessed to "No decision yet". The list does not get any prettier, but it becomes accurate, and the colleague with the draft letter knows for the first time what she can do in the meantime.

FAQ

Common questions

Why are yes and no not enough for AI tools?

Because most tools fall into neither. Tools appear faster than an organisation can assess them, and a tool that is not on the list is read as banned by one person and as allowed by the next. A third status, "No decision yet", gives that situation a name, and a fourth, "Limited use", makes room for a yes with a condition.

What does "No decision yet" mean?

That the organisation has not recorded anything about this tool. It is the starting status of every tool, including tools nobody has requested. It is neither a ban nor an approval, and it comes with an instruction: public information only, and a place to request the assessment.

What is the difference between "Limited use" and "Allowed"?

The condition. "Allowed" has none; with "Limited use" the organisation writes one itself, in a sentence someone can follow while working: business account only, no customer data, code only. The condition belongs to the organisation, not to a vendor or a risk score.

Does a risk score determine a tool's status?

No. A risk score summarises what is known about a vendor: where processing runs, whether input is used for training, which incidents are known. That is information for the decision. Two tools with the same score can rightly end up with different statuses, because the use inside the organisation differs.

Can you keep track of this without software?

Yes, in a spreadsheet that records for each tool the domain, the status, the condition, the alternative, the date of the decision, who took it and when it is reviewed. The hard part is not the list but the intake: knowing which tools are opened in the organisation, so they can start as "No decision yet".

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.