Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.
Provisions (4)
View Extraction-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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 ExtractionExplicit Board-Cited Precedents 1 Lineage Graph
Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.
Principle Established:
The purpose of Section III.8.a. (formerly Section 12(a)) is to provide the engineer whose work is being reviewed an opportunity to submit comments or explanations for technical decisions, enabling the reviewing engineer to have a fuller understanding of the original design.
Citation Context:
The Board cited this case to establish the purpose of Section III.8.a., which requires an engineer to notify the original engineer when reviewing their work, giving the original engineer an opportunity to provide comments or explanations for technical decisions. It is cited multiple times to both support and frame the analysis of Engineer B's obligations.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions (2 board)
View ExtractionWas Engineer B's act of notifying Engineer A of his relationship with franchiser consistent with the Code?
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?
Did the franchiser itself act unethically by instructing Engineer B to conceal the new engagement from Engineer A, and does the Code impose any obligation on a client not to direct engineers to violate peer review procedural fairness norms?
Should Engineer B have declined to share the preliminary results of his review with Engineer A at the time of notification, given that disclosing those results compounded the faithful agent violation by further exposing confidential client work product without authorization?
Does Engineer B's subsequent acceptance of the full design engineering contract with the franchiser - obtained in part through knowledge gained during the covert peer review - raise an independent ethical concern about exploitation of the peer review process for competitive advantage, regardless of whether the notification timing was ultimately reasonable?
Was it ethical for Engineer B to proceed with the review at that time?
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?
Does the principle of professional dignity for the incumbent engineer - which underlies the peer notification requirement - conflict with the principle of client loyalty invoked to constrain Engineer B's disclosure, and can professional dignity ever be subordinated to client confidentiality interests without undermining the foundational purpose of peer review?
Does the principle that benevolent motive does not cure an ethical violation - applied to Engineer B's well-intentioned notification - conflict with the principle of tripartite interest balancing, which might weigh Engineer A's right to know against the franchiser's confidentiality interest and find notification net-beneficial, thereby suggesting that motive and outcome together should inform the ethical assessment?
Does the principle of at-will employment symmetry - invoked to justify the franchiser's right to non-renew Engineer A's contract - conflict with the principle of reasonable timing compliance in peer review notification, in that the franchiser's use of the transition period to conduct a covert review exploits the at-will relationship to circumvent the procedural protections the notification timing requirement is designed to provide?
Cross-cutting analytical questions (8)
These questions consider the case as a whole rather than a specific board question above.
Show 8 cross-cutting questionsTheoretical (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?
From a deontological perspective, did Engineer B violate a strict duty of faithful agency to the franchiser by overriding the client's explicit confidentiality instruction, even if Engineer B's motive was to honor a competing professional obligation to Engineer A?
From a consequentialist perspective, did Engineer B's decision to notify Engineer A after completing the review - rather than before - produce a net outcome that better served the professional community, the franchiser, and Engineer A compared to either full silence or pre-review notification?
From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and collegial respect expected of a competent engineer by accepting a covert review engagement without first seeking clarification of the franchiser's reasons for the confidentiality instruction, and does the subsequent voluntary notification redeem or merely partially offset that initial failure of character?
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?
If Engineer B had notified Engineer A before conducting the design review rather than after, would that pre-review notification have satisfied the Code's peer review notification obligation and simultaneously preserved the faithful agent duty to the franchiser, or would the franchiser's confidentiality instruction have made any timing of notification equally impermissible under the faithful agent standard?
If Engineer B had disclosed the preliminary review results to Engineer A but withheld the fact of the new engagement relationship - as opposed to disclosing both - would that partial disclosure have constituted a lesser violation of the faithful agent duty while still partially honoring the spirit of the peer review notification obligation?
If Engineer A's contract with the franchiser had already expired before Engineer B conducted the review - rather than still being active - would the ethical weight of the peer review notification obligation have been diminished, and would the franchiser's confidentiality instruction have been more defensible under the faithful agent standard?
Decisions & Arguments (10)
View ExtractionShould Engineer B notify Engineer A of the peer review engagement despite the franchiser's explicit instruction to maintain confidentiality, or comply with the client's confidentiality directive and conduct the review without informing Engineer A?
The peer review notification obligation under Section III.8.a independently requires that an engineer whose work is under review be informed of that review, grounded in professional dignity and the incumbent's right to provide technical context. This obligation is not conditioned on client consent. Competing against this is the faithful agent and trustee duty under Section II.4, which requires Engineer B to carry out the client's transaction in the manner most beneficial to the client and to refrain from unauthorized disclosures, even altruistically motivated ones, when the client has explicitly instructed otherwise. The Board found that Engineer B's notification was not consistent with the Code under the faithful agent standard, while also recognizing that the client's direction does not authorize ethical violations.
Uncertainty arises because the faithful agent duty is expressly bounded in the Code by the phrase 'within ethical limits,' meaning it cannot categorically override a separately mandated disclosure. If the peer notification obligation is treated as a non-waivable professional floor, the faithful agent duty cannot be invoked to suppress it. The Board split on whether proceeding with the review at all was ethical, reflecting that the two provisions were not genuinely reconciled. Additionally, the one-week delay was found not unreasonable under the timing standard, which partially mitigates but does not eliminate the conflict.
The franchiser explicitly instructed Engineer B not to disclose the new review engagement to Engineer A before Engineer B conducted the peer review of Engineer A's active design work. Engineer A's contract remained active during the review period. Engineer B proceeded with the review and then notified Engineer A of both the engagement relationship and the preliminary review results one week later.
Should Engineer B accept the franchiser's successor design engineering contract while Engineer A's contract remains active, or refrain from accepting the successor engagement until Engineer A's contract has fully expired?
The peer review successor contract constraint establishes that a reviewing engineer must refrain from accepting a successor design contract from the same client until the incumbent's contract has fully expired, on the grounds that doing so constitutes improper competitive use of the peer review relationship. Engineer B's acceptance after contract expiration is technically within this boundary. However, the peer review program's foundational purpose is collegial improvement, not competitive intelligence gathering, and Engineer B gained informational advantage through a covert review that Engineer A could not participate in or respond to. The at-will employment symmetry principle legitimately permits the franchiser to non-renew Engineer A, but does not extend to authorizing use of the transitional overlap period as a covert competitive evaluation window.
Uncertainty arises because Engineer B's formal acceptance of the successor contract occurred after Engineer A's contract expired, which satisfies the literal boundary of the successor contract constraint. Whether the knowledge advantage gained during the covert review taints the legitimacy of that transition depends on whether the causal link between the review's findings and Engineer B's procurement advantage is treated as dispositive. The Board did not explicitly resolve whether the manner of the review, covert, with Engineer A unable to respond, independently disqualifies Engineer B from the successor engagement even if the timing of formal acceptance was technically compliant.
The franchiser provided Engineer A notice of non-renewal but retained Engineer B for an immediate peer review of Engineer A's active design work before Engineer A's contract expired. Engineer B conducted the review, gaining privileged access to Engineer A's design decisions and pending concerns under conditions Engineer A did not know about and could not contest. Engineer B subsequently accepted the full successor design engineering contract from the franchiser. Engineer A's contract had expired by the time Engineer B was formally retained as design engineer.
Should Engineer B accept the peer review engagement as structured under the franchiser's confidentiality instruction, seek clarification of the instruction's basis before proceeding, or decline the engagement unless the franchiser permits prior notification to Engineer A?
The covert peer review client instruction resistance obligation establishes that a reviewing engineer must resist and decline client instructions requiring a covert review of an incumbent's work, because such instructions cross from permissible client loyalty into facilitation of an ethical violation against a professional peer. A competent engineer exercising proactive ethical vigilance should recognize that a confidentiality instruction of this character signals a structural conflict between faithful agency and peer notification duties, and that accepting the engagement without inquiry forecloses the possibility of negotiating terms that could honor both obligations. The faithful agent duty, by contrast, supports deference to client instructions on engagement terms, and the franchiser's legitimate business interest in managing a confidential transition provides a plausible rationale for the instruction even if that rationale does not ultimately override the notification obligation.
Uncertainty arises from the unknowability of the franchiser's counterfactual response: if the franchiser would have granted notification permission rather than seek a different engineer, then Engineer B's failure to seek clarification was a missed opportunity for a compliant resolution. If the franchiser would have refused and sought a different engineer, then Engineer B's pre-engagement inquiry would have produced no better outcome for Engineer A. The virtue ethics redemption question, whether Engineer B's subsequent voluntary notification partially offsets the initial failure of proactive ethical character, also creates uncertainty about whether the pre-engagement lapse is analytically separable from or subsumed by the subsequent notification decision.
Prior to commencing the peer review, the franchiser explicitly instructed Engineer B not to disclose the new engagement to Engineer A. Engineer A's contract remained active. The confidentiality instruction was facially incompatible with the peer review notification obligation under Section III.8.a, which independently requires that the engineer whose work is under review be informed. Engineer B accepted the engagement without seeking clarification of the franchiser's reasons for the instruction and proceeded with the review the following week.
Should Engineer B limit notification to Engineer A to the existence of the new engagement relationship, or also disclose the preliminary results of the peer review when notifying Engineer A?
The peer review notification obligation and the reviewed engineer's technical comment opportunity preservation obligation together support disclosure of preliminary results, on the ground that Engineer A cannot meaningfully respond to technical concerns without knowing what those concerns are. Against this, the faithful agent duty and the altruistic disclosure non-justification principle hold that disclosing client work product, including preliminary analytical conclusions, without authorization constitutes an independent breach of confidentiality beyond any notification violation, and that benevolent motive does not cure the excess disclosure. A narrower disclosure limited to the existence of the engagement would more closely approximate compliance with Section III.8.a while minimizing the faithful agent violation.
Uncertainty arises from ambiguity about whether the peer review notification obligation is substantively satisfied by disclosing only the existence of the engagement, or whether meaningful compliance requires disclosure of enough preliminary content to give Engineer A a genuine opportunity to respond. If the notification obligation is construed substantively rather than formally, disclosure of at least some preliminary findings may be necessary to honor its purpose. The faithful agent duty's characterization as a general loyalty and fair dealing obligation rather than a strict fiduciary duty also creates ambiguity about whether partial disclosure of work-product conclusions constitutes a material breach or a minor deviation.
When Engineer B notified Engineer A of the new engagement relationship, Engineer B simultaneously disclosed the preliminary results of the peer review of Engineer A's design work. The franchiser had not authorized disclosure of any information, including preliminary analytical conclusions derived from the confidential review engagement. The peer review notification obligation under Section III.8.a requires that the incumbent engineer be informed of the successor's engagement and given an opportunity to respond to technical concerns, but does not expressly specify that preliminary findings must be transmitted as part of the notification.
Should Engineer B seek clarification of the franchiser's reasons for the confidentiality instruction before accepting the peer review engagement, or accept the engagement as structured and manage the resulting conflict between faithful agency and peer notification obligations after the fact?
The pre-engagement client instruction clarification obligation and the conflict recognition duty together support the position that Engineer B should have interrogated the confidentiality instruction before accepting, because a facially anomalous instruction signals a structural incompatibility that a competent engineer must investigate. The incumbent engineer knowledge requirement invoked by Engineer B against the client instruction further supports the view that Engineer B had an independent basis to recognize the conflict at the outset. Against this, the faithful agent duty and the at-will employment symmetry principle support the position that Engineer B was entitled to accept the engagement as offered, relying on the franchiser's legitimate authority to structure the transition and manage the timing of Engineer A's notification.
Uncertainty arises from the indeterminacy of what clarification would have produced: if the franchiser would have refused to modify the confidentiality instruction regardless of Engineer B's inquiry, the clarification obligation would have required Engineer B to decline the engagement entirely rather than merely seek information. The virtue ethics redemption question also creates uncertainty, whether Engineer B's subsequent voluntary notification partially or fully offsets the initial failure of proactive ethical vigilance is unresolved, and the consequentialist case for accepting the engagement and managing the conflict reactively is not obviously weaker than the deontological case for pre-engagement refusal.
The franchiser retained Engineer B and issued an explicit instruction not to disclose the new engagement to Engineer A before Engineer B had conducted any review or raised any questions about the instruction's compatibility with professional obligations. Engineer B accepted the engagement without seeking clarification of the franchiser's reasons for the confidentiality instruction, despite the fact that the instruction was facially anomalous, a client directing a successor engineer not to inform the incumbent of a peer review engagement is precisely the kind of instruction that signals a potential conflict with Section III.8.a. By accepting without inquiry, Engineer B foreclosed the possibility of negotiating engagement terms that might have honored both the faithful agent duty and the peer notification obligation simultaneously.
Should Engineer B notify Engineer A of his relationship with the franchiser and the ongoing peer review despite the franchiser's explicit confidentiality instruction, and if so, at what point relative to conducting the review?
Two competing obligations are in direct tension. The peer review notification obligation (Section III.8.a) requires that the incumbent engineer be informed of the successor's engagement so the incumbent may respond to technical concerns, this duty exists independently of client consent and reflects a categorical commitment to professional fairness and the incumbent's dignity. The faithful agent duty (Section II.4) requires Engineer B to act as a faithful agent and trustee to the franchiser, honoring the explicit confidentiality instruction, though this duty is expressly conditioned on consistency with ethical limits. The peer notification obligation is best understood as a duty owed to the professional community and to Engineer A as a rights-bearing professional; the faithful agent duty is a relational obligation conditioned on ethical limits and therefore cannot categorically override the notification requirement.
Uncertainty arises from the absence of a clear lexical ordering in the NSPE Code when two provisions point in opposite directions. If the faithful agent duty's 'within ethical limits' qualifier is sufficient to transform Engineer B's disclosure from a breach into a permitted act, the notification is vindicated. Conversely, if the one-week post-review notification delay is deemed reasonable under the peer review notification timing standard, the warrant against proceeding may be weakened. The Board split on whether proceeding with the review at that time was ethical, reflecting genuine equipoise between the two obligations.
The franchiser retained Engineer B to conduct a peer review of Engineer A's design work while Engineer A's contract remained active. The franchiser explicitly instructed Engineer B not to disclose the new engagement to Engineer A. Engineer B conducted the review without notifying Engineer A, then notified Engineer A of both the engagement relationship and the preliminary review results after the review was complete. Engineer A was kept uninformed throughout the review period, foreclosing any opportunity to provide context before Engineer B's conclusions were formed.
Should Engineer B have limited disclosure to Engineer A to the existence of the new engagement relationship, or was Engineer B also permitted, or obligated, to share the preliminary review results at the time of notification?
The peer review preliminary results disclosure obligation holds that Engineer A, as the reviewed engineer, is entitled to know the substance of the review's findings so as to have a meaningful opportunity to respond to technical concerns, a purely relational disclosure (existence of engagement only) may be insufficient to protect Engineer A's professional interests if the review has already identified substantive deficiencies. The competing faithful agent duty holds that preliminary review findings constitute confidential client work product, and disclosing them without authorization constitutes an independent breach of confidentiality beyond any notification violation, the notification obligation authorizes disclosure of the engagement relationship but not transmission of substantive analytical conclusions. The reviewed engineer's technical comment opportunity preservation obligation supports broader disclosure, while the faithful agent client interest non-neglect obligation supports limiting disclosure to the minimum required.
Uncertainty arises from ambiguity about whether the peer review notification obligation's purpose, giving the incumbent an opportunity to respond to technical concerns, implicitly requires disclosure of what those concerns are, or whether notification of the engagement relationship alone is sufficient to trigger the incumbent's right to inquire. If the faithful agent duty is a general loyalty and fair dealing obligation rather than a strict fiduciary duty, the scope of what constitutes an unauthorized disclosure may be narrower, creating ambiguity about whether sharing preliminary results crosses the line. The Board's conclusion that disclosure of preliminary results compounded the violation rests on treating the notification obligation as having a defined minimum scope that does not extend to work-product transmission.
When Engineer B notified Engineer A after completing the peer review, Engineer B disclosed both the existence of the new engagement relationship with the franchiser and the preliminary results of the design review. The franchiser had explicitly instructed Engineer B to maintain confidentiality. The peer review notification obligation under Section III.8.a is designed to give the incumbent engineer an opportunity to respond to technical concerns, but the Code provision does not independently authorize the successor engineer to transmit client work product or preliminary analytical conclusions without client consent.
When notifying Engineer A, should Engineer B disclose only the existence of the new engagement relationship (minimum required by Section III.8.a), disclose both the engagement relationship and the preliminary review results (as actually occurred), or disclose only the preliminary review results without identifying the new engagement relationship?
The peer review preliminary results disclosure obligation and the reviewed engineer technical comment opportunity preservation obligation together support sharing preliminary findings with Engineer A, because Engineer A's opportunity to respond to technical concerns is substantively meaningful only if Engineer A knows what those concerns are, disclosure of the engagement relationship alone may be procedurally compliant but substantively hollow. Against this, the faithful agent client interest non-neglect obligation holds that disclosing preliminary review findings constitutes unauthorized transmission of client work product derived from a confidential engagement, representing an independent breach of the confidentiality duty beyond any notification violation. The incumbent engineer knowledge requirement invoked as a competing obligation supports broader disclosure, while the faithful agent trustee duty invoked against Engineer B's disclosure supports limiting disclosure to the minimum required.
Uncertainty arises from the rebuttal condition that the faithful agent duty is a general loyalty and fair dealing obligation rather than a strict fiduciary duty, which creates ambiguity about whether sharing preliminary findings, which serve Engineer A's legitimate professional interest in responding to technical concerns, constitutes a material breach or a permissible exercise of professional judgment within the scope of the notification obligation. It is also unclear whether the peer notification obligation's purpose of preserving Engineer A's technical comment opportunity implicitly requires disclosure of findings sufficient to make that opportunity meaningful, or whether the obligation is satisfied by notice of the engagement relationship alone.
After completing the design review, Engineer B notified Engineer A of both the new engagement relationship with the franchiser and the preliminary results of the review. The franchiser's confidentiality instruction had not authorized disclosure of either the engagement relationship or the review findings. The peer review notification obligation under Section III.8.a requires that the incumbent engineer be informed of the successor's engagement and given an opportunity to respond to technical concerns, but does not expressly specify whether preliminary findings must also be shared. Engineer A's contract remained active at the time of notification.
Should Engineer B proceed with the design review before notifying Engineer A, or treat pre-review notification of Engineer A as a mandatory prerequisite that must be satisfied before any substantive review work begins?
The peer review notification obligation under Section III.8.a and the reasonable timing compliance standard together suggest that notification must precede substantive review work, because the notification's purpose, preserving the incumbent's opportunity to respond to technical concerns, is defeated if the review is already complete when notification occurs. Against this, the faithful agent duty and the franchiser's confidentiality instruction support completing the review before any disclosure, on the theory that the review itself is client work product and that notification timing is a secondary procedural matter that can be remedied post-hoc. The sequential dependency principle holds that the ethical permissibility of proceeding with the review is logically downstream of the notification timing question.
Uncertainty is created by the absence of a bright-line rule specifying when the notification obligation attaches relative to the incumbent's contract status and the review's commencement. If the one-week notification delay is deemed reasonable under the timing compliance standard, the warrant against proceeding may be weakened. Additionally, if Engineer A suffered no concrete professional harm from the timing, because Engineer A's technical comment opportunity was substantively preserved through the post-review notification, the consequentialist case against proceeding before notification is diminished. The Board split on this question and could not reach agreement.
Engineer B conducted the full design review while Engineer A remained uninformed and under an active contract. The review was completed before Engineer B notified Engineer A of the engagement relationship. Engineer A's opportunity to provide context or correct misunderstandings before Engineer B's preliminary conclusions were formed was permanently foreclosed by the time notification occurred. The franchiser's confidentiality instruction was in effect throughout the review period, and Engineer A's contract was still active during the review.
Should Engineer B have sought clarification of the franchiser's confidentiality instruction before accepting the engagement, potentially conditioning acceptance on modified terms, or was it permissible to accept the engagement as structured and navigate the resulting ethical conflict after the fact?
The pre-engagement clarification obligation holds that a competent engineer exercising reasonable professional judgment must recognize when a client instruction facially conflicts with a professional duty and must seek clarification before proceeding. This obligation is grounded in the principle that engineers should not accept engagements structured to make ethical compliance impossible from the outset. The competing warrant is the faithful agent duty, which generally requires deference to client instructions on business and operational matters, an engineer is not ordinarily required to interrogate every client instruction before accepting an engagement, and demanding justification for a confidentiality instruction could itself be seen as a breach of the client relationship. The at-will employment symmetry principle further supports the franchiser's position that it had legitimate business reasons for managing the transition confidentially, reasons it was not obligated to disclose to Engineer B at the outset.
Uncertainty arises from the indeterminacy of the threshold at which a client instruction becomes sufficiently anomalous to trigger a pre-engagement clarification duty. Not every unusual client instruction requires interrogation; the question is whether this particular instruction, directing concealment of a peer review engagement from the incumbent engineer, crossed the threshold of facial incompatibility with professional obligations that a competent engineer should have recognized. A further rebuttal condition is whether seeking clarification would have been futile: if the franchiser's business reasons for confidentiality were legitimate (e.g., avoiding disruption during a sensitive transition), clarification might have produced a modified engagement structure rather than a refusal, meaning the clarification obligation, if triggered, was not necessarily equivalent to a duty to decline. The virtue ethics redemption question also creates uncertainty: whether Engineer B's subsequent voluntary notification partially or fully offsets the initial failure of proactive ethical vigilance is unresolved.
The franchiser retained Engineer B and issued an explicit instruction not to disclose the new engagement to Engineer A. Engineer B accepted the engagement without seeking clarification of the reasons behind the confidentiality instruction. The instruction was facially anomalous, a client directing a successor engineer not to inform the incumbent engineer of a peer review engagement is precisely the kind of instruction that signals a potential conflict with professional obligations under Section III.8.a. By accepting without inquiry, Engineer B foreclosed the possibility of negotiating terms that might have honored both the faithful agent duty and the peer notification obligation simultaneously.
Event Timeline (13)
Case timeline
- Contractual obligation to provide notice of non-renewal
- Business prerogative to select engineering partners
- Spirit of fair dealing toward Engineer A, whose work was being reviewed without full transparency during an active contractual relationship
- Client's right to seek engineering services from a provider of its choosing
- Business obligation to address pending design concerns without delay
- Client's prerogative to set terms of engagement with retained engineers
- Business interest in managing a sensitive personnel and vendor transition
- 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
- 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
- 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)
- Contractual obligation to the franchiser to perform the requested design review
- Professional competence obligation to conduct a thorough engineering review
- NSPE Code Section III.8.a: notification to Engineer A that his work was being reviewed by another engineer for the same client
- 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'
Narrative (3 main characters)
View ExtractionOpening 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.
Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation
Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Covert Peer Review Client Instruction Resistance Obligation
Tension between Engineer B Preliminary Review Results Disclosure to Engineer A and Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure
Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Engineer B Client Confidentiality Instruction Faithful Agent Compliance
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.
Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Client Instruction Non-Override of Incumbent Peer-Review Notification Obligation
Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Covert Peer Review Client Instruction Resistance Obligation
Tension between Engineer B Preliminary Review Results Disclosure to Engineer A and Faithful Agent Trustee Duty Invoked Against Engineer B Disclosure
Tension between Engineer B Peer Review Notification of Engineer A Despite Client Instruction and Engineer B Client Confidentiality Instruction Faithful Agent Compliance
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.
Tension between Engineer B Covert Review Client Instruction Resistance and Covert Peer Review Client Instruction Resistance Obligation
Tension between Engineer B Peer Review Notification and Consent Fulfillment and Engineer B Client Confidentiality Instruction Faithful Agent Compliance
Tension between Engineer B Faithful Agent Peer Review Collegial Boundary Exercise and Franchiser Peer Review Procedural Fairness Non-Compliance Covert Instruction
Tension between Engineer B Client Confidentiality Instruction Faithful Agent Compliance BER Case and Peer Review Notification Obligation Standard Section III.8.a
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.
Tension between Engineer B Pre-Engagement Client Instruction Rationale Clarification BER Case and Covert Peer Review Client Instruction Resistance Obligation
Tension between Pre-Engagement Client Instruction Clarification Obligation and Faithful Agent Obligation Within Ethical Limits Invoked By Engineer B Toward Franchiser
Tension between Engineer B Faithful Agent Trustee General Loyalty Non-Fiduciary Interpretation BER Case and Peer Review Incumbent Notification Reasonable Timing Compliance Obligation
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.
Show 6 other tensions
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)
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.