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
Peer Review - Confidentiality Agreements
Step 4 of 5
Entity Review

251

Entities

2

Provisions

1

Precedents

17

Questions

18

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
Engineer A is held simultaneously within two binding obligation sets — the Peer Review Confidentiality Agreement and the Code's non-waivable public safety reporting duty — that cannot both be fully honored in the same moment of decision. The Board resolves the priority question in favor of public safety but does not eliminate the confidentiality obligation, does not transfer it to another party, and does not prescribe a definitive threshold at which the transition occurs. Instead, Engineer A must personally assess severity, imminence, and Engineer B's responsiveness to determine which rule-set governs at any given point, meaning the tension between the two obligation sets persists structurally throughout the entire escalation sequence and is never fully discharged by any single action.
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 (2)
View Extraction
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 42)
Obligation
Engineer B Ethics Code Business Form Non-Waivability Individual Compliance
This provision prohibits aiding unlawful practice, directly relating to Engineer B's obligation to recognize that business structures cannot waive individual compliance with ethics codes.
Action
Notify Engineer B of Violations
This provision governs the obligation to address unlawful engineering practice, which is directly implicated when notifying Engineer B of identified violations.
State
Engineer B Safety Code Violation Discovery During Peer Review
The provision on not aiding unlawful practice directly applies when Engineer A discovers Engineer B may be violating safety codes.
Obligation (2)
  • Engineer B Ethics Code Business Form Non-Waivability Individual Compliance
    This provision prohibits aiding unlawful practice, directly relating to Engineer B's obligation to recognize that business structures cannot waive individual compliance with ethics codes.
  • Engineer A Self-Policing Profession Peer Misconduct Reporting Foundational Duty
    This provision supports Engineer A's foundational duty to ensure the profession self-polices by not abetting unlawful or unsafe engineering practice.
Action (2)
  • Notify Engineer B of Violations
    This provision governs the obligation to address unlawful engineering practice, which is directly implicated when notifying Engineer B of identified violations.
  • Escalate to Proper Authorities
    Escalating violations to proper authorities is the mechanism by which an engineer avoids aiding or abetting unlawful engineering practice.
State (9)
  • Engineer B Safety Code Violation Discovery During Peer Review
    The provision on not aiding unlawful practice directly applies when Engineer A discovers Engineer B may be violating safety codes.
  • Engineer A Competing Duties. Confidentiality vs. Safety Reporting
    This provision creates the duty to report unlawful engineering practice that competes with Engineer A's confidentiality obligation.
  • Competing Duties Confidentiality vs. Public Safety Reporting
    This provision is explicitly identified as one of the two competing duties Engineer A faces regarding safety violation reporting.
  • Engineer A Peer Review Safety Violation Discovery
    The provision is triggered by Engineer A's discovery of potential safety code violations during the peer review.
  • Public Safety at Risk from Engineer B Design Work
    The provision addresses the obligation not to abet unlawful practice that endangers the public through non-compliant design work.
  • Public Safety at Risk from Engineer B Work
    The provision relates directly to the public safety risk created by Engineer B's potentially unlawful engineering work.
  • Graduated Escalation Obligation. Peer Review Safety Discovery
    The provision underpins Engineer A's obligation to escalate response proportionally based on the severity of the unlawful practice discovered.
  • Peer Review Confidentiality vs. Public Safety Override Threshold
    This provision establishes the safety-reporting duty that Engineer A weighs against confidentiality when determining if the threshold is crossed.
  • Potential Safety Risk Without Confirmed Imminent Harm. Engineer B Work
    The provision applies because even uncertain safety violations may constitute aiding unlawful practice if Engineer A takes no action.
Constraint (5)
  • Code of Ethics Universal Applicability Constraint. Engineer B Business Form Non-Waivability
    This provision prohibits aiding unlawful engineering practice, directly constraining Engineer B from hiding behind a business form to evade ethical obligations.
  • Self-Policing Profession Peer Misconduct Reporting Foundational Duty Constraint. Engineer A Safety Code Violation
    This provision underlies the duty not to abet unlawful practice, which grounds Engineer A's obligation to report Engineer B's safety code violations.
  • Peer Review Confidentiality Safety Override Constraint. Engineer A Safety Code Violation Discovery
    This provision supports the constraint that Engineer A cannot remain silent about safety violations, as silence could constitute aiding unlawful engineering practice.
  • Confidentiality Non-Bar to Safety-Critical Regulatory Disclosure Constraint. Engineer A State and Local Safety Codes
    This provision reinforces that confidentiality cannot bar disclosure when doing so would abet unlawful engineering practice through safety code violations.
  • Confidentiality Non-Bar to Safety-Critical Regulatory Disclosure Constraint. Engineer A NSPE Code Section III.4 Limit
    This provision directly limits the scope of III.4 confidentiality by establishing that aiding unlawful practice cannot be justified by a confidentiality agreement.
Principle (4)
  • Ethics Code Individual-Person Applicability Non-Waivability Through Business Form Affirmed by BER
    This provision targets unlawful practice by persons within business structures, directly linking to the BER affirmation that ethics obligations apply to Engineer B as an individual regardless of business form.
  • Engineering Self-Policing Obligation Invoked in Peer Review Safety Reporting Context
    Not aiding unlawful practice aligns with Engineer A's obligation to cooperate with authorities and report safety code violations discovered during peer review.
  • Confidentiality Non-Applicability To Engineer B Safety Code Violations
    If Engineer B's work violates safety codes, Engineer A cannot remain silent without potentially aiding unlawful engineering practice, making confidentiality inapplicable.
  • Confidentiality Non-Applicability to Public Danger Disclosure Invoked Against Peer Review Confidentiality Agreement
    The provision supports that a confidentiality agreement cannot be used to shield unlawful engineering practice from disclosure to proper authorities.
Role (1)
  • Engineer A Peer Review Safety Violation Discovering Engineer
    Engineer A must consider whether remaining silent about safety code violations discovered during peer review constitutes aiding unlawful engineering practice.
Event (4)
  • Safety Violations Discovered
    Discovering unlawful or improper engineering practice triggers the provision against aiding or abetting such practice.
  • Ethical Dilemma Instantiated
    The dilemma centers on whether staying silent about violations constitutes aiding or abetting unlawful engineering practice.
  • Corrective Action Deadline Triggered
    The deadline for corrective action directly relates to preventing continuation of potentially unlawful engineering practice.
  • Confidentiality Obligation Overridden
    Overriding confidentiality to report violations reflects the duty not to aid or abet unlawful engineering practice.
Resource (9)
  • NSPE-Code-Section-II.1.e
    This entity directly cites II.1.e as the provision obligating Engineer A to cooperate with proper authorities regarding code violations.
  • EngineerPublicSafetyEscalationStandard-CaseInstance
    II.1.e requires action when aware of alleged violations, directly governing Engineer A's duty to escalate discovered safety code violations.
  • Engineer-Public-Safety-Escalation-Standard
    II.1.e underpins the standard requiring escalation to authorities when Engineer B fails to take corrective action on violations.
  • StateAndLocalSafetyCodeRequirements-CaseInstance
    II.1.e is implicated when Engineer A discovers violations of state and local safety codes that constitute unlawful engineering practice.
  • OutOfScopeSafetyFindingReportingStandard-CaseInstance
    II.1.e requires Engineer A to report safety code violations even when outside the defined scope of the peer review role.
  • ClientConfidentialityPublicSafetyBalancingFramework-CaseInstance
    II.1.e is one of the competing obligations Engineer A must weigh when balancing confidentiality against the duty to report violations.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework
    II.1.e is a key provision in the balancing framework that weighs the duty to report unlawful practice against confidentiality obligations.
  • BER-Case-76-4
    BER Case 76-4 provides precedent for applying II.1.e when an engineer gains knowledge of information involving public health and safety violations.
  • NSPE-Code-of-Ethics
    II.1.e is a provision within the NSPE Code of Ethics, which serves as the primary normative authority governing Engineer A's obligations.
Capability (6)
  • Engineer B Ethics Code Business-Form Non-Waivability Self-Application
    This provision requires engineers not to aid unlawful practice, directly relating to Engineer B's obligation to recognize personal ethics code applicability regardless of business form.
  • Ethical Perception Engineer B Safety Code Violation Self-Recognition
    This provision requires engineers to avoid aiding unlawful practice, which requires Engineer B to perceive and recognize safety code violations in their own work.
  • Peer Review Safety Code Violation Detection Capability Engineer A Engineer B Design Projects
    This provision relates to Engineer A's capability to detect unlawful engineering practice through identification of safety code violations in Engineer B's work.
  • Engineer A Peer Review Safety Code Violation Detection
    This provision relates to Engineer A's capability to identify work that may constitute unlawful engineering practice through systematic review.
  • Peer Review Cooperation and Confidentiality Acceptance Capability Engineer B Peer Review Program
    This provision relates to Engineer B's obligation to cooperate with review processes that help prevent unlawful engineering practice.
  • Engineer B Peer Review Cooperation and Confidentiality Acceptance
    This provision relates to Engineer B's duty to cooperate with peer review, which serves to prevent continuation of potentially unlawful engineering practice.
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 72)
Obligation
Peer Review Confidentiality Agreement Signing Obligation Engineer A Peer Review Program
This provision directly requires engineers not to disclose confidential information without consent, grounding Engineer A's obligation to sign and honor the confidentiality agreement.
Action
Sign Confidentiality Agreement
Signing a confidentiality agreement is a formal acknowledgment of the duty not to disclose confidential information governed by this provision.
State
Engineer A Peer Review Confidentiality Agreement Bound
This provision directly governs Engineer A's formal obligation not to disclose confidential information obtained during the peer review.
Obligation (8)
  • Peer Review Confidentiality Agreement Signing Obligation Engineer A Peer Review Program
    This provision directly requires engineers not to disclose confidential information without consent, grounding Engineer A's obligation to sign and honor the confidentiality agreement.
  • Peer Review Confidentiality Non-Override of Safety Code Violation Reporting Obligation Engineer A Confidentiality Agreement Limit
    This provision establishes the confidentiality duty whose limits are at issue when Engineer A must recognize it cannot override the paramount safety reporting obligation.
  • Peer Review Confidentiality Agreement Cooperation Obligation Engineer B Peer Review Program
    This provision underpins the confidentiality protections that Engineer B relies upon when cooperating with the peer review process.
  • Engineer A Peer Review Confidentiality Maximum Disclosure Facilitation
    This provision directly governs Engineer A's obligation to honor the confidentiality agreement while facilitating maximum permissible disclosure within its bounds.
  • Engineer B Peer Review Confidentiality Agreement Cooperation
    This provision establishes the confidentiality framework that Engineer B must respect when cooperating fully with the peer review process.
  • Engineer A Confidentiality Non-Override Safety Code Violation Reporting
    This provision is the source of the confidentiality duty whose scope Engineer A must recognize as not overriding the safety reporting obligation.
  • Engineer A Confidentiality Scope Limitation Public Danger Disclosure
    This provision defines the confidentiality obligation whose scope Engineer A must assess to determine whether public danger disclosure is permissible.
  • Peer Review Program Collegial Improvement Participation Obligation Engineer A Engineer B Program
    This provision supports the confidentiality protections that make good-faith collegial participation in the peer review program possible.
Action (3)
  • Sign Confidentiality Agreement
    Signing a confidentiality agreement is a formal acknowledgment of the duty not to disclose confidential information governed by this provision.
  • Conduct Technical Documentation Review
    Reviewing confidential technical documentation creates the obligation under this provision to not disclose that information without consent.
  • Escalate to Proper Authorities
    This provision directly governs whether and how confidential information may be disclosed when escalating concerns to authorities.
State (8)
  • Engineer A Peer Review Confidentiality Agreement Bound
    This provision directly governs Engineer A's formal obligation not to disclose confidential information obtained during the peer review.
  • Engineering Peer Review Program Confidentiality Foundation
    The provision is the ethical basis for the confidentiality expectation that underpins the voluntary peer review program.
  • Peer Review Program Confidentiality Foundation Active
    The provision supports the systemic reliance on confidentiality as the foundation of professional trust within the peer review program.
  • Engineer A Competing Duties. Confidentiality vs. Safety Reporting
    This provision establishes the confidentiality duty that competes with Engineer A's safety reporting obligation.
  • Competing Duties Confidentiality vs. Public Safety Reporting
    This provision is explicitly identified as one of the two competing duties Engineer A faces regarding confidentiality.
  • Peer Review Confidentiality vs. Public Safety Override Threshold
    The provision defines the confidentiality obligation that Engineer A must weigh when deliberating whether the safety threshold overrides it.
  • Cooperative Disclosure Pathway. Collegial Discussion with Engineer B
    The provision supports a private collegial discussion as a first step that respects confidentiality before any external disclosure.
  • Engineer A Peer Review Safety Violation Discovery
    The provision governs what Engineer A may or may not disclose after discovering the safety violation during the confidential peer review.
Constraint (8)
  • Peer Review Confidentiality Agreement Binding Constraint. Engineer A Peer Review Program
    This provision directly creates the confidentiality obligation that binds Engineer A to the signed peer review confidentiality agreement.
  • Peer Review Program Integrity Confidentiality Foundation Constraint. Organized Peer Review Program
    This provision establishes the confidentiality duty that underpins the integrity and effectiveness of the organized peer review program.
  • Confidentiality Non-Bar to Safety-Critical Regulatory Disclosure Constraint. Engineer A NSPE Code Section III.4 Limit
    This provision is explicitly named in this constraint as the source of the confidentiality obligation whose limits are being defined.
  • Confidentiality Non-Bar to Safety-Critical Regulatory Disclosure Constraint. Engineer A State and Local Safety Codes
    This provision creates the confidentiality duty that this constraint limits when safety code violations are discovered.
  • Public Safety Paramount Over Confidentiality Constraint. Engineer A Engineer B Safety Code Violations
    This provision establishes the confidentiality duty that is overridden by public safety obligations in this constraint.
  • Peer Review Confidentiality Safety Override Constraint. Engineer A Safety Code Violation Discovery
    This provision is the source of the confidentiality duty that this constraint holds cannot operate as an absolute bar to safety disclosures.
  • Peer Review Program Collegial Improvement Non-Exploitation Constraint. Engineer A Peer Review Visit
    This provision underlies the confidentiality expectation that prohibits Engineer A from exploiting information obtained during the peer review visit.
  • Peer Review Program Collegial Improvement Non-Exploitation Constraint. Engineer A Peer Review Engagement
    This provision creates the confidentiality obligation that constrains Engineer A from exploiting peer review information for purposes beyond collegial improvement.
Principle (10)
  • Peer Review Confidentiality Agreement Obligation Binding Engineer A
    This provision directly embodies the obligation Engineer A undertook by signing the confidentiality agreement as a condition of serving as peer reviewer.
  • Peer Review Confidentiality Agreement Obligation Invoked by Engineer A
    The provision is the ethical basis for Engineer A's duty not to disclose confidential information learned during the peer review engagement.
  • Confidentiality-Bounded Public Safety Escalation Obligation On Engineer A
    The provision establishes the confidentiality boundary within which Engineer A must navigate the structured escalation pathway toward safety disclosure.
  • Confidentiality-Bounded Public Safety Escalation Sequence Invoked in Engineer A Engineer B Peer Review
    The provision grounds the confidentiality constraint that shapes the required escalation sequence Engineer A must follow before disclosing to authorities.
  • Peer Review Program Integrity Purpose Invoked In Engineer A Engineer B Review
    The provision supports the confidentiality expectation that makes peer review programs viable by protecting information shared within the review relationship.
  • Peer Review Program Integrity and Collegial Improvement Purpose Affirmed in Case Discussion
    The provision underpins the confidentiality norm that enables engineers to participate openly in peer review programs for professional improvement.
  • Confidentiality Non-Applicability To Engineer B Safety Code Violations
    The provision's scope is directly at issue when determining whether safety code violations fall outside its confidentiality protections.
  • Confidentiality Non-Applicability to Public Danger Disclosure Invoked Against Peer Review Confidentiality Agreement
    The provision is the rule being limited when public danger disclosure is deemed to override the confidentiality obligation it establishes.
  • Public Welfare Paramount Invoked By Engineer A In Peer Review Safety Discovery
    The provision is in tension with public welfare paramount, as Engineer A must weigh confidentiality obligations against the duty to protect public safety.
  • Public Welfare Paramount Invoked in Peer Review Safety Disclosure Decision
    The provision represents the confidentiality side of the conflict that public welfare paramount ultimately overrides in Engineer A's disclosure decision.
Role (2)
  • Engineer A Peer Review Safety Violation Discovering Engineer
    Engineer A signed a confidentiality agreement and must determine whether disclosing Engineer B's technical findings violates the duty to protect confidential client information.
  • Engineer B Peer-Reviewed Engineer Subject to Safety Code Findings
    Engineer B's technical processes and design documentation are the confidential information at issue that the provision is designed to protect from unauthorized disclosure.
Event (5)
  • Peer Review Program Established
    The peer review program creates the context in which confidential client information is accessed and must be protected.
  • Confidentiality Agreement Binding
    This provision directly governs the obligation not to disclose confidential information, which the agreement formalizes.
  • Ethical Dilemma Instantiated
    The dilemma arises from the tension between the confidentiality obligation under this provision and the duty to report safety violations.
  • Engineer B Notified of Violations
    Notifying Engineer B involves potentially disclosing confidential information obtained during the peer review.
  • Confidentiality Obligation Overridden
    This event directly represents a departure from the non-disclosure duty established by this provision.
Resource (9)
  • NSPE-Code-Section-III.4
    This entity directly cites III.4 as the provision obligating Engineer A not to disclose confidential information from a peer review engagement.
  • PeerReviewConfidentialityAgreement-CaseInstance
    III.4 directly applies to the confidentiality agreement Engineer A signed, reinforcing the non-disclosure obligation for information learned during peer review.
  • Peer-Review-Confidentiality-Agreement
    III.4 is the code provision that gives ethical force to the contractual confidentiality obligation created by the signed peer review agreement.
  • ClientConfidentialityPublicSafetyBalancingFramework-CaseInstance
    III.4 establishes the confidentiality duty that must be weighed against public safety obligations within this balancing framework.
  • Client-Confidentiality-vs-Public-Safety-Balancing-Framework
    III.4 is the specific code provision representing the confidentiality side of the graduated balancing framework applied in this case.
  • Peer-Review-Conduct-Standard
    III.4 underpins the confidentiality norms that are foundational to the collegial and constructive atmosphere of voluntary peer review programs.
  • PeerReviewConductStandard-CaseInstance
    III.4 governs the non-disclosure obligations that form part of the professional norms Engineer A must follow when conducting the peer review.
  • NSPE-Code-of-Ethics
    III.4 is a provision within the NSPE Code of Ethics, which is the primary normative authority governing Engineer A's confidentiality obligations.
  • BER-Case-76-4
    BER Case 76-4 provides precedent for applying III.4 when an engineer must weigh confidentiality against information damaging to a client involving public safety.
Capability (19)
  • Peer Review Confidentiality Agreement Scope Interpretation Capability Engineer A Peer Review Program
    This provision directly governs the confidentiality obligation that Engineer A must correctly interpret in scope and limits.
  • Peer Review Confidentiality Non-Override Safety Reporting Recognition Capability Engineer A Confidentiality Agreement Limit
    This provision is the confidentiality duty that Engineer A must recognize cannot override paramount safety reporting obligations.
  • Conflict Resolution Engineer A Confidentiality Safety Tension
    This provision establishes the confidentiality side of the tension Engineer A must resolve against safety reporting duties.
  • Norm Competence Engineer A Peer Review Safety Reporting Hierarchy
    This provision is one of the key norms Engineer A must store and apply when navigating the hierarchy between confidentiality and safety reporting.
  • Engineer A Dual NSPE Code Provision Simultaneous Obligation Recognition
    This provision is explicitly one of the two simultaneously triggered NSPE Code obligations Engineer A must recognize in the peer review scenario.
  • Engineer A Peer Review Confidentiality Trust-Building Rationale Articulation
    This provision is the confidentiality rule whose instrumental trust-building rationale Engineer A must understand and articulate.
  • Engineer A Peer Review Confidentiality Agreement Scope Interpretation
    This provision directly governs the confidentiality agreement whose scope and limits Engineer A must correctly interpret.
  • Engineer A Confidentiality Non-Override Safety Code Violation Reporting Recognition
    This provision is the confidentiality obligation that Engineer A must recognize cannot override the duty to report safety code violations.
  • Peer Review Collegial Improvement Purpose Fidelity Capability Engineer A Peer Review Program
    This provision supports the confidentiality framework that enables the collegial improvement purpose of peer review programs.
  • Engineer A Peer Review Collegial Improvement Purpose Fidelity
    This provision underpins the confidentiality protections that make good-faith collegial peer review participation possible.
  • Engineer A Peer Review Program Public Benefit Recognition
    This provision establishes the confidentiality protections whose instrumental value for public benefit through peer review Engineer A must recognize.
  • Peer Review Pre-Reporting Advisory Warning Delivery Capability Engineer A To Engineer B
    This provision relates to the confidentiality context within which Engineer A must navigate before disclosing information to governmental authorities.
  • Engineer A Peer Review Pre-Reporting Advisory Warning Delivery
    This provision governs the confidentiality obligations that shape how Engineer A must handle pre-reporting notification to Engineer B.
  • Engineer A Peer Review Imminent Harm Threshold Discrimination and Response Calibration
    This provision establishes the confidentiality duty whose override threshold Engineer A must assess against imminent harm risk.
  • Engineer A Peer Review Sequential Escalation Pathway Execution
    This provision governs the confidentiality obligations that frame the sequential escalation pathway Engineer A must execute.
  • Peer Review Sequential Escalation Pathway Execution Capability Engineer A Structured Pathway
    This provision establishes the confidentiality framework within which the structured sequential escalation pathway must be executed.
  • Ethical Perception Engineer A Safety Code Violation Recognition
    This provision establishes the confidentiality obligation whose limits Engineer A must perceive when recognizing ethically salient safety violations.
  • Peer Review Cooperation and Confidentiality Acceptance Capability Engineer B Peer Review Program
    This provision directly governs the confidentiality protections that Engineer B must accept and honor during the peer review process.
  • Engineer B Peer Review Cooperation and Confidentiality Acceptance
    This provision directly governs the confidentiality agreement that Engineer B must accept and honor as part of peer review cooperation.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

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

Principle Established:

An engineer who gains knowledge of information damaging to a client's interest that involves public health and safety faces competing ethical obligations between confidentiality and the duty to protect the public.

Citation Context:

The Board cited this case as a prior example of an engineer gaining knowledge of information damaging to a client's interest that involved public health and safety, establishing precedent for the current dilemma.

Relevant Excerpts
discussion: "The BER has considered at least one case involving an engineer gaining knowledge of information damaging to a client's interest which involved the public health and safety (see BER Case 76-4)."
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 74% Facts Similarity 61% Discussion Similarity 77% Outcome Alignment 100%
Same outcome True View Synthesis
Component Similarity 70% Facts Similarity 67% Discussion Similarity 98% Outcome Alignment 100%
Same outcome True View Synthesis
Component Similarity 64% Facts Similarity 63% Discussion Similarity 43% Outcome Alignment 100%
Same outcome True View Synthesis
Component Similarity 63% Facts Similarity 53% Discussion Similarity 29% Outcome Alignment 100%
Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 55% Discussion Similarity 34% Outcome Alignment 100%
Same outcome True View Synthesis
Component Similarity 59% Facts Similarity 42% Discussion Similarity 37% Outcome Alignment 100%
Same outcome True View Synthesis
Component Similarity 59% Facts Similarity 52% Discussion Similarity 69% Outcome Alignment 100%
Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 42% Discussion Similarity 34% Outcome Alignment 100%
Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 49% Discussion Similarity 39% Outcome Alignment 100%
Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 50% Discussion Similarity 39% Outcome Alignment 100%
Same outcome True View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

What are Engineer A’s ethical responsibilities under the circumstances?

Board conclusion If Engineer A determines that Engineer B’s work is or may be in violation of state and local safety requirements and endangers public health, safety and welfare, the appropriate action is for Engineer A to immediately discuss these issues with Engineer B in an effort to seek clarification and early resolution of this issue.
Implicit (4)

Does the confidentiality agreement Engineer A signed have any legal or ethical validity to the extent it purports to suppress disclosure of active public safety violations, and should engineers be permitted to sign such agreements in the first place?

AnalyticalThe Board's conclusion implicitly treats the confidentiality agreement as a legitimate and binding professional commitment while simultaneously holding that it cannot override the public safety reporting obligation. This dual treatment, though practically workable, leaves unresolved a deeper structural problem: the confidentiality agreement as designed creates a foreseeable and recurring conflict that the peer review program itself is institutionally responsible for resolving. Because the Code of Ethics imposes non-waivable individual duties on every engineer regardless of the business or programmatic context in which they operate, any confidentiality agreement that purports - even implicitly - to suppress disclosure of active safety code violations is void to that extent as a matter of professional ethics. The peer review program therefore bears an affirmative institutional obligation to include an explicit carve-out provision stating that safety code violations discovered during peer review must be reported to the appropriate authorities notwithstanding the confidentiality agreement. The absence of such a provision does not merely leave individual engineers in an uncomfortable dilemma; it represents a structural ethical failure of the program's design that foreseeably places peer reviewers in the position of appearing to choose between contractual loyalty and public safety - a choice the Code does not permit them to make in favor of confidentiality.
AnalyticalA confidentiality agreement that purports to suppress disclosure of active public safety violations has no valid ethical force under the NSPE Code, and its legal enforceability is similarly suspect. The Code's provision that engineers shall not disclose confidential information without consent (Section III.4) is explicitly bounded by the overriding duty to protect public safety. No contractual instrument can extinguish a duty that the Code imposes on every individual engineer as a non-waivable personal obligation. Engineers should therefore be cautious about signing peer review confidentiality agreements that do not contain explicit carve-outs for safety-critical disclosures. A well-drafted agreement would affirmatively state that nothing in it prevents the reviewer from reporting discovered safety code violations to proper authorities. The absence of such a carve-out does not, however, create an enforceable obligation of silence - it merely creates ambiguity that the engineer must resolve in favor of public safety. Peer review programs that present reviewers with agreements lacking this carve-out are themselves operating with a structural ethical deficiency.

At what point does Engineer A's continued silence about Engineer B's violations - even during the collegial discussion phase - constitute aiding or abetting unlawful engineering practice under the Code?

AnalyticalThe Board's conclusion that Engineer A should first discuss the violations with Engineer B before escalating to authorities is ethically sound as a general rule, but it carries a latent risk that the Board does not address: the collegial notification step could itself become a vehicle for aiding or abetting unlawful engineering practice if Engineer A, having notified Engineer B, then fails to follow through with regulatory reporting when Engineer B does not take prompt and verifiable corrective action. Engineer A's obligation does not terminate at the moment of collegial notification. Rather, notification of Engineer B triggers a secondary, time-bounded obligation to monitor whether corrective action is actually undertaken. If Engineer B acknowledges the violations but delays correction, disputes Engineer A's findings without credible technical justification, or takes no action, Engineer A's continued silence would cross the threshold from collegial deference into complicity with ongoing unlawful practice. This means Engineer A must establish - at the time of the collegial discussion - a clear and documented understanding of what corrective action is expected, by when, and what Engineer A will do if that action is not taken. The absence of such a follow-through framework renders the collegial discussion step ethically incomplete, regardless of how constructively it is conducted.
AnalyticalEngineer A's continued silence about Engineer B's violations - even during the collegial discussion phase - risks crossing into aiding or abetting unlawful engineering practice under Code Section II.1.e if that silence is prolonged, if Engineer B is unresponsive, or if the risk to the public is ongoing and concrete. The collegial notification step prescribed by the Board is not a license for indefinite delay. It is a first step in a time-bounded sequential escalation, not an open-ended courtesy period. If Engineer A notifies Engineer B and Engineer B fails to acknowledge the problem, disputes the finding without credible technical basis, or commits to corrective action but takes no meaningful steps, Engineer A's continued inaction would shift from collegial patience to complicit silence. The threshold at which silence becomes aiding and abetting is crossed when Engineer A possesses a good-faith belief that a violation exists, has given Engineer B a reasonable opportunity to respond, and yet takes no further action while the public remains exposed. The Code does not permit Engineer A to treat the collegial discussion as a substitute for escalation - it is only a precursor to it.

Should the peer review program itself bear any institutional responsibility for establishing clear protocols that resolve the confidentiality-versus-safety tension before reviewers encounter it in the field, rather than leaving individual engineers to navigate this conflict alone?

AnalyticalThe peer review program itself bears significant institutional responsibility for the ethical dilemma Engineer A faces. By establishing a confidentiality agreement without an explicit safety-disclosure carve-out, the program placed individual engineers in a foreseeable conflict between two legitimate duties. This is a structural design failure, not merely an individual ethical challenge. A well-governed peer review program should, before any reviewer enters the field, establish written protocols that (1) define the categories of findings that override confidentiality, (2) specify the escalation sequence and its time parameters, (3) clarify the reviewer's reporting obligations to authorities, and (4) indemnify reviewers who make good-faith safety disclosures from retaliation or breach-of-contract claims. The absence of these protocols does not relieve Engineer A of their individual ethical obligations, but it does mean the program has externalized its ethical risk onto individual reviewers rather than managing it institutionally. Programs that fail to resolve the confidentiality-versus-safety tension in their governing documents are, in effect, asking engineers to improvise solutions to a conflict the program itself created.

How should Engineer A assess and document the severity and imminence of the public safety risk discovered during the peer review, and does the standard of 'may be in violation' impose the same escalation obligations as a confirmed violation?

AnalyticalBeyond the Board's finding that Engineer A should immediately discuss the violations with Engineer B, the Board's prescribed sequential escalation pathway carries an implicit but critical temporal limitation: the collegial discussion step is only ethically permissible when the risk is uncertain or non-imminent. Where Engineer A assesses the public safety risk as imminent and severe - rather than merely potential - the sequential model collapses, and Engineer A bears an independent obligation to notify the proper authorities without delay, regardless of whether Engineer B has been consulted first. The 'may be in violation' standard the Board employs does not eliminate this distinction; it simply reflects the facts of this particular case. Engineer A must therefore conduct a documented severity-and-imminence assessment at the moment of discovery, because that assessment determines which escalation pathway is ethically required. Failure to make and record that assessment is itself an ethical shortcoming, since it leaves Engineer A unable to demonstrate that the chosen pathway was calibrated to the actual level of risk.
AnalyticalThe standard of 'may be in violation' articulated in the Board's conclusion imposes essentially the same escalation obligations as a confirmed violation, because the Code's public safety duty is triggered by a good-faith belief of risk, not by certainty of harm. Engineer A is not required to conduct a definitive legal or technical adjudication before acting. The appropriate standard is whether a reasonable, competent engineer in Engineer A's position would have a genuine, professionally grounded concern that the work poses a risk to public health, safety, or welfare. If that threshold is met, Engineer A must document the specific findings - the nature of the apparent code discrepancy, the design elements involved, the applicable state and local safety code provisions, and the potential harm pathway - and proceed with the escalation sequence. Documentation serves two purposes: it provides Engineer B with a precise basis for response during the collegial discussion phase, and it creates a record that Engineer A acted in good faith if the matter later requires regulatory reporting. The severity and imminence of the risk should calibrate the pace of escalation, not the decision to escalate.
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 Peer Review Confidentiality Agreement Obligation conflict with the Public Welfare Paramount principle, and if so, which should prevail and under what threshold of risk?

AnalyticalThe tension between the Peer Review Confidentiality Agreement Obligation and the Public Welfare Paramount principle was resolved not by eliminating confidentiality but by subordinating it to a threshold condition: once Engineer A discovers work that may violate state and local safety codes and endanger the public, the confidentiality obligation loses its force with respect to that specific finding. The case teaches that confidentiality in professional peer review programs is a conditional, not absolute, duty - it governs ordinary business information and practice observations, but it cannot serve as a legal or ethical shield against the disclosure of active public safety violations. The resolution is not that confidentiality is unimportant, but that it was never intended by the Code to extend to circumstances where silence would make Engineer A complicit in ongoing harm. The practical implication is that engineers entering peer review confidentiality agreements should understand from the outset that those agreements carry an implicit safety-override clause, whether or not the written agreement makes that clause explicit.

Does the Peer Review Program Integrity and Collegial Improvement Purpose conflict with the Engineering Self-Policing Obligation when the collegial improvement goal requires confidentiality that would delay or prevent mandatory safety reporting?

AnalyticalThe interaction between the Peer Review Program Integrity and Collegial Improvement Purpose and the Engineering Self-Policing Obligation reveals a structural hierarchy in which the program's collegial improvement goal is preserved as the first-step mechanism, but is ultimately subordinate to the profession's self-policing duty when collegial resolution fails or is unavailable. The Board's prescribed sequential escalation pathway - notify Engineer B first, then escalate to authorities if necessary - represents an attempt to honor both principles simultaneously rather than treating them as mutually exclusive. This synthesis teaches that professional program design and individual ethical duty are not inherently in conflict: a well-functioning peer review program can serve both collegial improvement and public safety simultaneously, precisely because the collegial notification step gives Engineer B the opportunity to self-correct before external reporting becomes necessary. However, the synthesis also reveals a limit: when the collegial improvement purpose is used as a reason to delay or avoid mandatory safety reporting indefinitely, it crosses from a legitimate first step into an ethical violation in its own right, effectively converting a program designed to improve practice into a mechanism for suppressing safety disclosures.

Does the Imminent Harm Threshold for Mandatory Peer-Review Safety Escalation conflict with the Confidentiality-Bounded Public Safety Escalation Sequence, in that the sequential escalation model may be inappropriate when harm is imminent and delay itself becomes an ethical violation?

AnalyticalThe interaction between the Imminent Harm Threshold for Mandatory Peer-Review Safety Escalation and the Confidentiality-Bounded Public Safety Escalation Sequence reveals that the sequential escalation model is not a rigid procedural rule but a risk-calibrated framework. The Board's conclusion prescribes collegial discussion as the appropriate first step under the facts presented - where the violation 'may be' rather than certainly is a safety threat - but this prescription implicitly encodes a variable: as the severity and imminence of harm increases, the permissible delay before bypassing the collegial step and reporting directly to authorities decreases, and at the extreme of imminent catastrophic harm, the sequential model collapses entirely into an immediate reporting obligation. This teaches a broader principle about how the Code resolves tensions between process-oriented duties and outcome-oriented duties: process obligations (notify Engineer B first) are ethically valid when they do not themselves generate harm through delay, but they become ethically impermissible when adherence to the process is itself the mechanism by which harm materializes. The Ethics Code Individual-Person Applicability Non-Waivability principle reinforces this conclusion by establishing that no programmatic structure - including a peer review confidentiality agreement - can contractually override Engineer A's individual duty to protect the public when that duty is triggered by a sufficiently serious risk.

Does the Ethics Code Individual-Person Applicability Non-Waivability principle conflict with the Peer Review Confidentiality Agreement Obligation, in that Engineer A cannot contractually waive a duty to report safety violations that the Code imposes on every individual engineer regardless of the business or programmatic context in which they operate?

Theoretical (4)

From a deontological perspective, did Engineer A fulfill their categorical duty to protect public safety by prioritizing the reporting obligation over the confidentiality agreement they voluntarily signed, and does the existence of a prior contractual commitment to confidentiality diminish or eliminate that categorical duty?

AnalyticalFrom a deontological perspective, Engineer A's categorical duty to protect public safety is not diminished by the prior voluntary acceptance of a confidentiality agreement. A Kantian analysis would hold that the maxim 'engineers may contractually suppress disclosure of safety violations' cannot be universalized without destroying the very foundation of public trust in engineering licensure. The confidentiality agreement, to the extent it purports to override the safety reporting duty, is not a morally binding commitment because it asks Engineer A to act on a principle that, if universalized, would be self-defeating and harmful. The prior contractual commitment therefore does not eliminate the categorical duty - it merely creates a competing obligation of lesser moral weight. Engineer A's duty to disclose is not contingent on the absence of a confidentiality agreement; it exists independently of and hierarchically above that agreement. The deontological framework thus supports the conclusion that Engineer A must report, and that the confidentiality agreement provides no moral shelter from that obligation.

From a consequentialist perspective, does the Board's prescribed sequential escalation pathway - first notifying Engineer B before reporting to authorities - produce the best overall outcomes for public safety, given that the delay inherent in collegial discussion could allow harm to materialize if Engineer B is uncooperative or the risk is more imminent than initially assessed?

AnalyticalFrom a consequentialist perspective, the Board's sequential escalation pathway - notify Engineer B first, then escalate to authorities - produces better overall outcomes in the typical case but may produce worse outcomes in scenarios involving imminent harm or an uncooperative Engineer B. The collegial first step has genuine consequentialist value: it allows for rapid private correction without the reputational, legal, and programmatic costs of immediate regulatory involvement, and it preserves the peer review program's effectiveness as a voluntary improvement mechanism. However, the consequentialist calculus shifts decisively when the probability of harm is high, the harm is severe and irreversible, or Engineer B's response signals bad faith. In those scenarios, the delay inherent in the collegial step produces a net negative outcome by allowing continued public exposure. A consequentialist framework therefore supports a conditional sequential model: the collegial step is appropriate when the risk is uncertain or moderate and Engineer B appears cooperative, but direct regulatory reporting is required when the risk is imminent, severe, or Engineer B is unresponsive. The Board's conclusion implicitly acknowledges this by framing the obligation as calibrated to the circumstances, but a fully consequentialist analysis would make the conditionality more explicit.

From a virtue ethics perspective, did Engineer A demonstrate the professional virtues of courage and integrity by being willing to confront Engineer B directly about the safety violations rather than either remaining silent to preserve the collegial peer review relationship or immediately escalating without giving Engineer B an opportunity to respond?

AnalyticalFrom a virtue ethics perspective, Engineer A demonstrates the professional virtues of courage and integrity most fully by engaging Engineer B directly and honestly about the discovered violations rather than either remaining silent to preserve the collegial relationship or bypassing Engineer B entirely to report immediately to regulators. Courage is required because confronting a peer about potential professional failures risks damaging the relationship, inviting defensiveness, and creating professional friction. Integrity is demonstrated by refusing to allow the confidentiality agreement to function as a shield for conduct that endangers the public. However, the virtue ethics analysis also recognizes that Engineer A's acceptance of the peer reviewer role and the confidentiality agreement creates a relational obligation of good faith toward the program and toward Engineer B - and that acting with integrity means honoring that obligation by giving Engineer B a genuine opportunity to respond before escalating externally. The virtuous engineer is neither a passive bystander nor a reflexive regulator; they are a professional who exercises practical wisdom to navigate competing obligations in a way that serves both the immediate relationship and the broader public interest. This analysis supports the Board's sequential escalation model as the virtuous pathway in the typical case.

From a virtue ethics perspective, does Engineer A's voluntary acceptance of the peer reviewer role and the accompanying confidentiality agreement create a special relational obligation of good faith toward the peer review program and Engineer B's firm - and if so, does acting with integrity require Engineer A to exhaust every internal resolution pathway before resorting to external reporting, or does genuine professional integrity demand immediate transparency with regulators when public safety is at stake?

Counterfactual (4)

What if Engineer A had determined that the safety violations posed an imminent and severe risk of harm - rather than a potential or uncertain risk - would the Board's prescribed sequential escalation pathway still apply, or would Engineer A be obligated to bypass the collegial notification step and report directly and immediately to the proper authorities?

AnalyticalIf Engineer A had determined that the safety violations posed an imminent and severe risk of harm, the Board's sequential escalation pathway would not apply in its standard form. The collegial notification step is appropriate when the risk is uncertain, moderate, or capable of being remediated before harm materializes. When harm is imminent - meaning the public is currently exposed to a concrete and serious risk from structures or systems already in use or under construction - the delay inherent in awaiting Engineer B's response is itself an ethical violation. In that scenario, Engineer A would be obligated to report directly and immediately to the proper authorities, potentially concurrent with or even before notifying Engineer B. This conclusion is supported by the constraint that imminent harm triggers an immediate escalation bypass, and by the general principle that the public safety duty is paramount. The Board's conclusion implicitly preserves this distinction by framing the sequential pathway as appropriate to the facts of the case - which involve a potential rather than confirmed imminent risk - but a more explicit articulation of the imminent harm exception would strengthen the ethical framework.

What if Engineer A had refused to sign the confidentiality agreement as a precondition of serving as a peer reviewer - would Engineer A have been ethically justified in declining the role, and would the absence of a confidentiality agreement have simplified or complicated Engineer A's subsequent obligation to report Engineer B's safety violations to the authorities?

AnalyticalIf Engineer A had refused to sign the confidentiality agreement as a precondition of serving as a peer reviewer, Engineer A would have been ethically justified in declining the role on those grounds, particularly if the agreement lacked a safety-disclosure carve-out. An engineer cannot be ethically required to accept a contractual constraint that would, in foreseeable circumstances, prevent them from fulfilling their paramount duty to protect public safety. Refusing to sign would not have been an act of bad faith toward the program - it would have been an act of professional integrity. The absence of a confidentiality agreement would have simplified Engineer A's subsequent obligations considerably: without the agreement, the only competing consideration would be the general professional norm of collegial courtesy, which is far weaker than a formal contractual commitment. Engineer A would still have been well-advised to notify Engineer B before escalating to authorities, as a matter of professional courtesy and to allow for rapid private correction, but the ethical weight of that step would have been advisory rather than obligatory. The confidentiality agreement thus adds ethical complexity without adding ethical legitimacy to the suppression of safety disclosures.

What if Engineer B, upon being notified by Engineer A of the potential safety code violations, had acknowledged the problem and committed to immediate corrective action - would Engineer A's obligation to report to the proper authorities be fully discharged by that private resolution, or would Engineer A still bear an independent duty to notify regulators given that the public was potentially already exposed to risk from the non-compliant designs?

AnalyticalIf Engineer B, upon being notified, acknowledged the problem and committed to immediate corrective action, Engineer A's obligation to report to proper authorities would not be fully discharged by that private resolution alone. The public may already have been exposed to risk from non-compliant designs that are in use, under construction, or submitted for permit approval. Engineer A must assess whether the corrective commitment is credible, specific, and timely - and whether the existing exposure to risk requires regulatory notification independent of Engineer B's future remediation. If the non-compliant designs have already been implemented in structures accessible to the public, the regulatory authorities may need to be informed so that they can independently assess whether interim protective measures are required. Engineer A's duty runs to the public, not merely to securing Engineer B's promise of future compliance. A private resolution that leaves the public unaware of a past exposure to risk, and leaves regulators without the information needed to verify remediation, does not fully satisfy Engineer A's ethical obligations under the Code. The appropriate outcome of a successful collegial discussion is not silence but a jointly agreed disclosure to the relevant authorities, or at minimum Engineer A's independent verification that the risk has been fully remediated before concluding that no further action is required.

What if the peer review program itself had included an explicit provision in its governing rules stating that safety code violations discovered during peer review must be reported to authorities regardless of the confidentiality agreement - would such a provision have eliminated Engineer A's ethical dilemma entirely, and does the absence of such a provision in the program's design represent a structural ethical failure of the program itself?

AnalyticalIf the peer review program had included an explicit provision requiring that safety code violations discovered during peer review be reported to authorities regardless of the confidentiality agreement, such a provision would have substantially reduced - though not entirely eliminated - Engineer A's ethical dilemma. It would have eliminated the tension between the confidentiality agreement and the safety reporting duty by making the safety exception part of the agreement itself, giving Engineer A clear contractual and ethical authority to report. However, it would not have eliminated all judgment: Engineer A would still need to assess the severity and imminence of the risk, determine the appropriate escalation sequence, and decide whether to notify Engineer B before or concurrently with reporting to authorities. The absence of such a provision in the program's design does represent a structural ethical failure. The program's designers could reasonably have foreseen that peer reviewers might discover safety violations, and the failure to address this foreseeable scenario in the program's governing documents reflects either an oversight or an implicit - and ethically indefensible - preference for confidentiality over safety. Programs that rely on individual engineers to improvise solutions to conflicts the program itself created are not operating with the institutional integrity that the engineering profession demands.
Decisions & Arguments (7)
View Extraction

Should Engineer A honor the peer review confidentiality agreement and refrain from external disclosure, first discuss the violations privately with Engineer B as a time-bounded collegial step before escalating to authorities, or immediately report the discovered safety code violations directly to the proper authorities without first consulting Engineer B?

Options considered:
O1 Immediately and expeditiously raise the discovered safety code violations directly with Engineer B in a collegial discussion, seeking clarification and early resolution, while documenting the findings and establishing a clear expectation of corrective action, then escalate to proper authorities if Engineer B fails to respond adequately within a reasonable time. Board's choice
O2 Bypass the collegial notification step and report the discovered safety code violations immediately to the appropriate governmental authorities, on the grounds that the public safety duty is paramount and any delay, including the time required for collegial discussion, risks ongoing public exposure to harm from non-compliant designs.
O3 Treat the signed confidentiality agreement as a binding professional commitment that precludes external disclosure, and refrain from reporting the discovered violations to authorities, relying on the peer review program's internal processes and Engineer B's own professional obligations to address any safety concerns identified during the review.
Argument structure:
Warrants

Two competing obligations are in tension: (1) the Peer Review Confidentiality Agreement Obligation, which binds Engineer A to non-disclosure of confidential information involving the peer-reviewed firm, and (2) the Public Welfare Paramount principle, which establishes that Engineer A's paramount responsibility as a licensed professional engineer is to protect public health and safety, a duty the Code imposes on every individual engineer as a non-waivable personal obligation that no contractual instrument can extinguish. A third warrant, the Peer Review Judgment and Discretion Contextual Safety Assessment Obligation, requires Engineer A to assess severity and imminence before selecting an escalation pathway.

Rebuttals

Uncertainty arises because the severity and imminence of the safety risk remain unconfirmed: if the violation is minor or speculative, the confidentiality warrant retains more force and the collegial discussion step is clearly appropriate; if harm is imminent and severe, the sequential model collapses and immediate reporting is required. Additional uncertainty is created by the scope ambiguity of the confidentiality agreement itself: if it was never intended to suppress regulatory safety reporting, the conflict may be less acute than it appears.

Grounds

Engineer A has signed a confidentiality agreement as a condition of serving as a peer reviewer in an organized peer review program. During the review, Engineer A discovers that Engineer B's work may be in violation of state and local safety code requirements and could endanger public health, safety, and welfare. The risk is characterized as potential rather than confirmed imminent harm.

Peer Review Confidentiality Non-Override of Safety Code Violation Reporting Obligation Engineer A Confidentiality Agreement Limit Peer Review Confidentiality Agreement Obligation Binding Engineer A

Should Engineer A apply the standard sequential escalation pathway, giving Engineer B a reasonable opportunity to respond and self-correct before reporting to authorities, or, upon assessing the severity and imminence of the risk, bypass the collegial step and report immediately to proper authorities without awaiting Engineer B's response?

Options considered:
O1 Conduct and document a professional severity-and-imminence assessment, determine that the risk is potential rather than confirmed imminent, and proceed with the sequential escalation pathway: notifying Engineer B, establishing a clear corrective action expectation with a defined timeframe, and committing to escalate to proper authorities if Engineer B fails to respond adequately. Board's choice
O2 Upon assessing that the severity and imminence of the public safety risk is sufficient to trigger the imminent harm exception, bypass the collegial notification step and report the discovered violations directly and immediately to the proper governmental authorities, potentially notifying Engineer B concurrently but not awaiting Engineer B's response before contacting regulators.
O3 Before initiating either the collegial discussion or external reporting, engage an independent technical expert to verify whether the identified discrepancies constitute actual safety code violations, on the grounds that the 'may be in violation' standard does not yet meet the good-faith threshold for mandatory escalation and that premature reporting could damage the peer review program and Engineer B's reputation without sufficient basis.
Argument structure:
Warrants

Two competing obligations govern this decision: (1) the Good Faith Safety Concern Threshold principle, which establishes that the public safety duty is triggered by a professionally grounded good-faith belief of risk, not by certainty of harm, meaning the 'may be in violation' standard imposes essentially the same escalation obligations as a confirmed violation; and (2) the Peer Review Imminent Harm Immediate Notification Obligation, which requires that when harm is imminent and severe, Engineer A must immediately notify Engineer B and, if Engineer B fails to act, cooperate with proper authorities without delay, collapsing the sequential model. The Peer Review Safety Code Violation Sequential Escalation Obligation provides the baseline pathway when risk is uncertain or non-imminent.

Rebuttals

Uncertainty is generated by the epistemic gap between 'may be in violation' and confirmed violation: if the standard for triggering escalation is subjective good-faith belief, Engineer A's documentation of the severity assessment becomes critical to demonstrating that the chosen pathway was calibrated to the actual risk level. The sequential escalation warrant loses its justificatory force when Engineer B is uncooperative, when the risk is more imminent than initially assessed, or when the time required for collegial notification exceeds the time available before harm materializes.

Grounds

Engineer A has discovered that Engineer B's work may be in violation of state and local safety code requirements. The violation is characterized as potential rather than confirmed. Engineer A must now determine the severity and imminence of the risk, document that assessment, and select the appropriate escalation pathway. The 'may be in violation' standard creates epistemic uncertainty about whether the threshold for mandatory external reporting has been met.

Peer Review Judgment and Discretion Contextual Safety Assessment Obligation Imminent Harm Threshold for Mandatory Peer-Review Safety Escalation Invoked by Engineer A

If Engineer B acknowledges the violations and commits to corrective action, should Engineer A treat that private resolution as fully discharging the reporting obligation, continue to monitor and verify corrective action before concluding no further steps are required, or independently notify proper authorities regardless of Engineer B's corrective commitment given the public's prior exposure to risk?

Options considered:
O1 Accept Engineer B's corrective commitment as a good-faith first step, but establish a documented framework specifying what corrective action is expected, by when, and what Engineer A will do if that action is not taken, then independently verify that the risk has been fully remediated before concluding no further action is required, and escalate to proper authorities if Engineer B's response is inadequate, delayed, or the public's prior exposure to risk warrants regulatory notification. Board's choice
O2 Accept Engineer B's acknowledgment and corrective commitment as fully discharging Engineer A's escalation obligation under the peer review program's confidentiality framework, on the grounds that the collegial resolution pathway achieved its intended purpose, that further external reporting would undermine the peer review program's effectiveness as a voluntary improvement mechanism, and that Engineer B's professional obligations now govern the remediation process.
O3 Independently notify the appropriate governmental authorities of the discovered safety code violations notwithstanding Engineer B's corrective commitment, on the grounds that the public may already have been exposed to risk from non-compliant designs, that regulators need the information to independently assess whether interim protective measures are required, and that Engineer A's duty runs to the public rather than to securing private promises of future compliance.
Argument structure:
Warrants

Three competing obligations are in tension: (1) the Peer Review Program Collegial Improvement Participation Obligation, which supports treating a successful collegial resolution as the intended outcome of the peer review process and honoring the confidentiality framework that made that resolution possible; (2) the Engineering Self-Policing Obligation, which establishes that Engineer A bears a foundational duty to cooperate with proper authorities in furnishing information about safety code violations: a duty that runs to the public, not merely to securing Engineer B's private promise of future compliance; and (3) the Peer Review Confidentiality Non-Override principle, which establishes that the confidentiality agreement cannot override the paramount duty to report once the structured escalation pathway with Engineer B is exhausted without full resolution of the public's exposure to risk.

Rebuttals

Uncertainty arises because the rebuttal condition, whether the public was already exposed to harm from non-compliant designs before corrective action was committed, is factually unresolved. If Engineer B's corrective commitment is credible, specific, timely, and the non-compliant designs have not yet been implemented in structures accessible to the public, the collegial resolution may adequately protect public safety without requiring independent regulatory notification. If the designs are already in use or under construction, the regulatory authorities may need to be informed so they can independently assess whether interim protective measures are required.

Grounds

Engineer A has notified Engineer B of the discovered safety code violations. Engineer B has acknowledged the problem and committed to corrective action. However, non-compliant designs may already have been implemented in structures accessible to the public, submitted for permit approval, or otherwise placed into use, meaning the public may already have been exposed to risk prior to Engineer B's corrective commitment. The peer review program's confidentiality agreement lacks an explicit safety-disclosure carve-out.

Peer Review Safety Violation Pre-Reporting Advisory Warning Obligation Engineer A To Engineer B Peer Review Program Collegial Improvement Participation Obligation Engineer A Engineer B Program

When Engineer A discovers that Engineer B's work may violate state and local safety codes during a confidential peer review, should Engineer A treat the confidentiality agreement as binding and remain silent, notify Engineer B privately as a first step before any external disclosure, or report directly to the proper authorities without waiting for Engineer B's response?

Options considered:
O1 Immediately discuss the discovered violations with Engineer B to seek clarification and allow for early private resolution, while documenting findings and establishing a clear timeline for corrective action, escalating to proper authorities if Engineer B fails to respond credibly or take prompt corrective steps. Board's choice
O2 Treat the signed confidentiality agreement as binding and refrain from disclosing the discovered violations to Engineer B or to authorities, on the grounds that the agreement was voluntarily accepted and the violation is characterized only as potential rather than confirmed.
O3 Bypass the collegial notification step and report the discovered safety code violations directly to the relevant regulatory authorities without first notifying Engineer B, on the grounds that the public safety duty is paramount and any delay, including the time required for collegial discussion, risks ongoing public exposure to harm.
Argument structure:
Warrants

Two competing obligations govern: (1) the Peer Review Confidentiality Agreement Obligation, which binds Engineer A to non-disclosure of information obtained during the review, grounded in Code Section III.4 and the voluntary contractual commitment; and (2) the Peer Review Confidentiality Non-Override of Safety Code Violation Reporting Obligation, which holds that confidentiality cannot suppress disclosure of active public safety violations, grounded in the Public Welfare Paramount principle and the Ethics Code Individual-Person Applicability Non-Waivability principle (BER Case 76-4). A third warrant, the Pre-Reporting Advisory Warning Obligation, supports notifying Engineer B first as a collegial intermediate step before external escalation.

Rebuttals

Uncertainty arises from three sources: (1) the scope ambiguity of the confidentiality agreement: if it was never intended to cover safety-code-violating conduct, the conflict may dissolve; (2) the epistemic gap between 'may be in violation' and a confirmed violation, which affects whether the escalation threshold has been crossed; and (3) the severity and imminence of the risk, which determines whether the sequential collegial-first model applies or whether immediate regulatory reporting is required. If the violation is minor or speculative, the confidentiality warrant retains more force; if harm is imminent and concrete, the confidentiality obligation loses all ethical force with respect to that finding.

Grounds

Engineer A accepted a peer reviewer role and signed a confidentiality agreement as a precondition. During the technical documentation review, Engineer A discovered that Engineer B's work may be in violation of state and local safety codes, creating a potential risk to public health, safety, and welfare. The confidentiality agreement contains no explicit carve-out permitting disclosure of safety violations. An ethical dilemma is instantiated between the binding confidentiality commitment and the paramount duty to protect the public.

Peer Review Confidentiality Non-Override of Safety Code Violation Reporting Obligation Peer Review Confidentiality Agreement Obligation Binding Engineer A

After notifying Engineer B of the discovered safety code violations, should Engineer A treat the collegial discussion as fulfilling the reporting obligation and await Engineer B's response indefinitely, establish a documented corrective-action deadline and escalate to authorities if that deadline is not met, or report to proper authorities concurrently with or immediately following the notification to Engineer B regardless of Engineer B's response?

Options considered:
O1 At the time of notifying Engineer B, establish a documented corrective-action framework specifying what remediation is expected, by what deadline, and what escalation steps Engineer A will take if Engineer B fails to act, then follow through with regulatory reporting if Engineer B does not take prompt and verifiable corrective action within that timeframe. Board's choice
O2 Treat the collegial notification as fulfilling the immediate reporting obligation and allow Engineer B a reasonable, open-ended period to assess and correct the violations before taking any further action, on the grounds that the peer review program's collegial improvement purpose is best served by giving Engineer B a genuine opportunity to self-correct without the pressure of a concurrent regulatory referral.
O3 Notify Engineer B of the violations and simultaneously, or immediately thereafter, report the findings to the proper regulatory authorities, on the grounds that the public may already be exposed to risk from implemented non-compliant designs and that Engineer A's duty runs to the public rather than to securing Engineer B's private promise of future compliance.
Argument structure:
Warrants

Three competing obligations govern: (1) the Peer Review Program Collegial Improvement Participation Obligation, which supports treating the notification of Engineer B as the primary and potentially sufficient remediation mechanism, preserving the program's voluntary improvement purpose; (2) the Prohibition on Aiding or Abetting Unlawful Engineering Practice (II.1.e), which holds that Engineer A's continued silence after notification, if Engineer B fails to act, crosses from collegial patience into complicity with ongoing unlawful practice; and (3) the Public Safety Paramount Over Confidentiality Constraint, which establishes that Engineer A's duty runs to the public, not merely to securing Engineer B's private promise of future compliance, and that past public exposure to risk may independently require regulatory notification.

Rebuttals

Uncertainty is created by three unresolved factual conditions: (1) whether Engineer B's response demonstrates good faith and credible corrective intent, which would support continued reliance on the collegial pathway; (2) whether the non-compliant designs have already been implemented in structures accessible to the public, which would trigger an independent regulatory notification obligation regardless of Engineer B's prospective commitment; and (3) the temporal ambiguity of when the collegial discussion phase ends and the escalation obligation begins: if Engineer B commits to correction with a specific, verifiable timeline, continued silence may be appropriate; if Engineer B disputes the findings without credible technical basis or delays without explanation, silence becomes complicity.

Grounds

Engineer B has been notified of the discovered safety code violations. A corrective action deadline has been triggered. The public may already have been exposed to risk from non-compliant designs that are in use, under construction, or submitted for permit approval. Engineer A must now determine whether the collegial discussion step discharges the reporting obligation or whether an independent duty to notify proper authorities persists regardless of Engineer B's response.

Peer Review Safety Violation Pre-Reporting Advisory Warning Obligation Peer Review Safety Code Violation Escalation Obligation Engineer A Engineer B Safety Codes

Upon discovering potential safety code violations during the peer review, should Engineer A proceed directly to notifying Engineer B under the standard sequential escalation model without a formal documented risk assessment, conduct and document a severity-and-imminence assessment first to determine which escalation pathway applies, or apply a uniform immediate-reporting standard to all discovered violations regardless of assessed severity?

Options considered:
O1 Before taking any escalation action, conduct and document a formal severity-and-imminence assessment identifying the specific code discrepancies, the design elements involved, the applicable safety code provisions, and the potential harm pathway, then select the escalation pathway (sequential collegial notification or immediate regulatory reporting) calibrated to the assessed level of risk. Board's choice
O2 Proceed directly to notifying Engineer B under the standard sequential escalation model without conducting a separate documented risk assessment, on the grounds that the 'may be in violation' standard uniformly triggers the collegial-first pathway and that a formal assessment introduces delay that is itself potentially harmful when a violation has already been identified.
O3 Report all discovered potential safety code violations directly to proper authorities without a severity-and-imminence assessment, on the grounds that any violation of state and local safety codes constitutes a sufficient public safety risk to trigger the paramount reporting duty, and that calibrating the response to assessed severity introduces subjective judgment that could be used to rationalize inaction.
Argument structure:
Warrants

Two competing frameworks govern: (1) the Good Faith Safety Concern Threshold, which holds that the public safety duty is triggered by a professionally grounded belief of risk, not certainty of harm, and that the 'may be in violation' standard imposes essentially the same escalation obligations as a confirmed violation, supporting the sequential model as the default; and (2) the Imminent Harm Threshold for Mandatory Peer-Review Safety Escalation, which holds that when harm is imminent and severe, the delay inherent in the collegial notification step is itself an ethical violation, requiring Engineer A to bypass the sequential model and report directly to authorities. The Graduated Escalation Obligation synthesizes these by making the permissible delay before bypassing the collegial step a function of assessed severity and imminence.

Rebuttals

Uncertainty is created by the epistemic gap between 'may be in violation' and confirmed violation: if the standard for triggering escalation is subjective good-faith belief, Engineer A's documentation of the assessment becomes the primary evidence that the chosen pathway was calibrated to the actual risk level. The rebuttal condition for the sequential model is that it loses justificatory force when the time required for collegial notification exceeds the time available before harm materializes. Conversely, the rebuttal condition for immediate bypass is that it applies only when harm is genuinely imminent, applying it uniformly to all potential violations would undermine the peer review program's collegial improvement purpose without corresponding safety benefit.

Grounds

Engineer A has completed a technical documentation review and discovered work that may be in violation of state and local safety codes. The severity and imminence of the public safety risk remain unconfirmed at the moment of discovery. The Code's escalation obligations are calibrated to the level of risk: the sequential collegial-first model applies when risk is uncertain or non-imminent, while an immediate bypass to regulatory authorities is required when harm is imminent and severe. Engineer A must determine which pathway applies before acting.

Peer Review Judgment and Discretion Contextual Safety Assessment Obligation Graduated Escalation Obligation. Peer Review Safety Discovery

Should Engineer A first discuss the discovered safety code violations directly with Engineer B before reporting to authorities, report immediately to the proper authorities without collegial notification, or pursue both simultaneously?

Options considered:
O1 Immediately discuss the discovered violations with Engineer B in a documented collegial meeting, establish a clear corrective action timeline, and commit to reporting to the proper authorities if Engineer B does not take prompt and verifiable corrective action within that timeframe. Board's choice
O2 Bypass the collegial notification step and report the discovered safety code violations immediately to the proper regulatory authorities, treating the 'may be in violation' finding as sufficient to trigger the public safety reporting duty regardless of whether Engineer B has been consulted.
O3 Simultaneously notify Engineer B of the discovered violations and report to the proper authorities, reasoning that the public safety duty and the collegial improvement purpose are not mutually exclusive and that concurrent notification eliminates the risk of harmful delay while still giving Engineer B the opportunity to respond.
Argument structure:
Warrants

The Peer Review Program Collegial Improvement Participation Obligation supports notifying Engineer B first, giving Engineer B an opportunity to self-correct before external reporting and preserving the program's voluntary improvement function. The Engineering Self-Policing Obligation and the Public Welfare Paramount principle support escalating to authorities without delay to ensure the public is protected. The Confidentiality-Bounded Public Safety Escalation Sequence supports a sequential model, notify Engineer B first, then escalate, as the ethically calibrated pathway when risk is uncertain or non-imminent.

Rebuttals

Uncertainty arises from the temporal ambiguity of when the collegial discussion phase ends and the escalation obligation begins. If Engineer B demonstrates good-faith corrective intent, continued silence during the collegial phase may be appropriate. If Engineer B is unresponsive or the risk is more imminent than initially assessed, the sequential model collapses and immediate regulatory reporting becomes obligatory. The 'may be in violation' standard does not eliminate the escalation duty but calibrates its pace.

Grounds

Engineer A has discovered work by Engineer B that may be in violation of state and local safety codes during a peer review. A confidentiality agreement is in force. The risk is characterized as potential rather than confirmed imminent. Engineer B has not yet been notified. The peer review program's collegial improvement purpose contemplates private resolution as a first step.

Peer Review Program Collegial Improvement Participation Obligation Engineer A Engineer B Program Peer Review Confidentiality Agreement Obligation Binding Engineer A
Event Timeline (13)
13 sequenced 6 actions 7 events
Case timeline
An organized peer review program is instituted, creating a formal structure for engineers to evaluate each other's work. This exogenous institutional arrangement sets the conditions under which Engineer A is selected and bound by its rules.
Engineer A voluntarily agrees to serve as a peer reviewer within an organized peer review program, taking on the associated professional responsibilities and obligations of that role.
Fulfills (3)
  • Support for professional development and improvement of engineering practice
  • Participation in organized professional self-regulation
  • Collegial responsibility to assist fellow engineers in improving practice
Engineer A signs a formal confidentiality agreement committing to non-disclosure of confidential information about firms encountered during the peer review process, as a precondition of participation.
Fulfills (4)
  • Honoring program requirements for participation
  • Supporting the confidentiality foundation that makes peer review programs effective
  • Respecting the trust relationship between peer reviewer and reviewed firm
  • NSPE Code Section III.4, commitment to non-disclosure of confidential business and technical information
Upon signing, the confidentiality agreement becomes legally and professionally binding on Engineer A, creating a formal constraint on disclosure of information obtained during the review. This is an automatic legal outcome triggered by the act of signing.
Engineer A actively reviews the technical documentation associated with Engineer B's firm's recent design projects as part of the formal peer review visit, exercising professional judgment to evaluate compliance and quality of work.
Fulfills (4)
  • Fulfillment of peer reviewer role and program obligations
  • Diligent and thorough professional evaluation
  • Service to the profession through quality assurance
  • Competent exercise of engineering judgment
During examination of Engineer B's technical documentation, Engineer A discovers evidence of potential violations of state and local safety codes that could endanger public health and safety. This is a critical outcome event that fundamentally changes the ethical landscape of the narrative.
The discovery of safety violations creates an active, irresolvable tension between Engineer A's contractual confidentiality obligation and the professional duty to protect public health and safety. This is an automatic trigger event arising from the co-existence of two conflicting binding obligations.
Following discovery of potential safety code violations, Engineer A exercises professional judgment to determine whether the risk constitutes an imminent threat to public health and safety requiring urgent action, or a serious but non-imminent concern permitting a deliberative resolution process.
Fulfills (3)
  • Exercise of appropriate engineering judgment and discretion
  • Paramount duty to protect public health and safety (NSPE Code Section II.1.e)
  • Responsible professional decision-making under conditions of uncertainty
Engineer A expeditiously initiates a direct discussion with Engineer B about the discovered potential safety code violations, seeking clarification and early resolution before considering any escalation to external authorities.
At stake (1)
  • Partial tension with confidentiality agreement, though disclosure is to Engineer B (the reviewed party) rather than external authorities, the confrontation signals potential future breach
Fulfills (4)
  • Paramount duty to protect public health and safety (NSPE Code Section II.1.e)
  • Collegial professional responsibility to engage Engineer B directly before external escalation
  • Proportionate response that preserves confidentiality to the extent possible
  • Honest and direct communication consistent with professional integrity
As an outcome of Engineer A's notification action, Engineer B becomes aware of the identified safety code violations in their firm's design work. This event shifts moral and corrective responsibility to Engineer B and starts a clock on remediation.
Upon notification of violations, an implicit or explicit deadline for Engineer B to take corrective action is automatically activated. If Engineer B fails to act within a reasonable timeframe, Engineer A's conditional obligation to escalate to proper authorities becomes unconditional.
If Engineer B fails to take appropriate corrective action following notification, Engineer A decides to cooperate with proper authorities by furnishing information and assistance as required, overriding the confidentiality agreement in fulfillment of the paramount obligation to protect public health and safety.
Fulfills (4)
  • Paramount duty to protect public health and safety (NSPE Code Section II.1.e)
  • Obligation to cooperate with proper authorities regarding known or alleged code violations
  • Ultimate professional responsibility as a licensed engineer to the public
  • Fulfillment of the escalation pathway prescribed by BER guidance
Violates (2)
  • Confidentiality agreement, formal commitment to non-disclosure is breached
  • NSPE Code Section III.4, obligation not to disclose confidential business affairs or technical processes without consent
When Engineer A escalates to proper authorities, the confidentiality agreement is effectively overridden by the paramount professional obligation to protect public health and safety. This is an automatic legal and ethical outcome: disclosure to authorities supersedes the contractual non-disclosure constraint.
Narrative (2 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, a licensed professional engineer participating in an organized peer review program designed to help engineers improve their professional practice. Before beginning your role, you signed a confidentiality agreement committing you not to disclose confidential information about peer-reviewed firms. During a review visit to Engineer B's firm, you examined technical documentation from a series of recent design projects and found that Engineer B's work may violate state and local safety code requirements in ways that could endanger public health, safety, and welfare. The confidentiality agreement you signed now stands in direct tension with your potential obligation to report what you have found. The decisions ahead will determine how you navigate that conflict.

Main characters (2)

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: Peer Review Safety Violation Discovering Engineer

Guided by: Ethics Code Individual-Person Applicability Non-Waivability Through Business Form Affirmed by BER, Public Welfare Paramount, Peer Review Confidentiality Agreement Obligation

Tension between Peer Review Safety Violation Pre-Reporting Advisory Warning Obligation Engineer A To Engineer B and Peer Review Program Collegial Improvement Participation Obligation Engineer A Engineer B Program

Tension between Peer Review Safety Violation Pre-Reporting Advisory Warning Obligation and Peer Review Safety Code Violation Escalation Obligation Engineer A Engineer B Safety Codes

Engineer A is obligated to warn Engineer B before escalating to regulatory authorities, giving Engineer B an opportunity to self-correct — a collegial, process-respecting duty that preserves professional relationships and program trust. However, when harm is imminent, a separate and competing obligation requires Engineer A to notify authorities immediately, bypassing the advisory warning step entirely. These obligations are structurally incompatible in time-critical scenarios: the pre-reporting warning introduces delay that the imminent harm obligation explicitly prohibits. Engineer A must judge whether the situation is sufficiently urgent to skip the warning, but that judgment itself carries moral risk in both directions.

Tension between Engineer A Peer Review Imminent Harm Immediate Notification and Graduated Escalation Obligation — Peer Review Safety Discovery

Engineer A signed a binding confidentiality agreement as a condition of participating in the peer review program, creating a legally and ethically enforceable duty of non-disclosure. However, the discovery of safety code violations triggers a countervailing constraint that public safety concerns override confidentiality commitments. These two constraints pull in opposite directions simultaneously: honoring the confidentiality agreement preserves program integrity and Engineer B's trust, but suppressing safety violations may expose the public to harm. The engineer cannot fully satisfy both — disclosure violates the agreement, while silence violates the safety override principle.

Tension between Peer Review Judgment and Discretion Contextual Safety Assessment Obligation and Imminent Harm Threshold for Mandatory Peer-Review Safety Escalation Invoked by Engineer A

Tension between Peer Review Confidentiality Non-Override of Safety Code Violation Reporting Obligation and Peer Review Confidentiality Agreement Obligation Binding Engineer A

Tension between Engineer A Peer Review Safety Code Violation Sequential Escalation and Peer Review Confidentiality Non-Override of Safety Code Violation Reporting Obligation Engineer A Confidentiality Agreement Limit

The peer review program is premised on collegial improvement, and Engineer A's access to Engineer B's practice was granted under that cooperative premise. Using that access as a basis for regulatory reporting risks exploiting the trust relationship that made the visit possible — a form of institutional bad faith that could undermine the entire peer review system. Yet the constraint that confidentiality cannot bar safety-critical regulatory disclosure demands that Engineer A act on what was discovered, regardless of how access was obtained. The tension is systemic: acting on the safety constraint instrumentalizes the collegial relationship, while honoring the non-exploitation constraint may allow safety violations to persist.

Tension between Peer Review Program Collegial Improvement Participation Obligation Engineer A Engineer B Program and Peer Review Confidentiality Agreement Obligation Binding Engineer A

Engineer B Roles in this case: Peer-Reviewed Engineer Subject to Safety Code Findings

Tension between Peer Review Safety Violation Pre-Reporting Advisory Warning Obligation Engineer A To Engineer B and Peer Review Program Collegial Improvement Participation Obligation Engineer A Engineer B Program

Tension between Peer Review Safety Violation Pre-Reporting Advisory Warning Obligation and Peer Review Safety Code Violation Escalation Obligation Engineer A Engineer B Safety Codes

Engineer A is obligated to warn Engineer B before escalating to regulatory authorities, giving Engineer B an opportunity to self-correct — a collegial, process-respecting duty that preserves professional relationships and program trust. However, when harm is imminent, a separate and competing obligation requires Engineer A to notify authorities immediately, bypassing the advisory warning step entirely. These obligations are structurally incompatible in time-critical scenarios: the pre-reporting warning introduces delay that the imminent harm obligation explicitly prohibits. Engineer A must judge whether the situation is sufficiently urgent to skip the warning, but that judgment itself carries moral risk in both directions.

Engineer A signed a binding confidentiality agreement as a condition of participating in the peer review program, creating a legally and ethically enforceable duty of non-disclosure. However, the discovery of safety code violations triggers a countervailing constraint that public safety concerns override confidentiality commitments. These two constraints pull in opposite directions simultaneously: honoring the confidentiality agreement preserves program integrity and Engineer B's trust, but suppressing safety violations may expose the public to harm. The engineer cannot fully satisfy both — disclosure violates the agreement, while silence violates the safety override principle.

The peer review program is premised on collegial improvement, and Engineer A's access to Engineer B's practice was granted under that cooperative premise. Using that access as a basis for regulatory reporting risks exploiting the trust relationship that made the visit possible — a form of institutional bad faith that could undermine the entire peer review system. Yet the constraint that confidentiality cannot bar safety-critical regulatory disclosure demands that Engineer A act on what was discovered, regardless of how access was obtained. The tension is systemic: acting on the safety constraint instrumentalizes the collegial relationship, while honoring the non-exploitation constraint may allow safety violations to persist.

Tension between Peer Review Program Collegial Improvement Participation Obligation Engineer A Engineer B Program and Peer Review Confidentiality Agreement Obligation Binding Engineer A

These tensions did not map cleanly to a single character.

Tension between Peer Review Judgment and Discretion Contextual Safety Assessment Obligation and Graduated Escalation Obligation — Peer Review Safety Discovery

Opening States (10)
Graduated Escalation Obligation - Peer Review Safety Discovery Peer Review Confidentiality vs. Public Safety Override Threshold - Engineer A Cooperative Disclosure Pathway - Collegial Discussion with Engineer B Peer Review Program Confidentiality Foundation Active Engineer B Safety Code Violation Discovery During Peer Review Engineer A Competing Duties - Confidentiality vs. Safety Reporting Engineer A Peer Review Confidentiality Agreement Bound Public Safety at Risk from Engineer B Design Work Peer Review Confidentiality vs. Public Safety Override Threshold State Engineering Peer Review Program Confidentiality Foundation
Summary
  • Peer review confidentiality agreements cannot serve as an absolute shield against the obligation to report genuine safety violations that endanger public health, welfare, and safety.
  • Engineers operating within structured peer review programs face a layered duty: first to advise the reviewed engineer of deficiencies, but ultimately to escalate to authorities when imminent harm thresholds are crossed regardless of collegial protocols.
  • The stalemate transformation type signals that no clean hierarchical resolution exists between confidentiality and safety obligations, requiring engineers to exercise contextual professional judgment rather than apply a mechanical rule.

© Licensed under the GNU GPL v3 | Report Issue