CDR Report Format for Engineering Technologist: 2026 Guide

Two Engineering Technologist CDRs can carry near-identical project descriptions and still split on the result: one clears assessment, the other draws an adverse finding. The culprit is rarely the engineering. It is the Summary Statement column headings, where one applicant used ET codes and the other copied a Professional Engineer template carrying PE codes. The CDR report format for engineering technologist applicants is a separate standard, not a lighter edition of the Professional Engineer submission, and Engineers Australia assesses it against its own Stage 1 Competency Standard for Engineering Technologists.

This guide maps the exact document set, the section-level word counts, the ET competency codes, and the Summary Statement mapping rules that decide the outcome. If you already know what a CDR is and want the format precision that most pages skip, start here.

What a Correctly Formatted Engineering Technologist CDR Report Must Demonstrate

Engineers Australia measures an Engineering Technologist against the Stage 1 Competency Standard for Engineering Technologists, a published set of 16 elements grouped as ET1 (Knowledge and Skill Base, six elements), ET2 (Engineering Application Ability, four elements), and ET3 (Professional and Personal Attributes, six elements). Your occupation sits under ANZSCO 233914, unit group 2339, assessed by Engineers Australia. Note that ANZSCO 3120-series codes are a parallel occupational classification used in some visa nomination contexts; if your state nomination or occupation list references a 3120-series code, confirm with the relevant authority whether your application route runs through the CDR pathway or a separate nomination pathway before proceeding.

The threshold that shapes every formatting decision is this: a technologist demonstrates the application of established engineering methods to broadly-defined problems. A Professional Engineer must evidence original analysis, design, and synthesis of complex problems. Format follows threshold. If your document set claims Professional Engineer depth but your evidence sits at technologist level, or the reverse, the mismatch reads as a category error before an assessor finishes the first Career Episode.

One eligibility note before format. If your qualification is a Sydney Accord-accredited three-year technology degree from a signatory country, you generally take the accord pathway rather than the CDR route. The CDR applies when no mutual-recognition agreement covers your qualification. For a full overview of what the Engineers Australia skills assessment involves, including fee and timeline expectations, see our detailed breakdown of Engineers Australia CDR fees for 2026.

The Three Documents That Make Up the CDR

A complete submission is three documents, the same set a Professional Engineer files: a Continuing Professional Development (CPD) list, three Career Episodes, and one Summary Statement. What changes is the standard each is measured against and, critically, the element codes the Summary Statement carries.

CPD list format and minimum requirements

CPD is graded, not a cover-page formality. Present it as a table on a single A4 page with four columns at minimum: activity title, date, duration, and organising body. Every entry must be engineering-relevant, covering technical short courses, conferences, formal study, structured workplace learning, and technical webinars. On minimum hours, be careful: the fixed figures circulating on service sites are not consistently traceable to the current Migration Skills Assessment (MSA) booklet, so confirm the current expectation against Engineers Australia’s own booklet before you finalise the list. The format itself is settled: tabular, one page, four fields, engineering content only.

Three Career Episodes: what Engineers Australia is counting

Each Career Episode narrates one engineering experience, and the assessor is counting your personal contribution, not the project’s headline achievement. A large project with your name buried in a team of forty proves little. A modest task where you selected the method, ran the calculation, and owned the outcome proves a great deal. Write every episode in the first person.

Summary Statement: the document that ties everything to competency codes

Think of your Career Episode paragraphs as an evidence locker and the Summary Statement as the index that tells the assessor which drawer holds proof of each competency. It is one three-column table covering all three episodes, and for an Engineering Technologist it carries ET-coded rows. Submit the PE-coded version and you have signalled, on page one of the mapping, that you assessed yourself against the wrong standard.

How to Structure Each Career Episode for Engineering Technologist

Each Career Episode runs 1,000 to 2,500 words and follows four named sections: Introduction, Background, Personal Engineering Activity, and Summary. Widely published MSA booklet guidance breaks the length down as follows, though remember that Engineers Australia assesses the quality of engineering content, not raw word count.

Introduction and background

The Introduction sets the scene in a few sentences: the dates, the organisation, the project, and your position on it. Keep it tight. The Background then establishes the engineering context, the nature of the work area, the objectives, and your specific duties. Its job is to frame the problem so the reader understands why the technical decisions that follow mattered.

Personal Engineering Activity section

This is the graded core, and it lives or dies on one word: “I”. Every sentence describing engineering work must use a first-person “I” statement. Passive constructions (“the design was completed”) and unattributed “we” (“we selected the pump”) are the leading trigger for adverse Engineering Technologist assessments, because they hide the individual contribution the standard exists to measure. Name the method you applied, the tools you used, the analysis you performed, the problems you solved, and the standards you worked to. Since the technologist threshold is application of established methods, show yourself selecting and applying recognised procedures competently, rather than claiming novel theory you cannot substantiate.

Summary paragraph: what it must confirm

At 50 to 100 words, the closing Summary confirms how your role met the project objectives and what you personally contributed. New claims do not belong here. It restates your engineering ownership so the Summary Statement mapping has a clean anchor to cite.

Engineering Technologist Competency Elements You Must Cover Across the Three Episodes

Here is the reference no competitor page prints in full. The Engineering Technologist standard uses ET-prefixed codes, and your three episodes together must surface evidence for each of them.

ET1 knowledge and skill base elements

Six elements covering the theory base:

• ET1.1: systematic, theory-based understanding of the natural and physical sciences and engineering fundamentals.

• ET1.2: conceptual understanding of mathematics, numerical analysis, statistics, and computer sciences.

• ET1.3: in-depth understanding of specialist bodies of knowledge within the technology domain.

• ET1.4: discernment of knowledge development within the technology domain.

• ET1.5: knowledge of contextual factors impacting the technology domain.

• ET1.6: understanding of the scope, principles, norms, accountabilities, and bounds of contemporary engineering practice.

ET2 engineering application ability elements

Four elements govern what the assessor actually tests in your Career Episodes:

• ET2.1: application of established engineering methods to broadly-defined problem solving within the technology domain.

• ET2.2: application of engineering techniques, tools, and resources.

• ET2.3: application of systematic synthesis and design processes.

• ET2.4: application of systematic approaches to the conduct and management of projects.

Read ET2.1 closely. The phrase “broadly-defined problem solving within the technology domain” is the published boundary line. The equivalent Professional Engineer element, PE2.1, reads “complex engineering problems”. That single language shift, broadly-defined versus complex, defines the gap between the two standards. Write your evidence to “broadly-defined” and you match your grade; overclaim to “complex” original design and an assessor will ask why you did not apply under the Professional Engineer standard.

ET3 professional and personal attributes elements

Six elements, and this is the group applicants consistently shortchange:

• ET3.1: ethical conduct and professional accountability.

• ET3.2: effective oral and written communication in professional and lay domains.

• ET3.3: creative, innovative, and pro-active demeanour.

• ET3.4: professional use and management of information.

• ET3.5: orderly management of self and professional conduct.

• ET3.6: effective team membership and team leadership.

ET3.3 through ET3.6 are routinely left thin because applicants pour every paragraph into technical detail. Fix this at the drafting stage by choosing episodes that naturally surface these attributes. A project where you proposed a process improvement covers ET3.3. Reports, drawings, and client briefings you produced cover ET3.2 and ET3.4. Managing your own deliverables and meeting deadlines cover ET3.5. A coordination or supervisory role covers ET3.6. If none of your three episodes shows these signals, the Summary Statement cannot cite them, and missing ET3 rows read as an incomplete profile.

Building the Summary Statement: Paragraph References Mapped to ET Elements

How to assign CE paragraph numbers to ET element codes

Number every paragraph in each Career Episode. Paragraph four of Career Episode one becomes CE 1.4; paragraph seven of Career Episode two becomes CE 2.7. The Summary Statement then lists each ET element in column one, a brief past or present-perfect summary of how you demonstrated it in column two, and the CE paragraph citations in column three. A completed row looks like this:

Every citation must point to a paragraph that genuinely shows the claimed competency. An assessor who follows CE 2.7 and finds no ET2.1 evidence there will distrust the rest of the map.

How many citations each ET element requires

No official per-element count exists, so treat what follows as a working rule rather than a published quota. Knowledge elements (ET1) are often satisfied with one solid citation per episode, since a single clear demonstration of understanding carries the point. Application elements (ET2) usually need two or three citations spread across different episodes, because consistent application across varied contexts is exactly what the standard tests. Each attribute element (ET3) needs at least one credible citation, and the ET3.3 to ET3.6 group is where thin mapping shows. Wherever an element allows it, aim for evidence drawn from more than one episode.

Engineering Technologist vs Professional Engineer CDR Format: Where the Requirements Diverge

The two submissions share a shape and diverge on the standard. This comparison is our reading of the two published Stage 1 Competency Standards, side by side.

The structural mechanics are identical. The competency language, the code prefix, and the correct template file are not. Engineers Australia publishes a separate ET Summary Statement template; download and use that one, because the PE template’s headings alone can sink an otherwise sound application.

Format Errors That Produce an Adverse Assessment

The recurring format failures are predictable, which means they are avoidable:

• Wrong template. Filing the PE-coded Summary Statement for a 233914 application. The column headings advertise the mistake before an assessor reads a single paragraph.

• Passive and collective voice. “The system was designed” and “we decided” strip out the personal ownership the standard measures. Convert every engineering sentence to “I”.

• Overclaiming to PE depth. Describing routine application of established methods as original design and synthesis invites the question of why you did not apply under the higher standard.

• Missing ET3 evidence. No creativity, communication, self-management, or teamwork signals in any episode means those Summary Statement rows sit empty.

• Broken citations. CE paragraph references that point to paragraphs where the cited competency does not actually appear.

• CPD treated as filler. A non-tabular list, missing columns, or non-engineering activities on a component that is graded.

For the wider set of content and evidentiary slips that trigger rejections, see our guide to common CDR mistakes in an EA skills assessment, and for a full drafting walkthrough, our ten ways to write a perfect CDR.

Frequently Asked Questions

How many career episodes does an Engineering Technologist CDR require?

Three. An Engineering Technologist CDR requires exactly three Career Episodes, the same number as a Professional Engineer submission. Each covers a distinct engineering experience, runs 1,000 to 2,500 words, and must be written in the first person, focused on your personal contribution.

What is the word count for each career episode in an Engineering Technologist CDR?

Each Career Episode runs 1,000 to 2,500 words. Commonly cited MSA booklet guidance splits that into roughly 100 words of Introduction, 200 to 500 words of Background, 500 to 1,000 words of Personal Engineering Activity, and 50 to 100 words of Summary. Engineers Australia assesses the quality of engineering content, not length, so do not pad to reach the ceiling.

How does the Engineering Technologist Summary Statement differ from a Professional Engineer’s?

It carries ET-prefixed element codes rather than PE codes, and it maps to the technologist threshold of “broadly-defined” problem solving instead of the “complex” problem solving the Professional Engineer standard demands. The two standards use separate published templates, and submitting the PE-coded template for a technologist application is itself a format error that can trigger an adverse outcome.

Which ET competency elements must an Engineering Technologist address in the Summary Statement?

All 16: ET1.1 to ET1.6 (knowledge and skill base), ET2.1 to ET2.4 (engineering application ability), and ET3.1 to ET3.6 (professional and personal attributes). Every element needs at least one Career Episode paragraph citation, with the application elements (ET2) typically citing evidence from more than one episode.

Can career episodes cover projects completed outside Australia for an Engineering Technologist CDR?

Yes. Career Episodes may describe engineering work completed anywhere, including projects undertaken entirely outside Australia. Engineers Australia assesses your personal engineering role and how it evidences the ET competency elements, not the project’s location.

Before you submit, confirm the rest of your file is complete: check our Engineers Australia skills assessment document checklist to make sure every supporting document is in order alongside your three-document CDR.