Step 4: Review

Engineers shall not aid or abet the unlawful practice of engineering by a person or firm.

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.

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.

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.

The 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.

The 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.

The 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.

Regarding 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.

Regarding 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.

Regarding 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.

From 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.

From 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.

Regarding 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.

Regarding 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.

The 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.

This 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.

The 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.

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

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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.

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.

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.

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.

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.

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.

The question arises because Engineer A occupies dual, potentially conflicting obligations as a bound peer reviewer and as an engineer with an overriding duty to public welfare, and the ambiguous severity of the discovered code violation makes it unclear which obligation should govern Engineer A's response.

The question emerged because Engineer A occupies two roles at once, a contractually bound peer reviewer and an ethically obligated professional, and the discovery of a code violation forces a choice between the two obligations without a clear rule establishing which one legally or ethically prevails.

The question arose because Engineer A's discovery of possible code violations creates ambiguity about whether the situation falls under routine peer review confidentiality or under the higher duty to protect public health and safety, and no objective criteria exist in the code to distinguish minor noncompliance from endangerment.

The question emerges because Corrective Action Failure exhausts the collegial remedy, forcing a choice between confidentiality and public safety warrants without clear guidance on escalation steps or institutional accountability, so the ambiguity of authority and process becomes the ethical question itself.

The question emerged because the case introduces a peer review program with its own confidentiality agreement, layering an additional institutional obligation on top of the standard client confidentiality versus public safety tension found in ordinary engineering practice, making it unclear whether existing precedent like BER Case 76-4 applies unchanged.

The question emerged because the peer review program's confidentiality norm was designed for collegial, non-adversarial evaluation, but the discovery of an uncorrected safety violation forces a choice between honoring that professional agreement and fulfilling the paramount obligation to protect the public.

The question arises because the peer review program's value depends on strict confidentiality, yet the discovery of a safety code violation activates a competing paramount duty to protect the public, and no clear threshold exists for when one obligation should yield to the other.

The question arises because the peer review relationship creates a confidentiality constraint that normally shields firm-level findings, yet the discovered violation involves potential public endangerment, forcing a comparison between Code Conformance Regardless of Business Form and Public Safety Paramount in Peer Review to determine which principle governs Engineer A's next action.

The question arises because a signed confidentiality agreement and a paramount duty to public welfare both apply to the same disclosure decision, forcing a deontological judgment about which obligation takes precedence when they conflict.

The question arises because Toulmin's model shows the same triggering data, a discovered safety violation, can be routed through two different obligation chains depending on whether cooperation or immediate protection is treated as the controlling warrant, and the case does not specify how imminent the risk is, leaving the consequentialist comparison unresolved.

The question arises because the peer review program's confidentiality structure was designed for collegial improvement, not for concealing genuine safety threats, so the discovery of a code violation forces a judgment about when the safety warrant supersedes the confidentiality warrant.

The question arises because the Board's original ruling bundled minor and major violations together under a single escalation obligation, and stakeholders want to know if the reasoning depended on the severity of harm rather than the mere existence of a violation.

The question arises because the Board's original reasoning may have treated the confidentiality agreement as foundational to the two-step process of warning then reporting, so removing that agreement forces examination of whether the private-resolution obligation stems from the contractual peer review context or from a broader, agreement-independent ethical principle.

Given that Engineer A found a possible safety violation and had an existing professional channel to Engineer B, the board concluded that immediate collegial discussion is the first ethical step, with escalation to authorities reserved as the fallback only if that discussion fails to resolve the issue.

Because the confidentiality provision in the Code is itself qualified by the absence of a safety concern, the board reasoned that once such a concern existed, Engineer A's contractual promise to the peer review program could never have ethically bound him to silence, making the apparent conflict actually a matter of contractual subordination to the Code.

Since the board did not supply objective criteria for distinguishing safety-endangering violations from minor noncompliance, it implicitly left this threshold determination to Engineer A's professional discretion, accepting the resulting risk of inconsistent application across similar cases.

Because the case record shows no program-level mechanism for handling safety violations, the board's conclusion effectively places the entire ethical and professional risk on Engineer A individually, without addressing whether the program itself should bear responsibility.

Given that the confidentiality agreement could not resolve a genuine, unremedied public safety risk after collegial efforts failed, the board concluded that the Code's paramount duty to public health and safety overrides the private contractual confidentiality obligation Engineer A undertook.

Given that Engineer B's violations ranged in severity and no explicit provision numerically ranks violation severity, the board concluded that Engineer A must use professional risk judgment, treating only violations with genuine safety implications as escalation-worthy.

Given that Engineer A's peer reviewer position grants privileged insight unavailable to an ordinary third party, the board concluded that this special access heightens rather than lessens the duty to protect the public, altering only the procedural path (first attempting collegial resolution) rather than the substantive obligation.

Given that Engineer B refused correction after collegial engagement and the risk was genuine, the board concluded that Engineer A's escalation to authorities fulfilled a categorical duty that cannot be waived by private contractual confidentiality.

Given that trying informal correction first did not preclude later reporting and preserved the functioning of the peer review system, the board concluded this sequencing produced better overall consequences than jumping straight to formal reporting.

Given the hypothetical that Engineer B's violations were merely technical without safety risk, the board concluded that Engineer A's ethical duty would be limited to advising correction privately, since the confidentiality-overriding safety duty specifically requires genuine endangerment.

Given that the sequencing obligation flows from professional collegiality norms rather than the signed agreement itself, the board reasoned that even absent that agreement Engineer A would still be expected to seek clarification with Engineer B before escalating to authorities.

Because the facts allowed for a private, collegial first step before any public safety risk became uncontrolled, the board concluded that confidentiality and public safety could be reconciled through staged rather than absolute priority.

Given that Engineer B's violations were found to genuinely endanger the public, the board concluded that the peer review confidentiality agreement could not ethically override the Code's paramount duty, though it would govern fully in the absence of such risk.

Because the peer review program was found to be an organizational arrangement rather than a substitute for code compliance, the board concluded that Engineer B's and Engineer A's core obligations remained unchanged by that business form.

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

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?

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?

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?

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