Copilot is installed. Nobody is using it.
The licence did not fail, the rollout did. Microsoft 365 Copilot arrives as a button in Word and Outlook, with no translation into the jobs your people actually do, so it gets clicked twice, produces something mediocre, and is quietly abandoned. Microsoft's own adoption guidance is clear that the deployment is a change programme rather than a licence assignment, and that is exactly the part most firms skip.
It is a conversation worth having before the renewal. A construction business bought licences, sometimes dozens, because it seemed like the responsible way to do AI. Twelve months on, the finance director wants to know what the business got. The honest answer is usually that a handful of people summarise the odd email, one enthusiast in the commercial team uses it properly, and everyone else forgot it exists.
This post is about activation, which assumes the licence is the right thing to own. Whether to buy it at all, what it costs across a workforce and where its documented limits sit in a contracting business, is answered separately in Copilot or a custom construction assistant.
Why does utilisation stay so low?
Four causes, and each has a different fix. Diagnosing which one you have matters, because the remedies are not interchangeable.
| Cause | What it looks like | The fix |
|---|---|---|
| Arrived as a feature, not a change | A button appeared. No explanation of what it is for | Name the specific tasks it helps with, in the language of the role |
| Never translated into construction | Training showed it drafting a marketing email | Retrain on payment notices, scope clarifications, monthly commentary |
| The data underneath is a mess | Answers are as confused as the SharePoint it reads | Fix structure, naming and permissions before blaming the tool |
| No agreed use cases | "Use AI more" as an instruction | Five named tasks per role, with explicit permission to use it for them |
The third row is the one people resist, because it is unglamorous and it is not what they bought. Copilot works over your SharePoint and Outlook. If SharePoint is a decade of unstructured folders, weak foundations quietly cap what the tool can do, and then the tool takes the blame for the filing. That is why the CDE and SharePoint groundwork tends to return more than the licence itself.
What does activation actually involve?
A short, practical adoption programme. It is not a technology project, which is why buying more technology does not fix it.
Pick the workflows first. For each role, identify a small number of weekly tasks where the tool demonstrably helps: minutes into actions, first-draft reports, inbox catch-up after leave, summarising a long document trail before a meeting.
Train by role, on real work. An hour with the bid team on their live tender beats a day of generic features. People adopt what solves their Tuesday, not what impressed them in a demo.
Fix the ground it stands on. Straighten the SharePoint structure, naming and permissions so the assistant has something coherent to read.
Set the rules. What can and cannot go into which tools, what must be reviewed and by whom, and what is out of bounds. Clear guardrails create confidence, and confident people use a tool more rather than less, which is the opposite of what most people expect.
Measure something. Utilisation, hours saved on the chosen workflows, adoption by team. Renewal conversations are straightforward when the number is visible and awkward when it is not.
Is this really about Copilot?
No. The same pattern applies to any AI capability a construction business buys, which is why it is worth understanding rather than working around.
The licence is the cheap part. The value lives in the translation from generic capability to your workflows, your documents and your people. That translation is exactly what most rollouts skip, because it does not appear on the invoice and nobody budgeted for it.
Budget for it and a modest licence outperforms an expensive platform. Skip it and the renewal conversation keeps being awkward, regardless of which vendor you picked. The same logic decides which model your team should be using in the first place, and it is usually not the one with the best demo.
If you already own the licences you are one focused activation away from being paid back for them. That is a considerably better starting position than buying anything new.