The idea

Continuing professional development (CPD) is how engineers keep getting better after their degree, and registration expects you to record it. It’s a cycle: work out what you need → learn it however suits you → reflect on what you learned → set the next goal. The skill underneath it is reflection: looking back at an experience honestly enough to change what you do next time.

Where CPD comes from

AcademicPracticalProfessionalVolunteering
Lectures, coursework, software, reportsProjects, competitions, prototypes, internshipsTalks, industry visits, institution events, societiesMentoring, outreach, running a club

The UK-SPEC CPD code asks engineers to own their development, do a variety of activities, and record, reflect, evaluate and review. They should also support other people’s development.

Gibbs’ reflective cycle

Gibbs' reflective cycle

StageAsk
DescriptionWhat happened?
FeelingsWhat did you, and others, feel?
EvaluationWhat went well and badly?
AnalysisWhy did it happen that way?
ConclusionWhat did you learn? What do you need to develop?
Action planWhat will you do next time, and what help do you need?

The analysis is where most reflections are weak. “The meeting went badly” is a description; “there was no agenda, nobody led, and I didn’t speak up when I could have” is analysis.

SMART goals

Ask
SpecificWhat exactly, and what are the steps?
MeasurableHow will I know I’ve done it?
AttainableIs it realistic for me now?
RelevantDoes it link to a real gap or next step?
Time-boundBy when?

Broad: “contribute more confidently in meetings.” SMART: “In each of the next two seminars, bring one prepared question or suggestion, ask a peer afterwards whether it was clear, and record one improvement.”

Evidencing development

A good CPD record links goal → activity and evidence → what I learned → review and next action. Evidence is anything dated and checkable: finished work, feedback, a certificate, a before-and-after comparison.

Check yourself