Step 4: Review

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.

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.

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.

Engineer B's act of notifying Engineer A of his relationship with franchiser was not consistent with the Code.

The Board was split on the second question and could not reach agreement.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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?

Was it ethical for Engineer B to proceed with the review at that time?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

The franchiser's confidentiality instruction to Engineer B directly violates the ethical prohibition on covert peer review and the principle that client instructions cannot override the incumbent engineer's right to notification under NSPE Code Section III.8.a.

By accepting the engagement without inquiring into the franchiser's rationale for the confidentiality instruction, Engineer B failed the pre-engagement clarification obligation that would have surfaced the ethical conflict between client loyalty and peer notification duties before work commenced.

Engineer B's review of Engineer A's design without prior notification violates the covert peer review prohibition and Engineer A's right to know, even though the review itself creates the obligation to subsequently disclose preliminary results and preserve Engineer A's opportunity for technical comment.

Engineer B's notification of Engineer A fulfills the paramount peer review notification obligation under Section III.8.a and preserves Engineer A's professional dignity, but simultaneously violates the faithful agent duty to the franchiser client, with the one-week delay subject to reasonableness scrutiny and the altruistic motive insufficient on its own to cure the client interest neglect.

The franchiser's termination of Engineer A, while ethically permissible as an at-will employment decision, is constrained by the requirement that Engineer B's successor contract acceptance must follow Engineer A's contract expiry and must not exploit the peer review process as a covert procurement mechanism.

The franchiser's early retention of Engineer B while Engineer A's contract is still active creates a parallel engagement overlap that violates the peer review successor contract prerequisite requiring incumbent contract expiry before successor engagement, and undermines procedural fairness obligations by initiating a covert review relationship before Engineer A's contract has concluded.

The question arose because Engineer B performed an act-notifying Engineer A-that was simultaneously compelled by one Code provision (Section III.8.a) and prohibited by another (Section II.4 faithful agent duty), making it impossible to assess Code consistency without first resolving which warrant governs. The franchiser's confidentiality instruction created the structural collision between these two obligations, forcing the question of whether compliance with one provision necessarily constitutes violation of the other.

This question emerged because the franchiser's early retention of Engineer B and the confidentiality instruction structurally required Engineer B to conduct at least some review activity before Engineer A could be informed, placing the act of proceeding itself under ethical scrutiny independent of the notification question. The absence of any confidentiality agreement protecting Engineer A's design decisions during the review period compounded the concern, making the timing and conditions of proceeding a distinct ethical issue from whether notification eventually occurred.

This question arose because Engineer B's failure to seek clarification before accepting the engagement is a temporally prior decision that shaped all subsequent ethical violations, raising the question of whether the obligation to avoid ethical conflict attaches at the moment of engagement rather than only after conflict materializes. The confidentiality instruction's facial tension with the peer review notification obligation meant that a competent engineer exercising professional judgment should have recognized the conflict risk at the pre-engagement stage, making the decision to accept without inquiry independently ethically significant.

This question emerged because the franchiser was the originating cause of the ethical conflict Engineer B faced, yet the BER case analysis focused almost entirely on Engineer B's obligations, leaving open whether the client's conduct was itself ethically assessable under the Code. The structural asymmetry between the Code's engineer-directed obligations and the franchiser's power to shape the engagement through confidentiality instructions created the question of whether client conduct that predictably induces engineer ethical violations is itself subject to ethical evaluation.

This question arose because the act of notification-already contested as a faithful agent violation-was further complicated by Engineer B's choice to include preliminary review results in that notification, raising the question of whether the content of the notification independently violated the faithful agent duty even if the notification itself was required. The absence of any confidentiality agreement governing the review created ambiguity about what information Engineer B was authorized to share, making the scope of permissible disclosure during notification a distinct ethical question from the obligation to notify at all.

This question emerged because the data - a covert review conducted under client-imposed confidentiality, followed immediately by Engineer B's retention for the full design contract - creates a factual pattern in which the peer review process appears to have functioned as a covert competitive intelligence mechanism rather than a collegial improvement exercise. The question is independently significant because it persists even if the notification timing is found reasonable, since the exploitation concern attaches to the procurement outcome rather than the notification conduct.

This question arose because the same act - Engineer B's notification of Engineer A - is simultaneously commanded by one Code provision and prohibited by another, and the Code does not supply an explicit priority rule for this conflict. The question is structurally irreducible because both warrants are grounded in legitimate Code text, making the conflict a genuine antinomy rather than a mere interpretive ambiguity.

This question emerged because the covert review data pattern directly implicates the foundational rationale for the peer notification requirement: if the incumbent engineer's professional dignity and right to respond are the purposes the rule serves, then a client instruction that systematically defeats those purposes cannot be reconciled with the rule's existence. The question forces a determination of whether client loyalty is a side-constraint on peer review procedure or a competing value capable of displacing it entirely.

This question arose because Engineer B's notification simultaneously satisfies one Code obligation (peer review notification) while violating another (faithful agent duty), and the benevolent motive that animated the disclosure creates pressure to treat the outcome - not just the act - as ethically relevant. The question is structurally significant because it tests whether the NSPE Code operates as a purely deontological system or admits consequentialist correction when competing provisions point in opposite directions.

This question arose because the franchiser's simultaneous exercise of two facially legitimate rights - the at-will right to non-renew Engineer A and the client right to instruct confidentiality to Engineer B - combined to produce a transition structure that systematically defeated the peer review notification requirement's protective purpose. The question is significant because it exposes how at-will employment authority, when deployed in conjunction with a covert review instruction, can function as a structural mechanism for circumventing procedural ethics rules without any single act being independently indefensible.

This question emerged because Engineer B received a client instruction that directly contradicted a Code-mandated peer-review notification duty, and the notification ultimately occurred only after the review was completed rather than before, making it impossible to assess compliance without first resolving whether the duty is truly categorical and client-instruction-proof. The deontological framing sharpens the question by demanding a binary answer - duty fulfilled or violated - rather than permitting a consequentialist balancing of outcomes.

This question arose because Engineer B's notification of Engineer A was simultaneously an act of Code compliance (Section III.8.a) and an act of client-instruction defiance (Section II.4), making it impossible to characterize the disclosure as purely virtuous or purely violative without resolving the hierarchical relationship between these two Code provisions. The deontological frame intensifies the question by insisting that good motive cannot cure a duty violation, forcing examination of whether a violation occurred at all.

This question emerged because the timing of Engineer B's notification - after rather than before the review - is the pivotal variable that determines whether the outcome was better or worse than the alternatives of full silence or pre-review disclosure, and the consequentialist framework requires comparing actual outcomes across counterfactual scenarios that the record does not fully resolve. The question is structurally necessary because neither full silence nor pre-review notification was chosen, making the intermediate path's net value genuinely contestable.

This question emerged because Engineer B's conduct involved two temporally distinct acts - an initial failure to seek clarification and a subsequent voluntary notification - that pull in opposite directions under virtue ethics, making it impossible to render a unified character assessment without resolving how virtue ethics weights initial omissions against subsequent corrective conduct. The question is further sharpened by the fact that Engineer B's notification was non-self-interested, which is morally relevant under virtue ethics but does not automatically cure the prior failure to exercise professional judgment at the engagement stage.

This question emerged because the conflict between faithful agency and peer-review notification duties had a structural resolution point - the pre-engagement moment - that Engineer B did not exploit, making it necessary to assess whether that unexploited leverage represented the ethically optimal path or an impractical ideal that would have produced worse outcomes. The question is counterfactual in structure, requiring evaluation of a path not taken against the actual path chosen, and it sits at the intersection of deontological duty (what Engineer B was obligated to demand) and consequentialist assessment (what outcomes the demand would have produced).

This question emerged because the actual sequence of events - review conducted before notification - left ambiguous whether the ethical violation was a function of timing alone or of the franchiser's confidentiality instruction as a categorical bar. The overlap between the active confidentiality instruction, the completed review, and the post-review notification created a structural gap in the argument: the data supports both a timing-cure reading and a categorical-prohibition reading, and neither the Code text nor the BER precedent directly adjudicates which warrant governs when pre-review notification is hypothetically substituted.

This question emerged because the data shows Engineer B disclosed both the review results and the engagement relationship, but the franchiser's instruction prohibited all disclosure, creating a gap in the argument about whether the ethical weight of the faithful agent violation scales with the content and scope of what is disclosed. The absence of any graduated violation framework in the Code or BER precedent - combined with the peer review obligation's focus on the reviewed engineer's opportunity to comment - left open whether partial disclosure could occupy a morally intermediate position between full compliance and full violation.

This question emerged because the active contract state of Engineer A is embedded in the data as a morally significant fact - it is what makes the covert review instruction particularly harmful and what gives the peer review notification obligation its sharpest application - but the BER analysis does not explicitly isolate contract-active status as a necessary condition for the notification obligation, leaving open whether the obligation's ethical weight is contingent on that status or independent of it. The hypothetical substitution of an expired contract thus contests the warrant's scope condition and simultaneously tests whether the franchiser's confidentiality instruction becomes more defensible when the incumbent's contractual stake has already lapsed.

The board concluded that the franchiser acted unethically by directing Engineer B to conceal the engagement, because the instruction was structurally designed to exploit the transitional period and predictably forced Engineer B into conflict with peer review obligations - and while the Code does not directly bind non-engineer clients, the principle that client direction cannot authorize ethical violations implicitly recognizes client responsibility for instructions that foreseeably produce such violations.

The board concluded that Engineer B's notification of Engineer A was not consistent with the Code because it breached the faithful agent and client confidentiality duties owed to the franchiser, and the peer review notification obligation under Section III.8.a did not, in the board's determination, independently authorize Engineer B to override the franchiser's explicit confidentiality instruction.

The board concluded that Engineer B's acceptance of the engagement without first seeking clarification was itself an independent ethical failure, because the confidentiality instruction was facially anomalous and a competent engineer exercising reasonable professional judgment should have recognized the conflict with peer review obligations before committing to terms that made simultaneous compliance with both duties impossible.

The board concluded that Engineer B's disclosure of the preliminary review results compounded the faithful agent violation by exceeding what the peer notification obligation required - the notification duty authorized Engineer B to inform Engineer A of the engagement's existence, but did not authorize transmission of confidential analytical conclusions, making the disclosure of results an independent ethical misstep that the peer review rationale alone could not justify.

The board reached no conclusion on Question 2 because members were split and could not achieve agreement, leaving the question of whether it was ethical for Engineer B to proceed with the review at that time formally unresolved without a majority determination.

The board concluded that Engineer B committed an independent ethical lapse distinct from the notification timing violation by accepting the engagement without first questioning the franchiser's confidentiality instruction, because a competent and ethically attentive engineer should have recognized that the instruction itself signaled a conflict between faithful agency and peer review obligations, and inquiry at that stage could have foreclosed the subsequent violation entirely.

The board concluded that while the notification's timing and manner were imperfect, the conclusion may overstate the faithful agent duty's weight by failing to account for its built-in ethical ceiling, because the franchiser's confidentiality instruction was not a neutral business preference but an affirmative directive to suppress a Code-required disclosure, placing it outside the protected scope of faithful agency.

The board concluded that Engineer B's simultaneous disclosure of preliminary review results to Engineer A compounded the faithful agent violation with an independent breach of client confidentiality, because the peer review notification requirement - whatever its scope - does not authorize the transmission of confidential work-product conclusions derived from a client engagement, and the two disclosure acts should be assessed separately rather than treated as a single undifferentiated notification event.

The board concluded that its split on Q2 obscures an important structural point: the ethical permissibility of proceeding with the review was logically downstream of the notification timing question, so the inability to reach agreement on Q2 may reflect a failure to recognize that a Q1 finding requiring pre-review notification necessarily resolves Q2 against Engineer B, making the review's conduct without prior notification independently impermissible under the Code.

The board concluded that Engineer B's acceptance of the full design contract - obtained in part through knowledge gained during the covert peer review - raises an independent ethical concern about exploitation of the peer review framework for procurement advantage, because the peer review process is structurally corrupted when it functions as a client-directed competitive evaluation rather than a collegial quality-assurance mechanism, warranting separate analysis beyond the notification and faithful agency questions the board formally resolved.

The board concluded that the franchiser's covert review instruction was an ethically impermissible client act because a client who knowingly directs an engineer to violate a Code provision is an active participant in the ethical conflict, not merely a passive beneficiary, and future guidance should require engineers to refuse such instructions at the point of engagement rather than navigate the resulting conflict retroactively.

The board concluded that even if Engineer B's acceptance of the successor contract was not a clear Code violation, the manner in which the peer review was conducted - covertly, with Engineer A unable to participate or respond - provided Engineer B with an informational competitive advantage that raises serious unresolved questions about whether the boundary between collegial review and competitive positioning was respected.

The board concluded that the faithful agent duty and the peer notification obligation are not irreconcilable - the former yields to the latter only to the extent required by the notification mandate, meaning Engineer B was obligated to disclose the existence of the engagement but not the preliminary results, and the disclosure of preliminary results therefore remained a faithful agent violation even though the notification itself was required.

The board concluded that professional dignity cannot be permanently subordinated to client confidentiality in peer review contexts because doing so would fundamentally undermine the purpose of peer review, and that client confidentiality instructions, while legitimate and important, do not extend to overriding the procedural rights of incumbent engineers whose professional standing is directly at stake in the review.

The board concluded that while Engineer B's notification produced a net-beneficial outcome under tripartite interest balancing and was motivated by genuine professional concern, those factors mitigate but do not rehabilitate the ethical violations, because the timing and scope deficiencies reflected a structural failure to organize the engagement in a way that could have honored all relevant Code obligations simultaneously.

The board concluded that the franchiser acted improperly by using the overlap period between Engineer A's notice and contract expiration to conduct a covert review, finding that the at-will employment principle - while valid for non-renewal decisions - cannot be weaponized to circumvent the procedural protections that peer review notification timing requirements are specifically designed to provide. The franchiser effectively converted a transition mechanism into a vulnerability window, which the board found structurally incompatible with the Code's engineer relations provisions.

The board applied a Kantian framework to determine that when two professional duties conflict, the duty that is categorical and unconditional takes precedence over the duty that is relational and explicitly conditioned on ethical limits, leading to the conclusion that Engineer B was right to notify Engineer A but wrong to disclose preliminary results, since that excess disclosure served no categorical duty and simply exceeded the scope of the competing obligation that justified overriding the confidentiality instruction.

The board concluded from a consequentialist standpoint that Engineer B's timing of notification was ethically suboptimal because the delay permanently eliminated Engineer A's ability to provide context before conclusions were formed, and that while the eventual notification partially mitigated the harm, a pre-review notification would have maximized net benefit across all three affected parties - Engineer A, the franchiser, and the professional community - by preserving procedural integrity without necessarily requiring a greater breach of the faithful agent duty.

The board concluded that Engineer B's conduct reflected partial but incomplete professional virtue: the voluntary notification decision demonstrated genuine collegial respect and moral courage consistent with a professionally virtuous engineer, but the failure to recognize and address the structural conflict between the confidentiality instruction and the peer notification obligation before accepting the engagement revealed an absence of the proactive ethical character that virtue ethics expects, making the subsequent notification a reactive correction rather than an expression of fully integrated professional integrity.

The board concluded that the ethically optimal resolution would have been for Engineer B to condition acceptance of the engagement on the franchiser's permission to notify Engineer A prior to the review, because this strategy would have preserved both the peer review notification obligation and the faithful agent duty without requiring Engineer B to violate either, and would have correctly allocated responsibility for any resulting delay or disruption to the franchiser - the party whose ethically incompatible instruction created the conflict in the first place.

The board concluded that pre-review notification would have been ethically superior on two independent grounds - it would have better served Engineer A's substantive interests under Section III.8.a and would have constituted a narrower breach of the faithful agent duty by disclosing only the existence of the engagement rather than both the engagement and preliminary results - but that the franchiser's confidentiality instruction made any timing of notification impermissible under a strict faithful agent reading, meaning timing modulates the degree of violation rather than eliminating it.

The board concluded that contract expiration meaningfully diminishes the ethical weight of the peer review notification obligation because the incumbent's direct professional accountability for the work is reduced, thereby making the franchiser's confidentiality instruction more defensible under the faithful agent standard, but that the notification obligation persists in attenuated form because the review's findings may still affect the incumbent's professional reputation and may be used to justify non-renewal or guide remediation by the successor engineer.

The board concluded that the faithful agent duty prevailed on the narrow question of whether Engineer B's notification was proper, but the split on Q2 demonstrates that this resolution was partial rather than principled - the board effectively deferred the harder question of whether the entire engagement was permissible, and the unresolved tension implies that the Code implicitly prohibits engineers from accepting engagements structured to make simultaneous compliance with both provisions impossible.

The board concluded that the internal contradiction between invoking 'client direction cannot override ethics' to justify notification and then invoking the faithful agent principle to condemn it reveals that the former principle functions as a trump only when the competing obligation is unambiguous and superior - conditions not met here - and that the more durable lesson is that Engineer B's failure to seek pre-engagement clarification of the confidentiality instruction was the point at which the irreconcilable conflict could have been avoided.

The board concluded that professional dignity was effectively subordinated to client loyalty in the Q1 resolution, but that this subordination was not cost-free: permitting client confidentiality instructions to override the incumbent engineer's right to know that their work is under review hollows out the peer review system's foundational purpose, and the Code's peer notification obligation should therefore be understood as a non-waivable duty that clients cannot override through confidentiality instructions, even where the faithful agent duty would otherwise require deference to client direction.

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?