Prevent unequal AI access by making allocation decisions explainable, testing whether people can do the approved work and giving blocked requests an owner. Buying the same paid licence for every employee is not always the right answer. But asking people to meet the same expectations while some cannot reach the necessary tool, information or support deserves a review.
This guide is for adoption and IT leads allocating approved AI access across a company. It focuses on who receives which capability, why a request is waiting or refused, and how employees can get that decision reconsidered. Accessibility, language and shift conditions still matter; the allocation process needs to recognize them rather than assume that an assigned account settles access.
Look beyond the number of assigned licences
A licence report tells you which accounts have an entitlement. It does not tell you whether the relevant employee can finish the intended task. Someone might have a licence but be blocked by organizational policy, lack permission to the source material or have no workable opportunity to practise.
There is reason to investigate how opportunity is distributed. In its 2025 Digital Etiquette survey, The Adaptavist Group surveyed 4,000 knowledge workers in the UK, US, Germany and Canada in June 2025. Higher earners reported being given new AI tools more regularly, alongside differences in guidance and training. The commercial provider's survey records workers' reports, rather than an audit of licence decisions or evidence that a particular employer caused an outcome.
Use that finding to ask a local question: who can get a supported attempt, and who cannot? Include employees whose requests were refused, people still waiting and colleagues who never knew how to ask. A survey of existing users alone will miss those groups.
Start with relevant work, not a presumed level of enthusiasm. Employees doing different tasks may reasonably need different tools. Employees doing comparable approved work should be able to understand a difference in access and have a route to raise a missing need.
Match the approved capability to the task
Write down what the employee needs the tool to do. “Access to AI” is too broad to make a useful allocation decision. Drafting from a permitted sample document, searching authorized company sources and operating a specialist coding environment can require different arrangements.
Microsoft's current Copilot Chat documentation illustrates this distinction. Eligible Microsoft 365 users can have a baseline chat experience without the additional Copilot licence, while available capabilities and organizational grounding depend on the licence and supported experience. Its administration guidance also explains that organizational controls can block access, including for licensed users. A personal sign-in and a work sign-in have separate permissions and protections.
That is a product-specific example, not a reason to choose a particular vendor. Have IT confirm the employee's actual account, configuration and required capability. Do not promise that two products with similar names offer the same approved workflow.
For each proposed use, establish:
- The work. Name the recurring task and the person who receives its output.
- The capability. Explain which feature is needed, rather than requesting the most expensive plan by default.
- The inputs and checking. Identify permitted information, the current source and who can judge the result.
- The opportunity. Arrange a usable device, time and support for an appropriate attempt.
A legitimate information restriction may remain even when the employee receives a licence. Resolve the task with the information owner. Buying more seats cannot grant permission to use material that has not been approved for that purpose.
Make the allocation rule visible
Explain how employees request access, who decides and what they should expect while waiting. Give managers the same criteria so that access does not depend mainly on knowing an influential sponsor or working near the pilot team.
Software asset manager Pavel Stukov proposes tracing seat requests and checking assignments against vendor records in a public practitioner post. That is a useful administrative starting point, rather than proof of a particular return. Add the employee's requested work and the reason for the decision to your record; the assigned seat alone cannot explain a refused request.
You can begin with the organization's existing service-request process. Keep its decision record concise:
- Requested work and capability. Name the approved task and the feature needed to complete it.
- Decision and reason. Explain what is available, refused or waiting, and why.
- Responsible owner. Identify who can resolve the missing information, permission or capacity.
- Review point. Tell the employee when or under what condition the unresolved request will be reconsidered.
The employee should receive an answer they can act on, including what information is missing or which dependency must be resolved.
If funds or support capacity limit the first trial, say so. Distinguish a request that is eligible but waiting for capacity from a task that is not currently permitted. The former needs a priority and review decision; the latter needs a clear explanation and an established way to finish the work.
Do not require employees to invent a savings figure to get their first supported attempt. They can describe the task, frequency, difficulty and intended check. Where value is uncertain, a bounded trial can help the work owner decide whether continuing access is justified.
Compare attempts under comparable conditions
Suppose a travel company wants booking advisers to draft an internal handover when a supplier changes an itinerary. The handover tells the evening adviser what changed and which arrangements still need confirmation. The trial uses approved sample itineraries and supplier change notices.
Jamie Lee at headquarters can open the approved assistant. Claire Bennett at a regional office cannot, because her account is outside the pilot group. Both prepare the same kind of handover. Sending Claire a recording of Jamie's demonstration would not resolve the allocation question.
IT checks Claire's eligibility and the group configuration. The work owner confirms that the same sample inputs and checking arrangements are suitable at her office. If access is appropriate, the responsible administrator can arrange it. If a real restriction remains, the owner needs to explain it and agree how Claire will finish the work.
Separate the observations before choosing a remedy:
| What the attempt shows | Decision needed | Responsible person |
|---|---|---|
Account excluded despite an approved task | Check eligibility and assignment | IT access owner |
Tool opens but the required source is unavailable | Review information permissions or the task design | Information and work owners |
Access works but practice cannot fit the workload | Agree time and coverage | Manager |
Complete attempt is possible, but the result needs correction | Provide task-specific practice and checking support | Work owner and coach |
After a change, ask Claire to repeat the complete attempt. She checks the draft against the supplier notice, making sure a cancelled transfer stays cancelled and an unconfirmed replacement is not presented as booked. The receiving evening adviser must be able to find the relevant source and open questions.
An account enabled successfully is one observation. A usable, checked handover is another. Record both without assuming that access guarantees good work.
The deskless and shift-work guide explains how to inspect device and support conditions across working hours. For an employee's assistive setup, use the complete-workflow accessibility checks. These checks help an allocation decision reflect the conditions in which the person will use it.
Explain and review changes in access
Access can change when a pilot ends, a budget is reduced, a person moves roles or an approved use changes. Tell affected employees what changed, what work remains expected and how to raise a problem. Keep the established work method available while a request is unresolved.
In a June 2026 Reddit account, an employee described losing access after a budget change, then seeing licences provided to other technical workers. They were in their notice period but still coding and handing over knowledge. What bothered them was not being told why they had not received a licence. The employer's actual reason and policy were not verified; the poster's explanation does not establish retaliation.
The useful question is whether the remaining work and access decision have been reconciled. If a person still has an approved task to complete, the work owner and access owner need to agree a workable arrangement under the applicable controls. Do not leave the employee to guess, buy a personal subscription or borrow another person's account.
Resolve an access problem with the employee
Record the blocked work
Describe the approved task, the point where access stops and the established method available while waiting.
Assign the decision
Send the issue to the person who can resolve the licence, information, policy or capacity constraint. Explain the next review point.
Check the changed arrangement
Repeat an appropriate complete attempt with the employee, including the output check and handoff.
Close the request with a usable answer
Confirm what is available, any remaining restriction and who will review an unresolved need.
Revisit allocation after relevant changes, including role moves and return from leave. Keep private accommodation discussions in the organization's confidential process. An ordinary access record should contain the work decision needed to act, rather than personal medical details.
Judge opportunity before interpreting usage
A low-use account may be unnecessary, or it may belong to someone who cannot yet complete the approved task. Check the reason before reclaiming it. Likewise, a high prompt count does not establish that a scarce premium capability is producing useful work.
A March 2025 Reddit discussion about Copilot licensing makes the tradeoff concrete. The person preparing the allocation structure had been asked to approve only employees who would use more than one application. In a reply, another user proposed supported trials and later discussion, pointing out that valuable use in one application might matter more than occasional use in several. This was practitioner advice in an anonymous discussion, not an evaluated allocation policy. Its older product claims are not a source for current feature availability.
Nor does research establish that identical access is always the best team arrangement. In Jiaxuan Han and Ruqin Ren's 2025 laboratory study, 120 university students in China worked in 60 pairs on short Chinese-language press-release tasks. In the treatment task, pairs with one AI user produced higher-rated work than pairs with both members using AI.
The authors identify limits involving the student sample, short collaboration and different control and treatment prompts. The result does not justify denying workplace access by seniority or show what happens to employees' longer-term learning.
You can differentiate access deliberately while still making the decision accountable. Identify the needed capability, examine the complete work and review people who were left out. For the travel company, that means reviewing Claire's request with the task owner and IT, then checking what she can actually do after the decision.
Begin with one refused or waiting request this week. Compare the stated reason with the approved task and ask who can resolve the remaining need. The people-and-change guide helps distinguish an opportunity problem from a skill or motivation question.
Questions about access to approved AI tools
Does every employee need a paid AI licence?
Every employee does not necessarily need the same paid AI licence. Decide which capability their approved work requires, what the company already provides and whether an alternative can support the complete task. Some product features depend on licensing or configuration even when a baseline chat experience is available.
Have IT verify the actual account and feature requirements, then arrange a supported attempt. Use the task and capability questions to explain the allocation. A different licence can be reasonable; an unexplained inability to do expected work still needs attention.
What should we do when the AI licence budget is exhausted?
When the AI licence budget is exhausted, make the capacity constraint visible and explain how waiting requests will be reviewed. Record the task, the capability needed and who decides the next allocation. Keep a permitted established method available while the employee waits, and review whether genuinely unused capacity can be reassigned.
Do not require invented savings forecasts or assume that employees can pay personally. Ask the work owner to compare the unresolved needs under the same allocation criteria. If the task is essential but cannot be supported, the priority or work expectation needs a decision too.
Should employees buy their own AI subscriptions while waiting?
Do not make a personal AI subscription the assumed workaround for missing workplace access. A personal account may have different permissions, information rules and organizational controls from the approved work account. The employee's ability to pay also does not determine whether that route is appropriate.
Ask the access and work owners for a permitted way to finish the task. That may be the existing non-AI method, a different approved capability or a revised trial. Follow the access-resolution process rather than transferring the unresolved decision to the employee.
Can we start an AI pilot with senior staff or enthusiastic volunteers?
An AI pilot can begin with a limited group when its purpose, support and restrictions are clear. Explain why that group was chosen and which relevant working conditions it can and cannot represent. Enthusiastic volunteers may help explore a use, but their successful attempts do not establish that excluded colleagues have comparable access.
Before expanding or judging adoption, inspect a request from someone outside the first group. Include the task, device, information and support they need. The travel-adviser comparison shows how a regional colleague's blocked account changes the conclusion.
Should we remove an AI licence when usage is low?
Low usage is a reason to investigate an AI licence, not a sufficient explanation by itself. Ask whether the employee knew the permitted use, could reach the tool and source, and had an opportunity to complete relevant work. Then examine the output and the capability that would be lost if the licence changed.
If the seat is unnecessary, explain the change and how a later need can be reconsidered. If a barrier prevented use, assign it to the person who can fix it. Review opportunity before interpreting usage, and use the learning-time guide when workload is the unresolved constraint.
