Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Pipeline Steps
Overview
1 Contextual Framework
2 Normative Requirements
3 Temporal Dynamics Reconcile
4 Whole-Case Synthesis
Extraction Review Full View
Provenance
Duty To Report Safety Violations
Step 4 of 5
Entity Review

337

Entities

6

Provisions

5

Precedents

17

Questions

24

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A held knowledge of a life-safety hazard but misclassified his confidentiality obligation as absolute, thereby blocking the transfer that the NSPE Code's own architecture required. The Board's resolution completed the transfer that Engineer A failed to execute: safety-critical information about electrical and mechanical code violations in an occupied building was determined to belong — via mandatory disclosure — with the appropriate public authorities, relieving Engineer A of the burden of the hazard only upon fulfilling the reporting duty. The original party (Engineer A) was never legitimately the terminal holder of this obligation; the Code's Section II.1.c exception clause pre-authorized and required the handoff to regulatory authorities, making the transfer the correct and intended resolution of the scenario.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (6)
View Extraction
I.1. Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 79)
Obligation
Engineer A Paramount Safety Word Supremacy Hierarchy Non-Recognition
Section I.1 establishes the paramount safety obligation that Engineer A was required to recognize as hierarchically supreme.
Action
Verbally Warning Client of Danger
Warning the client of danger is a direct action to protect public safety as required by this provision.
State
Public Safety at Risk from Known Code Violations in Occupied Building
This provision directly mandates that Engineer A hold paramount the safety of occupants exposed to known code violations.
Obligation (13)
  • Engineer A Paramount Safety Word Supremacy Hierarchy Non-Recognition
    Section I.1 establishes the paramount safety obligation that Engineer A was required to recognize as hierarchically supreme.
  • Engineer A Client Safety Violation Insistence or Withdrawal Failure
    Section I.1 requires holding public safety paramount, directly obligating Engineer A to insist on remediation or withdraw.
  • Engineer A Client Safety Violation Insistence or Project Withdrawal
    Section I.1 mandates paramount public safety, requiring Engineer A to insist on remediation before completing the engagement.
  • Engineer A Passive Acquiescence Known Safety Violation Independent Ethical Failure
    Section I.1 prohibits passive acquiescence to known safety violations by requiring active prioritization of public safety.
  • Engineer A Passive Acquiescence Independent Ethical Failure
    Section I.1 requires active measures to protect public safety, making passive acquiescence a direct violation.
  • Engineer A Occupied Building Electrical Mechanical Violation Occupant Escalation
    Section I.1 requires holding safety paramount, obligating escalation when occupants face known electrical and mechanical hazards.
  • Engineer A Tenant Occupant Direct Notification Electrical Mechanical Violations
    Section I.1 mandates paramount public safety, supporting direct notification of occupants facing known hazards.
  • Engineer A Competing Confidentiality Safety Code Provision Contextual Balancing
    Section I.1 is the paramount safety provision that must be weighed against confidentiality obligations in the contextual balancing.
  • Engineer A Competing Confidentiality-Safety Code Provision Contextual Balancing Failure
    Section I.1 is the paramount safety provision whose weight Engineer A failed to properly balance against confidentiality.
  • Engineer A Ethics Code Cross-Provision Non-Vacuum Reading Failure
    Section I.1 is one of the cross-provisions Engineer A was obligated to read in conjunction with confidentiality provisions.
  • Engineer A Going-Along After Client Safety Refusal Independent Ethical Violation
    Section I.1 requires paramount safety protection, making going along after client refusal a direct violation of this provision.
  • Engineer A As-Is Sale Directive Safety Reporting Non-Override
    Section I.1 establishes that public safety is paramount and cannot be overridden by a client business directive such as an as-is sale.
  • Case 84-5 Engineer Going-Along Without Dissent Analogous Violation
    Section I.1 requires paramount safety protection, making the analogous engineer's going-along without dissent a violation of this provision.
Action (2)
  • Verbally Warning Client of Danger
    Warning the client of danger is a direct action to protect public safety as required by this provision.
  • Declining to Report Violations Externally
    Declining to report safety violations externally may conflict with the duty to hold paramount the safety and welfare of the public.
State (7)
  • Public Safety at Risk from Known Code Violations in Occupied Building
    This provision directly mandates that Engineer A hold paramount the safety of occupants exposed to known code violations.
  • Engineer A Confidentiality vs. Public Safety Competing Duties
    The paramount safety obligation is the competing duty that challenges Engineer A's confidentiality commitment.
  • Engineer A Passive Acquiescence to Client Safety Refusal
    Failing to act on known safety violations contradicts the paramount duty to protect public safety.
  • Engineer A Paramount Safety Obligation Notification Duty
    The paramount safety obligation under I.1 is the foundational basis for Engineer A's duty to notify appropriate authorities.
  • Confidentiality Obligation vs. Occupant Safety Competing Duties
    I.1 establishes that public safety takes precedence, directly informing how this competing duty tension must be resolved.
  • Client As-Is Sale No Remediation Intent Active
    The client's refusal to remediate known hazards directly conflicts with Engineer A's paramount duty to public safety.
  • Out-of-Scope Code Violation Disclosure in Occupied Building Sale
    Knowledge of safety-threatening code violations in an occupied building triggers the paramount safety obligation regardless of scope.
Constraint (10)
  • Engineer A Public Safety Paramount Over Confidentiality Electrical Mechanical Violations
    Section I.1 establishes the paramount safety obligation that pre-empts confidentiality duties regarding the electrical and mechanical violations.
  • Engineer A Occupied Residential Building Electrical Mechanical Code Violation Occupant Injury Escalation
    Section I.1 requires holding public safety paramount, directly obligating escalation of known code violations in an occupied building.
  • Engineer A Paramount Safety Normative Hierarchy Confidentiality Subordination
    Section I.1's use of 'paramount' establishes the normative hierarchy that subordinates confidentiality obligations under Section III.4.
  • Engineer A Public Safety Paramount Over Confidentiality Occupied Building
    Section I.1 creates the paramount public safety obligation that overrides confidentiality when occupants face known electrical and mechanical hazards.
  • Engineer A Non-Acquiescence Client As-Is Sale Economic Override Safety
    Section I.1 prohibits acquiescing to economically motivated client decisions that compromise the paramount duty to protect public safety.
  • Engineer A Non-Acquiescence to Client Economic Override Safety Refusal
    Section I.1's paramount safety mandate constrains Engineer A from deferring to the client's economic refusal to remediate known safety violations.
  • Engineer A Comprehensive Code Integration Confidentiality-Safety Conflict
    Section I.1 is one of the provisions Engineer A was required to integrate when resolving the confidentiality-safety conflict.
  • Engineer A As-Is Sale Business Decision Safety Escalation Non-Override
    Section I.1 establishes that the paramount safety obligation cannot be extinguished by the client's business decision to sell as is.
  • Engineer A Agent-Trustee Confidentiality Rationale Non-Absolutism
    Section I.1's paramount safety mandate limits the agent/trustee confidentiality rationale when public safety is at risk.
  • Engineer A Passive Acquiescence Known Safety Violation Independent Ethical Failure
    Section I.1 creates the duty that passive acquiescence to unaddressed safety violations independently violates.
Principle (8)
  • Public Welfare Paramount Invoked By Engineer A In Occupied Building Safety Context
    I.1. directly embodies the paramount public safety obligation Engineer A recognized but failed to fully act upon regarding occupied building violations.
  • Public Welfare Paramount Invoked in Engineer A Confidentiality-Safety Conflict
    The Board explicitly invokes I.1.'s paramount language to establish that public safety overrides confidentiality in Engineer A's case.
  • Confidentiality Non-Applicability to Public Danger Disclosure Violated By Engineer A
    I.1. is the foundational provision establishing that public safety supersedes confidentiality when danger exists.
  • Non-Acquiescence to Unsafe Client Directive Violated By Engineer A
    I.1. requires engineers to hold public safety paramount, which Engineer A violated by acquiescing to the unsafe as-is sale directive.
  • Third-Party Affected Party Direct Notification Obligation Not Discharged By Engineer A
    I.1. underpins the obligation to protect building occupants by ensuring they are notified of dangerous conditions.
  • Passive Acquiescence Ethical Failure. Engineer A Going Along After Client Safety Refusal
    I.1. is violated by Engineer A's passive acquiescence, as holding safety paramount requires active steps beyond mere notification.
  • Non-Acquiescence to Unsafe Client Directives. Engineer A Should Have Refused to Continue
    I.1. requires prioritizing public safety over client directives, supporting the obligation to refuse continuation of unsafe work.
  • Competing Code Provision Contextual Balancing. III.4 vs. II.1.a. vs. II.1.c.
    I.1. is the overarching provision that tips the balance in the cross-provision analysis toward public safety disclosure.
Role (4)
  • Engineer A Confidentiality-Bound Structural Safety Discovering Engineer
    Engineer A discovered safety violations and is professionally obligated to hold public safety paramount above confidentiality obligations.
  • Engineer A Confidentiality-Bound Public Safety Inaction Engineer
    Engineer A's inaction in the face of known safety risks directly violates the duty to hold public safety paramount.
  • Case 84-5 Engineer Construction Phase Safety Recommendation Abandoning Engineer
    The engineer abandoned a safety recommendation during a dangerous construction phase, failing to hold public safety paramount.
  • Building Occupants Stakeholder
    Building occupants are the public whose safety, health, and welfare must be held paramount under this provision.
Event (3)
  • Occupants Remain Exposed to Hazard
    The paramount duty to protect public safety is directly implicated when occupants continue to face an unaddressed hazard.
  • Electrical and Mechanical Violations Disclosed
    Disclosing safety violations relates to the duty to hold public safety paramount by bringing dangerous conditions to light.
  • Engineer A's Conduct Retrospectively Condemned
    The condemnation of Engineer A's conduct is grounded in his failure to uphold the paramount duty to protect public safety.
Resource (6)
  • NSPE-Code-Section-I.1
    This provision is the source text that NSPE-Code-Section-I.1 directly represents and cites to establish the paramount safety obligation.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework
    I.1 establishes the paramount safety duty that must be weighed against confidentiality in this balancing framework.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework-Instance
    The Board explicitly invokes I.1 as the paramount obligation when constructing the balancing framework instance.
  • Engineer-Public-Safety-Escalation-Standard
    I.1 is the foundational provision requiring engineers to hold public safety paramount, which drives the escalation obligation.
  • Out-of-Scope-Safety-Finding-Reporting-Standard
    I.1 requires holding public safety paramount, which obligates reporting even when safety findings fall outside the engineer's contracted scope.
  • NSPE-Code-of-Ethics
    I.1 is a core provision of the NSPE Code of Ethics governing Engineer A's competing obligations in this case.
Capability (26)
  • Engineer A Out-of-Discipline Injury Risk Recognition
    I.1 requires holding public safety paramount, directly engaging the duty to recognize injury risks from out-of-discipline code violations.
  • Engineer A As-Is Sale Directive Safety Non-Override Recognition
    I.1 establishes that public safety is paramount and cannot be overridden by a client's business directive such as an as-is sale.
  • Engineer A Scope-of-Work Non-Shield Safety Disclosure Non-Recognition
    I.1 requires paramount public safety regardless of scope, meaning scope of work cannot shield an engineer from safety disclosure obligations.
  • Engineer A Scope of Work Non-Shield Safety Disclosure Recognition
    I.1 directly requires that public safety be held paramount, making scope of work an insufficient excuse for non-disclosure of known hazards.
  • Engineer A Brief Report Mention Insufficiency Recognition
    I.1 requires holding public safety paramount, meaning a brief confidential mention of hazards is insufficient to satisfy that obligation.
  • Engineer A Passive Acquiescence Independent Ethical Failure Recognition
    I.1 requires active protection of public safety, making passive acquiescence without insisting on corrective action an independent ethical failure.
  • Engineer A Client Insistence or Withdrawal Safety Enforcement
    I.1 requires holding public safety paramount, which supports the duty to insist on remediation or withdraw from the engagement.
  • Engineer A Competing Confidentiality Safety Provision Balancing
    I.1 establishes the paramount safety obligation that must be weighed against confidentiality provisions in any balancing analysis.
  • Engineer A Confidentiality Non-Applicability Public Danger Assessment
    I.1 requires paramount public safety, which is the basis for assessing whether confidentiality obligations yield when public danger exists.
  • Engineer A Tenant Occupant Direct Notification Consideration
    I.1 requires holding public safety paramount, which grounds the obligation to consider directly notifying tenants or occupants of known hazards.
  • Engineer A Post-Client-Refusal Regulatory Escalation Assessment
    I.1 requires paramount public safety, which necessitates assessing escalation to regulatory authorities when the client refuses to remediate.
  • Engineer A Client-Disclosed Safety Hazard Out-of-Scope Reporting
    I.1 requires holding public safety paramount regardless of scope, directly supporting the duty to report client-disclosed hazards even if out of scope.
  • Engineer A Confidentiality Pre-emption by Public Safety
    I.1 establishes the paramount safety obligation that pre-empts confidentiality when public danger is at stake.
  • Engineer A Paramount Safety Normative Hierarchy Supremacy Application Failure
    I.1 is the provision that establishes the normative supremacy of public safety, which Engineer A failed to apply.
  • Engineer A Going-Along Without Dissent Independent Ethical Violation Self-Recognition Failure
    I.1 requires active protection of public safety, making silent going-along with a dangerous directive an independent violation of this provision.
  • Engineer A NSPE Code Section II.1.c Exception Clause Non-Activation Failure
    I.1 is the paramount safety obligation that activates the exception clause in II.1.c, making failure to apply it a failure under I.1 as well.
  • Engineer A Post-Client-Override Public Safety Escalation Failure Instance
    I.1 requires paramount public safety, which mandates escalation after a client overrides safety concerns.
  • Engineer A Client Insistence or Project Withdrawal Safety Enforcement Failure
    I.1 requires holding public safety paramount, making failure to insist on remediation or withdraw a failure under this provision.
  • Engineer A Confidential Report Brief Mention Insufficiency Non-Recognition
    I.1 requires paramount public safety, meaning a brief confidential mention does not satisfy the obligation this provision imposes.
  • Engineer A Out-of-Discipline Code Violation Reporting Duty Activation Non-Recognition
    I.1 requires holding public safety paramount regardless of discipline, directly grounding the duty to report out-of-discipline code violations.
  • Engineer A Dual NSPE Code Provision Simultaneous Obligation Recognition Failure
    I.1 is one of the two simultaneously triggered provisions that Engineer A failed to recognize and apply together.
  • Engineer A Public Safety Escalation After Client Override Failure
    I.1 requires paramount public safety, which is the basis for the duty to escalate to authorities after a client override.
  • Engineer A Code Section Non-Vacuum Cross-Provision Integrated Reading Failure
    I.1 is the paramount safety provision that must be read in conjunction with III.4, and Engineer A failed to integrate them.
  • Engineer A BER Dual-Precedent Confidentiality Safety Synthesis
    I.1 is the paramount safety obligation that BER precedent cases apply, making its synthesis with confidentiality provisions necessary.
  • Engineer A Confidentiality Agreement Non-Excuse Safety Reporting Self-Recognition
    I.1 establishes that public safety is paramount, meaning a confidentiality agreement cannot excuse non-reporting of safety hazards.
  • Engineer A Confidentiality Agreement Scope Limitation for Safety Disclosure Non-Recognition
    I.1 requires paramount public safety, which limits the scope of any confidentiality agreement when public danger is present.
II.1.a. If engineers' judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate.
How this applies in the case (showing 3 of 59)
Obligation
Engineer A Post-Client-Override Public Safety Escalation Assessment
Section II.1.a directly requires engineers to notify appropriate authorities when their safety judgment is overruled by a client.
Action
Verbally Warning Client of Danger
Verbally warning the client is the act of notifying the employer or client when safety is endangered as required by this provision.
State
Engineer A Paramount Safety Obligation Notification Duty
This provision directly requires Engineer A to notify appropriate authorities when safety judgment is overruled by the client.
Obligation (10)
  • Engineer A Post-Client-Override Public Safety Escalation Assessment
    Section II.1.a directly requires engineers to notify appropriate authorities when their safety judgment is overruled by a client.
  • Engineer A Post-Client-Override Public Safety Escalation Failure
    Section II.1.a mandates notification of appropriate authority after client override, which Engineer A failed to perform.
  • Engineer A Appropriate Authority Notification After Client Safety Override Failure
    Section II.1.a explicitly requires notifying appropriate authorities when safety judgment is overruled, directly grounding this obligation.
  • Engineer A Out-of-Discipline Electrical Mechanical Code Violation Public Authority Reporting
    Section II.1.a requires reporting to appropriate authorities when safety judgment is overruled, regardless of whether the hazard is within the engineer's discipline.
  • Engineer A Brief Report Mention Insufficiency Public Authority Safety Notification
    Section II.1.a requires actual notification to appropriate authorities, making a brief mention in a confidential report insufficient.
  • Engineer A Brief Report Mention Insufficiency for Public Authority Safety Notification
    Section II.1.a mandates notification to appropriate authorities, which a confidential report mention does not satisfy.
  • Engineer A Going-Along After Client Safety Refusal Independent Ethical Violation
    Section II.1.a requires escalation to appropriate authorities when client overrules safety judgment, prohibiting silent going-along.
  • Engineer A Client-Disclosed Safety Hazard Out-of-Scope Reporting
    Section II.1.a requires reporting to appropriate authorities when safety judgment is overruled, applying even to out-of-scope hazards disclosed by the client.
  • Engineer A Confidentiality Agreement Non-Excuse Safety Code Violation Reporting
    Section II.1.a requires notification to appropriate authorities after client override, establishing that confidentiality does not excuse this reporting duty.
  • Case 84-5 Engineer Going-Along Without Dissent Analogous Violation
    Section II.1.a requires engineers to notify appropriate authorities when safety judgment is overruled, making the analogous engineer's silence a violation.
Action (3)
  • Verbally Warning Client of Danger
    Verbally warning the client is the act of notifying the employer or client when safety is endangered as required by this provision.
  • Declining to Report Violations Externally
    This provision requires notifying appropriate authorities when safety is endangered, making a decision to decline external reporting directly governed by it.
  • Documenting Conversation in Report
    Documenting the warning conversation supports the notification obligation required when judgment is overruled under dangerous circumstances.
State (7)
  • Engineer A Paramount Safety Obligation Notification Duty
    This provision directly requires Engineer A to notify appropriate authorities when safety judgment is overruled by the client.
  • Client As-Is Sale No Remediation Intent Active
    The client's as-is declaration constitutes overruling Engineer A's safety judgment, triggering the notification duty under II.1.a.
  • Engineer A Passive Acquiescence to Client Safety Refusal
    II.1.a requires active notification rather than passive continuation of work when safety judgment is overruled.
  • Engineer A Confidentiality vs. Public Safety Competing Duties
    II.1.a provides the specific mechanism for resolving this conflict by requiring notification to appropriate authorities.
  • Confidentiality Obligation vs. Occupant Safety Competing Duties
    II.1.a establishes that when life is endangered, notification to appropriate authority supersedes confidentiality concerns.
  • Engineer A Code-Based Confidentiality Exception Activation
    II.1.a is one of the code provisions whose exception clause releases Engineer A from strict confidentiality when safety is at risk.
  • Public Safety at Risk from Known Code Violations in Occupied Building
    The endangerment of occupants directly activates the notification requirement specified in II.1.a.
Constraint (10)
  • Engineer A Appropriate Authority Notification Post-Client-Safety-Override Failure
    Section II.1.a. directly requires notifying appropriate authority when the client overrules the engineer's judgment in ways that endanger life or property.
  • Engineer A Brief Report Mention Insufficiency Public Authority Safety Notification
    Section II.1.a. requires affirmative notification to appropriate authority, making a brief mention in a confidential report insufficient discharge of that obligation.
  • Engineer A Brief Report Mention Insufficiency for Public Authority Safety Notification
    Section II.1.a. mandates notification to appropriate authority, which a buried mention in a confidential structural report does not satisfy.
  • Engineer A Occupied Residential Building Electrical Mechanical Code Violation Occupant Injury Escalation
    Section II.1.a. requires escalation to appropriate public authority when the client refuses to address life-endangering code violations in an occupied building.
  • Engineer A Going-Along Without Dissent Independent Ethical Violation
    Section II.1.a. requires the engineer to notify appropriate authority rather than going along without dissent when safety is endangered.
  • Engineer A Non-Acquiescence Client As-Is Sale Economic Override Safety
    Section II.1.a. prohibits acquiescence by requiring notification to appropriate authority when the client's decision endangers life or property.
  • Engineer A Client-Directed Ethical Violation Non-Compliance As-Is Sale Suppression
    Section II.1.a. requires the engineer to notify appropriate authority rather than comply with client instructions that suppress safety-critical information.
  • Case 84-5 Engineer Going-Along Without Dissent Construction Phase
    Section II.1.a. requires notification to appropriate authority when judgment is overruled, which the engineer in Case 84-5 violated by going along without dissent.
  • Engineer A BER Case 84-5 Going-Along Precedent Cross-Domain Application
    Section II.1.a.'s notification requirement underpins the going-along prohibition applied by analogy from Case 84-5 to Engineer A's situation.
  • Engineer A Comprehensive Code Integration Confidentiality-Safety Conflict
    Section II.1.a. is one of the provisions Engineer A was required to integrate when resolving the confidentiality-safety conflict.
Principle (8)
  • Appropriate Authority Notification When Professional Judgment Overruled. Engineer A Obligation
    II.1.a. directly mandates notification of appropriate authority when judgment is overruled, which is the specific obligation Engineer A failed to meet.
  • Post-Client-Refusal Escalation Assessment Not Conducted By Engineer A
    II.1.a. requires escalation to appropriate authorities after the client overrules the engineer's safety concerns, which Engineer A failed to assess.
  • Post-Client-Refusal Escalation Assessment. Engineer A After As Is Sale Decision
    II.1.a. is the provision requiring Engineer A to evaluate escalation options after the client's as-is sale decision overruled his safety concerns.
  • Insistence on Remedial Action or Withdrawal Obligation Not Met By Engineer A
    II.1.a. supports the obligation to notify appropriate authorities when the client refuses remediation, which Engineer A failed to fulfill.
  • Insistence on Client Remedial Action or Withdrawal. Engineer A Obligation
    II.1.a. establishes the escalation pathway Engineer A was obligated to follow when the client refused to remediate code violations.
  • Competing Code Provision Contextual Balancing. III.4 vs. II.1.a. vs. II.1.c.
    II.1.a. is one of the three provisions explicitly balanced by the Board in resolving the confidentiality-safety conflict.
  • Client Notification Obligation Partially Discharged By Engineer A Brief Mention
    II.1.a. requires notification of employer or client when judgment is overruled, which Engineer A only partially discharged through a brief mention.
  • Passive Acquiescence After Safety Notification Independent Ethical Failure By Engineer A
    II.1.a. requires active notification steps beyond informing the client, making Engineer A's passive acquiescence an independent violation.
Role (3)
  • Engineer A Confidentiality-Bound Structural Safety Discovering Engineer
    Engineer A's judgment about safety violations being overruled by the client's as-is sale directive requires notifying appropriate authorities.
  • Engineer A Confidentiality-Bound Public Safety Inaction Engineer
    Engineer A failed to notify appropriate authorities when client directives overruled safety concerns, directly implicating this provision.
  • Case 84-5 Engineer Construction Phase Safety Recommendation Abandoning Engineer
    The engineer's safety recommendation was effectively overruled by the client, triggering the duty to notify appropriate authorities.
Event (3)
  • Occupants Remain Exposed to Hazard
    When occupants remain exposed to danger, the engineer is obligated to notify appropriate authorities if his judgment to address the hazard was overruled.
  • Electrical and Mechanical Violations Disclosed
    Disclosing violations to appropriate authorities is precisely the action required when life-endangering conditions are identified and not remedied.
  • Engineer A's Conduct Retrospectively Condemned
    Engineer A was condemned for failing to notify appropriate authorities as required when dangerous conditions endangered occupants.
Resource (5)
  • NSPE-Code-Section-II.1.a
    This provision is the source text directly represented by NSPE-Code-Section-II.1.a as cited in the case.
  • Engineer-Public-Safety-Escalation-Standard
    II.1.a directly governs the obligation to notify appropriate authorities when safety-endangering judgments are overruled.
  • Engineer-Safety-Recommendation-Rejection-Standard-Instance
    II.1.a applies when a client overrules an engineer's safety judgment, which is the scenario addressed by this standard instance.
  • BER-Case-84-5
    II.1.a is cited in conjunction with the precedent from BER-Case-84-5 regarding proceeding after client refusal of safety measures.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework-Instance
    II.1.a is read in conjunction with II.1.c to resolve the confidentiality-safety tension in the balancing framework instance.
Capability (10)
  • Engineer A Post-Client-Refusal Regulatory Escalation Assessment
    II.1.a directly requires notifying appropriate authorities when an engineer's judgment is overruled in ways that endanger life or property.
  • Engineer A Post-Client-Override Public Safety Escalation Failure Instance
    II.1.a requires escalation to appropriate authorities when a client overrides safety-related engineering judgment, which Engineer A failed to do.
  • Engineer A Public Safety Escalation After Client Override Failure
    II.1.a directly mandates notifying appropriate authorities after a client overrides safety concerns, making this failure a direct violation.
  • Engineer A Client Insistence or Withdrawal Safety Enforcement
    II.1.a supports the duty to take action including notifying authorities when the client refuses to address life-endangering conditions.
  • Engineer A Client Insistence or Project Withdrawal Safety Enforcement Failure
    II.1.a requires action when engineering judgment is overruled in dangerous circumstances, directly relating to the failure to insist or withdraw.
  • Engineer A Tenant Occupant Direct Notification Consideration
    II.1.a requires notifying such other authority as may be appropriate, which could include tenants or occupants facing danger.
  • Engineer A Going-Along Without Dissent Independent Ethical Violation Self-Recognition Failure
    II.1.a requires action when judgment is overruled in dangerous circumstances, making silent going-along a violation of this provision.
  • Engineer A BER Case 84-5 Going-Along Principle Cross-Context Analogical Application Failure
    II.1.a is the provision requiring notification when overruled, which the going-along principle in BER Case 84-5 directly implicates.
  • Case 84-5 Engineer Going-Along Without Dissent Analogous Violation Instance
    II.1.a requires action when engineering judgment is overruled in dangerous circumstances, which the Case 84-5 engineer violated by going along silently.
  • Engineer A Passive Acquiescence Independent Ethical Failure Recognition
    II.1.a requires active notification when overruled in dangerous circumstances, making passive acquiescence an independent failure under this provision.
II.1.c. Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code.
How this applies in the case (showing 3 of 53)
Obligation
Engineer A Section II.1.c. Exception Clause Non-Activation Violation
Section II.1.c directly contains the exception clause that Engineer A was obligated to recognize and apply to permit safety reporting.
Action
Declining to Report Violations Externally
This provision governs the decision not to reveal client information externally without consent, directly bearing on declining to report violations outside the organization.
State
Engineer A Confidentiality vs. Public Safety Competing Duties
II.1.c establishes the general confidentiality rule that creates the competing duty tension Engineer A faces.
Obligation (6)
  • Engineer A Section II.1.c. Exception Clause Non-Activation Violation
    Section II.1.c directly contains the exception clause that Engineer A was obligated to recognize and apply to permit safety reporting.
  • Engineer A Confidentiality Agreement Non-Excuse Safety Code Violation Reporting
    Section II.1.c contains the exception that releases engineers from confidentiality when required by law or the Code, making the confidentiality agreement non-excusing.
  • Engineer A Competing Confidentiality Safety Code Provision Contextual Balancing
    Section II.1.c is one of the competing provisions Engineer A was obligated to balance against confidentiality in determining reporting duties.
  • Engineer A Competing Confidentiality-Safety Code Provision Contextual Balancing Failure
    Section II.1.c provides the exception clause that should have been applied in the contextual balancing Engineer A failed to perform.
  • Engineer A Ethics Code Cross-Provision Non-Vacuum Reading Failure
    Section II.1.c is one of the cross-provisions Engineer A was obligated to read in conjunction with the confidentiality provision.
  • Engineer A Out-of-Discipline Electrical Mechanical Code Violation Public Authority Reporting
    Section II.1.c's exception clause authorizes disclosure required by the Code, supporting the obligation to report out-of-discipline safety violations.
Action (2)
  • Declining to Report Violations Externally
    This provision governs the decision not to reveal client information externally without consent, directly bearing on declining to report violations outside the organization.
  • Accepting Confidentiality Agreement
    Accepting a confidentiality agreement is directly governed by this provision which restricts revealing facts or data without prior client or employer consent.
State (7)
  • Engineer A Confidentiality vs. Public Safety Competing Duties
    II.1.c establishes the general confidentiality rule that creates the competing duty tension Engineer A faces.
  • Engineer A Code-Based Confidentiality Exception Activation
    II.1.c contains the exception clause allowing disclosure when authorized or required by law or the Code, activating Engineer A's disclosure right.
  • Confidentiality Instruction Suppressing Safety Report to Third Parties
    II.1.c is the code basis for the confidentiality instruction that suppresses disclosure to regulatory authorities.
  • Confidential Structural Engagement Agreement Active
    II.1.c codifies the confidentiality obligation that governs Engineer A's structural engagement and its findings.
  • Confidentiality Obligation vs. Occupant Safety Competing Duties
    II.1.c defines the confidentiality obligation side of the competing duties tension Engineer A must resolve.
  • Inspection-Discovered vs. Client-Disclosed Safety Information Distinction Active
    II.1.c's prohibition on revealing facts without consent is modulated by how the information was obtained, affecting its ethical weight.
  • Out-of-Scope Code Violation Disclosure in Occupied Building Sale
    II.1.c governs whether Engineer A may disclose the client-revealed code violation information to third parties.
Constraint (8)
  • Engineer A NSPE Code Section II.1.c Safety Exception Clause Confidentiality Override
    Section II.1.c. directly creates the exception clause that permits and requires disclosure when authorized or required by the Code, overriding general confidentiality.
  • Engineer A NSPE Code Section II.1.c. Exception Clause Confidentiality Release
    Section II.1.c. is the provision whose exception clause releases Engineer A from the confidentiality obligation when disclosure is Code-authorized.
  • Engineer A Confidentiality Non-Bar to Safety-Critical Regulatory Disclosure
    Section II.1.c.'s exception clause is the basis for concluding that confidentiality does not bar disclosure of safety-critical code violations.
  • Engineer A Confidentiality Agreement Non-Bar Safety Code Violation Reporting
    Section II.1.c. provides the code-authorized exception that prevents the contractual confidentiality agreement from barring safety violation reporting.
  • Engineer A Comprehensive Code Integration Confidentiality-Safety Conflict
    Section II.1.c. is one of the key provisions Engineer A was required to integrate when resolving the confidentiality-safety conflict.
  • Engineer A Code No-Direct-Exception Non-Absolute Interpretation
    Section II.1.c.'s exception clause informs the interpretation that Section III.4.'s absence of an explicit exception does not render confidentiality absolute.
  • Engineer A Client Confidentiality Reliance Factor Escalation Modulation Client-Confided Violations
    Section II.1.c. provides the code framework within which the client-confided nature of the violations modulates but does not eliminate the disclosure obligation.
  • Engineer A Client-Confided Out-of-Scope Safety Violation Confidentiality Weight Calibration
    Section II.1.c.'s exception clause is the provision against which the heightened confidentiality weight of client-confided violations must be calibrated.
Principle (9)
  • Confidentiality Principle Invoked By Engineer A Under Contractual Agreement
    II.1.c. is the provision Engineer A relied upon to justify non-disclosure, but its exception clause undermines that reliance.
  • Confidentiality Non-Applicability to Public Danger Disclosure Violated By Engineer A
    II.1.c.'s exception clause directly establishes that confidentiality does not apply when disclosure is required by the Code.
  • Code Exception Clause Activation Obligation Failed By Engineer A
    II.1.c. contains the exception clause Engineer A failed to recognize and activate when public safety required disclosure.
  • Code Exception Clause Activation. Section II.1.c. Releases Engineer A from Confidentiality
    II.1.c. is the specific provision whose exception clause the Board identifies as releasing Engineer A from confidentiality obligations.
  • Confidentiality Agreement Non-Supersession Principle Violated By Engineer A
    II.1.c.'s exception clause establishes that the Code itself can authorize disclosure, meaning the contractual agreement cannot supersede it.
  • Confidentiality Agreement Non-Supersession. Engineer A's Contractual Confidentiality vs. Imminent Danger
    II.1.c. provides the Code-based authorization for disclosure that overrides the contractual confidentiality agreement.
  • Competing Code Provision Contextual Balancing. III.4 vs. II.1.a. vs. II.1.c.
    II.1.c. is one of the three provisions explicitly balanced by the Board in resolving the confidentiality-safety conflict.
  • Client Direction Does Not Authorize Ethical Violation Applied To Engineer A Confidentiality Reliance
    II.1.c. establishes that Code-required disclosure overrides client direction, making Engineer A's reliance on client confidentiality directives improper.
  • Confidentiality Expectation Source-of-Information Distinction Applied in Case 82-2 Contrast
    II.1.c. is the provision whose exception clause applies differently depending on the source of information, relevant to the Case 82-2 distinction.
Role (3)
  • Engineer A Confidentiality-Bound Structural Safety Discovering Engineer
    Engineer A is bound by confidentiality but this provision governs when disclosure without consent may be authorized or required by the Code.
  • Engineer A Confidentiality-Bound Public Safety Inaction Engineer
    This provision governs Engineer A's handling of confidential safety information received during professional service delivery.
  • Client Confidential Safety Information Transmitting Client
    The client transmitted confidential information to Engineer A, and this provision governs the conditions under which that information may be disclosed.
Event (2)
  • Confidential Report Completed
    The confidential report represents information that generally cannot be revealed without client or employer consent except as the Code or law requires.
  • Electrical and Mechanical Violations Disclosed
    Disclosing the violations raises the question of whether revealing this information without client consent is permissible under the Code exception for safety.
Resource (6)
  • NSPE-Code-Section-II.1.c
    This provision is the source text directly represented by NSPE-Code-Section-II.1.c as cited in the case.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework
    II.1.c establishes the confidentiality duty and its exception, which is one side of the balancing framework.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework-Instance
    The Board interprets II.1.c alongside II.1.a to resolve the confidentiality-safety conflict in the specific framework instance.
  • BER-Case-85-4
    II.1.c is the provision that BER-Case-85-4 is cited as interpreting, though incompletely addressing the disclosure exception.
  • BER-Case-87-2
    II.1.c is the provision that BER-Case-87-2 is cited as interpreting, though incompletely addressing the disclosure exception.
  • NSPE-Code-of-Ethics
    II.1.c is a provision of the NSPE Code of Ethics governing Engineer A's confidentiality obligation and its exceptions.
Capability (10)
  • Engineer A Competing Confidentiality Safety Provision Balancing
    II.1.c contains the confidentiality obligation with an exception clause that must be balanced against the paramount safety obligation.
  • Engineer A NSPE Code Section II.1.c Exception Clause Non-Activation Failure
    II.1.c is the specific provision whose exception clause Engineer A failed to recognize and activate in the face of public danger.
  • Engineer A Confidentiality Non-Applicability Public Danger Assessment
    II.1.c's exception clause is directly relevant to assessing whether confidentiality applies when disclosure is required by the Code.
  • Engineer A Confidentiality Pre-emption by Public Safety
    II.1.c contains the exception that allows disclosure when required by the Code, directly supporting pre-emption by public safety.
  • Engineer A Code Section Non-Vacuum Cross-Provision Integrated Reading Failure
    II.1.c must be read in conjunction with I.1 to understand when its exception clause is triggered, which Engineer A failed to do.
  • Engineer A Dual NSPE Code Provision Simultaneous Obligation Recognition Failure
    II.1.c is one of the provisions simultaneously triggered alongside I.1 that Engineer A failed to recognize together.
  • Engineer A Confidentiality Agreement Non-Excuse Safety Reporting Self-Recognition
    II.1.c's exception clause establishes that Code-required disclosure overrides confidentiality, making the agreement an insufficient excuse.
  • Engineer A Confidentiality Agreement Scope Limitation for Safety Disclosure Non-Recognition
    II.1.c's exception clause limits the scope of confidentiality when disclosure is required by the Code, which Engineer A failed to recognize.
  • Engineer A BER Dual-Precedent Confidentiality Safety Synthesis
    II.1.c is a key provision in the confidentiality-versus-safety dilemma that BER precedent cases address and that must be synthesized.
  • Engineer A Client-Transmitted Confidential Information Section III.4 Engagement Boundary Identification
    II.1.c parallels III.4 in establishing confidentiality obligations and their limits, relevant to identifying when those obligations are engaged.
II.1.e. Engineers shall not aid or abet the unlawful practice of engineering by a person or firm.
How this applies in the case (showing 3 of 23)
Obligation
Engineer A Passive Acquiescence Known Safety Violation Independent Ethical Failure
Section II.1.e prohibits aiding unlawful practice, and passive acquiescence to known code violations could constitute aiding unlawful conduct.
Action
Declining to Report Violations Externally
Declining to report unlawful engineering practices could constitute aiding or abetting the unlawful practice of engineering, which this provision prohibits.
State
Engineer A Passive Acquiescence to Client Safety Refusal
By continuing work without addressing known code violations, Engineer A risks aiding conduct that may constitute unlawful practice or facilitation.
Obligation (3)
  • Engineer A Passive Acquiescence Known Safety Violation Independent Ethical Failure
    Section II.1.e prohibits aiding unlawful practice, and passive acquiescence to known code violations could constitute aiding unlawful conduct.
  • Engineer A Passive Acquiescence Independent Ethical Failure
    Section II.1.e prohibits aiding or abetting unlawful practice, which passive acquiescence to known building code violations may constitute.
  • Engineer A Going-Along After Client Safety Refusal Independent Ethical Violation
    Section II.1.e prohibits aiding unlawful engineering practice, and going along with known code violations without dissent implicates this prohibition.
Action (1)
  • Declining to Report Violations Externally
    Declining to report unlawful engineering practices could constitute aiding or abetting the unlawful practice of engineering, which this provision prohibits.
State (3)
  • Engineer A Passive Acquiescence to Client Safety Refusal
    By continuing work without addressing known code violations, Engineer A risks aiding conduct that may constitute unlawful practice or facilitation.
  • Domain-Specific Incompetence in Electrical and Mechanical Systems
    Engineer A opining or acting beyond structural licensure in electrical and mechanical domains could constitute aiding unlawful engineering practice.
  • Client As-Is Sale No Remediation Intent Active
    Facilitating a sale that conceals known code violations from buyers could constitute aiding unlawful conduct Engineer A is aware of.
Constraint (3)
  • Engineer A Passive Acquiescence Known Safety Violation Independent Ethical Failure
    Section II.1.e. prohibits aiding or abetting unlawful engineering practice, which passive acquiescence to known code violations implicates.
  • Engineer A Client-Directed Ethical Violation Non-Compliance As-Is Sale Suppression
    Section II.1.e. prohibits complying with client instructions that would aid or abet the unlawful suppression of known code violations.
  • Engineer A Going-Along Without Dissent Independent Ethical Violation
    Section II.1.e. supports the prohibition on going along without dissent by barring conduct that aids or abets unlawful engineering-related activity.
Principle (3)
  • Scope-of-Work Limitation Invoked As Incomplete Defense By Engineer A
    II.1.e. is implicated because Engineer A's passive acquiescence to known unlawful conditions could constitute aiding unlawful practice despite scope limitations.
  • Non-Acquiescence to Unsafe Client Directive Violated By Engineer A
    II.1.e. supports the principle that engineers must not aid unlawful activity, which Engineer A violated by acquiescing to the as-is sale with known code violations.
  • Passive Acquiescence Ethical Failure. Engineer A Going Along After Client Safety Refusal
    II.1.e. is implicated by Engineer A's passive continuation of work despite knowing the client intended to proceed with unlawful code violations unaddressed.
Role (2)
  • Engineer A Confidentiality-Bound Public Safety Inaction Engineer
    By remaining silent about code violations, Engineer A risks aiding the building owner in conducting transactions that involve unlawful conditions.
  • Building Owner Selling As-Is Client
    Selling a building with known code violations as-is may constitute unlawful practice that an engineer must not aid or abet.
Event (1)
  • Engineer A's Conduct Retrospectively Condemned
    If Engineer A's silence enabled unlawful building conditions to persist, his conduct could be seen as aiding unlawful practice, contributing to the condemnation of his actions.
Resource (2)
  • Applicable-Building-Electrical-Mechanical-Codes-and-Standards
    II.1.e prohibits aiding unlawful practice, which is directly implicated when the client acknowledges code violations in electrical and mechanical systems.
  • Out-of-Scope-Safety-Finding-Reporting-Standard
    II.1.e is relevant because remaining silent about known code violations could constitute aiding unlawful practice even when findings are outside scope.
Capability (5)
  • Engineer A Passive Acquiescence Independent Ethical Failure Recognition
    II.1.e prohibits aiding or abetting unlawful practice, and passive acquiescence to known code violations could constitute such aiding.
  • Engineer A Going-Along Without Dissent Independent Ethical Violation Self-Recognition Failure
    II.1.e prohibits aiding unlawful engineering practice, making silent going-along with known code violations a potential violation of this provision.
  • Engineer A Out-of-Discipline Code Violation Reporting Duty Activation Non-Recognition
    II.1.e prohibits aiding unlawful practice, which is relevant when an engineer fails to report known code violations that constitute unlawful conditions.
  • Case 84-5 Engineer Going-Along Without Dissent Analogous Violation Instance
    II.1.e prohibits aiding unlawful practice, and the Case 84-5 engineer's silent going-along with dangerous conditions implicates this provision.
  • Engineer A BER Case 84-5 Going-Along Principle Cross-Context Analogical Application Failure
    II.1.e's prohibition on aiding unlawful practice is part of the ethical framework underlying the going-along principle in BER Case 84-5.
II.4. Engineers shall act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 34)
Obligation
Engineer A Faithful Agent Role Misapplication to Confidentiality Absolutism
Section II.4 defines the faithful agent role that Engineer A misapplied by treating it as requiring absolute confidentiality over safety reporting.
Action
Accepting Confidentiality Agreement
Accepting a confidentiality agreement reflects acting as a faithful agent or trustee of the employer or client as required by this provision.
State
Client Relationship Established Under Confidential Structural Engagement
II.4 establishes Engineer A's duty to act as a faithful agent or trustee within the professional relationship with the building owner.
Obligation (4)
  • Engineer A Faithful Agent Role Misapplication to Confidentiality Absolutism
    Section II.4 defines the faithful agent role that Engineer A misapplied by treating it as requiring absolute confidentiality over safety reporting.
  • Engineer A As-Is Sale Directive Safety Reporting Non-Override
    Section II.4 defines the faithful agent role, which does not extend to following client directives that violate paramount safety obligations.
  • Engineer A Competing Confidentiality Safety Code Provision Contextual Balancing
    Section II.4 establishes the faithful agent duty that must be contextually balanced against the paramount safety obligation.
  • Engineer A Competing Confidentiality-Safety Code Provision Contextual Balancing Failure
    Section II.4 defines the faithful agent role whose limits Engineer A failed to recognize when balancing confidentiality against safety.
Action (2)
  • Accepting Confidentiality Agreement
    Accepting a confidentiality agreement reflects acting as a faithful agent or trustee of the employer or client as required by this provision.
  • Documenting Conversation in Report
    Documenting findings and conversations in a report is consistent with acting as a faithful agent by keeping the employer or client properly informed.
State (4)
  • Client Relationship Established Under Confidential Structural Engagement
    II.4 establishes Engineer A's duty to act as a faithful agent or trustee within the professional relationship with the building owner.
  • Engineer A Confidentiality vs. Public Safety Competing Duties
    The faithful agent duty to the client is one side of the tension competing against Engineer A's public safety obligations.
  • Confidential Structural Engagement Agreement Active
    II.4 underpins Engineer A's obligation to honor the terms of the confidential structural engagement as a faithful trustee.
  • Engineer A Client Cost-Driven Safety Oversight Rejection (Case 84-5 Analogy)
    The faithful agent duty is implicated when the client overrides Engineer A's professional recommendations, as in the analogous Case 84-5 scenario.
Constraint (4)
  • Engineer A Agent-Trustee Confidentiality Rationale Non-Absolutism
    Section II.4. establishes the faithful agent/trustee duty whose confidentiality rationale Engineer A was constrained from invoking absolutely against public safety.
  • Engineer A Confidential Client Information Electrical Mechanical Violation Disclosure Boundary
    Section II.4.'s faithful agent duty creates part of the boundary constraining Engineer A's ability to disclose client-confided information to third parties.
  • Engineer A Client Confidentiality Reliance Factor Escalation Modulation Client-Confided Violations
    Section II.4.'s agent/trustee obligation is the basis for the strong confidentiality reliance factor when violations are client-confided rather than independently observed.
  • Engineer A Comprehensive Code Integration Confidentiality-Safety Conflict
    Section II.4. is one of the provisions Engineer A was required to integrate when resolving the tension between client loyalty and public safety obligations.
Principle (4)
  • Faithful Agent Obligation Within Ethical Limits Misapplied By Engineer A
    II.4. is the faithful agent provision that Engineer A misapplied by treating client loyalty as overriding his public safety obligations.
  • Client Direction Does Not Authorize Ethical Violation Applied To Engineer A Confidentiality Reliance
    II.4. establishes faithful agent duty but does not authorize ethical violations, which Engineer A failed to recognize when following client directives.
  • Confidentiality Agreement Non-Supersession Principle Violated By Engineer A
    II.4. defines the faithful agent role within ethical limits, meaning the confidentiality agreement cannot extend beyond those limits.
  • Non-Acquiescence to Unsafe Client Directives. Engineer A Should Have Refused to Continue
    II.4. requires faithful service within ethical bounds, supporting the obligation to refuse client directives that violate public safety duties.
Role (4)
  • Engineer A Confidentiality-Bound Structural Safety Discovering Engineer
    Engineer A must act as a faithful agent to the building owner client while balancing that duty against overriding public safety obligations.
  • Engineer A Confidentiality-Bound Public Safety Inaction Engineer
    Engineer A's role as faithful agent to the client is directly implicated when deciding whether to disclose or withhold safety findings.
  • Case 84-5 Engineer Construction Phase Safety Recommendation Abandoning Engineer
    The engineer's duty as faithful agent required following through on safety recommendations rather than abandoning them under client pressure.
  • Case 84-5 Client Cost-Objecting Safety Staffing Refusing Client
    This provision governs the engineer's obligation to serve this client faithfully while not compromising safety duties.
Event (2)
  • Client Retains Engineer A
    The client-engineer relationship established by retaining Engineer A creates the faithful agent duty that governs his subsequent obligations.
  • Confidential Report Completed
    Completing the report for the client reflects Engineer A acting as a faithful agent or trustee in carrying out the assigned work.
Resource (5)
  • NSPE-Code-Section-II.4
    This provision is the source text directly represented by NSPE-Code-Section-II.4 as cited in the case.
  • Agent-Trustee-Distinction-Framework-Instance
    II.4 establishes the faithful agent/trustee characterization of the engineer-client relationship that the Board invokes to explain non-disclosure obligations.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework-Instance
    The Board cites II.4 as establishing the confidentiality obligation that must be balanced against the paramount safety duty.
  • BER-Case-61-8
    II.4 is one of the provisions that BER-Case-61-8 is cited as interpreting in the context of employer confidence obligations.
  • BER-Case-82-2
    II.4 is cited alongside III.4 in the context of client confidentiality precedent that BER-Case-82-2 addresses.
Capability (5)
  • Engineer A Faithful Agent Role Confidentiality Absolutism Misapplication
    II.4 establishes the faithful agent and trustee role that Engineer A misapplied to justify absolute confidentiality over public safety.
  • Engineer A As-Is Sale Directive Safety Non-Override Recognition
    II.4 requires acting as a faithful agent, but this role does not extend to following client directives that endanger public safety.
  • Engineer A Competing Confidentiality Safety Provision Balancing
    II.4's faithful agent obligation is one of the competing duties that must be balanced against the paramount public safety obligation.
  • Engineer A BER Dual-Precedent Confidentiality Safety Synthesis
    II.4's faithful agent role is part of the dual-obligation framework that BER precedent cases address in the confidentiality-safety dilemma.
  • Engineer A Dual NSPE Code Provision Simultaneous Obligation Recognition Failure
    II.4's faithful agent role is among the obligations simultaneously triggered that Engineer A failed to properly recognize and integrate.
III.4. Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve.
How this applies in the case (showing 3 of 46)
Obligation
Engineer A Section III.4 Client-Transmitted Confidentiality Engagement Recognition
Section III.4 is the confidentiality provision directly engaged by the client-disclosed electrical and mechanical deficiency information.
Action
Accepting Confidentiality Agreement
Accepting a confidentiality agreement directly aligns with this provision prohibiting disclosure of confidential business or technical information without consent.
State
Engineer A Confidentiality vs. Public Safety Competing Duties
III.4 establishes the confidentiality obligation that directly competes with Engineer A's public safety duties.
Obligation (8)
  • Engineer A Section III.4 Client-Transmitted Confidentiality Engagement Recognition
    Section III.4 is the confidentiality provision directly engaged by the client-disclosed electrical and mechanical deficiency information.
  • Engineer A Competing Confidentiality Safety Code Provision Contextual Balancing
    Section III.4 is the confidentiality provision that must be contextually balanced against the paramount safety obligation.
  • Engineer A Competing Confidentiality-Safety Code Provision Contextual Balancing Failure
    Section III.4 is the confidentiality provision whose weight Engineer A incorrectly treated as absolute in the balancing analysis.
  • Engineer A Ethics Code Cross-Provision Non-Vacuum Reading Failure
    Section III.4 is the confidentiality provision that Engineer A was obligated to read in conjunction with safety provisions rather than in isolation.
  • Engineer A Confidentiality Agreement Non-Excuse Safety Code Violation Reporting
    Section III.4 establishes the confidentiality obligation whose limits Engineer A was required to recognize when safety reporting was required.
  • Engineer A Faithful Agent Role Misapplication to Confidentiality Absolutism
    Section III.4 is the confidentiality provision that Engineer A misapplied by treating it as an absolute bar to safety reporting.
  • Engineer A Scope of Work Non-Shield Electrical Mechanical Safety Disclosure
    Section III.4 establishes confidentiality obligations that Engineer A incorrectly used as a shield alongside scope-of-work arguments against disclosure.
  • Engineer A Client-Disclosed Safety Hazard Out-of-Scope Reporting
    Section III.4 is the confidentiality provision whose exception clause applies to client-disclosed safety hazards requiring reporting regardless of scope.
Action (2)
  • Accepting Confidentiality Agreement
    Accepting a confidentiality agreement directly aligns with this provision prohibiting disclosure of confidential business or technical information without consent.
  • Declining to Report Violations Externally
    Declining to report externally may be governed by this provision protecting confidential client information from unauthorized disclosure.
State (8)
  • Engineer A Confidentiality vs. Public Safety Competing Duties
    III.4 establishes the confidentiality obligation that directly competes with Engineer A's public safety duties.
  • Engineer A Code-Based Confidentiality Exception Activation
    III.4 is explicitly cited as one of the provisions whose structure informs whether a confidentiality exception applies in this case.
  • Confidential Structural Engagement Agreement Active
    III.4 codifies the non-disclosure obligation covering the business affairs and technical findings of Engineer A's engagement.
  • Confidentiality Instruction Suppressing Safety Report to Third Parties
    III.4 is the code provision underlying the confidentiality instruction that prevents Engineer A from reporting to regulatory authorities.
  • Confidentiality Obligation vs. Occupant Safety Competing Duties
    III.4 defines the confidentiality obligation side of the ethical tension Engineer A must navigate regarding occupant safety.
  • Inspection-Discovered vs. Client-Disclosed Safety Information Distinction Active
    III.4's confidentiality protection applies to information concerning the client's business affairs, and its weight varies based on how information was obtained.
  • Client Relationship Established Under Confidential Structural Engagement
    III.4 governs the non-disclosure obligations arising from Engineer A's professional relationship with the building owner.
  • Out-of-Scope Code Violation Disclosure in Occupied Building Sale
    III.4 is the provision that would restrict Engineer A from disclosing the client-revealed code violation information without consent.
Constraint (10)
  • Engineer A Section III.4 Client-Transmitted Confidentiality Full Engagement
    Section III.4. is the provision whose confidentiality obligation was fully engaged when the client affirmatively transmitted information about the code violations.
  • Engineer A Confidential Client Information Electrical Mechanical Violation Disclosure Boundary
    Section III.4. directly creates the confidentiality constraint on Engineer A's ability to disclose client-confided information to third parties.
  • Engineer A Code No-Direct-Exception Non-Absolute Interpretation
    Section III.4. is the provision whose absence of an explicit exception clause Engineer A was constrained from treating as rendering confidentiality absolute.
  • Engineer A Agent-Trustee Confidentiality Rationale Non-Absolutism
    Section III.4. embodies the confidentiality obligation whose agent/trustee rationale Engineer A could not invoke absolutely against public safety.
  • Engineer A Paramount Safety Normative Hierarchy Confidentiality Subordination
    Section III.4. is the confidentiality provision that is subordinated in the normative hierarchy by Section I.1.'s paramount safety mandate.
  • Engineer A Confidentiality Non-Bar to Safety-Critical Regulatory Disclosure
    Section III.4. is the confidentiality provision that does not bar disclosure of safety-critical code violations when read in conjunction with the full Code.
  • Engineer A Confidentiality Agreement Non-Bar Safety Code Violation Reporting
    Section III.4. is the code-based confidentiality obligation that, like the contractual agreement, does not bar reporting of safety code violations.
  • Engineer A Client-Confided Out-of-Scope Safety Violation Confidentiality Weight Calibration
    Section III.4. is the provision whose confidentiality weight is heightened when violations are client-confided rather than independently observed.
  • Engineer A Client Confidentiality Reliance Factor Escalation Modulation Client-Confided Violations
    Section III.4. creates the confidentiality obligation that generates the strong reliance factor when violations are client-confided.
  • Engineer A Comprehensive Code Integration Confidentiality-Safety Conflict
    Section III.4. is the confidentiality provision that must be integrated with Sections I.1. and II.1.c. to resolve the confidentiality-safety conflict.
Principle (7)
  • Confidentiality Principle Invoked By Engineer A Under Contractual Agreement
    III.4. is the confidentiality provision Engineer A invoked to justify not reporting the code violations to third parties.
  • Confidentiality Principle Engaged by Client Transmission to Engineer A
    III.4. is fully engaged because the client directly transmitted confidential business information to Engineer A during the engagement.
  • Confidentiality Source-of-Information Distinction Applied To Client Voluntary Disclosure
    III.4. applies because the client voluntarily disclosed the deficiency information to Engineer A, triggering the confidentiality obligation under this provision.
  • Confidentiality Expectation Source-of-Information Distinction Applied in Case 82-2 Contrast
    III.4. is the provision whose applicability differs based on how the engineer obtained the information, central to the Case 82-2 distinction.
  • Competing Code Provision Contextual Balancing. III.4 vs. II.1.a. vs. II.1.c.
    III.4. is one of the three provisions explicitly balanced by the Board against the public safety and exception clause provisions.
  • Confidentiality Non-Applicability to Public Danger Disclosure Violated By Engineer A
    III.4. is the confidentiality provision whose limits are at issue when Engineer A failed to disclose dangerous conditions to appropriate authorities.
  • Confidentiality Agreement Non-Supersession. Engineer A's Contractual Confidentiality vs. Imminent Danger
    III.4. establishes the confidentiality obligation that the Board finds does not supersede the professional duty to disclose imminent danger.
Role (3)
  • Engineer A Confidentiality-Bound Structural Safety Discovering Engineer
    Engineer A is bound by a confidentiality agreement and this provision governs the duty not to disclose the client's confidential business information without consent.
  • Engineer A Confidentiality-Bound Public Safety Inaction Engineer
    This provision directly governs Engineer A's handling of confidential information received from the client during professional service.
  • Client Confidential Safety Information Transmitting Client
    The client's transmitted confidential information is protected under this provision, defining the scope of Engineer A's non-disclosure obligation.
Event (2)
  • Confidential Report Completed
    The completed confidential report contains client information that Engineer A is obligated not to disclose without consent under this provision.
  • Electrical and Mechanical Violations Disclosed
    Disclosing the violations found in the confidential report raises a direct tension with the duty not to reveal confidential client information without consent.
Resource (6)
  • NSPE-Code-Section-III.4
    This provision is the source text directly represented by NSPE-Code-Section-III.4 as the primary non-disclosure obligation provision.
  • Agent-Trustee-Distinction-Framework-Instance
    III.4 is the primary provision establishing non-disclosure obligations that the agent/trustee framework is invoked to explain.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework
    III.4 establishes the confidentiality duty concerning client business affairs that forms one side of the balancing framework.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework-Instance
    The Board cites III.4 as the primary confidentiality provision being balanced against the paramount safety obligation.
  • BER-Case-61-8
    III.4 is one of the provisions that BER-Case-61-8 is cited as interpreting regarding employer confidence obligations.
  • BER-Case-82-2
    III.4 is the provision whose client confidentiality obligation BER-Case-82-2 reaffirmed in the home inspection context.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 3 Lineage Graph

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

Section III.4 relates to confidential information given by the client to the engineer in the course of providing services; where no such transmission occurs, the confidentiality obligation under that section is not triggered.

Citation Context:

Cited to illustrate the principle of client confidentiality in private practice, and to distinguish it from the present case because in Case 82-2 there was no transmission of confidential information by the client to the engineer, whereas in the present case there was.

Relevant Excerpts
discussion: "in Case 82-2, an engineering consultant performed home inspection services for a prospective purchaser of a residence and thereafter disclosed the contents of the report to the real estate firm"
discussion: "In Case 82-2, there was no transmission of confidential information by the client to the engineer."

Principle Established:

When a client refuses to adopt safety measures the engineer believes are necessary to prevent danger, the engineer must either insist on those measures or refuse to continue work on the project rather than acquiescing.

Citation Context:

Cited by analogy to illustrate that an engineer who 'goes along' with a client's decision that endangers public safety, rather than insisting on safety measures or withdrawing, acts unethically.

Relevant Excerpts
discussion: "Case 84-5 involved a client who planned a project and hired an engineer to furnish complete engineering services for the project. Because of the potentially dangerous nature of implementing the design"
discussion: "We believe much of the same reasoning applies in the present case. Under the reasoning of Case 84-5, the engineer had an obligation to go further."
discussion: "Engineer A, like the engineer in Case 84-5, "went along" and proceeded with the work on behalf of the client. His conduct cannot be condoned under the Code."

Principle Established:

Section II.1.c has been interpreted by the Board in the context of an engineer's obligation regarding disclosure of information acquired during professional services.

Citation Context:

Cited as one of three cases in which the Board interpreted Section II.1.c, though the Board notes none of these cases fully outlined the scope of that section.

Relevant Excerpts
discussion: "The Board has interpreted Section II.1.c. on three different occasions (Cases 82-2, 85-4, 87-2) but in none of those cases has the Board outlined the scope of the Code section."

Principle Established:

Engineers have an ethical obligation to maintain the confidentiality of information made available to them during the course of employment.

Citation Context:

Cited as an early example of the Board interpreting confidentiality obligations under Sections II.4 and III.4 in the context of employed engineers maintaining confidences of their employer.

Relevant Excerpts
discussion: "the obligations of employed engineers to maintain the confidences of their employer particularly with regard to certain confidential information which might be made available to the engineer during the course of employment as in Case 61-8"

Principle Established:

Section II.1.c has been interpreted by the Board in the context of an engineer's obligation regarding disclosure of information acquired during professional services.

Citation Context:

Cited as one of three cases in which the Board interpreted Section II.1.c, though the Board notes none of these cases fully outlined the scope of that section.

Relevant Excerpts
discussion: "The Board has interpreted Section II.1.c. on three different occasions (Cases 82-2, 85-4, 87-2) but in none of those cases has the Board outlined the scope of the Code section."
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 71% Facts Similarity 78% Discussion Similarity 58% Provision Overlap 38% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1, II.1.a Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 55% Discussion Similarity 58% Provision Overlap 43% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1, II.1.a Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 48% Discussion Similarity 72% Provision Overlap 43% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.a, III.4 Same outcome True View Synthesis
Component Similarity 61% Facts Similarity 63% Discussion Similarity 50% Provision Overlap 38% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1, II.1.a Same outcome True View Synthesis
Component Similarity 56% Facts Similarity 46% Discussion Similarity 66% Provision Overlap 38% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1, II.1.a Same outcome True View Synthesis
Component Similarity 62% Facts Similarity 76% Discussion Similarity 41% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1, II.1.a Same outcome True View Synthesis
Component Similarity 57% Facts Similarity 43% Discussion Similarity 65% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 57%
Shared provisions: I.1, II.1, II.1.a, III.4 Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 55% Discussion Similarity 36% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.a, III.4 Same outcome True View Synthesis
Component Similarity 56% Facts Similarity 56% Discussion Similarity 54% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1.a Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 48% Discussion Similarity 56% Provision Overlap 30% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1, II.1.a Same outcome True View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

Was it ethical for Engineer A not to report the safety violations to the appropriate public authorities?

Board conclusion It was unethical for Engineer A not to report the safety violations to the appropriate public authorities.
Implicit (4)

Does the fact that the safety-critical information was voluntarily disclosed by the client - rather than independently discovered by Engineer A - reduce, eliminate, or actually strengthen Engineer A's obligation to report it to public authorities?

AnalyticalThe Board's conclusion that reporting was ethically required is strengthened - not weakened - by the fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A during inspection. Section I.1's public safety obligation is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. A client's voluntary disclosure does not transform dangerous information into protected business intelligence; it simply means the engineer received confirmed, first-hand knowledge of a life-safety hazard directly from the party responsible for it. If anything, client-transmitted disclosure eliminates the epistemic uncertainty that might otherwise justify caution before reporting, because the engineer need not rely on inference or indirect evidence - the client has affirmatively confirmed the violations exist. The source of the information therefore strengthens rather than modulates the reporting obligation.
AnalyticalThe fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A does not reduce - and may actually strengthen - Engineer A's reporting obligation. The NSPE Code's paramount safety duty in Section I.1 is framed in terms of the engineer's knowledge of danger, not the source of that knowledge. Once Engineer A possessed actual knowledge that occupants of an occupied building faced injury from known code violations, the ethical trigger was complete regardless of how that knowledge was acquired. If anything, the client's voluntary disclosure eliminated any ambiguity about whether the violations existed, removing the epistemic uncertainty that might otherwise counsel caution before reporting. The argument that client-confided information deserves heightened confidentiality protection under Section III.4 is not without force, but it cannot override the explicit exception in Section II.1.c, which releases engineers from confidentiality obligations precisely when public danger is present. The source of the information is therefore ethically irrelevant to the reporting threshold; it is relevant only to the weight of the confidentiality interest being overridden, and even that interest is expressly subordinated by the Code when safety is at stake.

Was Engineer A's brief mention of the electrical and mechanical deficiencies in his confidential structural report a meaningful discharge of any ethical obligation, or did it create a false appearance of compliance while ensuring the information would never reach those who needed it - the occupants or public authorities?

AnalyticalEngineer A's brief mention of the electrical and mechanical deficiencies within a confidential structural report constitutes a procedural gesture that affirmatively failed to discharge any meaningful ethical obligation. By embedding safety-critical information in a document contractually shielded from third-party disclosure, Engineer A created a record of awareness while simultaneously ensuring that the parties most exposed to the hazard - the building's current occupants - and the regulatory authorities empowered to act on it would never receive the information. This is not a partial discharge of the notification duty; it is a form of ethical concealment dressed as disclosure. The NSPE Code's public safety obligation under Section I.1 and the notification duty under Section II.1.a are directed at outcomes - specifically, that endangered parties receive actionable information - not at the mere creation of internal documentation. A confidential mention satisfies neither the letter nor the spirit of those provisions.
AnalyticalEngineer A's brief mention of the electrical and mechanical deficiencies in his confidential structural report did not constitute a meaningful discharge of any ethical obligation to protect public safety. On the contrary, it created a false appearance of compliance - a record that Engineer A had 'noted' the violations - while structurally ensuring that the information would never reach the parties who needed it most: the building's current occupants and the public authorities responsible for enforcing safety codes. A disclosure that is deliberately confined to a document the client controls, that no regulator will ever see, and that no occupant will ever read is functionally equivalent to no disclosure at all from a public safety standpoint. The NSPE Code's obligation under Section II.1.a requires notification to appropriate authorities when professional judgment is overruled under circumstances that endanger life or property. A notation in a confidential report addressed to the party who has already refused remediation satisfies none of the elements of that obligation: it reaches no authority, it triggers no regulatory response, and it protects no occupant. The brief mention therefore represents a procedural gesture that obscures rather than discharges the substantive ethical duty.

Given that Engineer A is a structural engineer without competence in electrical or mechanical systems, does his professional incompetence in those domains diminish his reporting obligation, or does the threshold for triggering a public safety duty require only that he recognize a risk of injury - not that he be able to evaluate it technically?

AnalyticalEngineer A's lack of competence in electrical and mechanical engineering does not diminish the reporting obligation and may not be invoked as a scope-of-work defense. The threshold for triggering the public safety duty under Section I.1 requires only that the engineer recognize a risk of injury - not that the engineer be technically qualified to evaluate, quantify, or remediate it. Engineer A explicitly acknowledged recognizing that the disclosed deficiencies could cause injury to occupants. That recognition alone activated the reporting duty. The competence boundary argument, if accepted, would produce an absurd result: engineers would be ethically insulated from reporting known dangers simply because those dangers fall outside their primary discipline. The Code contains no such carve-out, and the Board's precedents in analogous cases confirm that out-of-scope safety findings carry independent disclosure obligations. Engineer A's disciplinary limitations were relevant to the scope of his remediation authority - they were irrelevant to his obligation to notify public authorities of a known hazard.
AnalyticalEngineer A's lack of competence in electrical and mechanical engineering does not diminish his obligation to report the known code violations to public authorities. The threshold for triggering a public safety reporting duty under the NSPE Code requires only that the engineer recognize a risk of injury to the public - not that he be technically qualified to evaluate, diagnose, or remediate the hazard. Engineer A himself acknowledged that the disclosed deficiencies 'could cause injury to the occupants,' which means the recognition threshold was met by his own assessment. The scope-of-work and domain-competence arguments function as incomplete defenses at best: they might limit Engineer A's authority to demand specific corrective measures or to certify the severity of the violations, but they do not limit his capacity to convey to a public authority that a client has disclosed the existence of code violations in an occupied building. Reporting what one knows to those with the competence and authority to investigate is precisely the appropriate response when an engineer encounters a hazard outside his discipline. Domain incompetence is therefore a reason to escalate to qualified authorities, not a reason to remain silent.
AnalyticalEngineer A's domain incompetence in electrical and mechanical engineering does not diminish his reporting obligation, and this case establishes an important principle about the threshold for triggering a public safety duty: recognition of injury risk, not technical competence to evaluate it, is the operative standard. Engineer A himself acknowledged that the disclosed deficiencies could cause injury to occupants - that acknowledgment is precisely the threshold event. The duty to hold public safety paramount does not require the engineer to be able to diagnose, quantify, or remediate the hazard; it requires only that the engineer recognize that a hazard exists and that persons are exposed to it. Requiring technical competence as a precondition for reporting would perversely insulate engineers from safety obligations in exactly those situations where they are most dependent on others' expertise - and would allow scope-of-work boundaries to function as shields against accountability. This case teaches that the faithful agent role under Section II.4 is bounded by ethical limits, and that those limits include the obligation not to allow disciplinary boundaries to suppress safety-critical information from reaching appropriate authorities.

Did Engineer A have an independent ethical obligation to notify the building's current occupants directly of the known code violations, separate from any duty to report to regulatory or public authorities, given that the occupants are the parties most immediately exposed to the hazard?

AnalyticalEngineer A had an independent ethical obligation to consider notifying the building's current occupants directly of the known code violations, separate from any duty to report to regulatory or public authorities. The occupants of the 60-year-old apartment building are the parties most immediately and continuously exposed to the hazard: they live within it, they cannot protect themselves from dangers they do not know exist, and they have no contractual relationship with Engineer A that would generate any competing confidentiality interest. While the NSPE Code's explicit reporting pathway runs through 'appropriate public authorities' under Section II.1.a, the paramount safety obligation in Section I.1 is not exhausted by that single channel. When regulatory reporting is the most effective route, it should be pursued; but when occupants are immediately at risk and regulatory response may be delayed, direct notification to those at risk is consistent with - and may be required by - the spirit of the paramount safety obligation. Engineer A's failure to consider this pathway represents an additional dimension of ethical shortcoming beyond the failure to notify authorities.
Cross-cutting analytical questions (12)

These questions consider the case as a whole rather than a specific board question above.

Principle tension (4)

Does the principle that an engineer must act as a faithful agent or trustee of the client conflict with the principle that public safety is paramount and that confidentiality agreements cannot supersede the duty to prevent imminent danger - and if so, which principle controls and under what conditions?

AnalyticalThe conflict between the faithful agent principle under Section II.4 and the paramount safety obligation under Section I.1 is resolved unambiguously by the NSPE Code's own internal hierarchy: public safety is explicitly designated as paramount, meaning it takes precedence over all other duties including client loyalty and confidentiality. The faithful agent role is not absolute - it is expressly conditioned on the engineer acting 'within ethical limits,' and those limits are defined in part by the safety obligations in Sections I.1 and II.1.a. The condition that triggers the override is not merely theoretical danger but actual knowledge of a hazard that could cause injury to occupants, which Engineer A possessed. Engineer A's misapplication of the faithful agent principle as a basis for confidentiality absolutism therefore represents a category error: he treated a conditional, subordinate duty as though it were unconditional and supreme. The principle that controls is public safety, and the condition under which it controls is precisely the one present in this case - known, code-violating hazards in an occupied building.
AnalyticalThe tension between client confidentiality and public safety was not genuinely unresolvable in this case - it was falsely treated as such by Engineer A. The NSPE Code does not present these principles as equals requiring ad hoc balancing; it establishes a normative hierarchy in which public safety is explicitly paramount. Section I.1 places the safety, health, and welfare of the public at the apex of engineering obligation, and Section II.1.c contains an explicit exception clause that releases engineers from confidentiality duties precisely when public danger is present. Engineer A's error was not a failure of judgment in a genuinely ambiguous situation but a failure to recognize that the Code had already resolved the tension in advance. By treating confidentiality as an absolute constraint capable of overriding a known life-safety hazard in an occupied building, Engineer A inverted the Code's own priority structure. This case teaches that when the Code itself contains an exception clause addressing the exact conflict an engineer faces, invoking the general confidentiality rule while ignoring the exception is not a defensible ethical position - it is a misreading of the Code's architecture.

Does the principle that confidentiality does not apply when public danger is present conflict with the principle that client-transmitted confidential information carries its own distinct confidentiality weight under Section III.4 - and does the source of the information (client disclosure versus independent discovery) legitimately modulate the engineer's reporting threshold?

AnalyticalBeyond the Board's finding that Engineer A's failure to report was unethical, the confidentiality agreement itself cannot bear the interpretive weight Engineer A assigned to it. Section II.1.c expressly releases engineers from confidentiality obligations when public danger is present, meaning the contractual arrangement never legally or ethically foreclosed disclosure to public authorities. Engineer A's reliance on the confidentiality agreement as a complete bar to external reporting therefore reflects a fundamental misreading of the NSPE Code's internal hierarchy: the agreement was a valid constraint on routine business disclosures, but it was categorically inapplicable to life-safety code violations in an occupied residential building. The ethical failure was not merely that Engineer A chose confidentiality over safety - it was that Engineer A treated a conditional obligation as an absolute one, never activating the exception clause the Code explicitly provides.
AnalyticalThe tension between Section III.4's protection of client-transmitted confidential information and Section II.1.c's explicit exception releasing engineers from confidentiality when public danger is present is resolved by reading the Code as an integrated normative system rather than a collection of isolated provisions. Section III.4 establishes a genuine confidentiality obligation that applies to business affairs and technical processes disclosed by clients, and the fact that the client voluntarily confided the violations to Engineer A does carry some weight in calibrating the confidentiality interest at stake. However, Section II.1.c is not a general provision - it is a specific exception clause that was drafted precisely to address the situation where confidentiality and public danger collide. Specific exception clauses override general rules in any coherent normative system. Moreover, the source of the information (client disclosure versus independent discovery) may modulate the weight of the confidentiality interest, but it cannot eliminate the operation of an explicit exception clause. Engineer A's failure to activate Section II.1.c therefore cannot be justified by appeal to Section III.4, because the Code itself resolves that conflict in favor of disclosure when danger to the public is present.
AnalyticalThe source of the hazardous information - client voluntary disclosure rather than independent discovery - introduced a genuine complication that the Board did not fully resolve, but that complication does not ultimately alter the outcome. Section III.4 does create a distinct confidentiality weight for information transmitted by a client in confidence, and this distinguishes the case from one where an engineer independently discovers a defect during inspection. However, Section I.1's public safety obligation is framed in terms of the engineer's knowledge of danger, not the origin of that knowledge. Once Engineer A possessed knowledge that occupants of an occupied building faced injury from known code violations, the triggering condition for the paramount safety duty was satisfied regardless of how that knowledge was acquired. The source-of-information distinction is therefore relevant to calibrating the confidentiality weight on one side of the balance, but it cannot extinguish the safety obligation on the other side when the hazard is concrete, known, and affecting identifiable persons. This case teaches that Section III.4 and Section II.1.c must be read together, not in isolation: the former establishes that client-transmitted information carries confidentiality expectations, while the latter establishes that those expectations yield when public danger is present.

Does the principle requiring an engineer to insist on remedial action or withdraw from a project when safety is at stake conflict with the principle that an engineer's scope-of-work limitations and out-of-discipline boundaries constrain his authority to demand corrective action on electrical and mechanical systems - and how should these competing obligations be reconciled?

Does the principle that an engineer must notify appropriate authorities when professional judgment is overruled conflict with the principle that the engineer's duty to report is triggered only by dangers within his professional competence - and does passive acquiescence after verbally warning the client constitute an independent ethical violation even if the engineer genuinely believed the reporting duty was blocked by confidentiality?

AnalyticalEngineer A's passive acquiescence after verbally warning the client constitutes an independent ethical violation separate from and in addition to the failure to report to public authorities. The Board's precedent in BER Case 84-5 establishes that an engineer who goes along with a client's safety-compromising decision without formal dissent or escalation commits an ethical violation even if the engineer privately disagreed. Engineer A's single verbal warning, followed by silent compliance with the client's 'as is' sale directive, mirrors precisely the going-along-without-dissent pattern condemned in that precedent. The ethical obligation required Engineer A to either insist on remedial action, formally document objection and withdraw from the project, or escalate to public authorities - not to treat a verbal protest as a terminal act of compliance. Passive acquiescence after a client overrules safety concerns is not a neutral act; it is an affirmative ethical failure under Section II.1.a, which requires engineers whose judgment is overruled under life-endangering circumstances to notify appropriate authorities.
AnalyticalEngineer A's passive acquiescence after verbally warning the client constitutes an independent ethical failure distinct from the failure to report to public authorities, and this case teaches that the duty of non-acquiescence has both a procedural and a substantive dimension. Procedurally, as established in BER Case 84-5, an engineer who disagrees with a client's safety-compromising decision must formally document that objection - a single verbal warning does not satisfy the requirement. Substantively, even formal objection and documented dissent do not discharge the engineer's obligation when the hazard remains active and occupants remain exposed: the engineer must either insist on remedial action, withdraw from the project, or escalate to public authorities. The brief mention in a confidential report satisfies neither the procedural nor the substantive dimension - it is a record that ensures the information will never reach those who need it, while creating a superficial appearance of disclosure. This case therefore teaches that the principle requiring insistence on remedial action or withdrawal under Section II.1.a and the principle requiring appropriate authority notification when professional judgment is overruled are sequential obligations, not alternatives: exhausting one does not eliminate the other.
Theoretical (4)

From a deontological perspective, did Engineer A fulfill their categorical duty to protect public safety when they allowed a contractual confidentiality obligation to override the paramount duty established in NSPE Code Section I.1, given that the code itself contains an explicit exception clause in Section II.1.c that releases engineers from confidentiality when public danger is involved?

AnalyticalFrom a deontological perspective, Engineer A failed to fulfill his categorical duty to protect public safety. The NSPE Code's structure is explicitly hierarchical: Section I.1 designates public safety as paramount, and Section II.1.c contains an express exception clause that releases engineers from confidentiality obligations when public danger is involved. A deontological analysis does not require Engineer A to calculate consequences - it requires him to follow the duty that the Code itself identifies as supreme. The confidentiality obligation under Sections II.1.c and III.4 is not a categorical duty in the Kantian sense; it is a conditional duty that yields when the paramount duty is triggered. Engineer A's reliance on the confidentiality agreement as a categorical bar to disclosure therefore inverts the Code's own normative hierarchy. He treated a subordinate, conditional obligation as though it were absolute, while treating the paramount, unconditional obligation as though it were merely one consideration among many. This inversion is not a defensible interpretation of the Code - it is a failure to apply the Code's own explicit priority rules.

From a consequentialist perspective, did Engineer A's decision to limit disclosure to a brief mention in a confidential report - rather than notifying public authorities - produce the best reasonably achievable outcome for all affected parties, including building occupants who remained exposed to known electrical and mechanical code violations?

AnalyticalFrom a consequentialist perspective, Engineer A's decision to limit disclosure to a brief mention in a confidential report produced the worst reasonably foreseeable outcome for the most vulnerable affected parties. The building's current occupants - who had no knowledge of the violations, no ability to protect themselves, and no contractual relationship with Engineer A - remained continuously exposed to electrical and mechanical hazards that the client had already acknowledged violated applicable codes. The client's interests were served in the short term by the suppression of the violations, but even those interests are not clearly advanced by a strategy that exposes the client to future liability for selling a building with known, undisclosed safety defects. Engineer A's professional standing was not protected by his silence - it was ultimately condemned. The only outcome that would have produced the best reasonably achievable result for all affected parties was notification of public authorities, which would have triggered regulatory inspection, potentially required remediation before sale, and protected occupants from ongoing exposure. The consequentialist calculus therefore aligns with the deontological conclusion: reporting was the ethically required action.

From a virtue ethics perspective, did Engineer A demonstrate the professional integrity and moral courage expected of a licensed engineer when, after verbally warning the client of the danger, they passively acquiesced to the client's 'as is' sale directive rather than insisting on remedial action, withdrawing from the project, or escalating to public authorities?

AnalyticalFrom a virtue ethics perspective, Engineer A failed to demonstrate the professional integrity and moral courage expected of a licensed engineer. Virtue ethics asks not merely whether an agent followed rules but whether the agent acted as a person of good character would act in the circumstances. A virtuous engineer, upon learning that occupants of an occupied building faced injury from known code violations, would not have passively acquiesced to the client's 'as is' sale directive after a single verbal warning. Moral courage - a core professional virtue - requires the willingness to act on one's convictions even when doing so is costly, inconvenient, or contrary to a client's economic interests. Engineer A's conduct reflects the opposite disposition: he identified the danger, warned the client privately, documented the warning in a document no one outside the transaction would ever see, and then did nothing further. This pattern of behavior - identifying a problem, performing a minimal gesture, and then acquiescing - is precisely what the BER condemned in Case 84-5 as 'going along' without meaningful dissent. A virtuous engineer would have insisted on remedial action, withdrawn from the project if refused, or escalated to public authorities - not performed a procedural gesture designed to create a record of awareness while ensuring no protective action was taken.

From a deontological perspective, does the fact that the hazardous information was voluntarily disclosed by the client rather than independently discovered by Engineer A during inspection meaningfully alter Engineer A's duty to report, given that the NSPE Code's public safety obligation in Section I.1 is framed in terms of the engineer's knowledge of danger rather than the source of that knowledge?

Counterfactual (4)

If Engineer A had refused to accept the confidentiality agreement as a condition of engagement - or had negotiated an explicit carve-out permitting disclosure of life-safety code violations to public authorities - would the ethical conflict between client confidentiality and occupant safety have arisen at all, and does the failure to negotiate such terms itself constitute an ethical lapse?

AnalyticalThe ethical analysis reveals a structural problem that preceded Engineer A's conduct during the engagement: the failure to negotiate a life-safety carve-out from the confidentiality agreement at the outset. An engineer who accepts a blanket confidentiality agreement without reserving the right to disclose safety-critical information to public authorities has, at the moment of contracting, already compromised the ability to fulfill the paramount duty under Section I.1. While the Board did not address this antecedent failure, it represents a distinct ethical lapse - not merely a procedural oversight. Engineers are not passive recipients of contract terms; they are professionals with independent ethical obligations that cannot be contracted away. Accepting confidentiality terms that purport to suppress life-safety disclosures, without negotiating explicit exceptions, creates the very conflict that Engineer A later used as a justification for inaction. The ethical obligation to protect public safety begins before the engagement commences and includes the duty to structure contractual arrangements in ways that preserve - rather than foreclose - the ability to fulfill that obligation.
AnalyticalEngineer A's failure to negotiate a carve-out from the confidentiality agreement for life-safety code violations before accepting the engagement represents a preliminary ethical lapse that created the conditions for all subsequent failures. A prudent engineer, aware that he was being retained to inspect an occupied building and that confidentiality would be required, should have anticipated that the inspection might uncover - or that the client might disclose - safety-critical information. Negotiating an explicit exception permitting disclosure of life-safety violations to public authorities would have been consistent with the NSPE Code's paramount safety obligation and would have placed the client on notice from the outset that safety disclosures were non-negotiable. The failure to do so does not excuse Engineer A's subsequent inaction - the Code's safety obligations exist independently of contractual terms and cannot be waived by agreement - but it does represent a missed opportunity to prevent the ethical conflict from arising at all. Engineers who accept confidentiality agreements without safety carve-outs in contexts where safety-critical discoveries are foreseeable are not merely passive victims of an unforeseen conflict; they are partially responsible for creating the conditions that made the conflict inevitable.

If Engineer A had immediately notified the appropriate public authorities upon learning of the electrical and mechanical code violations - rather than merely mentioning them in a confidential report - what would the likely consequences have been for the building occupants, the client's sale transaction, and Engineer A's professional standing, and would those consequences have been ethically preferable to the outcome that actually occurred?

AnalyticalHad Engineer A immediately notified the appropriate public authorities upon learning of the electrical and mechanical code violations, the most likely consequences would have been: regulatory inspection of the building, potential enforcement action requiring remediation before occupancy could continue or the sale could proceed, protection of current occupants from ongoing exposure to the hazard, and possible delay or restructuring of the client's 'as is' sale. These consequences would have been ethically preferable to the outcome that actually occurred - in which occupants remained exposed, the client proceeded with a sale concealing known violations, and Engineer A's conduct was ultimately condemned. The client's short-term economic interests would have been disrupted, but the client had no legitimate interest in selling a building with known, code-violating safety defects to an uninformed buyer while current occupants remained at risk. Engineer A's professional standing would have been protected, not harmed, by compliance with the Code's paramount safety obligation. The counterfactual therefore confirms that the ethically correct action was available, feasible, and would have produced better outcomes for every party except the client's immediate economic interest - which the Code does not recognize as a legitimate basis for suppressing safety disclosures.

If Engineer A had been a licensed electrical or mechanical engineer rather than solely a structural engineer, would the scope-of-work and domain-competence arguments invoked as partial defenses have carried any weight, or would the ethical obligation to report known life-safety code violations to public authorities have been even more clearly triggered regardless of disciplinary boundaries?

AnalyticalIf Engineer A had been a licensed electrical or mechanical engineer rather than solely a structural engineer, the scope-of-work and domain-competence arguments would have carried no weight whatsoever, and the ethical obligation to report the known life-safety code violations to public authorities would have been even more clearly and unambiguously triggered. The domain-competence argument, as applied in the actual case, is already an incomplete defense - it limits Engineer A's authority to evaluate or certify the violations but does not limit his duty to report what he knows. In the counterfactual where Engineer A possessed full competence in the relevant domains, he would have had both the knowledge and the technical authority to assess the severity of the violations, making the case for reporting even stronger. This counterfactual confirms that domain incompetence functions as a marginal modulator of the reporting obligation at most - it might affect the specificity of what the engineer reports, but it cannot eliminate the duty to report the existence of known hazards to those with authority to investigate and enforce. The reporting obligation is triggered by knowledge of danger, not by technical mastery of the domain in which the danger exists.

Drawing on the precedent established in BER Case 84-5, if Engineer A had explicitly objected to the client's 'as is' sale decision and formally documented that objection - rather than passively acquiescing after a single verbal warning - would that act of dissent alone have been sufficient to discharge the ethical obligation, or would subsequent escalation to public authorities still have been required?

AnalyticalDrawing on the precedent established in BER Case 84-5, formal documentation of Engineer A's objection to the client's 'as is' sale decision - even if it had been explicit and emphatic rather than merely a brief mention in a confidential report - would not alone have been sufficient to discharge the ethical obligation. Case 84-5 established that an engineer who 'goes along' with a client's safety-overriding decision without meaningful dissent commits an independent ethical violation, but the lesson of that case is not that dissent alone is sufficient - it is that dissent is a necessary but not sufficient condition for ethical compliance when public safety is at stake. The NSPE Code's obligation under Section II.1.a requires notification to appropriate authorities when professional judgment is overruled under circumstances that endanger life or property. This is an affirmative duty to act, not merely a duty to object. An engineer who formally objects, documents the objection, and then does nothing further has satisfied the dissent requirement of Case 84-5 but has not satisfied the notification requirement of Section II.1.a. Subsequent escalation to public authorities would therefore still have been required, because the Code's safety obligation is not discharged by internal protest - it is discharged by ensuring that those with authority to protect the public are informed.
Decisions & Arguments (4)
View Extraction

Should Engineer A report the client-disclosed electrical and mechanical code violations to appropriate public authorities, or treat the confidentiality agreement as a complete bar to external disclosure?

Options considered:
O1 Notify appropriate public authorities (building code enforcement, fire marshal, or housing authority) of the client-disclosed electrical and mechanical code violations, invoking Section II.1.c's explicit exception to the confidentiality obligation on the grounds that public danger is present. Board's choice
O2 Treat the signed confidentiality agreement as a complete bar to external disclosure, relying on Section III.4's protection of client-transmitted confidential information and the faithful agent role under Section II.4, while limiting disclosure to the brief mention in the confidential structural report.
O3 Inform the client that Engineer A will withdraw from the engagement and notify public authorities unless the client either undertakes remediation or authorizes Engineer A to disclose the violations to appropriate authorities, treating the ultimatum as a final attempt to resolve the conflict within the client relationship before escalating externally.
Argument structure:
Warrants

The paramount safety obligation in Section I.1 places public safety above all competing duties, and Section II.1.c explicitly releases engineers from confidentiality when public danger is present, together these provisions required Engineer A to report to public authorities. Competing: Section III.4 creates a genuine and distinct confidentiality weight for information voluntarily transmitted by a client in confidence, and the faithful agent role under Section II.4 supports honoring the contractual arrangement Engineer A accepted.

Rebuttals

Uncertainty arises because the client-transmitted nature of the information engages Section III.4 in a way that independently discovered violations would not, potentially modulating the confidentiality weight upward. Additionally, the violations fell outside Engineer A's structural engineering scope, creating a plausible argument that his reporting authority was constrained by domain incompetence. The confidentiality agreement was a voluntarily accepted contractual obligation, not merely an informal expectation.

Grounds

The client voluntarily disclosed to Engineer A that the 60-year-old occupied apartment building contains electrical and mechanical code violations that could injure occupants. Engineer A verbally warned the client of the danger. The client declared the building would be sold 'as is' with no remedial action. Engineer A had signed a confidentiality agreement. Engineer A made only a brief mention of the violations in his confidential structural report and declined to notify any public authority.

Engineer A Confidentiality Agreement Non-Excuse Safety Code Violation Reporting Confidentiality Principle Invoked By Engineer A Under Contractual Agreement

After the client refused remediation, should Engineer A have escalated to public authorities or formally withdrawn from the project, or was a brief mention of the violations in the confidential structural report a sufficient discharge of his ethical obligation?

Options considered:
O1 Following the client's refusal to remediate, notify appropriate public authorities (building code enforcement, fire marshal, or housing authority) of the known electrical and mechanical code violations, recognizing that Section II.1.a requires escalation when professional judgment on life-endangering matters is overruled by the client. Board's choice
O2 Formally withdraw from the engagement after the client refuses remediation, documenting the objection in writing, on the grounds that continued participation would constitute going along with a safety-compromising decision, while treating the confidentiality agreement as still barring external disclosure to public authorities.
O3 Complete the structural engagement, include a written record of the client's disclosure and Engineer A's verbal warning in the confidential structural report, and take no further action, treating the written documentation as a sufficient discharge of the notification obligation given the scope-of-work limitation and the confidentiality agreement.
Argument structure:
Warrants

Section II.1.a requires engineers whose professional judgment is overruled under circumstances endangering life or property to notify appropriate authorities, a single verbal warning followed by silent compliance does not satisfy this affirmative duty. BER Case 84-5 establishes that going along with a client's safety-compromising decision without meaningful dissent or escalation constitutes an independent ethical violation. Competing: Engineer A did warn the client, did document the conversation, and the violations fell outside his structural engineering scope, providing a plausible basis for treating client notification as the limit of his authority to act.

Rebuttals

Uncertainty is created by the question of whether a verbal warning followed by written documentation, even in a confidential report, satisfies the procedural dissent requirement of BER Case 84-5, and whether the scope-of-work limitation on Engineer A's authority to demand corrective action on electrical and mechanical systems reduces the substantive escalation obligation. The competence-boundary argument is strongest if Engineer A genuinely could not assess the severity of the violations and therefore could not represent their urgency to public authorities with professional confidence.

Grounds

Engineer A verbally warned the client that the electrical and mechanical deficiencies could injure building occupants. The client responded by declaring the building would be sold 'as is' with no remedial action. Engineer A then completed his structural report, including only a brief mention of the conversation about the deficiencies, and took no further action, neither escalating to public authorities nor withdrawing from the project. The building's occupants remained continuously exposed to the known hazards.

Engineer A Passive Acquiescence Known Safety Violation Independent Ethical Failure Scope-of-Work Limitation Invoked As Incomplete Defense By Engineer A

Should Engineer A report the known electrical and mechanical code violations to appropriate public authorities, or confine disclosure to a brief mention in the confidential structural report delivered only to the client?

Options considered:
O1 Notify the appropriate regulatory or public authorities of the disclosed electrical and mechanical code violations, invoking the Section II.1.c exception clause that releases engineers from confidentiality obligations when public danger is present, and inform the client in advance that this disclosure is required by the NSPE Code's paramount safety obligation. Board's choice
O2 Document the electrical and mechanical violations in the confidential structural report delivered to the client, treating the confidentiality agreement and Section III.4's protection of client-transmitted information as a complete bar to external disclosure, on the grounds that the violations were client-confided rather than independently discovered and fall outside Engineer A's structural scope of work.
O3 Formally demand in writing that the client remediate the electrical and mechanical violations before proceeding with the sale, and if the client refuses, withdraw from the engagement and decline to deliver the structural report, stopping short of notifying public authorities on the grounds that the confidentiality agreement and domain-competence limitations constrain the reporting duty, while avoiding passive acquiescence to the client's 'as is' directive.
Argument structure:
Warrants

Warrant for reporting: Section I.1 designates public safety as paramount; Section II.1.a requires notification of appropriate authorities when professional judgment on life-endangering matters is overruled; Section II.1.c explicitly releases engineers from confidentiality obligations when public danger is present; Engineer A's own acknowledgment that the violations could injure occupants satisfied the recognition threshold regardless of his domain incompetence in electrical and mechanical systems; client-voluntary disclosure eliminates epistemic uncertainty and strengthens rather than weakens the reporting obligation; passive acquiescence after a single verbal warning constitutes an independent ethical failure under BER Case 84-5. Warrant for limiting disclosure to confidential report: Section III.4 creates a distinct confidentiality weight for information transmitted by a client in confidence; the faithful agent obligation under Section II.4 supports deference to client direction within ethical limits; Engineer A's scope of work was structural, not electrical or mechanical, arguably limiting his authority to assess or certify the severity of the violations; the client's voluntary disclosure may be argued to carry heightened confidentiality expectations distinct from independently discovered defects.

Rebuttals

Uncertainty arises from several sources: (1) Section III.4's protection of client-transmitted confidential information creates a genuine competing weight that the Code does not explicitly subordinate in the same explicit language as Section II.1.c's exception clause, leaving open whether the source-of-information distinction modulates the reporting threshold; (2) Engineer A's lack of competence in electrical and mechanical engineering could be argued to limit his capacity to assess whether the hazard rises to the level of 'imminent danger' required to trigger the exception clause; (3) the Code does not specify the minimum form or channel that safety notification must take, leaving open whether a written record in a professional report, even a confidential one, constitutes partial compliance; (4) the faithful agent role is itself bounded by ethical limits, but the precise boundary between legitimate client loyalty and impermissible safety suppression is not always self-evident from the Code's text alone.

Grounds

Engineer A was retained by a client to conduct a structural integrity assessment of a 60-year-old occupied apartment building under a confidentiality agreement. During the engagement, the client voluntarily disclosed the existence of electrical and mechanical code violations. Engineer A verbally warned the client that the deficiencies could cause injury to occupants, noted the violations briefly in the confidential structural report, and then declined to report them to any public authority or to notify the building's occupants. The client proceeded with an 'as is' sale. Occupants remained continuously exposed to the known hazards. Engineer A's conduct was subsequently condemned.

Paramount Safety Obligation Hierarchy Supremacy. Public Authority Notification Duty Confidentiality Agreement Accepted Under Client Engagement

After the client refuses remediation, should Engineer A escalate by formally documenting objection and notifying occupants or public authorities, withdraw from the project, or treat the verbal warning as sufficient discharge of the safety obligation and proceed with delivering the confidential report?

Options considered:
O1 After the client refuses remediation, formally document the objection in writing, notify the appropriate public regulatory authorities of the known code violations invoking the Section II.1.c safety exception, and consider direct notification to the building's occupants as an independent channel required by the paramount safety obligation, then withdraw from the engagement if the client objects to these disclosures. Board's choice
O2 Formally document the objection to the client's 'as is' directive in writing and withdraw from the engagement, declining to deliver the structural report, on the grounds that the scope-of-work and domain-competence limitations constrain Engineer A's authority to demand remediation of electrical and mechanical systems, while stopping short of notifying public authorities or occupants on the basis that the confidentiality agreement and Section III.4 continue to bind after withdrawal.
O3 Treat the verbal warning to the client as a complete discharge of the safety notification duty, note the violations briefly in the confidential structural report to create a written record of awareness, and deliver the report to the client: relying on the faithful agent obligation under Section II.4, the confidentiality agreement, and the domain-competence limitation to justify taking no further escalatory action after the client's refusal.
Argument structure:
Warrants

Warrant for escalation beyond verbal warning: BER Case 84-5 establishes that passive acquiescence after a client overrules safety concerns constitutes an independent affirmative ethical violation; Section II.1.a requires notification of appropriate authorities when professional judgment on life-endangering matters is overruled, a verbal warning to the client does not satisfy this obligation; the paramount safety obligation under Section I.1 is not exhausted by the single channel of regulatory notification and may independently require direct notification to occupants who are the parties most immediately and continuously exposed to the hazard and who have no other means of learning of the danger; moral courage as a core professional virtue requires sustained action, not a minimal procedural gesture followed by acquiescence. Warrant for treating verbal warning as sufficient: The faithful agent obligation under Section II.4 supports deference to client direction after the engineer has discharged a warning duty; Engineer A's scope of work was structural, and the violations fell outside his discipline, arguably limiting his authority to demand corrective action on electrical and mechanical systems; a single verbal warning, if genuine, may satisfy the spirit of the dissent requirement under a narrow reading of BER Case 84-5; the confidentiality agreement may be argued to constrain the channels through which Engineer A could escalate.

Rebuttals

Uncertainty is created by several factors: (1) BER Case 84-5 may be read narrowly to require only that the engineer not 'go along without dissent,' leaving open whether formal documentation and escalation are required or whether a genuine verbal warning satisfies the dissent standard; (2) the NSPE Code does not explicitly specify occupant direct notification as a required channel distinct from regulatory reporting, leaving open whether 'appropriate public authorities' encompasses or exhausts the notification obligation; (3) the competence-boundary argument creates genuine uncertainty about whether Engineer A had the authority to insist on remediation of electrical and mechanical systems outside his structural scope; (4) the question of whether passive acquiescence after a verbal warning constitutes an independent ethical violation separate from the failure to report to authorities depends on whether the two obligations are sequential or alternative, a question the Code does not resolve with complete clarity.

Grounds

After completing the structural assessment and learning of the electrical and mechanical violations through client disclosure, Engineer A verbally warned the client that the deficiencies could cause injury to occupants. The client directed Engineer A to proceed on an 'as is' basis. Engineer A noted the violations briefly in the confidential structural report, delivered the report to the client, and took no further action: neither formally documenting objection, withdrawing from the project, notifying public authorities, nor contacting the building's occupants. The occupants remained continuously exposed to the hazard. Engineer A's conduct was subsequently condemned. BER Case 84-5 had previously established that an engineer who 'goes along' with a client's safety-compromising decision without meaningful dissent commits an independent ethical violation.

Non-Acquiescence to Unsafe Client Directives. Post-Refusal Escalation Obligation Client Refusal of Remediation Under As-Is Sale Directive
Event Timeline (11)
11 sequenced 5 actions 6 events
Case timeline
Engineer A agreed to terms requiring the structural report to remain confidential before beginning work, knowing the client intended to sell the building 'as is' with no remediation. This pre-engagement decision bound Engineer A to non-disclosure obligations throughout the engagement.
At stake (1)
  • Prospective failure to protect public health and safety (Section I.1) by accepting terms that could foreseeably constrain safety reporting
Fulfills (2)
  • Faithful agent/trustee obligation to client (Section III.4)
  • Contractual obligation to honor agreed terms of engagement
Violates (1)
  • Failure to anticipate and negotiate exceptions for mandatory safety disclosures before accepting the confidentiality constraint
A client formally engages Engineer A to assess the structural integrity of a 60-year-old occupied apartment building prior to its sale, establishing a professional relationship with a confidentiality agreement in place.
Engineer A performed several structural tests on the 60-year-old occupied apartment building as retained, ultimately determining the building to be structurally sound. This was the primary professional service for which he was engaged.
Fulfills (3)
  • Obligation to perform professional services competently within area of licensure (structural engineering)
  • Obligation to provide honest and accurate findings to the client
  • Faithful performance of contracted professional services
Following structural integrity tests, Engineer A's assessment yields the outcome that the 60-year-old apartment building is structurally sound, satisfying the primary scope of the engagement.
During the engagement, the client discloses to Engineer A the existence of electrical and mechanical code violations in the building that pose a danger to its occupants, introducing a safety hazard into the professional relationship.
Upon learning from the client that the building contained electrical and mechanical code deficiencies, Engineer A informed the client that these deficiencies could cause injury to the building's occupants. This was a verbal advisory action taken directly with the client rather than with any authority or third party.
At stake (2)
  • Paramount obligation to hold public health and safety above all other considerations (Section I.1), warning the client alone was insufficient when the client had already indicated no remediation would occur
  • Obligation to notify appropriate authority when professional judgment is overruled under circumstances endangering public safety (Section II.1.c, as interpreted in Discussion)
Fulfills (2)
  • Partial fulfillment of duty to protect public health and safety by at minimum notifying the client of the risk (Section I.1)
  • Obligation to advise client of consequences of ignoring safety concerns
Because neither Engineer A nor the client reports the electrical and mechanical code violations to any authority, the building's occupants continue to be exposed to unmitigated dangers throughout and after the engagement.
Engineer A included a brief mention of his conversation with the client about the electrical and mechanical deficiencies in the confidential structural report, rather than omitting the matter entirely or reporting it to external authorities. This written notation was the only formal record of the known safety violations.
Fulfills (2)
  • Partial documentation of known safety concern within the professional report
  • Transparency with client by acknowledging the conversation in writing
Violates (3)
  • Paramount obligation to protect public health and safety (Section I.1), a confidential notation does not discharge the duty to notify appropriate authorities of conditions endangering occupants
  • Obligation to notify appropriate authority when safety is endangered and professional judgment is overruled (Section II.1.c as interpreted by Discussion)
  • Obligation not to merely 'go along' when public safety is at stake (Case 84-5 reasoning applied in Discussion)
Engineer A produces a confidential written report that documents the structural assessment findings and includes only a brief mention of the conversation about electrical and mechanical code violations, without escalating or formally flagging the safety hazard.
Engineer A made the explicit decision not to report the known electrical and mechanical code violations to any third party, regulatory authority, or public safety body, citing the confidentiality agreement as the governing constraint. This decision was the culminating professional choice that the Discussion identifies as the primary ethical failure.
Fulfills (2)
  • Non-disclosure obligation to client (Section III.4)
  • Contractual confidentiality obligation under the terms of engagement
Violates (4)
  • Paramount obligation to hold public health and safety above all other considerations (Section I.1)
  • Obligation to notify appropriate authority when professional judgment is overruled under circumstances where public safety is endangered (Section II.1.c, as interpreted in Discussion referencing Case 84-5)
  • Obligation not to passively 'go along' when safety of the public is endangered (Case 84-5 reasoning applied in Discussion)
  • Obligation to use the Section II.1.c exception permitting disclosure when required by the Code, given that Section I.1 paramountcy of safety constituted such a Code-based requirement
The Discussion section of the case analysis formally concludes that Engineer A failed his paramount obligation to public safety by not escalating the matter to authorities or refusing to continue the engagement, referencing prior NSPE cases as precedent.
Narrative (1 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are a licensed structural engineer retained by a client to assess the structural integrity of a 60-year-old occupied apartment building prior to its sale. Your agreement specifies that your report is confidential, and the client has stated the building will be sold as-is with no repairs or renovations planned. Your structural testing is complete, and the building is sound. During the engagement, however, the client disclosed that the building contains electrical and mechanical deficiencies that violate applicable codes, conditions outside your area of licensure but ones you recognize as potential hazards to the current occupants. You have noted the conversation briefly in your structural report, but have not contacted any public authority or third party about the violations. The decisions you face now concern your obligations to the occupants, your client, and the limits of your professional and ethical duties.

Main characters (1)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Engineer A Roles in this case: Confidentiality-Bound Structural Safety Discovering EngineerConfidentiality-Bound Public Safety Inaction Engineer

Tension between Engineer A Confidentiality Agreement Non-Excuse Safety Code Violation Reporting and Confidentiality Principle Invoked By Engineer A Under Contractual Agreement

Attaches to role: Confidentiality-Bound Structural Safety Discovering Engineer

Engineer A is bound by a confidentiality agreement with the client, who disclosed electrical and mechanical code violations in confidence. The obligation demands that confidentiality cannot legally or ethically excuse non-reporting of safety violations, yet the constraint recognizes that the client's reasonable expectation of confidentiality — especially for information disclosed voluntarily and outside the engineer's formal scope — carries genuine moral weight. Fulfilling the reporting obligation requires breaching a contractual and relational trust; honoring the confidentiality constraint risks leaving occupants exposed to known hazards. This is a genuine dilemma because both duties are grounded in recognized ethical principles (NSPE Code II.1.c vs. II.1.b), not merely competing preferences.

Attaches to role: Confidentiality-Bound Structural Safety Discovering Engineer

The engineer has a clear obligation to escalate known electrical and mechanical code violations that pose injury risk to current building occupants. However, the client has invoked a legitimate business decision — selling the property as-is — which constrains the engineer from unilaterally overriding client authority over property disposition. The tension is genuine because the as-is sale directive is not inherently fraudulent or illegal as a business choice, yet the occupants currently residing in the building face ongoing, unmitigated risk during the sale process. Escalating to public authorities may protect occupants but effectively overrides a client business decision the engineer was not retained to adjudicate.

Attaches to role: Confidentiality-Bound Structural Safety Discovering Engineer

Engineer A may have attempted to discharge safety duties by briefly mentioning the violations in the written report to the client, but the obligation establishes that such a mention is ethically insufficient — direct notification to public authorities is required when client remediation is refused. The constraint, however, marks a boundary on how far the engineer may go in disclosing confidential client information externally. This creates a dilemma of degree and method: the engineer must do more than mention the hazard internally, yet doing more means crossing the confidentiality boundary the constraint protects. The tension is not merely procedural — it determines whether Engineer A's ethical duty is satisfied or violated.

Attaches to role: Confidentiality-Bound Public Safety Inaction Engineer

Tension between Engineer A Passive Acquiescence Known Safety Violation Independent Ethical Failure and Scope-of-Work Limitation Invoked As Incomplete Defense By Engineer A

Attaches to role: Confidentiality-Bound Structural Safety Discovering Engineer

Tension between Engineer A Out-of-Discipline Electrical Mechanical Code Violation Public Authority Reporting and Engineer A Scope of Work Non-Shield Electrical Mechanical Safety Disclosure

Attaches to role: Confidentiality-Bound Structural Safety Discovering Engineer

Other people involved in the case but not central to the opening narrative.

Guided by: Public Welfare Paramount, Confidentiality Principle, Confidentiality Non-Applicability to Public Danger Disclosure

Engineer A is bound by a confidentiality agreement with the client, who disclosed electrical and mechanical code violations in confidence. The obligation demands that confidentiality cannot legally or ethically excuse non-reporting of safety violations, yet the constraint recognizes that the client's reasonable expectation of confidentiality — especially for information disclosed voluntarily and outside the engineer's formal scope — carries genuine moral weight. Fulfilling the reporting obligation requires breaching a contractual and relational trust; honoring the confidentiality constraint risks leaving occupants exposed to known hazards. This is a genuine dilemma because both duties are grounded in recognized ethical principles (NSPE Code II.1.c vs. II.1.b), not merely competing preferences.

The engineer has a clear obligation to escalate known electrical and mechanical code violations that pose injury risk to current building occupants. However, the client has invoked a legitimate business decision — selling the property as-is — which constrains the engineer from unilaterally overriding client authority over property disposition. The tension is genuine because the as-is sale directive is not inherently fraudulent or illegal as a business choice, yet the occupants currently residing in the building face ongoing, unmitigated risk during the sale process. Escalating to public authorities may protect occupants but effectively overrides a client business decision the engineer was not retained to adjudicate.

Engineer A may have attempted to discharge safety duties by briefly mentioning the violations in the written report to the client, but the obligation establishes that such a mention is ethically insufficient — direct notification to public authorities is required when client remediation is refused. The constraint, however, marks a boundary on how far the engineer may go in disclosing confidential client information externally. This creates a dilemma of degree and method: the engineer must do more than mention the hazard internally, yet doing more means crossing the confidentiality boundary the constraint protects. The tension is not merely procedural — it determines whether Engineer A's ethical duty is satisfied or violated.

Engineer A is bound by a confidentiality agreement with the client, who disclosed electrical and mechanical code violations in confidence. The obligation demands that confidentiality cannot legally or ethically excuse non-reporting of safety violations, yet the constraint recognizes that the client's reasonable expectation of confidentiality — especially for information disclosed voluntarily and outside the engineer's formal scope — carries genuine moral weight. Fulfilling the reporting obligation requires breaching a contractual and relational trust; honoring the confidentiality constraint risks leaving occupants exposed to known hazards. This is a genuine dilemma because both duties are grounded in recognized ethical principles (NSPE Code II.1.c vs. II.1.b), not merely competing preferences.

The engineer has a clear obligation to escalate known electrical and mechanical code violations that pose injury risk to current building occupants. However, the client has invoked a legitimate business decision — selling the property as-is — which constrains the engineer from unilaterally overriding client authority over property disposition. The tension is genuine because the as-is sale directive is not inherently fraudulent or illegal as a business choice, yet the occupants currently residing in the building face ongoing, unmitigated risk during the sale process. Escalating to public authorities may protect occupants but effectively overrides a client business decision the engineer was not retained to adjudicate.

Engineer A is bound by a confidentiality agreement with the client, who disclosed electrical and mechanical code violations in confidence. The obligation demands that confidentiality cannot legally or ethically excuse non-reporting of safety violations, yet the constraint recognizes that the client's reasonable expectation of confidentiality — especially for information disclosed voluntarily and outside the engineer's formal scope — carries genuine moral weight. Fulfilling the reporting obligation requires breaching a contractual and relational trust; honoring the confidentiality constraint risks leaving occupants exposed to known hazards. This is a genuine dilemma because both duties are grounded in recognized ethical principles (NSPE Code II.1.c vs. II.1.b), not merely competing preferences.

Engineer A may have attempted to discharge safety duties by briefly mentioning the violations in the written report to the client, but the obligation establishes that such a mention is ethically insufficient — direct notification to public authorities is required when client remediation is refused. The constraint, however, marks a boundary on how far the engineer may go in disclosing confidential client information externally. This creates a dilemma of degree and method: the engineer must do more than mention the hazard internally, yet doing more means crossing the confidentiality boundary the constraint protects. The tension is not merely procedural — it determines whether Engineer A's ethical duty is satisfied or violated.

These tensions did not map cleanly to a single character.

Tension between Paramount Safety Obligation Hierarchy Supremacy — Public Authority Notification Duty and Confidentiality Agreement Accepted Under Client Engagement

Tension between Non-Acquiescence to Unsafe Client Directives — Post-Refusal Escalation Obligation and Client Refusal of Remediation Under As-Is Sale Directive

Opening States (10)
Domain-Specific Incompetence in Electrical and Mechanical Systems Client As-Is Sale No Remediation Intent Active Public Safety at Risk from Known Code Violations in Occupied Building Engineer Passive Acquiescence to Client Safety Refusal State Code-Based Confidentiality Exception Activation State Engineer A Confidentiality vs. Public Safety Competing Duties Engineer A Code-Based Confidentiality Exception Activation Engineer A Passive Acquiescence to Client Safety Refusal Engineer A Client Cost-Driven Safety Oversight Rejection (Case 84-5 Analogy) Engineer A Paramount Safety Obligation Notification Duty
Summary
  • Confidentiality agreements cannot override an engineer's fundamental obligation to report known safety violations to public authorities, regardless of contractual provisions.
  • An engineer's lack of technical competence in a specific discipline does not eliminate the duty to report observed code violations that pose public safety risks — awareness, not expertise, triggers the reporting obligation.
  • Passive acquiescence to known safety violations constitutes an independent ethical failure, meaning silence itself is a breach of professional duty even when the engineer argues limited scope of work.

© Licensed under the GNU GPL v3 | Report Issue