Engineering ethics are frequently taught as abstract principle and encountered as commercial pressure. The situations that matter are mundane: a client who does not want to pay for the investigation, a fee that has been cut below what proper monitoring requires, a developer who wants a producer statement issued.
The hierarchy of obligation
Professional codes place the safety, health and wellbeing of the public first — ahead of obligations to clients and to employers.
That ordering is the whole point. It means that where a client’s instruction would create unacceptable risk to people, the professional obligation is to decline, and the commercial consequence is not a relevant consideration.
In practice these situations rarely present that starkly. They present as pressure to accept a slightly thinner investigation, a slightly optimistic assumption, or a scope reduction that leaves something unchecked.
Competence
Working within your competence is an ethical obligation, not just a licensing one. Recognising the limits of your own knowledge is explicitly part of the competence standard for chartered registration.
The pressures that push against it: a valued client asking for something adjacent to your expertise, a quiet period making unfamiliar work attractive, and reluctance to refer work away.
The correct response is to decline or to bring in someone competent, and to say so plainly. Referring work on generally builds more goodwill than taking it and struggling.
The producer statement pressure
The most common ethical pressure point in New Zealand engineering practice.
A PS4 asserts that construction monitoring was carried out and the work accords with the design. Being asked to issue one at project end for construction you did not observe is a request to make a statement that is not true.
The commercial pressure is real — the project cannot get its code compliance certificate, the client is angry, the fee is outstanding. The answer is still no.
Prevention is at engagement: state explicitly whether monitoring is in scope, at what level, and that a PS4 follows only if that monitoring occurs. Clients who decline to pay for monitoring should understand at the outset what does not follow.
Conflicts of interest
Common situations:
- Acting for both parties to a transaction or dispute.
- Reviewing your own work, or your firm’s, as an independent reviewer.
- A financial interest in a product, contractor or development you are specifying or assessing.
- Personal relationships with a contractor whose work you are certifying.
- Employment offers from a party in a matter you are advising on.
- Fee structures that create an interest in a particular outcome.
The management sequence: identify it, disclose it in writing to affected parties, and either decline or obtain informed consent to continue with agreed safeguards.
Non-disclosure is what turns a manageable conflict into a professional problem. A disclosed conflict that both parties accepted is defensible; an undisclosed one is not, regardless of whether it actually affected your judgement.
Independent review means independent
Peer review and design review only work if the reviewer is genuinely independent and empowered to disagree. A review by someone in the same reporting line as the designer, under fee pressure, on a compressed timeframe, is a formality.
Where you are asked to provide a PS2 design review, be clear about what you actually reviewed and to what depth, and record it.
Raising concerns
Engineers sometimes find themselves aware of a problem in work they did not do — a design they consider inadequate, construction departing from documents, a building they believe is unsafe.
The obligation to public safety means this cannot simply be filed. The escalation path usually runs: raise it with the responsible engineer, then with the client or employer, then with the building consent authority, and where necessary with the professional body or regulator.
Document each step. Protected disclosure legislation may apply in an employment context, and taking advice before escalating externally is sensible.
Employed engineers
An engineer employed by a contractor or developer holds professional obligations that can conflict with employer expectations. The professional obligation does not reduce because you are an employee.
Where an employer instructs something you consider professionally unacceptable, put your position in writing. That record protects you and frequently changes the instruction.
Why this is commercially rational
Beyond the professional obligation: New Zealand engineering is a small market where reputation travels, disciplinary decisions are published, and producer statements issued today may be examined in fifteen years.
Engineering New Zealand publishes its code of ethical conduct and complaint processes, and the Building Practitioners Board publishes disciplinary decisions — which are worth reading as an efficient way to understand where the lines sit.
General information only, not legal advice.
