Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Pipeline Steps
Overview
1 Contextual Framework
2 Normative Requirements
3 Temporal Dynamics Reconcile
4 Whole-Case Synthesis
Extraction Review Full View
Provenance
Independence of Peer Reviewer
Step 4 of 5
Entity Review

242

Entities

8

Provisions

3

Precedents

18

Questions

20

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
The ethical obligation to ensure procedural integrity and public safety is transferred from the Owner's control (who attempted to suppress it) to Engineer B as a non-waivable categorical duty. If the Owner takes no corrective action, the obligation transfers further outward to relevant public authorities. The original holder (Owner) is relieved of discretionary control because the duty exists independently of the client relationship and falls to whichever actor can legitimately discharge it.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

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

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (8)
View Extraction
I.1. Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 24)
Obligation
Engineer A Safety Review Consent
Holding public safety paramount requires Engineer A to consent to peer review after prior significant errors were found.
State
Engineer A Public Safety Risk
The public safety risk from known design defects directly invokes the paramount duty to protect public safety, health, and welfare.
Constraint
Engineer A Safety Review Consent Limit
The paramount duty to public safety limits Engineer A's ability to refuse consent to a peer review when significant design errors have been confirmed.
Obligation (5)
  • Engineer A Safety Review Consent
    Holding public safety paramount requires Engineer A to consent to peer review after prior significant errors were found.
  • Engineer A Competence Review Disclosure
    Public safety requires Engineer A to acknowledge limitations and support verification of the second tower plans.
  • Engineer B Confidential Review Safety Disclosure
    Public safety paramount obligation requires disclosure of safety code violations discovered during peer review despite confidentiality agreements.
  • Engineer A Peer Review Cooperation
    Cooperating with peer review directly supports public safety given known design errors in prior work.
  • Engineer A Error Acknowledgment Cooperation
    Acknowledging errors and cooperating with review is necessary to protect public safety.
State (4)
  • Engineer A Public Safety Risk
    The public safety risk from known design defects directly invokes the paramount duty to protect public safety, health, and welfare.
  • Engineer A Known Design Defects
    Confirmed defects in Engineer A's first tower design create a public safety concern that engineers must hold paramount.
  • Engineer A Prior Design Errors
    Significant design errors in the first tower represent a direct threat to public safety that must be held paramount.
  • Engineer B Competing Review Duties
    Engineer B's obligation to protect public safety weighs against any instruction that might suppress a safety-critical peer review.
Constraint (3)
  • Engineer A Safety Review Consent Limit
    The paramount duty to public safety limits Engineer A's ability to refuse consent to a peer review when significant design errors have been confirmed.
  • Engineer B Confidentiality Safety Override
    The duty to hold public safety paramount requires a peer reviewer to escalate safety code violations even when bound by confidentiality obligations.
  • Engineer A Peer Review Cooperation
    The public safety imperative creates the ethical obligation for Engineer A to cooperate with the peer review of potentially defective designs.
Principle (4)
  • Engineer A Public Safety Obstruction
    Engineer A's refusal to allow peer review directly threatened public safety, violating the paramount duty to protect public welfare.
  • Engineer A Public Safety Paramountcy
    The board cited the public safety paramount obligation as a converging reason why Engineer A's refusal to consent was unethical.
  • Engineer B Safety Disclosure Obligation
    The obligation to disclose safety code violations even under confidentiality agreements flows directly from the duty to hold public safety paramount.
  • Engineer A Professional Competence Review
    Significant design errors in the first tower raised public safety concerns that made peer review of the second tower a public safety imperative.
Role (2)
  • Engineer A Design Engineer
    Engineer A's plans contained significant errors that posed safety risks, directly implicating the duty to hold public safety paramount.
  • Engineer B Peer Reviewer
    Engineer B's peer review role was intended to identify safety-critical errors in the design, making public safety paramount to their conduct.
Event (2)
  • Design Errors Discovered
    Discovered design errors directly threaten public safety and welfare, triggering the paramount duty to protect the public.
  • Second Tower Design Unreviewed
    Leaving the second tower design unreviewed creates an unaddressed safety risk to the public.
Capability (4)
  • Engineer A Safety Accountability Judgment
    Engineer A's obligation to recognize that significant design errors create a professional duty directly relates to holding public safety paramount.
  • Engineer B Design Error Recognition
    Engineer B's capability to identify significant design errors through peer review directly serves the paramount duty to protect public safety.
  • Engineer B Safety Disclosure Escalation
    Engineer B's capability to escalate safety concerns discovered during peer review is a direct expression of the duty to hold public safety paramount.
  • Engineer A Safety Review Consent Judgment
    Engineer A's obligation to recognize that prior design errors create a duty to consent to safety review directly reflects the paramount public safety obligation.
I.4. Act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 18)
Obligation
Engineer B Client Instruction Limits
Acting as a faithful agent does not extend to following client instructions that violate professional ethical obligations such as covert review.
Action
Peer Review Refusal
This provision governs whether refusing a peer review aligns with acting as a faithful agent or trustee to the client.
State
Engineer B Competing Review Duties
Engineer B's duty to act as a faithful agent to the Owner conflicts with professional courtesy obligations toward Engineer A.
Obligation (3)
  • Engineer B Client Instruction Limits
    Acting as a faithful agent does not extend to following client instructions that violate professional ethical obligations such as covert review.
  • Engineer B Peer Review Knowledge
    Engineer B's duty as faithful agent to the Owner is bounded by ethical obligations including notifying Engineer A before review.
  • Owner Peer Review Notification Consent
    The Owner acting within proper bounds as client required agreeing to notify Engineer A as a condition of proceeding with the review.
Action (1)
  • Peer Review Refusal
    This provision governs whether refusing a peer review aligns with acting as a faithful agent or trustee to the client.
State (3)
  • Engineer B Competing Review Duties
    Engineer B's duty to act as a faithful agent to the Owner conflicts with professional courtesy obligations toward Engineer A.
  • Engineer A Engineer B Relationship
    Engineer B's engagement with the Owner to conduct the peer review reflects the faithful agent duty owed to the client.
  • Owner Covert Review Instruction
    Engineer B must weigh the Owner's instructions as a faithful agent while balancing other professional obligations.
Constraint (2)
  • Engineer B Client Instruction Limit
    The duty to act as a faithful agent to the client does not extend to following client instructions that require unethical conduct such as covert review.
  • Engineer B Confidentiality Review Scope
    Acting as a faithful agent to the Owner includes maintaining confidentiality of peer review findings on behalf of that client.
Principle (2)
  • Owner Client Loyalty Limits Engineer B
    Engineer B's duty as a faithful agent to the Owner did not extend to following instructions that required unethical covert conduct.
  • Owner Client Loyalty Limits Notification
    The faithful agent duty has limits and does not require compliance with client instructions that violate professional ethical obligations.
Role (2)
  • Engineer A Design Engineer
    Engineer A was retained by the Owner and owed a duty to act as a faithful agent in producing accurate and reliable designs.
  • Engineer B Peer Reviewer
    Engineer B was retained by the Owner and owed a duty to act as a faithful agent in conducting an honest and independent peer review.
Event (2)
  • Peer Review Blocked
    Blocking the peer review prevents the engineer from acting as a faithful agent to the client by ensuring work quality.
  • Second Tower Design Unreviewed
    Failing to complete the review of the second tower represents a failure to faithfully serve the client's interests.
Capability (3)
  • Engineer B Client Instruction Boundary
    Acting as a faithful agent requires recognizing the limits of client loyalty, which is precisely the boundary Engineer B had to identify.
  • Engineer B Ethical Reasoning Review Refusal
    Engineer B's deliberation on balancing client instructions against professional obligations reflects the tension inherent in acting as a faithful agent or trustee.
  • Engineer B Confidentiality Scope Reasoning
    Distinguishing between confidentiality obligations to the Owner and other professional duties is directly tied to the faithful agent relationship with the client.
I.6. Conduct themselves honorably, responsibly, ethically, and lawfully so as to enhance the honor, reputation, and usefulness of the profession.
How this applies in the case (showing 3 of 22)
Obligation
Engineer B Covert Review Refusal
Refusing to conduct a covert review reflects honorable and ethical conduct that upholds the reputation of the profession.
Action
Peer Review Refusal
This provision governs whether refusing a peer review under ethically compromised conditions upholds the honor and responsibility of the profession.
State
Engineer A Peer Review Refusal
Engineer A's refusal to cooperate with a legitimate peer review reflects on the honorable and responsible conduct expected of engineers.
Obligation (3)
  • Engineer B Covert Review Refusal
    Refusing to conduct a covert review reflects honorable and ethical conduct that upholds the reputation of the profession.
  • Engineer A Error Acknowledgment Cooperation
    Acknowledging errors and cooperating with review demonstrates responsible and ethical professional conduct.
  • Engineer A Professional Accountability Cooperation
    Cooperating with peer review as an expression of professional accountability reflects honorable and responsible conduct.
Action (2)
  • Peer Review Refusal
    This provision governs whether refusing a peer review under ethically compromised conditions upholds the honor and responsibility of the profession.
  • Peer Review Consent Refusal
    This provision governs whether refusing consent for a peer review is conducted in an honorable and ethical manner consistent with professional standards.
State (3)
  • Engineer A Peer Review Refusal
    Engineer A's refusal to cooperate with a legitimate peer review reflects on the honorable and responsible conduct expected of engineers.
  • Engineer A Peer Review Cooperation Refused
    Refusing to cooperate with peer review undermines the honor and reputation of the profession.
  • Engineer B Competing Review Duties
    Engineer B must conduct themselves honorably and responsibly when navigating competing obligations in this situation.
Constraint (2)
  • Engineer B Non-Deception Covert Review
    Conducting oneself honorably and ethically prohibits Engineer B from participating in a deceptive covert review process.
  • Engineer A Competence Defect Acknowledgment
    Conducting oneself honorably and responsibly requires Engineer A to acknowledge the competence limitations revealed by significant design errors.
Principle (3)
  • Engineer A Professional Integrity Resistance
    Engineer A's refusal to cooperate with peer review to protect personal reputation failed to conduct himself honorably and responsibly.
  • Engineer B Professional Integrity Insistence
    Engineer B's insistence on notifying Engineer A before proceeding exemplified honorable and responsible professional conduct.
  • Engineer A Professional Accountability Refusal
    Refusing peer review despite known prior errors reflects a failure to conduct oneself responsibly and ethically in a manner that enhances the profession.
Role (2)
  • Engineer A Design Engineer
    Engineer A's refusal to consent to peer review and production of error-laden plans reflects on honorable and responsible professional conduct.
  • Engineer B Peer Reviewer
    Engineer B's insistence on proper notification before proceeding reflects honorable and ethical professional conduct.
Event (2)
  • Peer Review Blocked
    Allowing a peer review to be improperly blocked undermines the honorable and ethical conduct expected of engineers.
  • Design Errors Discovered
    Handling discovered design errors responsibly and ethically is required to uphold the honor and reputation of the profession.
Resource (1)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code of Ethics framework used to assess whether Engineer B conducted themselves honorably and ethically in the peer review situation.
Capability (4)
  • Engineer B Situational Awareness Covert Review
    Recognizing that a covert review would be ethically problematic reflects the duty to conduct oneself honorably so as to enhance the profession's reputation.
  • Engineer B Justification Refusal
    Engineer B's ability to articulate principled reasoning for refusing the covert review reflects the duty to act honorably and responsibly.
  • Engineer A Norm Competence Accountability
    Engineer A's obligation to recognize and apply professional norms of cooperation with peer review reflects the duty to conduct oneself honorably within the profession.
  • Engineer A Professional Accountability Acceptance
    Accepting accountability for prior design errors and cooperating with review processes reflects the duty to act responsibly and ethically.
II.1.c. 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.
How this applies in the case (showing 3 of 15)
Obligation
Engineer B Confidentiality Review Scope
This provision governs the scope of Engineer B's obligation not to reveal review findings without Owner consent.
Action
Confidential Review Assignment
This provision governs whether confidential information can be revealed during a peer review assignment without prior client consent.
State
Owner Covert Review Instruction
The Owner's instruction to conduct a covert review raises questions about whether Engineer B would be revealing client or project information without proper consent.
Obligation (2)
  • Engineer B Confidentiality Review Scope
    This provision governs the scope of Engineer B's obligation not to reveal review findings without Owner consent.
  • Engineer B Confidentiality Scope Limit
    The provision on not revealing client information without consent is directly relevant to defining the limits of Engineer B's confidentiality obligation.
Action (1)
  • Confidential Review Assignment
    This provision governs whether confidential information can be revealed during a peer review assignment without prior client consent.
State (2)
  • Owner Covert Review Instruction
    The Owner's instruction to conduct a covert review raises questions about whether Engineer B would be revealing client or project information without proper consent.
  • Engineer B Covert Review Instruction
    Conducting a covert review could involve handling facts and data about Engineer A's work without Engineer A's consent, implicating this confidentiality provision.
Constraint (2)
  • Engineer B Confidentiality Review Scope
    This provision directly establishes the confidentiality obligation limiting Engineer B from disclosing peer review findings to third parties without client consent.
  • Engineer B Confidentiality Safety Override
    This provision establishes the confidentiality constraint that must be balanced against safety obligations when violations are discovered during review.
Principle (2)
  • Engineer B Confidentiality Review Scope
    This provision governs the scope of Engineer B's confidentiality obligation, covering review findings but not concealing the existence of the review itself.
  • Engineer B Safety Disclosure Obligation
    This provision establishes the baseline confidentiality duty from which the safety disclosure exception is carved out when required by the Code.
Role (1)
  • Engineer B Peer Reviewer
    Engineer B handling Engineer A's plans and associated data must respect confidentiality obligations to the client unless authorized to disclose.
Event (2)
  • Design Errors Discovered
    The discovery of design errors raises the question of whether the reviewer may disclose that information without prior client consent.
  • Notification Obligation Triggered
    The obligation to notify relevant parties about errors must be balanced against the duty not to reveal client information without consent.
Resource (1)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code of Ethics framework relevant to evaluating whether confidential facts or data were improperly revealed during the peer review process.
Capability (2)
  • Engineer B Confidentiality Scope Reasoning
    This provision directly governs Engineer B's reasoning about what review findings could be disclosed and to whom without client consent.
  • Engineer B Safety Disclosure Escalation
    The escalation sequence for safety concerns must account for the prohibition on revealing information without consent except as required by law or the Code.
III.1.a. Engineers shall acknowledge their errors and shall not distort or alter the facts.
How this applies in the case (showing 3 of 15)
Obligation
Engineer A Error Acknowledgment Cooperation
This provision directly requires Engineer A to acknowledge errors found in the first tower plans rather than distorting or concealing them.
Action
Confidential Review Assignment
This provision requires that during a confidential review assignment, engineers must not distort or alter facts in their findings.
State
Engineer A Prior Design Errors
Engineer A's obligation to acknowledge errors in the first tower design is directly addressed by the duty not to distort or alter facts.
Obligation (2)
  • Engineer A Error Acknowledgment Cooperation
    This provision directly requires Engineer A to acknowledge errors found in the first tower plans rather than distorting or concealing them.
  • Engineer A Competence Review Disclosure
    Acknowledging limitations arising from discovered errors aligns directly with the obligation not to distort or alter facts.
Action (1)
  • Confidential Review Assignment
    This provision requires that during a confidential review assignment, engineers must not distort or alter facts in their findings.
State (3)
  • Engineer A Prior Design Errors
    Engineer A's obligation to acknowledge errors in the first tower design is directly addressed by the duty not to distort or alter facts.
  • Engineer A Known Design Defects
    Known defects in Engineer A's design must be acknowledged rather than concealed or distorted.
  • Engineer A Peer Review Refusal
    Refusing peer review may be an attempt to avoid acknowledgment of errors, conflicting with the duty to acknowledge mistakes.
Constraint (1)
  • Engineer A Competence Defect Acknowledgment
    The requirement to acknowledge errors and not distort facts directly creates the constraint that Engineer A must acknowledge the significant design errors discovered.
Principle (3)
  • Engineer A Professional Accountability Refusal
    Engineer A's refusal to submit to peer review after known errors reflects a failure to acknowledge errors and take responsibility for design actions.
  • Engineer A Professional Accountability Review
    The duty to acknowledge errors and not distort facts required Engineer A to cooperate with peer review rather than obstruct it.
  • Engineer A Professional Integrity Resistance
    Prioritizing reputational protection over cooperation with review is inconsistent with the obligation to acknowledge errors honestly.
Role (1)
  • Engineer A Design Engineer
    Engineer A had a duty to acknowledge the significant errors discovered in the plans rather than potentially concealing or distorting them.
Event (1)
  • Design Errors Discovered
    Engineers must acknowledge the discovered errors and not distort or conceal the facts surrounding them.
Capability (3)
  • Engineer A Domain Expertise Design
    The discovery of significant errors in Engineer A's prior designs implicates the duty to acknowledge errors rather than distort or alter the facts.
  • Engineer A Professional Accountability Acceptance
    Accepting accountability for prior design errors is a direct application of the duty to acknowledge errors and not distort the facts.
  • Engineer A Safety Accountability Judgment
    Recognizing the professional duty arising from discovered errors requires the foundational commitment to acknowledge those errors honestly.
III.1.f. Engineers shall treat all persons with dignity, respect, fairness and without discrimination.
How this applies in the case (showing 3 of 15)
Obligation
Engineer B Covert Review Refusal
Refusing to conduct a covert review treats Engineer A with dignity and fairness as required by this provision.
Action
Peer Review Consent Refusal
This provision governs that refusing consent must be handled with dignity, respect, and fairness toward all parties involved.
State
Engineer A Peer Review Cooperation Refused
Engineer A's refusal to cooperate with Engineer B may reflect a failure to treat a fellow engineer with dignity, respect, and fairness.
Obligation (3)
  • Engineer B Covert Review Refusal
    Refusing to conduct a covert review treats Engineer A with dignity and fairness as required by this provision.
  • Engineer B Peer Review Notification
    Notifying Engineer A before commencing review treats Engineer A with fairness and respect.
  • Engineer A Professional Accountability Cooperation
    Treating the peer review process fairly and cooperatively reflects the dignity and respect owed among professionals.
Action (1)
  • Peer Review Consent Refusal
    This provision governs that refusing consent must be handled with dignity, respect, and fairness toward all parties involved.
State (2)
  • Engineer A Peer Review Cooperation Refused
    Engineer A's refusal to cooperate with Engineer B may reflect a failure to treat a fellow engineer with dignity, respect, and fairness.
  • Engineer A Engineer B Relationship
    The professional relationship between Engineer A and Engineer B should be conducted with mutual dignity and respect.
Constraint (2)
  • Engineer B Non-Deception Covert Review
    The requirement to treat all persons with dignity and fairness supports the constraint that Engineer B must not participate in a process that conceals the review from Engineer A.
  • Engineer B Notification Procedural Requirement
    Treating Engineer A with dignity and fairness underpins the procedural requirement that Engineer B notify Engineer A before commencing the peer review.
Principle (2)
  • Engineer B Transparency Notification
    Notifying Engineer A before commencing review treated Engineer A with dignity, fairness, and respect as a fellow professional.
  • Engineer B Collegial Notification Refusal
    Declining to conduct a covert review reflects treating Engineer A with dignity and fairness rather than acting behind his back.
Role (2)
  • Engineer B Peer Reviewer
    Engineer B's objection to proceeding without notifying Engineer A reflects treating a fellow engineer with fairness and respect.
  • Engineer A Design Engineer
    Engineer A's refusal to consent to the peer review raises concerns about treating fellow engineers and the process with fairness and respect.
Event (1)
  • Peer Review Blocked
    Blocking the peer review may involve unfair or disrespectful treatment of the reviewing engineer in the professional process.
Capability (2)
  • Engineer A Peer Review Cooperation
    Treating Engineer B with dignity and fairness requires Engineer A to cooperate fully with the legitimate peer review process rather than obstruct it.
  • Engineer B Peer Review Protocol
    Notifying Engineer A of the peer review treats the original design engineer with the dignity and respect required by this provision.
III.4. 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.
How this applies in the case (showing 3 of 17)
Obligation
Engineer B Confidentiality Review Scope
This provision directly governs Engineer B's obligation to protect confidential technical and business information of the Owner client.
Action
Confidential Review Assignment
This provision prohibits disclosing confidential technical or business information without consent, directly governing how a confidential review assignment must be handled.
State
Owner Covert Review Instruction
A covert review could result in Engineer B disclosing confidential technical information about Engineer A's work without proper consent.
Obligation (3)
  • Engineer B Confidentiality Review Scope
    This provision directly governs Engineer B's obligation to protect confidential technical and business information of the Owner client.
  • Engineer B Confidentiality Scope Limit
    This provision defines the confidentiality duty whose limits are at issue regarding whether concealing the review's existence is required.
  • Engineer B Confidential Review Safety Disclosure
    This provision establishes the confidentiality baseline against which safety disclosure obligations must be weighed.
Action (1)
  • Confidential Review Assignment
    This provision prohibits disclosing confidential technical or business information without consent, directly governing how a confidential review assignment must be handled.
State (3)
  • Owner Covert Review Instruction
    A covert review could result in Engineer B disclosing confidential technical information about Engineer A's work without proper consent.
  • Engineer B Covert Review Instruction
    Engineer B conducting a review without Engineer A's knowledge risks exposing confidential technical processes without consent.
  • Engineer A Engineer B Relationship
    The peer review relationship involves access to confidential design information that must be handled in accordance with this provision.
Constraint (2)
  • Engineer B Confidentiality Review Scope
    This provision directly establishes the confidentiality obligation restricting Engineer B from disclosing the Owner's technical and business information obtained during the peer review.
  • Engineer B Confidentiality Safety Override
    This provision creates the confidentiality constraint that must be navigated when Engineer B discovers safety violations during the peer review.
Principle (2)
  • Engineer B Confidentiality Review Scope
    This provision directly governs Engineer B's duty not to disclose confidential information about the Owner's technical processes without consent.
  • Owner Client Loyalty Limits Engineer B
    Engineer B's confidentiality obligation to the Owner is grounded in this provision, defining the legitimate scope of client loyalty.
Role (1)
  • Engineer B Peer Reviewer
    Engineer B gained access to Engineer A's confidential technical plans and processes and was obligated not to disclose them without consent.
Event (2)
  • Design Errors Discovered
    Information about design errors constitutes confidential technical data that must not be disclosed without client consent.
  • Notification Obligation Triggered
    The notification obligation must be weighed against the duty to protect confidential business and technical information of the client.
Resource (1)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code of Ethics framework used to assess Engineer B's obligations regarding confidential technical information encountered during the peer review.
Capability (2)
  • Engineer B Confidentiality Scope Reasoning
    This provision directly requires Engineer B to reason about the scope of confidentiality obligations regarding the Owner's technical and business information.
  • Engineer B Safety Disclosure Escalation
    The escalation sequence for safety concerns must be weighed against the prohibition on disclosing confidential client information without consent.
III.7.a. 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.
How this applies in the case (showing 3 of 40)
Obligation
Engineer B Peer Review Knowledge
This provision directly requires that Engineer A have knowledge of the peer review before Engineer B commences it.
Action
Confidential Review Assignment
This provision directly governs the conditions under which an engineer may be assigned to review another engineers work for the same client.
State
Engineer B Covert Review Instruction
This provision directly prohibits Engineer B from reviewing Engineer A's work without Engineer A's knowledge, which is exactly what the Owner instructed.
Obligation (6)
  • Engineer B Peer Review Knowledge
    This provision directly requires that Engineer A have knowledge of the peer review before Engineer B commences it.
  • Engineer B Peer Review Notification
    This provision directly obligates Engineer B to notify Engineer A before reviewing Engineer A's work for the same client.
  • Engineer B Covert Review Refusal
    This provision directly prohibits conducting a review of another engineer's work without that engineer's knowledge, requiring refusal of the covert review instruction.
  • Engineer B Client Instruction Limits
    This provision establishes that client instructions cannot override the requirement to notify the engineer whose work is being reviewed.
  • Owner Peer Review Notification Consent
    This provision requires that the Owner agree to notify Engineer A as a precondition for the peer review to proceed ethically.
  • Engineer A Professional Accountability Cooperation
    This provision implies Engineer A has a right to knowledge of the review, making cooperation an informed professional obligation.
Action (4)
  • Confidential Review Assignment
    This provision directly governs the conditions under which an engineer may be assigned to review another engineers work for the same client.
  • Peer Review Refusal
    This provision provides the basis for refusing a peer review if the original engineer has not been notified or their connection to the work has not been terminated.
  • Notification Consent
    This provision requires that the original engineer have knowledge of the review, making notification consent a direct requirement before proceeding.
  • Peer Review Consent Refusal
    This provision governs the situation where consent for the peer review is refused, as the review cannot proceed without the original engineers knowledge.
State (6)
  • Engineer B Covert Review Instruction
    This provision directly prohibits Engineer B from reviewing Engineer A's work without Engineer A's knowledge, which is exactly what the Owner instructed.
  • Owner Covert Review Instruction
    The Owner's instruction to conduct a covert review conflicts directly with the prohibition on reviewing another engineer's work without their knowledge.
  • Engineer A Engineer B Relationship
    The peer review engagement between Engineer B and the Owner is the precise scenario governed by this provision requiring Engineer A's knowledge.
  • Present Case Peer Review Consent Refused
    Engineer A's refusal to consent creates the condition under which Engineer B cannot ethically proceed with the review per this provision.
  • Engineer A Peer Review Refusal
    Engineer A's refusal to consent to the peer review directly triggers the applicability of this provision regarding review without knowledge or consent.
  • Engineer B Competing Review Duties
    This provision is central to Engineer B's competing obligations, as it restricts proceeding with review absent Engineer A's knowledge or termination of Engineer A's connection.
Constraint (5)
  • Engineer B Covert Review Prohibition
    This provision directly prohibits Engineer B from reviewing Engineer A's work without Engineer A's knowledge, establishing the covert review prohibition.
  • Engineer B Notification Procedural Requirement
    This provision directly creates the procedural requirement that Engineer B must notify Engineer A before commencing the peer review.
  • Engineer B Client Instruction Limit
    This provision limits the Owner's authority to instruct Engineer B to conduct a covert review by establishing a professional duty that overrides such instructions.
  • Engineer B Notification Sufficiency
    This provision requires notification of Engineer A but does not require consent, directly supporting the constraint that notification alone is sufficient for Engineer B to proceed.
  • Design-Build Contract Peer Review Consent
    This provision is the basis against which pre-authorized consent in design-build contracts is evaluated, as it normally requires engineer knowledge before review commences.
Principle (4)
  • Engineer B Transparency Notification
    This provision directly requires that Engineer B notify Engineer A before reviewing his work, which is exactly what Engineer B insisted upon.
  • Engineer B Collegial Notification Refusal
    Engineer B's refusal to conduct a covert review is a direct application of this provision requiring the original engineer's knowledge before review.
  • Owner Client Loyalty Limits Notification
    The owner's instruction to conceal the review from Engineer A directly violated this provision, exceeding permissible client direction.
  • Engineer A Cooperation Duty
    This provision implies that Engineer A, once notified, had a corresponding professional duty to cooperate with the properly initiated peer review.
Role (3)
  • Engineer B Peer Reviewer
    Engineer B was reviewing the work of Engineer A for the same client, which required knowledge or notification of Engineer A before proceeding.
  • Engineer B Peer Review Engineer
    Engineer B objected to performing the review without notifying Engineer A, directly invoking this provision governing review of another engineer's work.
  • Engineer A Design Engineer
    Engineer A is the engineer whose work was subject to peer review, and this provision protects Engineer A's right to be notified of such review.
Event (3)
  • Peer Review Blocked
    The provision directly governs the conditions under which a peer review of another engineer's work may be conducted, making it central to the blocking of that review.
  • Second Tower Design Unreviewed
    This provision addresses whether the reviewer may proceed to review the second tower without the original engineer's knowledge or consent.
  • Notification Obligation Triggered
    The requirement to have knowledge of or termination of the original engineer's connection implies a notification obligation before proceeding with review.
Resource (2)
  • NSPE Code Professional Obligation III.7.a
    This provision is directly cited as the controlling rule requiring Engineer B to notify Engineer A before conducting the peer review for the same client.
  • NSPE Code of Ethics
    This provision is part of the NSPE Code of Ethics which provides the normative framework for evaluating Engineer B's obligation to notify Engineer A.
Capability (7)
  • Engineer B Peer Review Protocol
    This provision is the direct source of the notification requirement that Engineer B's peer review protocol knowledge is built upon.
  • Engineer B Peer Review Protocol Competence
    Engineer B's technical and procedural knowledge of peer review standards including the notification requirement is a direct application of this provision.
  • Engineer B Situational Awareness Covert Review
    Engineer B's recognition that a covert review is ethically problematic is grounded directly in the prohibition stated in this provision.
  • Engineer B Justification Refusal
    Engineer B's principled reasoning for refusing the covert review traces directly to the authoritative norm established by this provision.
  • Engineer B Ethical Reasoning Review Refusal
    The ethical conflict Engineer B deliberated on is defined by this provision's requirement that the original engineer be notified before review proceeds.
  • Engineer A Peer Review Cooperation
    This provision implies that once notified, the original engineer has a corresponding obligation to cooperate with the legitimate peer review.
  • Engineer B Precedent Application
    Engineer B's application of prior BER rulings to determine proper conduct is grounded in the professional norm codified in this provision.
Cross-Case Connections
View Extraction
Explicit 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:

A peer reviewer who discovers potential safety code violations must first discuss concerns with the engineer being reviewed, and if unresolved, must advise that engineer of the obligation to inform authorities and then do so.

Citation Context:

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

Relevant Excerpts
discussion: "In BER Case 96-8, Engineer A was a peer reviewer serving as part of an organized peer-review program. When selected as a reviewer for the program, Engineer A contractually agreed not to disclose confidential information acquired in the review."
discussion: "The BER concluded that Engineer A had an obligation to immediately discuss these issues with Engineer B in order to seek clarification and resolution...and then to so inform the appropriate authorities."

Principle Established:

So long as the agency approves and the work complies with applicable state laws and regulations regarding conflicts of interest, it is not unethical for an engineer who conducted a peer review to later participate in a design-build joint venture submitting a proposal for the same project.

Citation Context:

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.

Relevant Excerpts
discussion: "In BER Case 18-10, Engineer A was the lead engineer on an independent external review of an agency-prepared project. The review's scope was limited to clarifications and refinements, and there was no confidentiality agreement."
discussion: "In Case 18-10, the Board concluded that, so long as the agency approves and the work complies with applicable state laws and regulations regarding conflicts of interest, it would not be unethical for Engineer A's firm to participate in a design-build joint venture submitting a proposal for the project."

Principle Established:

A prior case addressed the scenario where an owner refused to advise the engineer whose work was being reviewed of the planned peer review.

Citation Context:

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

Relevant Excerpts
discussion: "Owner reluctantly agreed to advise Engineer A of the planned peer review. [93-3 discussed a situation in which the Owner refused to advise the engineer of the planned peer review.]"
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 58% Facts Similarity 40% Discussion Similarity 68% Provision Overlap 56% Outcome Alignment 100% Tag Overlap 71%
Shared provisions: I.1, II.1.a, II.1.f, III.1.b, III.4 Same outcome True View Synthesis
Component Similarity 54% Facts Similarity 28% Discussion Similarity 35% Provision Overlap 62% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.a, II.1.f, III.1.b, III.4 Same outcome True View Synthesis
Component Similarity 70% Facts Similarity 52% Discussion Similarity 78% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 57%
Shared provisions: I.1, II.1.a, III.4 Same outcome True View Synthesis
Component Similarity 66% Facts Similarity 48% Discussion Similarity 47% Provision Overlap 22% Outcome Alignment 100% Tag Overlap 67%
Shared provisions: I.1, III.7.a Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 51% Discussion Similarity 55% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.1, II.1.a, II.1.f Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 42% Discussion Similarity 49% Provision Overlap 36% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.a, III.1.b, III.4 Same outcome True View Synthesis
Component Similarity 47% Facts Similarity 29% Discussion Similarity 50% Provision Overlap 44% Outcome Alignment 100% Tag Overlap 57%
Shared provisions: I.1, II.1.a, III.1.b, III.4 Same outcome True View Synthesis
Component Similarity 57% Facts Similarity 37% Discussion Similarity 31% Provision Overlap 38% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.1, II.1.a, III.1.b Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 48% Discussion Similarity 39% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 30%
Shared provisions: I.1, II.1.a, III.1.b Same outcome True View Synthesis
Component Similarity 56% Facts Similarity 40% Discussion Similarity 37% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.1, II.1.a, III.1.b Same outcome True View Synthesis
Questions & Conclusions (2 board)
View Extraction
Board Board question 1

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

Board conclusion Engineer B is ethically required to make certain that Engineer A is advised of the planned peer review.
Implicit (4)

If 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?

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

Does 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?

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

What 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?

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

Should 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?

AnalyticalIn 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.
AnalyticalThe 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.
Board Board question 2

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

The Board did not provide a conclusion specific to this question. The Discussion section covers the Board’s reasoning across all questions.

Principle tension (4)

Does 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?

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

Does 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?

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

How 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?

Does 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?

AnalyticalThe 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.
Cross-cutting analytical questions (8)

These questions consider the case as a whole rather than a specific board question above.

Theoretical (4)

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

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

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

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

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

Counterfactual (4)

If 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?

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

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, would the ethical obligations of Engineer B and the Owner regarding notification and consent have been materially different?

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

If 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?

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

If 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?

AnalyticalIn 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.
Decisions & Arguments (5)
View Extraction

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?

Options considered:
O1 Provide all requested documentation, access, and acknowledgment of prior errors to the peer reviewer, treating the review as a legitimate professional accountability measure regardless of whether it was anticipated in the original engagement. Board's choice
O2 Engage with the peer review process only after negotiating a written scope agreement that defines what materials will be reviewed, how findings will be used, and what confidentiality protections apply, on the grounds that structured cooperation protects all parties.
O3 Refuse to participate until the review is formally authorized through the original client contract or a new written agreement, arguing that an engineer is not obligated to submit work to an unilaterally imposed review outside the agreed engagement terms.
Argument structure:
Warrants

Professional accountability norms require engineers to support legitimate quality assurance processes, especially where prior errors have been established. The obligation to hold public safety paramount supports cooperation with safety-related reviews. Competing considerations include Engineer A's possible belief that the review was unauthorized, covert, or outside the contractual scope, and that cooperation could expose Engineer A to liability.

Rebuttals

Engineer A may have had reasonable grounds to question whether the peer review was properly authorized or whether its scope was defined. If the review was initiated without Engineer A's knowledge or consent, the refusal could be framed as a boundary-setting response rather than an ethical violation. The intermediate proficiency ratings for Engineer A's accountability judgment and peer review cooperation suggest genuine uncertainty about the norms governing this situation.

Grounds

Engineer A had produced prior work containing significant errors. The owner or client initiated a peer review as a quality assurance measure. Engineer A refused to cooperate with the review process, declining to provide access, documentation, or acknowledgment of prior errors. Multiple obligations related to peer review cooperation, error acknowledgment, and safety review consent were found unmet.

Engineer A Professional Accountability Cooperation

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?

Options considered:
O1 Report safety-relevant design errors to the appropriate parties beyond the commissioning client, treating the duty to protect public safety as a limit on the scope of peer review confidentiality obligations. Board's choice
O2 Deliver all findings, including safety-relevant errors, solely to the client who commissioned the review, on the grounds that the client is the appropriate party to decide on remediation and further disclosure.
O3 Present safety findings to the client and formally request authorization to disclose to additional parties, treating client consent as a prerequisite to broader disclosure except in cases of imminent danger.
Argument structure:
Warrants

Engineers owe confidentiality to clients regarding proprietary information and review findings. However, the paramount duty to protect public safety overrides confidentiality when design errors create genuine safety risks. The peer review confidentiality scope obligation recognizes that confidentiality is not absolute and does not extend to concealing safety hazards from those who need to act on them.

Rebuttals

The scope of the safety risk may be disputed. If the errors were significant but not immediately life-threatening, Engineer B might reasonably conclude that reporting to the client alone was sufficient. The intermediate proficiency rating for Engineer B's confidentiality scope reasoning suggests this was a genuinely difficult judgment call rather than a clear-cut case.

Grounds

Engineer B was engaged to conduct a peer review and discovered significant errors in Engineer A's design work. The client who commissioned the review may have instructed Engineer B to keep findings confidential. Engineer B's obligations related to confidentiality scope, safety disclosure escalation, and client instruction limits were all found met, indicating Engineer B navigated these tensions appropriately.

Peer Review Confidentiality Scope Obligation

Should Engineer A consent to and cooperate with the peer safety review of the design, or refuse to participate in the review process?

Options considered:
O1 Engineer A grants consent to the peer safety review and provides full access to design documents, calculations, and relevant records, treating the review as a legitimate professional accountability mechanism. Board's choice
O2 Engineer A declines to consent to or cooperate with the peer review, asserting that the original design authority rests with the design engineer and that unsolicited review is not professionally required.
O3 Engineer A agrees to participate in the review but negotiates limits on scope, requiring that only specific safety-critical elements be examined and that proprietary design methods remain protected.
Argument structure:
Warrants

Engineers hold a paramount duty to protect public safety, which includes submitting to legitimate peer review when safety concerns arise. Professional accountability norms require cooperation with oversight processes. Competing considerations include Engineer A's interest in protecting professional reputation, potential client instructions limiting disclosure, and the view that unsolicited peer review may encroach on the original engineer's authority.

Rebuttals

Engineer A may argue that consent was not properly sought, that the review process was initiated without adequate notice, or that cooperation would expose proprietary design information. The intermediate proficiency rating suggests Engineer A may genuinely misunderstand the scope of the cooperation duty rather than willfully refusing it.

Grounds

A peer safety review of Engineer A's design has been initiated. Engineer A's obligations of professional accountability cooperation and safety review consent are both recorded as unmet. Engineer A has intermediate proficiency in peer review cooperation and safety review consent judgment, suggesting awareness of the duty but failure to act on it.

Professional Accountability Cooperation Obligation

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?

Options considered:
O1 Engineer B accepts the confidential review assignment but explicitly reserves the right to disclose any findings that implicate public safety, notifying the client in advance that safety-critical findings cannot be suppressed by confidentiality terms. Board's choice
O2 Engineer B declines the assignment on the grounds that the client's confidentiality restrictions are incompatible with the engineer's duty to report safety hazards, and recommends the client engage a reviewer under terms that permit full disclosure.
O3 Engineer B accepts the assignment and conducts the review strictly within the confidentiality scope defined by the client, treating the client's instructions as binding and limiting any report to findings the client has authorized for disclosure.
Argument structure:
Warrants

Engineers must hold public safety paramount and cannot allow client-imposed confidentiality to suppress disclosure of safety-critical findings. At the same time, engineers have legitimate duties of confidentiality to clients and may accept assignments with reasonable scope limitations. The tension is between honoring client confidentiality instructions and ensuring that a safety review is not rendered meaningless by restrictions that prevent reporting genuine hazards.

Rebuttals

A reasonable engineer might accept confidentiality conditions if they are limited to protecting proprietary methods rather than suppressing safety findings. Engineer B's advanced proficiency suggests the ability to distinguish permissible confidentiality from impermissible suppression, and the board found Engineer B's conduct met the relevant obligations, indicating the restrictions were navigated appropriately.

Grounds

Engineer B has been assigned a peer review under conditions set by the client that impose confidentiality restrictions on the scope of findings that may be disclosed. Engineer B's obligations regarding client instruction limits and confidentiality review scope are both recorded as met, and Engineer B demonstrates advanced proficiency in client instruction boundary reasoning, covert review situational awareness, and safety disclosure escalation.

Engineer B Confidentiality Review Scope Engineer B Client Instruction Limits

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?

Options considered:
O1 Provide the owner with full notification of the peer review findings, including identified design errors that carry safety implications, regardless of client instructions to limit disclosure. Board's choice
O2 Restrict notification to the owner to only those findings the client has authorized for disclosure, honoring the confidentiality boundaries established in the peer review engagement agreement.
O3 Pause notification to the owner and first seek explicit client consent to expand the disclosure scope to include safety-relevant findings, escalating only if consent is denied and safety risk is imminent.
Argument structure:
Warrants

Engineer B has a duty to protect public safety by ensuring the owner is informed of significant design errors. Simultaneously, the client may have instructed Engineer B to limit the scope of what is disclosed, creating tension between client confidentiality obligations and the duty to notify affected parties of safety-relevant findings.

Rebuttals

Engineer B might argue that full notification to the owner exceeds the agreed scope of the peer review engagement, or that the client retains authority over what information is shared with the owner, limiting Engineer B's independent disclosure authority.

Grounds

Engineer B has completed a peer review, identified design errors with potential safety implications, and has met obligations related to covert review refusal, confidentiality scope, and confidential review safety disclosure. The owner has consented to the peer review notification. Engineer B's proficiency in safety disclosure escalation and ethical reasoning is rated advanced.

Owner Peer Review Notification Consent
Event Timeline (8)
8 sequenced 4 actions 4 events
Case timeline
Significant design errors were found in Engineer A's plans during construction of the first tower, revealing deficiencies in the original engineering work.
Owner retains Engineer B to conduct a peer review of Engineer A's plans for the second tower, with explicit instructions to keep the review secret from Engineer A.
Violates (1)
  • Professional Obligation III.7.a
Once Engineer B was retained for the peer review, the professional obligation to notify Engineer A automatically came into force, preceding any further action by Engineer B.
Engineer B declines to proceed with the peer review under the condition that Engineer A not be notified, citing professional obligations that prohibit reviewing another engineer's work for the same client without that engineer's knowledge.
Fulfills (1)
  • Professional Obligation III.7.a
Owner reluctantly agrees to notify Engineer A that a peer review of the second tower plans will be conducted by Engineer B, after Engineer B objects to proceeding without disclosure.
Fulfills (1)
  • Professional Obligation III.7.a
After being notified of the planned peer review, Engineer A refuses to consent to Engineer B reviewing the second tower plans, effectively withholding cooperation from the process.
Violates (4)
  • Obligation to Hold Paramount Public Health Safety and Welfare
  • Obligation to Acknowledge Errors
  • Obligation to Act in Client Best Interests
  • Obligation to Take Responsibility for Professional Actions
The peer review of Engineer A's second-tower plans was effectively blocked after Engineer A refused to consent, leaving the review unable to proceed despite the owner's agreement to notify Engineer A.
As a consequence of the blocked peer review, the second tower's design by Engineer A remained unreviewed despite known deficiencies in the parallel first-tower plans.
Narrative (3 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are Engineer B, a licensed professional engineer retained by an owner to conduct a peer review of the structural plans and design prepared by Engineer A for the second of two mirror-image towers in a planned development. The owner sought this review after discovering several significant design errors in Engineer A's work on the first tower, which is currently under construction. The owner initially instructed you to conduct the review without informing Engineer A, a condition you refused to accept. After the owner agreed to notify Engineer A, Engineer A objected and declined to consent to the peer review. You must now work through a series of decisions about your obligations to the owner, to Engineer A, and to the public as you proceed.

Main characters (3)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Engineer B Roles in this case: hover for definitions Peer ReviewerPeer Review Engineer

Engineer B holds a professional obligation to notify Engineer A that a peer review is being conducted, because transparency between engineers is a foundational norm of peer review practice. At the same time, the client may instruct Engineer B to withhold that notification, and the client instruction override constraint limits how far Engineer B can deviate from client directives. This creates a direct conflict between the procedural duty owed to a fellow professional and the boundary set by client authority over the engagement.

Attaches to role: Peer Reviewer

Tension between Engineer B Confidentiality Review Scope and Engineer B Client Instruction Limits

Attaches to role: Peer Reviewer

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.

Attaches to role: Peer Reviewer

Engineer A carries an obligation to cooperate with the peer review process and acknowledge errors when they are identified. The competence defect acknowledgment constraint simultaneously limits Engineer A from denying or minimizing deficiencies that the review surfaces. In practice, professional self-interest and reputational concern can make genuine acknowledgment difficult, creating tension between the cooperative duty and the psychological and professional pressures that work against honest self-assessment. This tension is especially significant because unresolved errors may carry safety consequences for downstream parties.

Attaches to role: Peer Review Engineer
Engineer A Roles in this case: hover for definitions Design Engineer

Engineer B holds a professional obligation to notify Engineer A that a peer review is being conducted, because transparency between engineers is a foundational norm of peer review practice. At the same time, the client may instruct Engineer B to withhold that notification, and the client instruction override constraint limits how far Engineer B can deviate from client directives. This creates a direct conflict between the procedural duty owed to a fellow professional and the boundary set by client authority over the engagement.

Engineer A carries an obligation to cooperate with the peer review process and acknowledge errors when they are identified. The competence defect acknowledgment constraint simultaneously limits Engineer A from denying or minimizing deficiencies that the review surfaces. In practice, professional self-interest and reputational concern can make genuine acknowledgment difficult, creating tension between the cooperative duty and the psychological and professional pressures that work against honest self-assessment. This tension is especially significant because unresolved errors may carry safety consequences for downstream parties.

Owner Project Roles in this case: Owner

Engineer B holds a professional obligation to notify Engineer A that a peer review is being conducted, because transparency between engineers is a foundational norm of peer review practice. At the same time, the client may instruct Engineer B to withhold that notification, and the client instruction override constraint limits how far Engineer B can deviate from client directives. This creates a direct conflict between the procedural duty owed to a fellow professional and the boundary set by client authority over the engagement.

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.

Opening States (10)
Engineer B Competing Review Duties Engineer A Engineer B Relationship Covert Review Request State Peer Review Consent Refused State Owner Covert Review Instruction Engineer A Peer Review Refusal Engineer A Prior Design Errors Present Case Peer Review Consent Refused Engineer B Covert Review Instruction Engineer A Public Safety Risk
Summary
  • Professional transparency between engineers is not a courtesy but a binding ethical obligation that client instructions cannot override.
  • When confidentiality agreements conflict with foundational peer review norms, the engineer must resolve the conflict before accepting the engagement, not after discovering a problem mid-review.
  • The transfer principle here is that client authority over an engagement has real limits, and those limits are defined by the professional duties engineers owe to one another and to the public.

© Licensed under the GNU GPL v3 | Report Issue