If you’re an engineer planning to migrate to Australia through the skilled migration pathway, chances are you’ve come across the term CDR — Competency Demonstration Report. For engineers who don’t hold a Washington Accord-recognised qualification, the CDR is the primary way Engineers Australia (EA) assesses whether your skills and experience meet Australian professional engineering standards.
This guide breaks down exactly what a CDR report is, what it must include, and how to write one that gives you the best possible chance of a positive outcome.
What Is a CDR Report?
A CDR is a formal documentation package submitted to Engineers Australia as part of a skills assessment for migration purposes (used for visa subclasses like 189, 190, and 491). It demonstrates that your engineering knowledge, technical ability, and professional conduct align with the competency standards set for your nominated occupational category — whether that’s Professional Engineer, Engineering Technologist, or Engineering Associate.
Unlike a resume or academic transcript, a CDR tells the story of how you applied engineering principles in real projects, using EA’s specific competency framework as the lens.
Core Components of a CDR
1. Continuing Professional Development (CPD) Statement
A record of the professional development activities you’ve undertaken to keep your skills current — training, courses, conferences, or self-study — typically covering the last three years.
2. Career Episode Reports (CERs)
Three separate reports, each 1,000–2,500 words, describing a distinct engineering project or work experience. Each episode should be broken into an introduction, background, personal engineering activity, and summary, and should clearly demonstrate individual contribution rather than team achievement.
3. Summary Statement
A table that maps specific paragraphs from your Career Episodes to each competency element required by EA for your nominated category. This is often the most scrutinised document, since it’s where assessors quickly check that every competency has supporting evidence.
4. Resume/CV
An updated, chronological account of your education and employment history.
Common Mistakes That Lead to Rejection
- Vague or generic descriptions that don’t show personal technical contribution
- Mismatched competencies — claiming skills your Career Episodes don’t actually demonstrate
- Plagiarism or templated content — EA uses similarity-checking software, and even paraphrased “sample” content can be flagged
- Inconsistent details between your CDR, resume, and other supporting documents
- Wrong occupational category — choosing an ANZSCO code that doesn’t match your actual work history
Tips for Writing a Strong CDR
- Use a STAR-style structure (Situation, Task, Action, Result) within each Career Episode to keep your writing focused and evidence-based.
- Write in first person, past tense, and use active voice — “I designed,” “I calculated,” “I supervised” — to make your individual role unmistakable.
- Be specific with technical detail. Mention the standards, codes, software, or methods you used, not just the outcome.
- Map competencies as you write, not after. Keep EA’s competency elements open in another window and check off each one as you describe your work.
- Get an independent review before submission. A fresh set of eyes — ideally familiar with EA’s current guidelines — will catch inconsistencies and weak competency mapping that are easy to miss in your own writing.
Final Thoughts
A well-written CDR isn’t about impressive language — it’s about clear, honest, competency-mapped evidence of your engineering experience. Take the time to plan each Career Episode around real projects, be specific about your individual contribution, and cross-check every claim against EA’s competency standards before you submit.