Creating a Staff Development Plan with Clear Skills and Review Dates

A useful staff development plan identifies a skill, the work in which it will be used, the support available and a date for reviewing evidence. “Attend training” is an activity. A stronger plan explains what the employee should be able to do afterwards and how the manager will help them practise it.

This guide provides an editorial planning method for UK workplaces. The examples are fictional and are not employment-law advice or a substitute for your organisation’s procedures. Start with a training needs analysis if you have not yet established which skills need attention.

Agree the purpose before choosing an activity

Begin with the work. Perhaps a team member needs to produce a monthly report, handle a wider range of customer questions or prepare to supervise a project. Describe the task clearly enough that both people know what successful performance would look like. Avoid broad labels such as “be more professional” that leave the employee guessing.

Discuss the employee’s experience and interests alongside the business need. Someone may already understand the topic but lack access to the system in which they must use it. Another person may be doing the task correctly but too rarely to feel confident. Those situations call for different support from a course that teaches the subject from the beginning.

Acas guidance on reviews and appraisals connects performance discussions with objectives, support and development. Use the conversation to agree expectations and record them. Explain whether this is routine development or part of a separate formal process; do not leave the employee to infer the purpose from an unfamiliar form.

Describe a starting point you can both recognise

Choose a small sample of relevant work and discuss what it shows. Ask the employee how they approached the task, where they needed help and what would make the next attempt easier. Separate an observed gap from a judgement about motivation. An incomplete report might reflect unclear instructions, unavailable information or competing priorities.

Record the starting point in neutral language. “The draft includes the sales totals but does not reconcile returns” gives you something to work on. “Not good with numbers” is too broad and can obscure the actual problem. Keep the record focused on the work and avoid unnecessary personal information.

Check that the selected task is appropriate for the person’s role and current responsibilities. If the plan involves a new responsibility, identify any supervision, authorisation or other preparation needed before independent work begins. A development plan should not quietly assign work that the employee is not equipped to carry out safely.

Write a goal with an observable outcome

A practical goal can name the task, the expected standard, the evidence and the review point. For example: “By the end of the next reporting cycle, prepare the draft stock report using the agreed checklist, explain any unexplained differences and review it with the supervisor before circulation.” This gives both parties a shared reference.

Use dates that match the opportunity to practise. A monthly task may need several reporting cycles; a daily task may provide evidence sooner. Avoid choosing a deadline simply because it fits a standard form. If the necessary system access or training has not been arranged, include that dependency in the plan.

Keep the number of goals manageable. A long list can hide the most important requirement and make review superficial. Select the priorities you can support now, with other ideas recorded for later discussion. Make clear which parts are essential for the present role and which support longer-term development.

Choose learning that fits the gap

When an apprenticeship is being considered for the role, check the employer responsibilities for a first apprentice alongside the development goal. Use our apprenticeship provider comparison questions to test how training, workplace practice and feedback will connect rather than simply adding a course name to the plan.

A course can introduce concepts or provide structured practice, but it is not the only option. A demonstration, coached attempt, job shadowing session or small project may suit a particular need. Choose the activity because of the skill to be developed, not because a training budget must be spent.

For a demonstration, ask the experienced colleague to explain decisions as well as actions. The learner needs to know why a step matters and what to do when the usual conditions change. Follow observation with a supervised attempt, then feedback tied to the agreed standard.

If you select an external course, compare its learning outcomes, entry assumptions, assessment and opportunities for practice. Ask how its content will transfer to the employee’s actual work. A completion certificate records participation or achievement under the course’s rules; it does not automatically prove independent competence in every workplace situation.

Make the manager’s commitments explicit

Write down what the manager will provide: time, equipment, access, examples, feedback or contact with a specialist. Name who will arrange each item. “The employee will improve their skills” is incomplete when every practical condition is controlled by someone else.

Discuss workload before adding learning activities. Decide which existing work will move, who will cover urgent requests and how practice time will be protected. If the same session is repeatedly cancelled for operational reasons, record that honestly. It is a delivery problem to resolve, not evidence that the learner failed to develop.

Ask whether the format or resources create barriers and use the appropriate workplace process to arrange support. Keep confidential matters in the correct channel rather than putting detailed personal information into a widely shared development spreadsheet. A concise plan should contain what the people delivering the support need to know.

1. AgreeName the task, starting point and expected result.
2. EnableProvide learning, practice time, resources and feedback.
3. ReviewLook at work evidence and agree the next supported step.

Review application and adapt the plan

At the review, return to the agreed task and examine the evidence together. Discuss what the employee can now do, where help is still needed and whether the original goal remains relevant. Ask for the employee’s account before drawing conclusions from one result.

Use several signals where appropriate: a work sample, an explanation of the reasoning and feedback from supervised practice. Distinguish speed from accuracy and routine performance from handling an unusual case. A single successful attempt can be encouraging without establishing that support is no longer needed.

Finish with a specific decision. You might close the goal, extend practice, revise the method or address a missing resource. Record why, who will act and when you will return to it. If a change of role is the wider ambition, compare the next requirements using our guide to skills, interests and real entry requirements.

Common questions

How long should a development plan be?

Long enough to make the goal, support, evidence and review arrangements clear. A short plan with one meaningful priority can be more useful than a large document nobody uses. Add detail where the task is complex or responsibilities need particular clarification.

Who should write it?

The manager and employee should discuss it together, even if one person records the result. The employee can explain existing knowledge and barriers; the manager can confirm expectations and resources. Both should be able to describe the agreed next action in their own words.

Does every goal need a training course?

No. Match the activity to the gap. Guided practice may suit an unfamiliar workplace process, while a course may help with a new body of knowledge. In either case, include an opportunity to apply the learning and receive feedback.

How often should progress be reviewed?

Choose intervals that fit the work and the learning activity. Use an early check to resolve access or timetable problems, then a later review when there is meaningful evidence. Do not wait for an annual meeting if a missing resource prevents any progress.

What if the employee completes the course but still needs help?

Examine the transfer to work. They may need supervised practice, a clearer procedure or examples that match the job. Discuss the remaining gap specifically rather than repeating the same course automatically. Update the plan with the support and evidence needed next.

Can career ambitions be included?

Yes, while distinguishing current-role priorities from possible future development. Record what can realistically be offered and avoid implying a guaranteed promotion or vacancy. A useful next step might be exploring a role, speaking with an experienced colleague or completing a relevant project.

What if business priorities change?

Review the goal openly and agree whether to change, pause or replace it. Preserve a brief record of what was completed and why the plan changed. Do not assess someone against an obsolete objective without considering the changed circumstances.

Is a development plan the same as a formal performance process?

Not necessarily. Similar documents can be used for different purposes. Explain the purpose, applicable policy and expectations clearly at the start. If formal employment issues arise, use the appropriate procedures and qualified advice rather than treating this general planning guide as a legal framework.

Sources and further reading

• Acas: Reviews and appraisals — objectives, feedback and development discussions. Accessed 21 October 2026.
• Acas: Appraisal templates — examples of records for review conversations. Accessed 21 October 2026.