An Engineers Australia assessor opens your file and reads the summary statement first, before a single career episode. That reading habit explains the entire CDR report format: every structural rule exists so one reviewer can confirm your competency quickly and defensibly. A negative finding blocks resubmission for twelve months, which for most permanent residency timelines means a lost year and a re-paid fee. This guide walks each of the four components the way the assessor evaluates them, and shows what a non-compliant submission looks like when it lands on the desk.
What the CDR Report Format Requires in the MSA Booklet
The Migration Skills Assessment (MSA) Booklet, available from the Engineers Australia portal, fixes the CDR report format and is the only rulebook that binds you. Download the current edition before you start, because the rules have moved: projects must now sit within the last ten years, not fifteen, and plagiarism or AI-generated text now draws a hard penalty.
One thing to settle first. The migration assessment is judged against the Stage 1 Competency Standard, the entry-to-practice benchmark. It is not Stage 2, which governs Chartered (CPEng) status and runs through a separate process. Several guides loosely call the migration standard “Stage 2”; that is a mislabel, and a Chartered-level template will map to the wrong indicators.
The four documents and the order you submit them
A complete CDR has four documents read as a set: a curriculum vitae, three career episodes, a continuing professional development (CPD) list, and a summary statement that cross-references all three episodes. The summary statement is written last because it points into the other documents. Think of the episodes as evidence exhibits and the summary statement as the index a reviewer reads to locate each one. Submit an episode with no matching summary reference, and the competency it proves may as well not be there.
How an assessor actually reads your file
The assessor works the summary statement row by row. For each indicator, they jump to the paragraph you cited to confirm the claim is real, specific, and yours. If the cited paragraph says what the row promises, the element is credited. If the paragraph is vague, describes team work, or does not exist at the number you gave, the element fails and a gap opens. Sixteen elements, each independently checkable: that is the machine your format has to feed.
Career Episode Format: Structure, Length, and Your Own Work
A career episode is a continuous first-person essay about one project or a defined period where you held a genuine engineering role. Before you draft, run three filters: is the project within the last ten years, did you personally perform engineering work on it, and does that work match tasks listed under your nominated ANZSCO occupation code? Fail any one, and the episode is weak before the first sentence.
The three-part episode: background, activity, summary
Engineers Australia expects four labelled parts, though the load sits on two of them. The introduction is short, roughly 100 words, setting date, location, and your title. The background runs 200 to 500 words on the project’s objectives, your organisation, and the reporting line. The personal engineering activity is the core section, 600 to 1,500 words, and it is the only part the summary statement will cite. The summary closes in 50 to 100 words on what you delivered and learned. One hard rule inside the activity section: prose only. No bullet lists, no tables, no diagrams in that narrative, because the assessor needs connected reasoning, not fragments.
Why 1,000 to 2,500 words is a signal, not a limit
Each episode must land between 1,000 and 2,500 words. Treat the band as a diagnostic. Come in under 1,000, and you are telling the assessor the role lacked engineering depth, or that you cannot articulate it; both read as thin evidence. Run well over 2,500, and the usual cause is padding, or worse, a project so large that your individual contribution is buried in collective work the assessor cannot untangle. The sweet spot is one project scoped tightly enough that every paragraph is defensibly yours.
First person, and the attribution rule behind it
Write “I”, not “we”. The assessor cannot attribute team work to an individual, so a paragraph that says “we designed the drainage network” earns no credit toward any element. This is the mechanism that decides whether a paragraph passes or fails. Name your specific act, the method you applied, and a result you can stand behind.
| Version | What the assessor sees |
|---|---|
| Non-compliant: “We designed the stormwater network to handle peak flows, and the team delivered the model on time.” | Collective voice, no method, no measurable result. Cannot be attributed to you, so it credits no element. |
| Compliant: “I sized the stormwater pipe network, computing peak flows with the Rational Method and modelling each reach in DRAINS; I cut surcharged nodes from nine to zero across two design iterations.” | Individual act, named technique, measurable outcome. Directly supports PE2.1 and PE2.3. |
Choosing three projects with no wasted overlap
Three episodes have to cover all sixteen elements between them, so choose projects that pull in different directions. If all three are design-heavy and none touches project management or stakeholder communication, PE2.4 and PE3.6 go unproven no matter how strong the engineering content is. Map coverage before writing: list the elements each candidate project can evidence, then pick the combination that leaves no blank rows. Some overlap is natural, but three episodes proving the same handful of elements waste two-thirds of your evidence budget.
Summary Statement Format: Mapping Codes to Competencies
The summary statement is not prose. It is a coded index, and it is the single most common point of failure in any submission.
Inside the four-column table
The current template is a four-column table: the competency element code, the indicator text, the paragraph reference in CE#.X form, and a brief description of the evidence. The paragraph reference is the load-bearing column. CE2.14 means career episode two, paragraph fourteen, so your episodes must carry numbered paragraphs for the reference to resolve. A fully populated example row:
| Element | Indicator | Reference | Evidence description |
|---|---|---|---|
| PE2.3 | Application of systematic engineering synthesis and design processes | CE2.14 | Sized the stormwater detention basin with the Rational Method for a 1-in-100-year event, iterating three geometries in DRAINS until peak outflow fell below the 1.2 m3/s pre-development limit. |
The 16 elements and confirming the current indicators
For a Professional Engineer, the sixteen elements split into three groups. PE1.1 to PE1.6 cover the Knowledge and Skill Base: engineering knowledge, problem analysis, and discipline specialism. PE2.1 to PE2.4 cover Engineering Application Ability: established methods applied to complex problems (PE2.1), fluent use of techniques and tools (PE2.2), synthesis and design (PE2.3), and project management (PE2.4). PE3.1 to PE3.6 cover Professional and Personal Attributes: ethical conduct, communication, a creative and proactive demeanour, information management, self-management, and team membership and leadership.
Note the count. Some third-party guides extend PE2 to PE2.6, giving eighteen elements; the Stage 1 standard defines four in that group. Confirm the exact list against the template you download, not a secondary site. Engineers Australia revises these indicators from time to time, so build your summary statement from the template in the current MSA Booklet rather than an older copy. The PE3 sub-elements in particular, especially information management (PE3.4) and self-management (PE3.5), expect examples tied to a concrete professional context rather than general statements of intent. A summary statement built on an outdated template can miss content the current standard expects, which leaves the file non-compliant before you write a word.
Mapping errors ranked by how badly they hurt
Not all mapping errors cost the same. A missing element, no row at all for PE3.5, is the worst outcome: the assessor has nothing to check and records a straight gap. A wrong paragraph number comes next, because the reference resolves to text that does not support the claim, so the element is unverifiable and fails. A vague evidence description such as “demonstrated good communication” cannot be credited even when the underlying work was strong. Most dangerous of all: a summary claim describing work that never appears in the cited episode. That reads as fabrication, which is a trust problem, not a formatting one.
CPD Format: What Counts and How to Log Three Years
CPD proves you kept developing after graduation. It is presented as a table, and each entry carries a title, date, duration, location, and organiser. Cover the most recent three years and span at least two recognised categories.
Three categories, their type codes, and the hour ceilings that apply
Engineers Australia uses a typed CPD system. The three headline categories each break into numbered types with individual hour caps across the three-year window:
Formal Learning covers accredited study and structured training.
- Type I (post-graduate study): no stated per-type cap, but counts toward the combined formal learning total
- Type II (short courses, seminars, workshops with assessment): counts toward formal learning total
Informal Learning covers self-directed activity.
- Type III (private study, technical reading, webinars, on-demand content): combined with workplace learning (Type IV), capped at 110 hours total
- Type IV (workplace learning, on-the-job training): capped at 75 hours; combined with Type III, the two together cannot exceed 110 hours
Professional Activities covers engagement beyond the desk.
- Type V (industry service, committee membership, board roles): capped at 50 hours
- Type VI (presentation of papers, published technical writing): no separate cap stated; counts toward professional activities
- Type VII (mentoring others, supervising graduates): counts toward professional activities
- Type VIII (Engineers Australia involvement, branch activity): counts toward professional activities
Load your log with 200 hours of on-the-job learning, and the excess beyond the 75-hour cap is simply discounted, which can drop your verified total below the expected threshold. Balance the categories deliberately and note the type code in each entry so the assessor can apply the correct ceiling.
Logging self-study without inflating hours
Self-directed study counts, but only at honest hours tied to real output. Reading AS/NZS 3500 to resolve a design question is legitimate CPD; claiming forty hours for skimming a standard invites scrutiny, especially when the assessor cross-checks your CPD against the methods cited in your episodes. Log the actual time. If a webinar ran ninety minutes, enter ninety minutes. The log’s credibility carries more weight than its volume.
A worked CPD log entry
| Date | Activity | Provider | Category / Type | Hours | Relevance |
|---|---|---|---|---|---|
| 14 Mar 2025 | Short course: hydraulic design to AS/NZS 3500 | Engineering Education Australia | Formal (Type II) | 8 | Refreshed the drainage design basis applied in Career Episode 3 |
CV Format: Where the CDR Version Breaks From a Resume
Your job-hunting resume will not pass as a CDR CV. The document stays under three pages, runs in reverse chronological order, and carries fields a standard resume omits.
Fields a normal resume leaves out
The CDR CV requires your full legal name exactly as it appears on your passport, your nationality, and for each qualification: the institution’s full name, the country, and the graduation month and year, not just the year. Professional membership numbers and their issuing bodies belong here too. The field most applicants miss is the verifier declaration: a statement that reads “I verify that this is a true statement of the career history of [applicant’s full name] during the period [start date] to [end date],” followed by the verifier’s name, address, phone number, and professional status. A standard resume has no equivalent, so it is easy to omit and expensive to leave out.
Concurrent roles, gaps, and overlapping projects
Real careers are messy, and the CV has to stay legible anyway. List concurrent roles as separate entries with their true date ranges rather than collapsing them, so overlapping project dates reconcile with the dates in your episodes. Explain employment gaps briefly rather than hiding them: an unexplained gap invites the assessor to ask what you were doing, and any inconsistency between your CV and your episodes is a documented trigger for closer scrutiny.
Why your exact institution and graduation month matter
The precise institution name, country, and graduation month let Engineers Australia verify your qualification against its records and recognition agreements. “B.Tech, 2019” forces the assessor to chase specifics or to doubt the entry. Provide the exact awarding institution, the campus country, and the month of graduation, and match them to the certificate you scan at a minimum of 300 dpi in colour. Certified photocopies are no longer accepted.
Format Mistakes That Trigger an Adverse Finding
These CDR report format failures sink submissions, roughly in order of how often they appear. The summary statement comes first: an index that does not resolve, whether through missing elements, wrong paragraph numbers, or claims absent from the cited episode, fails more submissions than any other single fault. Team language in the personal engineering activity ranks second: the collective “we” that strips individual attribution from every paragraph it touches.
The mechanical triggers follow, each capable of a rejection on its own: word counts outside the 1,000 to 2,500 band, projects older than ten years, scans below 300 dpi, and text flagged as plagiarised or AI-generated.
On that last point: using an AI assistant to check grammar differs from submitting AI-written episodes, but a career episode generated wholesale reads as generic, unattributable, and detectable. Combined with the twelve-month resubmission ban, that is a heavy price for a shortcut. Build the file to survive one careful reader, and the format takes care of itself.
FAQs
How many career episodes are required, and can I reuse a project?
Three, and no. Each episode must cover a distinct project or work period. Reusing the same project across two episodes duplicates evidence, wastes an episode’s worth of competency coverage, and signals a thin work history to the assessor.
What is the accepted word count for each career episode?
Between 1,000 and 2,500 words. Under 1,000 reads as insufficient engineering depth; over 2,500 usually means padding or team-attributed work the assessor cannot credit to you individually.
How do I map competency elements to paragraphs?
Number every paragraph in your episodes, then cite each element in the summary statement to the exact paragraph that proves it, in CE#.X form (for example, CE2.14). The cited paragraph must contain a specific, first-person engineering act, not a general statement.
What CPD counts, and how far back can it go?
Formal learning, informal learning, and professional activities all count, provided they cover the most recent three years, span at least two of the recognised categories, and stay within the hour ceilings: 75 hours for workplace learning (Type IV), 110 hours combined for Types III and IV, and 50 hours for industry service (Type V). Activity older than three years does not generally count.
How does the CDR CV differ from a standard resume?
It stays under three pages in reverse chronological order and adds fields a resume omits: full legal name as per passport, nationality, institution name and country, graduation month and year, membership numbers, and a signed verifier declaration.
Can career episodes come from outside my ANZSCO occupation?
They should not. Each episode must demonstrate tasks listed under your nominated ANZSCO occupation code. Episodes drawn from an adjacent role are a common reason assessors find the evidence misaligned with the occupation, which can produce an adverse outcome. For more on how occupation alignment affects your assessment, see what the CRR skills assessment process involves.
Before you submit, map every episode paragraph against the sixteen competency elements and confirm each row in your summary statement resolves to a specific, first-person paragraph. For a structured walkthrough of what happens when career episodes do not align with the nominated occupation, see our guide on CE and occupation misalignment.