You have written three career episodes. The engineering is sound, the projects are real, and the English is clean. Then the assessor returns a negative outcome, because your Summary Statement points element PE2.3 at a paragraph that never describes a design decision. Knowing how to map EA competency elements is what separates a CDR that reads well from one that survives assessment. This guide walks you through a four-step process to trace each engineering activity in your career episodes to the correct Stage 1 sub-element code, then write an evidence statement an assessor accepts. It assumes you can already do the engineering. What it fixes is the mapping.
Why Competency Element Mapping Determines Your Assessment Result
Mapping is the join between your narrative and the standard. Your career episodes prove you did the work; the Summary Statement names which of the 16 Stage 1 elements your work satisfies, paragraph by paragraph. If that claim is wrong, the strongest engineering career still fails, because the assessor scores the map, not your reputation.
What EA assessors check when reviewing a mapped element
For each mapped element, an assessor follows your cross-reference to the cited paragraph and checks one thing: does that specific sentence show you performing engineering, or does it only describe the project? A paragraph that sets the scene, budget, and team but never shows your reasoning does not satisfy the element it points to. A single blank element, left undemonstrated anywhere across the three episodes, is sufficient on its own for a negative outcome. Mapping accuracy is not a polish task, it is the pass condition.
The 16 EA Stage 1 Competency Elements You Map Against
Every competitor guide stops at the three broad groups. Assessment happens one level down, at the sub-element. There are 16 of them. The names below summarise the Engineers Australia Stage 1 Competency Standard as reproduced in the Migration Skills Assessment (MSA) booklet, which is the authoritative definition source. Treat the wording here as a working guide rather than the current official text: Engineers Australia updates the MSA booklet and the Professional Engineer Summary Statement template periodically, so verify every element definition against the current version at engineersaustralia.org.au before you submit.
PE1 Knowledge and Skill Base: PE1.1 to PE1.6
Code | Focus area | Evidence that satisfies it | Assessor signal phrase |
|---|---|---|---|
PE1.1 | Underpinning natural sciences and engineering fundamentals | Applying first-principles theory to a real problem | "I applied the fundamental principles of..." |
PE1.2 | Mathematics, numerical analysis, statistics, computing | A calculation, model, or statistical method you ran | "I used numerical modelling to determine..." |
PE1.3 | Specialist body of knowledge in your discipline | An advanced, discipline-specific technique | "Drawing on specialist knowledge of geotechnics..." |
PE1.4 | Knowledge development and research directions | A literature or standards review that shaped a decision | "I reviewed current research and codes to..." |
PE1.5 | Contextual factors impacting the discipline | Accounting for human, business, or international context | "I considered the commercial and regulatory context..." |
PE1.6 | Norms, accountabilities, and bounds of practice | Working within scope, codes, and sustainability limits | "I recognised the limits of my authority and applied..." |
PE1.3 is defined as in-depth understanding of a specialist body of knowledge within your discipline, such as geotechnics, power systems, or a manufacturing process. PE1.4 asks for demonstrated awareness of current advances and the ability to search, identify, and apply technical literature. PE1.5 carries several contextual indicators covering human factors, business management, and international practice.
PE2 Engineering Application Ability: PE2.1 to PE2.4
Code | Focus area | Evidence that satisfies it | Assessor signal phrase |
|---|---|---|---|
PE2.1 | Established methods on complex problems | Problem identification plus method selection | "I identified the problem and selected [method] because..." |
PE2.2 | Engineering techniques, tools, resources | Fluent use of named software or analytical tools | "I used PLAXIS to..." |
PE2.3 | Systematic synthesis and design processes | Generating and evaluating design alternatives | "I developed and compared design options, then selected..." |
PE2.4 | Conduct and management of engineering projects | Planning, scheduling, risk, and resource control | "I planned the work, managed the schedule and risks, and..." |
PE3 Professional and Personal Attributes: PE3.1 to PE3.6
Code | Focus area | Evidence that satisfies it | Assessor signal phrase |
|---|---|---|---|
PE3.1 | Ethical conduct and accountability | A described ethical dilemma or accountability decision | "I faced a conflict between... and resolved it by..." |
PE3.2 | Communication in professional and lay domains | Reports or presentations to distinct audiences | "I prepared a report for... and presented to..." |
PE3.3 | Creative, innovative, pro-active demeanour | Challenging or improving a professional practice | "I proposed a change to our standard practice..." |
PE3.4 | Professional use and management of information | Managing records, data, and version control | "I managed and controlled project documentation..." |
PE3.5 | Orderly self-management and professional conduct | Prioritisation, deadlines, ongoing development | "I organised my priorities to meet..." |
PE3.6 | Effective team membership and leadership | Collaboration, or leading a team to an outcome | "I coordinated the team to..." |
Step 1: How to Map EA Competency Elements from Your Career Episode
Mapping is evidence extraction, not decoration. You are not deciding where to sprinkle element codes. Read what you already wrote, sentence by sentence, and ask what engineering competency each sentence proves.
Telling a PE1 knowledge claim apart from a PE2 application moment
Hold one distinction firmly, because most mismaps start here. PE1 is what you understood; PE2 is what you did with that understanding on a complex problem. "I understood the soil behaved as a strain-softening material" is a PE1.3 knowledge claim. "I selected an effective-stress analysis because the soil was strain-softening" is a PE2.1 application moment. Same subject, different competency. Sentences that state knowledge land in PE1. Sentences that state a decision or action driven by that knowledge land in PE2.
Annotating your draft to surface element evidence before you map
Print the episode. Read each paragraph and write in the margin the single engineering thing you actually did there: analysed, selected, calculated, coordinated, resolved. Colour-code by group: PE1, PE2, PE3. Only after every paragraph carries a plain-language activity note do you assign sub-element codes. Mapping onto raw prose invites you to claim elements the text does not support.
Step 2: Assign a Specific Element Code to Each Activity
Worked example: mapping a structural analysis task to PE1.3 and PE2.1
Take this paragraph, numbered CE2.14 in the episode:
> "To assess the stability of the proposed 9 metre cut, I applied limit equilibrium analysis using the Morgenstern-Price method, drawing on my specialist knowledge of soil shear strength under drained and undrained conditions. I found that the existing borehole data underrepresented a weak clay seam, so I specified additional cone penetration testing before finalising the factor of safety."
Two distinct competencies live in those two sentences. The first sentence, your command of drained and undrained shear-strength behaviour, is knowledge: it maps to PE1.3. The second sentence, spotting inadequate data and choosing a method to close the gap, is application: it maps to PE2.1.
Write one evidence statement per element, each pointing to the same reference:
PE1.3 (CE2.14): "I applied in-depth geotechnical knowledge of drained and undrained shear strength to select an appropriate limit equilibrium method for the slope stability assessment."
PE2.1 (CE2.14): "I identified that borehole data underrepresented a weak clay seam and specified cone penetration testing to resolve the uncertainty before finalising the factor of safety."
One paragraph, two elements, two separate sentences doing the work. That is the mapping logic competitor pages describe but never show.
Choosing between two element codes when an activity fits both
Two pairs cause most of the trouble. PE1.3 against PE2.1: if the sentence proves what you knew, code it PE1.3; if it proves how you attacked the problem, code it PE2.1. PE2.3 against PE2.4: PE2.3 is design synthesis, generating and choosing between conceptual options; PE2.4 is project conduct, covering planning, scheduling, and managing risk and resources. A Gantt chart and a risk register belong under PE2.4. Three foundation concepts weighed against serviceability limits belong under PE2.3. When an activity genuinely spans both, split it into its two verbs: cite the design decision under PE2.3 and the management action under PE2.4, rather than citing the whole paragraph twice.
Step 3: Write a One-Sentence Evidence Statement Per Element
An evidence statement that addresses an element has three parts: the engineering activity you performed, the reasoning that made it an engineering judgment, and the outcome. Drop any part and the assessor reads it as a mention, not an address.
What addressing PE2.3 looks like versus mentioning design work
Mentioning: "I applied a systematic design synthesis process on the project." That paraphrases the element definition back to the assessor and proves nothing. It names the competency instead of demonstrating it.
Addressing: "I generated three foundation options (shallow raft, piled raft, bored piles), compared them on predicted differential settlement and cost, and selected the piled raft because it kept settlement within the project's serviceability limit." Activity, reasoning, outcome, all present. The first sentence could sit under any element. The second could only be PE2.3.
Step 4: Cross-Check Your Map Against the MSA Booklet
With every element mapped, run one pass with the MSA booklet element definitions open beside your map. For each of the 16 codes, check whether at least one episode carries a real, addressed evidence statement. Blanks fail silently, so finding them now costs you an afternoon; missing them in submission costs you the assessment.
Finding PE1.4, PE1.6, and PE3.3 gaps before your assessor does
Three elements go missing most often, because engineers do not recognise their own work as documentable. PE1.4 needs evidence that you searched and applied technical literature or tracked how a standard evolved; a design or research engineer usually did this and simply did not write it down. PE1.6 needs recognition of the bounds of practice: where your authority ended, which code governed, what you escalated. PE3.3 is misread constantly, a pattern covered in the errors below. If any of these three is blank, go back into the episodes and surface the sentence that already proves it.
Four Mapping Errors That Get a CDR Flagged
1. Assigning PE3.3 to technical innovation. A clever new analysis method is engineering application and belongs in PE2. PE3.3 asks for a pro-active improvement to how your team or profession works: challenging a standard practice, initiating a better process. Fix it by moving the technical cleverness to PE2 and finding a genuine practice-level initiative for PE3.3.
2. Mapping PE2.3 with no design output stated. Pointing PE2.3 at a paragraph that discusses design in general, with no option generated or selected, is a mention. Fix it by citing the specific sentence where you chose between alternatives.
3. Leaving PE1.4 and PE1.6 unmapped. These are the two most common blanks in rejected CDRs. Fix them by mining your episodes for a literature or standards review (PE1.4) and a scope or accountability limit you observed (PE1.6).
4. Mapping PE3.1 to code compliance. "I followed the code of ethics" is not evidence. PE3.1 needs a described situation: a conflict of interest, a safety-versus-schedule tension, an accountability call, and how you resolved it. Fix it by narrating the actual dilemma.
Turning Your Element Map into the Summary Statement
Your completed map already is the Summary Statement in draft. Each row is one element, one evidence statement, and one cross-reference such as CE2.14. Transfer them straight into the table. The one rule that catches people: when a single paragraph feeds two elements, each element still needs its own distinct sentence or clause, not a shared citation of the whole paragraph. If two elements point to identical text, one of them is unaddressed, and you have found a gap while you still have time to close it.
For a full walkthrough of how evidence statements translate into the table format, see the Engineers Australia Summary Statement guide or revisit your career episode drafting notes to surface any activities you may not have recorded.
FAQs
Do I need to address every one of the 16 Stage 1 competency elements in my CDR?
Yes. All 16 sub-elements must be demonstrated at least once across your three career episodes and cross-referenced in the Summary Statement. A single blank element is enough for a negative outcome, so complete coverage is not optional.
Can a single career episode paragraph address more than one competency element?
Yes, and strong paragraphs usually do. Each element must point to a distinct sentence or clause showing that specific competency. The worked example above maps one paragraph to both PE1.3 and PE2.1 using a separate sentence for each.
What is the difference between PE1, PE2, and PE3 competency element categories?
PE1 is your knowledge base: what you understand. PE2 is engineering application: what you did with that knowledge on complex problems. PE3 covers professional and personal attributes, including ethics, communication, initiative, information management, self-management, and teamwork. Mapping happens at the sub-element inside each group, not at the group level.
How do I know if I have addressed an element sufficiently rather than just mentioned it?
Check for three parts: the activity you performed, the engineering reasoning behind it, and the outcome. A statement that paraphrases the element definition or only names the competency is a mention. A statement that shows a decision only you could have made and records what resulted is an address.
Which Stage 1 competency elements are hardest to demonstrate for design or research roles?
PE1.6 and PE3.3 produce the thinnest evidence for these roles. A focused design or research engineer rarely narrates the bounds of practice PE1.6 asks for, and technical innovation often reads as PE2 rather than the practice-level improvement PE3.3 requires. PE3.1 can also run thin when the work involved no clear ethical or accountability decision. Surface these deliberately rather than hoping the assessor infers them.