Engineering practice
Engineering practice
This domain tests entry-to-practice judgement: how a registered engineer defines scope, gathers data, makes and records decisions, supervises work, and protects the public interest. Questions often place you at a project decision point rather than ask for a definition.
Core rules and concepts
- Practise only within your competence. If a task needs structural, geotechnical, electrical or other specialist input, obtain it and record who provided it.
- Define scope, deliverables, interfaces and acceptance criteria in writing before work starts. Ambiguity is a practice risk, not an administrative nuisance.
- Keep a traceable record: design basis, calculations, drawings, revision status, review comments, approvals and site instructions. If it is not recorded, it is difficult to defend.
- Delegate to competent people and review their output. Supervision is not the same as signing without checking.
- Consider constructability, operation, maintenance and whole-life impacts, not only first cost.
Worked example
A client asks you to approve a roof truss drawing prepared by a technician. The drawing has no load calculations or connection design. Reasoning: approval means taking professional responsibility. You request the design basis, loads, member checks and connection details; you review them or refer them to a competent structural engineer; you document the review and only then sign. If the evidence is inadequate, you decline to certify and state what is required.
Traps
Rubber-stamping another person’s work; treating software output as verification; accepting an oral scope; failing to record site instructions; and ignoring maintenance or safety in use.