KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesThe Engineering Profession: Competence, Registration and the Duty of CareEngineering · Civil & StructuralLesson 12/12← PrevNext →
GuidePublished 4 Aug 2026Updated 13 Aug 202611 min readBy Kevin JoginEngineering ProfessionRisk ManagementHistory of EngineeringCivil Engineering
On this page

Ask about this page

KEVOS AIThe Engineering Profession: Competence, Registration and the Duty of Care

KEVOS knowledge first · trusted web sources when needed

Knowledge LibraryEngineeringCivil EngineeringKL-ENG-HIST-1631

The Engineering Profession: Competence, Registration and the Duty of Care

Society stopped accepting self-declared expertise the year a bridge fell into the St Lawrence. What registration actually tests, why supervised experience carries the most weight, and how Australian obligations differ by state.

Part 12 of 12 Period 1907-present Milestones 1 Reading 5 min Updated 2026-08-04

01Executive summary

In 1907 Wyoming became the first American state to require engineers to be licensed. In the same year the Quebec Bridge collapsed during construction, killing seventy-five workers. The coincidence is not causal, but it is not accidental either.

By the early twentieth century engineers were routinely designing structures and systems whose failure could kill hundreds of people at once. Society had no way to distinguish a competent engineer from a confident one. Statutory registration was the institutional answer, and every competence framework, chartered status scheme and design certification regime in use today descends from it.

1907First statutory engineer registration in the United States
4Pillars of registration: education, examination, experience, ethics
75Workers killed in the 1907 Quebec Bridge collapse
1919Institution of Engineers, Australia established

02Why the Quebec Bridge is taught

The Quebec Bridge was to be the longest cantilever span in the world. During construction in August 1907 the south anchor arm failed and the structure collapsed into the St Lawrence River. The subsequent royal commission found that the dead load had been underestimated and never properly revised, that the compression chord design was inadequate for the members as built, and — most damningly — that measured deformations in those members had been observed and discussed in the weeks before the collapse without work being stopped.

The failure chain

An early assumption is not revisited as the design develops. Authority for the check is concentrated in one remote individual. Evidence of distress appears in the field. The evidence is reported but the decision to stop is deferred pending advice. The structure fails while the advice is in transit. Every element of that chain is organisational rather than technical, and every one of them recurs in modern failure investigations.

What the profession took from it

Independent checking

Significant designs are verified by a competent party with no stake in the original. Independence is the point; a second look by the same team is not a check.

Authority to stop

People who can see the evidence must be able to halt work without needing permission from those who cannot. Stop-work authority is a safety control, not an insubordination risk.

Design assumptions are live

Loads, load factors and material assumptions must be revisited whenever the design changes. An assumption made at concept and never revalidated is a latent defect.

Named responsibility

Someone competent signs. A signature attaches accountability to a person, which changes behaviour in a way that a process alone does not.

03The registration model

The North American professional engineer model has four components, and its logic is worth understanding because the same four appear in almost every subsequent scheme worldwide.

The four pillars and what each one actually tests
PillarMechanismWhat it verifies
Accredited educationDegree from a programme accredited against agreed outcomesThat the theoretical foundation is complete and independently assessed
Fundamentals examinationBroad written examination, usually soon after graduationThat the foundation was retained, not merely passed
Supervised experienceA period of practice under a registered engineerJudgement — the part that cannot be examined, only developed
Practice examinationSpecialised examination in the area of intended practiceCompetence in a defined scope, not in engineering generally

The third pillar is the one that carries the most weight and receives the least attention. Technical knowledge can be examined. Judgement — knowing which assumptions are fragile, when a result is implausible, when to escalate, when to stop — is acquired by supervised exposure to consequences. A registration scheme without a genuine supervised experience requirement tests only half of what matters.

Practice note — Australia

Australia’s arrangements are federated and have changed substantially in recent years. Engineers Australia administers Chartered status and the National Engineering Register, and accredits engineering degree programmes under the Washington Accord. Statutory registration exists at state level: Queensland has required registration of professional engineers for decades through the Board of Professional Engineers of Queensland; Victoria introduced a professional engineers registration scheme; and New South Wales regulates registered design and building practitioners for building work following the Design and Building Practitioners Act 2020, which requires declared designs and creates a statutory duty of care. The practical implication for engineers working nationally is that scope of practice, class of registration and declaration obligations differ by jurisdiction, and it is the engineer’s responsibility to confirm them before signing anything.

04Competence and the duty of care

Registration frameworks are built on a single principle that is easy to state and uncomfortable to apply: an engineer must work only within their demonstrated competence. The discomfort is that competence is scoped, and career progression usually involves being asked to work just outside it.

Scope of competence
Defined by education, experience and current practice — not by job title, seniority or confidence. It narrows as fields specialise and it decays if not maintained.
Continuing professional development
A registration obligation in most schemes, and the mechanism by which scope is maintained and extended. Treat it as maintaining a licence, not collecting hours.
Duty of care
Owed to those affected by the work, including parties with no contractual relationship to the engineer. In several Australian jurisdictions this duty is now statutory rather than only a common law obligation.
Conflict of interest
Disclosed and managed, or declined. A checker who reports to the designer is not independent, whatever the organisational chart says.
Obligation to speak
Professional codes require raising safety concerns even when it is commercially or personally costly. This is the clause that matters, and the one most often tested in practice.

A working test before you sign

  1. ScopeIs this work within my demonstrated competence, and can I show how? If not, who holds it?
  2. BasisAre the design assumptions current, documented and traceable to the design as actually built?
  3. CheckHas a genuinely independent competent party verified the critical load paths and failure modes?
  4. EvidenceWould a reasonable peer, reviewing this after a failure, find the reasoning defensible on the record?
Closing the series

Every earlier part of this series describes engineers extending what was physically possible. This part describes the profession accepting limits on who may do so. Both are engineering. The capacity to build things that can kill people at scale arrived first; the institutions that make that capacity accountable arrived afterwards, and they arrived because things fell down. That sequence is worth remembering whenever a new capability outruns the framework governing it — which is, at present, most of the time.

05Takeaways

Judgement is the licensed quality

Knowledge is examinable; judgement is developed under supervision. Protect the experience requirement.

Independence must be structural

A checker who depends on the designer is not a check. Design the reporting line, not just the process.

Stop-work authority is a control

The Quebec Bridge failed while advice was in transit. Whoever sees the evidence must be able to act on it.

Know your jurisdiction

Australian registration and declaration obligations differ by state. Confirm them before you sign, every time.

Previous in seriesFlight, sailing and the refrigeration cycleSeries indexMilestones of the Modern Era, 1845-1910

KL-ENG-HIST-1631 · KEVOS® Knowledge Library · Engineering / Civil Engineering

  • Engineering Profession
  • Risk Management
  • History of Engineering
  • Civil Engineering

Original KEVOS® synthesis. Historical dates, attributions and device descriptions are drawn from general engineering history; the analysis, structure, standards commentary and Australian practice notes are our own. Figures are indicative and are given for teaching purposes — verify against the governing standard or manufacturer data before using them in design.

© KEVOS® — Precision to Vision. Prepared by Kevin Jogin.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review The Engineering Profession: Competence, Registration and the Duty of Care. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to carry the subject from function and assumptions through design evidence, verification and controlled release. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Apply The Engineering Profession: Competence, Registration and the Duty of Care by beginning with the duty, not the component or software command. Convert the key ideas—profession, competence, registration, duty, care—into measurable requirements and interfaces. Record operating and non-operating environments, duty cycle, expected life, loads, energy sources, human interaction and reasonably foreseeable abnormal conditions. When a value is not a project requirement or verified supplier datum, identify it as an assumption or illustrative value.

Create a calculation and evidence trail that another competent person can audit. Every input should carry a source, unit, revision and uncertainty or tolerance where relevant. Every model should state its boundary conditions and limitations. Keep nominal capacity separate from design capacity, and keep verification margin separate from an arbitrary safety factor. If a code or standard governs the work, confirm the applicable edition and contractual status rather than copying a number from a secondary summary.

Design for manufacture, assembly, inspection, operation and maintenance at the same time. A technically valid geometry can still fail because it cannot be fixtured, measured, cleaned, guarded, reached or replaced. Review process capability, datum or reference strategy, tolerance accumulation, access, error-proofing and changeover. Where people interact with plant, apply the hierarchy of controls and consult those who will operate, clean, maintain and recover the equipment.

Plan verification before release. Define the characteristic, method, equipment, sample or test condition, acceptance criterion, record and responsible person. Validation then asks a different question: whether the resulting system is effective and suitable in the intended use context. A passed drawing check or analysis does not by itself validate usability, maintainability or production performance.

Step-by-step operating method

  1. Define the duty. Capture the required function, interfaces, operating environment, life, loads and unacceptable outcomes.
  2. Establish the model. Identify governing principles, units, material or process data, assumptions and uncertainty.
  3. Develop alternatives. Compare feasible concepts against performance, manufacturability, safety, maintainability and cost.
  4. Verify the design. Use analysis, test, inspection or demonstration with acceptance criteria defined before execution.
  5. Release and learn. Baseline the design, control changes, retain evidence and feed operating results into the next revision.

Illustrative design review record

Illustrative values only. Build a one-page record with the required function, input sources, assumptions, governing load or process condition, failure consequences, selected concept, verification method and acceptance criterion. Mark every numerical input as project requirement, verified supplier data, measured value, calculation output or assumption. Review the weakest evidence first. If an assumption can change safety, compliance, interchangeability or capacity, it must be resolved before release rather than buried in a calculation note.

Evidence classQuestionRelease expectation
RequirementWhat must the design do and under which conditions?Approved and traceable
InputWhere did the load, property, tolerance or process limit come from?Source, unit and revision recorded
AnalysisWhich model and assumptions connect input to result?Checkable calculation or simulation
VerificationHow will conformity be demonstrated?Method and acceptance criterion agreed
ValidationWill the solution work for intended users and conditions?Representative use evidence

Common failure modes and recovery actions

1. Watch for

Starting detailed design before interfaces and operating limits are agreed.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Using catalogue or typical values as though they were certified project inputs.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Checking nominal performance while ignoring tolerances, degradation and foreseeable misuse.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Confusing verification of requirements with validation of user need.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Releasing drawings or procedures without configuration, inspection and change controls.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

  • What function and failure consequence govern this decision?
  • Which inputs are measured, specified, assumed or illustrative?
  • How will conformity be demonstrated and recorded?
  • What change would invalidate the current evidence?
  • Are mandatory requirements distinguished from recommendations and illustrative values?
  • Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
  • Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
  • Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying The Engineering Profession: Competence, Registration and the Duty of Care?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which assumption about profession would change the result most if it proved false?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What evidence would allow an independent reviewer to reproduce or challenge the conclusion?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which boundary, exception or failure case has not yet been tested?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What must be handed over, monitored or reviewed after the immediate work is complete?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Authoritative references and use notes

The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.

  • SOLIDWORKS Design Help — Dassault Systèmes SOLIDWORKS. Used for feature-based CAD, sketches, structures and manufacturing outputs. Accessed 2026-08-13.
  • NASA Systems Engineering Handbook — NASA. Used for requirements, design, verification, validation and technical management. Accessed 2026-08-13.

Continue learning

Fluids and Comfort: Powered Flight, Sailing Hydrodynamics and Air ConditioningGuide · MechanicalBiomedical Engineering Begins: The ECG, the Defibrillator and Keyhole SurgeryGuide · ElectricalSignals and Standard Time: The Telephone Network and the Great ClockGuide · ElectricalNetworks of Movement: Transcontinental Rail, Cable Traction and the Great WheelGuide · Civil & Structural
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®