CPD Goal & Evidence Log

Set three development goals for the year, log what you do against them with the proof of what changed, and check the goals against that proof every quarter. At year-end you have a case you can show, not a memory you have to reconstruct.

Continuing professional development is mixed research: the tested evidence comes mostly from physicians' continuing education (synthesis of reviews: Cervero & Gaines, 2015), and elsewhere CPD is a regulated practice rather than a tested model (Leaton Gray, 2005). The log format itself is practice, not research.

Use it when:

• Your profession, employer or a credential requires you to show ongoing development.
• You want evidence for a performance review, a promotion or a new role, not a list of courses.
• You learn a lot on the job but cannot say what it adds up to.

Skip it when:

• You do not yet know which skills matter for where you are heading: map them first with 1.5 Skill Gap Map & Priority List.
• You want to work through one experience in depth: use 1.13 Gibbs Deep Reflection Template.

CPD rests on two claims: competence fades unless it is maintained on purpose, and that maintenance should be planned, recorded and reviewed. Outside medicine the claims are mostly built into professional rules rather than tested, and in teaching the term covers learning on courses and on the job alike (Leaton Gray, 2005). The best evidence, from physicians, suggests format matters more than attendance: interactive, repeated activities did better (Cervero & Gaines, 2015).

What this log keeps is the part anyone can audit. A claim backed by a goal, an activity, an application and evidence can be shown to a manager, a panel or a professional body. A claim backed by memory cannot. The deeper mechanism is honesty: writing down what an activity was for exposes the activities that were for nothing. That is why every goal starts with why it matters, every entry pairs the lesson with how you used it, and the quarterly review checks goals against evidence, not effort. Hours are the cost of development, not the proof of it. The limit: no study shows that keeping a log by itself improves learning.

Write at most three goals. For each, say why it matters for your role or the next one, and what evidence would convince a skeptical reader that you got there.

Strong answer: "Run supplier audits on my own. Why: the senior role I want requires it. Proof: two audit reports signed off by the quality manager without rework, by October."

Illustrative example: the role, the company and the hours are made up.

A quality engineer at a food manufacturer in Denmark wants the senior quality role in two years.

Section 1: Goal 1 is to run supplier audits alone, proved by two audit reports signed off without rework by October. Goal 2 is to present quality figures to the plant management team, proved by the plant manager's feedback after two presentations.

Section 2: in March the engineer shadowed two audits (6 hours, on-the-job experience) and learned to trace a deviation to the supplier's own records. Applied in April in a first own audit. Evidence: the report and the quality manager's written comments. A two-day course on food safety standards also went into the log, but the application column stayed empty.

Section 3: in the Q2 review Goal 1 is on track and Goal 2 is behind: no presentation has happened. Adjustment: ask the manager for the July slot.

Section 4: what works is learning on the job and applying it within a week. The engineer decides that the course must produce an applied entry before the next one is booked.