Step 4: Full View

Entities, provisions, decisions, and narrative

Appropriate Notification And Review Of Another Engineer's Work
Step 4 of 5

299

Entities

4

Provisions

1

Precedents

18

Questions

25

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
The ethical situation is trapped in a dual-obligation lock: Engineer B's faithful agent duty to the franchiser and the peer review notification duty to Engineer A are both recognized as legitimate Code obligations, yet the franchiser's confidentiality instruction made simultaneous compliance structurally impossible. The Board's split on Q2 and its layered, non-convergent conclusions across C1–C25 confirm that the tension was not resolved — it was documented, partially condemned, and left standing. No single party was relieved of its obligation, no clean transfer of responsibility occurred, and no temporal cycling was identified; instead, the stakeholders remain caught between incompatible rule-sets that the Code does not supply a clear lexical ordering to resolve.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
Provision (e.g., I.1.) Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis Entity (hidden by default)
Edges:
informs answered by applies to
Provisions (4)
View Extraction
II.1.c. Engineers shall not reveal facts, data, or information without the prior consent of the client or employer except as authorized or required by law or this Code.
How this applies in the case (showing 3 of 37)
Obligation
Engineer B Covert Review Client Instruction Resistance
II.1.c. governs when facts or information may be revealed, directly relevant to whether Engineer B could resist covert review instructions by assessing permissible disclosure boundaries.
Action
Franchiser Instructs Confidentiality to Engineer B
This provision governs the obligation not to reveal confidential facts or data, directly relevant to the franchiser instructing Engineer B to keep information confidential.
State
Franchiser Covert Review Instruction to Engineer B
The franchiser's instruction to conceal the engagement relates to withholding facts from Engineer A without consent, implicating disclosure restrictions.
Obligation (7)
  • Engineer B Covert Review Client Instruction Resistance
    II.1.c. governs when facts or information may be revealed, directly relevant to whether Engineer B could resist covert review instructions by assessing permissible disclosure boundaries.
  • Engineer B Peer Review Notification of Engineer A Despite Client Instruction
    II.1.c. addresses the tension between client confidentiality instructions and authorized disclosure, directly bearing on Engineer B's obligation to notify Engineer A despite the franchiser's instruction.
  • Engineer B Peer Review Notification and Consent Fulfillment
    II.1.c. requires consent before revealing information, directly linking to Engineer B's obligation to obtain or navigate consent when notifying Engineer A of the peer review.
  • Engineer B Preliminary Review Results Disclosure to Engineer A
    II.1.c. restricts disclosure of facts and data without client consent, directly applicable to whether Engineer B could disclose preliminary review results to Engineer A.
  • Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case
    II.1.c. is the confidentiality provision that underlies the franchiser's instruction not to disclose, directly shaping Engineer B's obligation to comply with that instruction.
  • Engineer B Altruistic Disclosure Non-Justification for Client Interest Neglect BER Case
    II.1.c. establishes that disclosure without consent is restricted regardless of motive, directly relevant to whether altruistic intent justifies overriding client confidentiality.
  • Franchiser Peer Review Procedural Fairness Non-Compliance Covert Instruction
    II.1.c. sets the framework for permissible disclosure, directly relevant to evaluating whether the franchiser's covert instruction was consistent with the Code.
Action (2)
  • Franchiser Instructs Confidentiality to Engineer B
    This provision governs the obligation not to reveal confidential facts or data, directly relevant to the franchiser instructing Engineer B to keep information confidential.
  • Engineer B Reviews Design Information
    Engineer B reviewing another engineer's design information raises the question of whether that information can be disclosed or used without consent.
State (4)
  • Franchiser Covert Review Instruction to Engineer B
    The franchiser's instruction to conceal the engagement relates to withholding facts from Engineer A without consent, implicating disclosure restrictions.
  • Client Covert Review Instruction to Engineer B
    The client's instruction not to notify Engineer A directly involves controlling disclosure of information, which this provision governs.
  • Engineer B Client-Directed Confidentiality Instruction Voluntarily Overridden
    Engineer B's decision to notify Engineer A despite the confidentiality instruction raises the question of whether disclosure was authorized or required by the Code.
  • Peer Review Confidentiality Agreement Absent. Engineer A Design Review
    The absence of a confidentiality agreement affects whether Engineer B's review and potential disclosure of Engineer A's design information was permissible under this provision.
Constraint (5)
  • Faithful Agent Client Instruction Non-Disclosure. Engineer B Obligation to Follow Franchiser Confidentiality Instruction
    II.1.c prohibits revealing information without client consent, directly grounding Engineer B's obligation to follow the franchiser's non-disclosure instruction.
  • Client Confidentiality Instruction Peer Review Notification Non-Override. Franchiser Instruction to Engineer B
    II.1.c establishes the confidentiality duty that the franchiser's instruction invokes, but which cannot override Engineer B's collegial notification obligation.
  • Engineer B Faithful Agent Client Non-Disclosure Instruction Compliance Constraint Instance
    II.1.c directly creates the constraint requiring Engineer B not to disclose the review engagement once the franchiser issued the non-disclosure instruction.
  • Engineer B Altruistic Motive Non-Override of Faithful Agent Duty Instance
    II.1.c underlies the faithful agent non-disclosure duty that Engineer B's altruistic motive could not override.
  • Engineer B Client Benefit vs. All-Party Benefit Disclosure Balancing Constraint Instance
    II.1.c creates the client confidentiality side of the balancing constraint Engineer B faced when deciding whether to disclose the review engagement.
Principle (7)
  • Client Direction Does Not Authorize Ethical Violation Invoked Against Franchiser Confidentiality Instruction
    This provision establishes the general duty not to reveal information without consent, which is the basis the franchiser invoked to instruct Engineer B to maintain confidentiality.
  • Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure
    This provision directly supports the argument that Engineer B should not have disclosed the review engagement without the client's consent.
  • Client Loyalty Invoked By Franchiser Toward Engineer B Confidentiality Instruction
    The franchiser's confidentiality instruction to Engineer B is grounded in this provision's prohibition on revealing client information without consent.
  • Client Loyalty Invoked to Constrain Engineer B Disclosure
    This provision embodies the duty to withhold client information without consent, directly constraining Engineer B's disclosure to Engineer A.
  • Benevolent Motive Does Not Cure Ethical Violation Applied to Engineer B
    This provision establishes that disclosure without consent is a violation regardless of the disclosing engineer's motivation.
  • Pre-Engagement Client Instruction Clarification Obligation Applied to Engineer B
    This provision's consent requirement implies Engineer B should have clarified the confidentiality instruction before accepting the engagement.
  • Competing Code Provision Balancing Applied to Peer Notification vs. Faithful Agent Duty
    This provision is one side of the competing obligations the Board balanced against the peer notification duty.
Role (2)
  • Engineer B Confidentiality-Directed Successor Design Engineer
    Engineer B was directed by the client not to disclose the engagement, raising the question of whether revealing or withholding facts about the review was permissible under this provision.
  • Engineer B Faithful Agent Peer-Notification-Conflicted Reviewing Engineer
    Engineer B faced a direct conflict between the client's instruction to withhold information and the obligation not to improperly conceal facts from affected parties.
Event (2)
  • Confidentiality Instruction Imposed on Engineer B
    The instruction to keep Engineer B silent directly implicates the provision governing when engineers may or may not reveal facts without client consent.
  • Engineer A Kept Uninformed During Review
    Withholding information from Engineer A during the review relates to the conditions under which facts and data may be concealed from a party.
Resource (3)
  • NSPE Code of Ethics - Sections II.1.c, III.4, III.4.a & b
    This provision is directly cited in this resource to clarify the scope of confidentiality obligations and distinguish them from the trustee duty in II.4.
  • Engineer-Confidentiality-and-Loyalty-Obligation-Standard-Instance
    This provision governs the tension between Engineer B's duty to follow the franchiser's confidentiality instruction and professional obligations of fairness.
  • NSPE-Code-of-Ethics
    This provision is part of the primary normative authority governing Engineer B's obligations regarding disclosure of information without client consent.
Capability (5)
  • Engineer B Covert Review Instruction Resistance
    This provision concerns revealing facts without consent, directly relevant to Engineer B resisting the instruction to conduct a covert review that would withhold information from Engineer A.
  • Engineer B Client Instruction Non-Override Collegial Notification Self-Recognition
    The provision on not revealing information without consent is what the franchiser invoked, and Engineer B had to recognize it did not override the collegial notification duty.
  • Engineer B Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation BER Case
    Engineer B needed to distinguish the scope of II.1.c confidentiality from the faithful agent duty under II.4 to correctly interpret their obligations.
  • Engineer B Pre-Engagement Client Confidentiality Instruction Rationale Inquiry BER Case
    The franchiser's instruction not to disclose was grounded in II.1.c, making it directly relevant to Engineer B's failure to seek clarification before accepting the engagement.
  • Engineer B Peer Review vs Faithful Agent Dual Code Provision Conflict Resolution BER Case
    II.1.c is one of the provisions Engineer B had to weigh when resolving the conflict between confidentiality obligations and peer review notification duties.
II.4. Engineers shall act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 50)
Obligation
Engineer B Faithful Agent Peer Review Collegial Boundary Exercise
II.4. directly requires engineers to act as faithful agents, which is the provision Engineer B must balance against collegial duties to Engineer A.
Action
Engineer B Accepts Project Without Clarification
Accepting a project without clarifying the relationship to the existing engineer may conflict with Engineer B's duty to act as a faithful agent or trustee to the client.
State
Franchiser Covert Review Instruction to Engineer B
Engineer B's duty as a faithful agent to the franchiser includes following the client's instruction to keep the engagement confidential.
Obligation (7)
  • Engineer B Faithful Agent Peer Review Collegial Boundary Exercise
    II.4. directly requires engineers to act as faithful agents, which is the provision Engineer B must balance against collegial duties to Engineer A.
  • Engineer B Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation BER Case
    II.4. is the exact provision being interpreted as a general duty of loyalty and fair dealing rather than a strict fiduciary standard in this obligation.
  • Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case
    II.4. obligates Engineer B to act as a faithful agent for the franchiser, directly grounding the obligation to comply with the client's confidentiality instruction.
  • Engineer B Faithful Agent Peer-Review Collegial Duty Boundary BER Case Discussion
    II.4. is the direct source provision for the faithful agent and trustee standard discussed in this obligation regarding the boundary between client loyalty and collegial duties.
  • Engineer B Altruistic Disclosure Non-Justification for Client Interest Neglect BER Case
    II.4. requires faithful service to the client, directly relevant to the obligation that altruistic motives do not justify neglecting the franchiser's interests.
  • Engineer A Incumbent Faithful Performance During Contract Wind-Down
    II.4. requires engineers to act as faithful agents for their employer or client, directly grounding Engineer A's obligation to continue performing contracted services faithfully.
  • Engineer B Pre-Engagement Client Instruction Rationale Clarification BER Case
    II.4. establishes the faithful agent duty that Engineer B must understand before accepting engagement, directly relevant to clarifying the client instruction's rationale.
Action (3)
  • Engineer B Accepts Project Without Clarification
    Accepting a project without clarifying the relationship to the existing engineer may conflict with Engineer B's duty to act as a faithful agent or trustee to the client.
  • Engineer B Notifies Engineer A of Relationship and Review
    Notifying Engineer A reflects Engineer B acting in good faith and as a faithful agent by being transparent about the overlapping professional relationship.
  • Franchiser Retains Engineer B Early
    The franchiser retaining Engineer B while Engineer A is still engaged raises concerns about whether Engineer B is acting as a faithful agent given the conflict of interest.
State (6)
  • Franchiser Covert Review Instruction to Engineer B
    Engineer B's duty as a faithful agent to the franchiser includes following the client's instruction to keep the engagement confidential.
  • Client Covert Review Instruction to Engineer B
    Acting as a faithful agent requires Engineer B to honor the client's explicit instruction not to notify Engineer A.
  • Engineer B Client-Directed Confidentiality Instruction Voluntarily Overridden
    Engineer B's decision to notify Engineer A against the client's wishes constitutes a direct breach of the faithful agent duty owed to the client.
  • Notification Duty vs. Faithful Agent Duty Conflict
    This entity directly embodies the tension between Engineer B's faithful agent obligation under II.4 and the notification duty under III.8.a.
  • Engineer B Non-Self-Interested Faithful Agent Violation
    Even without self-interest, Engineer B's disclosure still violated the faithful agent duty this provision establishes.
  • Engineer B Failure to Explore Client Motive Pre-Engagement
    A faithful agent would have clarified the client's reasons for the confidentiality instruction before accepting the engagement.
Constraint (8)
  • Faithful Agent Client Instruction Non-Disclosure. Engineer B Obligation to Follow Franchiser Confidentiality Instruction
    II.4 directly establishes the faithful agent and trustee duty that grounds Engineer B's obligation to follow the franchiser's confidentiality instruction.
  • Faithful Agent Duty Peer Review Collegial Obligation Boundary. Engineer B Notification of Engineer A Despite Franchiser Instruction
    II.4 creates the faithful agent duty whose boundary with collegial obligations under III.8.a is the central tension in this constraint.
  • Engineer B Faithful Agent Client Non-Disclosure Instruction Compliance Constraint Instance
    II.4 is the direct source of the faithful agent duty constraining Engineer B to comply with the franchiser's non-disclosure instruction.
  • Engineer B Altruistic Motive Non-Override of Faithful Agent Duty Instance
    II.4 establishes the faithful agent duty that Engineer B's altruistic motive could not override.
  • Trustee Term General Loyalty Non-Fiduciary Interpretation. BER Case 93-3
    II.4 contains the term trustee whose interpretation as general loyalty rather than strict fiduciary duty is the subject of this constraint.
  • Engineer Relations Code Provision Client Need Balancing. BER Case 93-3
    II.4 is one of the code provisions governing engineer relations that must be balanced against client needs in BER Case 93-3.
  • Engineer B Client Benefit vs. All-Party Benefit Disclosure Balancing Constraint Instance
    II.4 creates the faithful agent duty that forms one side of the balancing constraint Engineer B faced regarding disclosure.
  • Client Confidentiality Instruction Peer Review Notification Non-Override. Franchiser Instruction to Engineer B
    II.4 establishes the faithful agent duty invoked by the franchiser's instruction, which nonetheless cannot override Engineer B's notification obligation.
Principle (7)
  • Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser
    This provision directly establishes the faithful agent and trustee duty that Engineer B owed to the franchiser client.
  • Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure
    This provision is the direct source of the faithful agent and trustee obligation invoked to argue Engineer B should not have disclosed the engagement.
  • Client Loyalty Invoked By Franchiser Toward Engineer B Confidentiality Instruction
    This provision embodies the client loyalty dimension that the franchiser invoked when instructing Engineer B to maintain confidentiality.
  • Client Loyalty Invoked to Constrain Engineer B Disclosure
    This provision directly establishes the faithful agent duty that required Engineer B to respect the client's explicit confidentiality instruction.
  • Competing Code Provision Balancing Applied to Peer Notification vs. Faithful Agent Duty
    This provision is explicitly identified as one of the two competing code provisions the Board balanced in resolving the case.
  • Tripartite Interest Balancing Invoked In Engineer A to Engineer B Transition
    The faithful agent duty under this provision is one of the interests that had to be balanced in managing the engineer transition.
  • Client Direction Does Not Authorize Ethical Violation Invoked Against Franchiser Confidentiality Instruction
    This provision establishes the faithful agent duty whose limits are tested when a client direction would require an ethical violation.
Role (3)
  • Engineer B Confidentiality-Directed Successor Design Engineer
    Engineer B was retained by the franchiser and owed faithful agent duties to that client while navigating the confidentiality instruction.
  • Engineer B Faithful Agent Peer-Notification-Conflicted Reviewing Engineer
    This provision directly governs Engineer B's duty to act as a faithful agent to the client while also balancing professional obligations to notify Engineer A.
  • Engineer A Outgoing Incumbent Design Engineer
    Engineer A owed faithful agent duties to the franchiser throughout the wind-down period of the contract, including handling pending design work responsibly.
Event (3)
  • Parallel Engagement Overlap Created
    Engaging Engineer B while Engineer A was still under contract raises questions about faithful agency to the existing client-engineer relationship.
  • Design Review Completed Under Conflict
    Completing a design review under conflicting loyalties directly challenges the duty to act as a faithful agent or trustee to the employer or client.
  • Engineer A Kept Uninformed During Review
    Keeping Engineer A uninformed while reviewing their work undermines the faithful agent obligation owed to Engineer A as the incumbent engineer.
Resource (6)
  • NSPE Code of Ethics - Section II.4
    This resource directly references Section II.4 to establish the faithful agent or trustee obligation owed by Engineer B to the franchiser client.
  • Agent-Trustee Distinction Framework (NSPE Code Interpretation)
    This provision is the basis for the Board's analysis distinguishing between agent and trustee roles under the Code.
  • Agent-Trustee Loyalty Obligation Standard (General Duty of Fair Dealing)
    This provision grounds the countervailing obligation that Engineer B as faithful agent or trustee must deal fairly with the client's transaction.
  • Black's Law Dictionary (Fourth Edition)
    This provision's use of the term trustee prompted the Board to consult this resource for an authoritative definition clarifying its meaning.
  • NSPE Code of Ethics - Sections II.1.c, III.4, III.4.a & b
    This resource references II.4 alongside these other provisions to clarify that trustee in II.4 denotes general loyalty rather than strict fiduciary confidentiality.
  • NSPE-Code-of-Ethics
    This provision is part of the primary normative authority governing Engineer B's duty of loyalty and faithful agency to the franchiser.
Capability (7)
  • Engineer A Incumbent Faithful Performance During Contract Wind-Down
    II.4 requires faithful agent performance, directly obligating Engineer A to continue serving the franchiser competently during the wind-down period.
  • Engineer B Faithful Agent Peer Review Collegial Boundary Exercise
    II.4 is the provision Engineer B had to interpret to understand that faithful service to the franchiser did not extend to suppressing collegial notification obligations.
  • Engineer B Faithful Agent Trustee Term Scope Interpretation BER Case
    II.4 is the exact provision whose trustee and faithful agent language Engineer B needed to correctly interpret as general loyalty rather than strict fiduciary confidentiality.
  • Engineer B Peer Review vs Faithful Agent Dual Code Provision Conflict Resolution BER Case
    II.4 is one of the two provisions in direct tension that Engineer B needed to resolve when deciding whether to notify Engineer A.
  • Engineer B Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation BER Case
    II.4 is the provision whose faithful agent and trustee language required correct interpretation to distinguish it from the confidentiality obligations under II.1.c and III.4.
  • Engineer B Peer Review Collegial Improvement Purpose Fidelity BER Case
    II.4 requires Engineer B to serve the franchiser faithfully, which includes conducting the peer review for its legitimate purpose without exceeding its proper scope.
  • Engineer B Successor Contract Acceptance Incumbent Expiration Prerequisite Recognition
    II.4 faithful agent duty to the franchiser must be balanced against fair dealing toward Engineer A, making it relevant to when successor contract acceptance is permissible.
III.4. Engineers shall not disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve.
How this applies in the case (showing 3 of 39)
Obligation
Engineer B Covert Review Client Instruction Resistance
III.4. prohibits disclosure of confidential information without consent, directly relevant to evaluating the legitimacy of the franchiser's instruction for covert review.
Action
Franchiser Instructs Confidentiality to Engineer B
This provision directly governs the non-disclosure of confidential business or technical information, which the franchiser is instructing Engineer B to maintain.
State
Peer Review Confidentiality Agreement Absent. Engineer A Design Review
Engineer B's review of Engineer A's design work without a confidentiality agreement raises concerns about protecting confidential technical information belonging to a prior engineer-client relationship.
Obligation (6)
  • Engineer B Covert Review Client Instruction Resistance
    III.4. prohibits disclosure of confidential information without consent, directly relevant to evaluating the legitimacy of the franchiser's instruction for covert review.
  • Engineer B Peer Review Notification of Engineer A Despite Client Instruction
    III.4. restricts disclosure of confidential client information, directly creating the tension Engineer B faces when deciding whether to notify Engineer A against client instruction.
  • Engineer B Preliminary Review Results Disclosure to Engineer A
    III.4. prohibits disclosing confidential technical information without consent, directly applicable to whether Engineer B may share preliminary review results with Engineer A.
  • Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case
    III.4. is the confidentiality provision that reinforces the franchiser's instruction not to disclose, directly supporting Engineer B's obligation to maintain confidentiality.
  • Franchiser Client Peer Review Procedural Fairness Client Instruction Non-Override BER Case
    III.4. establishes confidentiality protections that inform the limits of what the franchiser can instruct Engineer B to keep confidential during the peer review process.
  • Engineer B Peer Review Notification and Consent Fulfillment
    III.4. directly governs disclosure of confidential information, relevant to Engineer B's obligation to navigate consent requirements when notifying Engineer A.
Action (2)
  • Franchiser Instructs Confidentiality to Engineer B
    This provision directly governs the non-disclosure of confidential business or technical information, which the franchiser is instructing Engineer B to maintain.
  • Engineer B Reviews Design Information
    Engineer B reviewing confidential design information from Engineer A's work is governed by the prohibition on disclosing confidential technical processes without consent.
State (5)
  • Peer Review Confidentiality Agreement Absent. Engineer A Design Review
    Engineer B's review of Engineer A's design work without a confidentiality agreement raises concerns about protecting confidential technical information belonging to a prior engineer-client relationship.
  • Franchiser Covert Review Instruction to Engineer B
    The franchiser's instruction to conceal the engagement relates to protecting confidential business affairs of the client relationship from unauthorized disclosure.
  • Client Covert Review Instruction to Engineer B
    The client's confidentiality instruction reflects an interest in protecting business affairs, which this provision requires engineers to respect.
  • Engineer A Client Relationship Established. Franchiser
    Engineer A's multi-year relationship with the franchiser means information about that engagement constitutes confidential business affairs protected under this provision.
  • Incumbent Engineer Under Active Review Without Knowledge
    Reviewing Engineer A's prior work without consent implicates the protection of confidential technical processes associated with Engineer A's prior client engagement.
Constraint (5)
  • Covert Peer Review Prohibition. Franchiser Instruction to Engineer B
    III.4 prohibits disclosure of confidential information without consent, providing the basis for the franchiser's confidentiality instruction to Engineer B.
  • No-Confidentiality-Agreement Peer Review Ethical Obligation Persistence. Engineer B Post-Review Successor Engagement
    III.4 establishes that confidentiality obligations persist even without a formal agreement, directly supporting this constraint.
  • Post-Peer-Review Insider Knowledge State-Law-Variable Conflict Assessment. Engineer B Successor Design Engineering Engagement
    III.4 prohibits use of confidential technical information gained during the peer review, requiring Engineer B to assess conflicts before accepting the successor contract.
  • Peer Review Program Collegial Improvement Non-Exploitation. Engineer B Successor Contract Acceptance
    III.4 prohibits exploiting confidential technical processes learned during the peer review to gain competitive advantage in the successor engagement.
  • Engineer Relations Code Provision Client Need Balancing. BER Case 93-3
    III.4 is one of the code provisions governing engineer relations that must be balanced against client needs in BER Case 93-3.
Principle (6)
  • Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure
    This provision reinforces the prohibition on disclosing confidential client information without consent, supporting the argument against Engineer B's disclosure.
  • Client Loyalty Invoked By Franchiser Toward Engineer B Confidentiality Instruction
    This provision directly supports the franchiser's instruction by prohibiting disclosure of confidential business affairs without consent.
  • Client Loyalty Invoked to Constrain Engineer B Disclosure
    This provision embodies the confidentiality obligation that constrained Engineer B from disclosing the review engagement to Engineer A.
  • Client Direction Does Not Authorize Ethical Violation Invoked Against Franchiser Confidentiality Instruction
    This provision establishes the confidentiality duty that the franchiser's instruction relied upon, whose limits are at issue when it conflicts with other ethical obligations.
  • Benevolent Motive Does Not Cure Ethical Violation Applied to Engineer B
    This provision establishes that unauthorized disclosure of confidential information is a violation regardless of the engineer's good faith motivation.
  • Pre-Engagement Client Instruction Clarification Obligation Applied to Engineer B
    This provision's confidentiality requirement underscores why Engineer B should have clarified the scope and reasons for the client's instruction before acting.
Role (3)
  • Engineer B Confidentiality-Directed Successor Design Engineer
    Engineer B was obligated not to disclose confidential technical or business information about the franchiser's affairs learned during the review engagement.
  • Engineer B Faithful Agent Peer-Notification-Conflicted Reviewing Engineer
    Engineer B's review of Engineer A's work involved access to confidential client information, making this provision directly applicable to Engineer B's conduct.
  • Client Confidentiality-Instructing Engineering Services Client
    The client's instruction to Engineer B to maintain confidentiality about the engagement reflects the client's interest protected under this provision.
Event (3)
  • Confidentiality Instruction Imposed on Engineer B
    The confidentiality instruction placed on Engineer B directly concerns the non-disclosure of information related to a client or employer's technical processes.
  • Multi-Year Relationship Established
    The long-standing relationship created confidential knowledge that Engineer B was then instructed not to disclose to Engineer A.
  • Design Review Completed Under Conflict
    Reviewing Engineer A's design without consent risks exposing confidential technical processes belonging to the prior engineer-client relationship.
Resource (3)
  • NSPE Code of Ethics - Sections II.1.c, III.4, III.4.a & b
    This provision is directly cited in this resource to address confidentiality obligations and distinguish them from the general loyalty duty under II.4.
  • Engineer-Confidentiality-and-Loyalty-Obligation-Standard-Instance
    This provision governs Engineer B's obligation not to disclose confidential information, directly relevant to the franchiser's instruction to withhold notification from Engineer A.
  • NSPE-Code-of-Ethics
    This provision is part of the primary normative authority governing Engineer B's confidentiality obligations to the franchiser client.
Capability (6)
  • Engineer B Covert Review Instruction Resistance
    III.4 prohibits disclosing confidential information without consent, which is the basis the franchiser used to instruct Engineer B not to disclose the review to Engineer A.
  • Engineer B Client Instruction Non-Override Collegial Notification Self-Recognition
    III.4 is the confidentiality provision the franchiser's instruction invoked, and Engineer B had to recognize it did not override the peer review notification obligation.
  • Engineer B Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation BER Case
    III.4 is the confidentiality provision whose scope Engineer B needed to distinguish from the faithful agent duty under II.4 to correctly resolve the conflict.
  • Engineer B Pre-Engagement Client Confidentiality Instruction Rationale Inquiry BER Case
    III.4 underpins the franchiser's confidentiality instruction, making it directly relevant to Engineer B's failure to inquire about the rationale before accepting the engagement.
  • Franchiser Peer Review Procedural Fairness Design BER Case
    III.4 sets the confidentiality boundary the franchiser had to respect when designing a procedurally fair peer review process that still allowed proper notification.
  • Franchiser Peer Review Procedural Fairness Design Obligation
    III.4 is relevant to the franchiser's obligation to design a peer review process that balances confidentiality concerns with the procedural fairness owed to Engineer A.
III.8.a. Engineers shall conform with state registration laws in the practice of engineering.
How this applies in the case (showing 3 of 58)
Obligation
Engineer B Peer Review Incumbent Notification Reasonable Timing Compliance BER Case
III.8.a. is explicitly cited in this obligation as the provision requiring Engineer B to notify Engineer A within a reasonable period following the review engagement.
Action
Engineer B Accepts Project Without Clarification
Accepting a project that may involve reviewing or supplanting another licensed engineer's work without proper process could implicate state registration law compliance.
State
Notification Duty vs. Faithful Agent Duty Conflict
This provision is one of the two obligations in direct conflict, requiring Engineer B to notify Engineer A as the incumbent engineer.
Obligation (5)
  • Engineer B Peer Review Incumbent Notification Reasonable Timing Compliance BER Case
    III.8.a. is explicitly cited in this obligation as the provision requiring Engineer B to notify Engineer A within a reasonable period following the review engagement.
  • Engineer B Peer Review Notification of Engineer A Despite Client Instruction
    III.8.a. requires conformance with state registration laws including peer review notification norms, directly grounding the obligation to notify Engineer A despite client instruction.
  • Engineer B Peer Review Notification and Consent Fulfillment
    III.8.a. requires conformance with state registration laws governing engineering practice, directly applicable to the procedural notification obligation when conducting a peer review.
  • Engineer B Reviewed Engineer Technical Comment Opportunity Preservation BER Case
    III.8.a. requires conformance with state registration laws, which include professional practice standards that support giving the reviewed engineer an opportunity to comment.
  • Engineer B Successor Contract Acceptance After Engineer A Contract Expiration
    III.8.a. requires conformance with state registration laws governing professional conduct, relevant to the proper sequencing of contract acceptance relative to Engineer A's engagement.
Action (2)
  • Engineer B Accepts Project Without Clarification
    Accepting a project that may involve reviewing or supplanting another licensed engineer's work without proper process could implicate state registration law compliance.
  • Engineer B Reviews Design Information
    Reviewing and potentially taking over another engineer's sealed or registered work must conform with state registration laws governing engineering practice.
State (6)
  • Notification Duty vs. Faithful Agent Duty Conflict
    This provision is one of the two obligations in direct conflict, requiring Engineer B to notify Engineer A as the incumbent engineer.
  • Engineer B Client-Directed Confidentiality Instruction Voluntarily Overridden
    Engineer B's decision to notify Engineer A aligns with the state registration law notification requirement this provision references.
  • One-Week Notification Delay Reasonableness Assessment
    This provision's requirement to conform with state registration laws, including timely notification of the incumbent engineer, is the direct standard against which the one-week delay is assessed.
  • Incumbent Engineer Under Active Review Without Knowledge
    State registration laws typically require notifying the incumbent engineer before reviewing their work, making this provision directly applicable to Engineer A's unknowing review status.
  • Client Transition Overlap. Franchiser Dual Engineer Engagement
    The simultaneous engagement of two engineers creates the exact scenario where state registration law notification requirements under this provision are triggered.
  • Engineer A Employment Terminated. Franchiser Non-Renewal
    The transition from Engineer A to Engineer B is the circumstance that activates the state registration law obligation to notify the incumbent engineer.
Constraint (13)
  • Covert Peer Review Prohibition. Franchiser Instruction to Engineer B
    III.8.a requires conformance with state registration laws, which typically mandate notification of incumbent engineers before conducting peer reviews, making the franchiser's covert instruction impermissible.
  • Covert Peer Review Prohibition. Engineer B Review of Engineer A Without Prior Notification
    III.8.a directly prohibits Engineer B from proceeding with the peer review without notifying Engineer A, as state registration laws require such notification.
  • Incumbent Engineer Active Contract Covert Review Prohibition. Engineer B Review of Engineer A Under Active Contract
    III.8.a requires conformance with state laws that prohibit covert review of an incumbent engineer's active contract work.
  • Faithful Agent Duty Peer Review Collegial Obligation Boundary. Engineer B Notification of Engineer A Despite Franchiser Instruction
    III.8.a is the specific provision that bounds Engineer B's faithful agent duty by imposing an independent obligation to notify Engineer A.
  • Client Confidentiality Instruction Peer Review Notification Non-Override. Franchiser Instruction to Engineer B
    III.8.a establishes the professional obligation that the franchiser's confidentiality instruction cannot override.
  • Peer Review Notification Timing Reasonableness. One-Week Delay Between Engineer B Engagement and Notification to Engineer A
    III.8.a requires conformance with state registration laws mandating timely notification, against which the one-week delay is assessed.
  • Engineer B Peer Review Notification One-Week Delay Reasonableness Assessment
    III.8.a is the provision under which the reasonableness of Engineer B's one-week notification delay is evaluated.
  • Incumbent Engineer Knowledge Requirement. Engineer A Engineer B Franchiser Review
    III.8.a directly requires that Engineer A have knowledge of the peer review, as state registration laws mandate notification of incumbent engineers.
  • Peer Review Preliminary Results Incumbent Disclosure. Engineer B Disclosure to Engineer A
    III.8.a supports the obligation to disclose preliminary peer review results to Engineer A as part of conforming with state registration law requirements for engineer notification.
  • Client Motive Inquiry Pre-Engagement Confidentiality Instruction. Engineer B Failure to Inquire Before Accepting Franchiser Engagement
    III.8.a requires conformance with state laws governing peer review engagements, which obligated Engineer B to inquire into the franchiser's motives before accepting the confidentiality-bound engagement.
  • Engineer B Pre-Engagement Client Motive Inquiry Constraint Instance
    III.8.a underlies the obligation requiring Engineer B to inquire into the franchiser's motives before accepting the engagement subject to the non-disclosure instruction.
  • Peer Review Successor Contract Incumbent Contract Expiry Prerequisite. Engineer B Successor Engagement After Engineer A Contract Expiry
    III.8.a requires conformance with state registration laws that constrain Engineer B from accepting a successor contract while Engineer A's contract remains active.
  • Engineer Relations Code Provision Client Need Balancing. BER Case 93-3
    III.8.a is one of the code provisions governing engineer relations that must be balanced against client needs in BER Case 93-3.
Principle (8)
  • Incumbent Engineer Knowledge Requirement Invoked By Engineer B Against Client Instruction
    This provision is the direct source of the obligation requiring Engineer B to notify Engineer A of the review engagement despite the client's instruction.
  • Incumbent Engineer Knowledge Requirement Invoked as Competing Obligation
    This provision is explicitly identified as imposing the competing obligation on Engineer B to notify Engineer A that Engineer B was reviewing Engineer A's work.
  • Professional Dignity Invoked For Engineer A As Incumbent Subject To Covert Review
    This provision's peer notification requirement protects the incumbent engineer's professional dignity by ensuring they know their work is under review.
  • Professional Dignity of Incumbent Engineer Underlying Peer Notification Purpose
    This provision embodies the peer notification obligation whose underlying purpose is protecting the incumbent engineer's professional dignity.
  • Competing Code Provision Balancing Applied to Peer Notification vs. Faithful Agent Duty
    This provision is explicitly identified as one of the two competing code provisions the Board balanced against the faithful agent duty.
  • Reasonable Timing Compliance in Peer Review Notification Applied to Engineer B One-Week Delay
    This provision is the standard against which Engineer B's one-week delay in notifying Engineer A was evaluated and found compliant.
  • Successor Engineer Post-Review Contract Acceptance Permissibility Invoked By Engineer B
    This provision governs the conduct of engineers reviewing others' work, establishing the framework within which Engineer B's subsequent contract acceptance was evaluated.
  • Client Direction Does Not Authorize Ethical Violation Invoked Against Franchiser Confidentiality Instruction
    This provision establishes the peer notification duty that the franchiser's confidentiality instruction would have violated if Engineer B had complied with it.
Role (3)
  • Engineer A Original Design Engineer Subject to Peer Review
    Engineer A's work was subject to peer review, and conformance with state registration laws governing engineering practice is directly relevant to the legitimacy of that work.
  • Engineer B Confidentiality-Directed Successor Design Engineer
    Engineer B conducting a peer review of engineering designs must conform with state registration laws applicable to the practice of engineering in that jurisdiction.
  • Engineer B Faithful Agent Peer-Notification-Conflicted Reviewing Engineer
    Engineer B's professional review activities must comply with state registration requirements governing the practice of engineering.
Event (3)
  • Engineer A Informed of Successor Engagement
    Notifying Engineer A of the successor engagement relates to the state registration law requirement that engineers notify a prior engineer before assuming their work.
  • Parallel Engagement Overlap Created
    Overlapping engagements without proper notification may violate state registration laws governing the assumption of another engineer's work.
  • Contract Non-Renewal Notice Received
    The point at which the contract non-renewal was issued is relevant to determining whether proper legal and registration procedures were followed in transitioning engineering responsibilities.
Resource (8)
  • NSPE Code of Ethics - Section III.8.a
    This resource directly references Section III.8.a as the central provision governing the obligation to notify the prior engineer before reviewing their work.
  • Peer-Review-Without-Notification-Standard-Instance
    This provision establishes the norm that Engineer B must not review Engineer A's work without notification, which this resource applies to the franchiser's instruction.
  • Engineer-Notification-Right-in-Review-Contexts-Instance
    This provision grounds Engineer A's professional right to be notified that Engineer B has been retained to review Engineer A's pending design work.
  • Peer-Review-Conduct-Standard-Instance
    This provision governs the procedural and ethical obligations applicable to Engineer B's review of Engineer A's pending design work.
  • Peer Review Notification Obligation Standard (Section III.8.a)
    This resource is directly named after and applies Section III.8.a to assess whether Engineer B fulfilled the notification requirement.
  • BER Case 79-7
    This provision was interpreted in BER Case 79-7, which established the purpose of the engineer-review-notification requirement under this section.
  • BER-Case-Precedent-Peer-Review-Notification
    This resource provides precedential reasoning specifically tied to the notification requirement established under this provision.
  • NSPE-Code-of-Ethics
    This provision is part of the primary normative authority governing Engineer B's obligation to notify Engineer A when retained to review Engineer A's work.
Capability (10)
  • Engineer B Active Contract Incumbent Review Prohibition Recognition BER Case
    III.8.a requires conformance with state registration laws including peer review notification rules, which Engineer B needed to recognize applied when Engineer A's contract was still active.
  • Engineer B Active Contract Incumbent Review Prohibition Recognition
    III.8.a mandates conformance with registration laws that include peer review notification obligations Engineer B recognized were triggered by Engineer A's active contract status.
  • Engineer B Peer Review Notification Protocol Fulfillment
    III.8.a requires conformance with state registration laws that mandate notifying the engineer whose work is under peer review, directly grounding Engineer B's notification obligation.
  • Engineer B Preliminary Results Disclosure to Engineer A
    III.8.a registration law conformance requirements underpin the obligation to disclose not just the existence but also the preliminary results of the peer review to Engineer A.
  • Engineer B Peer Review vs Faithful Agent Dual Code Provision Conflict Resolution BER Case
    III.8.a is one of the two provisions in direct tension with II.4 that Engineer B needed to resolve, as it mandates peer review notification under state registration laws.
  • Engineer B Peer Review Notification Protocol BER Case
    III.8.a is the provision directly requiring Engineer B to notify Engineer A of the peer review, as conformance with state registration laws includes peer review procedural obligations.
  • Engineer B Peer Review Technical Comment Opportunity Preservation BER Case
    III.8.a registration law conformance includes ensuring the reviewed engineer has an opportunity to submit technical comments, making it directly applicable to this capability.
  • Engineer B Peer Review Incumbent Notification Reasonable Timing Calibration BER Case
    III.8.a requires conformance with state registration laws on peer review notification, making the timeliness of Engineer B's notification directly subject to this provision.
  • BER Engineer Relations Code Evolution Historical Awareness BER Case
    III.8.a is the provision whose application the BER grounded in the historical evolution of engineer relations provisions, requiring awareness of that evolution to apply it correctly.
  • Engineer B Altruistic Disclosure Client Interest Neglect Self-Assessment BER Case
    III.8.a mandates the notification that Engineer B made, making it relevant to assessing whether Engineer B's disclosure nonetheless harmed the franchiser's interests beyond what the code required.
Cross-Case Connections
View Extraction
Explicit 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.

Relevant Excerpts
discussion: "In BER Case 79-7, an engineer was asked to inspect mechanical and electrical engineering work performed seven years earlier. The Board concluded that the engineer notified the former engineer that the engineer was being retained to perform review and inspection services..."
discussion: "We believe the reasoning cited by the Board in BER Case 79-7 are as cogent today as they were when the Board issued its opinion."
discussion: "In light of the facts and consistent with BER Case 79-7, we are persuaded that Engineer B acted unethically in notifying Engineer A of Engineer B's relationship with the client."
discussion: "Our conclusion is based upon the rationale cited above in BER Case 79-7 but is also based upon an analysis of the countervailing argument that Engineer B had an obligation as 'faithful agent and trustee'..."
Implicit Similar Cases 10 Similarity Network

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

Component Similarity 62% Facts Similarity 58% Discussion Similarity 73% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 29%
Shared provisions: II.4.a, III.7.a Same outcome True View Synthesis
Component Similarity 62% Facts Similarity 67% Discussion Similarity 71% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: III.7.a Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 51% Discussion Similarity 72% Provision Overlap 29% Outcome Alignment 100% Tag Overlap 11%
Shared provisions: III.7.a, III.8.a Same outcome True View Synthesis
Component Similarity 51% Facts Similarity 43% Discussion Similarity 65% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 80%
Shared provisions: II.4.a Same outcome True View Synthesis
Component Similarity 56% Facts Similarity 55% Discussion Similarity 74% Provision Overlap 22% Outcome Alignment 100% Tag Overlap 29%
Shared provisions: II.4, II.4.a Same outcome True View Synthesis
Component Similarity 57% Facts Similarity 60% Discussion Similarity 74% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: II.4.a Same outcome True View Synthesis
Component Similarity 56% Facts Similarity 56% Discussion Similarity 78% Provision Overlap 11% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: II.4.a Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 33% Discussion Similarity 68% Provision Overlap 29% Outcome Alignment 50% Tag Overlap 60%
Shared provisions: II.4, II.4.a View Synthesis
Component Similarity 54% Facts Similarity 50% Discussion Similarity 63% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: II.4.a Same outcome True View Synthesis
Component Similarity 61% Facts Similarity 63% Discussion Similarity 70% Outcome Alignment 100% Tag Overlap 29%
Same outcome True View Synthesis
Questions & Conclusions (2 board)
View Extraction
Board Board question 1

Was Engineer B's act of notifying Engineer A of his relationship with franchiser consistent with the Code?

Board conclusion Engineer B's act of notifying Engineer A of his relationship with franchiser was not consistent with the Code.
II.4. II.1.c. III.4.
Implicit (4)

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?

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

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?

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

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

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

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

Board conclusion The Board was split on the second question and could not reach agreement.
II.4. III.8.a.
Principle tension (4)

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?

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

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

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

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

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

Theoretical (4)

From a deontological perspective, did Engineer B fulfill a categorical duty 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?

AnalyticalIn response to Q301 and Q302: From a deontological perspective, Engineer B faced a genuine conflict between two categorical duties - the duty to notify the incumbent engineer prior to conducting a peer review, and the duty to act as a faithful agent to the client. The resolution of this conflict under a Kantian framework depends on which duty is more fundamental to the professional role. The peer review notification obligation is best understood as a duty owed to the professional community and to the incumbent engineer as a rights-bearing professional - it is not merely a courtesy but a procedural entitlement that exists independently of client consent. The faithful agent duty, by contrast, is a relational duty owed to a specific client and is explicitly conditioned in the Code on consistency with ethical limits. A deontological analysis therefore supports the conclusion that the peer notification duty takes precedence over the client confidentiality instruction, because the faithful agent duty is not absolute while the notification obligation reflects a categorical commitment to professional fairness. However, Engineer B's violation of the faithful agent duty in disclosing preliminary results - beyond what the notification obligation required - cannot be justified on deontological grounds, because that excess disclosure served no categorical duty and simply exceeded the scope of the competing obligation.

From a deontological perspective, did Engineer B violate a strict duty of faithful agency to the franchiser by overriding the client's explicit confidentiality instruction, even if Engineer B's motive was to honor a competing professional obligation to Engineer A?

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?

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

AnalyticalIn 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.
Counterfactual (4)

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?

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

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?

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

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

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?

Options considered:
O1 Inform Engineer A of the peer review engagement prior to commencing the review, honoring the Section III.8.a notification obligation and preserving Engineer A's opportunity to provide technical context, even though this directly contravenes the franchiser's confidentiality instruction.
O2 Conduct the peer review without informing Engineer A, treating the franchiser's explicit confidentiality instruction as binding under the faithful agent duty and deferring any disclosure until the client's engagement terms permit it or the contract situation changes. Board's choice
O3 Refuse to accept the review engagement unless the franchiser grants permission to notify Engineer A prior to the review, thereby conditioning acceptance on terms that make simultaneous compliance with both the faithful agent duty and the peer notification obligation structurally possible.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Engineer B Peer Review Notification of Engineer A Despite Client Instruction Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation

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?

Options considered:
O1 Refrain from accepting any successor design engineering engagement from the franchiser until Engineer A's contract has fully expired, ensuring that the peer review relationship is not used as a vehicle for competitive positioning while the incumbent's contractual relationship remains active. Board's choice
O2 Accept the franchiser's successor design engineering contract during the active review period, treating the franchiser's right to manage its own contractor relationships and the at-will employment symmetry principle as sufficient authorization for the concurrent engagement.
O3 Accept the successor contract after Engineer A's contract expires, but only after having fulfilled all collegial notification duties during the review phase, treating timely and complete notification of Engineer A as a prerequisite condition that must be satisfied before the successor engagement can be ethically accepted.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Successor Engineer Post-Review Expired-Contract Acceptance Permissibility Obligation Peer Review Successor Contract Incumbent Contract Expiry Prerequisite Constraint

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?

Options considered:
O1 Proceed with the peer review engagement as structured under the franchiser's confidentiality instruction, treating the client's direction as a binding engagement term and managing any resulting conflict between faithful agency and peer notification duties after the fact.
O2 Before accepting the engagement, ask the franchiser to explain the basis for the confidentiality instruction and explore whether modified engagement terms, permitting at least minimal notification to Engineer A, could satisfy both the client's transition interests and the Code's peer review notification requirement. Board's choice
O3 Refuse to accept the peer review engagement unless the franchiser agrees to permit prior notification to Engineer A, treating the confidentiality instruction as structurally incompatible with the Code's peer notification obligation and placing responsibility for any resulting delay on the franchiser's decision to impose an ethically incompatible instruction.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Engineer B Covert Review Client Instruction Resistance Covert Peer Review Client Instruction Resistance Obligation

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?

Options considered:
O1 Limit notification to Engineer A to the fact of the new engagement relationship and the existence of the peer review, without transmitting any preliminary analytical conclusions or design-specific findings derived from the confidential client engagement. Board's choice
O2 Notify Engineer A of both the new engagement relationship and the preliminary results of the peer review, on the ground that Engineer A cannot meaningfully exercise the right to respond to technical concerns without knowing the substance of those concerns.
O3 Before notifying Engineer A of anything, return to the franchiser and seek explicit authorization for the minimum disclosure necessary to satisfy the peer review notification obligation, thereby preserving the faithful agent relationship while attempting to create a compliant notification pathway.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Peer Review Preliminary Results Disclosure to Reviewed Engineer Obligation Faithful Agent Client Interest Non-Neglect Through Unauthorized Disclosure Obligation

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?

Options considered:
O1 Before accepting the franchiser's engagement, ask the franchiser to explain the business reason for the confidentiality instruction and negotiate engagement terms that permit at minimum the minimum disclosure required by Section III.8.a, conditioning acceptance on a satisfactory resolution of the conflict. Board's choice
O2 Accept the engagement as structured, treating the confidentiality instruction as a standard client direction within the faithful agent framework, and address any conflict with the peer notification obligation at the point it becomes operationally unavoidable during or after the review.
O3 Decline to accept the engagement at all unless the franchiser withdraws the confidentiality instruction, on the ground that an engagement structured to make simultaneous compliance with both the faithful agent duty and the peer notification obligation impossible should not be accepted by a professionally responsible engineer.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Pre-Engagement Client Instruction Clarification Obligation Faithful Agent Peer-Review Collegial Duty Boundary Obligation

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?

Options considered:
O1 Inform Engineer A of the new engagement relationship and the impending peer review prior to beginning any design review work, treating the notification obligation as a procedural prerequisite that the franchiser's confidentiality instruction cannot override, and limiting disclosure to the existence of the engagement rather than any preliminary findings.
O2 Conduct the peer review as instructed by the franchiser, then notify Engineer A of both the engagement relationship and the preliminary review results after the review is complete, reasoning that some notification, even post-review, partially honors the peer review obligation while minimizing disruption to the franchiser's transition process. Board's choice
O3 Refuse to accept the peer review engagement unless the franchiser grants permission to notify Engineer A prior to conducting the review, conditioning acceptance on the franchiser's agreement to a procedurally compliant notification arrangement and thereby placing responsibility for any resulting delay on the party who imposed the ethically incompatible instruction.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Engineer B Peer Review Notification and Consent Fulfillment Engineer B Client Confidentiality Instruction Faithful Agent Compliance

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?

Options considered:
O1 Limit notification to Engineer A to the fact of the new engagement relationship with the franchiser and the fact that a peer review was conducted, without sharing any preliminary findings or analytical conclusions, thereby honoring the minimum required by the peer notification obligation while minimizing the compounding breach of the faithful agent duty.
O2 Notify Engineer A of both the new engagement relationship and the preliminary review findings, reasoning that a notification limited to the existence of the engagement is insufficient to give Engineer A a meaningful opportunity to respond to technical concerns identified during the review, and that the peer notification obligation's substantive purpose requires disclosure of what was found. Board's choice
O3 Notify Engineer A of the engagement relationship immediately, then seek the franchiser's consent before sharing any preliminary review findings with Engineer A, preserving Engineer A's right to know of the review while honoring the faithful agent duty with respect to work-product confidentiality until the client either grants permission or the review process reaches a stage where disclosure is formally required.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Engineer B Preliminary Review Results Disclosure to Engineer A Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure

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?

Options considered:
O1 Limit notification to Engineer A to the minimum required by Section III.8.a, informing Engineer A that Engineer B has been engaged by the franchiser and that a review of Engineer A's design work has occurred or is occurring, without sharing any preliminary findings, conclusions, or client work product derived from the review.
O2 Notify Engineer A of both the new engagement relationship and the preliminary results of the design review, on the grounds that Engineer A's opportunity to respond to technical concerns is substantively meaningful only if Engineer A knows what those concerns are, and that the peer notification obligation's purpose of preserving technical comment opportunity implicitly requires disclosure of findings sufficient to make that opportunity real. Board's choice
O3 Notify Engineer A of the engagement relationship as required by Section III.8.a, but seek the franchiser's authorization before sharing any preliminary review findings, treating the preliminary results as client work product that requires client consent for disclosure and preserving the faithful agent duty with respect to substantive analytical conclusions while honoring the minimum notification obligation.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Peer Review Preliminary Results Disclosure to Reviewed Engineer Obligation Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation Compliance Obligation

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?

Options considered:
O1 Proceed with the full design review under the franchiser's confidentiality instruction, then notify Engineer A of the engagement relationship and preliminary findings after the review is complete, treating post-review notification as a reasonable accommodation of both the client's instruction and the peer notification obligation.
O2 Treat pre-review notification of Engineer A as a mandatory procedural prerequisite under Section III.8.a, notifying Engineer A of the engagement before conducting any substantive review work, even if this requires defying the franchiser's confidentiality instruction at the outset rather than after the review is complete. Board's choice
O3 Begin preliminary scoping of the engagement but suspend substantive design review work until the franchiser either authorizes notification to Engineer A or Engineer A's contract expires, thereby preserving the faithful agent duty while avoiding the most prejudicial form of covert review, conducting substantive analysis of active work without the incumbent's knowledge.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Engineer B Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation BER Case Peer Review Incumbent Notification Reasonable Timing Compliance Obligation

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?

Options considered:
O1 Before accepting the franchiser's engagement, ask the franchiser to explain the business reasons for the confidentiality instruction and negotiate modified engagement terms, such as permission to provide a limited notification to Engineer A of the engagement's existence, that would allow simultaneous compliance with both the faithful agent duty and the peer review notification obligation. Board's choice
O2 Accept the franchiser's engagement as structured, treating the confidentiality instruction as a standard business directive within the scope of the faithful agent duty, and address any conflict with the peer review notification obligation as it arises during the engagement, relying on professional judgment at that time to determine the appropriate course of action.
O3 Decline the engagement outright on the ground that the confidentiality instruction, on its face, makes simultaneous compliance with the faithful agent duty and the peer review notification obligation impossible, thereby refusing to accept an engagement structured to require an ethical violation as a condition of performance.
Argument structure:
Warrants

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.

Rebuttals

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.

Grounds

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.

Pre-Engagement Client Instruction Clarification Obligation Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser
13 sequenced 6 actions 7 events
Case timeline
Engineer A and the franchiser had developed a long-standing professional relationship over multiple years, creating mutual expectations of continuity and trust. This relationship forms the baseline context from which all subsequent disruptions emerge.
The franchiser made a deliberate business decision to end its multi-year engineering relationship with Engineer A, providing formal notice of non-renewal before the contract expired.
Fulfills (2)
  • Contractual obligation to provide notice of non-renewal
  • Business prerogative to select engineering partners
Engineer A receives formal notice from the franchiser that their contract will not be renewed, signaling the end of the multi-year professional relationship. This notice creates a defined countdown to contract expiration and triggers Engineer A's awareness that succession planning is underway.
Before Engineer A's contract expired, the franchiser proactively retained Engineer B to review pending design concerns across multiple franchise facilities, initiating a transition overlap.
At stake (1)
  • Spirit of fair dealing toward Engineer A, whose work was being reviewed without full transparency during an active contractual relationship
Fulfills (2)
  • Client's right to seek engineering services from a provider of its choosing
  • Business obligation to address pending design concerns without delay
At the time of retaining Engineer B, the franchiser explicitly instructed Engineer B not to disclose his relationship with the franchiser to Engineer A, imposing a confidentiality condition on the engagement.
Fulfills (2)
  • Client's prerogative to set terms of engagement with retained engineers
  • Business interest in managing a sensitive personnel and vendor transition
Violates (2)
  • Spirit of NSPE Code Section III.8.a, which supports Engineer A's right to know his work is under review
  • Fair dealing toward Engineer A as a professional whose work and reputation were being evaluated
The franchiser's explicit instruction to Engineer B not to disclose his relationship to Engineer A becomes an active constraint on Engineer B's behavior, creating a direct conflict between client instructions and professional ethical obligations. This is not a decision by Engineer B but an external imposition that shapes the ethical landscape he must navigate.
Engineer B accepted the franchiser's engagement and its confidentiality condition without first exploring or clarifying the reason why the client did not want Engineer B to disclose his relationship with the franchiser to Engineer A.
Violates (2)
  • Professional obligation to clarify the ethical implications of client instructions before accepting an engagement that places professional duties in conflict (noted explicitly as ethically problematic by the Board)
  • Duty of due diligence in understanding the terms and ethical dimensions of a new client relationship
As a direct result of the franchiser retaining Engineer B before Engineer A's contract expired, a period of simultaneous engagement exists where both engineers hold roles related to the same client. This overlap creates an inherently conflicted situation where Engineer A remains the active engineer of record while Engineer B is conducting preliminary reviews.
As a direct consequence of the franchiser's confidentiality instruction and Engineer B's initial compliance, Engineer A remains unaware that his work is being reviewed by a successor engineer while he is still under contract. This state of uninformed vulnerability persists for approximately one week.
One week after being retained and receiving the confidentiality instruction, Engineer B proceeded to review the pending design information related to several franchise facilities that had been designed by Engineer A.
At stake (1)
  • NSPE Code Section III.8.a: proceeding with review of another engineer's work without prior notification to that engineer (though the Board ultimately found the one-week delay before notification was not unreasonable)
Fulfills (2)
  • Contractual obligation to the franchiser to perform the requested design review
  • Professional competence obligation to conduct a thorough engineering review
Engineer B completes his review of the franchiser's pending design information while still operating under the confidentiality instruction and before notifying Engineer A. The review results are obtained in an ethically compromised context, raising questions about the validity and fairness of the assessment.
Following his review of the design information, and contrary to the franchiser's explicit instruction, Engineer B notified Engineer A of his relationship with the franchiser and the preliminary results of his design review.
Fulfills (1)
  • NSPE Code Section III.8.a: notification to Engineer A that his work was being reviewed by another engineer for the same client
Violates (3)
  • NSPE Code Section II.4: duty as faithful agent and trustee to act in the client's best interests
  • Direct client instruction not to disclose Engineer B's relationship with the franchiser to Engineer A
  • General duty of loyalty and fair dealing to the client as defined by the Board's interpretation of 'trustee'
One week after being retained, Engineer B notifies Engineer A of his relationship with the franchiser and shares the preliminary review results. This notification, while belated, partially remedies the ethical violation of non-disclosure and shifts the ethical landscape significantly.
Narrative (3 main characters)
View Extraction
Opening Context

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

You are Engineer B, a licensed 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.

Main characters (3)

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

Engineer A Roles in this case: Original Design Engineer Subject to Peer ReviewOutgoing Incumbent Design Engineer

Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation

Attaches to role: Original Design Engineer Subject to Peer Review

Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Covert Peer Review Client Instruction Resistance Obligation

Attaches to role: Original Design Engineer Subject to Peer Review

Tension between Engineer B Preliminary Review Results Disclosure to Engineer A and Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure

Attaches to role: Original Design Engineer Subject to Peer Review

Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Engineer B Client Confidentiality Instruction Faithful Agent Compliance

Attaches to role: Original Design Engineer Subject to Peer Review

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.

Attaches to role: Original Design Engineer Subject to Peer Review

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.

Attaches to role: Outgoing Incumbent Design Engineer
Engineer B Roles in this case: Confidentiality-Directed Successor Design EngineerFaithful Agent Peer-Notification-Conflicted Reviewing Engineer

Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation

Attaches to role: Confidentiality-Directed Successor Design Engineer

Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Covert Peer Review Client Instruction Resistance Obligation

Attaches to role: Confidentiality-Directed Successor Design Engineer

Tension between Engineer B Preliminary Review Results Disclosure to Engineer A and Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure

Attaches to role: Confidentiality-Directed Successor Design Engineer

Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Engineer B Client Confidentiality Instruction Faithful Agent Compliance

Attaches to role: Confidentiality-Directed Successor Design Engineer

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.

Attaches to role: Confidentiality-Directed Successor Design Engineer

Tension between Engineer B Covert Review Client Instruction Resistance and Covert Peer Review Client Instruction Resistance Obligation

Attaches to role: Confidentiality-Directed Successor Design Engineer

Tension between Engineer B Peer Review Notification and Consent Fulfillment and Engineer B Client Confidentiality Instruction Faithful Agent Compliance

Attaches to role: Confidentiality-Directed Successor Design Engineer

Tension between Engineer B Faithful Agent Peer Review Collegial Boundary Exercise and Franchiser Peer Review Procedural Fairness Non-Compliance Covert Instruction

Attaches to role: Confidentiality-Directed Successor Design Engineer

Tension between Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case and Peer Review Notification Obligation Standard Section III.8.a

Attaches to role: Confidentiality-Directed Successor Design Engineer

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.

Attaches to role: Faithful Agent Peer-Notification-Conflicted Reviewing Engineer

Tension between Engineer B Pre-Engagement Client Instruction Rationale Clarification BER Case and Covert Peer Review Client Instruction Resistance Obligation

Attaches to role: Confidentiality-Directed Successor Design Engineer

Tension between Pre-Engagement Client Instruction Clarification Obligation and Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser

Attaches to role: Confidentiality-Directed Successor Design Engineer

Tension between Engineer B Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation BER Case and Peer Review Incumbent Notification Reasonable Timing Compliance Obligation

Attaches to role: Confidentiality-Directed Successor Design Engineer
Franchiser National Roles in this case: Franchise Engineering Services Client

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.

Other people involved in the case but not central to the opening narrative.

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.


These tensions did not map cleanly to a single character.

Tension between Peer Review Preliminary Results Disclosure to Reviewed Engineer Obligation and Faithful Agent Client Interest Non-Neglect Through Unauthorized Disclosure 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 Successor Engineer Post-Review Expired-Contract Acceptance Permissibility Obligation and Peer Review Successor Contract Incumbent Contract Expiry Prerequisite Constraint

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 Clarification Obligation and Faithful Agent Peer-Review Collegial Duty Boundary Obligation

Tension between Pre-Engagement Client Instruction Rationale Clarification Obligation and Covert Peer Review Client Instruction Resistance Obligation

Opening States (10)
Client Transition Overlap - Franchiser Dual Engineer Engagement Engineer A Employment Terminated - Franchiser Non-Renewal Peer Review Confidentiality Agreement Absent - Engineer A Design Review Client-Directed Confidentiality Instruction Voluntarily Overridden by Engineer State Client Confidentiality Motive Unexplored Pre-Engagement State Non-Self-Interested Code Violation Mitigating Context State Notification Timing Reasonableness Assessment State Successor Engineer Retained Before Incumbent Contract Expiry State Engineer A Incumbent Active Contract State Franchiser Covert Review Instruction to Engineer B
Summary
  • 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.