The 16 Stage 1 Competencies, Explained With Real Evidence

Engineers Australia publishes one Stage 1 standard per occupational category. All follow the same three-group structure, and the element numbers carry a prefix naming your category:

• PE — Professional Engineer
• ET — Engineering Technologist
• EA — Engineering Associate

PE1.3 and ET1.3 address the same theme at different depths. Use the prefix matching the category you are applying under. A summary statement full of PE labels in an Engineering Technologist application tells the assessor you wrote to the wrong standard before they read a single episode.

The three groups are not equally weighted in practice. Knowledge elements are relatively easy to evidence, professional attributes are easy to evidence and easy to fumble, and the four application elements are where reports are won or lost.

PE1.4 is the one most often left bare, because it sounds academic. It is not. Every engineer has looked something up they did not already know — a standard newly issued, a method unfamiliar to them, a technical paper consulted for an unusual problem. Write that down.

These four are the heart of the assessment.

PE2.3 is the element that fails reports. Applicants from construction, maintenance and operations backgrounds frequently have no episode containing a design they personally developed. If that describes you, find one before submitting — temporary works, a design change you proposed, a university project. It does not have to be large. It has to be yours.

PE2.2 has a subtlety worth noting: the phrase is fluent application with judgement. Running ETABS is not evidence. Running ETABS, hand-checking the result, and finding a 4% difference that told you the mesh was adequate — that is evidence.

These are easy to evidence and easy to get wrong. The failure mode is asserting rather than showing.

Asserted: "I have excellent communication skills and always maintained the highest ethical standards."

Shown: "During factory acceptance testing I found the hydrostatic test certificate referenced a different serial number from the vessel delivered. The programme was two weeks late and the site manager asked whether it could be accepted pending paperwork. I declined, documented the discrepancy, and required a witnessed re-test under AS 1210. The re-test passed and delivery slipped four days."

Ethics is demonstrated by a decision that cost something. So is proactivity. So is communication — the specific report you wrote, the specific meeting where you translated a technical constraint into commercial language.

Build a grid: sixteen rows, three columns. Before drafting a word, mark which episode will carry which element.

You are checking two things. Full coverage — every element ticked at least once. And reasonable distribution — no episode left carrying two or three elements while another carries eleven.

Then write to the plan. Moving an element from episode two to episode three on a planning grid takes a minute. Discovering after 6,000 words that all three episodes demonstrate the same five elements costs a rewrite.

This is also the difference between a summary statement that is built and one that is retrofitted. A retrofitted summary statement is where broken paragraph references come from — the writer needed PE1.4 somewhere, and pointed at the closest paragraph rather than one that actually demonstrates it. Assessors check.

Two rules that resolve most confusion:

Coverage is across all three episodes combined. No single episode needs all sixteen elements. Each element needs to appear at least once, somewhere, referenced to a specific numbered paragraph.

References point at paragraphs, not pages. Your summary statement cites 1.7, 2.11, 3.4 — the numbered paragraphs inside your episodes. That is why the MSA booklet requires continuous paragraph numbering within each episode, and why an unnumbered episode cannot be assessed.

One element referenced three times across three episodes is stronger than one referenced once, but breadth beats depth here: an unevidenced element is a direct route to a negative or deferred outcome, while a thinly evidenced one usually is not.

If you have already written your episodes and want to know where you stand, our CDR review audits coverage element by element and verifies every reference against the paragraph it points at.

Applicants sometimes read about Stage 2 competencies and worry they are being assessed against them. They are not — but knowing the difference is useful, because Stage 2 is where you will end up later.

The practical sequence for a migrating engineer is Stage 1 for the visa, then Australian experience, then Stage 2 for registration once you have local evidence that referees can attest to. Attempting Stage 2 before you have that evidence is the common mistake.

Worth knowing now rather than later: the CPD record you build for your CDR is the beginning of the record Stage 2 will require, so keep it properly from the start.