Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Peer Review - Confidentiality Agreements
Step 4 of 5

151

Entities

2

Provisions

1

Precedents

13

Questions

14

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's obligation moves through a two-step transfer: first, the duty to address the violation rests with Engineer A within the confidential peer-review relationship (attempt collegial resolution with Engineer B); if that fails, the obligation transfers outward to the proper regulatory/enforcement authorities, who then bear responsibility for formal action. This is a conditional, one-directional transfer rather than a repeating cycle (oscillation) or an unresolved dual-obligation deadlock (stalemate).
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

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

II.1.e board + analysis Engineers shall not aid or abet the unlawful practice of engineering by a person or firm.
How this applies in the case (showing 3 of 17)
Obligation
Engineer A Public Safety Duty
This provision relates to preventing unlawful engineering practice which ties to public safety concerns discovered during review
State
Discovered Possible Code Violation
This provision addresses engineers aiding unlawful practice which relates to discovering a possible code violation
Constraint
Engineer B Safety Code Compliance
Producing design work that violates safety codes could constitute aiding unlawful engineering practice
Obligation (3)
  • Engineer A Public Safety Duty
    This provision relates to preventing unlawful engineering practice which ties to public safety concerns discovered during review
  • Engineer A Authority Cooperation Duty
    Cooperating with authorities on Code violations helps prevent aiding unlawful practice by another engineer
  • Engineer A Escalation Warning Duty
    Warning Engineer B and escalating if unresolved helps ensure Engineer A does not aid or abet unlawful practice
State (3)
  • Discovered Possible Code Violation
    This provision addresses engineers aiding unlawful practice which relates to discovering a possible code violation
  • Potential Public Endangerment From Design Work
    Aiding unlawful engineering practice can directly result in public endangerment from faulty design work
  • Code Applicability Despite Business Form
    The prohibition on aiding unlawful practice applies regardless of the business form under which engineering is conducted
Constraint (1)
  • Engineer B Safety Code Compliance
    Producing design work that violates safety codes could constitute aiding unlawful engineering practice
Principle (3)
  • Public Welfare in Peer Review
    Aiding unlawful or code violating engineering practice endangers public welfare which this provision aims to prevent
  • Public Safety Paramount in Peer Review
    Not aiding unlawful practice supports the duty to act when public safety is at imminent risk
  • Code Conformance Regardless of Business Form
    The obligation not to aid unlawful practice applies to the engineer as a person regardless of business form
Role (2)
  • Engineer A Peer Reviewer
    Engineer A must not aid or abet Engineer B's potentially unlawful practice by staying silent if violations are confirmed
  • Engineer B Design Engineer
    Engineer B's design work may constitute unlawful practice of engineering if it violates safety codes
Capability (5)
  • Engineer A Violation Recognition
    Recognizing unlawful or unsafe engineering practice relates to not aiding unlawful engineering conduct
  • Engineer A Safety Code Assessment
    Assessing safety code violations connects to the duty not to aid unlawful engineering practice
  • Engineer A Imminent Risk Assessment
    Determining risk of harm relates to the obligation to prevent unlawful or unsafe engineering practice
  • Engineer A Response Threshold Judgment
    Judging when to act on violations ties to preventing aiding of unlawful practice
  • Engineer A Peer Resolution Engagement
    Engaging Engineer B to resolve violations reflects fulfilling duty to not aid unlawful practice
III.4 board + analysis Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve.
How this applies in the case (showing 3 of 19)
Obligation
Engineer A Confidentiality Duty
This provision directly specifies the duty not to disclose confidential business or technical information without consent
Action
Confidentiality Agreement Signing
This provision directly governs the obligation not to disclose confidential information covered by such agreements
State
Peer Review Confidentiality Bound
This provision directly governs the confidentiality obligations engineers have during peer review
Obligation (1)
  • Engineer A Confidentiality Duty
    This provision directly specifies the duty not to disclose confidential business or technical information without consent
Action (3)
  • Confidentiality Agreement Signing
    This provision directly governs the obligation not to disclose confidential information covered by such agreements
  • Peer Review Conduct
    Peer reviewers may access confidential technical processes so this provision restricts disclosure during review
  • Collegial Issue Discussion
    Discussing issues with colleagues could risk disclosing confidential client information without consent
State (2)
  • Peer Review Confidentiality Bound
    This provision directly governs the confidentiality obligations engineers have during peer review
  • Confidentiality Versus Cooperation Dilemma
    This provision creates the tension between maintaining confidentiality and cooperating on ethical concerns
Constraint (1)
  • Engineer A Peer Review Confidentiality
    This provision directly establishes the duty not to disclose confidential peer review information without consent
Principle (3)
  • Confidentiality in Peer Review
    This provision directly addresses the duty not to disclose confidential information from peer review
  • Public Safety Paramount in Peer Review
    The confidentiality duty is overridden when disclosure is necessary to prevent imminent risk to public safety
  • Code Conformance Regardless of Business Form
    The confidentiality obligation applies to the engineer personally irrespective of the business arrangement
Role (2)
  • Engineer A Peer Reviewer
    Engineer A signed a confidentiality agreement restricting disclosure of information learned during peer review
  • Engineer B Design Engineer
    Engineer B is the client whose business affairs and technical processes are protected as confidential information
Event (2)
  • Safety Violation Discovery
    Confidential information from peer review may be involved when safety violations are discovered
  • Corrective Action Failure
    Disclosure obligations may conflict with confidentiality when corrective action fails
Resource (2)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code of Ethics addressing confidentiality of client information
  • BER Case 76-4
    This prior case directly addresses confidentiality obligations when an engineer learns information damaging to a client
Capability (3)
  • Engineer A Confidentiality Judgment
    Directly involves determining what confidential information can be disclosed without consent
  • Engineer A Peer Review Assessment
    Reviewing confidential technical documentation implicates the duty to protect client confidentiality
  • Engineer A Peer Resolution Engagement
    Discussing violations directly with Engineer B avoids improper disclosure of confidential information
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's knowledge of information damaging to a client's interest that involves public health and safety creates tension between confidentiality obligations and the duty to protect the public.

Citation Context:

The Board cited this case as a prior instance involving an engineer gaining knowledge of information damaging to a client's interest that involved public health and safety, similar to the present dilemma between confidentiality and public safety obligations.

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 70% Facts Similarity 61% Discussion Similarity 77% Provision Overlap 11% Outcome Alignment 100% Tag Overlap 12% Principle Overlap 82%
Shared provisions: III.4 Same outcome unclear View Synthesis
Component Similarity 51% Facts Similarity 25% Discussion Similarity 34% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 73%
Shared provisions: III.4 Same outcome unclear View Synthesis
Component Similarity 60% Facts Similarity 40% Discussion Similarity 47% Provision Overlap 33% Outcome Alignment 50% Tag Overlap 14% Principle Overlap 71%
Shared provisions: III.4 View Synthesis
Component Similarity 61% Facts Similarity 57% Discussion Similarity 46% Provision Overlap 20% Outcome Alignment 100% Tag Overlap 25%
Shared provisions: III.4 Same outcome unclear View Synthesis
Component Similarity 55% Facts Similarity 42% Discussion Similarity 37% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 69%
Same outcome unclear View Synthesis
Component Similarity 60% Facts Similarity 52% Discussion Similarity 69% Outcome Alignment 100% Tag Overlap 17% Principle Overlap 59%
Same outcome unclear View Synthesis
Component Similarity 59% Facts Similarity 42% Discussion Similarity 37% Outcome Alignment 100% Principle Overlap 78%
Same outcome unclear View Synthesis
Component Similarity 58% Facts Similarity 50% Discussion Similarity 24% Outcome Alignment 100% Principle Overlap 79%
Same outcome unclear View Synthesis
Component Similarity 52% Facts Similarity 36% Discussion Similarity 35% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 78%
Same outcome unclear View Synthesis
Component Similarity 60% Facts Similarity 44% Discussion Similarity 37% Outcome Alignment 100% Principle Overlap 73%
Same outcome unclear 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. If Engineer A and Engineer B are unable to resolve the issue, Engineer A must inform Engineer B that as a professional engineer, his only alternative is to notify and inform the proper authorities as indicated above.
Resolved by: The board sequences the obligations rather than choosing one absolutely, requiring collegial resolution first and only elevating public safety duty above confidentiality if that resolution fails. (confidence 0.85)
II.1.e. III.4. 3 principles 3 facts Conditions Narrative
Implicit (4)

Does the confidentiality agreement Engineer A signed upon becoming a peer reviewer create a binding contractual obligation that could legally conflict with the ethical duty to report safety violations to proper authorities?

AnalyticalThe Board's conclusion implicitly resolves the confidentiality-versus-safety tension in favor of public protection, but it does not explicitly address why the confidentiality agreement cannot function as a valid ethical shield. The NSPE Code's confidentiality provision (III.4) is itself conditioned on the absence of a public health and safety concern; once such a concern is identified, the underlying ethical duty supersedes any contractual promise Engineer A made to the peer review program. This means the confidentiality agreement was never actually in conflict with the Code—rather, it was always subordinate to it, since a private contractual agreement cannot ethically override a professional's paramount duty to protect the public.
Resolved by: The board treats the conflict as illusory rather than genuine, holding that confidentiality was never coequal with safety since the Code provision itself is conditioned on there being no public health and safety issue. (confidence 0.75)
III.4. 3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101, the confidentiality agreement Engineer A signed cannot be read as superseding the NSPE Code's mandatory public safety provisions. Even though the agreement creates a contractual expectation of confidentiality between Engineer A and the peer review program, professional obligations to protect public health and safety under the Code take precedence over private contractual confidentiality terms. Any conflict must be resolved in favor of disclosure to proper authorities once collegial resolution fails, since a private agreement cannot ethically bind an engineer to conceal information that endangers the public.
Resolved by: The board explicitly ranks the Code's public safety mandate above the private contractual confidentiality term, resolving any conflict in favor of disclosure once collegial means are exhausted. (confidence 0.80)
III.4. 2 principles 3 facts Conditions Narrative

What specific criteria should Engineer A use to determine whether Engineer B's code violations rise to the level of endangering public health, safety, and welfare versus being minor technical noncompliance?

AnalyticalThe Board's two-step process (discuss with Engineer B, then escalate if unresolved) presumes that Engineer A can reliably distinguish violations that merely constitute technical noncompliance from those that genuinely endanger public health, safety, and welfare. The Board does not articulate objective criteria for this threshold judgment, leaving it to Engineer A's professional discretion. This creates a practical risk: an engineer applying too conservative a standard might delay necessary escalation, while one applying too strict a standard might report matters that could have been resolved collegially, undermining the peer review program's rehabilitative purpose.
Resolved by: The board leaves the threshold judgment to professional discretion rather than weighing it directly, implicitly balancing the risk of under-escalation against the risk of damaging the program's collegial function through over-escalation. (confidence 0.70)
2 principles 3 facts Conditions Narrative
AnalyticalRegarding Q102, the Board's framework implies that the determining criterion is not mere technical noncompliance but whether the violation creates a genuine risk to public health, safety, or welfare. Engineer A must exercise professional judgment (Engineer A Safety Code Assessment and Engineer A Risk Assessment capabilities) to distinguish between minor deviations from code language that carry negligible risk and substantive violations that could result in structural, safety, or public harm. Only the latter triggers the escalation duty described in the Board's conclusion.
Resolved by: The board subordinates strict code-conformance language to a risk-based test, so escalation duties are triggered only by genuine danger to the public rather than by technical nonconformity alone. (confidence 0.60)
3 principles 3 facts Conditions Narrative

If Engineer B refuses to correct the violations, what specific steps and to which proper authorities must Engineer A report, and does the peer review program itself bear any institutional responsibility for ensuring such escalation occurs?

AnalyticalThe Board's conclusion places the entire burden of escalation on Engineer A as an individual professional, but does not consider whether the peer review program itself bears institutional responsibility for establishing clear protocols when violations affecting public safety are discovered. Without a program-level escalation mechanism, the ethical burden and potential professional risk (e.g., damaged relationships with peer-reviewed firms, program reputation, or legal exposure under the confidentiality agreement) falls disproportionately on the individual reviewer, even though the program derives its value from firms trusting the review process.
Resolved by: The board's silence on institutional responsibility is read as placing the full weight of escalation and its professional risks on the individual reviewer rather than distributing it to the program. (confidence 0.70)
2 principles 3 facts Conditions Narrative

Does Engineer A's role as a peer reviewer under an organized program alter the scope or nature of ethical obligations compared to an engineer who discovers similar violations in an ordinary client relationship?

AnalyticalRegarding Q104, Engineer A's role as a peer reviewer does not diminish or alter the fundamental ethical obligation to protect public safety; if anything, it heightens Engineer A's responsibility because the peer review relationship grants privileged access to information that an ordinary third party would not have. The organized program context changes the *procedural* path (first attempting resolution through the peer review relationship) but does not change the *substantive* duty, which remains identical to what any engineer discovering such violations in a client relationship would owe under the Code.
Resolved by: The board treats confidentiality as governing only the procedural sequence of action while public safety duty remains substantively undiminished and arguably intensified by privileged access. (confidence 0.75)
III.4. 2 principles 3 facts Conditions Narrative
Principle tension (2)

How should Confidentiality in Peer Review be balanced against Public Safety Paramount in Peer Review when the peer-reviewed firm's violations pose a genuine risk to the public?

AnalyticalThe Board did not resolve the tension between Confidentiality in Peer Review and Public Safety Paramount in Peer Review by declaring one principle categorically superior in all respects; instead it established a sequential procedure in which confidentiality is honored first through direct, private engagement with Engineer B, and only yields to the public safety duty if that collegial process fails to produce correction. This staged resolution allows both principles to operate within their proper domains: confidentiality governs the manner and timing of disclosure, while public safety ultimately governs the substantive outcome.
Resolved by: The board resolved the tension by sequencing rather than ranking the principles, letting confidentiality govern initial process while reserving public safety as the ultimate controlling duty if collegial correction fails. (confidence 0.85)
III.4. 3 principles 3 facts Conditions Narrative

How does the principle of Code Conformance Regardless of Business Form interact with Public Safety Paramount in Peer Review when determining whether Engineer A must escalate concerns beyond Engineer B's firm?

AnalyticalThe principle of Code Conformance Regardless of Business Form reinforces Public Safety Paramount in Peer Review by establishing that the organizational or programmatic context of the peer review relationship does not alter Engineer B's underlying obligation to comply with safety codes, nor does it diminish Engineer A's obligation to act when that compliance fails. This suggests that in the hierarchy of principles governing peer review, structural or contractual arrangements between engineers are subordinate to the substantive ethical duties owed to the public, regardless of the business or programmatic form through which engineering services are delivered or reviewed.
Resolved by: The board treated organizational or contractual arrangements between engineers as subordinate to the substantive safety duties owed to the public, so business form could not dilute either engineer's obligations. (confidence 0.70)
II.1.e. III.4. 3 principles 3 facts Conditions Narrative
Theoretical (3)

From a deontological perspective, did Engineer A fulfill the duty to protect public safety even though it required breaching the confidentiality agreement signed as part of the peer review program?

AnalyticalFrom a deontological perspective (Q301), Engineer A fulfills the categorical duty to protect public safety by escalating the matter to proper authorities after collegial resolution fails, regardless of the confidentiality agreement's terms. The duty to prevent harm to the public is treated as a higher-order, non-negotiable obligation that cannot be waived by private contract, meaning breach of the confidentiality agreement is ethically justified and even required when it conflicts with this duty.
Resolved by: The board subordinates the contractual confidentiality obligation to the categorical, non-waivable duty to prevent public harm, treating the former as breachable when it conflicts with the latter. (confidence 0.80)
III.4. 2 principles 3 facts Conditions Narrative

From a consequentialist standpoint, does the outcome of first attempting collegial resolution with Engineer B before notifying authorities produce better overall results for public welfare than immediate reporting?

AnalyticalFrom a consequentialist standpoint (Q302), attempting collegial resolution first likely produces better overall outcomes than immediate reporting, because it allows for rapid correction of the violation without unnecessary reputational or economic harm to Engineer B, preserves the trust necessary for peer review programs to function, and reserves formal reporting for cases where voluntary correction fails. This sequencing minimizes social costs while still ensuring that public welfare is protected if early resolution does not succeed.
Resolved by: The board weighs the social cost of preserving peer review trust and enabling rapid voluntary correction against the marginal delay in reporting, concluding sequencing minimizes total social costs while preserving safety as a backstop. (confidence 0.70)
III.4. 3 principles 3 facts Conditions Narrative

Did Engineer A act with professional integrity by balancing the confidentiality obligations of the peer review program against the paramount duty to safeguard public health and safety?

Counterfactual (2)

If Engineer B's design work had violated code requirements only in a minor technical sense without endangering public health, safety, or welfare, would the Board still have concluded that Engineer A must escalate the matter to proper authorities if resolution with Engineer B failed?

AnalyticalRegarding Q401, if Engineer B's violations were merely minor technical noncompliance without genuine risk to public health, safety, or welfare, the Board's reasoning suggests escalation to proper authorities would not be ethically required. In such a case, Engineer A's obligations would likely be limited to advising Engineer B to correct the deficiencies within the peer review relationship, since the paramount public safety duty that justifies overriding confidentiality is specifically tied to actual or probable endangerment, not mere procedural nonconformity.
Resolved by: The board reasons that without genuine risk to trigger the override, confidentiality remains intact and governs, so no escalation obligation arises. (confidence 0.65)
III.4. 2 principles 3 facts Conditions Narrative

If Engineer A had not signed a confidentiality agreement upon being selected as a peer reviewer, would the Board's analysis of the confidentiality-versus-cooperation dilemma still require Engineer A to first attempt private resolution with Engineer B before notifying authorities?

AnalyticalRegarding Q402, even absent a signed confidentiality agreement, the Board's analytical structure would likely still require Engineer A to first seek clarification and resolution directly with Engineer B before notifying authorities. This sequencing reflects a general professional norm of engineer-to-engineer collegiality and due process rather than being derived solely from the confidentiality agreement; the agreement affects the tension Engineer A must resolve but does not create the underlying obligation to attempt direct resolution first.
Resolved by: The board treated the duty to attempt direct engineer-to-engineer resolution as prior in sequence to the public safety escalation duty, independent of whether a contractual confidentiality obligation existed. (confidence 0.75)
III.4. 3 principles 3 facts Conditions Narrative
Analytical questions (1)

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

Principle tension (1)

Does Public Welfare in Peer Review conflict with Confidentiality in Peer Review when the peer review program's effectiveness depends on firms trusting that findings will remain private?

AnalyticalThis case demonstrates that contractual or programmatic confidentiality obligations, such as the peer review confidentiality agreement, cannot ethically override the Code's paramount public safety mandate; they can only condition how and when that mandate is fulfilled. Public Welfare in Peer Review functions as a threshold principle that, once triggered by a genuine safety risk, limits the scope of Confidentiality in Peer Review to matters not implicating public health and safety, effectively carving out an exception to the general duty of nondisclosure under III.4.
Resolved by: The board subordinated the contractual confidentiality obligation to the Code's paramount safety mandate, treating public welfare as a threshold condition that carves an exception into the general nondisclosure duty. (confidence 0.85)
III.4. 3 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer A immediately discuss the suspected violations with Engineer B, report the matter directly to authorities, or defer action pending further certainty?

Options considered:
O1 Immediately raise the suspected code violations with Engineer B to seek clarification and early resolution before any further action. Board's choice
O2 Bypass discussion with Engineer B and report the suspected violation directly to the proper regulatory authorities.
O3 Take no action and defer to Engineer B's professional judgment until additional evidence of a violation emerges.
Argument structure (Toulmin):
Grounds

Engineer A discovered facts suggesting Engineer B's design work may violate state and local safety requirements during the course of a peer review.

Warrant

Engineers must hold paramount the safety of the public, but professional collegiality obligates an engineer to first afford a colleague the opportunity to clarify or correct a suspected violation before escalating.

Rebuttal

Would not apply if the risk is imminent and severe, such as an immediate danger to life or property, in which case Engineer A must notify authorities without first attempting discussion with Engineer B.

Engineer A Public Safety Duty

Should Engineer A disclose the safety violation to proper authorities despite the signed confidentiality agreement, or maintain confidentiality and take no further action if Engineer B fails to correct the issue?

Options considered:
O1 Report the uncorrected violation to proper authorities despite the confidentiality agreement, treating public safety as overriding. Board's choice
O2 Honor the signed confidentiality agreement and refrain from disclosing the violation to any outside party.
O3 Request that the peer review program administrators formally release Engineer A from the confidentiality agreement before disclosing to authorities.
Argument structure (Toulmin):
Grounds

Engineer A signed a confidentiality agreement upon selection as a peer reviewer, and Engineer B did not take corrective action after being notified of the violation.

Warrant

The Code's paramount duty to protect public health and safety supersedes private contractual confidentiality obligations, since the Code's confidentiality provision is itself conditioned on the absence of a safety concern.

Rebuttal

Would not apply if the violation did not actually endanger public health, safety, or welfare, in which case the confidentiality agreement would remain fully binding.

Engineer A Authority Cooperation Duty Engineer A Confidentiality Duty

Should Engineer A treat the identified code deviations as a genuine public safety risk warranting escalation, or as minor technical noncompliance resolvable within the peer review relationship?

Options considered:
O1 Treat the violations as posing a genuine risk to public health, safety, or welfare, triggering the duty to escalate if uncorrected. Board's choice
O2 Treat the deviations as minor technical noncompliance requiring only private advisement to Engineer B, without escalation.
O3 Engage an independent third-party technical review to resolve uncertainty about the severity classification before deciding on escalation.
Argument structure (Toulmin):
Grounds

Engineer A's risk assessment and review of Engineer B's design work revealed violations of varying severity, with no numeric or codified ranking of severity provided.

Warrant

Engineers must exercise professional judgment to distinguish substantive safety violations from mere technical noncompliance, since only genuine endangerment triggers the duty that overrides confidentiality and collegial discretion.

Rebuttal

Would not apply if the violation is unambiguously severe, such as an imminent structural or life-safety hazard, which removes any discretion to treat it as minor.

Engineer A Public Safety Duty

If Engineer B refuses to correct the violation after collegial discussion, should Engineer A warn Engineer B and then escalate to proper authorities, or continue attempting informal resolution indefinitely?

Options considered:
O1 Inform Engineer B that reporting to proper authorities is the only remaining alternative, then escalate if correction still does not occur. Board's choice
O2 Keep attempting informal collegial resolution with Engineer B without setting a point at which escalation becomes necessary.
O3 Report the unresolved violation to the peer review program's internal administrators only, without notifying external regulatory authorities.
Argument structure (Toulmin):
Grounds

Engineer B failed to take corrective action despite Engineer A's collegial discussion of the identified safety violation.

Warrant

Engineers with knowledge of Code violations must cooperate with proper authorities in furnishing information or assistance once collegial resolution has failed and correction has not occurred.

Rebuttal

Would not apply if Engineer B corrects the violation upon receiving the warning, in which case the duty to escalate would not be activated.

Engineer A Escalation Warning Duty

Should Engineer A attempt collegial resolution with Engineer B before notifying authorities, or report the violation to authorities immediately upon discovery?

Options considered:
O1 Engage Engineer B directly in an effort to resolve the violation before considering any notification of outside authorities. Board's choice
O2 Notify proper authorities of the suspected violation immediately upon discovery, without first engaging Engineer B.
O3 Inform Engineer B of the violation while simultaneously preparing documentation for authorities, pending the outcome of discussion.
Argument structure (Toulmin):
Grounds

Engineer A had direct professional access to Engineer B through the peer review relationship, and no facts at the time of discovery indicated an uncontrollable or immediate hazard.

Warrant

Sequencing correction attempts before formal reporting preserves professional trust and the functioning of the peer review program while still protecting the public if voluntary correction fails.

Rebuttal

Would not apply if delay itself created danger to the public, since an imminent risk removes the warrant for sequencing and requires immediate action instead.

Engineer A Peer Notification Duty Engineer A Confidentiality Duty
Event Timeline (9)
9 sequenced 6 actions 3 events
Case timeline
Engineer A is selected by the organized peer review program to serve as a peer reviewer, which triggers the request to sign the confidentiality agreement.
State changes (2)
  • began: Confidentiality Versus Cooperation Dilemma
  • began: Peer Review Confidentiality Bound
Upon original selection as a peer reviewer, Engineer A signs a confidentiality agreement promising not to disclose confidential information about peer-reviewed firms.
Causal-normative reasoning(confidence 0.75)
Engineer A's signing of the confidentiality agreement establishes the guiding constraint that later shapes how the discovered safety violation can be discussed and disclosed, meaning this early commitment sets up the tension between confidentiality and public safety that the later chain must resolve.
State changes (1)
  • began: Peer Review Confidentiality Bound
Engineer B's firm performed design work on a series of recent projects that may be in violation of state and local safety code requirements and could endanger public health, safety, and welfare.
Violates (1)
  • Duty to Protect Public Health and Safety
Causal-normative reasoning(confidence 0.80)
Design Work Execution's violation of the duty to protect public health and safety matters precisely because it is the root cause that produces the Safety Violation Discovery, making Engineer B's original design choice the origin point for every downstream obligation to assess, discuss, and eventually report the risk.
State changes (1)
  • began: Potential Public Endangerment From Design Work
Engineer A conducts a peer review visit to Engineer B's firm and reviews the technical documentation of a series of recent design projects.
At stake (1)
  • Confidentiality Obligation
Causal-normative reasoning(confidence 0.75)
Because Peer Review Conduct is what causally leads to Safety Violation Discovery, conducting the review under the guiding norm of confidentiality is significant since it is the very act through which a public safety threat comes to light while also binding Engineer A to restraint in how that finding is handled.
State changes (1)
  • began: Discovered Possible Code Violation
During the peer review of technical documentation from Engineer B's recent design projects, Engineer A discovers that Engineer B's work may violate state and local safety code requirements and could endanger public health, safety, and welfare. This discovery creates the conflict between the confidentiality agreement and the duty to protect the public.
State changes (3)
  • began: Potential Public Endangerment From Design Work
  • began: Confidentiality Versus Cooperation Dilemma
  • began: Discovered Possible Code Violation
The Board prescribes that Engineer A must exercise judgment and discretion to determine whether there is an imminent risk of harm to the public health and safety, such as loss of life or serious risk of injury to persons or property.
At stake (1)
  • Duty to Protect Public Health and Safety
Causal-normative reasoning(confidence 0.75)
Risk Assessment is guided by the paramount duty to public health and safety, and its causal role in prompting Collegial Issue Discussion shows that Engineer A's evaluation of the discovered violation is the necessary link translating a safety concern into an actionable professional dialogue.
The Board prescribes that Engineer A should expeditiously discuss the potential safety code violations with Engineer B, seeking clarification and early resolution, and if imminent risk exists must immediately notify Engineer B.
At stake (1)
  • Duty to Protect Public Health and Safety
Causal-normative reasoning(confidence 0.70)
Collegial Issue Discussion, guided jointly by the paramount safety duty and confidentiality, matters because it is the point where Engineer A must reconcile the obligation to protect the public with the constraints of confidentiality before any further escalation such as authority cooperation can occur.
A hypothetical conditional occurrence contemplated by the Board, in which Engineer B fails to take appropriate corrective actions after being notified by Engineer A, leaving the safety issue unresolved and permitting Engineer A to cooperate with proper authorities.
The Board prescribes a conditional step: if Engineer B fails to take appropriate corrective actions or the issue is unresolved, Engineer A must inform Engineer B that his only alternative is to cooperate with proper authorities, and Engineer A may then cooperate with proper authorities in furnishing information or assistance as required.
Fulfills (2)
  • Duty to Cooperate with Proper Authorities
  • Duty to Protect Public Health and Safety
Violates (1)
  • Confidentiality Obligation
Causal-normative reasoning(confidence 0.85)
Because Engineer B's failure to correct the discovered safety violation left the public at risk, Engineer A's decision to cooperate with authorities fulfills the duty to protect public health and safety and the duty to cooperate with proper authorities, even though it necessarily breaches the confidentiality agreement, since the paramount duty to safeguard the public overrides the narrower professional obligation of confidentiality when corrective action within the peer review process has failed.
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 engineer who volunteers as a peer reviewer for a state society peer review program designed to help engineers improve their professional practice. When you joined the program, you signed a confidentiality agreement promising not to disclose information about the firms you review. As part of your duties, you conduct a peer review visit at Engineer B's firm, examining technical documentation from a series of recent design projects. During your review, you find calculations and drawings suggesting that Engineer B's work deviates from applicable state and local safety code requirements. The nature of these deviations raises concerns that the completed or in-progress projects could pose a risk to public health and safety if left uncorrected. You now have this information in hand, obtained through a process bound by confidentiality, while facing questions about what obligations you have to Engineer B, to the peer review program, and to the public. In the pages ahead, you will need to work through how to respond to what you have found.

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 Reviewer

Guided by: Public Welfare in Peer Review, Confidentiality in Peer Review, Public Safety Paramount in Peer Review

Engineer A's duty to protect the public from a known safety code deficiency can directly conflict with the constraint that peer review findings are to be treated as confidential work product owed to the client or firm that commissioned the review. Acting on the safety duty may require breaching the confidentiality constraint that otherwise governs the reviewer's role.

Engineer B's constraint to comply with the safety code creates pressure on Engineer A to disclose noncompliance discovered during peer review, which directly strains the constraint that peer review information remain confidential. The two constraints pull in opposite directions when noncompliance is discovered but not yet remedied.

Tension between Engineer A Authority Cooperation Duty and Engineer A Confidentiality Duty

Tension between Engineer A Peer Notification Duty and Engineer A Confidentiality Duty

If Engineer B fails to correct the deficiency after initial notification, Engineer A's duty to escalate the warning to a higher authority or client conflicts with the ongoing duty to keep peer review communications confidential, since escalation necessarily discloses details of the review and its findings.

Engineer B Roles in this case: Design Engineer

Engineer A's duty to protect the public from a known safety code deficiency can directly conflict with the constraint that peer review findings are to be treated as confidential work product owed to the client or firm that commissioned the review. Acting on the safety duty may require breaching the confidentiality constraint that otherwise governs the reviewer's role.

Engineer B's constraint to comply with the safety code creates pressure on Engineer A to disclose noncompliance discovered during peer review, which directly strains the constraint that peer review information remain confidential. The two constraints pull in opposite directions when noncompliance is discovered but not yet remedied.

If Engineer B fails to correct the deficiency after initial notification, Engineer A's duty to escalate the warning to a higher authority or client conflicts with the ongoing duty to keep peer review communications confidential, since escalation necessarily discloses details of the review and its findings.

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

If Engineer B fails to correct the deficiency after initial notification, Engineer A's duty to escalate the warning to a higher authority or client conflicts with the ongoing duty to keep peer review communications confidential, since escalation necessarily discloses details of the review and its findings.

Engineer A's duty to protect the public from a known safety code deficiency can directly conflict with the constraint that peer review findings are to be treated as confidential work product owed to the client or firm that commissioned the review. Acting on the safety duty may require breaching the confidentiality constraint that otherwise governs the reviewer's role.

The Board’s deliberation

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

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. If Engineer A and Engineer B are unable to resolve the issue, Engineer A must inform Engineer B that as a professional engineer, his only alternative is to notify and inform the proper authorities as indicated above.
Opening States (5)
Peer Review Confidentiality Bound Discovered Possible Code Violation Potential Public Endangerment From Design Work Confidentiality Versus Cooperation Dilemma Code Applicability Despite Business Form
Summary
  • When a confidential peer review uncovers a genuine public safety code violation, the engineer's paramount duty to protect public health and safety overrides any confidentiality obligation owed to the client or firm that commissioned the review.
  • Engineer A should first attempt to resolve the concern through direct communication with Engineer B or the responsible party before escalating to authorities, preserving professional courtesy while ensuring safety is addressed.
  • If the safety issue is not resolved through internal channels, Engineer A has an affirmative obligation to report the violation to the appropriate public authorities, even though this breaches the confidentiality of the peer review relationship.

© Licensed under the GNU GPL v3