Plan the L&D Year
When To Use
One person must build two programmes at once and every sponsor thinks theirs is first. Run this once a year, and again when a wave of new requests breaks the plan you had. It answers one question: with the design days and the budget you really have, which programmes run this year, in which quarter, and which ones wait in the open?
When Not To Use
If nobody has yet shown what teams lack, run Assess the Training Needs first; a plan made of requests alone is a wish list with dates on it. To plan the work on one approved programme, use Plan the Build.
Inputs
- The needs table from the needs assessment, or the open requests with the role of each sponsor.
- The business goals for the year, in the leadership team's own words.
- Your design days, delivery days and budget, what is already committed, and the items your programme reviews sent forward.
If you have none of this, I start from the list of requests and the top business goals and mark the output as a first draft.
Approach
This follows learning needs analysis as the CIPD factsheet frames it: needs flow from business strategy down to team and role, and the plan follows that flow instead of the loudest request. The judgement is to stop adding when the days run out and to say so in writing, where sponsors can see it. The failure it prevents: every request gets a polite "we will try", the calendar fills with half-built courses, and in the autumn the one programme leadership cared about is the one that slipped.
Workflow
- Ask at most three questions: which business goals will leadership be judged on this year, how many design and delivery days are left once admin, recurring sessions and fixed commitments are taken out, and who approves the final list?
- List every candidate programme with its need, its evidence and its sponsor's role. Add the items your programme reviews sent forward. A need nobody has shown keeps the label "requested, not shown"; it can still be ranked, but the label travels with it.
- Set the ranking criteria and their weights with the team, for example link to a named business goal, urgency, reach by role. You set them and you give the scores; I lay out the grid, do the sums and show the working, as a spreadsheet file if file creation is on.
- Cost each programme in design days, delivery days and budget, as [placeholders] you fill from your own past projects. Fixed commitments come off the top before anything new is counted.
- Fill capacity in rank order and draw the line where the days or the budget run out. Do not stretch the line to fit a favourite; move the favourite up by changing a criterion in the open, or leave it below.
- Write the not-this-year list for sponsors to read: one reason each sponsor can accept, and a cheaper move where one exists (a job aid, a manager conversation, a bought course).
- Place the programmes above the line in a quarterly calendar that spreads the design peaks, so two builds do not land on one person in the same weeks.
Output Format
# L&D Year Plan
Year: [year] | Owner: [L&D lead] | Capacity: [design days] design, [delivery days] delivery, [budget] | Already committed: [days, budget]
Criteria and weights the team set: [criterion, weight; criterion, weight]
## Programmes in rank order
| Rank | Programme | Business goal | Evidence | Score, by criterion | Design days | Delivery days | Budget |
|---|---|---|---|---|---|---|---|
| [n] | [programme] | [goal, or "not linked"] | [source, or "requested, not shown"] | [scores] | [days] | [days] | [cost] |
The capacity line falls after rank [n] because [days or budget run out].
## Quarterly calendar
| Quarter | In design | In delivery | Fixed commitments |
|---|---|---|---|
| [quarter] | [programme] | [programme] | [commitment] |
## Not this year
| Request | Sponsor (role) | Reason | Cheaper move meanwhile |
|---|---|---|---|
| [request] | [role] | [why it sits below the line] | [job aid, manager conversation, bought course, or none] |
## Decision
[Leadership sponsor] approves the ranked list and the capacity line by [date]; [L&D lead] tells each not-this-year sponsor by [date].
Done When
- Every programme links to a named business goal or is marked "not linked".
- The capacity line comes from your own days and budget, with fixed commitments taken off first.
- Every item below the line has a reason and, where one exists, a cheaper move, and review carry-overs are in the candidate list.
Quality Bar
- Criteria, weights, scores and every other number are yours to fill; nothing is estimated to help a programme win.
- The not-this-year list goes to sponsors; it is never a quiet backlog.
- No list of named employees to train is drawn from appraisal ratings; the plan stays at role and task level.
- Programmes are ranked, never people; the capacity line comes from your own days, and leadership approves the list and the line.
Next
Run ldg-make-the-business-case (Make the Business Case) for the programme that needs budget beyond the line.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: ldg-plan-the-year3description: Plans the L&D year on one page, producing programmes ranked against business goals on criteria the team sets, a capacity and budget line drawn from your own days, a quarterly calendar and a visible not-this-year list with a cheaper move per item. Use for "run ldg-plan-the-year", "training plan", "annual training plan", "l&d strategy", "training calendar", "learning and development plan", "prioritise training requests", "what we will not build this year", part of The Complete Claude Guide for L&D Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/ldg-plan-the-year6---78# Plan the L&D Year910## When To Use11One person must build two programmes at once and every sponsor thinks theirs is first. Run this once a year, and again when a wave of new requests breaks the plan you had. It answers one question: with the design days and the budget you really have, which programmes run this year, in which quarter, and which ones wait in the open?1213## When Not To Use14If nobody has yet shown what teams lack, run Assess the Training Needs first; a plan made of requests alone is a wish list with dates on it. To plan the work on one approved programme, use Plan the Build.1516## Inputs17- The needs table from the needs assessment, or the open requests with the role of each sponsor.18- The business goals for the year, in the leadership team's own words.19- Your design days, delivery days and budget, what is already committed, and the items your programme reviews sent forward.20If you have none of this, I start from the list of requests and the top business goals and mark the output as a first draft.2122## Approach23This follows learning needs analysis as the CIPD factsheet frames it: needs flow from business strategy down to team and role, and the plan follows that flow instead of the loudest request. The judgement is to stop adding when the days run out and to say so in writing, where sponsors can see it. The failure it prevents: every request gets a polite "we will try", the calendar fills with half-built courses, and in the autumn the one programme leadership cared about is the one that slipped.2425## Workflow261. Ask at most three questions: which business goals will leadership be judged on this year, how many design and delivery days are left once admin, recurring sessions and fixed commitments are taken out, and who approves the final list?272. List every candidate programme with its need, its evidence and its sponsor's role. Add the items your programme reviews sent forward. A need nobody has shown keeps the label "requested, not shown"; it can still be ranked, but the label travels with it.283. Set the ranking criteria and their weights with the team, for example link to a named business goal, urgency, reach by role. You set them and you give the scores; I lay out the grid, do the sums and show the working, as a spreadsheet file if file creation is on.294. Cost each programme in design days, delivery days and budget, as [placeholders] you fill from your own past projects. Fixed commitments come off the top before anything new is counted.305. Fill capacity in rank order and draw the line where the days or the budget run out. Do not stretch the line to fit a favourite; move the favourite up by changing a criterion in the open, or leave it below.316. Write the not-this-year list for sponsors to read: one reason each sponsor can accept, and a cheaper move where one exists (a job aid, a manager conversation, a bought course).327. Place the programmes above the line in a quarterly calendar that spreads the design peaks, so two builds do not land on one person in the same weeks.3334## Output Format35```markdown36# L&D Year Plan37Year: [year] | Owner: [L&D lead] | Capacity: [design days] design, [delivery days] delivery, [budget] | Already committed: [days, budget]38Criteria and weights the team set: [criterion, weight; criterion, weight]39## Programmes in rank order40| Rank | Programme | Business goal | Evidence | Score, by criterion | Design days | Delivery days | Budget |41|---|---|---|---|---|---|---|---|42| [n] | [programme] | [goal, or "not linked"] | [source, or "requested, not shown"] | [scores] | [days] | [days] | [cost] |4344The capacity line falls after rank [n] because [days or budget run out].45## Quarterly calendar46| Quarter | In design | In delivery | Fixed commitments |47|---|---|---|---|48| [quarter] | [programme] | [programme] | [commitment] |49## Not this year50| Request | Sponsor (role) | Reason | Cheaper move meanwhile |51|---|---|---|---|52| [request] | [role] | [why it sits below the line] | [job aid, manager conversation, bought course, or none] |53## Decision54[Leadership sponsor] approves the ranked list and the capacity line by [date]; [L&D lead] tells each not-this-year sponsor by [date].55```5657## Done When58- Every programme links to a named business goal or is marked "not linked".59- The capacity line comes from your own days and budget, with fixed commitments taken off first.60- Every item below the line has a reason and, where one exists, a cheaper move, and review carry-overs are in the candidate list.6162## Quality Bar63- Criteria, weights, scores and every other number are yours to fill; nothing is estimated to help a programme win.64- The not-this-year list goes to sponsors; it is never a quiet backlog.65- No list of named employees to train is drawn from appraisal ratings; the plan stays at role and task level.66- Programmes are ranked, never people; the capacity line comes from your own days, and leadership approves the list and the line.6768## Next69Run ldg-make-the-business-case (Make the Business Case) for the programme that needs budget beyond the line.7071## About the makers7273This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).