The Entry to Practice Assessment covers six topics, but the durable skill across all of them is deciding which obligation a scenario actually engages, and under which source — a professional code, a statute, a contract, or the common law duty of care. This guide teaches a three-part method: name the obligation, identify its source, then give a sequenced pathway of actions. It works through two full scenarios, a liability clause example, a comparison table of the four obligation sources, and a self-check rubric, so you practise the reasoning rather than memorising topic summaries.
Why One Scenario Triggers Four Different Sources of Obligation
One scenario can engage a code of ethics, a statute, a contract and a duty of care simultaneously. Identify which source creates each obligation before deciding what to do.
Professional practice material mixes four sources of obligation. A code of ethics binds you through your membership, registration or the profession's own disciplinary processes. Statutes — workplace safety, environmental, building and registration legislation — bind anyone the Act covers, regardless of agreement. A contract binds only its parties to what it says. The common law duty of care extends to people who foreseeably rely on your work, even with no contract at all. Each source answers a different question, so each needs separate identification.
Trace this example before moving on: your contract imposes strict confidentiality, but during a site inspection you observe a defect that could harm the public. Confidentiality is a contract duty owed to your client; public safety is a statutory and ethical duty that the contract cannot erase. A strong answer states both obligations, names their sources, and gives a sequenced pathway — verify the observation, report internally, escalate if unresolved. Skipping the source step collapses the analysis into a vague verdict about doing the right thing.
| Source of obligation | Who it binds | The question it asks | What happens if breached |
|---|---|---|---|
| Code of ethics | Members, registrants and practitioners the code covers | Is this consistent with the profession's duties to the public, clients and the profession itself? | Professional body or registration board processes, credential and reputational consequences |
| Statute and regulation | Anyone the legislation covers, whether or not they agreed | What does the law require or prohibit on this work? | Regulator action, penalties, statutory liability |
| Contract | Only the parties who signed it | What did we promise each other, and who carries which risk? | Breach of contract claim by the other party |
| Duty of care (tort) | Anyone owed a foreseeable duty, including non-parties | Did I meet the standard of a competent practitioner? | Negligence claim for the loss caused |
Worked Scenario: Employer Pressure to Certify Uncertain Work
The two obvious responses — sign quietly, or refuse outright — both fail. A defensible decision verifies the facts, objects in writing, proposes alternatives, and escalates through a documented pathway.
Scenario: you are the engineer responsible for signing off a concrete element. Test results are inconclusive, the program is critical, and your manager tells you to certify it and sort the paperwork later. The plausible mistake is framing this as a single yes-or-no loyalty choice. Signing despite uncertainty breaches the duty to the public and may exceed your actual knowledge; a flat refusal with no further action abandons the alternative paths that could still protect everyone. Neither response documents anything.
The better decision runs a sequence: confirm what the evidence actually shows and what the specification requires; state your position in writing; propose defensible alternatives such as later-age testing, additional investigation, or a design assessment of the as-built condition; and escalate to a senior engineer or a professional body's ethics advisory service if the pressure continues. This matters because the duty is not to be right instantly but to keep the decision inside your verified knowledge — and to leave a record showing that you did so.
Negligence in Four Elements, Not a General Fear of Being Sued
Liability questions become manageable when you separate duty of care, breach, causation and loss, and test each element against the scenario rather than concluding that someone is liable.
The standard of care is that of a competent practitioner of the same discipline in the same circumstances — not perfection, and not hindsight informed by the outcome. Duty of care usually rests on proximity and reliance: people who depend on your professional work. Breach asks whether your conduct fell below that competent-practice standard. Causation links the breach to the particular loss, and remoteness limits how far liability stretches. Vicarious liability can attach to an employer for an employee's work, which is separate from the individual practitioner's own accountability.
Consider a stormwater design that overtopps in a storm larger than its design basis. The tempting conclusion is that flooding proves negligence. The element-by-element check says otherwise: a duty was clearly owed, but a design meeting accepted practice for the specified storm is not a breach merely because a rarer event occurred, and the loss must flow from the shortfall rather than from an event outside the design basis. Reasonable professional decisions can produce poor outcomes without liability — and that distinction is exactly what the element test captures.
Indemnities, Liability Caps and Insurance Do Three Different Jobs
An indemnity shifts agreed losses to another party, a cap limits how much you can be claimed against, and insurance pays claims afterwards. Name which tool a scenario is actually using.
These instruments sit in different places in a scenario. An indemnity operates between contract parties and only as broadly as its wording — losses arising from your negligence is narrower than all losses. A liability cap may be a fixed sum, a multiple of fees, or the available insurance. Professional indemnity insurance funds payment after an event but does not change what you owe or reduce the underlying risk. Confusing them produces answers where insurance is offered as a substitute for safe work, which no source of obligation accepts.
Worked scenario: your consultancy holds a head contract capping your liability at a stated multiple of fees, and your subconsultant agreement caps the subconsultant at one fee payment. The plausible mistake is calling this back-to-back and moving on; the caps do not match, so a large claim leaves the gap with your firm. The better decision maps the exposure before signing — align the caps or insure the difference, verify the subconsultant's insurance is real and adequate, and record the treatment in the risk register as a deliberate choice.
Describing Risk Management as a Process, Not a Register You Mention
Risk management is a repeatable process — context, identification, analysis, evaluation, treatment, monitoring — and a strong answer walks a scenario through the steps to a named decision-maker.
The steps do distinct work. Establishing context sets what the analysis is for. Identification lists hazards without yet judging them. Analysis and evaluation rate likelihood and consequence, often against agreed criteria. Treatment selects controls, and the familiar hierarchy — elimination first, then substitution, engineering controls, administrative measures and finally protective equipment — orders them by effectiveness. Residual risk, what remains after treatment, must be accepted by someone identified as the risk owner, which is where the process connects back to accountability and documentation rather than ending in a completed spreadsheet.
Apply this to a mobile crane lift beside live traffic. A thin answer names the hazard and proposes spotters — an administrative control only. Walking the hierarchy: can the traffic be excluded or rerouted (elimination)? Can the lift location or crane type remove the exposure (substitution)? Only then do engineering measures, exclusion zones and administrative controls appear, and the residual risk goes to a named person for acceptance, with monitoring for changed conditions. The process produces a sequence of owned decisions, not a list of hazards.
Public Statements: Separating Verified Fact, Opinion and Advocacy
Communication duties depend on role and competence: report what you have verified, label professional opinion as opinion, stay inside your discipline, and protect confidential information even under pressure.
These categories blur under pressure. A verified fact is something you have checked or can source. Professional opinion is your judgement within your area of competence, and it must be labelled as such. Advocacy — promoting an employer's or client's position — is legitimate only while it does not mislead. Overreach takes two forms: certainty you cannot support, such as declaring a structure absolutely safe, and borrowing authority from your title to comment outside your discipline. Both breach honesty and competence duties even when intended to reassure.
A journalist contacts you about a defect in a building your client owns while the repair method is still being assessed. The tempting answer is reassurance: there is no safety issue. The better response states only what is verified — the defect exists, an assessment is underway, interim measures are in place — routes the conversation through the agreed communications protocol, and records exactly what was said. This matters because a public assurance you cannot yet support can itself cause harm if people rely on it, and the duty of honesty attaches to public statements.
A Three-Pass Preparation Sequence With a Self-Check Rubric
Prepare in three passes: build a source-of-obligation map, drill scenarios as short obligation-source-pathway notes, then write full answers under time limits, scoring yourself against a structured rubric.
In pass one, build a one-page map of the four obligation sources and the key distinctions in each topic — negligence elements, indemnity versus cap versus insurance, the control hierarchy, fact versus opinion. In pass two, work through practice questions for this assessment in short form: for each scenario, spend five minutes writing only the obligation, its source and the pathway, before reading any model answer. In pass three, write full structured answers under timed conditions. Adapt the passes to the weeks you have; the order matters more than the calendar.
Self-check exercise: after pass two, take an unfamiliar scenario and score your note against this rubric. Level one names an obligation with no source. Level two maps at least two obligations to their correct sources. Level three adds a sequenced pathway with escalation. Level four adds a documented record and identifies the risk owner. Expected observations: early notes read as verdicts; by the third attempt, sources appear before conclusions. One short administrative note: confirm current eligibility, format and scheduling with the issuing body, Engineers Australia, Australia's national engineering body, rather than from study material.
- Readiness check: you can classify a scenario's obligations as code, statutory, contractual or tort-based within a minute of reading it.
- Readiness check: you can write the four negligence elements and say which one a given scenario actually disputes.
- Readiness check: you can state, for a given clause, whether it indemnifies, caps or insures — and what each does not do.
- Readiness check: you can walk a hazard through the hierarchy of controls to a named residual-risk owner.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.