Step 4: Review
Review extracted entities and commit to OntServe
Commit to OntServe
Phase 2A: Code Provisions
code provision reference 8
Hold paramount the safety, health, and welfare of the public.
DetailsAct for each employer or client as faithful agents or trustees.
DetailsConduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession.
DetailsEngineers 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.
DetailsEngineers shall acknowledge their errors and shall not distort or alter the facts.
DetailsEngineers shall treat all persons with dignity, respect, fairness and without discrimination.
DetailsEngineers 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.
DetailsEngineers 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.
DetailsPhase 2B: Precedent Cases
precedent case reference 3
The Board cited this case to illustrate how the BER has previously addressed peer review issues, specifically regarding a lead engineer on an independent external review who later sought to participate in a design-build joint venture for the same project.
DetailsThe Board cited this case to illustrate the obligations of a peer reviewer who discovers potential safety code violations during a review, establishing that the reviewer must discuss concerns with the reviewed engineer and, if unresolved, inform appropriate authorities.
DetailsThe Board cited this case parenthetically to reference a prior situation in which the Owner refused to advise the engineer of the planned peer review, contrasting it with the present case where the Owner reluctantly agreed to notify Engineer A.
DetailsPhase 2C: Questions & Conclusions
ethical conclusion 20
Engineer B is ethically required to make certain that Engineer A is advised of the planned peer review.
DetailsBeyond the Board's finding that Engineer B is ethically required to notify Engineer A of the planned peer review, the notification obligation is not merely a matter of professional courtesy but is structurally grounded in Code provision III.7.a, which conditions peer review of another engineer's work on that engineer's knowledge. This means the notification duty is not waivable by the Owner as a client instruction, because it exists independently of the client relationship as a constraint on the legitimacy of the peer review engagement itself. Engineer B's refusal to proceed covertly was therefore not an optional exercise of professional discretion but a categorical ethical requirement: a covert review would have been procedurally invalid under the Code regardless of its technical quality or ultimate benefit to public safety. The Owner's consent to notification, while practically necessary to allow the engagement to proceed, did not create the notification duty—it merely removed the Owner's obstruction of a pre-existing professional obligation.
DetailsThe Board's conclusion that Engineer B must ensure Engineer A is notified implicitly resolves the tension between client loyalty and collegial transparency in favor of the latter, but the Board did not fully articulate the limiting principle governing that resolution. The resolution is best understood as follows: Engineer B's duty of loyalty to the Owner under provision I.4 extends only to lawful and ethically permissible instructions. An instruction to conduct a covert peer review falls outside the scope of permissible client direction because it would require Engineer B to act deceptively toward a fellow professional in a manner expressly prohibited by III.7.a. This is not a case where two legitimate ethical duties conflict and must be balanced—rather, the Owner's instruction to maintain secrecy was itself ethically impermissible, meaning no genuine tension existed once the instruction's illegitimacy is recognized. Engineer B's obligation was therefore not to balance competing duties but to decline an instruction that exceeded the Owner's authority to give. This framing also answers the implicit question of whether Engineer B would have been required to withdraw entirely had the Owner refused to consent to notification: yes, withdrawal would have been the only ethically available option, because proceeding covertly would have made Engineer B complicit in a violation of III.7.a.
DetailsThe Board's explicit conclusions address only Engineer B's notification duty and Engineer A's cooperation duty, but the case facts generate a third, unaddressed ethical dimension: Engineer B's independent obligation regarding the known design defects in the first tower. Once Engineer B became aware—through the engagement itself—of significant design errors in the first tower that posed a risk to public safety, provision I.1's paramount duty to protect public health, safety, and welfare was triggered independently of the peer review question. If the Owner takes no corrective action on the first tower's defects, Engineer B's confidentiality obligations under II.1.c and III.4 do not extinguish the safety disclosure obligation, because those provisions are subordinate to the paramount safety duty under I.1. The Board's silence on this point leaves a critical gap: Engineer B's ethical responsibilities do not terminate at the boundary of the peer review engagement, and the blocking of the second tower's peer review by Engineer A's refusal makes Engineer B's safety escalation obligation regarding the first tower more urgent, not less. Engineer B should be understood as ethically required to report the first tower's known defects to appropriate authorities if the Owner fails to act, regardless of how the peer review dispute is ultimately resolved.
DetailsEngineer A's refusal to consent to the peer review, while superficially framed as a defense of professional integrity, is ethically untenable given the specific factual context: significant design errors had already been confirmed in the structurally identical first tower. Under provision III.1.a, engineers are obligated to acknowledge their errors and not distort or alter the facts. Engineer A's refusal to cooperate with a review of the second tower's plans—which share a mirror-image design with a tower already known to contain significant defects—functions in practice as a suppression of facts material to public safety, even if Engineer A frames it as a procedural objection to unsolicited oversight. The ethical weight of Engineer A's cooperation duty is therefore not symmetrical with a routine peer review situation: the pre-existing confirmed defects transform the peer review from an optional quality assurance measure into a public safety necessity, and Engineer A's resistance to it implicates the paramount duty under I.1 in addition to the acknowledgment duty under III.1.a. The Board's implicit conclusion that Engineer A is ethically required to cooperate is thus supported not only by general professional accountability norms but by the specific safety stakes created by the known defects in the first tower.
DetailsThe Board's framing places the notification duty primarily on Engineer B, but the case facts also implicate an independent ethical obligation on the Owner's part that the Board did not address. The Owner, as the party who commissioned both the original design and the peer review, possessed full knowledge of the design defects in the first tower and had the most direct authority and practical ability to notify Engineer A of the planned review. By instructing Engineer B to conduct the review covertly, the Owner attempted to use Engineer B as an instrument to circumvent a professional norm that exists to protect the integrity of the engineering review process. This instrumentalization of Engineer B is itself ethically problematic: the Owner's instruction was not merely a business preference but an attempt to induce Engineer B to violate a Code provision. The Board's conclusion that Engineer B bears the notification duty should therefore be understood as a floor, not a ceiling—the Owner bears a concurrent and independent obligation not to instruct engineers to act in violation of their professional codes, and the Owner's eventual consent to notification, while necessary, does not fully discharge the ethical concern raised by the initial covert instruction.
DetailsIn response to Q101: If Owner had insisted on a covert review and refused to consent to notifying Engineer A, Engineer B would have been ethically required to withdraw from the engagement entirely rather than proceed. Code provision III.7.a. conditions the permissibility of reviewing another engineer's work for the same client on the original engineer's knowledge of the review. This is not a procedural preference but a threshold ethical requirement. Because the notification condition is non-waivable from Engineer B's perspective—Engineer B cannot unilaterally satisfy it without Owner's cooperation—and because proceeding covertly would violate the non-deception norm embedded in III.7.a., the only ethically consistent exit is withdrawal. Continuing under a covert mandate would make Engineer B complicit in deceiving Engineer A and would undermine the integrity of the peer review process itself, regardless of the technical quality of the review produced.
DetailsIn response to Q102: Engineer A's continued involvement on the second tower project despite confirmed design defects in the structurally identical first tower raises an independent ethical concern separate from the peer review dispute. Code provision III.1.a. requires engineers to acknowledge their errors and not distort or alter the facts. Engineer A's refusal to cooperate with the peer review, when combined with the known existence of significant design errors in the first tower, suggests a failure to acknowledge those errors in a professionally meaningful way. If Engineer A is continuing to design the second tower without disclosing the nature and scope of the first tower's defects to the Owner or without proactively seeking corrective review, that posture may itself constitute a breach of the duty to acknowledge errors and a potential threat to public safety under Code provision I.1. The peer review dispute and Engineer A's fitness to continue on the project are therefore analytically distinct but ethically interrelated concerns.
DetailsIn response to Q103: Engineer B bears an independent safety disclosure obligation that survives and transcends the peer review engagement itself. If Owner takes no corrective action after design defects in the first tower are discovered—and particularly if the second tower's review is blocked—Engineer B's paramount duty under Code provision I.1. to hold public safety above all other considerations would require escalation beyond the client relationship. This obligation is not extinguished by confidentiality provisions under II.1.c. or III.4., because those provisions do not shield information whose suppression would endanger public health, safety, or welfare. Engineer B would be ethically required to report the known defects to relevant authorities if Owner fails to act, even if doing so breaches client confidentiality. The confidentiality constraint yields to the safety override, and Engineer B's capability for safety disclosure escalation must be exercised at the point where inaction creates foreseeable public risk.
DetailsIn response to Q104: The Board's framing of the notification duty primarily as Engineer B's responsibility is analytically incomplete. Owner, as the party who commissioned the peer review and who possesses the direct contractual relationship with Engineer A, bears an independent and arguably primary ethical obligation to notify Engineer A. The Board's conclusion correctly identifies Engineer B's duty to ensure notification occurs, but this should not obscure that Owner's instruction to conduct a covert review was itself ethically impermissible. Owner's authority as client does not extend to directing engineers to deceive fellow professionals. Framing the notification duty solely through Engineer B's lens risks implying that Owner's covert instruction was merely inconvenient rather than independently wrongful. A complete ethical analysis would recognize that Owner violated a duty of fair dealing toward Engineer A by initially instructing secrecy, and that Engineer B's insistence on notification was a corrective response to Owner's own ethical lapse.
DetailsIn response to Q201: When Owner explicitly instructs secrecy, the tension between Engineer B's transparency obligation toward Engineer A and Engineer B's duty of loyalty toward Owner as client is resolved in favor of transparency, and the resolution is not close. Code provision I.4. requires Engineer B to act as a faithful agent or trustee of Owner, but faithful agency does not encompass facilitating deception of third parties, particularly fellow licensed professionals whose work is under review. Code provision III.7.a. establishes notification of the original engineer as a precondition for the permissibility of the peer review itself, meaning that Owner's instruction to proceed covertly is an instruction to engage in an ethically impermissible act. Engineer B's loyalty duty to Owner is bounded by the limits of what Owner may ethically instruct. Because Owner cannot ethically instruct a covert review, Engineer B's compliance with that instruction would not constitute faithful agency but rather complicity in a professional ethics violation. Transparency toward Engineer A therefore overrides client loyalty in this specific configuration.
DetailsIn response to Q202: Engineer A's invocation of professional integrity as grounds for resisting the peer review is ethically untenable given the confirmed existence of significant design defects in the first tower. Code provision I.1. establishes that public safety is paramount and overrides individual professional prerogatives. Engineer A's resistance to the peer review, framed as a matter of professional integrity or autonomy, cannot be sustained when the factual predicate for the review—known design errors in a structurally identical predecessor project—directly implicates public safety in the second tower. Professional integrity, properly understood, requires acknowledgment of errors under III.1.a. and cooperation with legitimate oversight mechanisms, not resistance to them. Engineer A's refusal therefore inverts the meaning of professional integrity: genuine professional integrity in this context would manifest as welcoming, not obstructing, independent review of work that may carry forward the same defects that endangered the first tower.
DetailsIn response to Q301 and Q304: From a deontological perspective, Engineer B's conduct exemplifies categorical compliance with professional transparency duties. By refusing to conduct a covert review and insisting on notifying Engineer A before proceeding, Engineer B treated the notification requirement under III.7.a. as a non-negotiable duty rather than a cost-benefit calculation. This is precisely the structure of deontological reasoning: the wrongness of the covert review was not contingent on whether it would have produced good outcomes, but on the nature of the act itself—deceiving a fellow professional whose work is under scrutiny. From a virtue ethics standpoint, Engineer B simultaneously demonstrated integrity toward Engineer A, professional courage in resisting Owner's instruction, and collegial respect by insisting that Engineer A be treated as a professional entitled to know of the review. These virtues operated in concert rather than in tension, suggesting that the ethically virtuous path and the deontologically required path converged in Engineer B's conduct.
DetailsIn response to Q401: If Engineer B had complied with Owner's instruction and conducted the peer review covertly, Engineer B would have violated professional ethics even if the review was technically competent and even if it ultimately served public safety by identifying defects. The ethical violation would be independent of the review's technical quality or its consequences. Code provision III.7.a. establishes notification as a precondition for the ethical permissibility of the review, not merely as a procedural nicety. A technically excellent covert review would still constitute a deceptive act toward Engineer A, violating the honesty and non-deception norms embedded in I.6. and implicitly in III.1.a. Consequentialist arguments that the covert review produced net safety benefits would not cure the deontological violation. Moreover, normalizing covert peer reviews would systematically undermine the trust and procedural fairness that make peer review a legitimate professional institution, producing long-run harms that outweigh any short-run safety benefit from a single covert review.
DetailsIn response to Q402: If Engineer A had proactively disclosed the design errors in the first tower and voluntarily requested a peer review of the second tower's plans, the ethical obligations of Engineer B and Owner regarding notification and consent would have been materially transformed. The notification requirement under III.7.a. exists primarily to protect the original engineer from being reviewed without knowledge—a protection grounded in professional fairness and the right to respond. If Engineer A had self-initiated the review, that protective rationale would be fully satisfied by Engineer A's own act of disclosure and request. Engineer B's obligation to ensure notification would be discharged by Engineer A's voluntary initiation, and Owner's consent to the review would be implicit in retaining Engineer B pursuant to Engineer A's request. More significantly, Engineer A's proactive disclosure would itself constitute compliance with III.1.a.'s duty to acknowledge errors, transforming the ethical posture of the entire situation from one of resistance and obstruction to one of professional accountability and cooperation.
DetailsIn response to Q403: Even if the two towers had not been mirror-image designs and the second tower's plans were entirely independent of the first, the known design defects in the first tower would still significantly weaken—though not necessarily eliminate—Engineer A's ethical standing to object to the peer review of the second tower. The defects in the first tower establish a factual record of design error that is directly relevant to Owner's reasonable basis for seeking independent review of Engineer A's subsequent work. Engineer A's professional accountability obligations under III.1.a. and the paramount public safety duty under I.1. do not disappear simply because the second project is technically independent. However, the ethical compulsion for Engineer A to cooperate would be somewhat less acute in the absence of the mirror-image relationship, because the direct inference that the second tower carries forward the same defects would be unavailable. The notification requirement under III.7.a. would remain fully applicable regardless of design similarity, but Engineer A's ethical obligation to affirmatively cooperate—rather than merely not obstruct—would be somewhat more contestable in a fully independent design scenario.
DetailsIn response to Q404: If Owner had terminated Engineer A from the project before retaining Engineer B for the peer review, Engineer B's ethical obligation to ensure notification of Engineer A would be substantially reduced but not entirely eliminated. The primary purpose of the III.7.a. notification requirement is to protect the original engineer's professional interests and afford procedural fairness in the review of their work. Termination does not erase Engineer A's authorship of the plans under review, nor does it eliminate Engineer A's professional interest in how that work is characterized and what conclusions are drawn from the review. A terminated engineer whose prior work is being formally reviewed retains a cognizable professional interest in knowing that review is occurring, particularly where the review's findings could affect their professional reputation or expose them to liability. However, the strength of the notification obligation diminishes after termination because Owner's ongoing relationship with Engineer A—which III.7.a. implicitly presupposes—no longer exists. Engineer B should still notify Engineer A as a matter of professional courtesy and fairness, but the ethical imperative is less categorical than in the active-engagement scenario.
DetailsThe tension between Engineer B's duty of loyalty to the Owner as client and Engineer B's obligation of transparency toward Engineer A was resolved by treating client loyalty as a bounded, not absolute, principle. The NSPE Code requires engineers to act as faithful agents of their clients, but that fidelity cannot extend to conduct that deceives or materially harms a fellow professional without notice. When the Owner instructed Engineer B to conduct the review covertly, Engineer B correctly identified that client loyalty ends where professional deception begins. The resolution was not a rejection of client loyalty but a clarification of its limits: Engineer B remained willing to perform the peer review—fully serving the Owner's legitimate interest in technical oversight—while insisting that the procedural condition of notification be met. This case teaches that client loyalty is an instrumental principle subordinate to the foundational duties of honesty and non-deception, and that an engineer may condition acceptance of an engagement on the client's agreement to ethically permissible terms without abandoning the client relationship entirely.
DetailsThe tension between Engineer A's claimed right to professional integrity and resistance to an unsolicited review, and the paramount duty to protect public safety, was not successfully resolved by Engineer A—and the case reveals that professional integrity, properly understood, cannot be invoked to shield one's own work from legitimate oversight when public safety is demonstrably at risk. Engineer A's refusal to consent to the peer review conflates two distinct concepts: the right to procedural fairness in how a review is conducted, which is legitimate, and the right to veto a review entirely, which is not. Because significant design defects had already been confirmed in the structurally identical first tower, Engineer A's continued resistance to review of the second tower's plans placed professional self-interest in direct conflict with the public safety paramountcy principle. The NSPE Code's requirement that engineers hold public safety paramount operates as a lexically prior obligation that overrides professional pride or reputational concern. This case teaches that professional integrity is not a license for self-insulation from accountability; genuine professional integrity would require acknowledgment of known errors and cooperation with corrective oversight, not obstruction of it.
DetailsThe interaction among Engineer B's confidentiality obligations, safety disclosure duties, and the scope of the peer review engagement reveals a hierarchical principle structure in which public safety functions as a trump card over confidentiality, but only when the safety risk is concrete and the confidentiality constraint would otherwise prevent corrective action. In this case, the confidentiality principle governing the peer review's findings does not operate in isolation: if the Owner were to receive Engineer B's findings of design defects in the second tower and take no corrective action, Engineer B's safety disclosure obligation would be triggered, overriding the confidentiality constraint. This interaction teaches that confidentiality in professional engineering engagements is always implicitly conditioned on the absence of unaddressed public safety threats—it is a default rule, not an absolute one. Furthermore, the case illustrates that the principle of Engineer B's transparency and notification toward Engineer A is not merely a collegial courtesy but a structural prerequisite that makes the entire peer review ethically coherent: without notification, the review would be tainted by deception, undermining the legitimacy of any safety-protective findings it might produce. Procedural integrity and substantive safety protection are thus mutually reinforcing rather than competing principles.
Detailsethical question 18
Is Engineer B ethically required to make certain that Engineer A is advised of the planned peer review?
DetailsIs Engineer A ethically required to cooperate with the peer review of Engineer B?
DetailsIf Owner had never consented to notifying Engineer A and had insisted on a covert review, would Engineer B have been ethically required to withdraw from the engagement entirely rather than proceed?
DetailsDoes Engineer A's continued involvement on the second tower project—despite known design defects in the first tower—itself raise an independent ethical concern about Engineer A's fitness to remain on the project, separate from the peer review dispute?
DetailsWhat obligation, if any, does Engineer B have to report the discovered design defects in the first tower to relevant authorities or the public if Owner takes no corrective action, independent of the peer review question?
DetailsShould the Board have addressed whether Owner bears an independent ethical obligation to proactively notify Engineer A of the peer review, rather than framing the notification duty primarily as Engineer B's responsibility?
DetailsDoes Engineer B's obligation of transparency and notification toward Engineer A conflict with Engineer B's duty of loyalty and confidentiality toward the Owner as client, and how should that tension be resolved when the Owner explicitly instructs secrecy?
DetailsDoes Engineer A's invocation of professional integrity and resistance to an unsolicited peer review conflict with the paramount duty to protect public safety, particularly when known design defects already exist in the first tower?
DetailsHow does Engineer A's right to professional accountability review—implying some degree of procedural fairness in how the review is conducted—conflict with the Owner's authority as client to commission independent technical oversight without the original engineer's consent?
DetailsDoes Engineer B's safety disclosure obligation—requiring escalation when public welfare is at risk—conflict with the confidentiality constraints governing the scope of the peer review engagement, and at what point does safety override confidentiality?
DetailsFrom a deontological perspective, did Engineer B fulfill a categorical duty of professional transparency by insisting that Engineer A be notified of the peer review, regardless of the Owner's instructions to the contrary?
DetailsFrom a deontological perspective, did Engineer A violate a professional duty to acknowledge errors and cooperate with legitimate oversight when refusing to consent to the peer review, given that known design defects in the first tower had already been discovered?
DetailsFrom a consequentialist perspective, did Engineer A's refusal to cooperate with the peer review create a net harm to public safety by leaving the second tower's design unreviewed despite known defects in the structurally identical first tower?
DetailsFrom a virtue ethics standpoint, did Engineer B demonstrate the virtues of professional integrity and collegial respect by simultaneously refusing to conduct a covert review and insisting on notifying Engineer A, thereby balancing loyalty to the client with honesty toward a fellow professional?
DetailsIf Engineer B had complied with the Owner's instruction and conducted the peer review covertly without notifying Engineer A, would Engineer B have violated professional ethics even if the review itself was technically competent and ultimately served public safety?
DetailsIf Engineer A had proactively disclosed the design errors in the first tower and voluntarily requested a peer review of the second tower's plans, would the ethical obligations of Engineer B and the Owner regarding notification and consent have been materially different?
DetailsIf the two towers had not been mirror-image designs and the second tower's plans were entirely independent of the first, would the known design defects in the first tower still ethically preclude Engineer A from objecting to the peer review of the second tower?
DetailsIf the Owner had terminated Engineer A from the project before retaining Engineer B for the peer review, would Engineer B still have been ethically obligated to ensure Engineer A was notified of the review, or does termination fully discharge that notification duty?
DetailsPhase 2E: Rich Analysis
causal normative link 4
By assigning the review under confidentiality, the Owner suppressed the disclosure mechanism that Professional Obligation III.7.a requires, and this suppression is causally significant because it is the origin point of a chain that eventually blocks independent review of the second tower design, leaving a potentially dangerous structure unexamined.
DetailsEngineer B's refusal to proceed without proper consent fulfils the obligation to avoid unauthorized disclosure, and this refusal matters causally because it redirects the situation toward the Owner, forcing a consent decision that becomes the pivotal moment determining whether the second tower's design errors will ever be independently evaluated.
DetailsThe Owner's granting of consent fulfils the disclosure obligation and opens the path for peer review, making this action causally significant because it is the necessary precondition for Engineer A's subsequent refusal to have any normative weight, since without consent there would have been no opportunity for Engineer A to block the review.
DetailsEngineer A's refusal to allow peer review of the second tower violates multiple obligations simultaneously, and the causal gravity of this action is severe because it is the direct cause of the second tower design remaining unreviewed, meaning any latent errors in that design are shielded from correction at the cost of public safety.
Detailsquestion emergence 18
The question arose because Engineer A's refusal to cooperate sits at the intersection of two genuine obligations: the duty to support professional accountability and public safety review, and the procedural requirement that peer review be conducted with proper consent and transparency. The presence of known design defects makes the refusal ethically costly, but the irregular origins of the review request give the refusal a surface plausibility that prevents the answer from being obvious.
DetailsThis question arose because Owner removed the procedural condition, Engineer A's consent, that would have made Engineer B's participation straightforwardly permissible, forcing Engineer B into a situation where every available path carries a distinct ethical cost. The question is not merely about procedure but about whether the prohibition on covert review is absolute or whether it yields when the alternative is leaving a known public safety risk unexamined.
DetailsThis question arose because the case presents two distinct wrongs by Engineer A, namely prior design defects and present obstruction of review, and the combination raises a question that neither wrong alone would force. The data of known defects plus active peer review refusal creates pressure on the warrant requiring engineers to be competent and accountable, and that pressure generates an independent question about whether continued project involvement is itself an ethical violation, separate from any dispute about how the peer review should be conducted.
DetailsThis question arose because Engineer B possesses knowledge of a concrete public safety risk from the first tower defects but acquired that knowledge within a confidential professional review context where the Owner, not Engineer B, holds primary authority over corrective action. The tension between the paramount duty to public safety and the bounded nature of a peer reviewer's role creates genuine uncertainty about whether Engineer B's obligation to act extends beyond the client relationship and into independent reporting to authorities.
DetailsThe question emerged because the Board's analysis focused on Engineer B's conduct under NSPE Code obligations while leaving unexamined whether the Owner, by instructing a covert review and controlling access to Engineer A, independently triggered the Peer Review Notification Obligation. The structural gap between the Owner's causal role in creating the covert review state and the Board's framing of notification as Engineer B's burden alone is what made this question contestable.
DetailsThis question arose because the Owner placed Engineer B in a structural conflict by instructing secrecy at the precise moment when professional norms independently required Engineer B to notify Engineer A of the review. The conflict is not resolvable by simple priority rules because both the transparency obligation and the client loyalty obligation are grounded in recognized professional duties, and the Owner's explicit instruction transforms what might otherwise be a procedural question into a direct test of which duty takes precedence when they cannot both be satisfied.
DetailsThis question emerged because two independently valid professional obligations collided at the moment Engineer A refused peer review while known design defects already existed in a related structure. The covert origin of the review request gave Engineer A a procedurally grounded basis for resistance, but the presence of confirmed prior errors made that resistance appear to obstruct a safety-critical process, forcing a direct contest between professional integrity as a personal prerogative and public safety as a paramount duty.
DetailsThis question arose because two legitimate structural features of professional peer review pulled in opposite directions once Engineer A refused consent. The data of prior design errors and a blocked review triggered both the Owner's authority to protect public safety through independent oversight and Engineer A's residual claim to procedural fairness in how that oversight is conducted, and neither warrant fully displaced the other given the simultaneous presence of a covert review instruction and a notification constraint.
DetailsThis question arose because Engineer B entered the engagement under confidentiality terms that were designed to govern ordinary review scope, but the discovery of known design defects in the first tower and the blocking of review of the second tower created a situation those terms were not designed to address. The gap between what the confidentiality agreement covers and what the safety obligation demands is exactly the contested space that generates the question.
DetailsThis question arose because the Owner's covert review instruction placed Engineer B at the intersection of two genuine professional obligations, one requiring transparent collegial notification and one permitting client-directed confidentiality, with no clear hierarchical rule resolving which obligation is categorical under deontological reasoning. The presence of known design defects and Engineer A's active refusal to cooperate sharpened the tension, because those facts could either strengthen the case for overriding confidentiality in the name of transparency or reinforce the Owner's legitimate interest in an independent undisclosed assessment.
DetailsThis question arose because the data record combines two distinct facts, confirmed prior design defects and an active refusal to permit review of a second structure, in a way that makes Engineer A's refusal look like obstruction of legitimate safety oversight rather than a neutral procedural choice. The deontological framing sharpens the question further because it asks whether the duty to acknowledge errors and cooperate with oversight is categorical once defects are known, or whether procedural irregularities in how the review was initiated can suspend that duty.
DetailsThis question arose because the data established a direct causal chain from Engineer A's refusal to a structurally dangerous design remaining unreviewed, which activates a consequentialist warrant holding that any act producing net harm to public safety is ethically impermissible. The question persists because a competing warrant holds that the net harm is not attributable solely to Engineer A's refusal when other actors, including Engineer B and the Owner, retained independent obligations to escalate the safety concern, making the causal and moral responsibility genuinely contested.
DetailsThe question arose because Engineer B's conduct involved two distinct acts, refusing the covert review and demanding notification of Engineer A, each of which can be evaluated separately under virtue ethics, and the combination of those acts in a context of known design defects and Owner pressure created genuine uncertainty about whether both acts together reflect integrated virtue or whether one of them exceeds what professional integrity and collegial respect actually require. The presence of Engineer A's refusal to cooperate further complicated the picture, because it raised the question of whether collegial respect is owed to a professional who is actively obstructing a safety-relevant review.
DetailsThis question arose because the data presents a scenario where the procedural wrong of covert review and the substantive good of technically competent safety-serving review are fully separable, forcing a judgment about whether professional ethics is violated by the method of conduct even when the result is defensible. The tension between the Collegial Notification Principle and the Public Safety Paramount principle, each grounded in the NSPE Code of Ethics, means that compliance with one norm appears to require deviation from the other, and no single warrant cleanly resolves the conflict without a rebuttal condition undermining it.
DetailsThis question arose because the original case analysis assumed an adversarial posture in which Engineer A refused consent and the Owner instructed covert review, generating specific obligations for Engineer B and the Owner as corrective responses to that posture. Asking whether proactive disclosure by Engineer A would have changed those obligations contests the warrant structure at its foundation, since the obligations of Engineer B and the Owner were derived from Engineer A's non-cooperation as the triggering data, and removing that data by substituting voluntary transparency forces a re-examination of whether the same conclusions still follow.
DetailsThis question arose because the original case rested on a tight logical link between the known defects in the first tower and the ethical justification for overriding Engineer A's objection to peer review of the second tower. Once that link is severed by stipulating design independence, the argument structure is contested at the warrant level, forcing a new question about whether professional accountability is person-bound or design-bound.
DetailsThis question arose because the original notification obligation was constructed around Engineer A's concurrent presence on the project, and the hypothetical of prior termination strips away that contextual anchor, forcing a determination of whether the duty is grounded in professional courtesy toward a colleague or in procedural fairness to an active participant. The tension between the Collegial Notification Principle and the Owner Client Loyalty Limits Notification principle is sharpened rather than resolved by termination, because the Owner's authority to discharge Engineer A does not automatically transfer to Engineer B the right to treat that engineer as a stranger to the review.
DetailsThis question arose because Engineer B was placed in a situation where the Owner's covert review instruction directly contested the professional norm requiring that a reviewed engineer be made aware of the review. The tension between client instruction limits and collegial notification created genuine uncertainty about whether Engineer B bore an independent duty to notify Engineer A, or whether that duty belonged to the Owner alone.
Detailsresolution pattern 20
Because Owner retained Engineer B to review Engineer A's plans without Engineer A's knowledge, and because III.7.a conditions such a review on the other engineer's awareness, the board concluded that Engineer B was ethically required to ensure notification occurred before proceeding, regardless of the Owner's initial preference for secrecy.
DetailsBecause III.7.a independently conditions the legitimacy of a peer review on the reviewed engineer's knowledge, the board concluded that the Owner's consent to notification did not create the duty but only removed an obstruction to a pre-existing obligation, and that a covert review would have been procedurally invalid under the Code regardless of its technical quality.
DetailsBecause the Owner's instruction to proceed covertly would have made Engineer B complicit in a violation of III.7.a rather than merely requiring a difficult professional judgment call, the board concluded that Engineer B had no discretion to comply, and that withdrawal would have been the only ethically available option had the Owner refused to consent to notification.
DetailsBecause Engineer B acquired knowledge of significant safety-threatening defects in the first tower through the engagement, and because Engineer A's refusal to cooperate with the second tower review left the public safety risk unaddressed, the board's framework implies that Engineer B's ethical obligations extend beyond the peer review dispute to require safety escalation if the Owner fails to act, with confidentiality provisions subordinated to the paramount duty under I.1.
DetailsBecause the second tower shared a mirror-image design with a tower already known to contain significant defects, Engineer A's refusal to cooperate with the peer review functioned in practice as a suppression of facts material to public safety, and the board concluded that the cooperation duty was supported not only by general professional accountability norms but by the specific and elevated safety stakes that the confirmed first-tower defects created.
DetailsBecause Owner held complete information about the defects and had direct authority over both engineers, the board concluded that framing the notification duty solely on Engineer B understated Owner's independent obligation, given that Owner's covert instruction was an attempt to induce Engineer B to violate a professional norm rather than a permissible exercise of client authority.
DetailsBecause Engineer B treated the notification requirement as a non-negotiable professional duty rather than a factor to weigh against client preferences, the board concluded that Engineer B fulfilled both the deontological obligation under III.7.a and the virtue ethics standard of professional integrity and collegial respect, with both frameworks pointing to the same conduct under these facts.
DetailsBecause III.7.a makes notification a precondition rather than a preference, the board concluded that a technically excellent covert review would still constitute an ethical violation, given that the deceptive act toward Engineer A is wrong in itself and that permitting outcome-based justifications would erode the institutional legitimacy of peer review over time.
DetailsBecause the notification requirement exists to protect Engineer A from unsolicited scrutiny without knowledge, the board concluded that Engineer A's voluntary initiation of the review would discharge that protective purpose, making the separate notification and consent obligations of Engineer B and Owner functionally redundant under those altered facts.
DetailsBecause the mirror-image relationship made it reasonable to infer that the first tower's defects were present in the second, the board concluded that Engineer A's ethical standing to object to the peer review was significantly weakened, while acknowledging that a fully independent design would reduce but not eliminate that weakening given the prior defect record.
DetailsGiven that Engineer A's employment had ended before Engineer B was retained, the board concluded that the structural premise of III.7.a., an ongoing client relationship requiring procedural fairness, was weakened, so the notification duty survived as a matter of professional courtesy rather than as a non-waivable threshold requirement.
DetailsGiven that the Owner's instruction demanded covert conduct that would deceive Engineer A, the board concluded that client loyalty ends at the point where following client instructions requires professional deception, and that Engineer B correctly conditioned acceptance of the engagement on the Owner's agreement to permit notification.
DetailsGiven that confirmed defects in the first tower created a concrete safety risk for the second tower of identical design, the board concluded that Engineer A's refusal to cooperate placed professional self-interest in direct conflict with the paramount duty to protect public safety, and that genuine professional integrity required cooperation with corrective oversight rather than obstruction of it.
DetailsGiven that confirmed defects in the first tower made a concrete safety risk foreseeable, the board concluded that confidentiality in this engagement was always implicitly conditioned on the Owner taking corrective action, and that procedural notification to Engineer A was not merely collegial courtesy but a structural requirement that preserved the ethical legitimacy of any safety-protective findings the review might produce.
DetailsGiven that the Owner's insistence on secrecy made it impossible for Engineer B to satisfy the notification requirement that III.7.a. treats as a precondition for permissible peer review, the board concluded that Engineer B would have been ethically required to withdraw, because continuing under a covert mandate would make Engineer B complicit in deceiving Engineer A and would undermine the integrity of the peer review process itself.
DetailsBecause the first tower's defects were confirmed and the second tower was structurally identical, the board found that Engineer A's continued involvement without disclosure or corrective action was not a neutral professional posture but a failure to acknowledge known errors, raising an independent fitness concern analytically separate from the peer review dispute itself.
DetailsBecause owner inaction combined with a blocked peer review left known structural defects unaddressed in a project affecting public safety, the board concluded that Engineer B's duty under I.1. required escalation to relevant authorities, and that confidentiality constraints under II.1.c. and III.4. yielded to that safety override rather than extinguishing it.
DetailsBecause Owner held the direct contractual relationship with Engineer A and issued the covert instruction, the board found that framing notification solely as Engineer B's duty obscured Owner's independent ethical lapse, and that a complete analysis required recognizing Owner's own obligation of fair dealing toward Engineer A as the primary source of the notification duty.
DetailsBecause III.7.a. makes notification of the original engineer a precondition for a permissible peer review, the board found that Owner's covert instruction asked Engineer B to engage in an ethically impermissible act, and that compliance would have constituted complicity rather than faithful agency, resolving the apparent tension decisively in favor of transparency toward Engineer A.
DetailsBecause confirmed defects in the first tower created a direct safety concern for the structurally identical second tower, the board concluded that Engineer A's resistance to the peer review inverted the meaning of professional integrity, since genuine professional integrity in these circumstances would have manifested as cooperation with independent review rather than obstruction of it.
DetailsPhase 3: Decision Points
canonical decision point 7
Should Engineer A cooperate with the peer review of the design work, or refuse participation on the grounds that the review was not consented to or was outside the agreed scope of engagement?
DetailsShould Engineer B treat all findings from the peer review as confidential to the client who commissioned the review, or disclose safety-relevant errors beyond the client when those errors pose a risk to public safety?
DetailsShould Engineer A consent to and cooperate with the peer safety review of the design, or refuse to participate in the review process?
DetailsShould Engineer B accept the peer review assignment under the client's confidentiality restrictions, or decline the assignment unless the scope permits full disclosure of safety-relevant findings?
DetailsShould Engineer A cooperate with the peer review by acknowledging identified design errors, or refuse to participate in the review process?
DetailsShould Engineer B notify the owner of the peer review findings and identified design errors, or limit disclosure in accordance with the client's confidentiality instructions?
DetailsShould Engineer B treat the peer review findings as fully confidential per client instructions, or recognize that safety-related findings fall outside the permissible scope of confidentiality?
DetailsPhase 4: Narrative Elements
Characters 4
Timeline Events 19 -- synthesized from Step 3 temporal dynamics
The case begins with two engineers operating in overlapping professional roles, where Engineer B holds review responsibilities that place him in direct conflict with the work of Engineer A. This structural tension sets the stage for a series of difficult ethical decisions involving loyalty, oversight, and professional duty.
Engineer B is assigned to conduct a confidential peer review of engineering work that is connected to Engineer A, creating an immediate question about impartiality and the boundaries of professional obligation. The confidential nature of the assignment adds complexity, as it limits what Engineer B can openly discuss or disclose.
When asked to participate in a formal peer review process, Engineer A declines, raising concerns about whether this refusal is appropriate under the circumstances. This decision is significant because peer review serves as a foundational quality control mechanism in engineering practice.
A question arises about whether Engineer B must obtain consent before notifying relevant parties about concerns discovered during the review process. How this question is resolved will shape the ethical and procedural path forward for both engineers.
Engineer A explicitly refuses to consent to any notification that Engineer B might wish to make based on findings from the peer review. This refusal puts Engineer B in a difficult position, caught between respecting a colleague's wishes and fulfilling broader professional responsibilities.
In the course of the review, Engineer B identifies substantive errors in the engineering design, elevating the situation from a procedural dispute to a potential public safety concern. The discovery transforms the ethical stakes considerably, as flawed designs can carry real consequences for public welfare.
Engineer A takes active steps to prevent the peer review from proceeding or being completed, effectively blocking the oversight process that professional standards are meant to protect. This obstruction raises serious questions about accountability and the integrity of engineering self-regulation.
With design errors confirmed and the review process blocked, Engineer B reaches a critical threshold where professional codes may require action regardless of the confidentiality constraints or the lack of consent. This moment represents the ethical core of the case, forcing a direct confrontation between competing obligations.
Second Tower Design Unreviewed
Tension between Engineer B Confidentiality Review Scope and Engineer B Client Instruction Limits
Engineer B is prohibited from conducting a covert review, yet the obligation to disclose safety-relevant findings discovered during a confidential review may pressure the engineer toward actions that resemble or require covert investigation. If Engineer B uncovers a safety defect while operating under confidentiality, the duty to disclose pulls against the prohibition on acting outside the sanctioned review scope. These two demands cannot always be satisfied simultaneously, especially when the client has not consented to safety-focused scrutiny.
Should Engineer A cooperate with the peer review of the design work, or refuse participation on the grounds that the review was not consented to or was outside the agreed scope of engagement?
Should Engineer B treat all findings from the peer review as confidential to the client who commissioned the review, or disclose safety-relevant errors beyond the client when those errors pose a risk to public safety?
Should Engineer A consent to and cooperate with the peer safety review of the design, or refuse to participate in the review process?
Should Engineer B accept the peer review assignment under the client's confidentiality restrictions, or decline the assignment unless the scope permits full disclosure of safety-relevant findings?
Should Engineer A cooperate with the peer review by acknowledging identified design errors, or refuse to participate in the review process?
Should Engineer B notify the owner of the peer review findings and identified design errors, or limit disclosure in accordance with the client's confidentiality instructions?
Should Engineer B treat the peer review findings as fully confidential per client instructions, or recognize that safety-related findings fall outside the permissible scope of confidentiality?
Engineer B is ethically required to make certain that Engineer A is advised of the planned peer review.
Ethical Tensions 4
Decision Moments 7
- Cooperate Fully with Peer Review board choice
- Cooperate Subject to Defined Scope Agreement
- Decline Participation Pending Authorization
- Disclose Safety Errors Beyond Client Confidentiality board choice
- Report Findings Exclusively to Commissioning Client
- Seek Explicit Client Authorization Before Broader Disclosure
- Consent and Cooperate Fully with Review board choice
- Refuse Participation in Peer Review
- Consent with Conditions on Scope
- Accept Assignment with Safety Disclosure Reserved board choice
- Decline Assignment Due to Confidentiality Restrictions
- Accept Assignment Within Client-Defined Scope Only
- Cooperate Fully and Acknowledge Errors board choice
- Dispute Findings Through Technical Rebuttal
- Decline to Participate in Review
- Notify Owner of All Safety-Relevant Findings board choice
- Limit Disclosure to Client-Approved Scope
- Seek Client Consent Before Notifying Owner
- Apply Confidentiality Limits for Safety Findings board choice
- Honor Full Confidentiality as Contracted
- Withdraw from Engagement Rather Than Disclose