Templates › Copilot adoption plan
Copilot adoption plan
Template id: adoption-plan
Responsible skills: copilot-adoption:adoption-readiness (section 2), copilot-adoption:launch-plan (sections 3 to 6) and copilot-adoption:adoption-measurement (section 7). Adoption results are reported on the coe-kpi-scorecard.
Use this plan for one organisation, business unit or wave. Every fact the organisation must supply is marked [To confirm: ...]; replace the marker when the fact is confirmed, and never fill it with a guess. Example rows are fictional and are there to be replaced or deleted. Adoption data in this plan is reported at team or role level only, never for named individuals.
1. Summary
| Field | Entry |
|---|---|
| Audience in scope | [To confirm: organisation, business unit or wave] |
| Executive sponsor | [To confirm: name and role] |
| Adoption lead | [To confirm: name and role] |
| Outcome the sponsor wants | [To confirm: one sentence, with a measure] |
| IT owner for technical enablement | [To confirm: name and role] |
| Linked Champions programme | [To confirm: charter reference, or "none yet"] |
| Linked Centre of Excellence or intake route | [To confirm] |
| Plan status | Draft / Agreed by sponsor / Superseded |
| Date agreed | [To confirm: date] |
2. Readiness assessment
Rate each area Ready, Partly ready or Not ready, with evidence. Any critical area at Not ready means this audience does not launch yet. Licence questions are referred to the Microsoft licensing guide or a licensing partner; this plan records only assignment and use.
| Area | Critical? | Rating | Evidence | Gap | Owner | Due |
|---|---|---|---|---|---|---|
| Sponsorship | Yes | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Licences assigned vs used (team or role level) | No | [To confirm] | [To confirm: assigned, active in last month] | [To confirm] | [To confirm] | [To confirm] |
| Technical enablement (confirmed by IT) | Yes | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Data and permissions hygiene (oversharing risk) | Yes | [To confirm] | [To confirm: permissions review reference] | [To confirm] | [To confirm] | [To confirm] |
| Approved-use guidance | Yes | [To confirm] | [To confirm: link to guidance] | [To confirm] | [To confirm] | [To confirm] |
| Support route, including data exposure reports | Yes | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Communications | Broad launch only | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
Overall recommendation to the sponsor: Launch / Launch to a narrower audience / Delay. Reason: [To confirm]
3. Launch waves
| Wave | Audience (teams or roles) | Personas | Start date | Exit criteria | Owner |
|---|---|---|---|---|---|
| Fictional example: 1 | Finance operations and HR advisers | Desk | Fictional example: week 1 | Support demand manageable; no open data exposure incidents; feedback reviewed | Adoption lead |
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
4. Executive and manager enablement
| Audience | Format | Content | Timing | Owner |
|---|---|---|---|---|
| Executives | [To confirm: for example a short private session] | Scenarios for their own work; the ask to use Copilot visibly | Before wave 1 | [To confirm] |
| Managers of each wave | [To confirm] | Purpose, starting scenarios, approved use, support, protecting practice time | Before their team's wave | [To confirm] |
5. Onboarding and reinforcement
| Persona | Starting scenarios (from the scenario-catalogue) | Onboarding format | Office hours | Scenario refresh | Six-week check-in |
|---|---|---|---|---|---|
| [To confirm] | [To confirm] | [To confirm] | [To confirm: rhythm and who runs them] | [To confirm] | [To confirm: date] |
Recurring learning calendar. Sessions are open to the whole workforce and recorded; where a Champions programme exists, mark which sessions count towards its journey (see the champion-capability-framework).
| Session | Rhythm | Personas | Counts towards the Champion journey? | Owner |
|---|---|---|---|---|
| Getting started and approved use | [To confirm] | All | [To confirm: for example joining the community] | [To confirm] |
| Copilot Chat | [To confirm] | All | [To confirm] | [To confirm] |
| Copilot in the Microsoft 365 apps, including Teams | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Agent awareness | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
6. Support model and feedback loop
| Type of need | Where it goes | Owner |
|---|---|---|
| "How do I" questions | Champions (first-line peer guidance), office hours, scenario catalogue | [To confirm] |
| Formal training | Learning calendar above, not Champions | [To confirm] |
| Faults | IT service desk | [To confirm] |
| Suspected data exposure | [To confirm: agreed security route] | [To confirm] |
| Ideas needing more than individual use | Opportunity intake | [To confirm] |
| Larger or higher-risk solutions | Centre of Excellence | [To confirm] |
Feedback channel: [To confirm]. Review rhythm: [To confirm]. How changes are published to users: [To confirm]
7. Measurement plan
Decisions the measures will inform: [To confirm: for example whether to expand to the next business unit]
Agreed minimum reporting group size: [To confirm: agreed with the data protection lead and HR]. Groups below it are suppressed or combined.
| Layer | Measure | Baseline (taken before launch) | Source | Owner | Reporting rhythm |
|---|---|---|---|---|---|
| Usage | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Capability | [To confirm: may include Champion community size and milestone conversion at programme level] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Behaviour change | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Outcomes | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
People rules for adoption data, agreed in writing: [To confirm: purposes, access, retention, no individual performance use]
8. Approval
| Role | Name | Decision | Date |
|---|---|---|---|
| Executive sponsor | [To confirm] | [To confirm] | [To confirm] |
| Data protection lead (measurement plan) | [To confirm] | [To confirm] | [To confirm] |
Credit: Template from CopilotForge by Simon Foote (https://github.com/SimonFoote-greensparx/CopilotForge), licensed under CC BY 4.0. Keep this credit when you share or adapt the template; in your own completed document you may keep it as a footer or remove it.