Prepare for the NER assessment by building one evidence bank per competency area rather than one long career story. For each of the six areas, write a short claim, attach a concrete project example, and finish with the judgement or decision that shows engineering maturity. Practise separating overlapping work: a single dam upgrade can feed your risk, communication and technical claims, but each must argue a different point. Use the comparison table and self-check rubric in this guide to test whether each claim would stand on its own, and confirm all administrative requirements directly with Engineers Australia.
How the Six NER Assessment Areas Differ From One Another
Professional ethics, risk and legal compliance, CPD, communication, project management and technical expertise each test a different capability. Treat them as six separate arguments about your practice, each needing its own evidence, not six headings covering the same story.
The overlap is the trap. A single project might involve an ethical constraint, a safety decision, stakeholder negotiations and complex analysis, so a narrative written once and pasted under all six headings will read as generic. Each area asks a distinct question: ethics asks how you chose when values conflicted; risk asks how you identified and controlled hazards; CPD asks how your capability grew by design rather than by accident.
To keep them separate, write each claim as a standalone argument a stranger could verify. The ethics claim needs a decision point; the risk claim needs a hazard, a control and a check; the CPD claim needs a planned learning goal and its application; the communication claim needs an audience and an outcome; the project claim needs scope, resources and trade-offs; the technical claim needs complexity and your specific contribution.
A workable habit is colour-coding: draft your project list once, then mark which competency area each anecdote genuinely serves. Expect your list to skew toward technical work; check whether yours thins out for CPD and communication, because that tells you exactly where drafting time should go.
- Ethics and integrity: conflicts between obligations, and the reasoning behind your choice
- Risk, safety and legal compliance: hazard identification, controls, and applicable Australian frameworks
- CPD: planned learning with a purpose, applied and reviewed
- Communication and stakeholder management: changing what an audience understood or decided
- Project and resource management: scope, budget, schedule and trade-offs you made
- Technical expertise: a problem complex enough to need engineering judgement, and your role in solving it
| Area | Weak claim sounds like | Strong claim contains |
|---|---|---|
| Ethics | "I always act with integrity" | A specific conflict, the options you weighed, and the decision made |
| Risk and compliance | "I follow safety procedures" | A hazard you identified, the control hierarchy reasoning, and how compliance was verified |
| CPD | "I attend courses" | An identified gap, a planned activity, application on the job, and reflection |
| Communication | "I liaise with stakeholders" | Who the audience was, what changed in their understanding or decision |
| Project management | "I managed projects" | Scope or resource trade-offs you personally made and their consequences |
| Technical expertise | "I design structures" | The source of complexity and the judgement calls that were yours alone |
Ethics and Integrity: Writing Decisions, Not Values Statements
An ethics claim proves judgement under competing obligations, not adherence to a code you can recite. Build it around one real situation where two legitimate duties pulled against each other, and show the reasoning that resolved the conflict.
Useful ethics evidence names the tension. Common tensions in Australian practice include commercial confidentiality versus public interest disclosure, schedule pressure versus adequate review, and a client instruction versus professional independence. Engineers Australia's Code of Ethics frames obligations in priority order, with the safety and welfare of the community first, so a strong claim shows you recognised where your situation sat in that ordering.
A claim that only says "I referred to the Code of Ethics and acted with integrity" demonstrates nothing, because it omits the decision. The assessable content is the fork in the road: what the competing duties were, what you considered, whom you consulted, and what you did. Write the claim so a reader could disagree with your choice and see why; that is what makes it evidence of judgement rather than compliance.
Practise on paper decisions you did not personally face, then map the same reasoning structure onto your own projects. This separates the reasoning skill from the memory of events and often surfaces real examples you had dismissed as ordinary.
Risk, Safety and Legal Compliance: Tracing One Decision End to End
This area wants a traceable chain: hazard identified, options for control considered in order of effectiveness, the control implemented, and compliance with applicable Australian requirements checked. One fully traced decision beats three shallow mentions.
Worked scenario: you are the design engineer on a warehouse fit-out where overhead services must be rerouted near an access walkway. Your draft design places a pipe bracket within reach of the walkway. Mistake: writing this up as "identified a hazard and complied with WHS requirements", which names no reasoning. Better: explain that you worked through the hierarchy of controls, judged that guarding an engineering control was weaker than eliminating the exposure altogether by relocating the bracket during design, documented the change, and had the revised design verified before issue. Why it matters: the second version shows you understand that the hierarchy ranks elimination above controls that merely reduce or guard the exposure, and that verification closes the loop.
Legal compliance needs the same specificity without overreach. Name the framework at the right level of generality you can actually defend: work health and safety duties in your jurisdiction, relevant Australian Standards or codes you applied, and any approval or certification pathway the work followed. If you are unsure of a threshold or duty wording, describe the category of obligation and check the current instrument rather than quoting from memory, because requirements differ across states and change over time.
A useful structure is five lines: hazard, who was exposed, control considered and chosen, why weaker options were rejected, and how you confirmed the control stayed in place. If any line is blank, the example is not yet ready to use.
Continuing Professional Development: Separating Planned Learning From Job Experience
CPD evidence is learning you planned for an identified gap, then applied and reviewed. It differs from accumulated work experience because it starts with the gap, not the activity. Show the loop: need, plan, apply, reflect.
The distinguishing test is causality. "I learned anchor design while delivering the retaining wall project" is experience, not CPD, because the learning was incidental. "A project review showed my anchor design knowledge relied on inherited spreadsheets, so I completed structured learning on the current standard, then revalidated our spreadsheets against it" is CPD, because the gap was identified before the activity and the application is traceable.
Reflection is easy to omit when you reconstruct entries months later, because distance from the activity makes it tempting to write vague statements about "broadening knowledge" that demonstrate nothing specific. A CPD claim strengthens considerably when it ends with what changed in your practice: what you now check that you previously did not, or a habit you corrected. Keep a running log with a one-line reflection per activity written while the application is still fresh.
Exercise with a self-check: list your last twelve months of learning activities. For each, write the gap it addressed and one practice change it produced. Rubric: a score of 2 means the gap and the change are both specific; 1 means one is specific; 0 means neither. Anything scoring 0 is log filler, not evidence, and needs either enrichment or replacement.
Communication and Stakeholder Management: Proving You Changed a Decision
Communication competence is demonstrated by outcomes, not activities. A strong claim names the audience, what they needed to decide, how you adapted the message, and what changed as a result. Reporting that you attended meetings is not evidence.
Worked scenario: a council client is interpreting a geotechnical report as supporting a cheaper shallow foundation, while your analysis suggests the costlier option is warranted. Mistake: "presented findings to the client and they accepted our recommendation", which hides the actual work. Better: describe how you recognised the disagreement was about risk allocation rather than technical content, prepared a two-page comparison of lifecycle consequences rather than a full technical annex, walked the client's non-technical decision-makers through the two failure modes, and documented the client's informed acceptance of the chosen option. Why it matters: the second version shows audience analysis, message adaptation and a traceable decision, which are the communicable skills; the first could describe simply handing over a report.
Stakeholder claims also carry an ethics dimension when audiences have unequal information. Showing that you checked the client genuinely understood the residual risk, rather than just obtaining a signature, demonstrates integrity inside the communication claim. That kind of cross-area richness is legitimate, as long as the claim's central argument stays about communication.
Practical exercise: pick three recent deliverables and, for each, write one sentence stating what the recipient did differently because of it. If you cannot complete the sentence, ask whether the deliverable had a purpose you can articulate, because that sentence is the spine of the claim.
Technical Expertise and Project Management: Scaling Examples to Your Actual Role
These two areas fail in opposite directions: technical claims can overreach beyond your true contribution, and project claims can undersell by listing managed outputs without judgement. Calibrate both to the decisions that were genuinely yours.
For technical expertise, complexity is the currency. A routine task executed flawlessly supports an experience claim, not an expertise claim. Identify where the problem resisted standard treatment: unusual site conditions, conflicting requirements, incomplete data, or the need to choose between defensible methods. Then be precise about your role. "Our team designed the structure" is not your claim; "I developed the load path model, identified that the transfer beam exceeded the precast standard's empirical limits, and designed an alternative verified by second-order analysis" is.
Worked scenario: you led delivery of a pump station upgrade with a fixed shutdown window. Mistake: writing "managed the project to time and budget", which any administrator could claim. Better: explain that when an excavation permit was delayed, you assessed the programme, negotiated a resequenced commissioning that kept the wet well online, accepted a documented scope deferral to a later package, and briefed the asset owner on the residual risk. Why it matters: this shows resource management as decision-making under constraint, which is the capability the area is about, and the scope deferral shows you understand that trade-offs must be owned and recorded, not quietly absorbed.
A calibration check: for each technical example, mark every sentence as either describing the project or describing your judgement. If fewer than a third of sentences describe your judgement, the example is about the project, not about you.
A Preparation Sequence and Readiness Checks You Can Actually Run
Work in a fixed order: map projects to areas, draft one claim per area, run the rubric, then deepen the weakest two. Avoid drafting chronologically through your career, which produces a story rather than six verifiable claims.
A realistic sequence for a four-week cycle: week one, list eight to twelve projects and colour-code them against the six areas, noting gaps; week two, draft one 150-200 word claim per area using the claim-evidence-reflection structure; week three, apply the rubric below and rewrite every claim scoring below threshold; week four, have a peer from a different discipline read one claim cold and state, without prompting, what you personally did and decided. Their summary is a good proxy for what a reader extracts.
Readiness checks before you consider drafting finished: every area has at least one claim where your individual decision is identifiable; the ethics and risk claims each contain a genuine conflict or traceable control chain; each CPD entry names a gap and a resulting practice change; no claim relies on unverifiable phrases such as "consistently demonstrated"; and you have confirmed current administrative requirements directly with Engineers Australia rather than from secondhand summaries.
Rubric for each claim, scored 0-2 per row: specificity of your role, quality of the judgement shown, verifiability of the outcome, and fit to the intended area. A claim ready to use should total 6 or more of 8; scores are learning milestones for your drafting, not predictions of any assessment outcome.
Administrative details such as eligibility, evidence formats and processes are set by Engineers Australia and do change, so treat this guide as drafting preparation and the issuer's site as the authority for requirements.
- Week 1: project inventory mapped to the six areas, gaps identified
- Week 2: one draft claim per area, 150-200 words each
- Week 3: rubric review and rewrite of weak claims
- Week 4: cold-read test with a peer from another discipline
- Ongoing: CPD log with one-line reflections added as activities happen
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.