Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainNode Types & Relationships
→ Question answered by Conclusion
→ Provision applies to Entity
NSPE Code Provisions Referenced
View ExtractionII.1.c. II.1.c.
Full Text:
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.
Relevant Case Excerpts:
"However, in view of the fact that drafters of the Code included separate provisions specifically addressing the obligations of engineers to not disclose confidential information (See Code Sections II.1.c., III.4."
Confidence: 75.0%
Applies To:
II.4. II.4.
Full Text:
Engineers shall act for each employer or client as faithful agents or trustees.
Relevant Case Excerpts:
"ments or suggestions for the benefit of the client." We believe the reasoning cited by the Board in BER Case 79-7 are as cogent today as they were when the Board issued its opinion. At the same time, Code Section II.4 places the obligation upon engineers to act in professional matters for clients as "faithful agents or trustees." An "agent" is generally defined as a "person authorized by another to act for him or"
Confidence: 95.0%
Applies To:
III.4. III.4.
Full Text:
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.
Relevant Case Excerpts:
"r, in view of the fact that drafters of the Code included separate provisions specifically addressing the obligations of engineers to not disclose confidential information (See Code Sections II.1.c., III.4."
Confidence: 75.0%
Applies To:
III.8.a. III.8.a.
Full Text:
Engineers shall conform with state registration laws in the practice of engineering.
Applies To:
Cited Precedent Cases
View ExtractionBER Case 79-7 supporting linked
Principle Established:
The purpose of Section III.8.a. (formerly Section 12(a)) is to provide the engineer whose work is being reviewed an opportunity to submit comments or explanations for technical decisions, enabling the reviewing engineer to have a fuller understanding of the original design.
Citation Context:
The Board cited this case to establish the purpose of Section III.8.a., which requires an engineer to notify the original engineer when reviewing their work, giving the original engineer an opportunity to provide comments or explanations for technical decisions. It is cited multiple times to both support and frame the analysis of Engineer B's obligations.
Relevant Excerpts:
"In BER Case 79-7, an engineer was asked to inspect mechanical and electrical engineering work performed seven years earlier. The Board concluded that the engineer notified the former engineer that the engineer was being retained to perform review and inspection services..."
"We believe the reasoning cited by the Board in BER Case 79-7 are as cogent today as they were when the Board issued its opinion."
"In light of the facts and consistent with BER Case 79-7, we are persuaded that Engineer B acted unethically in notifying Engineer A of Engineer B's relationship with the client."
"Our conclusion is based upon the rationale cited above in BER Case 79-7 but is also based upon an analysis of the countervailing argument that Engineer B had an obligation as 'faithful agent and trustee'..."
Questions & Conclusions
View ExtractionQuestion 1 Board Question
Was Engineer B's act of notifying Engineer A of his relationship with franchiser consistent with the Code?
Engineer B's act of notifying Engineer A of his relationship with franchiser was not consistent with the Code.
Beyond the Board's finding that Engineer B's notification was inconsistent with the Code, the violation is compounded by Engineer B's failure to seek clarification of the franchiser's reasons for the confidentiality instruction before accepting the engagement. A competent and ethically attentive engineer, upon receiving an explicit client instruction to conceal a new engagement from an incumbent engineer whose work is about to be reviewed, should recognize that the instruction itself signals a potential conflict between faithful agency and peer review obligations. By accepting the engagement without inquiry, Engineer B foreclosed the possibility of negotiating a disclosure arrangement that might have satisfied both the franchiser's legitimate transition interests and the Code's peer review notification requirement. This pre-engagement failure of ethical diligence is analytically distinct from the notification timing violation the Board identified, and it represents an independent lapse that the Board's conclusion does not fully capture.
The Board's conclusion that Engineer B's notification violated the faithful agent duty treats the two competing Code obligations - faithful agency to the franchiser and peer review notification to Engineer A - as though the faithful agent duty categorically prevails. However, a more nuanced reading reveals that the Code's faithful agent standard is expressly bounded by ethical limits: engineers act as faithful agents 'within the limits of the Code.' This internal qualification means the faithful agent duty cannot be invoked to authorize a client instruction that itself directs an engineer to violate a separate Code provision. The franchiser's confidentiality instruction was not a neutral business preference but an affirmative direction to suppress a disclosure the Code independently requires. Accordingly, the faithful agent principle, properly construed, does not support the franchiser's instruction; rather, the instruction falls outside the scope of conduct the faithful agent duty is designed to protect. The Board's conclusion, while correct that the notification's timing and manner were imperfect, may overstate the weight of the faithful agent duty by failing to account for its built-in ethical ceiling.
Across both Board conclusions, the franchiser's own ethical position remains unexamined. The franchiser affirmatively instructed Engineer B to conceal the new engagement from Engineer A - an instruction that, if followed, would have required Engineer B to conduct a covert peer review in direct violation of the Code's peer review notification standard. A client that knowingly directs an engineer to violate a Code provision is not merely a passive beneficiary of an engineer's ethical lapse; it is an active participant in the creation of the ethical conflict. While the Code's obligations run primarily to engineers rather than clients, the principle that client direction does not authorize ethical violations implies a correlative responsibility on the client's part not to issue instructions designed to circumvent professional ethical standards. The franchiser's covert review instruction should therefore be identified as an ethically impermissible client act that contributed materially to the conflict Engineer B faced, and future Board guidance should consider whether engineers have an affirmative obligation to refuse such instructions at the point of engagement rather than navigate the resulting conflict after the fact.
The Board's conclusion that Engineer B's notification was inconsistent with the Code does not address the separate and aggravating ethical dimension introduced by Engineer B's simultaneous disclosure of the preliminary review results to Engineer A. Even if some form of notification to Engineer A could have been ethically required or permissible under the peer review provisions, the disclosure of substantive preliminary findings went materially beyond what any notification obligation demands. The peer review notification requirement is designed to protect Engineer A's professional dignity and opportunity to respond - not to authorize the transmission of work-product conclusions derived from a confidential client engagement. By sharing preliminary results, Engineer B exposed the franchiser's confidential design concerns without authorization, compounding the faithful agent violation with an independent breach of client confidentiality. This dual disclosure - of the engagement relationship and of the review findings - should be treated as two analytically separable acts, each warranting its own ethical assessment, rather than as a single undifferentiated notification event.
The central principle tension in this case - between the faithful agent duty owed to the franchiser and the peer review notification obligation owed to Engineer A - was resolved by the Board in favor of the faithful agent duty, but only partially and without full consensus. The Board concluded that Engineer B's notification violated the faithful agent obligation, yet could not agree on whether proceeding with the review at that time was itself ethical. This split outcome reveals that the two principles were not genuinely reconciled; rather, the Board prioritized client loyalty on the disclosure question while leaving unresolved the deeper question of whether the entire engagement structure was permissible. The case teaches that when two Code provisions point in directly opposite directions - one commanding disclosure, the other forbidding it - the Code does not supply a clear lexical ordering, and the Board's inability to reach consensus on Q2 is itself evidence that the faithful agent principle cannot categorically override peer review notification norms without remainder. The unresolved tension suggests that the Code implicitly requires engineers to avoid accepting engagements structured so as to make compliance with both provisions simultaneously impossible.
The principle that a client's direction does not authorize an ethical violation - which the Board invoked to explain why Engineer B could not simply remain silent indefinitely - ultimately failed to resolve the conflict because the Board simultaneously applied the faithful agent principle to condemn the very notification that the first principle appeared to require. This internal contradiction exposes a structural gap in the Code: the 'client direction cannot override ethics' principle presupposes that the competing ethical obligation is unambiguous and superior, but where two Code provisions are in genuine equipoise, invoking one to override the other merely restates the problem rather than solving it. The case therefore teaches that the 'client direction does not authorize ethical violation' principle functions as a trump only when the competing obligation is clearly established and hierarchically superior - conditions that were not fully met here, given the Board's split on Q2. The more durable lesson is that Engineer B's pre-engagement failure to seek clarification of the franchiser's reasons for the confidentiality instruction was the point at which the conflict could have been avoided, and the Code's pre-engagement clarification obligation should be understood as the primary mechanism for preventing irreconcilable dual-provision conflicts from arising at all.
The principle of professional dignity for the incumbent engineer - which underlies the peer review notification requirement - was effectively subordinated to client loyalty in the Board's resolution of Q1, but this subordination was not cost-free and carries a systemic implication the Board did not fully articulate. When client confidentiality is permitted to override the incumbent engineer's right to know that their work is under review, the peer review process is transformed from a collegial professional improvement mechanism into a covert competitive intelligence tool available to clients willing to instruct successor engineers to remain silent. The franchiser's use of the transition overlap period to conduct a review without Engineer A's knowledge exploited the at-will employment symmetry principle - the franchiser's legitimate right not to renew - to circumvent the procedural protections that the notification timing requirement exists to provide. The case teaches that professional dignity and peer review procedural fairness cannot be indefinitely subordinated to client loyalty without hollowing out the peer review system's foundational purpose, and that the Code's peer notification obligation should be understood as a non-waivable professional duty that clients may not contractually or instructionally override, even if the faithful agent duty otherwise requires deference to client direction on confidentiality matters.
Question 2 Board Question
Was it ethical for Engineer B to proceed with the review at that time?
The Board was split on the second question and could not reach agreement.
The Board's conclusion that Engineer B's notification violated the faithful agent duty treats the two competing Code obligations - faithful agency to the franchiser and peer review notification to Engineer A - as though the faithful agent duty categorically prevails. However, a more nuanced reading reveals that the Code's faithful agent standard is expressly bounded by ethical limits: engineers act as faithful agents 'within the limits of the Code.' This internal qualification means the faithful agent duty cannot be invoked to authorize a client instruction that itself directs an engineer to violate a separate Code provision. The franchiser's confidentiality instruction was not a neutral business preference but an affirmative direction to suppress a disclosure the Code independently requires. Accordingly, the faithful agent principle, properly construed, does not support the franchiser's instruction; rather, the instruction falls outside the scope of conduct the faithful agent duty is designed to protect. The Board's conclusion, while correct that the notification's timing and manner were imperfect, may overstate the weight of the faithful agent duty by failing to account for its built-in ethical ceiling.
The Board's split on whether Engineer B could ethically proceed with the review at the time he did reflects a genuine and unresolved tension between two legitimate Code interests, but the split itself obscures an important structural point: the ethical permissibility of proceeding with the review was not independent of the notification question. If Engineer B was obligated to notify Engineer A before conducting the review - as the peer review notification standard suggests - then proceeding with the review before providing that notification was itself ethically impermissible, regardless of whether the subsequent notification partially remedied the procedural defect. The Board's inability to reach agreement on Q2 may stem from treating the two questions as analytically separable when they are in fact sequentially dependent: the answer to Q1 (notification timing) logically constrains the answer to Q2 (permissibility of proceeding). A finding that pre-review notification was required necessarily implies that conducting the review without it was premature and therefore impermissible under the Code.
Across both Board conclusions, the franchiser's own ethical position remains unexamined. The franchiser affirmatively instructed Engineer B to conceal the new engagement from Engineer A - an instruction that, if followed, would have required Engineer B to conduct a covert peer review in direct violation of the Code's peer review notification standard. A client that knowingly directs an engineer to violate a Code provision is not merely a passive beneficiary of an engineer's ethical lapse; it is an active participant in the creation of the ethical conflict. While the Code's obligations run primarily to engineers rather than clients, the principle that client direction does not authorize ethical violations implies a correlative responsibility on the client's part not to issue instructions designed to circumvent professional ethical standards. The franchiser's covert review instruction should therefore be identified as an ethically impermissible client act that contributed materially to the conflict Engineer B faced, and future Board guidance should consider whether engineers have an affirmative obligation to refuse such instructions at the point of engagement rather than navigate the resulting conflict after the fact.
The Board's split on Q2 also fails to address the independent ethical concern raised by Engineer B's subsequent acceptance of the full design engineering contract with the franchiser - a contract obtained in part through knowledge and professional positioning gained during the covert peer review. Even if the Board were to conclude that proceeding with the review was permissible under some reading of the Code, the peer review program's foundational purpose is collegial improvement of engineering practice, not competitive intelligence gathering. When a reviewing engineer leverages the peer review engagement to secure a successor contract - particularly one that displaces the very engineer whose work was reviewed - the review process is structurally transformed from a collegial quality-assurance mechanism into a client-directed competitive evaluation. This exploitation of the peer review framework for procurement advantage raises an independent ethical concern that neither the Board's Q1 conclusion nor its Q2 deliberations explicitly address, and it warrants separate analysis under the provisions governing engineer solicitation and competition ethics.
The central principle tension in this case - between the faithful agent duty owed to the franchiser and the peer review notification obligation owed to Engineer A - was resolved by the Board in favor of the faithful agent duty, but only partially and without full consensus. The Board concluded that Engineer B's notification violated the faithful agent obligation, yet could not agree on whether proceeding with the review at that time was itself ethical. This split outcome reveals that the two principles were not genuinely reconciled; rather, the Board prioritized client loyalty on the disclosure question while leaving unresolved the deeper question of whether the entire engagement structure was permissible. The case teaches that when two Code provisions point in directly opposite directions - one commanding disclosure, the other forbidding it - the Code does not supply a clear lexical ordering, and the Board's inability to reach consensus on Q2 is itself evidence that the faithful agent principle cannot categorically override peer review notification norms without remainder. The unresolved tension suggests that the Code implicitly requires engineers to avoid accepting engagements structured so as to make compliance with both provisions simultaneously impossible.
The principle that a client's direction does not authorize an ethical violation - which the Board invoked to explain why Engineer B could not simply remain silent indefinitely - ultimately failed to resolve the conflict because the Board simultaneously applied the faithful agent principle to condemn the very notification that the first principle appeared to require. This internal contradiction exposes a structural gap in the Code: the 'client direction cannot override ethics' principle presupposes that the competing ethical obligation is unambiguous and superior, but where two Code provisions are in genuine equipoise, invoking one to override the other merely restates the problem rather than solving it. The case therefore teaches that the 'client direction does not authorize ethical violation' principle functions as a trump only when the competing obligation is clearly established and hierarchically superior - conditions that were not fully met here, given the Board's split on Q2. The more durable lesson is that Engineer B's pre-engagement failure to seek clarification of the franchiser's reasons for the confidentiality instruction was the point at which the conflict could have been avoided, and the Code's pre-engagement clarification obligation should be understood as the primary mechanism for preventing irreconcilable dual-provision conflicts from arising at all.
The principle of professional dignity for the incumbent engineer - which underlies the peer review notification requirement - was effectively subordinated to client loyalty in the Board's resolution of Q1, but this subordination was not cost-free and carries a systemic implication the Board did not fully articulate. When client confidentiality is permitted to override the incumbent engineer's right to know that their work is under review, the peer review process is transformed from a collegial professional improvement mechanism into a covert competitive intelligence tool available to clients willing to instruct successor engineers to remain silent. The franchiser's use of the transition overlap period to conduct a review without Engineer A's knowledge exploited the at-will employment symmetry principle - the franchiser's legitimate right not to renew - to circumvent the procedural protections that the notification timing requirement exists to provide. The case teaches that professional dignity and peer review procedural fairness cannot be indefinitely subordinated to client loyalty without hollowing out the peer review system's foundational purpose, and that the Code's peer notification obligation should be understood as a non-waivable professional duty that clients may not contractually or instructionally override, even if the faithful agent duty otherwise requires deference to client direction on confidentiality matters.
Question 3 Implicit
Was it ethical for Engineer B to accept the franchiser's engagement at all without first seeking clarification of the reason behind the instruction not to disclose the relationship to Engineer A, given that the confidentiality instruction itself signaled a potential conflict with peer review obligations?
Beyond the Board's finding that Engineer B's notification was inconsistent with the Code, the violation is compounded by Engineer B's failure to seek clarification of the franchiser's reasons for the confidentiality instruction before accepting the engagement. A competent and ethically attentive engineer, upon receiving an explicit client instruction to conceal a new engagement from an incumbent engineer whose work is about to be reviewed, should recognize that the instruction itself signals a potential conflict between faithful agency and peer review obligations. By accepting the engagement without inquiry, Engineer B foreclosed the possibility of negotiating a disclosure arrangement that might have satisfied both the franchiser's legitimate transition interests and the Code's peer review notification requirement. This pre-engagement failure of ethical diligence is analytically distinct from the notification timing violation the Board identified, and it represents an independent lapse that the Board's conclusion does not fully capture.
In response to Q101: Engineer B's acceptance of the franchiser's engagement without first seeking clarification of the reason behind the confidentiality instruction was itself an ethically deficient act, independent of the subsequent notification violation. The confidentiality instruction was facially anomalous - a client directing a successor engineer not to inform the incumbent engineer of a peer review engagement is precisely the kind of instruction that signals a potential conflict with professional obligations. A competent engineer exercising reasonable professional judgment should have recognized that the instruction could not be reconciled with the peer review notification obligation under Section III.8.a without further inquiry. By proceeding without clarification, Engineer B effectively accepted a structurally compromised engagement from the outset, foreclosing the possibility of negotiating terms that might have honored both the faithful agent duty and the peer notification obligation simultaneously. The failure to inquire is not merely a procedural lapse; it reflects an absence of the proactive ethical vigilance the Code expects of engineers when client instructions appear to conflict with professional duties.
The principle that a client's direction does not authorize an ethical violation - which the Board invoked to explain why Engineer B could not simply remain silent indefinitely - ultimately failed to resolve the conflict because the Board simultaneously applied the faithful agent principle to condemn the very notification that the first principle appeared to require. This internal contradiction exposes a structural gap in the Code: the 'client direction cannot override ethics' principle presupposes that the competing ethical obligation is unambiguous and superior, but where two Code provisions are in genuine equipoise, invoking one to override the other merely restates the problem rather than solving it. The case therefore teaches that the 'client direction does not authorize ethical violation' principle functions as a trump only when the competing obligation is clearly established and hierarchically superior - conditions that were not fully met here, given the Board's split on Q2. The more durable lesson is that Engineer B's pre-engagement failure to seek clarification of the franchiser's reasons for the confidentiality instruction was the point at which the conflict could have been avoided, and the Code's pre-engagement clarification obligation should be understood as the primary mechanism for preventing irreconcilable dual-provision conflicts from arising at all.
Question 4 Implicit
Did the franchiser itself act unethically by instructing Engineer B to conceal the new engagement from Engineer A, and does the Code impose any obligation on a client not to direct engineers to violate peer review procedural fairness norms?
The Board's conclusion that Engineer B's notification violated the faithful agent duty treats the two competing Code obligations - faithful agency to the franchiser and peer review notification to Engineer A - as though the faithful agent duty categorically prevails. However, a more nuanced reading reveals that the Code's faithful agent standard is expressly bounded by ethical limits: engineers act as faithful agents 'within the limits of the Code.' This internal qualification means the faithful agent duty cannot be invoked to authorize a client instruction that itself directs an engineer to violate a separate Code provision. The franchiser's confidentiality instruction was not a neutral business preference but an affirmative direction to suppress a disclosure the Code independently requires. Accordingly, the faithful agent principle, properly construed, does not support the franchiser's instruction; rather, the instruction falls outside the scope of conduct the faithful agent duty is designed to protect. The Board's conclusion, while correct that the notification's timing and manner were imperfect, may overstate the weight of the faithful agent duty by failing to account for its built-in ethical ceiling.
Across both Board conclusions, the franchiser's own ethical position remains unexamined. The franchiser affirmatively instructed Engineer B to conceal the new engagement from Engineer A - an instruction that, if followed, would have required Engineer B to conduct a covert peer review in direct violation of the Code's peer review notification standard. A client that knowingly directs an engineer to violate a Code provision is not merely a passive beneficiary of an engineer's ethical lapse; it is an active participant in the creation of the ethical conflict. While the Code's obligations run primarily to engineers rather than clients, the principle that client direction does not authorize ethical violations implies a correlative responsibility on the client's part not to issue instructions designed to circumvent professional ethical standards. The franchiser's covert review instruction should therefore be identified as an ethically impermissible client act that contributed materially to the conflict Engineer B faced, and future Board guidance should consider whether engineers have an affirmative obligation to refuse such instructions at the point of engagement rather than navigate the resulting conflict after the fact.
In response to Q102: The franchiser's instruction to Engineer B to conceal the new engagement from Engineer A raises an independent ethical concern that the Board did not address. While the Code's explicit obligations fall on engineers rather than clients, the franchiser's instruction was designed to exploit the transitional overlap period to conduct a covert review of Engineer A's work while Engineer A's contract remained active and Engineer A remained professionally accountable for that work. By directing Engineer B to withhold information that the Code independently required Engineer B to disclose, the franchiser effectively attempted to use its contractual authority to engineer a violation of professional norms it had no standing to override. Although the Code does not directly impose obligations on clients as non-engineer parties, the principle that client direction does not authorize ethical violations implicitly recognizes that clients bear some responsibility for the consequences of instructions that predictably place engineers in ethical jeopardy. The franchiser's conduct was procedurally unfair to Engineer A and structurally incompatible with the peer review notification framework the Code establishes to protect incumbent engineers.
Question 5 Implicit
Should Engineer B have declined to share the preliminary results of his review with Engineer A at the time of notification, given that disclosing those results compounded the faithful agent violation by further exposing confidential client work product without authorization?
The Board's conclusion that Engineer B's notification was inconsistent with the Code does not address the separate and aggravating ethical dimension introduced by Engineer B's simultaneous disclosure of the preliminary review results to Engineer A. Even if some form of notification to Engineer A could have been ethically required or permissible under the peer review provisions, the disclosure of substantive preliminary findings went materially beyond what any notification obligation demands. The peer review notification requirement is designed to protect Engineer A's professional dignity and opportunity to respond - not to authorize the transmission of work-product conclusions derived from a confidential client engagement. By sharing preliminary results, Engineer B exposed the franchiser's confidential design concerns without authorization, compounding the faithful agent violation with an independent breach of client confidentiality. This dual disclosure - of the engagement relationship and of the review findings - should be treated as two analytically separable acts, each warranting its own ethical assessment, rather than as a single undifferentiated notification event.
In response to Q103: Engineer B's disclosure of the preliminary review results to Engineer A, in addition to disclosing the existence of the new engagement relationship, constituted a compounded violation of the faithful agent duty. The peer review notification obligation under Section III.8.a requires that the incumbent engineer be informed of the successor's engagement so that the incumbent may have an opportunity to respond to technical concerns - it does not independently authorize the successor engineer to share client work product or preliminary analytical conclusions without client consent. By disclosing both the relationship and the preliminary results, Engineer B exceeded what the notification obligation required and simultaneously deepened the breach of the confidentiality duty owed to the franchiser. A narrower disclosure - limited to the existence of the engagement and the fact of the review - would have more closely approximated compliance with Section III.8.a while minimizing the faithful agent violation. The disclosure of preliminary results thus represents an independent ethical misstep that cannot be justified by the peer notification rationale alone.
Question 6 Implicit
Does Engineer B's subsequent acceptance of the full design engineering contract with the franchiser - obtained in part through knowledge gained during the covert peer review - raise an independent ethical concern about exploitation of the peer review process for competitive advantage, regardless of whether the notification timing was ultimately reasonable?
The Board's split on whether Engineer B could ethically proceed with the review at the time he did reflects a genuine and unresolved tension between two legitimate Code interests, but the split itself obscures an important structural point: the ethical permissibility of proceeding with the review was not independent of the notification question. If Engineer B was obligated to notify Engineer A before conducting the review - as the peer review notification standard suggests - then proceeding with the review before providing that notification was itself ethically impermissible, regardless of whether the subsequent notification partially remedied the procedural defect. The Board's inability to reach agreement on Q2 may stem from treating the two questions as analytically separable when they are in fact sequentially dependent: the answer to Q1 (notification timing) logically constrains the answer to Q2 (permissibility of proceeding). A finding that pre-review notification was required necessarily implies that conducting the review without it was premature and therefore impermissible under the Code.
The Board's split on Q2 also fails to address the independent ethical concern raised by Engineer B's subsequent acceptance of the full design engineering contract with the franchiser - a contract obtained in part through knowledge and professional positioning gained during the covert peer review. Even if the Board were to conclude that proceeding with the review was permissible under some reading of the Code, the peer review program's foundational purpose is collegial improvement of engineering practice, not competitive intelligence gathering. When a reviewing engineer leverages the peer review engagement to secure a successor contract - particularly one that displaces the very engineer whose work was reviewed - the review process is structurally transformed from a collegial quality-assurance mechanism into a client-directed competitive evaluation. This exploitation of the peer review framework for procurement advantage raises an independent ethical concern that neither the Board's Q1 conclusion nor its Q2 deliberations explicitly address, and it warrants separate analysis under the provisions governing engineer solicitation and competition ethics.
In response to Q104: Engineer B's subsequent acceptance of the full design engineering contract with the franchiser raises an independent ethical concern that the Board did not resolve. The peer review process is designed to serve collegial improvement and public safety, not to function as a competitive audition for successor work. By conducting the review - even if the review itself was technically competent - Engineer B gained privileged access to Engineer A's design decisions, methodologies, and pending concerns under conditions that Engineer A did not know about and could not contest. This informational advantage, obtained through a process Engineer A had no opportunity to participate in or respond to, provided Engineer B with a structural competitive benefit in securing the successor contract. Even if Engineer B's acceptance of the successor contract was permissible under the Code's general provisions - given that Engineer A's contract had expired before Engineer B was formally retained as design engineer - the manner in which the review was conducted taints the legitimacy of that transition. The peer review program's integrity depends on successor engineers not exploiting the review process as a vehicle for competitive positioning, and Engineer B's trajectory from covert reviewer to successor contractor raises serious questions about whether that boundary was respected.
Question 7 Principle Tension
Does the principle that a client's direction does not authorize an ethical violation - invoked to justify Engineer B's notification of Engineer A - conflict with the faithful agent trustee duty invoked to prohibit that same disclosure, and if so, which principle should take precedence when the two Code provisions point in opposite directions?
In response to Q201: The conflict between the principle that client direction does not authorize ethical violations - invoked to justify Engineer B's notification of Engineer A - and the faithful agent trustee duty invoked to prohibit that same disclosure represents a genuine antinomy within the Code that the Board's split on Question 2 reflects but does not resolve. The more defensible resolution is that the faithful agent duty, properly understood, operates within ethical limits and cannot be construed to require an engineer to suppress a disclosure that the Code independently mandates. Section II.4 itself conditions the faithful agent obligation on consistency with ethical limits, meaning that the faithful agent duty is not absolute. However, this resolution does not fully vindicate Engineer B's conduct, because the notification as executed - disclosing preliminary results in addition to the relationship - exceeded what the competing obligation required. The correct hierarchy is: the peer notification obligation overrides the client confidentiality instruction as to the existence of the engagement, but the faithful agent duty continues to govern the scope of what may be disclosed, limiting Engineer B to the minimum disclosure necessary to honor the notification obligation.
The central principle tension in this case - between the faithful agent duty owed to the franchiser and the peer review notification obligation owed to Engineer A - was resolved by the Board in favor of the faithful agent duty, but only partially and without full consensus. The Board concluded that Engineer B's notification violated the faithful agent obligation, yet could not agree on whether proceeding with the review at that time was itself ethical. This split outcome reveals that the two principles were not genuinely reconciled; rather, the Board prioritized client loyalty on the disclosure question while leaving unresolved the deeper question of whether the entire engagement structure was permissible. The case teaches that when two Code provisions point in directly opposite directions - one commanding disclosure, the other forbidding it - the Code does not supply a clear lexical ordering, and the Board's inability to reach consensus on Q2 is itself evidence that the faithful agent principle cannot categorically override peer review notification norms without remainder. The unresolved tension suggests that the Code implicitly requires engineers to avoid accepting engagements structured so as to make compliance with both provisions simultaneously impossible.
The principle that a client's direction does not authorize an ethical violation - which the Board invoked to explain why Engineer B could not simply remain silent indefinitely - ultimately failed to resolve the conflict because the Board simultaneously applied the faithful agent principle to condemn the very notification that the first principle appeared to require. This internal contradiction exposes a structural gap in the Code: the 'client direction cannot override ethics' principle presupposes that the competing ethical obligation is unambiguous and superior, but where two Code provisions are in genuine equipoise, invoking one to override the other merely restates the problem rather than solving it. The case therefore teaches that the 'client direction does not authorize ethical violation' principle functions as a trump only when the competing obligation is clearly established and hierarchically superior - conditions that were not fully met here, given the Board's split on Q2. The more durable lesson is that Engineer B's pre-engagement failure to seek clarification of the franchiser's reasons for the confidentiality instruction was the point at which the conflict could have been avoided, and the Code's pre-engagement clarification obligation should be understood as the primary mechanism for preventing irreconcilable dual-provision conflicts from arising at all.
Question 8 Principle Tension
Does the principle of professional dignity for the incumbent engineer - which underlies the peer notification requirement - conflict with the principle of client loyalty invoked to constrain Engineer B's disclosure, and can professional dignity ever be subordinated to client confidentiality interests without undermining the foundational purpose of peer review?
In response to Q202: The principle of professional dignity for the incumbent engineer, which underlies the peer notification requirement, cannot be permanently subordinated to client confidentiality interests without fundamentally undermining the purpose of peer review. The peer review notification obligation exists precisely because engineers whose work is under review have a professional stake in that review - they may have information relevant to the reviewer's conclusions, they bear reputational consequences from the review's findings, and they are entitled to the opportunity to respond to technical concerns before those concerns are acted upon. A client confidentiality instruction that systematically overrides this notification right would reduce peer review to a covert audit mechanism, stripping it of the collegial character that distinguishes it from adversarial inspection. While client confidentiality is a legitimate and important Code value, it operates most forcefully with respect to business information, proprietary data, and client affairs - not with respect to the procedural rights of third-party engineers whose professional standing is directly implicated by the review. The professional dignity principle therefore represents a structural limit on the scope of client confidentiality instructions in peer review contexts.
The principle of professional dignity for the incumbent engineer - which underlies the peer review notification requirement - was effectively subordinated to client loyalty in the Board's resolution of Q1, but this subordination was not cost-free and carries a systemic implication the Board did not fully articulate. When client confidentiality is permitted to override the incumbent engineer's right to know that their work is under review, the peer review process is transformed from a collegial professional improvement mechanism into a covert competitive intelligence tool available to clients willing to instruct successor engineers to remain silent. The franchiser's use of the transition overlap period to conduct a review without Engineer A's knowledge exploited the at-will employment symmetry principle - the franchiser's legitimate right not to renew - to circumvent the procedural protections that the notification timing requirement exists to provide. The case teaches that professional dignity and peer review procedural fairness cannot be indefinitely subordinated to client loyalty without hollowing out the peer review system's foundational purpose, and that the Code's peer notification obligation should be understood as a non-waivable professional duty that clients may not contractually or instructionally override, even if the faithful agent duty otherwise requires deference to client direction on confidentiality matters.
Question 9 Principle Tension
Does the principle that benevolent motive does not cure an ethical violation - applied to Engineer B's well-intentioned notification - conflict with the principle of tripartite interest balancing, which might weigh Engineer A's right to know against the franchiser's confidentiality interest and find notification net-beneficial, thereby suggesting that motive and outcome together should inform the ethical assessment?
In response to Q203: The principle that benevolent motive does not cure an ethical violation, applied by the Board to Engineer B's well-intentioned notification, is sound as a deontological matter but does not fully account for the relevance of outcomes in assessing the overall ethical quality of Engineer B's conduct. The tripartite interest balancing framework - which weighs the interests of Engineer A, the franchiser, and the broader professional community - suggests that Engineer B's notification, though procedurally deficient as to timing and scope, produced a net outcome that was superior to the alternative of complete silence. Engineer A was informed of the review and given an opportunity to respond, the franchiser's transition was managed with some degree of transparency, and the professional community's interest in peer review integrity was partially served. However, the outcome-based argument cannot rehabilitate the timing violation or the disclosure of preliminary results, because those deficiencies were not merely procedural - they reflect a failure to structure the engagement in a way that could have honored all relevant obligations simultaneously. The correct analytical conclusion is that motive and outcome are relevant to the overall ethical assessment but cannot substitute for compliance with the Code's specific procedural requirements.
Question 10 Principle Tension
Does the principle of at-will employment symmetry - invoked to justify the franchiser's right to non-renew Engineer A's contract - conflict with the principle of reasonable timing compliance in peer review notification, in that the franchiser's use of the transition period to conduct a covert review exploits the at-will relationship to circumvent the procedural protections the notification timing requirement is designed to provide?
In response to Q204: The franchiser's use of the transitional overlap period - during which Engineer A's contract remained active - to conduct a covert review through Engineer B represents a structural exploitation of the at-will employment relationship that the peer review notification timing requirement is specifically designed to prevent. The at-will employment symmetry principle, which legitimately permits the franchiser to non-renew Engineer A's contract, does not extend to authorizing the franchiser to use the notice period as a window for covert competitive evaluation of Engineer A's work. The notice period exists to facilitate an orderly professional transition, not to create a vulnerability window during which the incumbent engineer's work can be reviewed without the incumbent's knowledge. By instructing Engineer B to conduct the review before Engineer A's contract expired and before Engineer A was informed, the franchiser effectively weaponized the transitional period against the very engineer it had placed on notice. This conduct is inconsistent with the reasonable timing compliance standard that the peer review notification obligation implies and undermines the procedural fairness that the Code's engineer relations provisions are designed to protect.
The central principle tension in this case - between the faithful agent duty owed to the franchiser and the peer review notification obligation owed to Engineer A - was resolved by the Board in favor of the faithful agent duty, but only partially and without full consensus. The Board concluded that Engineer B's notification violated the faithful agent obligation, yet could not agree on whether proceeding with the review at that time was itself ethical. This split outcome reveals that the two principles were not genuinely reconciled; rather, the Board prioritized client loyalty on the disclosure question while leaving unresolved the deeper question of whether the entire engagement structure was permissible. The case teaches that when two Code provisions point in directly opposite directions - one commanding disclosure, the other forbidding it - the Code does not supply a clear lexical ordering, and the Board's inability to reach consensus on Q2 is itself evidence that the faithful agent principle cannot categorically override peer review notification norms without remainder. The unresolved tension suggests that the Code implicitly requires engineers to avoid accepting engagements structured so as to make compliance with both provisions simultaneously impossible.
The principle of professional dignity for the incumbent engineer - which underlies the peer review notification requirement - was effectively subordinated to client loyalty in the Board's resolution of Q1, but this subordination was not cost-free and carries a systemic implication the Board did not fully articulate. When client confidentiality is permitted to override the incumbent engineer's right to know that their work is under review, the peer review process is transformed from a collegial professional improvement mechanism into a covert competitive intelligence tool available to clients willing to instruct successor engineers to remain silent. The franchiser's use of the transition overlap period to conduct a review without Engineer A's knowledge exploited the at-will employment symmetry principle - the franchiser's legitimate right not to renew - to circumvent the procedural protections that the notification timing requirement exists to provide. The case teaches that professional dignity and peer review procedural fairness cannot be indefinitely subordinated to client loyalty without hollowing out the peer review system's foundational purpose, and that the Code's peer notification obligation should be understood as a non-waivable professional duty that clients may not contractually or instructionally override, even if the faithful agent duty otherwise requires deference to client direction on confidentiality matters.
From a deontological perspective, did Engineer B fulfill a categorical duty to notify Engineer A prior to conducting the design review, regardless of the franchiser's confidentiality instruction, given that the Code's peer review notification obligation exists independently of client consent?
In response to Q301 and Q302: From a deontological perspective, Engineer B faced a genuine conflict between two categorical duties - the duty to notify the incumbent engineer prior to conducting a peer review, and the duty to act as a faithful agent to the client. The resolution of this conflict under a Kantian framework depends on which duty is more fundamental to the professional role. The peer review notification obligation is best understood as a duty owed to the professional community and to the incumbent engineer as a rights-bearing professional - it is not merely a courtesy but a procedural entitlement that exists independently of client consent. The faithful agent duty, by contrast, is a relational duty owed to a specific client and is explicitly conditioned in the Code on consistency with ethical limits. A deontological analysis therefore supports the conclusion that the peer notification duty takes precedence over the client confidentiality instruction, because the faithful agent duty is not absolute while the notification obligation reflects a categorical commitment to professional fairness. However, Engineer B's violation of the faithful agent duty in disclosing preliminary results - beyond what the notification obligation required - cannot be justified on deontological grounds, because that excess disclosure served no categorical duty and simply exceeded the scope of the competing obligation.
From a deontological perspective, did Engineer B violate a strict duty of faithful agency to the franchiser by overriding the client's explicit confidentiality instruction, even if Engineer B's motive was to honor a competing professional obligation to Engineer A?
In response to Q301 and Q302: From a deontological perspective, Engineer B faced a genuine conflict between two categorical duties - the duty to notify the incumbent engineer prior to conducting a peer review, and the duty to act as a faithful agent to the client. The resolution of this conflict under a Kantian framework depends on which duty is more fundamental to the professional role. The peer review notification obligation is best understood as a duty owed to the professional community and to the incumbent engineer as a rights-bearing professional - it is not merely a courtesy but a procedural entitlement that exists independently of client consent. The faithful agent duty, by contrast, is a relational duty owed to a specific client and is explicitly conditioned in the Code on consistency with ethical limits. A deontological analysis therefore supports the conclusion that the peer notification duty takes precedence over the client confidentiality instruction, because the faithful agent duty is not absolute while the notification obligation reflects a categorical commitment to professional fairness. However, Engineer B's violation of the faithful agent duty in disclosing preliminary results - beyond what the notification obligation required - cannot be justified on deontological grounds, because that excess disclosure served no categorical duty and simply exceeded the scope of the competing obligation.
From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and collegial respect expected of a competent engineer by accepting a covert review engagement without first seeking clarification of the franchiser's reasons for the confidentiality instruction, and does the subsequent voluntary notification redeem or merely partially offset that initial failure of character?
In response to Q304: From a virtue ethics perspective, Engineer B's conduct reflects a partial but incomplete expression of professional integrity. The voluntary decision to notify Engineer A despite the franchiser's explicit instruction demonstrates a degree of collegial respect and moral courage that is consistent with the character of a professionally virtuous engineer. However, the failure to seek clarification of the franchiser's reasons for the confidentiality instruction before accepting the engagement reflects an absence of the proactive ethical vigilance that virtue ethics would expect. A truly virtuous engineer would have recognized the structural incompatibility between the confidentiality instruction and the peer notification obligation at the outset and would have sought to resolve that tension before proceeding - either by negotiating modified engagement terms or by declining the engagement. The subsequent voluntary notification, while morally creditable, represents a reactive correction of a problem that a more ethically attentive engineer would have prevented. Virtue ethics therefore supports a nuanced assessment: Engineer B demonstrated genuine professional integrity in the notification decision but fell short of the standard of proactive ethical character that the engagement's initial circumstances demanded.
From a consequentialist perspective, did Engineer B's decision to notify Engineer A after completing the review - rather than before - produce a net outcome that better served the professional community, the franchiser, and Engineer A compared to either full silence or pre-review notification?
In response to Q303: From a consequentialist perspective, Engineer B's decision to notify Engineer A after completing the review - rather than before - produced a mixed outcome that was superior to complete silence but inferior to pre-review notification. The post-review notification gave Engineer A some opportunity to respond to the preliminary findings and preserved a degree of professional transparency, which served Engineer A's interests and the professional community's interest in peer review integrity. However, by the time notification occurred, the review was complete and Engineer B's preliminary conclusions were already formed, meaning Engineer A's opportunity to provide context or correct misunderstandings before those conclusions were reached was permanently foreclosed. A pre-review notification would have maximized the net benefit by preserving Engineer A's full participatory rights, minimizing the faithful agent violation to the extent the franchiser might have consented to a narrower disclosure, and producing a more defensible professional record. The consequentialist analysis therefore supports the conclusion that the timing of notification was suboptimal and that the ethical harm of the delay was real, even if the eventual notification partially mitigated that harm.
Question 15 Counterfactual
If Engineer B had refused to accept the engagement unless the franchiser permitted prior notification to Engineer A, would the franchiser have been compelled to either grant that permission or seek a different successor engineer, and would such a refusal have represented the ethically optimal resolution of the conflict between faithful agency and peer review notification duties?
In response to Q401: If Engineer B had refused to accept the engagement unless the franchiser permitted prior notification to Engineer A, this would have represented the ethically optimal resolution of the conflict between the faithful agent duty and the peer review notification obligation. Such a refusal would have forced the franchiser to choose between granting permission for notification - thereby enabling a procedurally compliant review - or seeking a different successor engineer who might face the same ethical constraint. Either outcome would have been preferable to the path actually taken: a covert review followed by a post-hoc notification that violated both the timing requirement and the faithful agent duty. The refusal strategy is also consistent with the Code's implicit expectation that engineers not accept engagements structured in ways that make ethical compliance impossible from the outset. By conditioning acceptance on notification permission, Engineer B would have preserved the integrity of both the peer review process and the faithful agent relationship, while placing the responsibility for any resulting delay or inconvenience squarely on the franchiser's decision to impose an ethically incompatible instruction.
Question 16 Counterfactual
If Engineer B had notified Engineer A before conducting the design review rather than after, would that pre-review notification have satisfied the Code's peer review notification obligation and simultaneously preserved the faithful agent duty to the franchiser, or would the franchiser's confidentiality instruction have made any timing of notification equally impermissible under the faithful agent standard?
In response to Q402: If Engineer B had notified Engineer A before conducting the design review rather than after, the pre-review notification would have substantially satisfied the Code's peer review notification obligation under Section III.8.a, but the franchiser's confidentiality instruction would have made any timing of notification equally impermissible under a strict reading of the faithful agent standard. The faithful agent duty, as the Board interpreted it, does not distinguish between pre-review and post-review disclosure - both would have violated the franchiser's explicit instruction. However, pre-review notification would have been ethically superior for two independent reasons: first, it would have preserved Engineer A's full opportunity to provide context before Engineer B's conclusions were formed, honoring the substantive purpose of the notification obligation; and second, it would have minimized the scope of the faithful agent violation by disclosing only the existence of the engagement rather than both the engagement and preliminary results. The timing question therefore matters not only for compliance with Section III.8.a but also for calibrating the degree of the faithful agent violation - pre-review notification would have been a lesser breach of the faithful agent duty while producing a more complete satisfaction of the peer notification obligation.
Question 17 Counterfactual
If Engineer B had disclosed the preliminary review results to Engineer A but withheld the fact of the new engagement relationship - as opposed to disclosing both - would that partial disclosure have constituted a lesser violation of the faithful agent duty while still partially honoring the spirit of the peer review notification obligation?
Question 18 Counterfactual
If Engineer A's contract with the franchiser had already expired before Engineer B conducted the review - rather than still being active - would the ethical weight of the peer review notification obligation have been diminished, and would the franchiser's confidentiality instruction have been more defensible under the faithful agent standard?
In response to Q404: If Engineer A's contract with the franchiser had already expired before Engineer B conducted the review, the ethical weight of the peer review notification obligation would have been meaningfully diminished but not eliminated. The notification requirement under Section III.8.a is most forceful when the incumbent engineer remains professionally accountable for the work under review - an active contract creates ongoing professional responsibility that makes covert review particularly prejudicial to the incumbent's interests. Once the contract has expired, the incumbent engineer's direct professional stake in the review is reduced, though not extinguished, because the review's findings may still affect the incumbent's professional reputation and the quality record associated with completed work. The franchiser's confidentiality instruction would have been more defensible under the faithful agent standard in a post-expiry scenario, because the competing obligation to notify would have been weaker. However, the peer notification obligation does not disappear entirely upon contract expiration - the Code's concern for professional dignity and the opportunity to respond to technical concerns extends to completed work, particularly where the review's conclusions may be used to justify the non-renewal decision or to inform the successor engineer's approach to remediation.
Rich Analysis Results
View ExtractionCausal-Normative Links 6
Engineer B Reviews Design Information
- Peer Review Preliminary Results Disclosure to Reviewed Engineer Obligation
- Engineer B Reviewed Engineer Technical Comment Opportunity Preservation BER Case
- Reviewed Engineer Technical Comment Opportunity Preservation Obligation
- Engineer B Peer Review Notification of Engineer A Despite Client Instruction
- Covert Peer Review Client Instruction Resistance Obligation
- Peer Review Procedural Fairness Client Instruction Non-Compliance Facilitation Obligation
Franchiser Instructs Confidentiality to Engineer B
- Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation
- Covert Peer Review Client Instruction Resistance Obligation
- Peer Review Procedural Fairness Client Instruction Non-Compliance Facilitation Obligation
- Franchiser Client Peer Review Procedural Fairness Client Instruction Non-Override BER Case
Engineer B Accepts Project Without Clarification
- Pre-Engagement Client Instruction Rationale Clarification Obligation
- Engineer B Pre-Engagement Client Instruction Rationale Clarification BER Case
- Faithful Agent Client Interest Non-Neglect Through Unauthorized Disclosure Obligation
Engineer B Notifies Engineer A of Relationship and Review
- Engineer B Peer Review Notification of Engineer A Despite Client Instruction
- Engineer B Peer Review Notification and Consent Fulfillment
- Engineer B Peer Review Incumbent Notification Reasonable Timing Compliance BER Case
- Peer Review Incumbent Notification Reasonable Timing Compliance Obligation
- Engineer B Reviewed Engineer Technical Comment Opportunity Preservation BER Case
- Reviewed Engineer Technical Comment Opportunity Preservation Obligation
- Engineer B Preliminary Review Results Disclosure to Engineer A
- Peer Review Preliminary Results Disclosure to Reviewed Engineer Obligation
- Engineer B Covert Review Client Instruction Resistance
- Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case
- Faithful Agent Client Interest Non-Neglect Through Unauthorized Disclosure Obligation
- Engineer B Altruistic Disclosure Non-Justification for Client Interest Neglect BER Case
- Altruistic Disclosure Non-Justification for Client Interest Neglect Obligation
Franchiser Terminates Engineer A
- Engineer B Successor Contract Acceptance After Engineer A Contract Expiration
- Successor Engineer Post-Review Expired-Contract Acceptance Permissibility Obligation
Franchiser Retains Engineer B Early
- Successor Engineer Post-Review Expired-Contract Acceptance Permissibility Obligation
- Engineer B Successor Contract Acceptance After Engineer A Contract Expiration
- Peer Review Successor Contract Incumbent Contract Expiry Prerequisite Constraint
- Franchiser Client Peer Review Procedural Fairness Client Instruction Non-Override BER Case
Question Emergence 18
Triggering Events
- Parallel Engagement Overlap Created
- Engineer A Kept Uninformed During Review
- Design Review Completed Under Conflict
- Confidentiality Instruction Imposed on Engineer B
Triggering Actions
- Engineer B Reviews Design Information
- Engineer B Accepts Project Without Clarification
- Franchiser Retains Engineer B Early
Competing Warrants
- Covert Peer Review Client Instruction Resistance Obligation Engineer B Faithful Agent Peer Review Collegial Boundary Exercise
- Engineer B Peer Review Notification and Consent Fulfillment Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Parallel Engagement Overlap Created
- Engineer A Kept Uninformed During Review
Triggering Actions
- Engineer B Accepts Project Without Clarification
- Franchiser Instructs Confidentiality to Engineer B
Competing Warrants
- Pre-Engagement Client Instruction Rationale Clarification Obligation Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case
- Client Motive Inquiry Pre-Engagement Confidentiality Instruction - Engineer B Failure to Inquire Before Accepting Franchiser Engagement Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Engineer A Kept Uninformed During Review
- Parallel Engagement Overlap Created
Triggering Actions
- Franchiser Instructs Confidentiality to Engineer B
- Franchiser Retains Engineer B Early
Competing Warrants
- Client Loyalty Invoked By Franchiser Toward Engineer B Confidentiality Instruction
- Peer Review Procedural Fairness Client Instruction Non-Compliance Facilitation Obligation At-Will Employment Symmetry Invoked For Franchiser Non-Renewal of Engineer A Contract
Triggering Events
- Engineer A Kept Uninformed During Review
- Confidentiality Instruction Imposed on Engineer B
- Design Review Completed Under Conflict
- Parallel Engagement Overlap Created
Triggering Actions
- Franchiser Instructs Confidentiality to Engineer B
- Engineer B Reviews Design Information
- Engineer B Notifies Engineer A of Relationship and Review
Competing Warrants
- Professional Dignity of Incumbent Engineer Underlying Peer Notification Purpose Client Loyalty Invoked to Constrain Engineer B Disclosure
- Reviewed Engineer Technical Comment Opportunity Preservation Obligation Faithful Agent Client Interest Non-Neglect Through Unauthorized Disclosure Obligation
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Engineer A Informed of Successor Engagement
- Design Review Completed Under Conflict
Triggering Actions
- Franchiser Instructs Confidentiality to Engineer B
- Engineer B Notifies Engineer A of Relationship and Review
Competing Warrants
- Faithful Agent Trustee Duty as General Loyalty and Fair Dealing Incumbent Engineer Knowledge Requirement Invoked as Competing Obligation
- Faithful Agent Client Instruction Non-Disclosure - Engineer B Obligation to Follow Franchiser Confidentiality Instruction Client Direction Does Not Authorize Ethical Violation Invoked Against Franchiser Confidentiality Instruction
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Parallel Engagement Overlap Created
- Design Review Completed Under Conflict
- Engineer A Informed of Successor Engagement
Triggering Actions
- Engineer B Accepts Project Without Clarification
- Engineer B Reviews Design Information
- Engineer B Notifies Engineer A of Relationship and Review
- Franchiser Instructs Confidentiality to Engineer B
Competing Warrants
- Pre-Engagement Client Instruction Clarification Obligation Incumbent Engineer Knowledge Requirement Invoked By Engineer B Against Client Instruction
- Benevolent Motive Does Not Cure Ethical Violation Applied to Engineer B Professional Dignity Invoked For Engineer A As Incumbent Subject To Covert Review
Triggering Events
- Design Review Completed Under Conflict
- Parallel Engagement Overlap Created
- Confidentiality Instruction Imposed on Engineer B
- Engineer A Kept Uninformed During Review
Triggering Actions
- Engineer B Reviews Design Information
- Franchiser Retains Engineer B Early
- Engineer B Accepts Project Without Clarification
Competing Warrants
- Peer Review Program Collegial Improvement Non-Exploitation - Engineer B Successor Contract Acceptance
- Engineer-Solicitation-and-Competition-Ethics-Standard-Instance Post-Peer-Review-Procurement-Conflict-Standard-Instance
Triggering Events
- Engineer A Informed of Successor Engagement
- Confidentiality Instruction Imposed on Engineer B
- Parallel Engagement Overlap Created
Triggering Actions
- Engineer B Notifies Engineer A of Relationship and Review
- Franchiser Instructs Confidentiality to Engineer B
Competing Warrants
- Benevolent Motive Does Not Cure Ethical Violation Applied to Engineer B Tripartite Interest Balancing Invoked In Engineer A to Engineer B Transition
- Altruistic Disclosure Non-Justification for Client Interest Neglect Obligation Competing Code Provision Balancing Applied to Peer Notification vs. Faithful Agent Duty
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Engineer A Informed of Successor Engagement
- Parallel Engagement Overlap Created
Triggering Actions
- Franchiser Instructs Confidentiality to Engineer B
- Engineer B Notifies Engineer A of Relationship and Review
Competing Warrants
- Engineer B Peer Review Notification of Engineer A Despite Client Instruction Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case
Triggering Events
- Engineer A Informed of Successor Engagement
- Design Review Completed Under Conflict
- Peer Review Confidentiality Agreement Absent - Engineer A Design Review
Triggering Actions
- Engineer B Notifies Engineer A of Relationship and Review
- Engineer B Reviews Design Information
Competing Warrants
- Faithful Agent Client Interest Non-Neglect Through Unauthorized Disclosure Obligation Reviewed Engineer Technical Comment Opportunity Preservation Obligation
- Engineer B Altruistic Disclosure Non-Justification for Client Interest Neglect BER Case Peer Review Preliminary Results Incumbent Disclosure Constraint
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Engineer A Informed of Successor Engagement
- Parallel Engagement Overlap Created
Triggering Actions
- Franchiser Instructs Confidentiality to Engineer B
- Engineer B Notifies Engineer A of Relationship and Review
Competing Warrants
- Client Direction Does Not Authorize Ethical Violation Invoked Against Franchiser Confidentiality Instruction Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure
- Incumbent Engineer Knowledge Requirement Invoked By Engineer B Against Client Instruction Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser
Triggering Events
- Parallel Engagement Overlap Created
- Confidentiality Instruction Imposed on Engineer B
- Engineer A Kept Uninformed During Review
- Contract_Non-Renewal_Notice_Received
- Design Review Completed Under Conflict
Triggering Actions
- Franchiser Retains Engineer B Early
- Franchiser Instructs Confidentiality to Engineer B
- Franchiser Terminates Engineer A
- Engineer B Reviews Design Information
Competing Warrants
- At-Will Employment Symmetry Invoked For Franchiser Non-Renewal of Engineer A Contract
- Peer Review Procedural Fairness Client Instruction Non-Compliance Facilitation Obligation Peer Review Successor Contract Incumbent Contract Expiry Prerequisite Constraint
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Engineer A Kept Uninformed During Review
- Design Review Completed Under Conflict
- Engineer A Informed of Successor Engagement
Triggering Actions
- Franchiser Instructs Confidentiality to Engineer B
- Engineer B Reviews Design Information
- Engineer B Notifies Engineer A of Relationship and Review
Competing Warrants
- Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation Faithful Agent Client Instruction Non-Disclosure - Engineer B Obligation to Follow Franchiser Confidentiality Instruction
- Peer Review Notification Obligation Standard (Section III.8.a) Client Loyalty Invoked to Constrain Engineer B Disclosure
Triggering Events
- Design Review Completed Under Conflict
- Engineer A Informed of Successor Engagement
- Confidentiality Instruction Imposed on Engineer B
- Engineer A Kept Uninformed During Review
Triggering Actions
- Engineer B Reviews Design Information
- Engineer B Notifies Engineer A of Relationship and Review
- Franchiser Instructs Confidentiality to Engineer B
Competing Warrants
- Reasonable Timing Compliance in Peer Review Incumbent Notification Tripartite Interest Balancing Invoked In Engineer A to Engineer B Transition
- Peer Review Notification Obligation Standard (Section III.8.a) Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Parallel Engagement Overlap Created
- Engineer A Kept Uninformed During Review
- Design Review Completed Under Conflict
Triggering Actions
- Franchiser Instructs Confidentiality to Engineer B
- Engineer B Accepts Project Without Clarification
- Franchiser Retains Engineer B Early
Competing Warrants
- Covert Peer Review Client Instruction Resistance Obligation Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser
- Pre-Engagement Client Instruction Clarification Obligation At-Will Employment Symmetry Invoked For Franchiser Non-Renewal of Engineer A Contract
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Parallel Engagement Overlap Created
- Engineer A Kept Uninformed During Review
- Design Review Completed Under Conflict
- Engineer A Informed of Successor Engagement
Triggering Actions
- Franchiser Instructs Confidentiality to Engineer B
- Engineer B Accepts Project Without Clarification
- Engineer B Reviews Design Information
- Engineer B Notifies Engineer A of Relationship and Review
Competing Warrants
- Peer Review Incumbent Notification Reasonable Timing Compliance Obligation
- Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation Compliance Obligation
- Client Loyalty Invoked to Constrain Engineer B Disclosure
Triggering Events
- Confidentiality Instruction Imposed on Engineer B
- Parallel Engagement Overlap Created
- Engineer A Kept Uninformed During Review
- Engineer A Informed of Successor Engagement
Triggering Actions
- Franchiser Instructs Confidentiality to Engineer B
- Engineer B Notifies Engineer A of Relationship and Review
- Engineer B Reviews Design Information
Competing Warrants
- Peer Review Preliminary Results Disclosure to Reviewed Engineer Obligation Faithful Agent Client Interest Non-Neglect Through Unauthorized Disclosure Obligation
- Incumbent Engineer Knowledge Requirement Invoked as Competing Obligation Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure
- Reviewed Engineer Technical Comment Opportunity Preservation Obligation Altruistic Disclosure Non-Justification for Client Interest Neglect Obligation
Triggering Events
- Contract_Non-Renewal_Notice_Received
- Parallel Engagement Overlap Created
- Confidentiality Instruction Imposed on Engineer B
- Design Review Completed Under Conflict
- Engineer A Informed of Successor Engagement
Triggering Actions
- Franchiser Terminates Engineer A
- Franchiser Retains Engineer B Early
- Franchiser Instructs Confidentiality to Engineer B
- Engineer B Reviews Design Information
- Engineer B Notifies Engineer A of Relationship and Review
Competing Warrants
- Peer Review Successor Contract Incumbent Contract Expiry Prerequisite Constraint Peer Review Incumbent Notification Reasonable Timing Compliance Obligation
- Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation
- At-Will Employment Symmetry Invoked For Franchiser Non-Renewal of Engineer A Contract Professional Dignity Invoked For Engineer A As Incumbent Subject To Covert Review
Resolution Patterns 25
Determinative Principles
- Peer review notification obligation is strongest when the incumbent engineer bears active professional accountability for the work under review
- Professional dignity and reputational interest survive contract expiration
- Faithful agent deference to client confidentiality instructions is more defensible when the competing obligation is weaker
Determinative Facts
- Engineer A's contract was active at the time of the review, creating ongoing professional responsibility
- A post-expiry review would reduce but not eliminate Engineer A's professional stake in the findings
- The franchiser's non-renewal decision and successor remediation approach could still be informed by review findings affecting Engineer A's completed work
Determinative Principles
- Professional dignity and peer review procedural fairness for the incumbent engineer underlie the notification requirement
- Client loyalty and faithful agent duty were permitted to subordinate professional dignity in the board's resolution of Q1
- Peer review notification obligation should be understood as a non-waivable professional duty that clients may not contractually or instructionally override
Determinative Facts
- The franchiser used the transition overlap period — while Engineer A's contract was still active — to conduct a covert review without Engineer A's knowledge
- The franchiser's at-will right not to renew was exploited to circumvent the procedural protections the notification timing requirement exists to provide
- The board subordinated professional dignity to client loyalty on Q1 without fully articulating the systemic implications of that subordination
Determinative Principles
- Peer review notification as a categorical duty owed to the professional community, not merely a courtesy
- Faithful agent duty as a relational and conditioned obligation, not an absolute one
- Excess disclosure beyond what the competing duty required cannot be deontologically justified
Determinative Facts
- The Code explicitly conditions the faithful agent duty on consistency with ethical limits
- Engineer B disclosed preliminary review results to Engineer A beyond what notification alone required
- The peer review notification obligation exists independently of client consent
Determinative Principles
- Faithful agent and trustee duty prohibits unauthorized disclosure of client information
- Benevolent motive does not cure an ethical violation
- Client confidentiality instructions, even if ethically problematic in origin, retain binding force on the engineer
Determinative Facts
- Engineer B notified Engineer A of his relationship with the franchiser
- The franchiser had explicitly instructed Engineer B not to disclose the engagement to Engineer A
- Engineer B disclosed the relationship without obtaining the franchiser's prior consent
Determinative Principles
- Proactive ethical vigilance requires engineers to seek clarification when client instructions facially conflict with professional obligations
- Acceptance of a structurally compromised engagement forecloses later compliance with competing duties
- A facially anomalous confidentiality instruction signals a potential conflict that a competent engineer must investigate before proceeding
Determinative Facts
- The franchiser's instruction not to disclose the engagement to Engineer A was facially anomalous given the peer review notification obligation
- Engineer B accepted the engagement without seeking clarification of the reason behind the confidentiality instruction
- Proceeding without clarification foreclosed the possibility of negotiating terms that could have honored both the faithful agent duty and the peer notification obligation
Determinative Principles
None identifiedDeterminative Facts
- The board was unable to reach internal agreement on whether it was ethical for Engineer B to proceed with the review at the time he did
- The question of timing and whether proceeding was ethical given the circumstances produced irreconcilable disagreement among board members
Determinative Principles
- Pre-engagement ethical diligence: a competent engineer must interrogate client instructions that signal conflicts before accepting an engagement
- Conflict recognition duty: an explicit instruction to conceal a new engagement from an incumbent engineer is itself a red flag requiring inquiry
- Negotiated resolution principle: seeking clarification preserves the possibility of satisfying both client and Code obligations simultaneously
Determinative Facts
- The franchiser explicitly instructed Engineer B not to disclose the new engagement to Engineer A before Engineer B accepted the engagement
- Engineer B accepted the engagement without seeking clarification of the reason behind the confidentiality instruction
- A negotiated disclosure arrangement might have satisfied both the franchiser's transition interests and the Code's peer review notification requirement had Engineer B inquired
Determinative Principles
- Internal qualification of faithful agency: the Code's faithful agent standard is bounded by the phrase 'within the limits of the Code,' meaning it cannot authorize a client instruction that directs a Code violation
- Hierarchy of Code obligations: a client instruction that affirmatively directs suppression of a separately required disclosure falls outside the scope of conduct the faithful agent duty protects
- Ethical ceiling principle: no single Code provision can be weaponized to nullify another provision's independent requirement
Determinative Facts
- The franchiser's confidentiality instruction was an affirmative direction to suppress a disclosure the Code independently requires under peer review notification norms
- The Board's conclusion correctly identified imperfect notification timing and manner but treated the faithful agent duty as categorically prevailing over the peer review notification obligation
- The Code's faithful agent provision (P2) contains an implicit ethical ceiling that limits its scope to lawful and Code-consistent client instructions
Determinative Principles
- Sequential dependency principle: the ethical permissibility of conducting the review was not independent of the notification obligation but was logically constrained by it
- Procedural prerequisite rule: if pre-review notification was required, then proceeding without it rendered the review itself ethically impermissible regardless of subsequent remediation
- Analytical inseparability of Q1 and Q2: the board's split on Q2 may stem from treating the two questions as separable when they are in fact sequentially ordered
Determinative Facts
- The Board reached a split decision on Q2 regarding whether Engineer B could ethically proceed with the review at the time he did
- Engineer B conducted the review before notifying Engineer A, and the notification occurred after the review was substantially underway or completed
- The peer review notification standard suggests notification should precede the review, creating a procedural prerequisite that conditions the permissibility of the review itself
Determinative Principles
- Client direction does not authorize ethical violations
- Correlative client responsibility not to direct engineers to circumvent professional standards
- Engineers have an affirmative obligation to refuse ethically impermissible instructions at the point of engagement
Determinative Facts
- The franchiser affirmatively instructed Engineer B to conceal the new engagement from Engineer A
- Following that instruction would have required Engineer B to conduct a covert peer review in direct violation of the Code's peer review notification standard
- The franchiser was an active participant in creating the ethical conflict, not a passive beneficiary
Determinative Principles
- Professional dignity for the incumbent engineer represents a structural limit on client confidentiality instructions in peer review contexts
- Client confidentiality operates most forcefully with respect to business information and proprietary data, not the procedural rights of third-party engineers
- Peer review must retain its collegial character and cannot be reduced to a covert audit mechanism
Determinative Facts
- Engineers whose work is under review have a professional stake in that review — they may have information relevant to the reviewer's conclusions and bear reputational consequences
- A client confidentiality instruction that systematically overrides the notification right would strip peer review of its collegial character
- Engineer A had no opportunity to respond to technical concerns before those concerns were acted upon
Determinative Principles
- Benevolent motive does not cure an ethical violation as a deontological matter
- Motive and outcome are relevant to overall ethical assessment but cannot substitute for compliance with specific procedural requirements
- Tripartite interest balancing — weighing Engineer A's, the franchiser's, and the professional community's interests — informs but does not override procedural compliance
Determinative Facts
- Engineer B's notification, though procedurally deficient as to timing and scope, produced a net outcome superior to complete silence — Engineer A was informed and given an opportunity to respond
- The timing violation and disclosure of preliminary results were not merely procedural deficiencies but reflected a failure to structure the engagement to honor all obligations simultaneously
- The franchiser's transition was managed with some degree of transparency and the professional community's interest in peer review integrity was partially served
Determinative Principles
- Proactive ethical vigilance as a virtue ethics standard for professional character
- Moral courage demonstrated through voluntary notification despite client instruction
- Reactive correction is morally creditable but inferior to prevention
Determinative Facts
- Engineer B voluntarily notified Engineer A despite the franchiser's explicit confidentiality instruction
- Engineer B did not seek clarification of the franchiser's reasons for the confidentiality instruction before accepting the engagement
- The structural incompatibility between the confidentiality instruction and the peer notification obligation was identifiable at the outset
Determinative Principles
- Client direction does not authorize ethical violations that clients have no standing to override
- Procedural fairness to incumbent engineers underlies the peer review notification framework
- At-will contract rights cannot be weaponized to circumvent professional procedural protections
Determinative Facts
- The franchiser explicitly instructed Engineer B to conceal the new engagement from Engineer A during the transitional overlap period
- Engineer A's contract remained active and Engineer A remained professionally accountable for the work while the covert review was conducted
- The franchiser's instruction was designed to exploit the overlap period to conduct a review without Engineer A's knowledge
Determinative Principles
- Foundational purpose of peer review: the peer review program exists for collegial improvement of engineering practice, not as a mechanism for competitive intelligence gathering or procurement advantage
- Structural transformation concern: when a reviewing engineer leverages a peer review engagement to secure a successor contract displacing the reviewed engineer, the review is transformed from a quality-assurance mechanism into a client-directed competitive evaluation
- Independent solicitation and competition ethics: the subsequent acceptance of the full design contract raises concerns under provisions governing engineer solicitation and competition that are analytically separate from the notification and faithful agency questions
Determinative Facts
- Engineer B subsequently accepted the full design engineering contract with the franchiser after completing the peer review
- The successor contract displaced Engineer A, the very engineer whose work Engineer B had reviewed
- Knowledge and professional positioning gained during the covert peer review contributed to Engineer B's ability to secure the subsequent contract
Determinative Principles
- Faithful agent duty commands client loyalty on disclosure questions
- Peer review notification obligation commands disclosure to the incumbent engineer
- The Code does not supply a clear lexical ordering when two provisions point in directly opposite directions
Determinative Facts
- The board reached a split outcome — condemning Engineer B's notification as a faithful agent violation while failing to reach consensus on whether proceeding with the review was ethical
- Engineer B notified Engineer A despite the franchiser's explicit confidentiality instruction
- The engagement was structured so that simultaneous compliance with both provisions was impossible
Determinative Principles
- Client direction does not authorize an ethical violation — but functions as a trump only when the competing obligation is clearly superior
- Faithful agent duty can neutralize the 'client direction cannot override ethics' principle when two Code provisions are in genuine equipoise
- Pre-engagement clarification obligation is the primary mechanism for preventing irreconcilable dual-provision conflicts
Determinative Facts
- The board invoked 'client direction cannot override ethics' to justify Engineer B's notification, then simultaneously invoked the faithful agent principle to condemn that same notification
- Engineer B did not seek clarification of the franchiser's reasons for the confidentiality instruction before accepting the engagement
- The board's split on Q2 indicates the two provisions were not in a clear hierarchy
Determinative Principles
- Net benefit maximization across all affected parties
- Pre-review notification as the outcome-superior alternative
- Partial mitigation through post-review notification is real but insufficient
Determinative Facts
- Engineer B notified Engineer A after the review was complete, not before
- Engineer A's opportunity to provide context before conclusions were formed was permanently foreclosed by the timing
- The post-review notification gave Engineer A some opportunity to respond to preliminary findings
Determinative Principles
- Engineers should not accept engagements structured to make ethical compliance impossible from the outset
- Conditioning acceptance on notification permission as the ethically optimal resolution strategy
- Responsibility allocation — placing the burden of ethically incompatible instructions on the party who imposed them
Determinative Facts
- The franchiser's confidentiality instruction made simultaneous compliance with both the faithful agent duty and the peer notification obligation structurally impossible
- A refusal to accept without notification permission would have forced the franchiser to choose between granting permission or seeking another engineer
- The path actually taken — covert review followed by post-hoc notification — violated both the timing requirement and the faithful agent duty
Determinative Principles
- The peer review notification obligation authorizes disclosure of the engagement relationship but does not independently authorize disclosure of client work product or preliminary analytical conclusions
- Disclosure of confidential client work product without authorization constitutes an independent faithful agent violation beyond the notification breach
- A narrower disclosure honoring the minimum required by the notification obligation would have minimized the compounding breach
Determinative Facts
- Engineer B disclosed both the existence of the new engagement relationship and the preliminary review results to Engineer A
- The franchiser had not consented to disclosure of the preliminary review results
- The peer review notification obligation under Section III.8.a requires notification of the engagement, not transmission of client work product or analytical conclusions
Determinative Principles
- Scope limitation of peer review notification: the notification obligation protects professional dignity and opportunity to respond, not the transmission of substantive work-product conclusions
- Client confidentiality as an independent duty: disclosing preliminary review findings without client authorization constitutes a breach of confidentiality separate from and in addition to any notification violation
- Analytical separability: the disclosure of the engagement relationship and the disclosure of review findings are two distinct acts each warranting independent ethical assessment
Determinative Facts
- Engineer B disclosed not only the existence of the new engagement to Engineer A but also the preliminary results of the design review
- The franchiser had not authorized disclosure of the preliminary review findings to Engineer A
- The peer review notification requirement is designed to protect Engineer A's professional dignity and opportunity to respond, not to authorize transmission of confidential client work product
Determinative Principles
- Peer review must not function as a competitive audition for successor work
- Informational advantage obtained through a process the incumbent could not contest taints the legitimacy of the successor contract
- The integrity of the peer review program depends on successor engineers not exploiting the review for competitive positioning
Determinative Facts
- Engineer B gained privileged access to Engineer A's design decisions, methodologies, and pending concerns under conditions Engineer A did not know about and could not contest
- Engineer B subsequently accepted the full design engineering contract with the franchiser
- Engineer A's contract had expired before Engineer B was formally retained as design engineer, which the board noted but found insufficient to cure the taint
Determinative Principles
- The faithful agent duty operates within ethical limits and cannot require suppression of a disclosure the Code independently mandates
- The peer notification obligation overrides client confidentiality as to the existence of the engagement
- The faithful agent duty continues to govern the scope of permissible disclosure, limiting Engineer B to the minimum necessary
Determinative Facts
- Section II.4 itself conditions the faithful agent obligation on consistency with ethical limits, meaning the duty is not absolute
- Engineer B disclosed preliminary review results in addition to the existence of the relationship, exceeding what the competing obligation required
- The Board was split on Question 2, reflecting a genuine antinomy within the Code that neither prior conclusion fully resolved
Determinative Principles
- Reasonable timing compliance in peer review notification
- At-will employment symmetry does not extend to authorizing covert competitive evaluation
- Procedural fairness in engineer relations
Determinative Facts
- Engineer B conducted the review while Engineer A's contract was still active
- Engineer A was not informed of the review before it was conducted
- The franchiser instructed Engineer B to conduct the review before Engineer A's contract expired and before Engineer A was notified
Determinative Principles
- Peer review notification timing determines substantive fairness to the incumbent engineer
- Faithful agent duty prohibits unauthorized disclosure regardless of timing
- Lesser breach principle — pre-review notification minimizes the scope of the faithful agent violation
Determinative Facts
- Engineer B notified Engineer A after the review was conducted, not before
- The franchiser issued an explicit confidentiality instruction prohibiting disclosure of the new engagement
- Pre-review notification would have preserved Engineer A's opportunity to provide context before conclusions were formed
Decision Points
View ExtractionShould Engineer B notify Engineer A of the peer review engagement despite the franchiser's explicit instruction to maintain confidentiality, or comply with the client's confidentiality directive and conduct the review without informing Engineer A?
- Notify Engineer A Before Conducting Review
- Comply With Client Instruction and Withhold Notification
- Decline Engagement Unless Notification Permitted
Should Engineer B accept the franchiser's successor design engineering contract while Engineer A's contract remains active, or refrain from accepting the successor engagement until Engineer A's contract has fully expired?
- Decline Successor Contract Until Engineer A Contract Expires
- Accept Successor Contract Concurrent With Review Engagement
- Accept Successor Contract Only After Fulfilling Notification Duties
Should Engineer B accept the peer review engagement as structured under the franchiser's confidentiality instruction, seek clarification of the instruction's basis before proceeding, or decline the engagement unless the franchiser permits prior notification to Engineer A?
- Accept Engagement Under Confidentiality Instruction
- Seek Clarification Before Accepting Engagement
- Decline Engagement Unless Notification Terms Renegotiated
Should Engineer B notify Engineer A of the new engagement and peer review despite the franchiser's explicit confidentiality instruction, or comply with the client's instruction and proceed with the review without disclosing the relationship to Engineer A?
- Notify Engineer A Before Conducting Review
- Comply With Confidentiality Instruction and Proceed
- Condition Acceptance on Notification Permission
Should Engineer B limit notification to Engineer A to the existence of the new engagement relationship, or also disclose the preliminary results of the peer review when notifying Engineer A?
- Disclose Engagement Existence Only
- Disclose Engagement and Preliminary Findings
- Seek Client Authorization Before Any Disclosure
Should Engineer B seek clarification of the franchiser's reasons for the confidentiality instruction before accepting the peer review engagement, or accept the engagement as structured and manage the resulting conflict between faithful agency and peer notification obligations after the fact?
- Seek Clarification Before Accepting Engagement
- Accept Engagement and Manage Conflict Reactively
- Decline Engagement Unless Instruction Is Withdrawn
Should Engineer B notify Engineer A of his relationship with the franchiser and the ongoing peer review despite the franchiser's explicit confidentiality instruction, and if so, at what point relative to conducting the review?
- Notify Engineer A Before Conducting Review
- Notify Engineer A After Completing Review
- Decline Engagement Without Notification Permission
Should Engineer B have sought clarification of the franchiser's confidentiality instruction before accepting the peer review engagement, or was it permissible to accept the engagement and navigate the resulting conflict after the fact?
- Seek Clarification Before Accepting Engagement
- Accept Engagement and Navigate Conflict Later
- Accept Engagement Subject to Code Compliance Reservation
Should Engineer B have limited disclosure to Engineer A to the existence of the new engagement relationship, or was Engineer B also permitted — or obligated — to share the preliminary review results at the time of notification?
- Disclose Engagement Existence Only
- Disclose Both Engagement and Preliminary Results
- Seek Client Consent Before Disclosing Results
Should Engineer B notify Engineer A of the new engagement relationship before conducting the design review (defying the franchiser's confidentiality instruction), notify Engineer A after completing the review (as actually occurred), or remain silent entirely and comply with the franchiser's instruction?
- Notify Engineer A Before Conducting Review
- Notify Engineer A After Completing Review
- Comply Fully With Confidentiality Instruction
Should Engineer B accept the franchiser's engagement as structured under the confidentiality instruction, seek clarification of the franchiser's reasons for the instruction and negotiate modified terms before accepting, or decline the engagement unless the franchiser permits prior notification to Engineer A?
- Accept Engagement Under Existing Terms
- Seek Clarification Before Accepting
- Decline Unless Notification Permitted
When notifying Engineer A, should Engineer B disclose only the existence of the new engagement relationship (minimum required by Section III.8.a), disclose both the engagement relationship and the preliminary review results (as actually occurred), or disclose only the preliminary review results without identifying the new engagement relationship?
- Disclose Engagement Relationship Only
- Disclose Both Relationship and Preliminary Results
- Seek Client Authorization Before Disclosing Results
Should Engineer B notify Engineer A of the new engagement and peer review relationship in defiance of the franchiser's confidentiality instruction, or comply with the client's instruction and remain silent?
- Notify Engineer A of Engagement Only
- Comply With Confidentiality Instruction Fully
- Disclose Engagement and Preliminary Results
Should Engineer B accept the franchiser's engagement under the confidentiality instruction as given, seek clarification of the instruction's rationale before accepting, or condition acceptance on the franchiser's permission to notify Engineer A prior to conducting the review?
- Accept Engagement Under Instruction As Given
- Seek Clarification Before Accepting
- Condition Acceptance on Notification Permission
Should Engineer B proceed with the design review before notifying Engineer A, or treat pre-review notification of Engineer A as a mandatory prerequisite that must be satisfied before any substantive review work begins?
- Complete Review Then Notify Engineer A
- Notify Engineer A Before Beginning Review
- Suspend Review Pending Client Authorization
Should Engineer B notify Engineer A of the new engagement relationship before conducting the peer review (defying the franchiser's confidentiality instruction), after completing the review (as actually occurred), or remain silent entirely — and should that notification include preliminary review findings or be limited to the existence of the engagement?
- Notify Engineer A Before Conducting Review
- Notify Engineer A After Review With Full Disclosure
- Decline Engagement Without Notification Permission
Should Engineer B have sought clarification of the franchiser's confidentiality instruction before accepting the engagement — potentially conditioning acceptance on modified terms — or was it permissible to accept the engagement as structured and navigate the resulting ethical conflict after the fact?
- Seek Clarification Before Accepting Engagement
- Accept Engagement and Resolve Conflict Later
- Decline Engagement as Structurally Incompatible
Case Narrative
Phase 4 narrative construction results for Case 126
Opening Context
You are Engineer A, the original design engineer — and you are only now beginning to sense that your work is being reviewed without your knowledge. Your professional engagement with the franchising client that once anchored a significant portion of your practice is quietly winding down, a non-renewal handled with the particular politeness that makes it difficult to object to and impossible to ignore. What you do not yet know is that another engineer has already been retained to examine the designs you produced — designs you stand behind, designs that carry your stamp and your judgment. No one has told you a review is underway. No confidentiality agreement compels silence on anyone's part, but silence is what you are receiving nonetheless. What unfolds is a test of professional endurance at the intersection of your right to know, your obligation to your own work, and the standards your license demands you uphold — even when the process unfolding around you was never designed with your interests, or your awareness, in mind. The ethical question is not only whether the review is being conducted fairly, but whether the absence of any instruction to notify you resolves the question of whether you should have been notified at all.
Characters (6)
A newly retained reviewing engineer who prioritized his ethical obligation to notify the incumbent over explicit client instructions to maintain secrecy, ultimately earning the successor contract.
- To uphold professional ethics and peer-review obligations even at the risk of client displeasure, while positioning himself as a trustworthy and principled long-term engineering partner.
- To fulfill remaining contractual obligations responsibly and safeguard his professional standing during a period of institutional displacement and reduced client trust.
- To protect the integrity and reputation of his prior design work while ensuring fair procedural treatment during a professionally vulnerable transition period.
Provided engineering design services to the franchiser for several years under a long-term contract; received notice of non-renewal; had pending design concerns under active review at the time of contract wind-down; was the subject of a confidential successor review by Engineer B, who ultimately notified Engineer A of the review despite client instruction to the contrary.
A reviewing engineer caught between competing duties who ultimately chose incumbent notification over client confidentiality, resulting in an ethical finding against him for breaching his faithful agent obligation despite his good-faith intent.
- To reconcile conflicting professional duties by defaulting to peer-review ethics, accepting the professional and ethical consequences of prioritizing colleague notification over strict client loyalty.
A powerful commercial client that orchestrated a covert engineering transition by directing its successor engineer to conceal the review engagement from the outgoing incumbent.
- To minimize operational disruption and potential conflict during the contract transition while quietly evaluating and securing a replacement engineering relationship.
Retained by client to review Engineer A's work; instructed by client not to disclose the engagement to Engineer A; ultimately did notify Engineer A of the relationship and preliminary review results after approximately one week; found to have acted unethically by notifying Engineer A in violation of the faithful agent duty, but the one-week delay before notification was found not to violate Section III.8.a.
Retained Engineer B to review Engineer A's work and explicitly instructed Engineer B not to disclose the new engagement to Engineer A; the Board found Engineer B should have first explored the client's reasons for this instruction before accepting the project.
States (10)
Event Timeline (34)
| # | Event | Type |
|---|---|---|
| 1 | The case centers on a professional conflict of interest involving a franchiser who simultaneously employed two engineers, Engineer A and Engineer B, creating an ethically complex situation where both professionals had overlapping responsibilities to the same client. This dual-engineer arrangement set the stage for a series of decisions that would challenge fundamental principles of professional loyalty and confidentiality. | state |
| 2 | The franchiser explicitly instructed Engineer B to keep their working relationship confidential, effectively asking Engineer B to conceal a material fact from Engineer A, who was still actively serving the same client. This directive placed Engineer B in an immediate ethical dilemma, as complying with the instruction risked violating professional obligations of transparency and honesty toward a fellow engineer. | action |
| 3 | Engineer B agreed to take on the project without seeking clarification about the ethical implications of working confidentially alongside Engineer A, who remained the franchiser's engineer of record at the time. By proceeding without addressing this conflict upfront, Engineer B missed a critical opportunity to establish clear professional boundaries and protect the integrity of all parties involved. | action |
| 4 | Engineer B examined design materials and technical information that had been developed by Engineer A during his tenure with the franchiser, raising serious questions about the appropriate use of a fellow engineer's prior work. This review of proprietary design information, conducted without Engineer A's knowledge or consent, represented a significant point of potential professional misconduct. | action |
| 5 | After reviewing the design information, Engineer B informed Engineer A that he had been engaged by the same franchiser and had already examined work associated with the project, bringing the conflict of interest into the open for the first time. While this disclosure was a step toward transparency, its timing — after the review had already occurred — raised questions about whether Engineer B had acted with sufficient promptness in addressing the ethical conflict. | action |
| 6 | Following Engineer B's disclosure of the overlapping engagement, the franchiser moved to formally terminate Engineer A's professional relationship, effectively ending his role on the project. This termination, occurring in the wake of the confidential parallel engagement, suggested that Engineer B's involvement may have been part of a deliberate transition strategy rather than an independent hiring decision. | action |
| 7 | It was revealed that the franchiser had actually brought Engineer B on board at an earlier point than initially apparent, indicating that the client had been planning the transition away from Engineer A while still maintaining that professional relationship. This timeline raised serious concerns about the franchiser's conduct and about whether Engineer B had knowingly participated in a process designed to undermine Engineer A's position. | action |
| 8 | Engineer A received formal notice that his contract with the franchiser would not be renewed, marking the official conclusion of his professional engagement and confirming that his replacement had been orchestrated in advance. This non-renewal notice crystallized the ethical harm done to Engineer A and underscored the importance of the NSPE's examination of whether the conduct of all parties met established standards of professional practice. | automatic |
| 9 | Multi-Year Relationship Established | automatic |
| 10 | Parallel Engagement Overlap Created | automatic |
| 11 | Confidentiality Instruction Imposed on Engineer B | automatic |
| 12 | Engineer A Kept Uninformed During Review | automatic |
| 13 | Design Review Completed Under Conflict | automatic |
| 14 | Engineer A Informed of Successor Engagement | automatic |
| 15 | Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation | automatic |
| 16 | Tension between Successor Engineer Post-Review Expired-Contract Acceptance Permissibility Obligation and Peer Review Successor Contract Incumbent Contract Expiry Prerequisite Constraint | automatic |
| 17 | Should Engineer B notify Engineer A of the peer review engagement despite the franchiser's explicit instruction to maintain confidentiality, or comply with the client's confidentiality directive and conduct the review without informing Engineer A? | decision |
| 18 | Should Engineer B accept the franchiser's successor design engineering contract while Engineer A's contract remains active, or refrain from accepting the successor engagement until Engineer A's contract has fully expired? | decision |
| 19 | Should Engineer B accept the peer review engagement as structured under the franchiser's confidentiality instruction, seek clarification of the instruction's basis before proceeding, or decline the engagement unless the franchiser permits prior notification to Engineer A? | decision |
| 20 | Should Engineer B notify Engineer A of the new engagement and peer review despite the franchiser's explicit confidentiality instruction, or comply with the client's instruction and proceed with the review without disclosing the relationship to Engineer A? | decision |
| 21 | Should Engineer B limit notification to Engineer A to the existence of the new engagement relationship, or also disclose the preliminary results of the peer review when notifying Engineer A? | decision |
| 22 | Should Engineer B seek clarification of the franchiser's reasons for the confidentiality instruction before accepting the peer review engagement, or accept the engagement as structured and manage the resulting conflict between faithful agency and peer notification obligations after the fact? | decision |
| 23 | Should Engineer B notify Engineer A of his relationship with the franchiser and the ongoing peer review despite the franchiser's explicit confidentiality instruction, and if so, at what point relative to conducting the review? | decision |
| 24 | Should Engineer B have sought clarification of the franchiser's confidentiality instruction before accepting the peer review engagement, or was it permissible to accept the engagement and navigate the resulting conflict after the fact? | decision |
| 25 | Should Engineer B have limited disclosure to Engineer A to the existence of the new engagement relationship, or was Engineer B also permitted — or obligated — to share the preliminary review results at the time of notification? | decision |
| 26 | Should Engineer B notify Engineer A of the new engagement relationship before conducting the design review (defying the franchiser's confidentiality instruction), notify Engineer A after completing the review (as actually occurred), or remain silent entirely and comply with the franchiser's instruction? | decision |
| 27 | Should Engineer B accept the franchiser's engagement as structured under the confidentiality instruction, seek clarification of the franchiser's reasons for the instruction and negotiate modified terms before accepting, or decline the engagement unless the franchiser permits prior notification to Engineer A? | decision |
| 28 | When notifying Engineer A, should Engineer B disclose only the existence of the new engagement relationship (minimum required by Section III.8.a), disclose both the engagement relationship and the preliminary review results (as actually occurred), or disclose only the preliminary review results without identifying the new engagement relationship? | decision |
| 29 | Should Engineer B notify Engineer A of the new engagement and peer review relationship in defiance of the franchiser's confidentiality instruction, or comply with the client's instruction and remain silent? | decision |
| 30 | Should Engineer B accept the franchiser's engagement under the confidentiality instruction as given, seek clarification of the instruction's rationale before accepting, or condition acceptance on the franchiser's permission to notify Engineer A prior to conducting the review? | decision |
| 31 | Should Engineer B proceed with the design review before notifying Engineer A, or treat pre-review notification of Engineer A as a mandatory prerequisite that must be satisfied before any substantive review work begins? | decision |
| 32 | Should Engineer B notify Engineer A of the new engagement relationship before conducting the peer review (defying the franchiser's confidentiality instruction), after completing the review (as actually occurred), or remain silent entirely — and should that notification include preliminary review findings or be limited to the existence of the engagement? | decision |
| 33 | Should Engineer B have sought clarification of the franchiser's confidentiality instruction before accepting the engagement — potentially conditioning acceptance on modified terms — or was it permissible to accept the engagement as structured and navigate the resulting ethical conflict after the fact? | decision |
| 34 | In response to Q102: The franchiser's instruction to Engineer B to conceal the new engagement from Engineer A raises an independent ethical concern that the Board did not address. While the Code's exp | outcome |
Decision Moments (17)
- Notify Engineer A Before Conducting Review
- Comply With Client Instruction and Withhold Notification Actual outcome
- Decline Engagement Unless Notification Permitted
- Decline Successor Contract Until Engineer A Contract Expires Actual outcome
- Accept Successor Contract Concurrent With Review Engagement
- Accept Successor Contract Only After Fulfilling Notification Duties
- Accept Engagement Under Confidentiality Instruction
- Seek Clarification Before Accepting Engagement Actual outcome
- Decline Engagement Unless Notification Terms Renegotiated
- Notify Engineer A Before Conducting Review
- Comply With Confidentiality Instruction and Proceed Actual outcome
- Condition Acceptance on Notification Permission
- Disclose Engagement Existence Only Actual outcome
- Disclose Engagement and Preliminary Findings
- Seek Client Authorization Before Any Disclosure
- Seek Clarification Before Accepting Engagement Actual outcome
- Accept Engagement and Manage Conflict Reactively
- Decline Engagement Unless Instruction Is Withdrawn
- Notify Engineer A Before Conducting Review
- Notify Engineer A After Completing Review Actual outcome
- Decline Engagement Without Notification Permission
- Seek Clarification Before Accepting Engagement
- Accept Engagement and Navigate Conflict Later Actual outcome
- Accept Engagement Subject to Code Compliance Reservation
- Disclose Engagement Existence Only
- Disclose Both Engagement and Preliminary Results Actual outcome
- Seek Client Consent Before Disclosing Results
- Notify Engineer A Before Conducting Review
- Notify Engineer A After Completing Review Actual outcome
- Comply Fully With Confidentiality Instruction
- Accept Engagement Under Existing Terms Actual outcome
- Seek Clarification Before Accepting
- Decline Unless Notification Permitted
- Disclose Engagement Relationship Only
- Disclose Both Relationship and Preliminary Results Actual outcome
- Seek Client Authorization Before Disclosing Results
- Notify Engineer A of Engagement Only
- Comply With Confidentiality Instruction Fully Actual outcome
- Disclose Engagement and Preliminary Results
- Accept Engagement Under Instruction As Given
- Seek Clarification Before Accepting Actual outcome
- Condition Acceptance on Notification Permission
- Complete Review Then Notify Engineer A
- Notify Engineer A Before Beginning Review Actual outcome
- Suspend Review Pending Client Authorization
- Notify Engineer A Before Conducting Review
- Notify Engineer A After Review With Full Disclosure Actual outcome
- Decline Engagement Without Notification Permission
- Seek Clarification Before Accepting Engagement Actual outcome
- Accept Engagement and Resolve Conflict Later
- Decline Engagement as Structurally Incompatible
Sequential action-event relationships. See Analysis tab for action-obligation links.
- Franchiser Instructs Confidentiality to Engineer B Engineer B Accepts Project Without Clarification
- Engineer B Accepts Project Without Clarification Engineer B Reviews Design Information
- Engineer B Reviews Design Information Engineer B Notifies Engineer A of Relationship and Review
- Engineer B Notifies Engineer A of Relationship and Review Franchiser Terminates Engineer A
- Franchiser Terminates Engineer A Franchiser Retains Engineer B Early
- Franchiser Retains Engineer B Early Contract_Non-Renewal_Notice_Received
- conflict_1 decision_1
- conflict_1 decision_2
- conflict_1 decision_3
- conflict_1 decision_4
- conflict_1 decision_5
- conflict_1 decision_6
- conflict_1 decision_7
- conflict_1 decision_8
- conflict_1 decision_9
- conflict_1 decision_10
- conflict_1 decision_11
- conflict_1 decision_12
- conflict_1 decision_13
- conflict_1 decision_14
- conflict_1 decision_15
- conflict_1 decision_16
- conflict_1 decision_17
- conflict_2 decision_1
- conflict_2 decision_2
- conflict_2 decision_3
- conflict_2 decision_4
- conflict_2 decision_5
- conflict_2 decision_6
- conflict_2 decision_7
- conflict_2 decision_8
- conflict_2 decision_9
- conflict_2 decision_10
- conflict_2 decision_11
- conflict_2 decision_12
- conflict_2 decision_13
- conflict_2 decision_14
- conflict_2 decision_15
- conflict_2 decision_16
- conflict_2 decision_17
Key Takeaways
- A client's instruction to conceal a new engineering engagement from an incumbent engineer does not override the successor engineer's independent ethical obligation to provide peer-review notification, regardless of contractual or business pressures.
- The expiration of an incumbent engineer's contract is a necessary but not sufficient condition for a successor engineer to ethically accept a new engagement — proper notification protocols must still be observed before proceeding.
- When a franchiser-client relationship introduces layered authority, the engineer's duty to the profession and to peer-review transparency supersedes the franchiser's operational directives, creating a non-negotiable ethical floor.