Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Duty To Report Safety Violations
Step 4 of 5

191

Entities

6

Provisions

5

Precedents

14

Questions

16

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's confidential, internal notification to the client (functionally equivalent to no disclosure per C4/C6) fails to satisfy his duty; the Board holds that the obligation to act on the known safety risk must transfer from the engineer's private/contractual sphere to the public authorities who can enforce compliance and protect occupants. The confidentiality obligation is not erased but subordinated, and the paramount safety duty is redirected to the appropriate regulatory body via the engineer's reporting obligation.
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

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

I.1 board + analysis Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 24)
Obligation
Engineer A Safety Precedence Duty
This provision directly establishes the paramount duty to public safety health and welfare
Action
Client Safety Warning
Warning the client about safety issues upholds paramount duty to public safety
State
Occupant Injury Risk
Public safety must be paramount when occupants face injury risk
Obligation (3)
  • Engineer A Safety Precedence Duty
    This provision directly establishes the paramount duty to public safety health and welfare
  • Engineer A Occupant Safety Duty
    This provision requires prioritizing occupant safety over other duties once deficiencies are known
  • Engineer A Safety Violation Reporting Duty
    Holding safety paramount necessitates reporting code violations that endanger occupants
Action (3)
  • Client Safety Warning
    Warning the client about safety issues upholds paramount duty to public safety
  • Structural Investigation
    Investigating structural issues serves the duty to protect public safety
  • Nondisclosure to Authorities
    Failing to report safety hazards to authorities conflicts with holding public safety paramount
State (5)
  • Occupant Injury Risk
    Public safety must be paramount when occupants face injury risk
  • Code-Violating Building Deficiencies
    Safety of public is paramount over code violating deficiencies
  • Confidentiality Versus Safety Conflict
    Paramount safety duty resolves conflict in favor of disclosure
  • Engineer A Injury Risk Awareness
    Awareness of injury risk triggers paramount safety obligation
  • Safety Violations Withheld From Third Parties
    Withholding safety violations conflicts with paramount public safety duty
Constraint (2)
  • Engineer A Going Along Limit
    Public safety paramountcy prevents proceeding silently when deficiencies endanger welfare
  • Client Building Code Compliance
    Public safety obligation directly relates to ensuring building meets code requirements
Principle (2)
  • Public Welfare of Building Occupants
    This provision requires prioritizing occupant safety over other duties.
  • Public Welfare Paramount over Confidentiality
    This provision establishes that safety must override confidentiality obligations.
Role (2)
  • Engineer A Structural Inspection Engineer
    He must hold public safety paramount when discovering code violations endangering occupants
  • Board of Ethical Review
    The Board weighs this paramount safety obligation in its adjudication
Event (2)
  • Structural Soundness Finding
    Public safety is directly implicated by findings on structural soundness
  • Safety Risk Recognition
    Recognizing a safety risk directly invokes the paramount duty to protect public welfare
Resource (2)
  • Engineer A Structural Report
    The report concerns structural integrity affecting occupant safety in an aging building.
  • NSPE Code of Ethics
    This provision is part of the paramount public safety duty within the Code.
Capability (3)
  • Engineer A Injury Risk Recognition
    Recognizing injury risk directly implicates the paramount duty to public safety
  • Engineer A Deficiency Disclosure
    Disclosing injury risk to the client fulfills the paramount safety obligation
  • Board Normative Framework Assessment
    The Board explicitly applies I.1 as a governing safety provision
II.1.a board + analysis 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 20)
Obligation
Engineer A Authority Notification Duty
This provision directly requires notifying appropriate authority when judgment is overruled and safety is endangered
Action
Client Safety Warning
Notifying the client of overruled judgment on safety matters is required by this provision
State
Engineer A Judgment Overruled
Directly addresses notification when engineering judgment is overruled endangering life
Obligation (2)
  • Engineer A Authority Notification Duty
    This provision directly requires notifying appropriate authority when judgment is overruled and safety is endangered
  • Engineer A Safety Violation Reporting Duty
    This provision mandates reporting to authorities when safety is endangered
Action (2)
  • Client Safety Warning
    Notifying the client of overruled judgment on safety matters is required by this provision
  • Nondisclosure to Authorities
    Provision requires notifying other authorities when life or property is endangered
State (4)
  • Engineer A Judgment Overruled
    Directly addresses notification when engineering judgment is overruled endangering life
  • Client No-Remediation Stance
    Client refusal to remediate requires notifying other appropriate authority
  • Code-Violating Building Deficiencies
    Deficiencies endangering life require notification to appropriate authority
  • Occupant Injury Risk
    Risk to occupants triggers duty to notify appropriate authority
Constraint (2)
  • Engineer A Going Along Limit
    This provision requires notifying other authority when judgment is overruled on safety issues rather than proceeding without dissent
  • Client Building Code Compliance
    Overruled judgment on code violations triggers duty to notify appropriate authority
Principle (2)
  • Public Welfare Paramount over Confidentiality
    This provision requires notifying appropriate authority when safety is endangered.
  • Public Welfare of Building Occupants
    This provision mandates reporting dangers that could injure occupants.
Role (2)
  • Engineer A Structural Inspection Engineer
    He must notify appropriate authority when his safety concerns are overruled by client confidentiality
  • Appropriate Authority
    This is the authority that should have been notified under this provision
Event (2)
  • Safety Risk Recognition
    Engineer must notify employer or authorities when a safety risk endangers life or property
  • Structural Soundness Finding
    Findings that endanger life or property require notification to appropriate parties
Resource (2)
  • Engineer A Structural Report
    The report reflects an engineering judgment on safety that may need escalation if overruled.
  • BER Case 84-5
    This case addresses an engineer proceeding despite believing a decision was dangerous, directly invoking this provision.
Capability (2)
  • Engineer A Confidentiality Judgment
    Deciding whether to notify other authorities relates to the duty to report when judgment is overruled and danger exists
  • Board Normative Framework Assessment
    The Board considers II.1.a as part of the notification obligation framework
II.1.c board + analysis 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 21)
Obligation
Engineer A Confidentiality Duty
This provision restricts disclosure of client information without consent except as required by law or code
Action
Limited Report Disclosure
Disclosure of information is limited without client consent under this provision
State
Confidential Structural Report Term
Confidentiality term restricts revealing report information without consent
Obligation (2)
  • Engineer A Confidentiality Duty
    This provision restricts disclosure of client information without consent except as required by law or code
  • Engineer A Safety Violation Reporting Duty
    This provision provides the exception allowing disclosure when required for safety reporting
Action (2)
  • Limited Report Disclosure
    Disclosure of information is limited without client consent under this provision
  • Nondisclosure to Authorities
    Provision restricts revealing facts without consent unless legally required
State (5)
  • Confidential Structural Report Term
    Confidentiality term restricts revealing report information without consent
  • Confided Deficiency Information Held
    Confided information cannot be revealed absent consent or legal requirement
  • Section II.1.c Scope Ambiguity
    This provision is the source of the scope ambiguity regarding exceptions
  • Code Exception Disclosure Release
    Provision explicitly allows disclosure when authorized or required by code
  • Confidentiality Versus Safety Conflict
    Provision creates tension between confidentiality and required disclosure
Constraint (2)
  • Engineer A Report Confidentiality
    This provision directly establishes the constraint against revealing information without client consent
  • Engineer A Client Confidentiality Boundary
    This provision creates the general confidentiality restriction on business affairs information
Principle (2)
  • Confidentiality in Building Report
    This provision restricts disclosure of information without client consent under agreement terms.
  • Confidentiality in As-Is Sale Investigation
    This provision limits disclosure of confidential findings absent client consent.
Role (2)
  • Engineer A Structural Inspection Engineer
    He is bound not to reveal client information without consent unless legally required
  • Client Apartment Building Seller
    The client's confidentiality agreement invokes this provision's protections
Event (1)
  • Confidential Information Transmission
    This provision restricts revealing information without proper consent or legal authorization
Resource (3)
  • NSPE Code of Ethics
    This provision defines confidentiality limits within the Code itself.
  • BER Case 85-4
    This case is specifically about interpreting Section II.1.c.
  • BER Case 87-2
    This case is specifically about interpreting Section II.1.c.
Capability (2)
  • Engineer A Confidentiality Judgment
    Weighing confidentiality against disclosure directly relates to the restriction on revealing client information
  • Board Normative Framework Assessment
    The Board applies II.1.c to assess permissible disclosure limits
II.1.e board + analysis Engineers shall not aid or abet the unlawful practice of engineering by a person or firm.
How this applies in the case
Event
Safety Risk Recognition
Ignoring or concealing a recognized safety risk could aid unlawful engineering practice
II.4 board + analysis Engineers shall act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 14)
Obligation
Engineer A Faithful Agent Duty
This provision directly establishes the duty to act as a faithful agent or trustee for the client
Action
Confidential Engagement Acceptance
Accepting the engagement establishes the engineer as a faithful agent to the client
State
Structural-Only Engagement Scope
Faithful agency duty is bounded by the scope of the structural engagement
Obligation (1)
  • Engineer A Faithful Agent Duty
    This provision directly establishes the duty to act as a faithful agent or trustee for the client
Action (2)
  • Confidential Engagement Acceptance
    Accepting the engagement establishes the engineer as a faithful agent to the client
  • Continued Client Service
    Continuing service reflects the duty to act as a faithful agent for the client
State (3)
  • Structural-Only Engagement Scope
    Faithful agency duty is bounded by the scope of the structural engagement
  • Client No-Remediation Stance
    Acting as faithful agent is complicated by client refusal to remediate
  • Confidential Structural Report Term
    Faithful agent duty includes respecting confidentiality terms of engagement
Constraint (2)
  • Engineer A Report Confidentiality
    Faithful agency duty supports the confidentiality obligation to the client
  • Engineer A Going Along Limit
    Faithful agency duty conflicts with silently proceeding despite unresolved safety deficiencies
Principle (1)
  • Loyalty as Faithful Agent to Client
    This provision defines the engineer's duty of faithful agency to the client.
Role (1)
  • Engineer A Structural Inspection Engineer
    He must act as a faithful agent to his client while balancing other duties
Event (1)
  • Confidential Information Transmission
    Faithful agency requires careful handling of confidential information
Resource (1)
  • NSPE Code of Ethics
    This provision establishes the faithful agent duty central to the Code's confidentiality framework.
Capability (2)
  • Engineer A Deficiency Disclosure
    Informing the client of risks reflects faithful agency to the client
  • Engineer A Confidentiality Judgment
    Balancing confidentiality reflects the engineer's duty as a faithful agent or trustee
III.4 board + analysis 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 21)
Obligation
Engineer A Confidentiality Duty
This provision directly prohibits disclosing confidential business or technical information without consent
Action
Confidential Engagement Acceptance
Accepting a confidential engagement triggers the duty not to disclose client information
State
Confidential Structural Report Term
Prohibits disclosing confidential technical information from the report without consent
Obligation (2)
  • Engineer A Confidentiality Duty
    This provision directly prohibits disclosing confidential business or technical information without consent
  • Engineer A Faithful Agent Duty
    This provision reinforces the confidentiality component of the faithful agent obligation
Action (3)
  • Confidential Engagement Acceptance
    Accepting a confidential engagement triggers the duty not to disclose client information
  • Limited Report Disclosure
    Limiting the report reflects compliance with confidentiality obligations
  • Nondisclosure to Authorities
    Withholding information from authorities aligns with confidentiality duty absent consent
State (3)
  • Confidential Structural Report Term
    Prohibits disclosing confidential technical information from the report without consent
  • Confided Deficiency Information Held
    Confided deficiency information is protected as confidential business information
  • Confidentiality Versus Safety Conflict
    Confidentiality obligation directly conflicts with need to disclose safety issues
Constraint (2)
  • Engineer A Client Confidentiality Boundary
    This provision directly creates the constraint prohibiting disclosure of confidential business affairs information
  • Engineer A Report Confidentiality
    This provision reinforces the restriction on disclosing confidential technical and business information
Principle (2)
  • Confidentiality in As-Is Sale Investigation
    This provision directly grounds the engineer's obligation not to disclose confidential business information.
  • Confidentiality in Building Report
    This provision supports withholding confidential information under the agreement.
Role (3)
  • Engineer A Structural Inspection Engineer
    He is restricted from disclosing confidential client business information without consent
  • Client Apartment Building Seller
    The client's confidential information is protected under this provision
  • Board of Ethical Review
    The Board directly weighs this confidentiality provision against public safety
Event (1)
  • Confidential Information Transmission
    This provision directly governs disclosure of confidential business or technical information
Resource (3)
  • NSPE Code of Ethics
    This provision is the confidentiality rule discussed in the Code's topic summary.
  • BER Case 61-8
    This case addresses employed engineers' duty to maintain employer confidences under this type of provision.
  • BER Case 82-2
    This case directly interprets the scope of Section III.4.
Capability (2)
  • Engineer A Confidentiality Judgment
    Deciding whether to disclose confidential business information ties directly to this provision
  • Board Normative Framework Assessment
    The Board identifies III.4 as a key governing confidentiality provision
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:

An engineer who has genuine safety concerns must insist on proper safety measures or refuse to continue work rather than silently acceding to a client's wishes that compromise public safety.

Citation Context:

Cited as an analogous precedent where an engineer unethically acceded to a client's wishes despite safety concerns instead of insisting on proper safety measures or refusing to continue work; the Board applies this reasoning to conclude Engineer A similarly should have taken further action.

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... They found it was unethical for the engineer to proceed with his work on the project knowing that the client would not agree to hire a full-time project representative."
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: "Instead, Engineer A, like the engineer in Case 84-5, "went along" and proceeded with the work on behalf of the client."

Principle Established:

Section III.4 necessarily relates to confidential information given to the engineer by the client in the course of providing services; it does not apply when there is no transmission of such confidential information.

Citation Context:

Cited as a prior case interpreting Section III.4 in the context of private practice client relationships, but distinguished because no confidential information was actually transmitted by the client to the engineer in that case.

Relevant Excerpts
discussion: "For example, 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 handling the sale of the residence. The Board reaffirmed the principle of the right of confidentiality on behalf of the client."
discussion: "In Case 82-2, there was no transmission of confidential information by the client to the engineer."

Principle Established:

The Board has interpreted Section II.1.c on multiple occasions without clarifying the scope of the disclosure exception.

Citation Context:

Cited among cases where the Board previously interpreted Section II.1.c but did not outline the scope of that Code 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:

Employed engineers have an obligation to maintain the confidences of their employer regarding confidential information obtained during employment.

Citation Context:

Cited to show the Board's prior interpretation of Sections II.4 and III.4 in the context of employed engineers maintaining employer confidences.

Relevant Excerpts
discussion: "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:

The Board has interpreted Section II.1.c on multiple occasions without clarifying the scope of the disclosure exception.

Citation Context:

Cited among cases where the Board previously interpreted Section II.1.c but did not outline the scope of that Code 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 76% Facts Similarity 78% Discussion Similarity 58% Provision Overlap 40% Outcome Alignment 100% Tag Overlap 40%
Shared provisions: II.1.a, II.1.c Same outcome unethical View Synthesis
Component Similarity 58% Facts Similarity 63% Discussion Similarity 70% Provision Overlap 43% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: II.1.c, II.4, III.4 Same outcome unethical View Synthesis
Component Similarity 72% Facts Similarity 67% Discussion Similarity 74% Provision Overlap 29% Outcome Alignment 50% Tag Overlap 60%
Shared provisions: II.1.c, III.4 View Synthesis
Component Similarity 67% Facts Similarity 71% Discussion Similarity 58% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 29%
Shared provisions: II.1.c Same outcome unethical View Synthesis
Component Similarity 67% Facts Similarity 55% Discussion Similarity 58% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 17%
Shared provisions: II.1.a Same outcome unethical View Synthesis
Component Similarity 64% Facts Similarity 48% Discussion Similarity 72% Provision Overlap 40% Outcome Alignment 50% Tag Overlap 22%
Shared provisions: I.1, III.4 View Synthesis
Component Similarity 58% Facts Similarity 48% Discussion Similarity 56% Outcome Alignment 100% Tag Overlap 60%
Same outcome unethical View Synthesis
Component Similarity 71% Facts Similarity 62% Discussion Similarity 55% Provision Overlap 17% Outcome Alignment 50% Tag Overlap 40%
Shared provisions: III.4 View Synthesis
Component Similarity 56% Facts Similarity 33% Discussion Similarity 55% Provision Overlap 33% Outcome Alignment 50% Tag Overlap 60%
Shared provisions: II.1.a, II.4 View Synthesis
Component Similarity 56% Facts Similarity 56% Discussion Similarity 56% Outcome Alignment 100% Tag Overlap 60%
Same outcome unethical 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.
Resolved by: The Board treated the paramount duty to public safety as categorically outweighing the contractual duty of confidentiality once a genuine occupant injury risk was recognized. (confidence 0.85)
I.1. II.1.a. II.1.c. 3 principles 3 facts Conditions Narrative
Implicit (3)

Since Engineer A is not an electrical or mechanical engineer, did he have a competency-based obligation to recommend that the client retain qualified specialists to further evaluate and address the deficiencies, rather than merely noting them in his structural report?

AnalyticalThe Board's finding that Engineer A acted unethically in not reporting the violations does not turn on his lack of electrical or mechanical licensure; the paramount duty to public safety under Section I.1 attaches to any engineer who becomes aware of a genuine safety risk, regardless of whether that risk falls within his own discipline. Engineer A's competency limitations may have precluded him from independently verifying or remediating the electrical and mechanical deficiencies, but they did not excuse him from the separate and more basic obligation to ensure that qualified authorities were notified once he recognized, in his own professional judgment, that occupants faced a risk of injury.
Resolved by: The Board separated the duty to notify (discipline-independent) from the duty to verify or remediate (discipline-dependent), finding the former unaffected by licensure gaps. (confidence 0.82)
I.1. 3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101, Engineer A's lack of licensure in electrical or mechanical engineering did not excuse him from a competency-based obligation to advise the client to retain qualified specialists. Recognizing a genuine risk of occupant injury, even outside one's own discipline, triggers a responsibility to ensure the matter is properly evaluated by someone with the requisite expertise, not merely to note it and move on.
Resolved by: The Board weighed the passive act of noting deficiencies against the affirmative competency-based obligation to ensure qualified evaluation, finding the latter required once risk was recognized outside the engineer's discipline. (confidence 0.80)
I.1. 3 principles 3 facts Conditions Narrative

Does merely mentioning the confided deficiencies briefly in a confidential report, without further action, satisfy or fall short of Engineer A's duty once he recognized a genuine risk of occupant injury?

AnalyticalMerely noting the deficiencies briefly within a confidential report that only the client would see did not discharge Engineer A's duty, because that disclosure was functionally equivalent to no disclosure at all from the standpoint of the building occupants and public authorities who lacked access to the report. The Board's reasoning implies a threshold distinction between passive internal documentation and affirmative external notification: only the latter satisfies the paramountcy obligation once a real risk of occupant injury has been identified, regardless of the engineer's good-faith warning to the client.
Resolved by: The Board contrasted passive internal documentation against affirmative external notification, concluding only the latter discharges the paramountcy obligation regardless of good-faith intent behind the former. (confidence 0.80)
I.1. II.1.c. 3 principles 3 facts Conditions Narrative
AnalyticalOn Q102, a brief mention of the deficiencies buried within a confidential structural report does not satisfy Engineer A's duty once he recognized a real risk of injury to occupants. Such limited disclosure functions more as a liability shield for Engineer A than as a meaningful safeguard for the public, since the report's confidentiality ensured the information would never reach those capable of acting on it.
Resolved by: The board found that once a genuine safety risk is recognized, the duty to protect the public outweighs a minimal, functionally inert disclosure made only to preserve the engineer's own liability position. (confidence 0.85)
I.1. II.1.c. 3 principles 3 facts Conditions Narrative

What obligations, if any, does Engineer A have toward the building occupants themselves, who are third parties not privy to the confidentiality agreement between Engineer A and the client?

AnalyticalIn response to Q103, Engineer A owed an independent duty to the building occupants notwithstanding their absence from the confidentiality agreement. The Code's paramountcy clause establishes that the engineer's obligation to protect public safety exists independently of, and can override, contractual privity between engineer and client, precisely because third parties like occupants cannot protect themselves through that contractual relationship.
Resolved by: The board weighed contractual privity between engineer and client against the independent, non-contractual duty owed to third-party occupants and found the paramountcy clause overrides privity limits. (confidence 0.85)
I.1. II.1.c. II.4. 3 principles 3 facts Conditions Narrative
Principle tension (3)

How should Public Welfare Paramount over Confidentiality be balanced against Confidentiality in Building Report and Confidentiality in As-Is Sale Investigation when the confided information concerns systems outside Engineer A's own area of expertise?

AnalyticalAddressing Q201, the tension between public welfare and confidentiality is not diminished merely because the confided information falls outside Engineer A's own area of expertise. The paramountcy of public safety under the Code attaches to any engineer who becomes aware of a genuine risk to life or property, regardless of whether the specific defect lies within their licensed discipline, because the ethical duty derives from awareness and capacity to act, not from subject-matter authorship.
Resolved by: The board balanced discipline-based competency boundaries against the paramountcy duty and concluded that awareness and capacity to act, not subject-matter licensure, triggers the safety obligation. (confidence 0.80)
I.1. II.1.c. 3 principles 3 facts Conditions Narrative
AnalyticalThe case establishes a clear hierarchy in which Public Welfare Paramount over Confidentiality trumps both Confidentiality in Building Report and Confidentiality in As-Is Sale Investigation once an engineer becomes aware of a genuine risk of occupant injury. Engineer A's confidentiality obligations were not eliminated but were subordinated: he could still honor the narrow contractual duty not to publicize the structural report's contents, yet he was independently obligated under I.1. to notify public authorities of the code violations. The Board's conclusion shows that Confidentiality in Building Report and Confidentiality in As-Is Sale Investigation function as defeasible client-protective principles that yield when public safety is implicated, rather than as absolute contractual bars to disclosure.
Resolved by: The board subordinated the confidentiality principles to public welfare rather than treating them as absolute bars, allowing the narrow contractual nonpublication duty to survive while requiring independent notification of authorities. (confidence 0.85)
I.1. II.1.c. III.4. 3 principles 3 facts Conditions Narrative

Does Loyalty as Faithful Agent to Client conflict with Public Welfare of Building Occupants when the client explicitly states an intention to take no remedial action before an as-is sale?

AnalyticalRegarding Q202, Engineer A's loyalty as a faithful agent to the client is fundamentally subordinate to the Code's mandate to hold paramount the safety and welfare of the public. When the client's explicit no-remediation stance created a foreseeable risk to occupants, faithful agency could not ethically extend to silence before third-party authorities; the Code does not permit client loyalty to be exercised in a manner that knowingly endangers others.
Resolved by: The board subordinated the faithful-agent duty to the client to the paramount duty to protect the public once the client's explicit refusal to remediate made harm to occupants foreseeable. (confidence 0.80)
I.1. II.4. II.1.a. 3 principles 3 facts Conditions Narrative
AnalyticalLoyalty as Faithful Agent to Client and Public Welfare of Building Occupants were placed in direct conflict by the client's explicit as-is, no-remediation stance, and the Board resolved this conflict entirely in favor of the occupants' welfare rather than seeking a compromise that preserved client loyalty. This suggests that faithful-agent duties under II.4. are conditioned on the client's conduct remaining within lawful and safe bounds; once a client signals an intent to knowingly leave code violations unaddressed and transfer risk to unwitting third parties (the occupants and possibly the buyer), the agent relationship no longer commands deference on the disclosure question.
Resolved by: The board resolved the conflict wholly in favor of occupant welfare rather than seeking a middle path, treating faithful-agent loyalty as conditioned on the client staying within lawful and safe conduct. (confidence 0.85)
I.1. II.4. 3 principles 3 facts Conditions Narrative

In cases where confidentiality obligations and public safety obligations directly conflict, does the Code's paramountcy clause always resolve the tension in favor of disclosure, or are there limits based on scope of engagement and the engineer's discipline?

AnalyticalThe case demonstrates that principle prioritization does not depend on the engineer's disciplinary scope of expertise: even though the electrical and mechanical deficiencies fell outside Engineer A's structural competency, the paramount safety obligation attached the moment he recognized a risk of injury, independent of whether he was qualified to remediate or fully evaluate the underlying technical issues. This indicates that the duty to report under I.1. is triggered by awareness of risk, not by professional jurisdiction over the specific system at issue, which somewhat decouples the paramountcy principle from the competency-based principles that might otherwise limit an engineer's sphere of obligation.
Resolved by: The board subordinated competency-based limitations on an engineer's sphere of obligation to the paramount safety duty, holding that recognition of risk alone, not technical qualification to remediate it, activates the obligation that competes with confidentiality. (confidence 0.75)
I.1. II.1.c. 3 principles 3 facts Conditions Narrative
Theoretical (3)

From a deontological perspective, did Engineer A fulfill his duty to hold paramount the safety, health, and welfare of the public when he prioritized the confidentiality agreement over reporting known code violations?

AnalyticalOn Q301, from a deontological standpoint Engineer A failed his duty under Section I.1 by treating the confidentiality agreement as if it could override an unconditional obligation to protect public safety. A strict deontological reading of the Code treats the paramountcy clause as a threshold rule that trumps contractual promises once a genuine safety risk is recognized, meaning Engineer A's prioritization of confidentiality was a duty failure regardless of the eventual outcome for occupants.
Resolved by: The board applied a strict deontological reading in which the paramountcy clause functions as a threshold rule that automatically trumps the contractual confidentiality promise once a genuine risk is recognized, independent of consequences. (confidence 0.85)
I.1. 2 principles 3 facts Conditions Narrative

Did the outcome for the building occupants justify Engineer A's decision to withhold the safety violations from the appropriate authorities, given that the deficiencies posed a recognized risk of injury?

Did Engineer A act with professional integrity when he informed the client of the injury risk but nonetheless allowed the confidentiality agreement to override any further action to protect the occupants?

AnalyticalIn response to Q303, Engineer A's act of warning the client privately, while allowing the confidentiality agreement to foreclose further protective action, reflects only partial professional integrity. True integrity would have required Engineer A to escalate the matter to appropriate authorities once the client made clear no remedial action would be taken, rather than considering his ethical obligation discharged by an internal warning that occupants would never learn of.
Resolved by: The board treated the private warning as a necessary but insufficient discharge of the safety duty, finding that continued deference to confidentiality once the client refused remediation improperly subordinated public welfare to loyalty. (confidence 0.85)
I.1. II.4. 3 principles 3 facts Conditions Narrative
Counterfactual (3)

If Engineer A had been licensed as an electrical or mechanical engineer rather than solely a structural engineer, would the Board still have concluded that he had no independent duty to report the code violations to the appropriate authorities?

AnalyticalConcerning Q401, even if Engineer A had been licensed in electrical and mechanical engineering, the Board's conclusion would likely remain unchanged, since the ethical violation stemmed not from a lack of technical competence to independently verify the deficiencies but from the failure to report a recognized safety risk to appropriate authorities once it was confided and understood.
Resolved by: The board weighed technical competence to independently verify deficiencies against the duty to report a recognized risk, finding the latter controlling regardless of the former. (confidence 0.80)
I.1. 2 principles 3 facts Conditions Narrative

If the client had agreed to remediate the electrical and mechanical deficiencies before sale rather than insisting on an as-is sale with no remedial action, would the Board still have found Engineer A's nondisclosure to authorities unethical?

If the structural report had not been subject to a confidentiality agreement between Engineer A and the client, would the Board's conclusion that nondisclosure was unethical need to be reconsidered as a distinct confidentiality-versus-safety issue?

AnalyticalRegarding Q403, even absent a confidentiality agreement, the underlying safety-versus-loyalty conflict would still exist because Engineer A's duty to report arises from the paramountcy of public welfare rather than from the specific contractual confidentiality term; removing the agreement would eliminate one competing obligation but would not by itself have justified Engineer A's original nondisclosure, since the safety duty operates independently of any confidentiality clause.
Resolved by: The board separated the contractual confidentiality obligation from the independent public welfare obligation, concluding that removing the former would not retroactively justify the original nondisclosure because the latter operates on its own force. (confidence 0.80)
I.1. II.1.c. III.4. 3 principles 3 facts Conditions Narrative
Analytical questions (1)

Questions the analysis generates beyond the board’s explicit questions: implicit issues, principle tensions, theoretical framings, and counterfactuals. A question with an identified source board question appears nested under that question above.

Implicit (1)

Should the pre-existing agreement to keep the structural report confidential have anticipated and carved out an exception for safety-related disclosures discovered during the engagement, and does the absence of such a carve-out itself raise an ethical problem in how the engagement was structured?

AnalyticalThe Board's conclusion implicitly treats the confidentiality agreement as incapable of overriding the paramountcy clause, which suggests that any pre-engagement confidentiality arrangement failing to carve out safety disclosures is itself ethically deficient at the point it was formed. Engineer A and the client arguably should have anticipated, at the outset of a structural investigation of an occupied building, that safety-relevant information might surface, and the agreement should have been structured to permit disclosure to public authorities in such circumstances. The absence of such a carve-out does not, however, relieve Engineer A of his independent duty once the conflict actually arose.
Resolved by: The Board weighed the foreseeability of safety issues arising in an occupied-building investigation against the completeness of the confidentiality agreement, finding the agreement's silence on safety disclosure itself ethically deficient, while still holding the engineer independently responsible once the conflict materialized. (confidence 0.78)
I.1. II.1.c. III.4. 3 principles 3 facts Conditions Narrative
Decisions & Arguments (3)
View Extraction

Should Engineer A report the electrical and mechanical code violations to the appropriate public authorities, or confine his response to warning the client under the confidentiality agreement?

Options considered:
O1 Notify the appropriate building or safety authority of the electrical and mechanical code violations once the client confirms no remediation will occur before the as-is sale. Board's choice
O2 Limit action to briefly noting the deficiencies in the confidential structural report and privately warning the client, treating the confidentiality agreement as controlling further disclosure.
O3 Warn the client of the danger and make continued professional services or sign-off contingent on the client agreeing to remediate the deficiencies before proceeding with the sale.
Argument structure (Toulmin):
Claim unless the risk to occupants is merely speculative or not imminent, in which case a private warning to the client may suffice

Engineer A should have notified the appropriate public authorities of the electrical and mechanical code violations once he recognized they posed a real risk of injury to the building occupants, rather than limiting his response to a private warning to the client and a brief mention in the confidential structural report.

Grounds

During a structural investigation of an occupied building slated for as-is sale, maintenance personnel confided electrical and mechanical deficiencies to Engineer A; Engineer A recognized these as code violations posing an injury risk; he noted them briefly in a confidential report seen only by the client, informed the client of the danger, and the client stated no remedial action would be taken before the sale; Engineer A did not notify any public authority.

Warrant

Engineers must hold paramount the safety, health, and welfare of the public, and this duty prevails over an engineer's duty of confidentiality and faithful agency to a client whenever the engineer becomes aware of a genuine risk of injury to third parties who are not party to the confidentiality agreement.

Backing

NSPE Code I.1, II.1.c

Rebuttal

would not apply if the confidentiality agreement's scope and Section II.1.c's language require notification only where the danger is clear and imminent, and the deficiencies here did not meet that threshold

Engineer A Safety Violation Reporting Duty

Should Engineer A recommend that the client retain qualified electrical and mechanical specialists to evaluate the deficiencies, or merely note the deficiencies within his own structural report and take no further action?

Options considered:
O1 Formally advise the client to engage licensed electrical and mechanical engineers to evaluate and address the identified deficiencies before any sale. Board's choice
O2 Limit the response to briefly documenting the electrical and mechanical deficiencies within the confidential structural report, without further recommendation.
O3 Treat the electrical and mechanical issues as outside the structural engagement's scope and omit them from the report entirely, leaving discovery to any future specialist inspection.
Argument structure (Toulmin):
Claim provided the client does not already possess sufficient information to independently seek qualified help

Engineer A should have advised the client to retain qualified electrical and mechanical specialists to further evaluate and address the deficiencies, rather than merely mentioning them in his structural report and considering his obligation discharged.

Grounds

Engineer A was retained solely to assess structural soundness; during that investigation he identified electrical and mechanical deficiencies outside his own licensed discipline; he noted these deficiencies briefly in his confidential structural report without recommending specialist evaluation.

Warrant

Engineers must hold paramount public safety even for risks outside their own discipline, and where an engineer lacks the competence to evaluate or remediate a recognized hazard, professional responsibility requires directing the client to a qualified specialist rather than leaving the matter unaddressed.

Backing

NSPE Code I.1, II.2.b

Rebuttal

would not apply if the client already had independent knowledge of the deficiencies sufficient to seek specialist help on their own, or if Engineer A's mention in the report was reasonably understood by the client as a call to obtain further evaluation

Engineer A Safety Precedence Duty Structural-Only Engagement Scope

Should Engineer A have negotiated a safety-disclosure carve-out into the confidentiality agreement before accepting the engagement, or accepted the client's standard confidentiality terms without modification?

Options considered:
O1 Insist, before accepting the engagement, that the confidentiality agreement explicitly permit disclosure to public authorities if safety violations affecting occupants are discovered. Board's choice
O2 Accept the client's standard confidentiality terms without modification, relying on general professional judgment to handle any safety issues that arise during the engagement.
O3 Refuse to accept the confidential engagement unless the client agrees in advance to a safety-disclosure exception, foregoing the project if the client will not agree.
Argument structure (Toulmin):
Claim presumably, since explicit safety carve-outs are not always customary in real estate transaction engagements

Engineer A and the client should have anticipated, at the time the confidentiality agreement was formed, that safety-relevant information might surface during a structural investigation of an occupied building, and should have included an exception permitting disclosure to public authorities in such circumstances.

Grounds

Engineer A accepted a confidential engagement to investigate the structural soundness of an occupied building in advance of an as-is sale; the confidentiality agreement contained no exception for safety-related disclosures; during the investigation Engineer A learned of electrical and mechanical code violations from confided information.

Warrant

Engineers must hold paramount the safety, health, and welfare of the public over contractual duties of confidentiality, and agreements governing engineering investigations of occupied structures should be structured so as to preserve rather than foreclose that paramount duty.

Backing

NSPE Code I.1, III.4

Rebuttal

would not apply if confidentiality agreements are understood within the profession to always carry an implicit safety exception, in which case the absence of an explicit carve-out would not itself constitute an ethical defect at formation

Engineer A Faithful Agent Duty
Event Timeline (9)
9 sequenced 6 actions 3 events
Case timeline
Engineer A accepted the retention to investigate the structural integrity of the 60-year old occupied apartment building under an agreement requiring his structural report to remain confidential.
Fulfills (1)
  • Faithfulness to the Client
Causal-normative reasoning(confidence 0.80)
Accepting the confidential engagement sets in motion the entire causal chain, from the investigation to the eventual discovery of a safety risk, so fulfilling Faithfulness to the Client here establishes the very obligation that later collides with public safety duties once the risk is uncovered.
State changes (1)
  • began: Confidential Structural Report Term
Engineer A performed several structural tests on the building and determined that the building is structurally sound.
Fulfills (1)
  • Faithfulness to the Client
Causal-normative reasoning(confidence 0.75)
The investigation fulfills Faithfulness to the Client by producing the Structural Soundness Finding, but this same act of diligence is what causally generates the safety-relevant knowledge that later obligates disclosure beyond the client relationship.
The structural tests performed by Engineer A yield the determination that the 60-year-old apartment building is structurally sound.
During the course of the engagement, the client confides in Engineer A that the building contains electrical and mechanical deficiencies that violate applicable codes and standards. This transmission of confidential information brings Section III.4 into play and places Engineer A in possession of safety-relevant knowledge outside his own discipline.
State changes (3)
  • began: Confidential Structural Report Term
  • began: Code-Violating Building Deficiencies
  • began: Confidentiality Versus Safety Conflict
Although Engineer A is not an electrical or mechanical engineer, he realizes that the disclosed deficiencies could cause injury to the occupants of the building. This non-volitional realization creates his awareness of a public safety hazard.
State changes (2)
  • began: Engineer A Injury Risk Awareness
  • began: Occupant Injury Risk
Upon learning from the client of electrical and mechanical code violations, Engineer A informed the client that those deficiencies could cause injury to the occupants of the building.
Causal-normative reasoning(confidence 0.75)
Because Safety Risk Recognition arose directly from confidential information and threatens public welfare, Engineer A's warning to the client is guided by the paramount duty to protect public safety even though it creates tension with the confidentiality obligations governing the same engagement, making it a necessary but insufficient first step toward discharging that duty.
State changes (1)
  • began: Engineer A Injury Risk Awareness
Engineer A proceeded with the work on behalf of the client despite knowing the client would sell the building as is and take no remedial action, rather than insisting on further steps or notifying the appropriate authority.
At stake (1)
  • Paramount Public Health and Safety
Causal-normative reasoning(confidence 0.75)
Because A1 is the direct downstream result of Engineer A's decision not to disclose the building's safety risk to authorities, continuing to serve the client under the guise of faithfulness to the client effectively perpetuates a public safety risk rather than resolving it, showing that loyalty to a client cannot by itself justify inaction when it flows causally from suppressed critical safety information.
State changes (1)
  • began: Client No-Remediation Stance
In his written report, Engineer A made only a brief mention of his conversation with the client concerning the electrical and mechanical deficiencies.
Fulfills (1)
  • Confidentiality of Client Information
Causal-normative reasoning(confidence 0.70)
Limited Report Disclosure fulfills Confidentiality of Client Information by controlling what information reaches outside parties, but because it stems from the same causal branch that produced the safety risk, this limitation on disclosure foreshadows the deeper conflict resolved improperly in Nondisclosure to Authorities.
State changes (2)
  • began: Confided Deficiency Information Held
  • began: Confidential Structural Report Term
Engineer A, deferring to the confidentiality terms of his agreement, did not report the known safety violations to any third party or appropriate authority, an omission the Board treats as his conduct and finds cannot be condoned.
Fulfills (1)
  • Confidentiality of Client Information
Violates (2)
  • Paramount Public Health and Safety
  • Duty to Notify Appropriate Authority When Public Safety Is Endangered
Causal-normative reasoning(confidence 0.85)
Nondisclosure to Authorities fulfills Confidentiality of Client Information yet violates the Paramount Public Safety principle and the Duty to Notify, and because this choice directly causes Continued Client Service instead of remediation or warning to endangered parties, it represents the critical point where prioritizing client faithfulness over public welfare produces an unresolved public safety hazard.
State changes (1)
  • began: Safety Violations Withheld From Third Parties
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 Engineer A, retained by a client to investigate the structural integrity of a 60 year old occupied apartment building the client intends to sell. Your agreement with the client specifies that your structural report is to remain confidential, and the client has told you plainly that the building will be sold "as is" with no remedial work planned before the sale. Your structural tests confirm the building is sound. During the engagement, the client confides in you that the building's electrical and mechanical systems contain deficiencies that violate applicable codes and standards. You are not an electrical or mechanical engineer, but you recognize that these deficiencies could pose a risk of injury to the building's occupants, and you communicate this concern to the client. In your final report, you briefly reference your conversation with the client about these deficiencies, but consistent with the confidentiality terms, you do not disclose them to any outside party. You now face a series of decisions about how to proceed given what you know and what you are bound to keep confidential.

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: Structural Inspection Engineer

Tension between Engineer A Occupant Safety Duty and Structural-Only Engagement Scope

Acting as a faithful agent who follows the client's instructions and stays within the agreed scope of work conflicts with the obligation to report discovered safety violations that could endanger building occupants.

Tension between Engineer A Safety Precedence Duty and Structural-Only Engagement Scope

Tension between Engineer A Confidentiality Duty and Engineer A Safety Violation Reporting Duty

The duty to notify an appropriate authority about the safety violations found in the building conflicts with the constraint that limits what the engineer may disclose about client related information, since notifying authorities likely requires revealing details the client wanted kept confidential.

The constraint that sets a limit on how far the engineer can go along with the client's wishes conflicts with the duty to act as a faithful agent, because faithful agency would otherwise imply deference to the client's instruction to remain silent about the deficiencies.

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

The duty to notify an appropriate authority about the safety violations found in the building conflicts with the constraint that limits what the engineer may disclose about client related information, since notifying authorities likely requires revealing details the client wanted kept confidential.

Acting as a faithful agent who follows the client's instructions and stays within the agreed scope of work conflicts with the obligation to report discovered safety violations that could endanger building occupants.

The duty to notify an appropriate authority about the safety violations found in the building conflicts with the constraint that limits what the engineer may disclose about client related information, since notifying authorities likely requires revealing details the client wanted kept confidential.

The constraint that sets a limit on how far the engineer can go along with the client's wishes conflicts with the duty to act as a faithful agent, because faithful agency would otherwise imply deference to the client's instruction to remain silent about the deficiencies.

Acting as a faithful agent who follows the client's instructions and stays within the agreed scope of work conflicts with the obligation to report discovered safety violations that could endanger building occupants.

The Board’s deliberation

How the Board of Ethical Review resolved the case, verbatim from its published conclusions.

It was unethical for Engineer A not to report the safety violations to the appropriate public authorities.
Opening States (10)
Confidential Structural Report Term Confided Deficiency Information Held Code-Violating Building Deficiencies Occupant Injury Risk Structural-Only Engagement Scope Client No-Remediation Stance Engineer A Injury Risk Awareness Safety Violations Withheld From Third Parties Confidentiality Versus Safety Conflict Code Exception Disclosure Release
Summary
  • An engineer's duty to protect public safety extends beyond the specific scope of their contracted engagement when they discover hazards, even incidentally.
  • Confidentiality obligations to a client do not override the ethical obligation to report imminent safety violations to public authorities.
  • Limiting professional engagement to a narrow technical scope, such as structural review, does not exempt an engineer from broader duties to public welfare when safety issues become known.

© Licensed under the GNU GPL v3