How to Write a CDR for Engineers Australia

What is a CDR and why is it hard?

The CDR (Competency Demonstration Report) is the set of documents you write yourself to demonstrate your engineering competency against the Engineers Australia standard. It is not a CV or an employment history — it is evidence of engineering competency presented in a specific structure that EA prescribes.

The CDR is challenging for two reasons: (1) you have to write about your engineering work in English against a competency standard you have never formally studied; and (2) EA reviews submissions closely — reports that are vague, generic, or that describe a management role while you have claimed to be a technical engineer can be refused or returned for revision.

CDR structure

A complete CDR has three components:

1. Continuing Professional Development (CPD)
2. Three Career Episodes (CE1, CE2, CE3)
3. Summary Statement

These three parts are linked: the Career Episodes are where you tell your engineering story, and the Summary Statement is the table that links each competency to a specific paragraph in your CEs.

Continuing Professional Development (CPD)

The CPD is a list of the learning and professional development activities you have undertaken over the most recent 5 years. The usual format is a table with four columns: date, activity name, duration, and impact on your competency.

Valid CPD activities include:

• Courses, workshops, and webinars on engineering topics
• Reading engineering journals, standards, and design guides
• Presenting papers or attending conferences
• Self-study of new engineering software
• Working on projects with a new learning element

EA does not prescribe a specific total number of CPD hours for the MSA, but a list that is too short (fewer than 5–10 items) will be assessed as inadequate. Aim for 20–40 items across a variety of activity types.

Career Episodes: structure of each episode

Each Career Episode (CE) describes a specific project, period of work, or engineering task you took part in. The three CEs should be drawn from different stages of your career to show your development.

Required structure of each CE:

Introduction: Name of the organisation, your position, dates, location, and the project context. About one paragraph.

Background: A description of the organisation, the project, its engineering objectives, and your role within the team. About one to two paragraphs.

Personal Engineering Activity: This is the longest and most important section. It must describe what you personally did — not the team, and not the project in general. Use the pronoun “I” and be specific: what you calculated, what you designed, which engineering problem you solved and how.

Summary: Results, lessons learned, and your personal contribution. About one paragraph.

Length: EA recommends 1,000–2,500 words per CE. In practice, 1,500–2,000 words is common.

Summary Statement: the part that decides the outcome

The Summary Statement is a table that links each EA competency element to a specific paragraph in your Career Episodes, using a reference such as “PE1.1” (Career Episode 1, paragraph 1) or similar.

EA provides a ready-made template for each occupational category (Professional Engineer, Engineering Technologist, and so on). You complete each cell in this table, pointing to the exact paragraph you wrote in your CEs.

Common mistake: Filling in the Summary Statement before writing the CEs. The correct order is: (1) write the CEs and number the paragraphs, then (2) complete the Summary Statement. If a CE does not contain enough content to point to, you have to revise the CE — you cannot simply adjust the Summary Statement.

Choosing suitable projects for Career Episodes

Criteria for a strong CE:

• You had a clear personal engineering role (not a purely coordinating or management role)
• The project was complex enough to demonstrate the competency elements (calculation, design, problem solving, risk assessment)
• You can describe it in detail in English — a small project you know thoroughly is better than a large one you describe vaguely
• The three CEs cover different stages: for example CE1 (early career), CE2 (mid-career), CE3 (recent)

What to avoid:

• A CE that describes managerial, supervisory, or administrative work — EA wants to see engineering activity
• A CE that is too short or lacks specific engineering detail
• Three CEs with the same content or all drawn from a single project
• Using “we” instead of “I” — it then is not clear what you personally did

Writing in English in the CDR

The CDR must be written in English. EA checks grammar and consistency — writing that is unusually stiff, or that contains many grammatical errors, can raise questions about authenticity.

An English score is not a direct criterion in the MSA (the English requirement applies at the visa stage), but EA needs to be able to understand the engineering content you have written. Some applicants use a proofreading service after they have written the engineering content — this is acceptable, provided the content remains your own.

Warning: Using a service to write your CDR entirely for you (ghostwriting) breaches EA policy and can lead to a permanent ban from submitting. EA has mechanisms to detect reports that were not written by the applicant.

Realistic order and timeline

1. Weeks 1–2: Choose three projects and outline the content of each CE
2. Weeks 2–6: Write the three CEs (each CE may take 1–2 weeks if you are new to the format)
3. Weeks 6–7: Write the CPD list
4. Weeks 7–8: Complete the Summary Statement and cross-check it against the CEs
5. Weeks 8–9: Review the whole report and correct the grammar
6. Weeks 9–10: Prepare supporting documents (qualifications, transcripts) and submit

Total preparation time for a first CDR: 2–3 months is realistic. Applicants who already understand the structure may complete it in 4–6 weeks.

If EA requests further information or refuses your application, see the guide on what to do when an Engineers Australia assessment is refused.