CDR Report Format for Engineers Australia: Complete Guide

An assessor at Engineers Australia spends far less time reading your submission than you spent writing it, and the CDR report format for Engineers Australia is what either earns their confidence in the first minute or triggers a return request. Mislabel a paragraph, miss a word-count band, or leave a competency cell empty, and the document bounces back before the engineering is even assessed. This guide walks the format section by section for the Professional Engineer category: the structure the Migration Skills Assessment (MSA) booklet sets, the paragraph-numbering system that ties the three documents together, and the Summary Statement table that most guides describe in prose but never actually show. It assumes you already understand the broader skills assessment pathway, so it stays on format.

What Your Engineers Australia CDR Contains and How Assessors Read It

Confirm one thing before you format a single line: that you are building against the right competency standard. Engineers Australia assesses four occupation categories, and each uses its own Summary Statement template with its own element codes.

Your nominated ANZSCO code decides the category, and the category decides the template. This is a genuine trap for mid-career engineers whose experience straddles two levels: choose the Professional Engineer template when your code maps to Engineering Technologist, and every paragraph reference points at the wrong sub-elements. Fix the code question first. Everything below assumes the Professional Engineer standard.

A complete CDR holds three documents that interlock. First, the Continuing Professional Development (CPD) log: a single-page table of what you have done to stay current. Each of the three Career Episodes then runs 1,000 to 2,500 words in the first person, describing engineering work you personally performed. Tying them together, the Summary Statement maps numbered paragraphs from those episodes to each Professional Engineer competency element. This is why the CDR report format for Engineers Australia is judged as a system, not three separate uploads.

How an assessor moves through your submission

An assessor typically opens the Summary Statement first and uses it as an index. Each row names a competency element and points to a Career Episode paragraph, for example CE2.4, that is meant to prove it. The assessor jumps to that paragraph, verifies it genuinely demonstrates the element, and moves on. Miss, blur, or misdirect that reference, and the element counts as unevidenced. That is not cosmetic: a broken reference means an unproven competency, which means a return request or a negative outcome. For the specific mistakes that cause this, see the common CDR submission errors.

CPD Log Format: The Four Fields Every Entry Needs

Keep the whole CPD log to one A4 page in table format. Within that table, every entry needs four fields. The MSA booklet specifies date, activity description, duration in hours, and learning outcome as the required fields; the field applicants most often drop, or replace with a venue name, is the learning outcome. Some templates add a provider or venue column as a fifth field, but that column is supplementary. The four the booklet mandates are the ones assessors check.

The distinction between the two right-hand cells matters. The activity description says what you attended or did. The learning outcome says what changed in your practice as a result. “Attended a seminar on geotechnical risk” is a description; “revised our site investigation checklist to add two additional boreholes” is a learning outcome. An entry that repeats the activity title in the outcome column reads as padding and invites a query.

Engineers Australia counts formal courses, workshops, conferences, structured private study, and relevant volunteering. Informal reading with no demonstrable output attached is the category most often questioned, precisely because there is no practice change to describe in the outcome field. For how much CPD you need and which activities qualify, see the Engineers Australia CPD requirements.

Career Episode Format and Word-Count Targets

Each Career Episode runs 1,000 to 2,500 words and stays in the first-person singular from the first word to the last. Write “I designed”, “I calculated”, “I decided”, never “the team” or “we”, because the assessor is evaluating your individual competence, not your employer’s project. Each episode splits into four internal sections, and the word split matters as much as the total.

The Personal Engineering Activity carries the assessment, so give it the room. A Background that swells past 500 words usually means you are describing the project instead of your work, which is the single most common reason a strong engineer produces a weak episode. Keep the Summary genuinely short and reflective; do not restate what the Background already said.

The CE[x].[y] paragraph numbering convention

Number every paragraph in the Personal Engineering Activity so the Summary Statement can cite it. The convention is CE followed by the episode number, a dot, then the paragraph number. CE1.3 is Career Episode 1, paragraph 3. CE2.8 is Career Episode 2, paragraph 8. Place the label at the start of the paragraph in the running text, like this:

> CE1.3 To bring the pump station within its hydraulic design tolerance, I modelled the transient load profile, ran three surge scenarios against the manufacturer’s pump curve, and specified an air vessel sized to hold the pressure rise below the pipe’s rated limit.

That paragraph is positioned to evidence PE2.1, the application of established engineering methods. When you build the Summary Statement, one row names PE2.1, describes what you did in a phrase, and points to CE1.3. The label in the text and the reference in the table must match exactly, which means you should finalise episode wording before assigning paragraph numbers. For narrative technique inside these paragraphs, the ten CDR writing principles go deeper than format allows here.

CDR Report Format for Engineers Australia: Summary Statement Structure

The Summary Statement is a table, not a set of paragraphs. The MSA booklet specifies three columns for the Professional Engineer template: the competency element code and its descriptor, a brief statement of how you applied that competency, and the Career Episode paragraph reference. Build yours to match that structure exactly.

A four-column variant circulates in some preparation guides and adds an “indicators” column between the descriptor and the application statement. That column does not appear in the current MSA booklet’s Professional Engineer template. Use the three-column structure above and verify it against the Engineers Australia template you download directly from their portal before you lodge.

Mapping all 17 PE sub-elements without gaps

The Professional Engineer standard groups competencies into three units: PE1 Knowledge and Skill Base (PE1.1 to PE1.6), PE2 Engineering Application Ability (PE2.1 to PE2.6), and PE3 Professional and Personal Attributes (PE3.1 to PE3.5). That is 17 sub-elements, and the Summary Statement needs a row for every one, with no gaps. Confirm the PE3 count against your edition of the booklet before you finalise: Engineers Australia has revised the Professional Attributes indicators, and some current templates show a sixth PE3 element, so match your live template rather than this or any other guide.

Our format analysis, mapped from the public structure of the MSA booklet, shows which episode section is best placed to feed each part of the table:

PE1 and PE2 tend to look after themselves, because engineers naturally write about what they knew and what they built. The elements that go under-evidenced sit in PE3. In practice, PE3.2 (effective oral and written communication), PE3.4 (professional use and management of information), and PE3.5 (personal and professional development) are the three most commonly left without a traceable paragraph reference, because a technical narrative rarely stops to demonstrate them explicitly. Before you lodge, read your three episodes with only the PE3 rows open and check that each one points to a real paragraph showing the professional behaviour, not just an engineering outcome.

CDR Report Format for Engineers Australia: Pre-Lodge Checklist

Run the mechanical checks last, once the content is locked. Submit the CDR as a single PDF. Set the body in Times New Roman or Arial at 11 or 12 point. Keep consistent margins, number your pages, and confirm the CPD log still fits on one A4 page after any edits.

Five formatting faults trigger an Engineers Australia return request more often than content weaknesses do:

1. A Career Episode under 1,000 or over 2,500 words.

2. Paragraph labels that are missing, inconsistent, or do not match the Summary Statement references, so an element cannot be traced.

3. A CPD log that spills past one A4 page or omits the learning outcome field.

4. The wrong Summary Statement template for your ANZSCO category, so the element codes do not match the standard you are assessed under.

5. Career Episodes drifting out of first person, or reused wording that plagiarism detection flags, which can carry a ban period.

The fees for lodging, and for re-lodging after a return, are set out in the 2026 CDR fees breakdown; a return request is an avoidable cost. If you are still confirming your eligibility, settle that via the Professional Engineer pathway guide before you format anything.

Get the paragraph numbers, the word bands, and the Summary Statement references aligned, and the assessment turns on your engineering, which is where you want it decided. Before you draft, confirm your CPD log meets the assessor’s standard, because a compliant log is the easiest of the three documents to get right and the one applicants most often leave until last.

Frequently Asked Questions

Can I reference the same engineering project in all three Career Episodes?

No. Each Career Episode should cover a different engineering project or a distinctly different role, because three episodes drawn from one project rarely demonstrate the full spread of PE1, PE2, and PE3 competencies. You can draw from the same employer or the same broad program, but the specific engineering activity in each episode must be separate.

Does the CPD log have a minimum word count, or just a minimum number of entries?

There is no word count for the CPD log. It is judged on the activities recorded, not on length, and the whole table must fit on one A4 page. Focus each entry on a clear activity description, its duration in hours, and a concrete learning outcome rather than on padding the wording.

What paragraph-numbering format does Engineers Australia require for Summary Statement cross-references?

Use CE followed by the episode number, a dot, and the paragraph number: CE1.5 means Career Episode 1, paragraph 5. Number the paragraphs in each Personal Engineering Activity section and cite those exact labels in the Summary Statement’s reference column, so every competency element traces to a specific passage.

Can a Career Episode describe a non-engineering role if it demonstrates engineering competency?

The role can carry a non-engineering title, but the activity you describe must be engineering work that demonstrates the Professional Engineer competencies. A project manager or operations lead can write a valid episode, provided the paragraphs show engineering analysis, design, or problem-solving that you personally performed, not general management.

What file format, font, and margin does Engineers Australia accept for CDR submissions?

Submit as a PDF, set in Times New Roman or Arial at 11 or 12 point, with consistent margins and numbered pages. Confirm the exact current requirements against the MSA booklet before you lodge, since these presentation rules are the cheapest part of the submission to get right.

Read the companion guide on Engineers Australia CPD requirements to confirm your professional development log meets the assessor’s standard before you submit.