A Copilot Rollout Plan for a Small Team
Share
Most Copilot rollouts stop at licence assignment. Everyone gets the tool, nobody changes how they work, and six months later someone asks what the money bought.
Direct answer
Four weeks, small group first. Fix permissions in week zero, pick eight volunteers across different roles in week one, give each one a single weekly task in week two, collect the prompts that worked in week three, and decide in week four.
Based on the AI and Automation Practitioner standard (ST1512), a Level 4 apprenticeship for people already in work. Funding rules described here are the England position and are set by the funding body.
Potentially free for you
The learner never pays. Employers potentially pay nothing either, and where the apprentice is aged 16 to 24 the government funds the whole cost even if the employer does not pay the levy.
Closing any gap. A levy transfer from another employer covers 100% of the cost. Unused transfer allowance is not carried forward at the end of the tax year, and it must be agreed before the apprentice starts.
From 1 August 2026 the government stopped adding the 10% top-up to new funds entering levy accounts, so there is less in the system than there was.
Part of our guide to Microsoft 365 Copilot Training for UK Teams.
Week zero: permissions
Run a sharing report across SharePoint and OneDrive. You are looking for anything shared with everyone that should not be.
The classic finds are old salary spreadsheets, a HR folder shared to a whole department, and site permissions inherited from a project that ended.
Copilot does not create this problem, it makes it visible in seconds. Fixing it first is the only step here that carries real risk if skipped.
Assign this to someone with the time to finish it. A half-done permissions review is worse than a known-bad one.
Week one: pick the right eight people
Choose volunteers across different roles. You want to learn where it fails for ordinary users, not where it succeeds for enthusiasts.
Avoid loading the pilot with the most technical staff. They will make anything work and teach you nothing about the rest of the organisation.
Include at least one sceptic. Their objections are the ones you will hear from everyone else in month three.
Ask each person to name one weekly task before they get the licence. This forces a specific commitment rather than general exploration.
Week two: one task each
Everyone uses Copilot for their single named task and nothing else. General exploration produces stories, not evidence.
Ask them to time it, roughly. Minutes before and minutes after, across whatever instances occur that week.
Give them a short reference sheet with the prerequisites. Files in OneDrive, AutoSave on, tables formatted properly.
Check in mid-week. The people who have not started by Wednesday will not start, and that is useful information.
There is more on this in our guide to Microsoft 365 Copilot training for UK teams.
Week three: capture what worked
Collect the prompts that produced usable output, in a shared document with a line on what each is for.
This library is the actual deliverable of the pilot. The licences are replaceable and the prompts in your house style are not.
Also record what failed and why. Half of it will be prerequisites rather than capability, which is a training fix not a tooling one.
Ask each pilot user whether they would keep it if it came out of their own budget. The answers are more honest than a satisfaction score.
The UK compliance steps to fold in
Update your privacy notice if the rollout changes how staff data is processed. This is easy to overlook and simple to do.
Check your data protection impact assessment position. Widespread rollout of a new processing capability may trigger the need for one.
Tell staff what is changing about monitoring, if anything. Trust is harder to rebuild than to keep, and rumours fill silence quickly.
Consult recognised unions or staff representatives where you have them. Doing it early is far cheaper than doing it after an objection.
Week four: decide honestly
If fewer than half the pilot group kept using it past week two, widening the rollout will not fix that. Find out why first.
If the saving concentrated in one role, licence that role and stop. Organisation-wide rollout is a decision, not a default.
If the blocker was prerequisites and habits rather than the tool, the answer is training rather than more licences.
Write down what you decided and why. In six months somebody will ask, and an honest record is worth more than an optimistic one.
Key takeaways
- Fix permissions before anyone gets a licence.
- Pick eight volunteers across roles, including one sceptic.
- One named weekly task each, not general exploration.
- The prompt library is the real deliverable of the pilot.
- Under half still using it by week two means training, not more licences.
Frequently asked questions
How long does a Copilot rollout take?
Four weeks for a team under fifty, using a pilot group. The delay is habit change rather than technical setup.
What should I do before rolling out Copilot?
Run a sharing report and close anything overshared. Copilot surfaces everything a user can already access, in seconds.
How many people should be in the pilot?
Around eight, spread across different roles. Enough to see patterns, small enough to support properly.
Should the pilot be technical staff?
No. They will make anything work and teach you nothing about ordinary adoption. Include at least one sceptic instead.
How do I measure whether Copilot works?
Have each pilot user name one weekly task and roughly time it before and after. General satisfaction scores tell you very little.
What if people stop using it?
If under half are still using it by week two, widening the rollout will not fix that. The cause is usually prerequisites or habits rather than the tool.
What is the most useful output of a pilot?
A shared library of prompts that produced usable output in your organisation's voice. That outlasts any licensing decision.
Should everyone get a licence?
Not by default. If the saving concentrates in one role, licence that role. Organisation-wide rollout should be a decision you can justify.
The funded route, in figures
Figures are the England position. Levy-paying employers usually draw the whole cost from the levy they already contribute, so they pay nothing extra. Employers below the £3 million pay bill threshold pay nothing for an apprentice aged 16 to 24. For an older apprentice the government funds 95 per cent, and a levy transfer from a larger employer can cover the rest. Eligibility and funding rules are set by the funding body and can change.
Where to go next
If the blocker turns out to be capability rather than licensing, a funded apprenticeship builds it into one person's job at no cost to the learner.
We help UK employers and employees access government-funded AI training. Training is delivered by third-party providers. We do not guarantee a place, a qualification, a job or any particular outcome. Eligibility and funding rules are set by the funding body and can change. Always check the current position before you commit. See our disclaimer.