Step 4: Full View

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

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.

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

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.

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.

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.

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.

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

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.

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.

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.

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

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

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.

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.

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.

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

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

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

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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