Templates › AI learning plan
AI learning plan
Template id: ai-learning-plan
Responsible skill: learning-and-skills:ai-role-curriculum. Sections are completed with learning-and-skills:ai-skills-needs-analysis (section 2), learning-and-skills:ai-learning-pathway (section 3), learning-and-skills:practice-labs (section 5), learning-and-skills:learning-evidence-rubric (section 6), learning-and-skills:facilitator-guide (section 7), learning-and-skills:office-hours (section 8), learning-and-skills:advanced-pathways (section 9) and learning-and-skills:skills-measurement (section 10).
Use this plan for one organisation, business unit or rollout 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. Learning is verified by demonstrated practice, not attendance. All skills and learning data in this plan is reported at role or team level above the agreed minimum group size, and is never used to assess, score or rank individuals.
1. Plan details
| Field | Entry |
|---|---|
| Scope | [To confirm: organisation, business unit or wave] |
| Learning Lead | [To confirm: name and role] |
| Sponsor | [To confirm: name and role] |
| Linked adoption plan | [To confirm: reference to the adoption-plan for this scope] |
| Linked Champions programme | [To confirm: charter reference, or "none yet"] |
| Approved tools and agents by group | [To confirm: reference to the approved list; never assumed] |
| Minimum group size for reporting | [To confirm: agreed with the data protection lead] |
| Learning records retention | [To confirm: agreed with the data protection lead] |
| Plan status | Draft / Agreed by sponsor / Superseded |
| Version, date and next review | [To confirm] |
2. Needs by role
One row per role and skill area with a gap. Skill areas: safe and approved use, verification, everyday productivity, working with agents, delegating work, building.
| Role | Future work with AI | Skill area | Gap rating (None / Light / Substantial / Critical) | Evidence and confidence | Response type | Priority this wave |
|---|---|---|---|---|---|---|
| Fictional example - account manager | Prepares client meetings with Copilot summarising recent mail and documents | Verification | Substantial | Survey and Champion observations; medium confidence | Curriculum module with practice | High |
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
Deliberately deferred this wave, and why: [To confirm]
3. Pathway levels
| Level | Who it is for | Behaviour at this level | Exit evidence | Open now? | Level owner | Review point |
|---|---|---|---|---|---|---|
| Foundation | Everyone with approved AI access | [To confirm] | Safe use and a verified output on a real, non-sensitive task | [To confirm] | [To confirm] | [To confirm] |
| Applied | Roles with defined scenarios | [To confirm] | Rubric evidence on two role scenarios | [To confirm] | [To confirm] | [To confirm] |
| Proficient | Frequent users, team leads, people who help others | [To confirm] | A reusable pattern or delegated task a colleague has used | [To confirm] | [To confirm] | [To confirm] |
| Advanced | Makers, power users, specialists | See section 9 | Set by each track | [To confirm] | [To confirm] | [To confirm] |
| Movement rule | Entry |
|---|---|
| Skipping a level by evidence | [To confirm: allowed for all levels, or exceptions] |
| Equivalence with Champion capabilities | [To confirm: agreed with the Champions programme owner, or "not yet agreed"] |
| Any level that is a condition of access | [To confirm: sponsor decision with HR involvement, or "none"] |
| Refresher triggers | [To confirm: for example a change in what people see, a new approved agent, a change to approved-use guidance] |
4. Role curricula
Complete one block per priority role.
| Field | Entry |
|---|---|
| Role and approximate headcount | [To confirm] |
| Business owner who confirms the curriculum | [To confirm: name and role] |
| Agreed learning time per month | [To confirm: agreed with the business owner] |
| Working pattern and default formats | [To confirm] |
| Pathway levels covered | [To confirm] |
| Content owner and delivery owner | [To confirm] |
| Review date | [To confirm] |
| Module | Learning outcome (observable work) | Scenario | Format | Practice task | Evidence expected | Time | Access confirmed? |
|---|---|---|---|---|---|---|---|
| Fictional example - Checking client summaries | Prepares a meeting brief with Copilot and checks every date and figure against the source | Meeting preparation | Live session, practice on own work the same week | Brief for a real upcoming meeting, checked against the source documents | Prompt, output and check described, at Meets on the rubric | [To confirm] | [To confirm] |
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
Deferred modules and reasons (for example pending access or scenario not ready): [To confirm]
5. Practice environment
| Lab | Type (own-work / shared scenario pack / maker sandbox / specialist lab) | Purpose | Location and who can reach it | Data allowed | Owner | Reset routine | Expiry | Security review date |
|---|---|---|---|---|---|---|---|---|
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | Fictional or synthetic only, unless own-work practice | [To confirm] | [To confirm] | [To confirm] | [To confirm, or "not required" for own-work practice] |
Lab rules for learners (what may and may not enter, sharing limits, how to report a problem): [To confirm]
6. Evidence rubric
A level is evidenced when its required dimensions are at least Meets. Strong is used for feedback only and never creates a status.
| Dimension | Not yet | Meets | Strong |
|---|---|---|---|
| Real work | Demo or invented task | A task from the person's own role or an assigned lab exercise | A recurring task valued by the team |
| Safe use | Sensitive data shared, or an unapproved tool used | Approved tools only; nothing that should not have been shared | Explains what was deliberately left out and why |
| Verification | Output used without checking | Output checked against its source; the check is described | The check is built into a reusable pattern |
| Judgement | No sense of limits | Notes where AI did not help or got it wrong | Explains when they would not use AI for this task |
| Transfer | Only the author could repeat it | Someone else could follow it | A colleague has used it |
| Checking arrangement | Entry |
|---|---|
| Who checks evidence at each level | [To confirm] |
| Calibration rhythm and exemplars used | [To confirm] |
| Submission route and access | [To confirm: access-restricted route in governed storage] |
| What is recorded, and for how long | [To confirm: agreed with the data protection lead] |
Fictional example: a learner shows the prompt used to summarise a supplier contract, the summary, and a note that they compared every date and value with the contract and corrected one date. Verification is at Meets.
7. Sessions and facilitation
| Session | Module | Facilitator guide reference | Facilitators | Rhythm | Pre-flight check owner | Last tested against current product |
|---|---|---|---|---|---|---|
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
8. Office hours
| Format (open drop-in / themed / bookable / maker / embedded) | Audience | Rhythm and time | Hosts and agreed time | Booking route |
|---|---|---|---|---|
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Triage route | Where it goes |
|---|---|
| Faults, access, licence not applied | [To confirm: service desk route] |
| Suspected data exposure or inappropriate output | [To confirm: security reporting route] |
| Ideas for agents, automation or scenarios | [To confirm: intake route] |
| Licensing or data protection questions | [To confirm: licensing owner or DPO] |
Theme review owner and rhythm (themes recorded without names): [To confirm]
9. Advanced pathways
| Track | Audience by declared role | Entry conditions | Learning environment | Mentors and agreed time | Evidence to complete | Track owner | Open now? |
|---|---|---|---|---|---|---|---|
| [To confirm: for example power user, agent maker, automation maker, developer, AI specialist] | [To confirm] | Proficient evidence, approved access, maker commitments accepted | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
Route from a learning build into intake and release: [To confirm: agreed with platform governance]
10. Measures
All measures are reported at role or team level above the minimum group size in section 1.
| Measure | Definition | Source | Baseline | Target | Owner | Rhythm |
|---|---|---|---|---|---|---|
| Declared skills change | Change by skill area and role against the needs baseline, same survey wording | Repeat survey | [To confirm] | [To confirm] | Learning Lead | Each wave |
| Verified evidence rate | Share of each role with evidence at each level | Aggregate evidence records | [To confirm] | [To confirm] | Learning Lead | [To confirm] |
| Progression | Movement between levels; time from access to foundation evidence | Aggregate evidence records | [To confirm] | [To confirm] | Learning Lead | [To confirm] |
| Link to adoption | Adoption measures for groups with high and low evidence rates, read as association only | Adoption measures from the adoption lead | [To confirm] | Not targeted | Learning Lead with adoption lead | Each wave |
11. Review and agreement
| Role | Name | Date | Comment |
|---|---|---|---|
| Learning Lead | [To confirm] | [To confirm] | |
| Sponsor | [To confirm] | [To confirm] | |
| Data protection lead (records, retention, minimum group size) | [To confirm] | [To confirm] | |
| Business owners of priority roles | [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.