Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.
NSPE Code Provisions Referenced
Section II. Rules of Practice 2 87 entities
Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code.
Engineers shall act for each employer or client as faithful agents or trustees.
Section III. Professional Obligations 2 97 entities
Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve.
Engineers shall conform with state registration laws in the practice of engineering.
Cross-Case Connections
View ExtractionExplicit Board-Cited Precedents 1 Lineage Graph
Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.
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.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions
View ExtractionWas 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.
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.
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 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.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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 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.
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.
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?
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.
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.
Decisions & Arguments
View ExtractionCausal-Normative Links 6
- 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
- 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
- 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
- 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
- Engineer B Successor Contract Acceptance After Engineer A Contract Expiration
- Successor Engineer Post-Review Expired-Contract Acceptance Permissibility Obligation
- 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
Decision Points 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?
The peer review notification obligation under Section III.8.a independently requires that an engineer whose work is under review be informed of that review, grounded in professional dignity and the incumbent's right to provide technical context. This obligation is not conditioned on client consent. Competing against this is the faithful agent and trustee duty under Section II.4, which requires Engineer B to carry out the client's transaction in the manner most beneficial to the client and to refrain from unauthorized disclosures, even altruistically motivated ones, when the client has explicitly instructed otherwise. The Board found that Engineer B's notification was not consistent with the Code under the faithful agent standard, while also recognizing that the client's direction does not authorize ethical violations.
Uncertainty arises because the faithful agent duty is expressly bounded in the Code by the phrase 'within ethical limits,' meaning it cannot categorically override a separately mandated disclosure. If the peer notification obligation is treated as a non-waivable professional floor, the faithful agent duty cannot be invoked to suppress it. The Board split on whether proceeding with the review at all was ethical, reflecting that the two provisions were not genuinely reconciled. Additionally, the one-week delay was found not unreasonable under the timing standard, which partially mitigates but does not eliminate the conflict.
The franchiser explicitly instructed Engineer B not to disclose the new review engagement to Engineer A before Engineer B conducted the peer review of Engineer A's active design work. Engineer A's contract remained active during the review period. Engineer B proceeded with the review and then notified Engineer A of both the engagement relationship and the preliminary review results one week later.
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?
The peer review successor contract constraint establishes that a reviewing engineer must refrain from accepting a successor design contract from the same client until the incumbent's contract has fully expired, on the grounds that doing so constitutes improper competitive use of the peer review relationship. Engineer B's acceptance after contract expiration is technically within this boundary. However, the peer review program's foundational purpose is collegial improvement, not competitive intelligence gathering, and Engineer B gained informational advantage through a covert review that Engineer A could not participate in or respond to. The at-will employment symmetry principle legitimately permits the franchiser to non-renew Engineer A, but does not extend to authorizing use of the transitional overlap period as a covert competitive evaluation window.
Uncertainty arises because Engineer B's formal acceptance of the successor contract occurred after Engineer A's contract expired, which satisfies the literal boundary of the successor contract constraint. Whether the knowledge advantage gained during the covert review taints the legitimacy of that transition depends on whether the causal link between the review's findings and Engineer B's procurement advantage is treated as dispositive. The Board did not explicitly resolve whether the manner of the review, covert, with Engineer A unable to respond, independently disqualifies Engineer B from the successor engagement even if the timing of formal acceptance was technically compliant.
The franchiser provided Engineer A notice of non-renewal but retained Engineer B for an immediate peer review of Engineer A's active design work before Engineer A's contract expired. Engineer B conducted the review, gaining privileged access to Engineer A's design decisions and pending concerns under conditions Engineer A did not know about and could not contest. Engineer B subsequently accepted the full successor design engineering contract from the franchiser. Engineer A's contract had expired by the time Engineer B was formally retained as design engineer.
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?
The covert peer review client instruction resistance obligation establishes that a reviewing engineer must resist and decline client instructions requiring a covert review of an incumbent's work, because such instructions cross from permissible client loyalty into facilitation of an ethical violation against a professional peer. A competent engineer exercising proactive ethical vigilance should recognize that a confidentiality instruction of this character signals a structural conflict between faithful agency and peer notification duties, and that accepting the engagement without inquiry forecloses the possibility of negotiating terms that could honor both obligations. The faithful agent duty, by contrast, supports deference to client instructions on engagement terms, and the franchiser's legitimate business interest in managing a confidential transition provides a plausible rationale for the instruction even if that rationale does not ultimately override the notification obligation.
Uncertainty arises from the unknowability of the franchiser's counterfactual response: if the franchiser would have granted notification permission rather than seek a different engineer, then Engineer B's failure to seek clarification was a missed opportunity for a compliant resolution. If the franchiser would have refused and sought a different engineer, then Engineer B's pre-engagement inquiry would have produced no better outcome for Engineer A. The virtue ethics redemption question, whether Engineer B's subsequent voluntary notification partially offsets the initial failure of proactive ethical character, also creates uncertainty about whether the pre-engagement lapse is analytically separable from or subsumed by the subsequent notification decision.
Prior to commencing the peer review, the franchiser explicitly instructed Engineer B not to disclose the new engagement to Engineer A. Engineer A's contract remained active. The confidentiality instruction was facially incompatible with the peer review notification obligation under Section III.8.a, which independently requires that the engineer whose work is under review be informed. Engineer B accepted the engagement without seeking clarification of the franchiser's reasons for the instruction and proceeded with the review the following week.
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?
The peer review notification obligation under Section III.8.a independently requires that the incumbent engineer be informed of the successor's engagement so the incumbent may respond to technical concerns: this obligation exists independently of client consent. Against this, the faithful agent and trustee duty under Section II.4 requires Engineer B to act as a faithful agent to the franchiser and to follow the client's confidentiality instruction, with the Code conditioning faithful agency on consistency with ethical limits. The principle that client direction does not authorize ethical violations supports notification; the principle that benevolent motive does not cure an ethical violation and that client confidentiality instructions retain binding force supports compliance with the instruction.
Uncertainty arises because the Code does not supply a clear lexical ordering when the faithful agent duty and the peer notification obligation point in directly opposite directions. The faithful agent duty is expressly conditioned on ethical limits, which could mean the notification obligation overrides the confidentiality instruction, but the Board concluded the notification was not consistent with the Code, finding the faithful agent duty prevailed on the disclosure question. The Board split on whether proceeding with the review at all was ethical, leaving unresolved whether the two provisions are genuinely irreconcilable or whether a pre-engagement clarification could have avoided the conflict entirely.
The franchiser retained Engineer B as a successor engineer and explicitly instructed Engineer B not to disclose the new engagement to Engineer A, whose contract remained active. Engineer B accepted the engagement without seeking clarification of the confidentiality instruction, conducted the peer review of Engineer A's design work while Engineer A remained uninformed, and only notified Engineer A of the relationship and review after the review was complete. A parallel engagement overlap was created during which Engineer A bore ongoing professional accountability for the work under covert review.
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?
The peer review notification obligation and the reviewed engineer's technical comment opportunity preservation obligation together support disclosure of preliminary results, on the ground that Engineer A cannot meaningfully respond to technical concerns without knowing what those concerns are. Against this, the faithful agent duty and the altruistic disclosure non-justification principle hold that disclosing client work product, including preliminary analytical conclusions, without authorization constitutes an independent breach of confidentiality beyond any notification violation, and that benevolent motive does not cure the excess disclosure. A narrower disclosure limited to the existence of the engagement would more closely approximate compliance with Section III.8.a while minimizing the faithful agent violation.
Uncertainty arises from ambiguity about whether the peer review notification obligation is substantively satisfied by disclosing only the existence of the engagement, or whether meaningful compliance requires disclosure of enough preliminary content to give Engineer A a genuine opportunity to respond. If the notification obligation is construed substantively rather than formally, disclosure of at least some preliminary findings may be necessary to honor its purpose. The faithful agent duty's characterization as a general loyalty and fair dealing obligation rather than a strict fiduciary duty also creates ambiguity about whether partial disclosure of work-product conclusions constitutes a material breach or a minor deviation.
When Engineer B notified Engineer A of the new engagement relationship, Engineer B simultaneously disclosed the preliminary results of the peer review of Engineer A's design work. The franchiser had not authorized disclosure of any information, including preliminary analytical conclusions derived from the confidential review engagement. The peer review notification obligation under Section III.8.a requires that the incumbent engineer be informed of the successor's engagement and given an opportunity to respond to technical concerns, but does not expressly specify that preliminary findings must be transmitted as part of the notification.
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?
The pre-engagement client instruction clarification obligation and the conflict recognition duty together support the position that Engineer B should have interrogated the confidentiality instruction before accepting, because a facially anomalous instruction signals a structural incompatibility that a competent engineer must investigate. The incumbent engineer knowledge requirement invoked by Engineer B against the client instruction further supports the view that Engineer B had an independent basis to recognize the conflict at the outset. Against this, the faithful agent duty and the at-will employment symmetry principle support the position that Engineer B was entitled to accept the engagement as offered, relying on the franchiser's legitimate authority to structure the transition and manage the timing of Engineer A's notification.
Uncertainty arises from the indeterminacy of what clarification would have produced: if the franchiser would have refused to modify the confidentiality instruction regardless of Engineer B's inquiry, the clarification obligation would have required Engineer B to decline the engagement entirely rather than merely seek information. The virtue ethics redemption question also creates uncertainty, whether Engineer B's subsequent voluntary notification partially or fully offsets the initial failure of proactive ethical vigilance is unresolved, and the consequentialist case for accepting the engagement and managing the conflict reactively is not obviously weaker than the deontological case for pre-engagement refusal.
The franchiser retained Engineer B and issued an explicit instruction not to disclose the new engagement to Engineer A before Engineer B had conducted any review or raised any questions about the instruction's compatibility with professional obligations. Engineer B accepted the engagement without seeking clarification of the franchiser's reasons for the confidentiality instruction, despite the fact that the instruction was facially anomalous, a client directing a successor engineer not to inform the incumbent of a peer review engagement is precisely the kind of instruction that signals a potential conflict with Section III.8.a. By accepting without inquiry, Engineer B foreclosed the possibility of negotiating engagement terms that might have honored both the faithful agent duty and the peer notification obligation simultaneously.
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?
Two competing obligations are in direct tension. The peer review notification obligation (Section III.8.a) requires that the incumbent engineer be informed of the successor's engagement so the incumbent may respond to technical concerns, this duty exists independently of client consent and reflects a categorical commitment to professional fairness and the incumbent's dignity. The faithful agent duty (Section II.4) requires Engineer B to act as a faithful agent and trustee to the franchiser, honoring the explicit confidentiality instruction, though this duty is expressly conditioned on consistency with ethical limits. The peer notification obligation is best understood as a duty owed to the professional community and to Engineer A as a rights-bearing professional; the faithful agent duty is a relational obligation conditioned on ethical limits and therefore cannot categorically override the notification requirement.
Uncertainty arises from the absence of a clear lexical ordering in the NSPE Code when two provisions point in opposite directions. If the faithful agent duty's 'within ethical limits' qualifier is sufficient to transform Engineer B's disclosure from a breach into a permitted act, the notification is vindicated. Conversely, if the one-week post-review notification delay is deemed reasonable under the peer review notification timing standard, the warrant against proceeding may be weakened. The Board split on whether proceeding with the review at that time was ethical, reflecting genuine equipoise between the two obligations.
The franchiser retained Engineer B to conduct a peer review of Engineer A's design work while Engineer A's contract remained active. The franchiser explicitly instructed Engineer B not to disclose the new engagement to Engineer A. Engineer B conducted the review without notifying Engineer A, then notified Engineer A of both the engagement relationship and the preliminary review results after the review was complete. Engineer A was kept uninformed throughout the review period, foreclosing any opportunity to provide context before Engineer B's conclusions were formed.
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?
The pre-engagement clarification obligation holds that a competent engineer exercising reasonable professional judgment must interrogate client instructions that facially conflict with professional duties before accepting an engagement. By accepting without inquiry, Engineer B effectively committed to a structurally compromised engagement from the outset. The competing consideration is that engineers routinely accept engagements subject to client confidentiality instructions without demanding justification for each instruction, and the faithful agent duty generally requires deference to client direction on business and transition matters. The franchiser's at-will right to manage the transition, including controlling the timing of disclosures, provides a plausible business rationale that Engineer B might reasonably have credited without further inquiry.
Uncertainty arises from the indeterminacy of the threshold at which a client instruction becomes sufficiently anomalous to trigger a pre-engagement clarification duty. If the franchiser's instruction could be read as a routine confidentiality preference rather than an affirmative direction to suppress a Code-required disclosure, Engineer B's acceptance without inquiry might fall within the range of reasonable professional judgment. Additionally, even if clarification had been sought, the franchiser might have declined to explain its reasons, leaving Engineer B in the same structural conflict, meaning the clarification obligation may be necessary but not sufficient to resolve the underlying tension.
When the franchiser retained Engineer B, it explicitly instructed Engineer B not to disclose the new engagement to Engineer A. This instruction was facially anomalous: a client directing a successor engineer to conceal a peer review engagement from the incumbent engineer whose work is under review is precisely the kind of instruction that signals a structural conflict with the Code's peer review notification obligation. Engineer B accepted the engagement without seeking clarification of the franchiser's reasons for the instruction, thereby foreclosing the possibility of negotiating terms that might have honored both the faithful agent duty and the peer notification obligation simultaneously.
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?
The peer review preliminary results disclosure obligation holds that Engineer A, as the reviewed engineer, is entitled to know the substance of the review's findings so as to have a meaningful opportunity to respond to technical concerns, a purely relational disclosure (existence of engagement only) may be insufficient to protect Engineer A's professional interests if the review has already identified substantive deficiencies. The competing faithful agent duty holds that preliminary review findings constitute confidential client work product, and disclosing them without authorization constitutes an independent breach of confidentiality beyond any notification violation, the notification obligation authorizes disclosure of the engagement relationship but not transmission of substantive analytical conclusions. The reviewed engineer's technical comment opportunity preservation obligation supports broader disclosure, while the faithful agent client interest non-neglect obligation supports limiting disclosure to the minimum required.
Uncertainty arises from ambiguity about whether the peer review notification obligation's purpose, giving the incumbent an opportunity to respond to technical concerns, implicitly requires disclosure of what those concerns are, or whether notification of the engagement relationship alone is sufficient to trigger the incumbent's right to inquire. If the faithful agent duty is a general loyalty and fair dealing obligation rather than a strict fiduciary duty, the scope of what constitutes an unauthorized disclosure may be narrower, creating ambiguity about whether sharing preliminary results crosses the line. The Board's conclusion that disclosure of preliminary results compounded the violation rests on treating the notification obligation as having a defined minimum scope that does not extend to work-product transmission.
When Engineer B notified Engineer A after completing the peer review, Engineer B disclosed both the existence of the new engagement relationship with the franchiser and the preliminary results of the design review. The franchiser had explicitly instructed Engineer B to maintain confidentiality. The peer review notification obligation under Section III.8.a is designed to give the incumbent engineer an opportunity to respond to technical concerns, but the Code provision does not independently authorize the successor engineer to transmit client work product or preliminary analytical conclusions without client consent.
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?
Two competing obligations govern Engineer B's decision. The peer review notification obligation (Section III.8.a) requires that the incumbent engineer be informed of the successor's engagement so the incumbent may respond to technical concerns, this duty exists independently of client consent and reflects a categorical commitment to professional fairness and Engineer A's dignity as a rights-bearing professional. The faithful agent and trustee duty (Section II.4) requires Engineer B to act as a faithful agent to the franchiser and honor the explicit confidentiality instruction, treating client information as confidential. The Code's faithful agent standard is expressly bounded by 'within the limits of the Code,' creating ambiguity about which obligation prevails when they directly conflict.
Uncertainty arises from the absence of a clear lexical ordering in the NSPE Code for resolving conflicts between Section II.4 (faithful agent) and Section III.8.a (peer notification). If the one-week post-review notification delay is deemed reasonable under the Peer Review Notification Reasonable Timing Constraint, the warrant against proceeding is weakened. Additionally, if the faithful agent duty's 'within ethical limits' qualifier is sufficient to transform Engineer B's disclosure from a breach into a permitted act, the notification may be vindicated, but the disclosure of preliminary results beyond the minimum required by the notification obligation remains a compounding violation regardless of which primary warrant prevails.
Engineer B was retained by the franchiser to conduct a peer review of Engineer A's design work while Engineer A's contract remained active. The franchiser explicitly instructed Engineer B not to disclose the new engagement to Engineer A. Engineer B proceeded with the review without notifying Engineer A, completed the review, and only then notified Engineer A of both the engagement relationship and the preliminary review results. A parallel engagement overlap was created during which Engineer A was kept uninformed.
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?
The pre-engagement clarification obligation holds that a competent engineer exercising reasonable professional judgment must recognize when a client instruction facially conflicts with a professional duty and must seek clarification before proceeding, because acceptance of a structurally compromised engagement forecloses later compliance with competing duties. The covert peer review client instruction resistance obligation holds that Engineer B should have conditioned acceptance on the franchiser's permission to notify Engineer A, which would have forced the franchiser to either grant permission or seek a different engineer, either outcome being preferable to the covert review that resulted. Against these, the faithful agent duty supports accepting the engagement as offered, treating the confidentiality instruction as a legitimate business preference within the franchiser's contractual authority to direct the transition on its own terms.
Uncertainty is created by the unknowability of the franchiser's counterfactual response: if the franchiser would have refused to grant notification permission and simply retained a different engineer, Engineer B's refusal would have produced no improvement in Engineer A's situation while sacrificing Engineer B's own legitimate professional opportunity. Additionally, the pre-engagement clarification obligation's scope is indeterminate, it is unclear whether the Code imposes a duty to interrogate every client instruction that creates tension with a professional obligation, or only those where the conflict is irreconcilable on its face. The virtue ethics redemption question also creates uncertainty: whether Engineer B's subsequent voluntary notification partially or fully offsets the initial failure of proactive ethical vigilance.
Before conducting any review, Engineer B received an explicit instruction from the franchiser not to disclose the new engagement to Engineer A, whose contract remained active. 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 under Section III.8.a. Engineer B accepted the engagement without seeking clarification of the franchiser's reasons for the instruction or negotiating terms that might have honored both the faithful agent duty and the peer notification obligation simultaneously.
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?
The peer review preliminary results disclosure obligation and the reviewed engineer technical comment opportunity preservation obligation together support sharing preliminary findings with Engineer A, because Engineer A's opportunity to respond to technical concerns is substantively meaningful only if Engineer A knows what those concerns are, disclosure of the engagement relationship alone may be procedurally compliant but substantively hollow. Against this, the faithful agent client interest non-neglect obligation holds that disclosing preliminary review findings constitutes unauthorized transmission of client work product derived from a confidential engagement, representing an independent breach of the confidentiality duty beyond any notification violation. The incumbent engineer knowledge requirement invoked as a competing obligation supports broader disclosure, while the faithful agent trustee duty invoked against Engineer B's disclosure supports limiting disclosure to the minimum required.
Uncertainty arises from the rebuttal condition that the faithful agent duty is a general loyalty and fair dealing obligation rather than a strict fiduciary duty, which creates ambiguity about whether sharing preliminary findings, which serve Engineer A's legitimate professional interest in responding to technical concerns, constitutes a material breach or a permissible exercise of professional judgment within the scope of the notification obligation. It is also unclear whether the peer notification obligation's purpose of preserving Engineer A's technical comment opportunity implicitly requires disclosure of findings sufficient to make that opportunity meaningful, or whether the obligation is satisfied by notice of the engagement relationship alone.
After completing the design review, Engineer B notified Engineer A of both the new engagement relationship with the franchiser and the preliminary results of the review. The franchiser's confidentiality instruction had not authorized disclosure of either the engagement relationship or the review findings. The peer review notification obligation under Section III.8.a requires that the incumbent engineer be informed of the successor's engagement and given an opportunity to respond to technical concerns, but does not expressly specify whether preliminary findings must also be shared. Engineer A's contract remained active at the time of notification.
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?
Two competing obligations are in direct tension: (1) the faithful agent and trustee duty under Section II.4 requires Engineer B to follow the franchiser's confidentiality instruction and not disclose client information without authorization; (2) the peer review notification obligation under Section III.8.a requires Engineer B to inform Engineer A of the engagement so that Engineer A may have an opportunity to respond to technical concerns. The principle that client direction does not authorize ethical violations is invoked to support notification; the faithful agent duty is invoked to prohibit it. The faithful agent duty is expressly conditioned on consistency with ethical limits, which creates a potential internal hierarchy favoring the notification obligation.
Uncertainty arises because the Code does not supply a clear lexical ordering when two provisions point in opposite directions. The faithful agent duty's 'within ethical limits' qualifier may or may not be sufficient to transform Engineer B's disclosure from a breach into a permissible act. Additionally, Engineer B disclosed not only the existence of the engagement but also preliminary review results, an excess beyond what Section III.8.a requires, which compounds the faithful agent violation regardless of whether the existence-disclosure was permissible. The Board concluded the notification was inconsistent with the Code but split on whether proceeding with the review at all was ethical.
The franchiser explicitly instructed Engineer B not to disclose the new engagement to Engineer A. Engineer A's contract remained active during the review period, creating a parallel engagement overlap. Engineer B conducted the design review and subsequently notified Engineer A of both the engagement relationship and the preliminary review results. The Code's Section III.8.a independently requires that the incumbent engineer be informed of a successor's engagement.
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?
The pre-engagement clarification obligation requires engineers to interrogate client instructions that facially conflict with professional duties before accepting an engagement. The covert peer review client instruction resistance obligation suggests Engineer B should have refused to proceed under terms that made ethical compliance with Section III.8.a impossible. Against these, the faithful agent duty and the franchiser's legitimate business interest in managing a confidential transition support accepting the engagement on the client's stated terms, particularly given that Engineer A's contract was approaching expiration through a lawful non-renewal.
Uncertainty arises from the unknowability of the franchiser's counterfactual response: if the franchiser would have granted notification permission rather than seek a different engineer, conditioning acceptance on that permission would have been the optimal resolution; if the franchiser would have sought a different engineer, Engineer B's refusal would have merely displaced the ethical conflict onto a successor who might have been less scrupulous. Additionally, the at-will employment symmetry principle provides some support for the franchiser's right to manage the transition confidentially, creating genuine ambiguity about whether the confidentiality instruction was facially impermissible or merely in tension with a competing obligation.
Before conducting any review, the franchiser instructed Engineer B not to disclose the new engagement to Engineer A. Engineer A's contract was still active. The confidentiality instruction was facially anomalous, a client directing a successor engineer to conceal a peer review engagement from the incumbent whose work is under review is precisely the kind of instruction that signals a structural conflict with Section III.8.a. Engineer B accepted the engagement without seeking clarification of the instruction's rationale, foreclosing the possibility of negotiating terms that might have honored both duties simultaneously.
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?
The peer review notification obligation under Section III.8.a and the reasonable timing compliance standard together suggest that notification must precede substantive review work, because the notification's purpose, preserving the incumbent's opportunity to respond to technical concerns, is defeated if the review is already complete when notification occurs. Against this, the faithful agent duty and the franchiser's confidentiality instruction support completing the review before any disclosure, on the theory that the review itself is client work product and that notification timing is a secondary procedural matter that can be remedied post-hoc. The sequential dependency principle holds that the ethical permissibility of proceeding with the review is logically downstream of the notification timing question.
Uncertainty is created by the absence of a bright-line rule specifying when the notification obligation attaches relative to the incumbent's contract status and the review's commencement. If the one-week notification delay is deemed reasonable under the timing compliance standard, the warrant against proceeding may be weakened. Additionally, if Engineer A suffered no concrete professional harm from the timing, because Engineer A's technical comment opportunity was substantively preserved through the post-review notification, the consequentialist case against proceeding before notification is diminished. The Board split on this question and could not reach agreement.
Engineer B conducted the full design review while Engineer A remained uninformed and under an active contract. The review was completed before Engineer B notified Engineer A of the engagement relationship. Engineer A's opportunity to provide context or correct misunderstandings before Engineer B's preliminary conclusions were formed was permanently foreclosed by the time notification occurred. The franchiser's confidentiality instruction was in effect throughout the review period, and Engineer A's contract was still active during the review.
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?
Two competing obligations are in direct tension. First, Section III.8.a imposes a peer review notification obligation requiring that the incumbent engineer (Engineer A) be informed of the successor's engagement so the incumbent may respond to technical concerns, this obligation exists independently of client consent and reflects the professional dignity and participatory rights of the reviewed engineer. Second, Section II.4 imposes a faithful agent and trustee duty requiring Engineer B to act as a faithful agent to the franchiser, which the franchiser invoked through an explicit confidentiality instruction. The faithful agent duty is expressly conditioned on consistency with ethical limits, creating ambiguity about whether it can override the notification obligation. A further sub-tension exists within the notification question itself: even if some notification was required or permissible, the disclosure of preliminary review results exceeded what Section III.8.a demands, compounding the faithful agent violation beyond the minimum necessary to honor the notification obligation.
Uncertainty arises from multiple sources. First, the Code does not supply a clear lexical ordering when the faithful agent duty and the peer notification obligation point in opposite directions, leaving unresolved whether the 'within ethical limits' qualifier in Section II.4 is sufficient to make the notification obligation categorically superior. Second, the one-week post-review notification delay may or may not satisfy a 'reasonable timing' standard under Section III.8.a: if deemed reasonable, the warrant against proceeding weakens. Third, the rebuttal condition for the faithful agent analysis is whether Engineer B's disclosure of preliminary results (beyond the engagement relationship) constitutes a separable and independent breach or merely an aggravated form of the same notification act. Fourth, the consequentialist assessment is uncertain because it is unclear whether Engineer A suffered concrete professional harm from the timing, or whether a pre-review notification would have materially changed the review's outcome.
The franchiser retained Engineer B early and instructed him to keep the new engagement confidential from Engineer A. A parallel engagement overlap was created while Engineer A's contract remained active. Engineer B conducted the design review, then notified Engineer A of both the engagement relationship and the preliminary review results after the review was complete. Engineer A had been kept uninformed during the review itself.
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?
The pre-engagement clarification obligation holds that a competent engineer exercising reasonable professional judgment must recognize when a client instruction facially conflicts with a professional duty and must seek clarification before proceeding. This obligation is grounded in the principle that engineers should not accept engagements structured to make ethical compliance impossible from the outset. The competing warrant is the faithful agent duty, which generally requires deference to client instructions on business and operational matters, an engineer is not ordinarily required to interrogate every client instruction before accepting an engagement, and demanding justification for a confidentiality instruction could itself be seen as a breach of the client relationship. The at-will employment symmetry principle further supports the franchiser's position that it had legitimate business reasons for managing the transition confidentially, reasons it was not obligated to disclose to Engineer B at the outset.
Uncertainty arises from the indeterminacy of the threshold at which a client instruction becomes sufficiently anomalous to trigger a pre-engagement clarification duty. Not every unusual client instruction requires interrogation; the question is whether this particular instruction, directing concealment of a peer review engagement from the incumbent engineer, crossed the threshold of facial incompatibility with professional obligations that a competent engineer should have recognized. A further rebuttal condition is whether seeking clarification would have been futile: if the franchiser's business reasons for confidentiality were legitimate (e.g., avoiding disruption during a sensitive transition), clarification might have produced a modified engagement structure rather than a refusal, meaning the clarification obligation, if triggered, was not necessarily equivalent to a duty to decline. The virtue ethics redemption question also creates uncertainty: whether Engineer B's subsequent voluntary notification partially or fully offsets the initial failure of proactive ethical vigilance is unresolved.
The franchiser retained Engineer B and issued an explicit instruction not to disclose the new engagement to Engineer A. Engineer B accepted the engagement without seeking clarification of the reasons behind the confidentiality instruction. The 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 under Section III.8.a. By accepting without inquiry, Engineer B foreclosed the possibility of negotiating terms that might have honored both the faithful agent duty and the peer notification obligation simultaneously.
Event Timeline
Causal Flow
- 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
Opening Context
View ExtractionYou are Engineer B, a licensed engineer who has been approached by a major franchiser to review pending design concerns across several franchise facilities throughout the United States. The franchiser is in the process of ending its contract with Engineer A, the firm currently responsible for those designs, and has retained you to conduct that review before the existing contract expires. As a condition of the engagement, the franchiser has explicitly instructed you not to disclose your relationship with them to Engineer A. Engineer A's stamp and professional judgment are on the designs you are being asked to evaluate, and Engineer A has not been told a review is underway. The decisions ahead concern how you handle that instruction, when and whether you notify Engineer A, and what the scope of any such notification should include.
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.
Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation
Tension between Successor Engineer Post-Review Expired-Contract Acceptance Permissibility Obligation and Peer Review Successor Contract Incumbent Contract Expiry Prerequisite Constraint
Tension between Engineer B Covert Review Client Instruction Resistance and Covert Peer Review Client Instruction Resistance Obligation
Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Covert Peer Review Client Instruction Resistance Obligation
Tension between Peer Review Preliminary Results Disclosure to Reviewed Engineer Obligation and Faithful Agent Client Interest Non-Neglect Through Unauthorized Disclosure Obligation
Tension between Pre-Engagement Client Instruction Clarification Obligation and Faithful Agent Peer-Review Collegial Duty Boundary Obligation
Tension between Engineer B Peer Review Notification and Consent Fulfillment and Engineer B Client Confidentiality Instruction Faithful Agent Compliance
Tension between Engineer B Faithful Agent Peer Review Collegial Boundary Exercise and Franchiser Peer Review Procedural Fairness Non-Compliance Covert Instruction
Tension between Engineer B Preliminary Review Results Disclosure to Engineer A and Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure
Tension between Reviewed Engineer Technical Comment Opportunity Preservation Obligation and Faithful Agent Client Interest Non-Neglect Through Unauthorized Disclosure Obligation
Tension between Pre-Engagement Client Instruction Rationale Clarification Obligation and Covert Peer Review Client Instruction Resistance Obligation
Tension between Peer Review Preliminary Results Disclosure to Reviewed Engineer Obligation and Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation Compliance Obligation
Tension between Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case and Peer Review Notification Obligation Standard Section III.8.a
Tension between Engineer B Pre-Engagement Client Instruction Rationale Clarification BER Case and Covert Peer Review Client Instruction Resistance Obligation
Tension between Engineer B Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation BER Case and Peer Review Incumbent Notification Reasonable Timing Compliance Obligation
Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Engineer B Client Confidentiality Instruction Faithful Agent Compliance
Tension between Pre-Engagement Client Instruction Clarification Obligation and Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser
Engineer B is professionally obligated under peer review ethics to notify Engineer A that a review is being conducted — this is a foundational procedural fairness norm. Simultaneously, the Franchiser client has explicitly instructed Engineer B to keep the review covert, invoking the faithful agent duty that engineers serve their clients' interests. Fulfilling the notification obligation directly violates the client's confidentiality instruction, while complying with the client instruction directly enables a covert review that violates Engineer A's professional rights. There is no middle path: one duty must yield to the other, making this a genuine and irresolvable dilemma at the moment of engagement.
Peer review procedural fairness requires that Engineer B share preliminary findings with Engineer A, giving the reviewed engineer an opportunity to respond, correct errors, or provide context before conclusions are finalized. This protects Engineer A's professional reputation and the integrity of the review process. However, the faithful agent constraint holds that Engineer B must prioritize the Franchiser client's interests and not make disclosures the client has not authorized. Disclosing preliminary results to Engineer A could alert Engineer A to the review, allow defensive actions, or undermine the client's strategic objectives — all outcomes the Franchiser sought to prevent through the confidentiality instruction. Fulfilling the disclosure obligation thus directly conflicts with the client-primacy constraint.
Opening States (10)
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.