Engineering Practice: Professional Practice and Ethics
This domain tests whether you can apply the PEC Code of Ethics to realistic workplace situations - not recite slogans. Items are scenario-based: a client pressure, a colleague's error, a gift, a request to certify work you did not see.
What the code actually requires
- Public safety, health and welfare rank above client, employer and personal interest.
- Work only within your competence; where you are not competent, engage or recommend a specialist and say so in writing.
- Disclose conflicts of interest: shares in a supplier, a relative bidding for the contract, hospitality that could bias a decision.
- Keep client information confidential - but safety risk is the recognised exception; imminent danger must be reported.
- Be honest about qualifications and experience; never sign, seal or certify work you did not prepare or supervise.
- Compete fairly; criticise another engineer's work only on technical grounds, and give credit for others' contributions.
Worked example
A client asks you to certify a structural design prepared by another firm, without fee or time for review. Certification is a professional opinion you must be able to defend, so the correct response is to decline certification and instead offer a defined review (scope, fee, duration). Signing unverified work breaches the competence and honesty obligations and transfers liability to you. If a review reveals an error, notify the originating engineer first so it can be corrected, then inform the client.
Traps that cost marks
"The client instructed me" is not a defence; a verbal clearance from a senior manager does not transfer professional responsibility; confidentiality does not justify silence about danger; small gifts that create obligation are still conflicts of interest.