Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.
NSPE Code Provisions Referenced
Section I. Fundamental Canons 3 90 entities
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.
Section II. Rules of Practice 1 19 entities
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.
Section III. Professional Obligations 4 108 entities
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.
Cross-Case Connections
View ExtractionExplicit Board-Cited Precedents 3 Lineage Graph
Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.
Principle Established:
An engineer who conducted an independent external review of a public project may ethically participate in a design-build joint venture for that same project, so long as the agency approves and applicable conflict-of-interest laws are followed.
Citation Context:
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.
Principle Established:
A prior case addressed the ethical implications when an Owner refuses to advise the engineer whose work is being reviewed of the planned peer review.
Citation Context:
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.
Principle Established:
A peer reviewer who identifies potential violations of safety codes threatening public health, safety, and welfare must first seek resolution with the engineer being reviewed, and if unsuccessful, must inform appropriate authorities, notwithstanding any confidentiality agreement.
Citation Context:
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.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions
View ExtractionIs Engineer B ethically required to make certain that Engineer A is advised of the planned peer review?
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.
Is Engineer A ethically required to cooperate with the peer review of Engineer B?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
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?
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.
Decisions & Arguments
View ExtractionCausal-Normative Links 6
- Engineer A Non-Obstruction Peer Review Obligation Instance
- Non-Obstruction of Legitimate Peer Review Obligation
- Engineer A Non-Obstruction Peer Review Second Tower Refusal
- Engineer A Client Interest Alignment Peer Review Cooperation Second Tower
- Engineer A Public Safety Paramount Peer Review Cooperation Second Tower
- Engineer A Error Acknowledgment Responsibility Acceptance Second Tower
- Post-Error Peer Review Facilitation Obligation
- Engineer A Post-Error Peer Review Facilitation Obligation Instance
- Client Interest Alignment Peer Review Cooperation Obligation
- Owner Peer Review Procedural Fairness Obligation Instance
- Owner Peer Review Procedural Fairness Notification Engineer A
- Post-Error Peer Review Facilitation Obligation
- Peer Review Procedural Fairness Client Obligation
- Owner Peer Review Procedural Fairness Obligation Instance
- Peer Review Notification and Consent Obligation
- Owner Peer Review Procedural Fairness Notification Engineer A
- Engineer B Peer Review Notification Obligation Instance
- Engineer B Peer Review Notification Refusal Covert Assignment
- Engineer B Faithful Agent Obligation Within Ethical Limits Instance
- Peer Review Notification and Consent Obligation
- Engineer A Error Acknowledgment Obligation Instance
- Engineer A Post-Error Peer Review Facilitation Obligation Instance
- Engineer A Professional Accountability Peer Review Context Instance
- Engineer A Public Safety Paramount Peer Review Cooperation Second Tower
- Owner Peer Review Procedural Fairness Obligation Instance
- Peer Review Notification and Consent Obligation
- Owner Peer Review Procedural Fairness Notification Engineer A
Decision Points 13
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?
NSPE Code III.7.a prohibits an engineer from reviewing a colleague's work for the same client without the knowledge of that engineer, establishing notification as a categorical professional norm. The Faithful Agent Obligation under I.4 requires Engineer B to serve the Owner's interests, but only 'within ethical limits,' meaning client instructions that require violation of professional norms protecting third-party engineers fall outside the scope of lawful client service. The Peer Review Independence and Integrity principle further establishes that a covert review would likely be a fruitless exercise without Engineer A's cooperation. Engineer B's independent affirmative duty requires not merely passive reliance on the Owner's promise to notify but active verification that notification has occurred before commencing any review activity.
Uncertainty arises from whether the notification norm is a threshold condition precedent to engagement acceptance or merely a procedural obligation that can be satisfied after initial acceptance. If the Owner retains ultimate authority over notification timing and voluntarily agrees to notify Engineer A, it is unclear whether Engineer B's independent obligation is fully discharged by the Owner's promise or requires Engineer B's own verification. Additionally, the faithful agent obligation's scope is contested: if the Owner's covert instruction is characterized as a legitimate confidential business decision rather than an intent to deceive, the categorical force of the notification duty may be weakened.
The Owner retains Engineer B to peer review Engineer A's second tower designs after significant design errors were discovered in the first tower. The Owner instructs Engineer B not to disclose the review to Engineer A. Engineer B objects to conducting the review without advising Engineer A. The Owner ultimately agrees to notify Engineer A before the review proceeds.
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?
The Non-Obstruction of Legitimate Peer Review Obligation bars Engineer A from refusing consent to a legitimately commissioned peer review, particularly after known errors have been discovered, because the client's right to independent technical verification outweighs the engineer's interest in avoiding scrutiny. The Post-Error Peer Review Facilitation Obligation independently requires Engineer A to actively facilitate, or at minimum refrain from obstructing, any legitimately commissioned peer review of related work, given that prior errors create a heightened public safety interest in independent verification. The Error Acknowledgment and Corrective Disclosure Obligation under III.1.a requires Engineer A to acknowledge errors and not distort or alter the facts, and cooperation with peer review is the concrete professional mechanism through which that acknowledgment obligation is discharged in the context of ongoing design work for the same client. The Public Welfare Paramount principle under I.1 establishes that Engineer A's personal or reputational interests cannot override the public safety imperative created by confirmed design errors in a related structure.
Uncertainty is created by the absence of a formal peer review program agreement binding Engineer A, because without such a contractual or programmatic framework the warrant authorizing mandatory cooperation is less clearly established. Additionally, the categorical-violation conclusion is undermined if Engineer A can demonstrate that the error-acknowledgment obligation is satisfied by direct disclosure to the Owner and corrective redesign without peer review. The override justification also weakens if the Owner retains independent authority to commission a separate structural review without Engineer A's participation, because in that case the harm of unchecked defects may be addressable through alternative means. Finally, prior design errors diminish Engineer A's dignity objections only if those errors are causally connected to the specific review being refused.
Significant design errors were discovered in Engineer A's plans and designs for the first tower. The Owner commissions a peer review of Engineer A's second tower designs and retains Engineer B. Engineer A is notified of the planned peer review. Engineer A objects and refuses to consent to the peer review, blocking the process. The Owner must then select a post-refusal strategy to proceed.
Should the Owner notify Engineer A before commissioning the peer review of the second tower designs, or instruct Engineer B to conduct the review covertly without Engineer A's knowledge?
The Peer Review Procedural Fairness Client Obligation requires the Owner, as the commissioning party, to ensure that the peer review is conducted through procedurally fair means, including notifying Engineer A before the review commences, because covert peer review without the knowledge of the reviewed engineer undermines professional dignity, may compromise the integrity of the review process, and is inconsistent with the ethical treatment of licensed professionals whose reputations and livelihoods are implicated. The Covert Peer Review Prohibition Constraint derived from NSPE Code Section III.7.a and professional courtesy norms prohibits client instructions that direct the reviewing engineer to conduct the review covertly. The Owner's instruction to Engineer B to maintain secrecy falls outside the scope of legitimate client direction because it requires Engineer B to violate a professional norm protecting Engineer A's procedural rights. Additionally, termination of Engineer A as a workaround to the notification requirement would not constitute an ethically equivalent substitute for notification, because termination eliminates rather than satisfies Engineer A's right to be informed.
Uncertainty arises because the Owner's legal authority to manage the engagement, including decisions about timing and confidentiality, may be characterized as a legitimate business prerogative rather than an ethical violation, particularly if the Owner's motivation for secrecy was to avoid tipping off Engineer A before the review could be properly scoped. If the Owner voluntarily agrees to notify Engineer A after Engineer B's objection, it is unclear whether the initial covert instruction itself constitutes an independent ethical violation by the Owner or merely a corrected procedural misstep. The perverse incentive created by the Owner's option to terminate Engineer A as a substitute for notification further complicates the analysis, because if termination is treated as a permissible workaround, the protective purpose of the notification norm is effectively optional for any Owner willing to pay the transactional cost of dismissal.
The Owner decides to obtain a peer review of Engineer A's second tower plans and designs following the discovery of significant design errors in the first tower. The Owner retains Engineer B but instructs Engineer B to conduct the peer review without letting Engineer A know. Engineer B objects to the covert instruction. The Owner is thereby forced into transparency and ultimately consents to notifying Engineer A before the review proceeds.
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?
The Faithful Agent Obligation (I.4) requires Engineer B to serve the Owner's interests, but explicitly only 'within ethical limits.' The Peer Review Notification and Consent Obligation (III.7.a) independently requires that Engineer A be informed when their work is under review. The Professional Dignity principle (III.1.f) protects Engineer A's right to know their work is being scrutinized. These obligations converge to make notification a structural precondition to legitimate engagement, not a waivable procedural preference. The Faithful Agent Obligation does not authorize Engineer B to become an instrument of conduct that violates a third-party engineer's procedural rights.
Uncertainty arises from whether the faithful agent obligation categorically yields whenever a client instruction conflicts with any professional standard, or only when the conflict is sufficiently serious. A further rebuttal condition is that if the Owner's covert instruction was motivated by a legitimate confidentiality concern rather than intent to deceive, Engineer B's refusal might appear disproportionate. Additionally, if the Owner retains ultimate authority over notification timing and voluntarily agrees to notify, it is unclear whether Engineer B's independent obligation is fully discharged by the Owner's promise alone or requires Engineer B to verify actual notification before commencing.
Owner retains Engineer B covertly to peer review Engineer A's second tower plans after design errors were discovered in the first tower. Owner explicitly instructs Engineer B to conduct the review without notifying Engineer A. Engineer B refuses the covert instruction and conditions engagement on Owner's agreement to notify Engineer A. Owner ultimately consents to notification.
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?
The Non-Obstruction of Legitimate Peer Review Obligation bars Engineer A from blocking a properly notified, Owner-authorized review. The Client Interest Alignment and Post-Error Peer Review Facilitation Obligation requires Engineer A to actively support review mechanisms that protect the client's project from replication of known errors. The Public Welfare Paramount principle (I.1) independently compels cooperation because confirmed first-tower errors create a concrete safety risk of replication in the second tower. The Error Acknowledgment Obligation (III.1.a) independently requires Engineer A to acknowledge errors and not obstruct the professional accountability process through which those errors and their potential replication would be identified. Engineer A's professional dignity interest under III.1.f is substantially addressed by the notification already provided and does not extend to a substantive veto over Owner-authorized, properly notified review.
Uncertainty is created by the absence of a formal peer review program agreement binding Engineer A, because without such a contractual or programmatic framework the warrant authorizing mandatory cooperation is less clear. A further rebuttal condition is that if Engineer A had proactively disclosed the first-tower errors and taken corrective action, the error acknowledgment obligation might be partially satisfied without requiring peer review cooperation. The categorical-violation conclusion is also weakened if Engineer A can demonstrate that the error-acknowledgment obligation is satisfied by direct disclosure and corrective redesign without peer review participation.
Design errors were discovered in Engineer A's first tower plans. Engineer A is simultaneously designing the second tower for the same Owner. Engineer A is notified of the planned peer review of the second tower plans. Engineer A refuses to consent to the peer review, blocking the process. The Owner must then select a post-refusal strategy. Engineer A has not proactively disclosed the first-tower errors to the Owner.
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?
Code provision III.1.a requires engineers to acknowledge their errors and not distort or alter the facts: this obligation is self-executing and triggered by Engineer A's own knowledge, not by external review or client demand. The obligation arose at the moment Engineer A became aware of the first-tower errors, independent of whether a peer review was ever commissioned. Continuing professional work on the second tower while withholding known material safety-relevant information compounds the ethical violation: Engineer A is not merely passively concealing past errors but actively continuing work for the same client on a related structure while impeding the Owner's informed decision-making. Client loyalty under I.4 cannot justify concealing material design errors from the very client whose project is affected, because doing so harms rather than serves the client's genuine interests. The public safety obligation under I.1 further reinforces disclosure because the Owner's ability to protect the public through informed project decisions is directly impaired.
Uncertainty is created by the absence of a clear threshold in the NSPE Code specifying when known design errors rise to the level of 'endangerment to public safety' sufficient to trigger mandatory proactive disclosure versus permitting internal correction without client notification. A further rebuttal condition is that the error acknowledgment obligation might be satisfied by corrective redesign and internal remediation without formal disclosure to the Owner, particularly if the errors were caught and corrected before any structural harm occurred. The client loyalty principle might also be invoked to argue that disclosure timing is within Engineer A's professional judgment when the errors have not yet caused harm and corrective action is underway.
Engineer A discovers or is aware of significant design errors in the first tower plans. Engineer A continues designing the second tower for the same Owner without proactively disclosing the first-tower errors. The Owner has not yet demanded disclosure. A peer review is subsequently commissioned by the Owner. Engineer A refuses to cooperate with the peer review. The Owner's ability to make informed decisions about the second tower is directly impaired by Engineer A's non-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?
III.7.a imposes a direct notification requirement on Engineer B when reviewing a colleague's work for the same client. The Faithful Agent Obligation under I.4 requires Engineer B to serve the Owner's interests, but only 'within ethical limits.' The Peer Review Notification Obligation protects Engineer A's professional dignity and procedural rights under III.1.f. Notification is a structural precondition to the legitimacy of the peer review itself, not a waivable procedural preference. Engineer B's independent affirmative duty requires verification that notification has actually occurred before commencing review, not mere reliance on the Owner's promise.
Uncertainty arises if the Owner's covert instruction is characterized as a legitimate confidential business decision that does not itself endanger the public, potentially weakening the categorical force of the notification duty. Additional uncertainty exists as to whether Engineer B's obligation is fully discharged once the Owner voluntarily agrees to notify, or whether Engineer B must independently verify that notification has in fact occurred. The ambiguity of whether the notification norm is a threshold condition precedent to engagement acceptance or merely a procedural obligation satisfiable after acceptance also creates uncertainty.
The Owner retains Engineer B covertly to review Engineer A's work without notifying Engineer A. Engineer B's notification obligation is activated by the existence of design errors in the first tower and the planned review of second tower plans. The Owner initially instructs secrecy, but Engineer B refuses the covert assignment, after which the Owner consents to notifying Engineer A.
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?
The Non-Obstruction of Legitimate Peer Review Obligation bars Engineer A from blocking a properly notified, Owner-authorized review. The Error Acknowledgment and Corrective Disclosure Obligation under III.1.a independently compels Engineer A not merely to tolerate but to actively facilitate the review, because cooperation is the concrete professional mechanism for discharging the acknowledgment duty in the context of ongoing design work for the same client. The Public Welfare Paramount principle under I.1 overrides Engineer A's professional autonomy interest when confirmed prior errors create a concrete risk of replication in a second structure. The Client Interest Alignment Peer Review Cooperation Obligation further supports cooperation as serving the Owner's genuine interests. Professional dignity under III.1.f is a procedural entitlement satisfied by notification, not a substantive veto over Owner-authorized review.
Uncertainty is created by the absence of a formal peer review program agreement binding Engineer A, because without such a contractual or programmatic framework the warrant authorizing mandatory cooperation is weakened. The categorical-violation conclusion is also undermined if Engineer A can demonstrate that the error-acknowledgment obligation is satisfied by direct disclosure to the Owner and corrective redesign without peer review. Additionally, the prior design errors diminish Engineer A's dignity objections only if those errors are causally connected to the specific review being refused, leaving open whether errors in the first tower sufficiently implicate the second tower review.
Design errors are discovered in Engineer A's first tower work. The second tower plans are implicated as potentially replicating those errors. Engineer A is properly notified of the planned peer review. Engineer A refuses to consent to the peer review, blocking the process. The Owner must then select a post-refusal strategy. Engineer A has created flawed plans and has not proactively disclosed the known errors to the Owner.
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?
The Public Safety Paramount obligation under I.1 places safety above all other considerations and supersedes both confidentiality obligations under II.1.c and III.4 and the faithful agent obligation under I.4 when genuine structural risks exist. The Peer Review Safety Code Violation Escalation Obligation, reinforced by BER Case 96-8 precedent, establishes that even within a confidential peer review framework, safety code violations trigger escalation obligations. Peer review confidentiality protects the content of proceedings from unauthorized third-party disclosure but does not shield confirmed public safety hazards from required reporting. Engineer B's obligations do not terminate with delivery of the report to the Owner, the engagement carries a potential obligation to escalate findings over the Owner's objection if public safety demands it.
Uncertainty arises because the Owner's authority over the engagement scope may limit Engineer B's independent reporting duty, and this rebuttal condition may or may not be overridden by the public welfare paramount principle depending on the severity and imminence of the identified defects. The confidentiality-yields-to-safety conclusion is further weakened if the safety risk is not sufficiently specific, imminent, and non-speculative, leaving open the contested question of when design defects rise to the level of endangerment sufficient to trigger mandatory proactive reporting. The threshold in the NSPE Code for when known design errors constitute a public safety hazard requiring escalation is not clearly defined.
Design errors are discovered in Engineer A's first tower work and the second tower plans are implicated. Engineer A creates flawed plans and refuses peer review consent, blocking the process. The Owner retains Engineer B covertly and Engineer B is aware of the known design defects. The peer review confidentiality framework is in place, but the Owner may decline to act on findings that confirm structural defects posing public safety risks.
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?
The Peer Review Notification and Consent Obligation (III.7.a) requires Engineer B to ensure Engineer A is informed before any review of Engineer A's work proceeds: this is a structural precondition to the legitimacy of the review, not a waivable procedural courtesy. The Faithful Agent Obligation (I.4) requires Engineer B to serve the Owner's interests, but only 'within ethical limits,' meaning client instructions that require violation of a peer professional's procedural rights fall outside the scope of lawful client service. The Professional Dignity principle (III.1.f) independently bars covert review as a mode of professional conduct. The Peer Review Independence and Integrity principle requires that Engineer B not become an instrument of a process designed to circumvent a colleague's right to notice.
Uncertainty arises from whether the notification norm is a threshold condition precedent to engagement acceptance or merely a procedural obligation satisfiable after initial acceptance. If the Owner's instruction can be characterized as a legitimate confidential business decision that does not itself endanger the public, the faithful agent duty might be argued to permit provisional acceptance pending notification. Additionally, if the Owner voluntarily agrees to notify Engineer A, it is unclear whether Engineer B's independent obligation is fully discharged by reliance on that promise or whether Engineer B must independently verify that notification has actually occurred before commencing review.
The Owner retains Engineer B to conduct a peer review of Engineer A's second tower plans without notifying Engineer A, explicitly instructing secrecy. Design errors have already been discovered in Engineer A's first tower work, and the second tower plans are implicated. Engineer B's notification obligation is activated by the covert instruction. Engineer B refuses the covert engagement and conditions participation on the Owner agreeing to notify Engineer A, which the Owner ultimately accepts.
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?
The Public Welfare Paramount principle (I.1) requires that Engineer A not obstruct a review designed to prevent replication of known structural design errors in a second occupied structure, because the risk of harm to the public from unchecked defects vastly outweighs Engineer A's professional autonomy interest in avoiding scrutiny. The Non-Obstruction of Legitimate Peer Review Obligation bars Engineer A from using a consent refusal to block an Owner-authorized, properly notified review. The Error Acknowledgment and Corrective Disclosure Obligation (III.1.a) independently compels Engineer A to facilitate rather than obstruct the review, because cooperation is the concrete professional mechanism through which the acknowledgment duty is discharged in the context of ongoing design work for the same client. The Client Interest Alignment principle further supports cooperation, as the Owner's genuine interest in quality assurance is served by the review. Professional Dignity (III.1.f) is substantially addressed by the notification already provided and does not extend to a substantive veto over legitimate, properly initiated review.
Uncertainty is created by the absence of a formal peer review program agreement binding Engineer A: without a contractual or programmatic framework, the warrant authorizing mandatory cooperation is weakened. Engineer A's dignity-based objection retains some force if the prior errors are not causally connected to the specific review being refused. The override justification also weakens if the Owner retains independent authority to commission a separate structural review without Engineer A's participation, reducing the necessity of coercing Engineer A's consent. Additionally, if Engineer A had proactively disclosed the first-tower errors before the review was commissioned, Engineer A's ethical standing to raise procedural objections would have been materially stronger, though still insufficient to override the Owner's right to commission the review.
Engineer A has been notified of the planned peer review of the second tower plans. Design errors have been discovered in Engineer A's first tower work, and the second tower plans are implicated as potentially containing replicated errors. Engineer A refuses to consent to the peer review, blocking the process. The Owner must then select a post-refusal strategy. Engineer A is simultaneously continuing design work on the second tower for the same client while withholding acknowledgment of the first tower errors.
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?
The Error Acknowledgment and Corrective Disclosure Obligation (III.1.a) is self-executing: it is triggered by Engineer A's own knowledge of the errors, not by the initiation of external review, client demand, or peer review commissioning. Engineer A's duty to disclose the first-tower errors to the Owner arose at the moment Engineer A became aware of those errors. Continuing professional work on a related structure while withholding known material safety-relevant information compounds the ethical violation: Engineer A is not merely passively concealing past errors but actively continuing work for the same client on a related structure while impairing the Owner's informed decision-making. The Public Welfare Paramount principle (I.1) independently requires escalation to relevant authorities when safety code violations are confirmed and the Owner fails to act, as established by BER Case 96-8. Client loyalty under I.4 cannot justify concealing material design errors from the very client whose project is affected, because doing so harms rather than serves the client's genuine interests.
Uncertainty is created by the absence of a clear threshold in the NSPE Code specifying when known design errors rise to the level of 'endangerment to public safety' sufficient to trigger mandatory proactive disclosure versus permitting internal correction without formal notification. The error acknowledgment obligation may be argued to be satisfied by direct corrective redesign without formal disclosure if the errors are remediated before they cause harm. The escalation obligation under BER 96-8 is conditioned on the safety risk being sufficiently specific, imminent, and non-speculative, leaving open whether design defects that have not yet caused observable harm meet this threshold. Additionally, Engineer A's post-review participation in design-build arrangements under BER 18-10 precedent may be conditioned on the outcome of the review rather than triggering independent pre-review disclosure obligations.
Engineer A has discovered significant design errors in the first tower. The second tower plans are implicated as potentially containing replicated errors. Engineer A continues design work on the second tower for the same client without proactively disclosing the first tower errors to the Owner. The peer review process is subsequently blocked by Engineer A's refusal to consent. Engineer A's non-disclosure directly impairs the Owner's ability to make informed decisions about the second tower. Where safety code violations are confirmed, BER Case 96-8 precedent establishes an escalation obligation to relevant authorities.
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?
III.1.a imposes a self-executing obligation on Engineer A to acknowledge errors and not distort or alter the facts: triggered by Engineer A's own knowledge, not by external demand. The Non-Obstruction of Legitimate Peer Review principle bars Engineer A from blocking a properly notified, Owner-authorized review. The Public Welfare Paramount obligation under I.1 independently compels cooperation because confirmed first-tower errors create a concrete risk of replication in the second structure. The Client Interest Alignment obligation further requires Engineer A to facilitate review that protects the Owner's project from defective design. Refusing peer review simultaneously violates III.1.a (error acknowledgment), the non-obstruction principle, and I.1 (public safety paramount), compounding the original design failure.
Uncertainty arises because the error acknowledgment obligation under III.1.a may be satisfied by direct disclosure to the Owner and corrective redesign without requiring submission to peer review, leaving open whether peer review cooperation is independently mandated or merely one permissible mechanism for discharging the acknowledgment duty. Additionally, the non-obstruction principle's force depends on whether a formal peer review program agreement binds Engineer A; absent such a contractual or programmatic framework, the warrant authorizing mandatory cooperation is weakened. The categorical-violation conclusion is also contested if Engineer A can demonstrate that the first-tower errors are not causally connected to the specific second-tower work being reviewed.
Design errors were discovered in Engineer A's first tower work. The second tower plans are implicated as potentially replicating those errors. Engineer A was notified of the planned peer review, refused consent, and thereby blocked the peer review process. Engineer A continues designing the second tower for the same client while the errors in the first tower remain unacknowledged and undisclosed.
Event Timeline
Causal Flow
- Engineer A Creates Flawed Plans Owner Retains Engineer B Covertly
- Owner Retains Engineer B Covertly Engineer B Refuses Covert Review
- Engineer B Refuses Covert Review Owner Consents to Notifying Engineer A
- Owner Consents to Notifying Engineer A Engineer A Refuses Peer Review Consent
- Engineer A Refuses Peer Review Consent Owner_Selects_Post-Refusal_Strategy
- Owner_Selects_Post-Refusal_Strategy Design Errors Discovered
Opening Context
View ExtractionYou are Engineer A, a licensed structural engineer who designed two mirror-image commercial towers for the same owner, with construction scheduled two years apart. During construction of the first tower, several significant design errors were discovered in your plans. The owner has now retained Engineer B to conduct a peer review of your designs for the second tower. Engineer B has raised concerns about proceeding without notifying you, and the owner has since informed you of the planned review. You have refused to consent to the peer review. The choices you make regarding the review, your obligations to the owner, and the safety implications of the known design errors will define how this situation unfolds.
Characters (8)
An engineering firm whose work was subjected to formal peer review under an organized program, with identified safety code violations triggering mandatory collegial discussion and potential regulatory reporting.
- Primarily motivated by protecting firm reputation and project continuity, while ultimately subject to the corrective mechanisms built into the peer review program to ensure public safety compliance.
- Motivated by contractual confidentiality commitments balanced against an overriding duty to public safety, navigating the tension between program loyalty and the ethical imperative to prevent harm.
- Motivated by adherence to professional ethical standards and collegial respect, recognizing that conducting a secret review would undermine trust, due process, and the integrity of the peer review process itself.
The original design engineer for both towers whose work contained significant errors discovered during construction, and who actively resisted the peer review process for the second tower rather than engaging transparently.
- Motivated by self-protection of professional reputation and liability concerns, with refusal to consent to peer review suggesting prioritization of personal interests over public safety and project integrity.
In BER Case 96-8 precedent, Engineer B's firm was the subject of peer review by Engineer A under an organized program; Engineer A identified potential safety code violations in Engineer B's work, triggering collegial discussion obligations and potential authority reporting.
Prepared original plans and designs for both towers; significant design errors were discovered during construction of the first tower; refused to consent to peer review of second tower designs
Developing a two-tower site; discovered design errors in first tower; commissioned peer review of second tower designs; initially instructed Engineer B to conduct review without notifying Engineer A; reluctantly consented to notification after Engineer B's objection
Original designer of the project whose work contains known design defects and who is subject to a peer review initiated by the Owner; initially the subject of an instruction to keep the review confidential from them, but ultimately notified; bears ethical obligation to cooperate fully with Engineer B's peer review.
Peer reviewer retained by Owner to review Engineer A's design work; correctly declined the assignment when initially instructed not to disclose the review to Engineer A; proceeded after Owner agreed to notify Engineer A; bears obligations of thoroughness, objectivity, and public safety reporting.
In BER Case 18-10 precedent, Engineer A served as lead engineer on an independent external review of an agency project and subsequently participated in a design-build joint venture RFP for the same project; BER concluded participation was not unethical provided agency approval and legal compliance.
Tension between Peer Review Notification and Consent Obligation and Covert Peer Review Prohibition Constraint
Tension between Owner Peer Review Procedural Fairness Obligation Instance and Covert Peer Review Prohibition Constraint
Tension between Engineer B Faithful Agent Obligation Within Ethical Limits Instance and Covert Peer Review Prohibition Constraint
Tension between Engineer A Post-Error Peer Review Facilitation Obligation Instance and Non-Obstruction of Legitimate Peer Review Obligation
Tension between Engineer A Error Acknowledgment Obligation Instance and Error Acknowledgment and Corrective Disclosure Obligation
Tension between Peer Review Notification and Consent Obligation and Covert Peer Review Prohibition Constraint
Tension between Non-Obstruction of Legitimate Peer Review Obligation and Engineer A Non-Obstruction Peer Review Second Tower Refusal
Tension between Peer Review Safety Code Violation Escalation Obligation and Peer Review Confidentiality Agreement Cooperation Obligation
Tension between Owner Peer Review Procedural Fairness Notification Engineer A and Covert Peer Review Prohibition Constraint
Tension between Engineer A Public Safety Paramount Peer Review Cooperation Second Tower and Non-Obstruction of Legitimate Peer Review Obligation
Tension between Engineer A BER 96-8 Peer Review Safety Code Violation Escalation and Post-Error Peer Review Facilitation Obligation
Tension between Engineer A Error Acknowledgment and Peer Review Cooperation Obligation and Non-Obstruction of Legitimate Peer Review
Engineer B is obligated to notify Engineer A and obtain consent before conducting peer review, yet the public safety constraint permits or requires proceeding with review even when consent is withheld. When Engineer A refuses consent, Engineer B faces a genuine dilemma: honoring the procedural consent norm respects professional autonomy but may allow unsafe designs to persist, while proceeding without consent violates Engineer A's rights but protects the public. These duties pull in opposite directions with no costless resolution.
Engineer B has agreed to maintain confidentiality of findings as a condition of the peer review program, yet the safety override constraint mandates disclosure or escalation when code violations posing public risk are discovered. If the review uncovers serious safety deficiencies, honoring the confidentiality agreement suppresses information the public needs, while disclosing it breaches a binding professional commitment. This is a classic conflict between promise-keeping and harm-prevention, with third-party public safety as the decisive but procedurally constrained interest.
Having made a prior design error, Engineer A carries a heightened obligation to facilitate peer review as a corrective accountability measure. Yet the consent refusal override constraint acknowledges Engineer A's right to withhold consent to review. These two norms conflict because Engineer A's self-protective refusal of consent is procedurally permissible but morally compromised by the prior error context: exercising the refusal right obstructs the very corrective mechanism that professional accountability demands, creating a tension between individual procedural rights and post-error remedial duties.
Opening States (10)
Key Takeaways
- Transparency is a non-negotiable prerequisite for ethical peer review, requiring that the engineer being reviewed must be notified before the process begins.
- An engineer's duty to serve as a faithful agent to an owner does not extend to executing procedurally unfair or covert professional evaluations of colleagues.
- The resolution transfers the ethical burden onto Engineer B as the active party, establishing that the person conducting or facilitating a review bears responsibility for ensuring due process notification.