CPEng First-Time Assessment: Writing Evidence of Judgment

Prepare for the CPEng first-time assessment by practising the writing skill the assessment rewards: converting real project decisions into short evidence narratives that name the decision you owned, the alternatives you weighed, the uncertainties you managed, and who you engaged with and why. Work through the scenario rewrites, the competency mapping table, and the five-point rubric below, and build your evidence set in stages. For administrative matters such as current eligibility requirements, assessment format, fees, and timelines, check directly with Engineering New Zealand (engineeringnz.org), which is the issuing body; this guide addresses preparation, not those administrative rules.

From Task List to Evidence: Making Advanced Engineering Knowledge Visible

The advanced knowledge competency asks for depth of engineering analysis applied to real problems. Evidence works when it names a technical problem, the analytical depth you chose, why that depth was sufficient, and what you changed because of the result.

Contrast two ways of writing the same experience. 'I designed the stormwater network for a 40-lot subdivision' is a task history; it could have been written by anyone on the team. 'I selected a two-stage design approach because the upstream catchment had no gauged flow data, tested the sensitivity of peak flows to rational-method assumptions, and enlarged the downstream trunk capacity after the sensitivity run' shows knowledge applied and its limits acknowledged. The second version is what an assessor can evaluate.

A practical drafting habit: for each project, write one sentence starting 'the technically difficult part was...'. Then answer three questions in order: what methods or theory you applied, why those were proportionate to the problem, and where your own knowledge ran out and what you did about it, such as commissioning specialist input or returning to first principles. If you cannot write that third sentence, choose a different project, because knowledge applied entirely inside your comfort zone demonstrates less than knowledge stretched and checked.

Design and Delivery: Proving You Made Decisions, Not Just Drawings

Design evidence must show options generated, criteria applied, and trade-offs resolved; delivery evidence must show how your design survived contact with approvals, construction, and change. Outputs alone prove production, not judgment.

For design, structure each narrative as a short decision record: the brief constraint that drove the design, two or more options genuinely considered, the evaluation criteria, the option chosen and why the others lost. A pavement design narrative that says 'asphalt was chosen over concrete on whole-of-life cost and local contractor capability' is examinable; one that says 'the pavement was designed to the standard' is not, because every designer reaches that output but not every designer could defend the choice.

For delivery, mine the moments when the design changed. A requested variation, an unforeseen ground condition, a clash discovered on site: each is a chance to show you taking responsibility for a redesign under commercial and programme pressure. Write who you consulted before changing the design, what checks you re-ran, and how the change was recorded so the as-built matched the approved intent. Delivery competence is invisible in drawings and lives entirely in this kind of change management.

Risk and Sustainability: A Worked Scenario on Defensible Trade-offs

Risk and sustainability evidence needs identified hazards, treatment choices, residual risk honestly stated, and trade-offs explained. Code compliance without reasoning is the weak form; sensitivity analysis and communicated residual risk are the strong form.

Worked scenario: you assessed scour risk for a rural bridge replacement and selected the design flood event plus freeboard. A plausible first draft reads, 'I completed the scour assessment in accordance with the relevant standard and the bridge was built accordingly.' The mistake is treating compliance as the argument. It shows no judgment about the ungauged catchment data, no sensitivity testing of the hydrological assumptions, and no consideration of the debris blockage scenario that a local maintenance contractor mentioned, which materially changed the answer.

The better version records the sensitivity runs on rainfall-runoff assumptions, the design change when blockage was included, and the written note to the asset owner explaining the residual risk that remained after treatment. Why it matters: the competency being evidenced is independent ownership of a risk decision, including its uncertainties and their communication to whoever carries the consequence. A reader of the weak draft cannot tell whether you understood the risk or only completed a form; a reader of the strong draft can, and the same contrast applies to sustainability trade-offs such as justifying a higher-embodied-carbon option on resilience grounds.

Communication and Stakeholder Engagement When the Audience Disagrees

Communication evidence is strongest where technical information met a contested, non-technical audience. Show how you translated uncertainty, absorbed a challenge to your data, and let the exchange change your output, not just your presentation style.

Take a scenario where you presented modelled flood levels to a community meeting and residents disputed the mapping because it contradicted floods they had witnessed. 'I presented the modelling results to stakeholders' is the weak draft: it records attendance. The stronger narrative explains how you separated modelled event probabilities from observed flood heights in plain language, how you responded when a resident's photo evidence suggested a local blockage the model did not represent, and what you subsequently corrected or caveated in the public report.

The learning point is to collect engagement artifacts while they exist: meeting notes, the question that stumped you, the sentence you rewrote after the discussion. When drafting evidence later, pick a contested exchange rather than a smooth briefing, because routine reporting demonstrates formatting skill while a disagreement demonstrates whether you can hold technical authority and openness simultaneously. Name the stakeholder groups involved, what each needed from you, and one thing the engagement changed in the engineering itself.

Ethics and Conduct: Resolving a Dilemma on Paper, Not Reciting Values

Ethical competence is evidenced by a dilemma you personally recognised and resolved within the profession's rules, walked through step by step: the issue, the applicable rules, the options, your decision, and the escalation or refusal that followed.

Engineering New Zealand publishes the ethical rules and standards that govern chartered practice, and your preparation should include working directly from those documents rather than from memory of them. The evidence skill is applying them: a mini scenario is being asked to certify an inspection you did not personally carry out because the programme was tight. The weak account says 'I always act honestly.' The strong account identifies why certification without verification breaches the duty to the public and to the client, sets out the options considered, records what you proposed instead, such as a limited-scope certification or a delayed inspection, and states who you escalated the pressure to.

Not every engineer has a dramatic refusal in their history, and you should not invent one. Lesser situations work if the reasoning is complete: a conflict of interest declared before it was queried, a supplier's specification you declined to adopt uncritically, a safety concern raised about your own earlier design. The assessor is looking for the structure of ethical reasoning, so practise writing one dilemma in five steps: facts, ethical issue, rules engaged, options, decision and follow-through.

Cultural Competence and Te Tiriti o Waitangi: Integration Versus Attendance

This competency area asks how Te Tiriti obligations and Māori values connect to your engineering decisions. Genuine evidence shows engagement that changed a design outcome, plus honest reflection on what you are still learning, not a list of events attended.

Worked scenario: a stormwater outfall discharging to a stream near land of cultural significance. The plausible mistake is writing, 'I attended a tikanga workshop and a welcome ceremony at the project start.' That evidences presence, not competence. An assessor cannot tell from it whether any Māori perspective reached the engineering, or whether you understand why Te Tiriti partnership is relevant to infrastructure decisions affecting whenua and waterways at all.

The stronger narrative starts earlier: engagement with mana whenua representatives at options stage, learning the stream's values such as mahinga kai and proximity to wāhi tapu, the resulting change from a bare concrete outfall to a planted riparian edge and shifted discharge point, and an honest record of where you deferred to cultural expertise you did not hold. Why it matters: the competency concerns capability in practice, so the causal link from engagement to design change is the evidence. If your experience so far lacks such projects, evidence structured learning about Te Tiriti and a concrete plan for applying it, stated honestly rather than overstated.

A companion habit is reflecting on your own position: what obligations partnership creates for you as an engineer, whose knowledge your usual process excludes, and what you would do differently on your last project. This reflection, written specifically, carries evidential weight that generic respect statements never do.

Mapping Your Projects, a Rewrite Exercise, and Readiness Checks

Build preparation in stages: inventory your work, map it against the competency areas, write one decision narrative per pairing, have it interrogated by a chartered engineer, then fill New Zealand-specific gaps and rehearse your weakest narratives aloud.

The exercise: choose one project and write a 300-word narrative for each competency area it touches, then test every narrative against this rubric. One, it names a specific decision you personally owned. Two, it states at least two alternatives considered and the criteria used. Three, it identifies the main uncertainty or limitation and how you treated it. Four, it shows who was consulted and what changed as a result. Five, it records the outcome and one thing you would now do differently. First drafts of this kind typically satisfy checks one and five but fail two and four; expect to need two rewrite passes per narrative before all five hold.

Use the table below to decide which of your projects to develop, then track readiness with concrete observations rather than feelings. Administrative specifics of the assessment, including eligibility and format, sit with Engineering New Zealand and should be confirmed there.

Readiness looks like this: you can speak to any key decision in your three strongest projects for five minutes without notes; every drafted narrative passes all five rubric checks; and you can state plainly where your evidence is thin, such as limited iwi engagement, together with what you are doing about it.

• Weeks 1-2: inventory eight to ten pieces of work and shortlist three diverse projects using the table above.
• Weeks 3-5: draft one decision narrative per competency area per project; apply the five-check rubric.
• Week 6: have a chartered engineer interrogate the decisions in your drafts, not the spelling.
• Weeks 7-8: close New Zealand-specific gaps, working from Engineering New Zealand's published ethics rules and standards and structured Te Tiriti learning.
• Final week: rehearse your two weakest narratives aloud and rewrite the weakest sentence in every draft.

References and further reading

Use these references to explore the concepts and check the latest information from the relevant organizations.

• engineeringnz.org

Continue your preparation

• Cpeng First Time Assessment
• Study Guides