Start by inventorying six real decisions from your own experience, one per competence area, and write each as a short record: the situation, what you personally did, which alternative you rejected and why, and the outcome. Rehearse from those records, not from definitions.
Why a Competence Assessment Judges Judgment, Not Recall
A competence-based assessment asks whether you can apply professional judgment in realistic situations. Preparation therefore shifts from memorising definitions to mapping decisions you personally made onto named areas including ethics, law, risk, contracts, leadership and competence assessment itself.
In a knowledge test, the unit of evidence is a correct fact. In a competence assessment, the unit of evidence is a decision: what the situation was, what you did, which options you considered, and what followed. Reciting the definition of duty of care demonstrates little; describing a time you identified that a design change created a new duty situation demonstrates competence.
Begin with an inventory rather than a syllabus pass. List the projects you have contributed to, and under each note genuine decision points. Aim for six records, one per competence area. The sixth — competence assessment frameworks — is about judging capability itself: recognising when a task exceeded your own competence, or when a team member needed development, and what you did about it. Gaps in your inventory show which areas need example-hunting rather than more reading.
Public Safety Versus Employer Pressure: An Ethics Scenario Worked Through
Ethics questions test whether you can apply the principle that public safety takes priority over commercial and employer interests, through a documented reasoning process rather than a dramatic refusal.
Scenario: you are the site engineer for a contractor. The programme requires a slab pour tomorrow morning, but one batch of cube test results is still outstanding. Your construction manager tells you to proceed because the delay claim from the client would be significant. A plausible mistake is to frame this as a loyalty question — weighing your employer's interest against your conscience as if they were equal items on a scale — or to escalate with a vague protest that solves nothing and leaves no record.
The stronger response follows a reasoning process. Professional codes place the welfare and safety of the public first, so an unverified structural pour is not a tradeable commercial risk. The better decision is to state the concern specifically, propose a proportionate verification step — confirming the outstanding results, or a supervised alternative check — and document the exchange in writing. That combination of governing principle, proportionate action and written record is what makes such an answer strong, because it mirrors how ethical practice functions on real projects.
Negligence and Breach of Contract: Where Professional Liability Attaches
Professional liability in a common law jurisdiction such as Hong Kong arises through two distinct routes. Negligence requires duty, breach, causation and loss; contract liability flows from promises made. Knowing which route a scenario engages changes your answer.
Negligence asks whether you failed to meet the standard of care of a reasonably competent professional in the same position, and whether that failure caused loss. The standard is reasonable professional practice, not perfection. Analyse a scenario by separating the elements explicitly: was a duty owed, what would a competent peer have done, did the departure from that standard cause the loss, and what loss occurred. A design error caught and corrected before harm generally fails on causation and loss, even if care was imperfect.
Contract liability works differently: it arises from what the parties agreed, not from a general social duty. That is why the same engineer can face parallel exposure under both routes — a concept often called concurrent liability — and why contractual wording about responsibilities, reliance and exclusions matters so much. Compare the routes when you revise: who can claim, what must be proven, and what remedy follows. A client suing over a defective design may plead both, and the defences differ, which is the distinction worth being ready to explain.
Risk Register Versus Risk Assessment: A Second Scenario
Risk management competence shows in understanding the loop — identify hazards, assess likelihood and severity, control, assign ownership, monitor — rather than treating a register as a compliance document.
Distinguish the named concepts first. Hazard identification names what could cause harm. Risk assessment judges how likely and how severe that harm is, before and after controls. A risk register is the living record connecting each risk to its controls, its owner and its review trigger. Scenario: your register lists 'mobile crane operating near site boundary — medium' with no owner, no controls listed and no review date. A plausible mistake is to treat the entry as finished once the rating is assigned, so the risk is neither controlled nor revisited when the crane position changes.
The better decision is to complete the loop. Assess the risk in context — proximity to the boundary, ground conditions, the lift plan — then apply controls in a recognised order of preference, starting with elimination and substitution before administrative measures. Name an owner, define when the rating must be re-examined, and record all of it. Strong answers treat the register as a dynamic loop: who is watching this risk, and what would tell you it has changed? An answer that shows the loop demonstrates competence; an answer that recites a rating scale does not.
Procurement Routes and Who Actually Carries the Risk
Contracts and procurement questions test whether you can connect a procurement route to its risk allocation and its consequences for design control, coordination and claims.
The core learning task is tracing design risk through each route. Under a traditional arrangement, the employer's consultant completes the design and the contractor prices drawings and specifications, so design risk rests largely with the employer. Under a design-and-build route, the contractor takes responsibility for design as well as construction, giving the employer a single point of responsibility but weakening direct control over design decisions. Neither route is universally better; each shifts different risks to different parties.
Do not memorise route names in isolation. For each, ask three connected questions: who designs, who coordinates the interfaces, and who bears the cost of design change or incomplete information. Then anchor the comparison in one project from your own experience — for example, a variation on a traditionally procured job that triggered a claim because the design was not fully resolved at tender. Narrating how the route shaped that outcome is far stronger evidence than a textbook description, because it shows you understand procurement as a risk-allocation decision rather than a label.
| Aspect | Traditional route | Design-and-build route |
|---|---|---|
| Who carries design responsibility | Employer's design consultant | Contractor, as a single point of responsibility |
| Employer's control over design | Direct, through the consultant | Indirect, exercised through employer's requirements |
| Effect of unresolved design at tender | Priced later, often through variations and claims | Absorbed within contractor's price and programme |
| Best suited when | Design must be tightly specified before tender | Employer wants outcomes and speed over detailed control |
Communication, Leadership and Judging Competence: Three Evidence Patterns
Leadership and communication competence shows through examples where you adapted a message to an audience or moved people without formal authority; competence-framework evidence shows you can judge capability gaps and act on them.
An assessable communication example contains more than the fact that you wrote a report. It names the audience — a client, a regulator, a site team — and shows how the message was adapted: technical detail reduced, consequences made explicit, a decision requested. It also includes the feedback loop: what the recipient understood, what question they asked, what changed. For leadership, separate authority from influence; directing a subcontractor's foreman away from an unsafe method demonstrates leadership without any title. Pair one influence example with one formal-responsibility example so both dimensions are covered.
The sixth area, competence assessment frameworks, needs its own record, and in your own preparation it is easy to fold it into a general teamwork story — resist that. Evidence here means recognising the boundary of your own competence — declining to certify work outside your discipline, or flagging that a task needed a named specialist — and recognising capability gaps in others, such as arranging supervision or training for an inexperienced team member. Keep it separate from teamwork narratives: the judgment being demonstrated is the assessment of competence itself, not the delivery of a task.
A Four-Week Evidence-Bank Exercise With a Self-Check Rubric
Spend four weeks converting project memories into six written evidence records, one per competence area, drafted at three per week, each checked against a rubric before you rehearse speaking about it.
The exercise: select six decisions that together cover ethics, professional practice and law, risk, contracts and procurement, communication and leadership, and competence assessment frameworks. For each, write roughly 150 words covering the situation, your specific action, one alternative you rejected and why, the outcome or how it is being monitored, and the professional principle involved. Writing forces the distinctions traced above — duty versus promise, register versus loop, authority versus influence — to become explicit rather than assumed. Weeks one and two: draft three records per week, starting with your strongest areas so you learn the format on familiar ground. Week three: reconstruct or replace any record that fails the rubric, drawing on supervised experience where you can honestly describe your own contribution. Week four: rehearse explaining each record aloud and answering a follow-up about the alternatives you rejected.
Use the rubric below on every record. A record that fails two or more checks needs rework before rehearsal, because rehearsing a vague record only entrenches the vagueness. These checks are learning milestones for your own tracking, not predictions of any assessment outcome.
- Names the competence area explicitly and stays within it.
- Uses first-person verbs — I checked, I advised, I stopped — not 'we did'.
- States one rejected alternative and the reason it was rejected.
- States the outcome, or how the decision is still being monitored.
- Identifies the governing principle: public safety, duty of care, contractual obligation, risk control, or the limits of competence.
| Week | Focus | Concrete output |
|---|---|---|
| 1 | Strongest areas first | Three drafted evidence records |
| 2 | Remaining areas | Three more records, including ethics and law |
| 3 | Gap-filling | Replacements for any record failing the rubric |
| 4 | Rehearsal and follow-ups | Each record explained aloud plus one 'what else could you have done?' answer |
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.