Treat reassessment as a rewriting task, not a re-proving task. Whatever the outcome of a prior attempt, the productive move is to make your evidence align more precisely with each competence element. Use the judgment-first pattern — I identified, I evaluated, I decided, the consequence was — and map every example to one specific element. Practise with the self-check rubric in Section 6 until your own scoring and a reviewer's scoring agree. One short note: confirm administrative details such as format, fees, and timelines directly with Engineering New Zealand (engineeringnz.org), as this guide covers preparation, not process logistics.
Why 'We Did' Statements Weaken a Reassessment Submission
Reassessment evidence must show you personally exercising each competence element, not simply that capable projects happened around you. The pivotal distinction to master is between an experience narrative and a competence demonstration.
An experience narrative describes a project: its scope, its team, its outcome. A competence demonstration isolates a single element — say, complex problem solving — and names your decision, the options you weighed, your reasoning, and the consequence. Chartered assessment is of the individual engineer, so a collective voice such as 'the team completed the detailed design' hides the very person being assessed. Treat a reassessment read as a closer read: prepare as though any vagueness in your examples will be scrutinised, and remove it before you submit.
Adopt a fixed rewrite pattern for every example: 'I identified [the problem or uncertainty]; I evaluated [options or criteria]; I decided [the action]; the result was [outcome or consequence]; in hindsight I would [change something].' This structure forces element-specific judgment into each paragraph. Also separate two ideas that submissions often merge: being responsible for a task (a role) and being accountable for a judgment (a competence). Compare 'I was responsible for the geotechnical input' with 'I judged the default bearing assumption unsafe and required additional testing before proceeding.' Only the second sentence is assessable evidence.
Showing Judgment in Complex Problem Solving, Not Just Method
Complexity is shown through how you framed a problem under incomplete information, not through naming the analysis method you used. Evidence should cover framing, assumptions, trade-offs, and how you handled residual uncertainty.
Useful complexity indicators in your own work include conflicting requirements, unreliable or missing data, novel constraints, and disagreement between stakeholders about what the real problem is. Evidence should show how you framed the problem before solving it: which assumptions you adopted, how you tested them, and what you did about the uncertainty you could not remove. Naming a software tool or a standard demonstrates tool familiarity. Describing why you chose a conservative input value, or why you paused a design to buy information, demonstrates judgment.
Worked scenario: a trunk water main renewal crosses ground with widely varying published stiffness values, and the two boreholes available are metres from a critical crossing. Weak version: 'I performed the structural analysis using the relevant design standard and the design passed all checks.' This describes compliance, not decision-making. Stronger version: 'The ground stiffness range spanned values that changed the pipe's support condition; I adopted the upper-bound stiffness for settlement estimates because the conservative alternative would have forced an unwanted realignment, and I commissioned a targeted third borehole at the crossing rather than accept the range.' Why it matters: the stronger version shows independent engineering judgment under uncertainty, which is exactly the competence claim the element makes.
Turning Safety Evidence from Standard Compliance into Risk Decisions
Hazard, risk, and safety assurance are three distinct concepts, and evidence should show each separately. Compliance with a standard is a floor; assessable judgment appears in decisions that removed, reduced, or explicitly accepted residual risk.
Keep the terms distinct in your writing. A hazard is a potential source of harm. Risk combines the likelihood and consequence of that harm being realised. Safety assurance is the demonstration that controls exist, were implemented, and remain effective. Evidence that collapses these into 'the design complied with the relevant standards' shows none of your reasoning. Stronger evidence walks the chain: the hazard you identified, how you ranked it against others, the design change you made, and how you verified the control survived into construction documentation. When describing safety duties that apply to designers in New Zealand, cite the current statutory framework rather than relying on memory, and link the issuer for authoritative guidance.
A recurring weakness is safety presented as a list of standards consulted. Flip it around a decision. For example: 'Site access for maintenance of the pump station originally routed personnel along a live traffic lane; I relocated the access hatch to the compound side, accepting a longer maintenance route in exchange for removing the traffic exposure, and flagged the residual manual-handling risk for the operations manual.' This shows the hierarchy of controls in action — eliminating the hazard instead of relying on signage or procedures — and names who carried the residual risk forward. That is a demonstration of safety judgment, not of document familiarity.
Demonstrating Legal and Ethical Accountability Through What You Did When It Went Wrong
Legal compliance means meeting consents, standards, and contract conditions; ethical reasoning is what you do when compliance and professional judgment pull apart. The strongest evidence of obligation comes from documented responses to problems, not from clean projects.
Evidence that only lists consents obtained or standards applied demonstrates awareness of the regulatory environment, not accountability within it. Stronger evidence shows a moment of tension: a potential non-compliance you identified, a conflict of interest you declared, or a client instruction you questioned. In New Zealand practice these situations typically touch building consent and resource consent processes, so keep your example grounded in the framework that actually governed your project and avoid citing legislation from memory — confirm the current statutory names and duties through the issuer. The assessable content is your documented response: who you told, what you recommended, and how you protected the public interest.
Worked scenario: during construction observation of a stormwater device, you notice the as-built soakage performance appears to deviate from the consented design. Weak version: 'I ensured the contractor complied with the consent conditions.' This claims oversight without any judgment. Stronger version: 'The recorded infiltration was below the consented rate; I assessed whether the deviation fell within the design's tolerance, concluded it did not, notified the client the same week, recommended disclosure to the council contact, and documented the agreed remedial testing.' Why it matters: the stronger version shows you recognised an obligation that ran to parties beyond your client, assessed severity before escalating, and created a paper trail. Evidence about obligations is strongest when it documents judgment under pressure, which is why imperfect projects often make the best examples.
Making Sustainability and Stakeholder Claims Concrete and Decision-Based
Sustainability becomes evidence when tied to a reasoned comparison — reuse versus replacement, embodied versus operational impacts, whole-of-life cost. Stakeholder competence is shown when input from others visibly changed an engineering decision.
Distinguish 'sustainability was considered' from 'whole-of-life reasoning changed the design.' The second requires a comparison you can describe: an option you rejected, a trade-off you accepted, or a quantified — or at least clearly reasoned — difference between alternatives. Reusing an existing foundation instead of replacing it, specifying a material for its lower embodied impact despite a higher capital cost, or designing for future adaptation are all decision-shaped claims. If you cannot name the alternative you rejected and why, the paragraph is aspiration rather than evidence, and it will not carry the element on its own.
For stakeholder engagement, separate three activities that submissions often blur: informing, consulting, and negotiating. The strongest evidence shows you adapted technical content for a non-technical audience and that the interaction changed the engineering. For example: presenting flood model results to a community board required translating probabilistic language into concrete scenarios; the board's concern about access during events led you to revise the warning signage and re-present the residual risk in plain terms. Document what changed as a result of the engagement. Two-way influence — where listening altered your recommendation — is the mark of competence that one-way reporting cannot show.
A Self-Check Rubric for Scoring Your Own Evidence
Score every evidence paragraph against a three-level rubric: 0 for activity description, 1 for personal action, 2 for personal judgment with reasoning and consequence. Aim for consistent 2s across all elements before treating yourself as ready.
Exercise: take one substantial project and 45 quiet minutes. Write or list one example per competence element — complex problem solving, risk and safety, legal and ethical obligations, sustainability, stakeholder engagement, and your ongoing competence development. Score each with the rubric below, then rewrite every paragraph scoring below 2 using the judgment-first pattern from Section 1. Repeat the scoring after rewriting.
Expected observations: in this exercise, sustainability and ethics examples are the likeliest to score lowest on a first pass, because they drift into values statements without decisions. Collective voice also easily creeps back in toward the end of long examples ('we then proceeded'), so re-check the ending of each example, not just the opening. If you and a trusted peer score the same paragraph differently by more than one level, the paragraph is ambiguous — which is itself the finding to act on. Remember these scores are learning milestones for your own editing; they are not predictions of any assessment outcome.
| Score | What the paragraph shows | Typical trigger phrase | Next action |
|---|---|---|---|
| 0 | Activity or project description; the element could be true of anyone on the team | 'The project involved…', 'The team completed…' | Identify one decision you personally made and rebuild the paragraph around it |
| 1 | Personal action is clear, but reasoning or consequence is missing | 'I prepared the design…', 'I attended the site review…' | Add what you weighed, why you chose, and what followed |
| 2 | Personal judgment with explicit reasoning, uncertainty, and outcome | 'I judged… because… the consequence was…' | Check the ending for collective-voice drift and confirm it maps to one named element |
An Adaptable Preparation Sequence and Final Readiness Checks
Prepare in six adaptable steps: audit prior feedback, build an evidence map, rewrite the weakest examples, peer-review with the rubric, rehearse explaining each example aloud, and run a final accuracy and anonymity check.
Start by rereading any prior feedback and converting each criticism into a specific rewrite instruction — for example, 'too much team voice' becomes 'every example opens with I identified or I judged.' Then build an evidence map: three or four projects listed against all competence elements, showing where you have genuine first-person judgments and where you are guessing. Rewrite the two weakest examples first, because they teach you the pattern fastest. Share the rewrites with a mentor or peer and have them score with the Section 6 rubric; disagreement between your scores is the signal to keep editing.
Finish by rehearsing each example aloud in three to four minutes, since explaining a judgment verbally exposes gaps that written paragraphs can hide. Close with a factual check: verify every standard, statute, and consent name in your examples against current sources, and anonymise any confidential project details. One-line note for administrative matters — assessment format, timelines, and fees are set by Engineering New Zealand, so confirm those on engineeringnz.org rather than from memory or third-party summaries. Use these readiness checks before you consider the preparation complete:
- You can state the core judgment of every example in one sentence starting with 'I decided' or 'I recommended'
- Every competence element has at least one first-person example, and the weakest two have been rewritten at least twice
- Each example names an uncertainty or constraint and explains how you handled it, not just the final answer
- A peer using the rubric scores all of your paragraphs at level 2, and your own scoring matches theirs
- You can answer 'what would you do differently now?' for each example without hesitating
- All named standards, legislation, and consent processes in your examples have been verified against current sources
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.