Step 4: Review

Hold paramount the safety, health, and welfare of the public.

Act for each employer or client as faithful agents or trustees.

Conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession.

Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code.

Engineers shall acknowledge their errors and shall not distort or alter the facts.

Engineers shall treat all persons with dignity, respect, fairness and without discrimination.

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.

Engineers in private practice shall not review the work of another engineer for the same client, except with the knowledge of such engineer, or unless the connection of such engineer with the work has been terminated.

The Board cited this case to illustrate how prior peer review involvement does not necessarily preclude later participation in a design-build joint venture, provided agency approval and conflict-of-interest compliance are met.

The Board cited this case to establish that a peer reviewer who discovers potential safety code violations has an obligation to discuss concerns with the reviewed engineer and, if unresolved, to notify appropriate authorities even when bound by a confidentiality agreement.

The Board cited this case parenthetically to contrast the present situation, noting that Case 93-3 addressed a scenario where the Owner refused to advise the engineer of the planned peer review, unlike the present case where the Owner agreed to do so.

Engineer B is ethically required to make certain that Engineer A is advised of the planned peer review.

Beyond the Board's finding that Engineer B is ethically required to ensure Engineer A is advised of the planned peer review, Engineer B's obligation does not merely require passive reliance on the Owner's promise to notify. Engineer B bears an independent, affirmative duty to verify that notification has actually occurred before commencing any review activity. If the Owner fails to follow through on the agreed notification, Engineer B's continued participation in the review would itself constitute a violation of the peer review notification norm embedded in Code provision III.7.a. The ethical obligation is not discharged by the Owner's mere consent to notify; it is discharged only when Engineer B has reasonable confirmation that Engineer A has in fact been informed. This means Engineer B must treat notification as a precondition to engagement, not merely a procedural courtesy to be delegated entirely to the Owner.

The Board's conclusion that Engineer B must ensure notification implicitly resolves the tension between the Faithful Agent Obligation and the Peer Review Notification Obligation in favor of the latter, but the Board did not articulate the limiting principle. The correct limiting principle is that the Faithful Agent Obligation operates only within ethical limits, as the Code itself specifies in provision I.4. When an Owner's instruction - here, to conduct a covert review - would require Engineer B to violate a professional norm protecting a third-party engineer's dignity and procedural rights under III.7.a. and III.1.f., that instruction falls outside the scope of lawful and ethical client service. Engineer B's refusal of the covert instruction was therefore not a breach of client loyalty but rather the precise conduct that the Code's faithful agent standard demands: serving the client's legitimate interests while refusing to become an instrument of professionally impermissible conduct. The Board should have made this limiting principle explicit to prevent future misreading of the faithful agent duty as an override of peer review procedural norms.

The Board's conclusion that Engineer A may not ethically object to the peer review, while sound, rests on a public safety predicate - the known design errors in the first tower - that the Board did not fully develop into an independent affirmative obligation. Engineer A's prior acknowledgment duty under Code provision III.1.a., which requires engineers to admit their errors and not distort or alter the facts, independently compels Engineer A not merely to tolerate the peer review but to actively facilitate it. An engineer who has produced significant design errors and who then refuses to cooperate with a review designed to prevent replication of those errors in a second structure is not simply exercising a procedural objection; that engineer is actively impeding the correction of a known professional failure in a context where public safety is at stake. This conduct simultaneously violates III.1.a. (error acknowledgment), the Non-Obstruction of Legitimate Peer Review principle, and the paramount public welfare obligation of Code provision I.1. The Board's answer to Q2 should therefore have been grounded not only in the Owner's right to commission the review but in Engineer A's independent ethical duty to cooperate arising from the prior error.

The Board did not address the perverse incentive created by the Owner's option to terminate Engineer A as an alternative to notification. If termination is treated as an ethically equivalent substitute for notification - effectively allowing the Owner to circumvent the peer review notification norm by simply removing the engineer whose work is being reviewed - the protective purpose of Code provision III.7.a. is gutted. An engineer cannot be notified of a review of their work if they have already been removed from the project. The Board should have clarified that termination used as a mechanism to avoid notification, rather than as a genuine exercise of the Owner's right to select engineers, would itself constitute a procedurally impermissible workaround. Engineer B, upon learning that the Owner was considering termination specifically to avoid the notification obligation, would have an independent duty to decline the engagement under those circumstances, because proceeding would make Engineer B complicit in the circumvention of the very norm Engineer B had previously insisted upon.

The Board's analysis implicitly assumed that the peer review process, once properly initiated with notification, is self-contained and its findings are for the Owner's use alone. However, if Engineer B's peer review of the second tower plans reveals that the same categories of significant design errors present in the first tower have been replicated, Engineer B faces an independent obligation that the Board did not address: the duty to consider escalation to public authorities if the Owner declines to act on the findings. Code provision I.1. places public safety paramount, and Code provision II.1.c. and III.4. protect client confidentiality only to the extent that disclosure is not required to protect the public. A peer review that uncovers structural defects posing genuine public safety risks cannot ethically remain confidential if the Owner suppresses the findings. Engineer B must therefore understand, at the outset of the engagement, that the peer review confidentiality framework is bounded by the same public safety override that the Board recognized in BER Case 96-8, and that Engineer B's obligations do not terminate with delivery of the report to the Owner.

The Board's conclusion that Engineer A may not ethically object to the peer review would have been materially more difficult to sustain absent the public safety predicate established by the known design errors in the first tower. In a scenario where no prior errors had been discovered, Engineer A's refusal to consent would have presented a genuine tension between the Owner's right to commission independent review and Engineer A's professional dignity interest in not being subjected to unsolicited scrutiny of competent work. The existence of prior significant design errors is therefore not merely a factual background detail but the essential ethical predicate that converts Engineer A's refusal from a potentially defensible professional position into an ethically impermissible obstruction. This distinction matters for future cases: the Board's reasoning should not be read as establishing that engineers may never object to peer review of their work, but rather that engineers who have produced known errors in related prior work on the same project have forfeited the standing to obstruct review of subsequent work on that project, because the public safety interest has been concretely activated by their own prior professional failure.

In response to Q101: If the Owner had never voluntarily agreed to notify Engineer A, Engineer B would have faced an independent, unconditional obligation to refuse the covert engagement entirely rather than simply object and await resolution. The notification requirement under Code provision III.7.a is not a procedural preference that can be waived by client instruction - it is a structural precondition to the legitimacy of the peer review itself. Engineer B's acceptance of a covert assignment, even provisionally, would have constituted an ethical violation at the moment of acceptance, not merely at the moment of conducting the review. The ethical violation inheres in agreeing to participate in a process designed to circumvent a colleague's right to notice, regardless of whether the review is ultimately conducted. Engineer B's proper course, absent Owner agreement to notify, would have been to decline the engagement entirely and explain that the engagement could only proceed on terms consistent with professional obligations. The fact that the Owner did agree to notify does not retroactively validate Engineer B's initial acceptance under covert terms; it merely cures the procedural defect before the violation was consummated.

In response to Q102: The Owner's legal ability to terminate Engineer A as a workaround to the notification requirement creates a genuine perverse incentive that the Board's conclusion, while correct on its face, fails to fully address. If notification is required but termination is a permissible substitute, then the protective norm is effectively optional for any Owner willing to pay the transactional cost of dismissal. The Board should have addressed whether termination-as-substitution is ethically equivalent to notification. It is not. Termination severs the professional relationship and eliminates Engineer A's opportunity to respond, correct, or participate - outcomes that notification is specifically designed to preserve. A termination motivated primarily by the desire to avoid notification obligations would itself constitute an ethically problematic use of the Owner's contractual power, potentially implicating the Owner's own duty of procedural fairness toward Engineer A. Engineer B, upon learning that termination was being contemplated as a substitute for notification, would have an independent obligation to flag this concern to the Owner, since facilitating a termination-as-evasion strategy would undermine the very professional norm Engineer B is obligated to uphold.

In response to Q103: Engineer A bears affirmative, independent disclosure obligations regarding the known design errors in the first tower that exist entirely apart from and prior to any peer review being commissioned. Code provision III.1.a requires engineers to acknowledge their errors and not distort or alter the facts. This obligation is self-executing - it is triggered by Engineer A's own knowledge of the errors, not by the initiation of external review. Engineer A's duty to disclose the first-tower errors to the Owner arose at the moment Engineer A became aware of those errors, and that duty was not contingent on whether a peer review was ever commissioned, whether the Owner asked, or whether the errors were discovered by a third party. The failure to proactively disclose known design errors to the Owner while simultaneously designing the second tower compounds the ethical violation: Engineer A was not merely passively concealing past errors but was actively continuing professional work for the same client on a related structure while withholding material safety-relevant information. This sequence of conduct implicates not only III.1.a but also the paramount public safety obligation under I.1, since the Owner's ability to make informed decisions about the second tower was directly impaired by Engineer A's non-disclosure.

In response to Q104: Engineer B has an independent obligation to report known design defects in Engineer A's first tower work to public authorities if the Owner declines to act on them, regardless of the outcome of the peer review process. This obligation derives from the paramount public safety duty under I.1, which supersedes both the confidentiality obligations under II.1.c and III.4 and the faithful agent obligation under I.4. The peer review process is a mechanism for identifying and correcting defects - it is not a substitute for public safety reporting when the Owner fails to act. If Engineer B, through the peer review, confirms significant structural defects in the first tower and the Owner declines to remediate or report, Engineer B's obligation to hold paramount the safety, health, and welfare of the public independently compels escalation to relevant authorities. The confidentiality protections that ordinarily shield client information do not extend to concealing known public safety hazards. The Board's silence on this point is a significant gap: the peer review framework cannot function as a mechanism that simultaneously uncovers safety defects and then seals them within a confidential client relationship. Engineer B must understand from the outset that accepting this engagement carries the potential obligation to escalate findings over the Owner's objection if public safety demands it.

In response to Q201: The tension between Engineer B's faithful agent obligation under I.4 and the peer review notification obligation under III.7.a is resolved by the Code's own internal hierarchy. The faithful agent duty is explicitly bounded by ethical limits - I.4 requires Engineer B to act as a faithful agent 'within ethical limits,' meaning that client instructions that require Engineer B to violate professional obligations are not instructions Engineer B is ethically permitted to follow. The Owner's instruction to conduct a covert review without notifying Engineer A is precisely the kind of client instruction that falls outside the scope of the faithful agent duty. Engineer B's resolution of this tension - refusing the covert instruction and conditioning engagement on notification - is not a breach of client loyalty but rather the correct application of the Code's hierarchy: faithful agency operates within, not above, professional ethical obligations. Engineer B's refusal to comply with the covert instruction is therefore not a tension requiring compromise but a straightforward application of the principle that client loyalty cannot be used to override professional norms that protect third parties.

In response to Q202: The confidentiality principle does not categorically conflict with the public welfare paramount principle in the peer review context - rather, the peer review framework itself is the mechanism through which these principles are reconciled. Confidentiality under II.1.c and III.4 protects client information from unauthorized third-party disclosure; it does not protect an engineer's design work from legitimate review commissioned by the client who owns that work. The Owner, as the commissioning party for both the original design and the peer review, has not violated Engineer A's confidentiality by authorizing Engineer B to review Engineer A's plans - the Owner is the client whose consent is required, and the Owner has given that consent. Engineer A's confidentiality interest in the design work runs to the Owner, not against the Owner. The public safety predicate - confirmed design errors in the first tower creating risk of replication in the second - does not need to override confidentiality because confidentiality is not properly invoked as a barrier to Owner-authorized peer review. The public welfare paramount principle operates independently to ensure that even if confidentiality were somehow implicated, it would yield to the safety imperative.

In response to Q203: The professional dignity principle protecting Engineer A from covert or disrespectful review under III.1.f does not survive intact once the notification requirement has been satisfied. Engineer A's dignity interest is protected by the notification obligation - the requirement that Engineer A be informed of the review before it proceeds. Once notification has occurred, Engineer A's dignity-based objection to the manner of the review is substantially addressed. The existence of prior design errors does not extinguish Engineer A's dignity interests entirely, but it does significantly constrain the weight those interests can carry against the public safety imperative. An engineer who has produced work containing significant design errors and who is now designing a related structure for the same client has a diminished claim to object to professional scrutiny of that subsequent work on dignity grounds. The dignity principle protects engineers from arbitrary, malicious, or procedurally unfair review - it does not protect engineers from legitimate, Owner-authorized, properly notified review of work that has already demonstrated quality concerns. Engineer A's refusal to consent, framed as a dignity objection, is therefore not ethically sustainable under the Code.

In response to Q204: The conflict between Engineer A's error acknowledgment and corrective disclosure obligation under III.1.a and the client loyalty principle under I.4 is resolved by the same hierarchical logic that resolves Engineer B's faithful agent tension. Client loyalty, like faithful agency, operates within ethical limits. III.1.a imposes an unconditional obligation to acknowledge errors - the provision contains no exception for situations where disclosure might damage the client relationship or expose the engineer to professional consequences. Engineer A's obligation to acknowledge the first-tower design errors to the Owner arose independently of the peer review and was not contingent on the Owner's demand for disclosure. The client loyalty principle cannot be invoked to justify concealing material design errors from the very client whose project is affected by those errors, because doing so would harm rather than serve the client's genuine interests. The Board's failure to address this tension explicitly leaves open the question of whether Engineer A's non-disclosure prior to the peer review was itself an independent ethical violation - and the answer, under a straightforward reading of III.1.a, is that it was.

In response to Q301: From a deontological perspective, Engineer B's duty to notify Engineer A of the peer review is unconditional and derives from both professional courtesy norms and public safety obligations, though the two grounds operate differently. The professional courtesy ground - rooted in III.7.a and III.1.f - establishes notification as a categorical rule of professional conduct that applies regardless of consequences: engineers do not conduct covert reviews of colleagues' work because doing so violates the dignity and procedural rights of the reviewed engineer as a matter of principle. The public safety ground - rooted in I.1 - establishes notification as instrumentally necessary to ensure that the peer review process functions legitimately and that its findings can be acted upon without procedural taint. A deontological analysis does not require Engineer B to calculate whether covert review would produce better outcomes; it requires Engineer B to recognize that covert review is categorically impermissible as a mode of professional conduct. The Owner's instruction to conduct a covert review is therefore not merely inadvisable - it is a request that Engineer B act in a manner inconsistent with categorical professional duties, and Engineer B's refusal is not a matter of prudential judgment but of ethical obligation.

In response to Q302: From a consequentialist perspective, the demonstrated risk of replicating known design errors in the second tower provides a compelling and sufficient justification for proceeding with peer review over Engineer A's refusal to consent. The consequentialist calculus here is not close: the potential harm from unchecked structural defects in a second tower - which could include structural failure, injury, or death - vastly outweighs the harm to Engineer A from undergoing a professionally conducted, properly notified peer review. The harm of coerced professional review, to the extent it constitutes harm at all, is primarily reputational and professional - it is the discomfort of having one's work scrutinized after a prior error has been confirmed. This harm is not trivial, but it is categorically different in kind and magnitude from the public safety risk posed by potentially defective structural design. A consequentialist analysis would also note that the peer review process, properly conducted with confidentiality protections, minimizes the reputational harm to Engineer A while maximizing the safety benefit to the public. The Board's implicit conclusion that Engineer A may not ethically object is therefore well-supported on consequentialist grounds, and the public safety predicate is not merely a rhetorical device but the central consequentialist justification for overriding Engineer A's refusal.

In response to Q303: From a virtue ethics standpoint, Engineer B's refusal to comply with the Owner's covert review instruction and insistence on notification as a precondition to engagement exemplifies the kind of professional integrity and collegial respect that the NSPE Code envisions. The virtuous engineer is not merely one who follows rules when convenient but one who maintains professional standards even when client pressure creates incentives to deviate. Engineer B's conduct - identifying the ethical problem with the covert instruction, refusing to proceed on those terms, and conditioning continued engagement on the Owner's agreement to notify Engineer A - demonstrates practical wisdom, professional courage, and genuine respect for a colleague's procedural rights. This conduct is particularly significant because Engineer B had a financial and professional interest in retaining the engagement: refusing the Owner's instruction carried the risk of losing the assignment entirely. The willingness to accept that risk in order to maintain professional standards is precisely the kind of honorable conduct that I.6 envisions when it requires engineers to 'conduct themselves honorably, responsibly, ethically, and lawfully.' Engineer B's refusal is not merely procedurally correct - it is a model of professional virtue in a situation where the easier path was available.

In response to Q304: From a deontological perspective, Engineer A's prior acknowledgment obligation under III.1.a independently compels cooperation with the peer review, such that refusal constitutes a categorical ethical violation irrespective of outcomes. The reasoning proceeds as follows: Engineer A has already produced work containing significant design errors. III.1.a requires Engineer A to acknowledge those errors. Cooperation with a legitimately commissioned peer review of related subsequent work is the concrete professional mechanism through which that acknowledgment obligation is discharged in the context of ongoing design work for the same client. Refusing to cooperate with the peer review is therefore not merely a separate ethical violation - it is a continuation and compounding of the original failure to acknowledge errors, now extended to obstruct the process by which those errors and their potential replication might be identified and corrected. The deontological force of this conclusion does not depend on whether the peer review will actually find errors in the second tower: the obligation to cooperate derives from the prior error and the acknowledgment duty, not from the anticipated findings. Engineer A's refusal is therefore not merely imprudent or consequentially harmful - it is a categorical violation of the duty to acknowledge errors and not obstruct legitimate professional accountability processes.

In response to Q401: If Engineer B had complied with the Owner's initial instruction and conducted the peer review covertly without notifying Engineer A, the findings would have been ethically compromised and their usability by the Owner would have been seriously impaired. The procedural violation - conducting a review without the required notification - taints the process regardless of the substantive accuracy of the findings. From an ethical standpoint, the Owner could not rely on those findings to take adverse action against Engineer A without exposing both the Owner and Engineer B to legitimate professional and potentially legal challenge based on the procedural defect. Engineer B would have incurred professional liability for the violation of III.7.a independent of whether the review uncovered genuine safety defects. The discovery of real safety defects would not retroactively cure the procedural violation; it would instead create a secondary dilemma in which Engineer B possessed safety-critical information obtained through an ethically impermissible process. In that scenario, Engineer B's public safety obligation under I.1 would likely require disclosure of the safety findings despite the procedural taint, but Engineer B would simultaneously face professional accountability for the manner in which those findings were obtained. The covert review path therefore creates a no-win scenario for Engineer B that the proper notification path entirely avoids.

In response to Q402: Had no design errors been discovered in the first tower, the ethical calculus for overriding Engineer A's refusal to consent to peer review would have been materially different, and the Board's conclusion that Engineer A may not ethically object would have required substantially more justification. The public safety predicate - confirmed errors in the first tower creating risk of replication in the second - is doing significant work in the Board's analysis. Without that predicate, Engineer A's refusal to consent would have been a closer ethical question. The Owner's right to commission peer review of work being performed for the Owner's benefit is not contingent on prior errors having been found, but the ethical weight of Engineer A's objection would have been considerably greater in the absence of a demonstrated quality concern. In that scenario, the peer review would have appeared more like an expression of Owner distrust than a response to identified risk, and Engineer A's dignity and professional autonomy interests would have carried more weight against the non-obstruction principle. The Board's conclusion that Engineer A may not ethically object is therefore most defensible as a public-safety-predicated conclusion, and its application to peer reviews lacking that predicate would require independent justification grounded in the Owner's general right to quality assurance rather than in the specific safety imperative present in this case.

In response to Q403: If the Owner had chosen to terminate Engineer A from the project rather than notify them of the peer review, Engineer B's notification obligation would not have been fully discharged by that termination. The notification obligation under III.7.a exists to protect the reviewed engineer's professional interests and dignity - it is not merely a procedural formality that can be satisfied by eliminating the engineer's role in the project. Termination of Engineer A would have changed the factual circumstances of the review but would not have addressed the underlying professional courtesy norm that notification is designed to serve. Moreover, a termination motivated primarily by the desire to avoid the notification obligation would itself raise independent ethical concerns: it would constitute a use of the Owner's contractual power to circumvent a professional norm, and Engineer B's awareness of that motivation would implicate Engineer B's own obligation not to participate in arrangements that undermine professional standards. The termination path would also raise the question of whether Engineer B, now reviewing the work of a terminated engineer who had no opportunity to respond or participate, was conducting a fair and professionally legitimate review - a question that bears directly on the integrity of the peer review process itself and on Engineer B's obligations under I.6.

In response to Q404: If Engineer A had proactively disclosed the first-tower design errors to the Owner before the peer review was commissioned, that voluntary disclosure would have materially improved Engineer A's ethical standing but would not have extinguished the Owner's right to commission peer review of the second tower. The voluntary disclosure would have demonstrated compliance with III.1.a's acknowledgment obligation and would have shown good faith professional accountability - factors that would weigh significantly in Engineer A's favor in any assessment of Engineer A's overall professional conduct. However, the Owner's right to commission peer review of ongoing design work is not contingent on whether the original engineer has acknowledged prior errors; it derives from the Owner's legitimate interest in quality assurance for work being performed on the Owner's behalf. The public safety imperative - the risk that errors might be replicated in the second tower - would have independently sustained the Owner's right to commission the review regardless of Engineer A's prior disclosure. What the voluntary disclosure would have changed is the ethical weight of Engineer A's potential objection to the review: an Engineer A who had proactively acknowledged errors would have had a stronger claim to professional good faith, making any subsequent refusal to cooperate with peer review appear more as a procedural objection than as an attempt to conceal ongoing problems. Even so, that stronger claim would not have been sufficient to override the Owner's right to peer review given the confirmed safety predicate.

The tension between the Faithful Agent Obligation and the Peer Review Notification Obligation was resolved by treating professional courtesy and transparency as threshold conditions that define the outer boundary of legitimate client service, not as competing values to be balanced against client instructions. When the Owner instructed Engineer B to conduct a covert review, Engineer B's refusal was not a breach of client loyalty but rather a recognition that the Faithful Agent Obligation operates only 'within ethical limits.' The case teaches that client instructions which require an engineer to violate a peer professional's right to notification are categorically outside the scope of faithful agency - the obligation to serve the client simply does not extend to procedurally improper conduct. Engineer B's ethical path was therefore not a compromise between two equal duties but a sequential gate: notification compliance was a precondition to any legitimate engagement, not a factor to be weighed against the Owner's preference for secrecy.

The tension between the Public Welfare Paramount principle and the Confidentiality Principle was resolved asymmetrically and conditionally: confidentiality protects the content of peer review proceedings once properly initiated, but it does not shield the existence of a peer review from the engineer whose work is being reviewed. The case establishes a two-stage confidentiality architecture. In the first stage - the decision to commission and conduct a peer review - transparency is mandatory and confidentiality yields entirely to the professional dignity and notification rights of the reviewed engineer. In the second stage - the conduct and findings of the review itself - confidentiality is restored as a mechanism that actually facilitates cooperation, because Engineer A's willingness to engage is conditioned on assurance that findings will not be weaponized beyond the immediate safety purpose. This sequencing reveals that Public Welfare Paramount does not simply override confidentiality; rather, it restructures when and how confidentiality applies, using it instrumentally to achieve the safety outcome rather than treating it as an obstacle. The precedent from BER Case 96-8 reinforces this by showing that even within a confidential peer review framework, safety code violations can trigger escalation obligations, confirming that public welfare sets the ceiling above which no confidentiality norm can reach.

The tension between the Professional Dignity principle protecting Engineer A from covert or disrespectful review and the Non-Obstruction of Legitimate Peer Review principle barring Engineer A from blocking the review was resolved by making dignity-protection procedurally contingent rather than substantively absolute. Engineer A's dignity interest was fully honored at the notification stage - the requirement that Engineer A be informed before any review proceeds is precisely the mechanism by which professional respect is operationalized. However, once notification occurred and the public safety predicate was established through the confirmed design errors in the first tower, Engineer A's dignity-based objections to the review itself were extinguished. The case teaches that professional dignity is a procedural entitlement, not a substantive veto. The Error Acknowledgment and Corrective Disclosure Obligation further erodes Engineer A's standing to object: an engineer who has produced significant design errors and has not proactively disclosed them cannot invoke professional dignity to prevent the very review mechanism designed to protect the public from those errors. The prior errors do not merely weaken Engineer A's dignity claim - they affirmatively activate a competing obligation that runs in the opposite direction, requiring facilitation rather than obstruction of the review. This interaction between the dignity principle and the error acknowledgment obligation reveals that professional dignity in the NSPE framework is not a shield against accountability but a guarantee of fair process within an accountability structure.

Is Engineer B ethically required to make certain that Engineer A is advised of the planned peer review?

Is Engineer A ethically required to cooperate with the peer review of Engineer B?

If Owner had never voluntarily agreed to notify Engineer A, what ethical obligation would Engineer B have had to unilaterally refuse the engagement or independently ensure notification, and at what point does Engineer B's acceptance of a covert assignment itself become an ethical violation?

Does the Owner's ability to simply terminate Engineer A as a workaround to the notification requirement create a perverse incentive that undermines the protective purpose of the peer review notification norm, and should the Board have addressed whether termination is an ethically equivalent substitute for notification?

What affirmative obligations, if any, does Engineer A have to proactively disclose the known design errors in the first tower to the Owner and to relevant authorities, independent of and prior to any peer review being commissioned?

Should the Board have addressed whether Engineer B has an independent obligation to report the known design defects in Engineer A's first tower work to public authorities if the Owner declines to act on them, regardless of the outcome of the peer review process?

Does the Faithful Agent Obligation requiring Engineer B to serve the Owner's interests conflict with the Peer Review Notification Obligation requiring Engineer B to ensure Engineer A is informed, and how should Engineer B resolve this tension when the Owner explicitly instructs secrecy?

Does the Confidentiality Principle protecting Engineer A's design work and client relationship conflict with the Public Welfare Paramount principle that demands peer review of potentially defective second tower plans, and under what conditions does public safety categorically override confidentiality in the peer review context?

Does the Professional Dignity principle protecting Engineer A from covert or disrespectful review conflict with the Non-Obstruction of Legitimate Peer Review principle that bars Engineer A from blocking the review, and does the existence of prior design errors diminish or extinguish Engineer A's dignity-based objections entirely?

Does the Error Acknowledgment and Corrective Disclosure Obligation imposed on Engineer A conflict with the Client Loyalty principle that might lead Engineer A to minimize or conceal design errors to preserve the client relationship, and how should the Board weigh these competing duties when the client has not yet demanded disclosure?

From a deontological perspective, does Engineer B have an unconditional duty to notify Engineer A of the peer review regardless of the Owner's instructions, and does that duty derive from professional courtesy norms, public safety obligations, or both?

From a consequentialist perspective, does the demonstrated risk of replicating known design errors in the second tower sufficiently justify overriding Engineer A's refusal to consent to peer review, and how should the Board weigh the harm of coerced professional review against the harm of unchecked structural defects?

From a virtue ethics standpoint, did Engineer B demonstrate professional integrity and collegial respect by refusing the Owner's covert review instruction, and does that refusal itself constitute the kind of honorable conduct that the NSPE Code envisions when engineers navigate conflicts between client loyalty and professional courtesy?

From a deontological perspective, does Engineer A's prior acknowledgment obligation under the Code - requiring engineers to admit their errors - independently compel cooperation with the peer review, such that refusing the review is not merely imprudent but constitutes a categorical ethical violation irrespective of outcomes?

If Engineer B had complied with the Owner's initial instruction and conducted the peer review covertly without notifying Engineer A, would Engineer B's subsequent findings have been ethically usable by the Owner, and would Engineer B have incurred professional liability for the procedural violation even if the review itself uncovered genuine safety defects?

Had no design errors been discovered in the first tower, would the ethical calculus for overriding Engineer A's refusal to consent to peer review have been materially different, and would the Board's conclusion that Engineer A 'may not ethically object' still hold absent the public safety predicate?

If the Owner had chosen to terminate Engineer A from the project rather than notify them of the peer review, would Engineer B's notification obligation have been fully discharged, and would that termination path have raised independent ethical concerns about using peer review as a pretext for removing an inconvenient engineer?

If Engineer A had proactively disclosed the first-tower design errors to the Owner before the peer review was commissioned, would that voluntary disclosure have altered Engineer A's ethical standing to object to the peer review of the second tower, or would the public safety imperative have independently sustained the Owner's right to commission the review regardless?

Engineer A's production of significantly flawed plans for the first tower directly triggers downstream peer review obligations and public safety constraints, establishing the factual predicate that makes all subsequent actions ethically necessary while simultaneously violating Engineer A's baseline professional accountability and error acknowledgment obligations.

The Owner's covert retention of Engineer B, while motivated by a legitimate interest in independent review of potentially dangerous second tower plans, directly violates the peer review notification and consent obligation owed to Engineer A and transgresses the covert peer review prohibition constraint that protects professional dignity and procedural fairness.

Engineer B's refusal to conduct a covert peer review fulfills the peer review notification and consent obligation and the faithful agent obligation within ethical limits, as Engineer B correctly recognizes that professional courtesy and ethical constraints prohibit reviewing a colleague's work without that colleague's knowledge, even when instructed to do so by the client.

The Owner's consent to notify Engineer A remedies the prior procedural violation of covert retention, fulfilling the peer review notification and consent obligation and restoring procedural fairness, though it simultaneously activates the reviewed engineer consent refusal override constraint by opening the possibility that Engineer A will refuse to cooperate.

Engineer A's refusal to consent to peer review of the second tower plans violates multiple overlapping obligations - including non-obstruction of legitimate peer review, post-error peer review facilitation, public safety paramountcy, and professional accountability - because the confirmed existence of significant design errors in the first tower creates an especially strong ethical duty to cooperate with independent review rather than obstruct it.

Having been forced into transparency by Engineer B's refusal to conduct a covert review and then confronted with Engineer A's explicit refusal to consent to peer review, the Owner must now select among difficult post-refusal strategies - such as proceeding with the review over Engineer A's objection, replacing Engineer A, or abandoning the second tower project - each of which is bounded by the Owner's procedural fairness obligations, the prohibition on covert review, public safety imperatives arising from confirmed design errors in the first tower, and the constraint that Engineer A's consent refusal cannot simply be allowed to block a legitimately warranted peer review.

This question emerged because the Owner's instruction to conduct a covert review placed Engineer B at the intersection of two legitimate but conflicting professional obligations-client loyalty and collegial notification-neither of which is absolute. The question crystallizes precisely because the data (covert instruction, Engineer B's objection, Owner's eventual concession) leaves unresolved whether Engineer B's ethical duty is satisfied by securing a promise of notification or requires personal confirmation.

This question arose because Engineer A's refusal to consent placed the non-obstruction and public-safety warrants in direct conflict with the principle that professional obligations must be grounded in identifiable duties rather than mere client preference. The data-confirmed design errors, a legitimately commissioned review, and an explicit refusal-creates irreducible tension between accountability norms and the limits of compellable professional cooperation.

This question emerged because the Board's resolution depended on the Owner voluntarily agreeing to notify Engineer A, leaving unanalyzed the harder counterfactual in which no such agreement is reached-a gap that exposes whether Engineer B's ethical obligation is merely to advocate for notification or to refuse engagement entirely when notification is denied. The data of a covert instruction combined with the notification warrant's silence on the threshold-versus-procedural distinction creates the irreducible uncertainty this question addresses.

This question emerged because the Board identified termination as one of three Owner options without analyzing whether it is ethically equivalent to the covert review Engineer B refused to conduct, leaving a structural gap in the analysis that allows the protective purpose of the notification norm to be defeated through a formally distinct but functionally identical mechanism. The data of Engineer A's refusal combined with the Owner's unconstrained post-refusal options creates the perverse-incentive tension this question targets.

This question emerged because the Board's analysis focused on the peer review process as the mechanism for addressing Engineer A's design errors, leaving unexamined whether Engineer A's independent professional obligations under the public-safety paramount principle required proactive disclosure before, during, or entirely apart from any peer review. The data of confirmed first-tower errors combined with Engineer A's refusal to cooperate with peer review creates an accountability vacuum that the notification and cooperation analysis alone cannot fill, forcing the question of what Engineer A must do unilaterally.

This question arose because the Board's opinion resolved Engineer B's notification obligation to Engineer A and the Owner's procedural duties but did not explicitly address whether Engineer B holds a residual, independent duty to report known first-tower defects to public authorities if the Owner refuses corrective action. The gap between the faithful agent obligation and the public welfare paramount principle creates a structural void in the Board's analysis that the question exposes.

This question arose because the Owner's covert instruction placed Engineer B at the intersection of two simultaneously activated warrants with no explicit hierarchy established in the NSPE Code for this specific peer review context. The question crystallizes because the Board resolved the outcome (Engineer B should notify) without fully articulating the normative priority rule that subordinates faithful agency to peer review notification obligations.

This question arose because the BER 96-8 precedent established a confidentiality-bounded safety escalation framework but did not specify the precise conditions under which public safety categorically overrides confidentiality in the peer review initiation context as opposed to the mid-review discovery context. The gap between when confidentiality protection attaches and when public welfare paramountcy displaces it generates the question.

This question arose because the Board's framework for peer review consent treats notification as resolving the dignity concern without addressing whether prior professional errors alter the normative weight of dignity-based objections. The collision between Engineer A's procedural right to dignified treatment and the substantive accountability implications of known prior errors creates a question the Board's binary consent analysis does not resolve.

This question arose because the Board's analysis focused on the peer review process as the mechanism for addressing Engineer A's errors rather than directly confronting whether Engineer A bears an independent, proactive disclosure obligation that operates prior to and independent of any peer review outcome. The tension between client loyalty as a relationship-preserving instinct and error acknowledgment as a non-negotiable professional duty generates the question precisely because the client has not yet demanded disclosure, leaving the trigger condition for Engineer A's obligation ambiguous.

This question arose because the Owner's covert instruction placed Engineer B at the intersection of two independently authoritative norms - client loyalty and peer-review procedural fairness - neither of which is obviously subordinate to the other in the absence of an imminent safety emergency. The question of whether the duty to notify derives from professional courtesy, public safety, or both is therefore not resolved by the data alone and requires a deontological ranking of the competing warrants.

This question emerged because Engineer A's refusal created a genuine consequentialist dilemma: the harm calculus of allowing potentially defective second-tower plans to proceed unchecked appears to outweigh the harm of procedural coercion, yet the peer-review framework's legitimacy depends on consent norms that cannot be suspended merely because the subject engineer is uncooperative. The Board must therefore weigh incommensurable harms - structural risk against professional autonomy - without a clear lexical ordering between them.

This question arose because Engineer B's conduct sits at the boundary between two virtue-ethics ideals - collegial respect for Engineer A and loyal service to the Owner - and the NSPE Code does not explicitly rank these virtues when they conflict in a peer-review context. The question of whether the refusal itself constitutes honorable conduct therefore requires a virtue-theoretic account of which character trait the Code most centrally envisions engineers to embody.

This question emerged because the NSPE Code's error-acknowledgment provision and its peer-review consent framework were not designed in explicit coordination, leaving open whether the former can serve as an independent deontological basis for compelling the latter. Engineer A's simultaneous possession of known design errors and refusal of review created a factual predicate that forces the question of whether these two Code provisions interact categorically or merely presumptively.

This question arose because the hypothetical scenario exposes a gap in the peer-review framework: the Code addresses the obligation to notify and the obligation to report safety violations, but does not explicitly resolve whether a procedurally defective review that uncovers genuine hazards creates separable questions of finding usability and reviewer liability. The coexistence of a safety-discovery outcome with a consent-violation process forces a Toulmin analysis of whether the warrant authorizing use of safety findings can be severed from the warrant condemning the procedural breach.

This question emerged because the Board's reasoning chain is structurally dependent on the first-tower error as the factual trigger for the public-safety warrant; removing that trigger exposes whether the peer-review cooperation obligation is independently grounded or whether it collapses back into a standard consent framework. The question forces examination of whether 'may not ethically object' is a categorical professional duty or a context-sensitive conclusion whose warrant evaporates with its factual predicate.

This question emerged because the ethical analysis of Engineer B's notification obligation was resolved in the canonical fact pattern by Owner notification, leaving unexamined whether the obligation's purpose is procedural (inform the engineer) or substantive (protect the engineer from retaliatory use of peer review). The termination counterfactual exposes that gap by presenting a scenario where the letter of the notification duty is bypassed while its protective spirit may be violated, raising independent concerns about Owner Peer Review Procedural Fairness Obligation Instance and the integrity of the peer-review institution itself.

This question emerged because the canonical analysis treats Engineer A's error acknowledgment and the Owner's peer-review right as parallel but independent obligations, never examining whether voluntary disclosure by Engineer A could modulate the ethical weight of either. The counterfactual forces a structural question about whether the public-safety warrant is purely objective-triggered by the existence of risk regardless of Engineer A's conduct-or whether it incorporates a professional-accountability dimension that voluntary disclosure can partially satisfy, thereby altering the ethical calculus around Engineer A's standing to object under the Peer Review Notification and Consent Obligation.

The Board concluded that III.7.a. imposes a direct notification requirement on Engineer B when reviewing a colleague's work for the same client, and that this obligation is not contingent on the Owner's cooperation or consent - Engineer B is the professional bound by the Code and therefore bears personal responsibility for ensuring the notification occurs.

The Board extended C1 by clarifying that Engineer B's duty is active and verificatory rather than passive and delegable - because the Code binds Engineer B as the professional actor, Engineer B must confirm that notification has actually occurred before commencing review, and failure to do so transforms Engineer B's participation into a direct violation of III.7.a. rather than merely a procedural oversight.

The Board determined that Engineer B's refusal of the Owner's covert instruction was not a breach of client loyalty but was in fact the precise conduct the faithful agent standard demands, because I.4. operates only within ethical limits - when an Owner's instruction requires violation of a colleague's procedural rights under III.7.a., that instruction falls outside the scope of legitimate client service and Engineer B's refusal is ethically mandatory rather than optional.

The Board concluded that Engineer A may not ethically object to the peer review, but C4 extends this by grounding the conclusion in Engineer A's independent affirmative duty under III.1.a. - an engineer who has produced known design errors and then refuses to cooperate with a corrective review is not merely exercising a procedural right but is actively violating the error acknowledgment norm and the public welfare obligation simultaneously, making non-cooperation a categorical ethical violation rather than a permissible professional choice.

The Board did not address this question, but C5 fills the gap by concluding that termination deployed specifically to avoid the notification obligation - rather than as a genuine exercise of the Owner's right to select engineers - is itself a procedurally impermissible act, and that Engineer B, upon learning of this intent, would bear an independent duty to decline the engagement because proceeding would make Engineer B an instrument of the very norm-circumvention that Engineer B's prior refusal of the covert instruction was designed to prevent.

The Board implicitly resolved Q6 and Q8 by establishing that the peer review confidentiality framework is not self-contained: if the Owner suppresses findings revealing structural defects, Engineer B's independent public safety obligation under I.1 activates an escalation duty to public authorities, because the Code's confidentiality provisions protect client information only up to the threshold where disclosure becomes necessary to protect the public.

The Board concluded that Engineer A may not ethically obstruct the peer review because the prior design errors in the first tower concretely activated the public safety interest under I.1, converting what might otherwise be a defensible professional objection into an ethically impermissible act of obstruction - and the Board explicitly limited this reasoning to cases where prior errors exist, preserving the possibility that objection could be defensible in error-free contexts.

The Board resolved Q1 and Q3 by holding that Engineer B's obligation to ensure notification under III.7.a is self-executing and unconditional: absent Owner agreement to notify, Engineer B's only ethical course was to decline the engagement entirely, because accepting a covert assignment constitutes an ethical violation at the moment of acceptance regardless of whether the review is ever conducted - though the Owner's subsequent agreement to notify cured the procedural defect before the violation was consummated.

The Board resolved Q4 by acknowledging that while the Owner's legal power to terminate is real, termination-as-substitution for notification is not ethically equivalent because it destroys rather than satisfies the protective purpose of III.7.a - and Engineer B, upon learning that termination was being contemplated as an evasion strategy, would be independently obligated to flag this concern to the Owner rather than passively facilitate the circumvention of a professional norm Engineer B is duty-bound to uphold.

The Board resolved Q5 and Q10 by holding that Engineer A's duty to disclose the first-tower design errors arose at the moment of awareness and was not contingent on any external trigger - and that the compounding effect of continuing to design the second tower while concealing known errors elevated the violation beyond mere passive concealment into active impairment of the Owner's safety-relevant decision-making, implicating both III.1.a and the paramount public safety obligation under I.1.

The board concluded that Engineer B bears an independent, non-delegable obligation to escalate confirmed design defects to public authorities if the Owner refuses to act, because the confidentiality protections that ordinarily govern client information cannot logically extend to concealing known structural hazards - to permit otherwise would allow the peer review process itself to function as a mechanism for suppressing safety findings, which the board identified as a structural gap in the original opinion requiring explicit closure.

The board concluded that Engineer B's refusal to comply with the Owner's secrecy instruction was not a breach of client loyalty but the only ethically correct response, because the Code's own language in I.4 subordinates faithful agency to ethical limits, and III.7.a's notification requirement constitutes precisely such a limit - the apparent tension dissolves once the internal hierarchy of the Code is properly applied rather than treated as a genuine conflict between co-equal duties.

The board concluded that the confidentiality principle and the public welfare paramount principle do not genuinely conflict in the peer review context because confidentiality protects client information from unauthorized external disclosure, not from the client's own authorized scrutiny - the Owner's consent to the review is both necessary and sufficient to remove the confidentiality barrier, and I.1 operates as an independent reinforcing principle ensuring that even a residual confidentiality claim would yield to confirmed structural safety risks.

The board concluded that Engineer A's dignity interest under III.1.f is substantially addressed by the notification requirement itself, and that once notification has occurred, Engineer A's refusal to consent framed as a dignity objection is not ethically sustainable - the dignity principle shields engineers from arbitrary, malicious, or procedurally unfair review, not from legitimate Owner-authorized review of work that has already demonstrated quality concerns, and an engineer with a prior error record designing a related structure has a materially constrained basis for dignity-grounded obstruction.

The board concluded that Engineer A's obligation to acknowledge design errors arose independently of and prior to any peer review, was not contingent on Owner demand, and could not be subordinated to client relationship preservation because doing so would harm rather than serve the client's genuine interests - the board further identified the original opinion's silence on this point as a gap, and determined that Engineer A's failure to proactively disclose known first-tower errors before the peer review was commissioned constitutes an independent ethical violation under a straightforward reading of III.1.a.

The board concluded that Engineer B's notification duty is unconditional and derives from two independent deontological grounds - professional courtesy norms (III.7.a and III.1.f) and public safety obligations (I.1) - such that the Owner's instruction to proceed covertly was not merely inadvisable but a request for categorically impermissible conduct that Engineer B was obligated to refuse as a matter of ethical duty rather than prudential judgment.

The board concluded that the demonstrated risk of replicating known structural design errors in the second tower provided a compelling and sufficient consequentialist justification for overriding Engineer A's refusal to consent, because the potential harm of structural failure - including injury or death - vastly exceeded in both kind and magnitude the harm of coerced professional review, which was primarily reputational and professionally bounded.

The board concluded that Engineer B's refusal to comply with the covert review instruction and insistence on notification as a precondition to engagement exemplified professional virtue - specifically practical wisdom, professional courage, and genuine collegial respect - because Engineer B maintained professional standards at personal professional and financial risk rather than taking the easier path of compliance, which is precisely the honorable conduct I.6 envisions.

The board concluded that Engineer A's prior acknowledgment obligation under III.1.a independently and categorically compelled cooperation with the peer review, because cooperation was the concrete professional mechanism for discharging that duty in context, and refusal therefore constituted not merely a separate ethical violation but a continuation and compounding of the original failure to acknowledge errors - a conclusion that held irrespective of whether the peer review would actually find additional errors.

The board concluded that had Engineer B conducted the review covertly, the findings would have been ethically compromised and practically unusable for adverse action against Engineer A, Engineer B would have incurred independent professional liability for the III.7.a violation, and the discovery of genuine safety defects would have created a secondary dilemma in which Engineer B held safety-critical information obtained through an impermissible process - a scenario that the proper notification path entirely avoided by preserving both procedural integrity and substantive usability.

The Board resolved Q16 by clarifying that its conclusion that Engineer A 'may not ethically object' was not a general rule but a public-safety-predicated one: the confirmed errors in the first tower were doing the decisive ethical work, and without that predicate the balance between Engineer A's professional autonomy and the Owner's peer review right would have been materially closer, requiring independent justification grounded in quality assurance rather than safety emergency.

The Board resolved Q17 and Q4 by holding that termination of Engineer A would not discharge Engineer B's notification obligation because that obligation protects the reviewed engineer's professional dignity and interests as a substantive norm - not a formality eliminable by removing the engineer from the project - and that a termination designed to avoid notification would raise independent ethical concerns about both the Owner's use of contractual power and Engineer B's complicity in undermining professional standards.

The Board resolved Q18 and Q5 by distinguishing between Engineer A's ethical standing (materially improved by proactive disclosure, demonstrating good faith under III.1.a) and the Owner's right to commission peer review (independently grounded in quality assurance and public safety, and therefore not extinguished by prior disclosure), concluding that voluntary acknowledgment would have made Engineer A's objection appear more as a procedural concern than concealment but would not have been sufficient to override the safety-predicated review right.

The Board resolved Q7, Q11, and Q13 by rejecting a balancing approach in favor of a sequential gate structure: Engineer B's Faithful Agent Obligation under I.4 operates only 'within ethical limits,' so the Owner's instruction to conduct a covert review was not a competing duty to be weighed against notification but rather a categorically impermissible instruction that fell outside the scope of faithful agency entirely, making Engineer B's refusal not a breach of client loyalty but the only ethically available path.

The Board resolved Q8, Q2, and Q12 by establishing a two-stage confidentiality architecture in which Public Welfare Paramount does not simply defeat confidentiality but restructures when and how it applies - mandatory transparency at the peer review initiation stage protects Engineer A's notification rights, while restored confidentiality at the conduct stage instrumentally facilitates the safety outcome by assuring Engineer A that findings will be used only for their intended purpose, with BER Case 96-8 confirming that public welfare sets an absolute ceiling above which no confidentiality norm can operate.

The board resolved the tension between Professional Dignity (P6, III.1.f) and Non-Obstruction of Peer Review (P8, III.7.a) by bifurcating dignity into a procedural stage and a substantive stage: dignity was fully honored by the notification requirement, but once notification occurred and the public safety basis was established through confirmed first-tower errors, Engineer A's dignity interest could no longer block the review. The board further reasoned that Engineer A's failure to proactively acknowledge errors under III.1.a (P5) did not merely weaken the dignity claim but affirmatively generated a competing obligation running in the opposite direction - requiring facilitation of accountability rather than obstruction of it - thereby converting Engineer A's refusal from a defensible professional stance into a categorical ethical violation.

Must Engineer B refuse to conduct the peer review without first ensuring Engineer A is notified of the planned review, and must Engineer B decline the engagement entirely if the Owner insists on covert review?

Must Engineer A cooperate with and refrain from obstructing the Owner's legitimately commissioned peer review of the second tower designs, particularly given that significant design errors were already discovered in Engineer A's first tower work?

Is the Owner obligated to ensure that the peer review of Engineer A's second tower designs is conducted through procedurally fair means, including notifying Engineer A before the review commences, rather than instructing Engineer B to conduct the review covertly?

Should Engineer B refuse the Owner's instruction to conduct a covert peer review and independently ensure Engineer A is notified as a precondition to engagement?

Should Engineer A cooperate with and actively facilitate the peer review of the second tower plans rather than refuse consent, given the confirmed design errors in the first tower and the public safety implications?

Should Engineer A proactively disclose the known design errors in the first tower to the Owner as an independent, self-executing obligation arising at the moment of awareness, irrespective of whether a peer review has been commissioned or the Owner has demanded disclosure?

Should Engineer B refuse the Owner's instruction to conduct a covert peer review and independently ensure that Engineer A is notified before commencing any review activity?

Should Engineer A cooperate with and refrain from obstructing the Owner-commissioned peer review of the second tower plans, given the confirmed design errors in the first tower and the public safety risk of replication?

Should Engineer B treat the peer review confidentiality framework as bounded by an independent public safety escalation obligation, such that Engineer B must report confirmed structural defects to public authorities if the Owner suppresses or declines to act on the findings?

Should Engineer B refuse to conduct a covert peer review and independently ensure that Engineer A is notified of the planned review before any engagement proceeds?

Should Engineer A cooperate with and actively facilitate the peer review of the second tower plans rather than refuse consent, given the known design errors in the first tower and the public safety risk of replication?

Should Engineer A proactively disclose the known design errors in the first tower to the Owner and, where safety code violations are implicated, escalate to relevant authorities, independent of and prior to any peer review process?

Should Engineer A acknowledge the known design errors and cooperate with the peer review of the second tower, or refuse consent and obstruct the review process?