If you are an engineer planning to migrate Australia, your work history may be a key component of your skills assessment. But don't think that a few years of engineering experience will automatically lead to a clear Competency Demonstration Report (CDR) that clearly shows the competencies required by Engineers Australia (EA).
The problem is, how to explain your engineering work in a way that reveals your technical knowledge, decision making, problem-solving and professional responsibility. Your project description may be mostly about what your employer did, but it may not address the following questions: What did you do? What engineering principles did you use? What was the reason for selecting the specific solution? What did you find out about the results?
The important thing to remember is to correlate real-life project experience with the corresponding element(s) of the EA and provide evidence from the project to substantiate each claim. You will describe your individual engineering acts in your Career Episodes and you will identify where the required competencies are evidenced in your Summary Statement.
Engineers Australia evaluates Migration skills applications in various ways. Applicants seeking to be assessed through the CDR pathway must prove that their skills and experience in engineering is relevant to their nominated occupation and the relevant assessment requirements.
In this guide, we will explain how to pick relevant engineering projects, match your experience with the competency elements, put together a good engineering technical example, and how to prevent common CDR errors. We also demonstrate how civil, mechanical and electrical engineers can team up to present a better evidence-based evaluation application.
Engineer Australia is the Authority for engineering migration skills assessment. The assessment pathway will be determined based on your qualifications and nominated occupation and can vary, please check the pathway you need to follow before you prepare your documents.
Applicants on a CDR route are not required to submit competency evidence that is just a list of responsibilities copied from a CV. You will have to show how your engineering knowledge and skills were used in your studies or your work.
So writing, “I was responsible for the design of a commercial building” provides the reader with information about your role, but not the engineering decisions you made. A more complete account would explain the limitations of the design, calculations made, alternatives considered, standards to be met and checks carried out.
The competency framework for the nominated occupational category is to be used. Engineers Australia also have competency standards for the professional engineering, engineering technologists and engineering associates. There are distinct expectations for each of these categories, and applicants are expected to use appropriate official standards and Summary Statement template for each assessment.
The competency elements are grouped into three general areas for a Professional Engineer applying under the appropriate Stage 1 competency level.
These are general descriptions and are not meant to replace the competency language. Apply the standards of your nominated occupational category to mapping Career Episodes.
🌟 Verify CDR Need: Confirm if your occupation requires a Competency Demonstration Report. Check CDR Requirements
Selection of appropriate projects is one of the key points in preparation of a CDR. A big project doesn't always make a good Career Episode. If you can show your technical reasoning and individual contribution in a sufficient amount of detail, a smaller project might be a better evidence.
First, check out projects from your job, engineering courses, supervised projects or any experience you may have that is relevant to your application. Review each project with the competency elements you must demonstrate.
Seek out projects that involved a problem, choice, weighing of an alternate or enhancement of a current system.
Examples could be:
The project need not be won an award or achieve outstanding commercial savings. The important thing is that you are able to explain the problem of engineering, your contribution and why you did what you did.
Teams of multidisciplinary engineers are involved in many engineering projects. This is a normal situation but your Career Episode should document work in a way that makes it clear how it contributes to the team's successful work. Look at the two descriptions and compare:
Too broad: "We developed a wastewater treatment plant and delivered the project within the budget.
More informative: “I estimated the volume of wastewater produced and match this against the design requirements and determined that the initial pump selection did not have sufficient operating margin, I made a note of this and consulted with the project engineer for an alternative pump selection.”
Second example describes what the applicant did and how he/she did it technically. Use only information which reflects your own experiences and which you can substantiate.
Before choosing a project, ask yourself:
If the work content of a project is primarily administrative, the project may demonstrate a limited technical engineering skill. The engineering activity might be clearer in another project or you can use part of that experience if relevant, but it may be preferable to have a project with a more clear engineering activity.
After you have identified your potential projects, fill in a competency mapping table. This will help you determine the project that will have evidence for each element before you begin writing the Career Episodes.
Don't restrict all competencies to all projects. Instead, instead, present a collection of evidence for your category from the episodes you have gathered.
A possible arrangement of project evidence for a Professional Engineer is shown in the table below. It is a worked example – it is not a substitute for Engineers Australia's Summary Statement.
| Competency area | Evidence to look for | Possible project example |
|---|---|---|
| PE1: Engineering knowledge | Principles, technical theory, calculations and methods | Structural load calculations or motor selection |
| PE1: Specialist knowledge | Knowledge specific to the nominated engineering discipline | Hydraulic analysis or electrical protection design |
| PE2: Problem analysis | Identification of constraints, investigation and evaluation of alternatives | Investigating repeated pump failures |
| PE2: Solution development | Design decisions, testing, verification and optimisation | Comparing two equipment configurations |
| PE2: Engineering context | Safety, environmental, economic and operational considerations | Evaluating drainage alternatives with environmental constraints |
| PE3: Communication and teamwork | Technical reporting, coordination and explanation of decisions | Presenting a design change to a project team |
| PE3: Professional responsibility | Ethical judgement, safe practice and accountability | Escalating an unsafe design assumption |
| PE3: Self-management and development | Planning, prioritisation, reflection and learning | Managing design revisions and documenting lessons learned |
The actual number of elements and the language used needs to be from the competency standard appropriate to your nominated category. Your Summary Statement should be prepared in the required format and refer to specific paragraphs in your Career Episodes that illustrate the elements.
There are simple ways to arrange your evidence in a simple spreadsheet before you start writing.
| Column | What to record |
|---|---|
| Competency element | The official element number and wording |
| Project | The project or experience that demonstrates it |
| Your action | What you personally did |
| Technical evidence | Calculations, analysis, standards, testing or decisions |
| Career Episode | The episode in which you explain the work |
| Paragraph reference | The exact numbered paragraph that provides the evidence |
| Evidence gap | What needs clarification or further development |
This exercise is useful to detect missing evidence at an early stage. It also minimizes the chance of finishing the Career Episodes and realizing that there is an important competency that has not been sufficiently captured.
💯 Pass EA Assessment: Submit your Career Episodes based on these projects to Engineers Australia. EA Assessment Guide
Career Episodes will provide you with a space to describe your use of engineering knowledge in a particular context. The intention of a well organised episode is to give the reader enough information to understand the project, but to not overwhelm him/her with information and to give enough attention to his/her engineering activity.
Engineers Australia offers specific advice on preparing Career Episodes and the Summary Statement. Please adhere to the current official guidelines for the prescribed format and your assessment pathway.
Introduce the project, the time frame, the place, the organisation / educational setting and your role at the project. The introduction should set the scene and should not employ too much space in the company's history.
For example:I worked from March to August 2025 as a graduate mechanical engineer on an industrial project designed to improve the cooling system, which involved studying operational information, analysing temperature variations, and assessing potential modifications to the cooling system.
Use your actual project details and responsibilities. The example is illustrative.
Explain the problem the project was to solve and the technical requirements and constraints that affected your project.
For example, An industrial cooling project could include an inconsistent outlet temperature, limited installation space, energy consumption goals and restrictions on production downtime.
Only describe what is needed for the person to understand what you did. You will not be demonstrating your personal engineering skills with a lengthy company description.
This is the most crucial element of the story. Describe the steps you followed, how you did it, what choices you made and why.
A useful sequence is:
Don't make this part of a day log. Each paragraph should contribute to the demonstration of engineering knowledge, problem solving or engineering judgement.
Describe the consequences of your intervention. Use appropriate measures, test results or documented outcomes from actual projects where you have actual project records.
For example, you could write and explain that you had a vibration problem and changed the pump type and the operating flow was improved.
Avoid making up percentage, savings, test scores, project results etc. to make the episode look good. If the result was inconclusive, discuss what you learned and what more you would need to confirm.
When using the Career Episodes, evidence is mapped to the Summary Statement with the help of paragraph numbers. Follow the format set out in the current official guidance and keep references when editing document.
Verify that the paragraph in which each competency element is mentioned includes evidence of that competency element's skills, rather than just the topic.
Just because a list of tasks exists doesn't necessarily mean that competency exists. The reasoning and how it related to your decisions should be in your account.
Consider the difference between these two descriptions.
Task-based description:
"I performed structural calculations, prepared drawings, and attended design meetings."
Reasoning-based description:
Examined initial column layout and determined that the proposed column locations were inconsistent with the architectural layout; compared the various framing alternatives, considered the load transfer and constructability implications of each framing option, and discussed the selected option with the appropriate project team and updated the drawings accordingly.
The second description provides the reader with a better understanding of the engineering problem and the response to it.If you have to write your own account use a simple sequence:
Not all engineering activities will need all the steps in the same level of detail. The sequence is a practical choice of how to make sure that your narrative is sufficiently technical.
Your Career Episodes link to the competency elements for your nominated occupational category in the Summary Statement. Should not make unsupported claims or just restate your project summaries.
Rather, it points out the numbered paragraphs in your episodes where the assessor can locate evidence for each competency.
Guidance is available for engineers on preparing Career Episodes and the Summary Statement, published by Engineers Australia. Use the latest version of the template(s) being used.
Now, write paragraph 2.4 of your second Career Episode that describes how you analysed the maintenance records and operating data to understand why pumps were failing so often. Your map could be something like this:
| Summary Statement field | Illustrative entry |
|---|---|
| Competency element | Relevant element concerning engineering problem analysis |
| Career Episode reference | CE2, paragraph 2.4 |
| Supporting evidence | Investigation of operating data and maintenance history, identification of possible causes and evaluation of technical constraints |
| Final check | Ensure that paragraph 2.4 clearly and precisely shows the competency element in the relevant official standard. |
Competency description above is a guide and not an element number or prescribed language. For each occupational category, you need to choose the appropriate element of the template.
If it is not fully supported, add more factual, relevant detail (where possible) to the underlying Career Episode. Avoid using a competency label on a paragraph that fails to show competency.
Even if one is a professional engineer, one can find it difficult to explain one's work. The following errors may make it more difficult for an assessor to recognise the evidence of competency required.
| Common mistake | Why it creates a problem | How to improve it |
|---|---|---|
| Describing the entire team's achievements | Your individual contribution becomes unclear | Explain your own decisions, calculations and actions |
| Writing mainly about routine duties | Responsibilities alone may not demonstrate engineering competence | Describe specific technical problems and how you addressed them |
| Listing calculations without explaining them | The reasoning behind your work is difficult to follow | Explain why you used the method and how you interpreted the results |
| Using the same project evidence repeatedly | Important competency elements may remain inadequately demonstrated | Plan coverage across all three Career Episodes |
| Making unsupported technical claims | The narrative may lack credibility or traceability | Use accurate details supported by your experience and available records |
| Copying another engineer's Career Episode | The account may misrepresent your experience and compromise authorship | Write your own account using your actual project history |
| Incorrect Summary Statement references | The assessor may have difficulty locating the supporting evidence | Check each element against the exact numbered paragraphs |
| Ignoring the nominated occupation | Your evidence may not clearly align with the occupation being assessed | Review the relevant occupational description and assessment requirements |
Reports that have been prepared as examples may provide a good idea of structure; however, copying the language, calculations or project details from another report is not a good indicator of competence. Another engineer might have dealt with other equipment, other constraints, other standards or other responsibilities.
The application must be based on your own engineering experiences and be prepared following the Engineers Australia authorship and application guidelines.
For those who have confidentiality requirements, ensure that sensitive information relating to the client and the employer is protected. The technical challenge can be described with suitably anonymised information and project information, but project information cannot be fabricated and information that is not approved for disclosure cannot be disclosed without permission.
Please use this checklist to work through before you submit your application. The exact requirements will vary from pathway to pathway and person to person and are subject to change, please refer to the application specifications in the current official application as the final reference. Before completing the documents, use this checklist to check if your project is aligned.
This checklist is intended to assist in drafting, not as an assessment checklist. General writing guidelines will be superseded by the following instructions published by Engineers Australia.
👑 Lodge Visa 189 : Claim points for your skills and apply for Permanent Residency. Apply for Visa 189 →
When presenting your experience for engineering projects, you can align your projects with the EA competency elements. It helps you to understand how your technical work relates to the skills needed to work in your nominated occupational category.
The application is strong when it relates the project context, your contribution to the project, your engineering reasoning and appropriate competency evidence. It also ensures consistency between the Career Episodes, Summary Statement, CV and supporting documents.
But you can't ensure the outcome you want in an assessment by how carefully you write it. Applications are assessed by Engineers Australia using the requirements that are relevant to the application and the assessment pathway. Please refer to the official Engineers Australia Migration Skills Assessment page.
Engineers Australia's current application guidance outlines the standard format of a CDR documentation consisting of three written Career Episodes and a Summary Statement. Check the requirements for your assessment pathway before you start to apply..
The competency elements required are to be displayed in the three Career Episodes for the relevant CDR category. Each episode can have evidence for several elements and should be planned accordingly; do not expect each episode to show evidence of each element.
Depending on the assessment requirements and what you actually did, relevant academic engineering projects can be used. Select projects where you can share your engineering knowledge, decisions, methods and contribution to the project. Please refer to the official EA instructions for your pathway.
Yes. Evidence for a competency can be exhibited in multiple projects, such as multiple projects that demonstrate technical analysis, design decisions, risk consideration and communication. The actual content of the Career Episode and the applicable competency words should be included in each mapping.
Summary Statement relates the required competency elements to numbered paragraphs in your Career Episodes. It assists the assessor in finding evidence to demonstrate each competency. It should adequately capture the stories without making unsupported claims.
Be specific about what details are required to tell the engineering contribution. Provide calculations, methods, assumptions, alternatives, and decisions that are relevant to the problem but avoid unnecessary background information and information that does not show competence. The technical details should not distract from the story, but rather give the reader enough information to understand your reasoning.
No service can afford to guarantee an assessment outcome. You can seek professional writing/review assistance to help you to structure your true experience and to identify any gaps, however the decision is to be made by Engineers Australia. The applicant is still responsible for the reliability and correctness of the information he/she supplies.
Understanding assessment pathway, choosing assessment projects that yield meaningful evidence, and articulating a personal engineering contribution clearly are the first steps to aligning engineering projects with EA competency elements.
Create Career Episodes that are based on authentic engineering problems. Demonstrate analysis of problems, application of technical knowledge, evaluation of options, decision-making and checking of outcomes for problems. Then, link that evidence to the appropriate competency elements on the official Summary Statement template.
A well contoured CDR is not just a representation of your career. It is a formal description of your actual engineering experience and evidence of the skills needed for your chosen career. A credible application is built on grounds of accuracy, reasoning and careful cross referencing.
Creating engineering evaluation documents requires more than just being bilingual in English. You must plan your project history and make a clear and concise explanation of the technical decisions you have made and relate your actual experience to the related competency requirements.
WritingAhead.org can be considered if you are looking for assistance with organising engineering project information, improving the clarity of technical writing or reviewing the structure of your assessment documents. Ensure the scope of services offered is as advertised before hiring a provider.
WritingAhead.org Organise your experience into a clear, evidence-based account of your engineering work.
Depending on the services available, ask about support with:
Checking document consistency, structure and language.
Contact: +61 489 995 985 - Please confirm availability, costs and turnaround time directly.
🚀 Struggling to write? Avoid plagiarism bans and ensure your projects are presented perfectly. Find Trusted CDR Writers
Writing or reviewing should maintain your authorship and accuracy of your experience. Avoid handing in fake work and Career Episodes or technical claims that are not supported. Before using an external provider, please refer to Engineers Australia's current rules on authorship and third party assistance. Engineers Australia is responsible for the assessment. No writing service will guarantee a positive skills assessment, migration approval or visa outcome.