Engineers Australia can return a Competency Demonstration Report before an assessor weighs a single technical claim, purely on length and format. Get the CDR report word count wrong, whether too thin to prove competency or so long it buries your personal engineering contribution, and you trigger a revision request that adds weeks to an already slow Migration Skills Assessment. This reference maps every section length and formatting rule Engineers Australia sets in its MSA booklet (2023/2024 edition), then hands you a word-budget model so you know what a compliant submission looks like before you write a sentence.
What the MSA Booklet Specifies About CDR Length
Section C of the MSA booklet (2023/2024 edition) is the governing source for what a CDR must contain and how each part is structured. It does not publish one master CDR report word count for the whole report. Instead, it fixes a range for the career episodes and describes the shape of the summary statement and CPD list, and the totals fall out of those pieces.
The Four Documents in a Complete CDR Submission
A complete CDR is four documents, not one: a Continuing Professional Development (CPD) list, three career episodes, a single summary statement, and your curriculum vitae with supporting evidence. Engineers Australia also fixes the order they appear in the uploaded file: CPD list first, then Career Episode 1, Career Episode 2, Career Episode 3, and the summary statement last. Assessors read in that sequence, so a report that opens with a career episode instead of the CPD list already reads as non-standard.
Why Length Signals Evidence Depth to Assessors
Word count is a proxy for evidence. An assessor is looking for enough demonstrated engineering activity to map competency indicators to specific paragraphs. A starved episode simply does not give them enough material. The opposite problem is subtler: a 3,000-word episode padded with organisational background and team achievements dilutes the “I did this” signal the whole exercise depends on. Length is not the goal; sufficient, attributable evidence is. The ranges below exist to keep you inside that band.
The Three-Tier CDR Report Word Count Model
Most competitor pages quote a per-section number and stop. None give you a running budget, so here is a full CDR report word count allocation model with the arithmetic shown so you can adjust it to your own writing.
| Submission tier | Three career episodes | Summary statement | CDR introduction | Approx prose total |
|---|---|---|---|---|
| Minimum viable | 1,000 x 3 = 3,000 | ~600 | optional | ~3,600 |
| Recommended | 1,800 x 3 = 5,400 | ~1,300 | ~350 | ~7,050 |
| Safe ceiling | 2,500 x 3 = 7,500 | ~1,500 | ~400 | ~9,400 |
CPD sits outside that prose count: it is a one-page table of activities, not flowing text. One published length analysis puts a well-documented CDR around 6,000 to 6,800 words in total, which lands squarely inside the recommended tier. Aim there. The minimum tier clears the rules but leaves no room for the specifics that turn a bare “meets” into a confident one. The ceiling tier is where dilution starts, unless every episode genuinely earns its length.
Career Episode Word Count: The 1000 to 2500 Word Window
Each career episode must run between 1,000 and 2,500 words, and you need three of them. That range is the one hard number Engineers Australia publishes for the CDR report word count, and every other budget in this guide is built around it.
When a Career Episode Falls Below 1000 Words
An episode under 1,000 words usually draws an insufficient-evidence finding. The assessor cannot locate enough distinct engineering activity to satisfy the competency indicators, so the episode fails regardless of how strong the underlying project was. This is the more common rejection of the two, and it catches applicants who compress a genuinely complex project into three brisk paragraphs.
Why Passing 2500 Words Weakens Your Case
Exceeding 2,500 words rarely causes outright rejection, but it works against you. The extra length almost always comes from project context, company history, or team accomplishments, and every one of those sentences pushes your personal contribution further into the background. Assessors read for the first-person “I”, and a longer episode gives them more places to lose it.
How to Structure Each Career Episode
Inside each episode, the booklet expects four parts, and the internal budget matters as much as the total: Introduction 150 to 200 words, Background 200 to 500 words, Personal Engineering Activity 600 to 1,500 words, and a short Summary of 50 to 150 words. The Personal Engineering Activity is where the assessment is won or lost.
Introduction: Project Context in 150 to 200 Words
Open with the project’s name, dates, location, and your position, in 150 to 200 words. Its only job is to orient the assessor before the technical detail starts, so resist the urge to make competency claims here.
Background: The Technical Environment and Your Place in It
200 to 500 words is sufficient for this section. Set the stage: the organisation, the scope of the work, the team structure, and where you sat in it. Anything longer starts eating into the budget that should belong to your own engineering.
Personal Engineering Activity: Where Your Words Must Go
This is the core, and it should carry 600 to 1,500 words, more than half the episode. Write in the first-person singular: “I designed”, “I calculated”, “I resolved”, never “we” or “the team”. Number the paragraphs (1.1, 1.2, 1.3 for the first episode; 2.1, 2.2 for the second), because those numbers are what your summary statement will point to. Engineers Australia expects continuous prose here; a bullet list reads as an attempt to skip the demonstration.
Summary: The Outcome You Personally Delivered
Close each episode in 50 to 150 words with the result and your specific contribution to it. This is a genuine wrap-up of that one project, not a summary of the whole report.
Summary Statement Word Count and Competency Mapping
The summary statement is a table, not an essay, and it is the single most mechanical part of the CDR. It cross-references every competency element you must demonstrate to the exact career-episode paragraph that proves it. Across all three episodes, it typically runs about 1,500 words.
How Many Competency Elements You Must Cover
For a Professional Engineer, the summary statement addresses the full set of elements across three areas: PE1 Knowledge and Skill Base, PE2 Engineering Application Ability, and PE3 Professional and Personal Attributes, 18 core elements in total. Every indicator cell needs 2 to 4 sentences, and no cell may be left blank. One important update: Engineers Australia’s June 2025 guide, “How to Write Career Episodes and a Summary Statement”, added two new indicators to the PE3 area. If you are working from a template or a competitor page that lists the older count, download the current template from Engineers Australia directly before you map anything.
How Many Words Per Competency Element, and the Figure to Ignore
Two widely shared “mistakes” pages state that the summary statement cannot exceed 100 words. Ignore that number. It is an apparent transcription error, contradicted by every detailed source, which puts the summary statement near 1,500 words. At 2 to 4 sentences per indicator across roughly 18 indicators, 100 words is arithmetically impossible. Budget about 60 to 90 words per indicator and let the total land where it lands.
Here is what one filled cell looks like. To evidence PE2.3 (fluent application of engineering techniques), you write “CE2.7” in the Paragraph Reference column, referencing paragraph 2.7 of Career Episode 2, and in the description column you write something like: “In CE2.7 I selected and applied finite-element analysis to verify the bracket design against fatigue loading. I justified the mesh density and interpreted the stress results to revise the weld detail.” That is the entire mechanism: indicator label (e.g., PE2.3), CE-prefixed paragraph reference (CE2.7), then 2 to 4 sentences of attributed evidence.
Which Template Your ANZSCO Code Selects
The competency standard you write against depends on your nominated occupation, and applicants routinely map to the wrong one. Professional Engineer roles (ANZSCO 233xxx) use the PE1-PE2-PE3 framework above. Engineering Technologist applicants (233914) write against a different standard, Engineering Associates (312xxx) against a third, and Engineering Managers against a fourth. Check your ANZSCO unit group first, then pull the matching summary statement template from MSA Section C. A flawlessly written statement mapped to the wrong occupational standard still fails.
CPD List: Format, Recency, and Activity Types
The CPD list is the smallest document and the easiest to over-engineer. For migration assessment, it is a single A4 page, in a table or list, showing each activity’s title, date, duration, and venue or organising body, in reverse chronological order.
The Three-Year Recency Rule
List only the CPD you completed in the three years immediately before you apply. That recency window is about how current your development is, not how long your assessment lasts. Activities from a decade ago do not belong on the list.
What Counts as CPD, and the Framework You Can Ignore
Engineers Australia’s MSA booklet recognises four broad CPD activity categories for migration assessment: formal education and training (courses, seminars, workshops, and conferences); work-based activities (project engineering, technical problem-solving, and mentoring); self-directed learning (technical reading and private study relevant to your discipline); and professional service (committee work, peer review, and contributions to engineering bodies). Label each entry in your CPD list by one of those four categories alongside the title, date, and duration in hours.
The biggest trap is not under-documenting but over-documenting. Engineers Australia’s 8-type, 150-hour CPD framework, the one with capped hours for workplace learning and private study, applies to Chartered status, not to migration assessment. For your CDR, you do not need 150 logged hours or a type breakdown beyond the four categories above; you need a tidy one-page list. If you have read our note on the CRR skill assessment, the same principle holds: document what the specific pathway asks for, and nothing more.
The CDR Introduction Section: Purpose and Length
Separate from each episode’s own introduction, some applicants add a short overall introduction to the CDR that sketches their engineering background and frames the three episodes. It is optional, and where used, it should stay brief, roughly 300 to 400 words. Treat it as orientation for the assessor, not a fourth career episode. If it starts making competency claims of its own, cut it back; those claims belong in the episodes, where they can be paragraph-numbered and cross-referenced.
Formatting Rules Assessors Check First
Before an assessor engages with your engineering, the file has to clear a formatting pass. These checks are fast, mechanical, and unforgiving.
File Format, Font, and Margins
Submit as a PDF, on A4, in Times New Roman or Arial at 11 or 12 point, with standard margins and consistent spacing. Keep the CV to three pages at most. Inconsistent fonts or spacing across sections can read as text pasted from multiple sources, which is exactly what plagiarism screening is tuned to notice.
Referencing, Plagiarism, and Language
Write in Australian English throughout. Every submission goes through Turnitin, and content lifted from online samples, template banks, or another applicant’s report leads to rejection, sometimes with an integrity flag that follows you. Reference any external technical material you drew on, and keep the writing your own from the first line.
Six Formatting Errors That Trigger a Revision Request
These are the structural mistakes that most often bounce a CDR back before its content is assessed:
1. Bullet points in a career episode. Episodes must be continuous prose; convert every list back into numbered paragraphs.
2. Writing in “we” instead of “I”. Team voice erases the personal contribution the assessment exists to verify.
3. Career episodes outside the 1,000 to 2,500 word range. Too short reads as thin evidence; too long dilutes it.
4. Unnumbered paragraphs. Without 1.1, 2.4-style numbering, the summary statement has nothing to point to.
5. Charts, tables, or photographs inside episodes. Heavy visuals and long calculations belong in an appendix, not the narrative.
6. Wrong file type or occupational template. A Word file, or a summary statement built on the wrong ANZSCO standard, fails the format check outright.
Common Questions About CDR Word Count and Formatting
Does Engineers Australia Set a Strict Minimum for Career Episodes?
Yes. Each career episode must reach at least 1,000 words, with no discretion below that. An episode under the floor typically draws an insufficient-evidence finding, because the assessor cannot map enough distinct engineering activity to the competency indicators.
Can a Career Episode Run Longer Than 2500 Words?
You can, but you should not. The 2,500-word ceiling is the published limit, and exceeding it rarely causes outright rejection while reliably weakening the episode. The extra length almost always comes from project or team context, which pushes your personal contribution into the background.
How Many Words Per Competency Element in the Summary Statement?
Budget roughly 60 to 90 words, or 2 to 4 sentences, per indicator. Across the 18 Professional Engineer elements, that totals about 1,500 words. Ignore the 100-word figure circulating on some mistakes pages; it is an error inconsistent with every detailed source.
Does EA Accept CDRs as Word Documents, or Only as PDFs?
Submit as a PDF. Engineers Australia expects the final CDR in PDF form, and a Word document can fail the format check before assessment begins. Draft in Word if you like, then export to PDF for upload.
Do Career Episode Word Limits Include Headings and Subheadings?
Yes. Count everything inside the episode toward the 1,000 to 2,500 range, including headings, subheadings, and paragraph numbers. Because the difference is small, do not try to game the count with heading length; write to the substance and the total takes care of itself.
What If Two Career Episodes Describe the Same Industry?
Same industry is fine; the same project is not. Your three episodes can all sit in, say, structural engineering, provided each demonstrates different competencies through a distinct project and role. What draws scrutiny is repeated or overlapping evidence, which ties back to whether your episodes are aligned with your nominated occupation. Vary the engineering activity, not just the setting.
Before you draft your first career episode, walk through our annotated CDR sample to see these word count and structure rules applied to a real engineering project.