Obligation-Conflict Resolution

Case 17-3 (2017) · Public Health, Safety and Welfare—Discovery of Structural Defect Affecting Subdivision

Professional obligations conflict, and the board applies no fixed rule for which one wins. Each resolution is recorded as three edges: competesWith (the tension), prevailsOver (the obligation the board allowed to win in this case), and defeasibleUnder (the situation under which the yielding obligation gives way). The same tension is then traced across comparable cases, where its resolution shifts with context. Hover any obligation or state to see its definition; click to open it in OntServe.
How this case resolved it competition structure in OntServe
Featured
Engineer A Building Officials Advisory Duty prevails over Engineer A Client Defect Reporting Duty
the two obligations are in tension (competesWith)
the yielding obligation gives way only under (defeasibleUnder):
  • Higher Ethical Threshold for Engineer A
Engineer A Corrective Action Escalation Duty prevails over Engineer A Client Defect Reporting Duty
the two obligations are in tension (competesWith)
the yielding obligation gives way only under (defeasibleUnder):
  • Higher Ethical Threshold for Engineer A
Open tensions recorded without a resolution: Engineer A Client Defect Reporting Duty vs Engineer A Public Safety Duty
What the board concluded
  • Contrary to the advice of the State Board of Professional Engineers, Engineer A did not fulfill his ethical obligations under the NSPE Code of Ethics by only providing the report to the insurance company that retained him. Engineer A had a responsibility to take additional steps beyond merely submitting a written report to the insurance company, including contacting local building officials,...
Recorded violations: Omission of Further Notification violates Engineer A Corrective Action Escalation Duty
How comparable cases resolved this and related tensions

Read at the type level, this resolution is: Reporting Obligation yields to Reporting Obligation. Comparison across cases happens at this level; the duty types recur while each case's obligations instantiate them. Cases below are grouped by how much of that pairing they share. A duty type that yields here may prevail elsewhere, which is the context-dependence itself, not an inconsistency.

Same tension: both duty types match, so the board ruled on this exact pairing. Related tension: only one duty type matches; the other duty differs, so these show how a type behaves elsewhere rather than a ruling on this pairing.

Case Prevailing type Yielding type Relation to this case
Related tension: one duty type matches (7)

Closest instance-level matches, ranked on the specific obligations and contexts of this case:

Case Obligation that prevailed Yielding obligation Context (defeasibleUnder)
18-9
Public Health and Safety—Building Codes to...
Engineer A Public Safety Duty Engineer A Client Persuasion Duty Client Duty Versus Public Safety Conflict; Owner Cost Based Refusal
08-10
Public Welfare—Design of Medical Equipment
Engineer A Internal Recourse Duty Engineer A Conditional Reporting Duty Internal Mechanisms Available MedTech
96-8
Peer Review - Confidentiality Agreements
Engineer A Authority Cooperation Duty Engineer A Confidentiality Duty Confidentiality Versus Cooperation Dilemma