Search for 'CPD statement Engineers Australia' and half the first-page results will tell you to log 150 hours over three years. For a Competency Demonstration Report (CDR), that figure is wrong. It belongs to Stage 2 Chartered status and National Engineering Register renewal, not to the migration skills assessment you are preparing. Copy it and you will either pad your log with filler or worry about a threshold no assessor will ever apply to your application.
This guide covers what the document actually is for a migration applicant: the activity categories Engineers Australia accepts, the fields every entry must carry, and an annotated sample for each category that models the one column deciding whether an entry reads as evidence or as attendance. If you already hold membership and just need your annual cycle, the general Engineers Australia CPD overview covers that instead. This piece is written for overseas-trained engineers on the CDR pathway.
What the CPD statement proves inside your CDR
Your career episodes argue that you practised engineering competently in the past. The CPD statement does a different job: it shows you have kept learning since, and that your recent development still points at the occupation you are nominating. Assessors read the two documents together, so a report full of strong past projects but no current, role-relevant learning raises an obvious question about whether your skills are still sharp.
Why Engineers Australia asks for it
Engineering knowledge dates fast. Standards revise, methods change, and an applicant who stopped developing five years ago is a different professional from one still tracking their field. The CPD statement is the evidence that you belong in the second group.
What an assessor is actually checking
Working through a stack of applications, an assessor is not tallying your hours. Three things get checked: that your activities fall inside the valid window, that they spread across more than one category, and that each one connects to a competency your nominated role demands. An entry that names a course and a number but nothing learned reads like a receipt, not a record.
The four CPD categories Engineers Australia accepts
Engineers Australia's Migration Skills Assessment booklet (the MSA booklet, the governing document for the CDR pathway) groups acceptable development into four broad categories. Some competitor pages split these into six or eight labels, but the extra rows mostly subdivide the same four. Cover at least three and you demonstrate breadth.
Formal education
Accredited courses, postgraduate study, and structured training with a defined syllabus. A master's unit in geotechnical engineering, a certified short course in AS 3600 concrete design, or a formal software certification all sit here.
Informal learning
Webinars, technical reading, standards review, and self-directed study. Working through a new Australian Standard, following a recorded conference session, or reading a technical journal to close a specific knowledge gap all count, provided you can say what you took from them.
Work-based learning
Skills gained on a live project: a new analysis technique picked up designing a pump station, a first exposure to Building Information Modelling on site, or a commissioning process learned by running it. This is often the richest category for a practising engineer, and overseas project work belongs here too.
Service to the profession
Mentoring junior engineers, presenting at a conference, sitting on a technical committee, or reviewing papers. These show engagement beyond your own job and read strongly when they connect to your discipline.
What every CPD statement entry must contain
Every row carries five fields. Miss the last one and your entry looks like nine out of ten samples circulating online.
The five fields every row needs
Date of the activity, the activity name, the provider or source, the duration in hours, and the competency developed. The first four are administrative and take seconds. The fifth carries the weight. Name it in one or two lines: what specific engineering skill or knowledge the activity built, and why it matters to your nominated role. Across the current first-page results, this field is absent from almost every sample, which is exactly why bare CPD tables fail to impress.
Table or paragraph: which an assessor prefers
Use a table. An assessor scanning many applications reads a grid far faster than running prose, and common CDR guidance recommends fitting the log onto roughly one A4 page. Keep the first four fields tight and give the competency column room to breathe.
Linking each entry to your ANZSCO code
Assessors verify that CPD entries support the duties of your nominated ANZSCO occupation, not just that you attended training. If you nominate Civil Engineer (233211), a course on structural detailing maps cleanly to that role; a generic project-management webinar does not, unless you write the competency field to make the link explicit. Choose activities that a reader can trace back to your code, and spell out the connection in the reflection.
How to build your CPD statement from scratch
Step 1: Set your window and gather records. Cover the three years immediately before submission. If you graduated less than three years ago, run the window from your graduation date to now. Pull together certificates, calendar entries, and project notes for that period.
Step 2: Sort each activity into one of the four categories. Label every item before you write anything. Gaps surface early this way, and if everything lands in one category, you will see it now, rather than in an assessor's feedback.
Step 3: Draft the competency field for each entry. For every activity, write one or two lines naming the skill developed and tying it to a duty of your nominated role. Write every reflection in your own words; never copy text between rows.
Step 4: Check breadth and alignment before you finalise. Confirm your activities span at least three categories and that each one visibly supports your ANZSCO code. Engineers Australia does not publish a mandatory minimum hour count for CDR applicants, so do not chase a total. Evidence of genuine, relevant development beats a padded tally every time.
CPD statement Engineers Australia sample entries by category
These samples use recent dates a 2026 applicant could plausibly claim. For each one, compare the weak competency line (attendance only) with the strong line (learning tied to the role).
Formal course
Field | Entry |
|---|---|
Date | 12 March 2024 |
Activity | Advanced Structural Analysis short course |
Provider | Engineering Education Australia |
Hours | 16 |
Competency, weak: Completed a course in structural analysis.
Competency, strong: Applied finite element modelling to a multi-storey frame and learned to verify member capacity against AS 3600, strengthening the structural design duties central to Civil Engineer (233211).
Informal learning
Field | Entry |
|---|---|
Date | 8 June 2025 |
Activity | Webinar and self-directed reading on AS 3600 concrete detailing |
Provider | Concrete Institute of Australia |
Hours | 6 |
Competency, weak: Watched a webinar about concrete standards.
Competency, strong: Compared AS 3600 reinforcement detailing with the code I trained under overseas, so I can now specify compliant detailing to the Australian standard, a direct requirement of my nominated role.
Work-based learning
Field | Entry |
|---|---|
Date | 20 August 2024 |
Activity | Stormwater design for a 40-lot subdivision (project in Muscat) |
Provider | On the job, previous employer |
Hours | 30 |
Competency, weak: Worked on a subdivision drainage project.
Competency, strong: Developed detention-basin sizing and stormwater modelling skills using regional rainfall data, transferable to water-sensitive urban design duties in Australian practice. Overseas project work like this qualifies because the activity date falls inside the three-year window.
Service to the profession
Field | Entry |
|---|---|
Date | 14 November 2025 |
Activity | Presented a technical paper at a regional structures conference |
Provider | Institution of Engineers (regional chapter) |
Hours | 8 |
Competency, weak: Attended a conference and gave a talk.
Competency, strong: Prepared and delivered a paper on seismic retrofit methods, building the technical communication and knowledge-sharing skills expected of a professional engineer.
Three entry patterns that draw assessor scrutiny
Activities logged with no reflection. Most common rejection trigger. A row of dates, titles, and hours proves you turned up, not that you learned. If most of your competency fields say some version of 'completed the course', an assessor treats the whole statement as a formality you rushed.
Dates outside the window, or no verifiable date at all. An activity from 2016 does nothing for a 2026 application, and an entry with no date cannot be checked. Several widely shared sample tables online are built from 1998 to 2016 activities that read as employment history; do not model yours on them.
Text that matches another applicant word for word. Reused competency lines, often lifted from a template or a paid sample, get flagged the same way plagiarism in career episodes does. Write every reflection from your own activity, in your own words.
Questions Engineers Australia applicants ask about the CPD statement
Does my CPD statement need to cover exactly 3 years?
No. Cover the three years immediately before submission. If you graduated less than three years ago, run the window from your graduation date to now, and that shorter period is accepted without penalty.
Can I include CPD I completed in my home country before migrating?
Yes. Overseas activities count as long as the activity date falls inside your valid window. For overseas-trained applicants, home-country courses, on-the-job learning, and conferences are legitimate entries and often make up most of the statement.
How many CPD entries should I include?
No official number exists. Common CDR guidance points to roughly 10 to 20 activities spread across the categories, but breadth and relevance matter far more than count. A dozen well-reflected entries beat thirty bare ones.
Is a table or paragraph format better?
A table. Assessors can scan the administrative fields quickly and read your competency reflections in a consistent column, and the layout fits neatly onto about one A4 page.
What if most of my CPD is informal or self-directed?
Engineers Australia accepts informal learning, so a statement weighted toward webinars, standards review, and private study is valid. Aim to include at least one or two activities from other categories as well, since breadth across categories reads more convincingly than depth in a single one.
Before you write your own, it helps to see what a reviewed entry looks like next to a first draft. Study strong, competency-linked examples on our CDR samples and review page, then build your statement from your real activities. For the wider pathway, our Engineers Australia skills assessment guide shows where the CPD statement fits.