Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Pipeline Steps
Overview
1 Contextual Framework
2 Normative Requirements
3 Temporal Dynamics Reconcile
4 Whole-Case Synthesis
Extraction Review Full View
Provenance
Confidentiality of Competitor Information Submitted to Government Agency
Step 4 of 5
Entity Review

280

Entities

4

Provisions

3

Precedents

17

Questions

25

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
Engineer A is permanently positioned at the intersection of two incompatible obligation sets — her right to pursue private employment at Company Y and her categorical, duration-indeterminate duty to protect Company X's confidential regulatory submissions — without any mechanism established by the Board to exit that intersection. The Board's conditional permission preserves both obligations simultaneously rather than resolving the conflict: Engineer A may work at Company Y (Obligation Set 1 honored) but must never operationalize her government-acquired knowledge of Company X's designs (Obligation Set 2 honored), yet the practical work environment at a direct competitor makes these two obligations structurally incompatible in any assignment domain touching Company X's facility designs. The stalemate is further entrenched by the Board's silence on duration, recusal formalization, Company X notification, and adversarial participation risk — each unresolved dimension adding another layer of competing valid duties that Engineer A must navigate indefinitely without a governing resolution mechanism.
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.4. Engineers shall act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 34)
Obligation
Engineer A Regulatory Submission Confidentiality Protection
Acting as a faithful agent requires Engineer A to protect confidential information received in a regulatory capacity on behalf of the government body.
Action
Resign from Government Agency
Acting as a faithful agent requires the engineer to consider obligations to the government agency before resigning to work for a competitor.
State
Engineer A Client Relationship with Company Y
Engineer A must act as a faithful agent to Company Y while managing prior confidential obligations to Company X.
Obligation (6)
  • Engineer A Regulatory Submission Confidentiality Protection
    Acting as a faithful agent requires Engineer A to protect confidential information received in a regulatory capacity on behalf of the government body.
  • Engineer A Regulatory Submission Confidentiality Protection Company X
    Faithful agent duty obligates Engineer A to safeguard Company X's proprietary information received during regulatory proceedings.
  • Engineer A Post-Public-Employment Confidential Information Non-Use
    Faithful agent obligations extend to refraining from exploiting confidential information gained while serving in a public regulatory role.
  • Engineer A Post-Public-Employment Confidential Information Non-Use Company X
    Acting as a faithful agent requires Engineer A not to disclose or use Company X's confidential information accessed during government service.
  • Engineer A Government-to-Private Competitive Employment Acceptance With Confidentiality Constraint
    The faithful agent duty underlies the obligation to refrain from using confidential information even when accepting new private employment.
  • Company Y AE Firm Incumbent Advantage Non-Exploitation Regarding Company X Information
    Company Y as an employer must act faithfully and not exploit confidential competitor information improperly obtained through hiring Engineer A.
Action (3)
  • Resign from Government Agency
    Acting as a faithful agent requires the engineer to consider obligations to the government agency before resigning to work for a competitor.
  • Accept Position at Competitor
    Taking a position at a competitor while holding duties to a current employer or client implicates the faithful agent obligation.
  • Withhold Company X Confidential Information
    Faithfully serving the government agency includes not misusing confidential competitor information accessed through that role.
State (5)
  • Engineer A Client Relationship with Company Y
    Engineer A must act as a faithful agent to Company Y while managing prior confidential obligations to Company X.
  • Engineer A Post-Employment Conflict of Interest
    Acting as a faithful agent to a new employer is directly compromised by prior access to a competitor's confidential information.
  • Engineer A Post-Government Competitor Employment Conflict
    The duty to act as a faithful agent to Company Y conflicts with obligations arising from prior access to Company X's proprietary information.
  • Engineer A Continuing Post-Termination Loyalty to Attorney Z's Client. BER Case 85-4
    The faithful agent duty extends to prior clients and creates continuing obligations even after formal termination of the relationship.
  • Engineer A Cross-Side Retention After Plaintiff Confidential Access. BER Case 85-4
    Accepting retention by the defendant's attorney violates the duty to act as a faithful agent to the original plaintiff client.
Constraint (5)
  • Engineer A Faithful Agent Confidentiality Obligation. Government Agency Regulatory Context
    The faithful agent provision directly creates Engineer A's duty to protect Company X's confidential information entrusted to the government agency.
  • Engineer A Revolving Door Government-to-Competitor Employment Conflict. Company Y
    Acting as a faithful agent prohibits Engineer A from leveraging her government role to benefit a competitor employer.
  • Engineer A Revolving Door Government-to-Competitor Conflict. Current Case
    The faithful agent duty underlies the conflict created by Engineer A transitioning from a regulatory role to employment with a direct competitor.
  • Company Y Non-Exploitation of Engineer A's Prior Government Access to Company X Information
    The faithful agent obligation extends to preventing Company Y from exploiting the trust relationship Engineer A held with the government agency.
  • Engineer A No Formal Revolving Door Provision Gap. Government Agency Employment Contract
    The faithful agent duty exists independently of contractual provisions, meaning the absence of explicit revolving door clauses does not eliminate Engineer A's obligations.
Principle (3)
  • Faithful Agent Confidentiality Obligation Grounding Engineer A's Duty
    The faithful agent provision directly grounds Engineer A's duty to maintain confidentiality of Company X's information as a trustee.
  • Loyalty Obligation of Engineer A to Company Y Within Ethical Limits
    The faithful agent provision establishes Engineer A's loyalty obligation to Company Y while recognizing ethical limits on that loyalty.
  • Conflict of Interest Avoidance Through Confidentiality Maintenance
    Acting as a faithful agent requires Engineer A to manage the conflict of interest arising from Company X's confidential information through confidentiality maintenance.
Role (2)
  • Engineer A Confidentiality-Bound Government Agency Engineer
    Engineer A must act as a faithful agent to the government agency employer and protect the confidential information entrusted to that agency.
  • Engineer A Forensic Expert Switching Sides
    Engineer A must act as a faithful agent to each client, meaning switching sides between Attorney Z and Attorney X raises concerns about faithful service.
Event (2)
  • Competitive Conflict Situation Arises
    Engineers must act as faithful agents or trustees, which is directly tested when a competitive conflict situation emerges between client interests.
  • Engineer Retained By Opposing Party (BER 82-6)
    Being retained by an opposing party challenges the engineer's duty to act as a faithful agent or trustee to the original client.
Resource (3)
  • NSPE_Code_of_Ethics_Confidentiality_Provisions
    The faithful agent obligation directly governs Engineer A's duty to protect confidential information obtained during government service.
  • Transitional_Employment_Ethics_Framework_Regulatory_Context
    Acting as a faithful agent applies to Engineer A's obligations as she transitions from public to private employment.
  • Engineer Confidentiality and Loyalty Obligation Standard - General
    The general loyalty and confidentiality obligation standard directly reflects the faithful agent duty under II.4.
Capability (5)
  • Engineer A Faithful Agent Trustee Confidentiality Obligation Source Recognition
    This provision directly establishes the faithful agent and trustee duty that Engineer A must recognize as the source of confidentiality obligations to Company X.
  • Engineer A Permissible Competitive Employment Acceptance With Confidentiality Constraint Navigation
    Acting as a faithful agent requires Engineer A to navigate employment with Company Y while honoring confidentiality constraints owed to Company X.
  • Engineer A Post-Public-Employment Confidential Information Non-Use Company X
    The faithful agent duty requires Engineer A not to use Company X's confidential information accessed during government employment for competitive purposes.
  • Company Y Competitor Firm Incumbent Information Advantage Non-Exploitation
    Company Y's obligation to avoid exploiting Engineer A's prior access aligns with the faithful agent duty owed to Company X through Engineer A.
  • Company Y Competitor Firm Incumbent Information Advantage Non-Exploitation Organizational
    Company Y as an organization must refrain from exploiting competitive advantages derived from Engineer A's prior government access, consistent with faithful agent obligations.
II.4.a. Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services.
How this applies in the case (showing 3 of 38)
Obligation
Engineer A Conflict of Interest Disclosure to Company Y Regarding Company X Access
This provision directly requires Engineer A to disclose the potential conflict arising from prior access to Company X's confidential information.
Action
Accept Position at Competitor
Accepting employment at a competitor creates a conflict of interest that must be disclosed to all relevant parties.
State
Engineer A Conflict of Interest. Cross-Side Adversarial Retention BER 85-4
Engineer A must disclose the conflict arising from prior obligations to the plaintiff when being retained by the defendant's attorney.
Obligation (4)
  • Engineer A Conflict of Interest Disclosure to Company Y Regarding Company X Access
    This provision directly requires Engineer A to disclose the potential conflict arising from prior access to Company X's confidential information.
  • Engineer A Post-Public-Service Competitor Employment Conflict Avoidance
    Assessing and disclosing conflicts before accepting employment with a competitor is directly required by the conflict of interest disclosure provision.
  • Engineer A Conflict of Interest Disclosure Evolution Compliance
    This provision mandates prompt disclosure of all known conflicts, which is the evolved standard Engineer A must comply with.
  • BER 82-6 Engineer US Government Dam Failure Switching Sides
    Switching sides in a dispute creates a conflict of interest that should have been disclosed, directly implicating the conflict disclosure requirement.
Action (2)
  • Accept Position at Competitor
    Accepting employment at a competitor creates a conflict of interest that must be disclosed to all relevant parties.
  • Access Confidential Design Information
    Accessing a competitor's confidential information while considering outside employment represents a potential conflict of interest requiring disclosure.
State (5)
  • Engineer A Conflict of Interest. Cross-Side Adversarial Retention BER 85-4
    Engineer A must disclose the conflict arising from prior obligations to the plaintiff when being retained by the defendant's attorney.
  • Engineer A Post-Government Competitor Employment Conflict
    Engineer A must disclose the conflict of interest created by possessing Company X's confidential information while employed by competitor Company Y.
  • Engineer A Post-Employment Conflict of Interest
    The transition from regulatory employment to private employment with a competitor creates a conflict that must be disclosed to all interested parties.
  • Engineer A Revolving Door Transition
    The movement from a regulatory role with access to confidential submissions to private industry employment creates a conflict requiring disclosure.
  • Engineer A Cross-Side Retention After Plaintiff Confidential Access. BER Case 85-4
    Engineer A must disclose the conflict of interest arising from prior confidential access to the plaintiff's information before accepting the defendant's retention.
Constraint (6)
  • Engineer A Conflict of Interest Disclosure to Company Y. Prior Government Access to Company X Information
    This provision directly requires Engineer A to disclose her prior access to Company X's confidential information to Company Y before accepting employment.
  • Engineer A Conflict of Interest Disclosure to Company Y. Current Case
    The conflict of interest disclosure provision directly mandates Engineer A to inform Company Y of her prior regulatory access to Company X's proprietary data.
  • Engineer A Revolving Door Government-to-Competitor Employment Conflict. Company Y
    The potential conflict of interest created by moving from regulator to competitor employee must be disclosed under this provision.
  • Engineer A Revolving Door Government-to-Competitor Conflict. Current Case
    This provision requires disclosure of the conflict arising from Engineer A's prior regulatory authority over Company X when joining Company Y.
  • Engineer A Full Discussion With Attorney Z Obligation Constraint. BER Case 85-4
    The obligation to disclose conflicts of interest requires full discussion with the original retaining party before switching sides, as illustrated in BER Case 85-4.
  • Engineer A Switching Sides Forensic Expert Bar. BER Case 85-4
    The conflict of interest disclosure provision underlies the prohibition on switching from plaintiff's counsel to defendant's counsel without disclosure and consent.
Principle (4)
  • Conflict of Interest Disclosure Evolution Principle Invoked By Engineer A Dual Relationship
    The conflict of interest disclosure provision directly applies to Engineer A's dual relationship involving simultaneous knowledge of Company X's confidential information and employment with Company Y.
  • Post-Public-Service Conflict Avoidance Invoked By Engineer A Transition to Company Y
    The disclosure provision requires Engineer A to disclose the potential conflict arising from transitioning to Company Y after accessing Company X's confidential information.
  • Revolving Door Integrity Invoked By Engineer A Government-to-Private Transition
    The conflict disclosure provision applies to Engineer A's government-to-private transition where prior access to proprietary information creates an apparent conflict.
  • Conflict of Interest Avoidance Through Confidentiality Maintenance
    The provision requiring disclosure of conflicts directly relates to managing the conflict created by Engineer A's access to Company X's confidential information.
Role (2)
  • Engineer A Forensic Expert Switching Sides
    Engineer A must disclose the conflict of interest arising from being initially retained by plaintiff's counsel and then sought by defendant's counsel on the same case.
  • Engineer A Confidentiality-Bound Government Agency Engineer
    Engineer A must disclose potential conflicts of interest stemming from prior access to Company X's confidential information when taking on new employment or engagements.
Event (2)
  • Competitive Conflict Situation Arises
    When a competitive conflict situation arises, engineers are obligated to disclose all known or potential conflicts of interest.
  • Engineer Retained By Opposing Party (BER 82-6)
    Accepting employment with an opposing party creates a conflict of interest that must be disclosed to all relevant parties.
Resource (4)
  • Adversarial_Proceeding_Conflict_of_Interest_Standard_Competitor_Context
    The conflict of interest disclosure requirement applies directly to Engineer A working for a competitor against Company X whose confidential data she accessed.
  • Public_Official_Conflict_of_Interest_Standard_Regulatory_Access
    Engineer A's prior regulatory access to competitors' proprietary data creates a conflict of interest she must disclose under II.4.a.
  • Revolving_Door_Employment_Policy_Regulatory_Engineer
    The revolving door policy framework implicates the conflict of interest disclosure obligation when Engineer A moves to a competing private employer.
  • NSPE Code of Ethics - Section II.4.b
    Section II.4.b is referenced in BER Case No. 85-4 in connection with conflict of interest and side-switching, directly linking to the disclosure requirement of II.4.a.
Capability (9)
  • Engineer A Post-Government-Employment Competitive Conflict Pre-Acceptance Assessment
    This provision requires Engineer A to assess and disclose potential conflicts of interest before accepting employment at Company Y.
  • Engineer A Prior Government Access Disclosure to Company Y
    This provision directly requires Engineer A to disclose her prior government access to Company X's confidential information to Company Y upon or before accepting employment.
  • Engineer A Revolving Door Conflict Recognition Government to Company Y
    Recognizing the revolving door conflict is a prerequisite to disclosing it as required by this provision.
  • Engineer A Conflict of Interest Disclosure Evolution Compliance
    This provision establishes the disclosure standard that Engineer A must comply with under the evolved conflict-of-interest management framework.
  • Engineer A Conflict of Interest Evolution Standard Compliance
    This provision requires Engineer A to apply the current standard of prompt disclosure of all known conflicts, directly linking to this capability.
  • Engineer A Forensic Expert Side-Switching Conflict Assessment
    This provision requires Engineer A to assess and disclose the conflict of interest arising from switching sides in a forensic expert capacity.
  • Engineer A Forensic Expert Switching Sides Conflict Assessment BER 85-4
    This provision requires disclosure of conflicts that could influence judgment, directly applicable to the side-switching forensic expert scenario.
  • BER 82-6 Dam Failure Engineer Switching Sides Adverse Retention Motivation Recognition
    Recognizing adverse retention motivation is necessary to fulfill the conflict disclosure obligation required by this provision.
  • Engineer A Adverse Retention Motivation Recognition
    Recognizing that retention is motivated by a desired favorable opinion is necessary to identify and disclose the conflict as required by this provision.
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 57)
Obligation
Engineer A Post-Public-Employment Confidential Information Non-Use
This provision directly prohibits disclosing confidential information of a former employer or public body without consent.
Action
Withhold Company X Confidential Information
This provision directly governs the obligation not to disclose confidential business or technical information obtained from a client or employer without consent.
State
Engineer A Confidential Information Held. Government Agency Context
Engineer A must not disclose Company X's confidential and proprietary design information acquired through government agency employment.
Obligation (9)
  • Engineer A Post-Public-Employment Confidential Information Non-Use
    This provision directly prohibits disclosing confidential information of a former employer or public body without consent.
  • Engineer A Post-Public-Employment Confidential Information Non-Use Company X
    This provision directly prohibits Engineer A from disclosing or using Company X's confidential information obtained during government regulatory work.
  • Engineer A Regulatory Submission Confidentiality Protection
    This provision requires protection of confidential information received from Company X during the regulatory approval process.
  • Engineer A Regulatory Submission Confidentiality Protection Company X
    This provision directly mandates that Engineer A not disclose Company X's proprietary design information received in a regulatory context.
  • Engineer A Government-to-Private Competitive Employment Acceptance With Confidentiality Constraint
    This provision underlies the confidentiality constraint that applies even when Engineer A permissibly accepts new employment with a competitor.
  • Engineer A Former Regulatory Access Adversarial Non-Participation Company X
    Refraining from activities that exploit confidential information is directly tied to the prohibition on disclosing confidential information without consent.
  • Engineer A Former Regulatory Access Adversarial Non-Participation
    This provision prohibits using confidential information in ways adverse to the former client or public body, supporting the non-participation obligation.
  • Engineer A Former Client Confidentiality Perpetuation Post-Termination
    This provision requires continued protection of confidential information obtained from a former client even after the engagement ends.
  • Company Y AE Firm Incumbent Advantage Non-Exploitation Regarding Company X Information
    This provision supports the obligation that confidential competitor information must not be exploited, binding both Engineer A and Company Y.
Action (3)
  • Withhold Company X Confidential Information
    This provision directly governs the obligation not to disclose confidential business or technical information obtained from a client or employer without consent.
  • Access Confidential Design Information
    Accessing and potentially using confidential design information without consent violates the prohibition on disclosing confidential client or employer information.
  • Accept Retention by Opposing Party (BER 82-6)
    Accepting retention by an opposing party risks unauthorized disclosure of confidential information gained through prior engagement.
State (7)
  • Engineer A Confidential Information Held. Government Agency Context
    Engineer A must not disclose Company X's confidential and proprietary design information acquired through government agency employment.
  • Engineer A Government Regulatory Access to Confidential Submissions
    Confidential submissions received from Company X and other companies during regulatory employment must not be disclosed without consent.
  • Engineer A Government Agency Confidential Access to Company X Information
    Company X's confidential and proprietary design information retained after government employment must not be disclosed without consent.
  • Engineer A Employment Terminated from Government Agency
    Post-employment termination does not eliminate the obligation to protect confidential information accessed during government service.
  • Engineer A Post-Government Competitor Employment Conflict
    Employment with a direct competitor creates a direct risk of disclosing Company X's confidential information in violation of this provision.
  • Engineer A Client Relationship with Company Y
    Working for Company Y as a competitor of Company X creates pressure to disclose confidential information that must be protected under this provision.
  • Engineer A Continuing Post-Termination Loyalty to Attorney Z's Client. BER Case 85-4
    Confidential information shared by the plaintiff's attorney must not be disclosed even after the formal retainer relationship has ended.
Constraint (10)
  • Engineer A Post-Public-Employment Confidential Information Non-Use. Company X Design Information
    This provision directly prohibits Engineer A from disclosing or using Company X's confidential design information accessed during government employment.
  • Engineer A Regulatory Submission Confidentiality Protection. Company X Information
    This provision creates the obligation to protect Company X's confidential information received through the regulatory submission process.
  • Engineer A Post-Employment Confidential Information Retention. Company X Design Data
    This provision prohibits retention and use of confidential information after the employment relationship ends.
  • Engineer A Post-Public-Employment Non-Exploitation of Company X Confidential Information. Current Case
    This provision directly prohibits Engineer A from exploiting Company X's confidential information accessed during her government role.
  • Engineer A Government Regulatory Access Competitor Employment Scope Limitation. Current Case
    This provision creates the constraint that limits the scope of Engineer A's permissible activities at Company Y by prohibiting use of confidential information.
  • Engineer A Former Regulatory Access Adversarial Non-Participation. Company X Matters at Company Y
    This provision prohibits Engineer A from participating in work adverse to Company X that would exploit confidential information she received without consent.
  • Company Y Non-Exploitation of Engineer A's Prior Government Access to Company X Information
    This provision supports the constraint that Company Y cannot exploit confidential information about Company X that Engineer A accessed without Company X's consent.
  • BER 82-6 Engineer US Government Dam Failure Contractor Retention Bar
    This provision underlies the prohibition on the government-retained engineer disclosing confidential information by switching to represent the contractor.
  • Engineer A Switching Sides Forensic Expert Bar. BER Case 85-4
    This provision prohibits Engineer A from disclosing confidential information gained while retained by plaintiff's counsel by switching to defendant's counsel.
  • Engineer A Post-Employment Duty of Trust Duration. BER Case 85-4
    This provision establishes that the confidentiality obligation persists after formal termination of the retainer agreement.
Principle (7)
  • Confidentiality Obligation of Engineer A Toward Company X Regulatory Submissions
    This provision directly prohibits Engineer A from disclosing Company X's confidential regulatory submission information without consent.
  • Regulatory Submission Confidentiality Protection Obligation Invoked By Engineer A Access to Company X Information
    The provision establishes the confidentiality obligation protecting Company X's proprietary design information accessed during government employment.
  • Confidentiality Obligation Invoked for Company X Information Held by Engineer A
    This provision is the direct source of Engineer A's prohibition against disclosing Company X's confidential and proprietary design information.
  • Regulatory Submission Confidentiality Protection Applied to Company X Information
    The provision supports the obligation to protect Company X's confidential information submitted to the government agency for regulatory purposes.
  • Confidentiality Duration Indeterminacy Acknowledged by Board
    This provision underlies the Board's acknowledgment that the post-relationship confidentiality duty persists without a specified duration.
  • Former Client Adversarial Participation Prohibition Invoked By Engineer A Company X Knowledge
    The confidentiality provision supports prohibiting Engineer A from participating adversarially against Company X using information gained during prior access.
  • Faithful Agent Confidentiality Obligation Grounding Engineer A's Duty
    This provision directly establishes the confidentiality duty that grounds Engineer A's obligation as a faithful agent toward Company X's information.
Role (3)
  • Engineer A Confidentiality-Bound Government Agency Engineer
    Engineer A is directly bound not to disclose confidential and proprietary design information obtained from Company X during government agency employment.
  • Engineer A Forensic Expert Switching Sides
    Engineer A must not disclose Company X's confidential information when providing forensic analysis for either Attorney Z or Attorney X without consent.
  • Company Y Competitor-Employing Private Engineering Company
    Company Y's hiring of Engineer A creates a situation where confidential information from Company X could be improperly disclosed, implicating this provision.
Event (4)
  • Confidential Knowledge Accumulated
    The accumulation of confidential information triggers the obligation not to disclose it without consent.
  • Perpetual Confidentiality Obligation Activated
    This provision directly establishes the ongoing duty not to disclose confidential business or technical information without consent.
  • Engineer Retained By Opposing Party (BER 82-6)
    When retained by an opposing party, the engineer risks disclosing confidential information gained from the former client without consent.
  • Favorable Report Opportunity Foreclosed (BER 85-4)
    The foreclosure of a favorable report opportunity relates to the prohibition on disclosing confidential information that could benefit a competing party.
Resource (7)
  • NSPE_Code_of_Ethics_Confidentiality_Provisions
    III.4 is the primary confidentiality provision directly governing Engineer A's obligation not to disclose proprietary information obtained during government service.
  • Government_Agency_Confidential_Information_Access_Policy_Instance
    III.4 directly applies to the specific confidential and proprietary design information Engineer A received from Company X and others in her regulatory role.
  • BER_Case_Precedent_Confidentiality_PostEmployment
    Prior BER decisions on post-employment confidentiality obligations provide analogical reasoning grounded in III.4.
  • BER Case No. 82-6
    BER Case No. 82-6 establishes precedent under confidentiality provisions consistent with III.4 regarding engineers who obtained confidential information in government service.
  • BER Case No. 85-4
    BER Case No. 85-4 applies confidentiality obligations analogous to III.4 in the context of an engineer switching sides after gaining confidential information.
  • Engineer Confidentiality and Loyalty Obligation Standard - General
    The general confidentiality obligation standard directly implements III.4 in determining what Engineer A may and may not disclose to Company Y.
  • NSPE Code of Ethics - Section III.4.b
    Section III.4.b is cited in BER Case No. 82-6 as the basis for the confidentiality finding, making it directly linked to the III.4 provision framework.
Capability (7)
  • Engineer A Confidential Regulatory Submission Information Boundary Recognition
    This provision directly requires Engineer A to recognize and respect the confidentiality boundaries of Company X's proprietary design information received during government employment.
  • Government Agency Employer Regulatory Submission Confidentiality Protection
    This provision obligates the government agency to protect confidential information submitted by Company X without consent for disclosure.
  • Engineer A Post-Public-Employment Confidential Information Non-Use Company X
    This provision directly prohibits Engineer A from disclosing or using Company X's confidential information accessed during government employment without consent.
  • Engineer A Adversarial Non-Participation Scope Determination at Company Y
    This provision requires Engineer A to identify and avoid assignments at Company Y that would involve disclosing or using Company X's confidential information.
  • Engineer A Confidential Information Mental Segregation Impossibility Recognition
    This provision underlies the concern that Engineer A cannot avoid disclosing confidential information if mental segregation is impossible after exposure.
  • Engineer A Faithful Agent Trustee Confidentiality Obligation Source Recognition
    This provision is one of the direct sources of the confidentiality obligation that Engineer A must recognize as applying to Company X's information.
  • Engineer A Former Client Duty of Trust and Loyalty Duration Assessment
    This provision establishes that confidentiality duties to former clients persist, requiring Engineer A to assess their duration and ongoing applicability.
III.4.a. Engineers shall not, without the consent of all interested parties, promote or arrange for new employment or practice in connection with a specific project for which the engineer has gained particular and specialized knowledge.
How this applies in the case (showing 3 of 40)
Obligation
Engineer A Post-Public-Service Competitor Employment Conflict Avoidance
This provision directly addresses the obligation to assess conflicts before arranging new employment connected to specialized knowledge gained on a specific project.
Action
Accept Position at Competitor
This provision prohibits arranging new employment using specialized knowledge gained from a specific project without consent of all interested parties.
State
Engineer A Revolving Door Transition
Engineer A arranged new private employment using specialized knowledge gained from regulatory access to confidential industry submissions.
Obligation (5)
  • Engineer A Post-Public-Service Competitor Employment Conflict Avoidance
    This provision directly addresses the obligation to assess conflicts before arranging new employment connected to specialized knowledge gained on a specific project.
  • Engineer A Former Regulatory Access Adversarial Non-Participation Company X
    This provision prohibits arranging new practice that exploits specialized knowledge gained in a prior role, supporting non-participation in adverse activities.
  • Engineer A Former Regulatory Access Adversarial Non-Participation
    This provision restricts participation in new employment activities that leverage specialized knowledge gained from a prior regulatory engagement.
  • BER 82-6 Engineer US Government Dam Failure Switching Sides
    This provision prohibits arranging new employment on the opposing side of a matter for which the engineer gained specialized knowledge, directly applicable to switching sides.
  • Engineer A Government-to-Private Competitive Employment Acceptance With Confidentiality Constraint
    This provision conditions new employment acceptance on not exploiting specialized knowledge gained in the prior regulatory role involving Company X.
Action (3)
  • Accept Position at Competitor
    This provision prohibits arranging new employment using specialized knowledge gained from a specific project without consent of all interested parties.
  • Resign from Government Agency
    Resigning to pursue employment leveraging specialized knowledge gained through the government role implicates this provision.
  • Accept Retention by Opposing Party (BER 82-6)
    Arranging new retention by an opposing party using specialized knowledge from a prior engagement is directly governed by this provision.
State (5)
  • Engineer A Revolving Door Transition
    Engineer A arranged new private employment using specialized knowledge gained from regulatory access to confidential industry submissions.
  • Engineer A Post-Government Competitor Employment Conflict
    Engineer A's new employment with Company Y is directly connected to the specialized knowledge gained from reviewing Company X's confidential submissions.
  • Engineer A Post-Employment Conflict. Company Y Competitor Employment
    Accepting employment with a competitor after gaining specialized knowledge from confidential regulatory submissions implicates this provision directly.
  • Engineer A Cross-Side Retention After Plaintiff Confidential Access. BER Case 85-4
    Engineer A arranged new employment with the opposing party using specialized knowledge gained from confidential access during the original engagement.
  • Engineer A Government Agency Confidential Access to Company X Information
    The specialized knowledge gained from Company X's confidential submissions was the basis for Engineer A's transition to competitor employment.
Constraint (7)
  • Engineer A Revolving Door Government-to-Competitor Employment Conflict. Company Y
    This provision prohibits arranging new employment with Company Y using specialized knowledge gained from reviewing Company X's confidential regulatory submissions.
  • Engineer A Revolving Door Government-to-Competitor Conflict. Current Case
    This provision directly applies to Engineer A's transition to Company Y, a competitor, using specialized knowledge gained from her government regulatory role over Company X.
  • Engineer A Government Regulatory Access Competitor Employment Scope Limitation. Current Case
    This provision creates the limitation on Engineer A's new employment scope by prohibiting use of specialized knowledge gained from Company X's regulatory submissions.
  • Engineer A Switching Sides Forensic Expert Bar. BER Case 85-4
    This provision prohibits Engineer A from arranging new employment with opposing counsel using specialized knowledge gained from the original retaining party.
  • BER 82-6 Engineer US Government Dam Failure Contractor Retention Bar
    This provision prohibits the government engineer from accepting retention by the contractor using specialized knowledge gained from the government-commissioned study.
  • Engineer A Naivety Non-Exculpation. BER Case 85-4
    This provision's prohibition on leveraging specialized knowledge for new employment applies regardless of Engineer A's claimed unawareness of the opposing party's motivations.
  • Engineer A Former Regulatory Access Adversarial Non-Participation. Company X Matters at Company Y
    This provision constrains Engineer A from participating in work at Company Y that exploits the specialized knowledge gained from Company X's regulatory submissions.
Principle (5)
  • Post-Public-Service Conflict Avoidance Invoked By Engineer A Transition to Company Y
    This provision directly addresses Engineer A's acceptance of new employment with Company Y in connection with specialized knowledge gained from Company X's regulatory submissions.
  • Revolving Door Integrity Invoked By Engineer A Government-to-Private Transition
    The provision restricting new employment arrangements using specialized knowledge directly applies to Engineer A's government-to-private sector transition.
  • Competitive Employment Freedom Invoked for Engineer A Joining Company Y
    This provision qualifies the limits on Engineer A's freedom to join Company Y by restricting use of specialized knowledge gained from Company X.
  • Switching Sides Prohibition Applied to Engineer A Forensic Expert Role in BER Case 85-4
    The provision against arranging new employment using specialized project knowledge parallels the switching sides prohibition applied in BER Case 85-4.
  • Former Client Adversarial Participation Prohibition Invoked By Engineer A Company X Knowledge
    This provision supports prohibiting Engineer A from leveraging specialized knowledge of Company X's submissions in a new role adverse to Company X.
Role (2)
  • Engineer A Confidentiality-Bound Government Agency Engineer
    Engineer A must not arrange new employment or practice using specialized knowledge gained about Company X's confidential designs from government agency work.
  • Company Y Competitor-Employing Private Engineering Company
    Company Y's engagement of Engineer A in work connected to projects where Engineer A gained specialized confidential knowledge implicates this provision.
Event (3)
  • Engineer Retained By Opposing Party (BER 82-6)
    This provision directly addresses arranging new employment with a party connected to a project where the engineer gained specialized knowledge.
  • Confidential Knowledge Accumulated
    Specialized and particular knowledge accumulated from a prior client cannot be used to arrange new employment on a related project without consent.
  • BER Precedent Framework Established
    The BER precedent framework addresses the conditions under which an engineer may or may not accept new employment based on prior specialized knowledge.
Resource (5)
  • Transitional_Employment_Ethics_Framework_Regulatory_Context
    III.4.a prohibits arranging new employment using specialized knowledge from a specific project, directly governing Engineer A's transition to Company Y.
  • Revolving_Door_Employment_Policy_Regulatory_Engineer
    The revolving door policy framework directly implicates III.4.a's prohibition on leveraging specialized government-acquired knowledge to arrange private employment.
  • BER Case No. 74-2
    BER Case No. 74-2 addresses part-time consultant arrangements relevant to the scope of III.4.a regarding new employment connected to specific project knowledge.
  • BER Case No. 82-6
    BER Case No. 82-6 establishes that an engineer cannot use government-acquired specialized knowledge to arrange subsequent employment adverse to that role, consistent with III.4.a.
  • Public_Official_Conflict_of_Interest_Standard_Regulatory_Access
    Engineer A's specialized regulatory access to competitor data is precisely the kind of particular knowledge III.4.a prohibits using to arrange new employment.
Capability (5)
  • Engineer A Post-Government-Employment Competitive Conflict Pre-Acceptance Assessment
    This provision requires Engineer A to assess whether accepting employment at Company Y involves specialized knowledge gained from government work on Company X matters.
  • Engineer A Revolving Door Conflict Recognition Government to Company Y
    This provision directly addresses the revolving door scenario where Engineer A gained specialized knowledge during government employment that now affects new employment.
  • Engineer A Permissible Competitive Employment Acceptance With Confidentiality Constraint Navigation
    This provision governs the conditions under which Engineer A may accept employment with Company Y given specialized knowledge gained from prior government access to Company X information.
  • Engineer A Adversarial Non-Participation Scope Determination at Company Y
    This provision requires identifying which assignments involve specialized knowledge gained from prior government work, informing the scope of non-participation at Company Y.
  • Company Y Competitor Firm Incumbent Information Advantage Non-Exploitation Organizational
    This provision requires consent of all interested parties before arranging employment that exploits specialized knowledge, obligating Company Y to avoid such exploitation.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 3 Lineage Graph

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

A part-time consultant arrangement to municipalities by engineers in private practice did not preclude those same engineers from providing normal engineering services to the same municipalities, where the engineer's loyalties were not divided.

Citation Context:

The Board cited this case to illustrate a situation where a part-time consultant arrangement did not create divided loyalties, contrasting with situations where confidentiality obligations may conflict.

Relevant Excerpts
discussion: "In BER Case No. 74-2 , the Board held that a part-time consultant arrangement to municipalities by engineers in private practice did not preclude those same engineers from providing normal engineering services to the same municipalities. The Board noted, under the facts, that the engineer's loyalties were not divided."

Principle Established:

An engineer who gains access to confidential information while working for one party retains an ethical obligation to protect that information even after the professional relationship ends, and cannot subsequently provide services to an adverse party who seeks to exploit that prior access.

Citation Context:

The Board cited this case extensively to establish that an engineer who gains access to confidential information from one party cannot subsequently work for an adverse party, even after the original relationship is terminated, because the duty of confidentiality and loyalty persists.

Relevant Excerpts
discussion: "In another BER case, Case No. 85-4 , Engineer A, a forensic engineer, was hired as a consultant by Attorney Z to provide an engineering and safety analysis report and courtroom testimony in support of a plaintiff in a personal injury case."
discussion: "In deciding that Engineer A's actions were not ethical, the Board noted that the mere fact that Engineer A ceased performing services for Attorney Z would not be an adequate solution to the ethical dilemma at hand."
discussion: "It may be argued that Engineer A's loyalties under the facts in BER Case No. 85-4 were not divided because he had terminated his relationship with the plaintiff's attorney."

Principle Established:

It is not ethical for an engineer retained by the US government to subsequently be retained by a contractor filing a claim against that same government without the former client's consent, per NSPE Code Section III.4.b.

Citation Context:

The Board cited this case to establish that an engineer retained by one client cannot ethically agree to represent an adverse party without the former client's consent, illustrating the duty of loyalty and confidentiality to former clients.

Relevant Excerpts
discussion: "In BER Case No. 82-6 , the Board ruled that where an engineer is retained by the US government to study the causes of a dam failure, it would not be ethical for the engineer to agree to be retained by the contractor involved in the construction of the dam."
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 46% Discussion Similarity 64% Provision Overlap 36% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: III.4, III.4.a, III.4.b, III.5 Same outcome True View Synthesis
Component Similarity 62% Facts Similarity 57% Discussion Similarity 73% Provision Overlap 40% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: III.4, III.4.a, III.4.b, III.5 Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 61% Discussion Similarity 59% Provision Overlap 55% Outcome Alignment 50% Tag Overlap 62%
Shared provisions: I.4, II.1.c, III.4, III.4.a, III.4.b, III.5 View Synthesis
Component Similarity 55% Facts Similarity 50% Discussion Similarity 71% Provision Overlap 36% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.4, II.1.c, III.4, III.5 Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 65% Discussion Similarity 54% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 57%
Shared provisions: II.1.c, III.4, III.5 Same outcome True View Synthesis
Component Similarity 57% Facts Similarity 56% Discussion Similarity 73% Provision Overlap 30% Outcome Alignment 100% Tag Overlap 44%
Shared provisions: III.4, III.4.a, III.4.b Same outcome True View Synthesis
Component Similarity 54% Facts Similarity 67% Discussion Similarity 74% Provision Overlap 27% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: III.4.a, III.4.b, III.5 Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 52% Discussion Similarity 74% Provision Overlap 30% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.4, II.1.c, III.4 Same outcome True View Synthesis
Component Similarity 51% Facts Similarity 39% Discussion Similarity 50% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.4, III.5 Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 70% Discussion Similarity 72% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 20%
Shared provisions: III.4, III.5 Same outcome True View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

What are Engineer A’s ethical obligations under these circumstances?

Board conclusion Engineer A is free to pursue employment with Company Y provided Engineer A does not disclose any confidential and proprietary design information Engineer A learned about Company X during Engineer A's employment with the government agency and makes this obligation clear to Company Y before accepting employment.
II.4. II.4.a. III.4. III.4.a.
Implicit (4)

Does Engineer A have an obligation to proactively recuse herself from any work at Company Y that directly involves Company X, even if Company Y never explicitly asks her to contribute such knowledge, and how should that recusal be structured and documented?

AnalyticalBeyond the Board's finding that Engineer A may join Company Y provided she withholds Company X's confidential information and discloses the conflict before accepting employment, the Board's conclusion is structurally incomplete because it addresses only the threshold moment of employment acceptance and not the ongoing conduct obligations that persist throughout Engineer A's tenure at Company Y. Engineer A's ethical duties do not terminate once she discloses the conflict and accepts the position; rather, they generate a continuing affirmative obligation to recuse herself from any project, assignment, or internal deliberation at Company Y that directly involves Company X's facility designs, regulatory submissions, or competitive positioning in domains where her government access gave her privileged structural knowledge. This recusal obligation should be documented formally - through written notice to Company Y's management and project assignment records - so that the boundary between permissible general expertise and impermissible use of confidential regulatory knowledge is institutionally traceable and not left to Engineer A's individual judgment alone. The absence of such a documented recusal mechanism creates a structural gap in the Board's otherwise sound conditional permission, because the risk of inadvertent or subconscious use of confidential knowledge is highest precisely in the ongoing work environment where competitive pressures are constant and the line between general expertise and privileged knowledge is difficult to police without formal procedures.
AnalyticalIn response to Q101, Engineer A's ethical obligations extend beyond merely refraining from active disclosure of Company X's confidential design information. A genuinely compliant posture requires Engineer A to proactively recuse herself from any assignment at Company Y that involves competing directly with Company X's approved or pending facility designs, particularly where her government-acquired structural knowledge of Company X's design approaches could - even subconsciously - inform her technical judgments. This recusal should be formalized in writing at the outset of employment, specifying the subject-matter domains from which Engineer A is excluded, and should be documented in a manner accessible to Company Y's project managers so that inadvertent assignment can be prevented. The recusal record also serves a protective function for Engineer A herself, creating a contemporaneous audit trail demonstrating good-faith compliance with her confidentiality obligations. Without such structural safeguards, the Board's conditional permission to accept employment risks becoming a nominal constraint that is practically unenforceable.

Is the Board's conclusion sufficient in only requiring disclosure to Company Y before accepting employment, or should Engineer A also be required to notify Company X that its confidential information is now held by an employee of a direct competitor?

AnalyticalThe Board's conclusion requires Engineer A to disclose her prior government access to Company Y before accepting employment, but it does not address whether Company X - the party whose proprietary information is most directly at risk - bears any right to notification or whether Engineer A or Company Y bears any corresponding duty to provide it. This omission is ethically significant. Under the faithful agent and trustee standard, Engineer A's confidentiality obligation runs not merely as a prohibition on disclosure but as an affirmative duty of trust toward the interests of those whose information she holds. Company X submitted its confidential design information to the government agency with a reasonable expectation that the regulatory process would protect it from competitive exploitation. That expectation is materially threatened when an engineer with direct access to those submissions transitions to a direct competitor. While the NSPE Code does not explicitly require notification to Company X, the principle that engineers shall not promote or arrange for new employment to the detriment of a client or employer - read in conjunction with the faithful agent standard - supports the conclusion that Engineer A should at minimum consider whether Company X's interests require some form of protective notice, particularly if Engineer A is assigned to work that directly competes with Company X's approved or pending facility designs. The Board's silence on this point leaves Company X without any procedural protection beyond Engineer A's individual conscience, which is an insufficient safeguard given the structural competitive asymmetry created by the employment transition.
AnalyticalIn response to Q102, the Board's conclusion is incomplete in limiting its disclosure requirement solely to Company Y. Because Company X is the party whose proprietary regulatory submissions are most directly at risk from Engineer A's transition to a direct competitor, basic principles of fairness and the faithful-agent obligation suggest that Company X also has a legitimate interest in knowing that an individual with access to its confidential design information has joined a competing firm. While the NSPE Code does not explicitly mandate notification to the originating company, the spirit of Section III.4 - which protects confidential information concerning the business affairs of clients - implies that Engineer A should at minimum consider whether Company X's consent or awareness is warranted. Notification to Company X would allow that company to assess whether any protective measures are necessary, such as seeking additional assurances or adjusting its ongoing regulatory submissions. The absence of a mandatory notification requirement in the Board's conclusion leaves a structural gap that could undermine the very confidentiality protections the Code is designed to enforce.

Given that the Board acknowledges the indeterminacy of the confidentiality obligation's duration, what mechanism or standard should govern when, if ever, Engineer A's duty to protect Company X's confidential design information expires, particularly as technology and competitive landscapes evolve?

AnalyticalThe Board acknowledges that the duration of Engineer A's confidentiality obligation is indeterminate but declines to establish any standard or mechanism for when, if ever, that obligation expires. This indeterminacy, left unresolved, creates a practical problem that undermines the workability of the Board's conditional permission over time. From a deontological perspective, the duty of trust that grounds Engineer A's confidentiality obligation does not automatically dissolve with the passage of time, because the obligation derives from the nature of the relationship and the act of entrusting - not from the continued commercial sensitivity of the information. However, from a consequentialist perspective, a perpetual and absolute confidentiality obligation that never accounts for changed circumstances - such as the public disclosure of Company X's facility design through regulatory approval, the obsolescence of the underlying technology, or Company X's own abandonment of the design - would impose career restrictions on Engineer A that are disproportionate to any remaining protective interest. A more analytically complete conclusion would hold that Engineer A's obligation persists as long as the information retains competitive or regulatory sensitivity that was not publicly disclosed through the approval process itself, and that the burden of demonstrating that sensitivity has lapsed falls on Engineer A before she may treat the information as freely usable. This standard preserves the protective purpose of the confidentiality obligation while providing Engineer A with a principled mechanism for assessing when her constraint has been lifted by changed circumstances rather than by the mere passage of time or her own convenience.
AnalyticalIn response to Q103, the Board's acknowledgment of the indeterminacy of the confidentiality obligation's duration is ethically significant but practically insufficient without a governing standard. A workable framework should assess expiration of the confidentiality duty against at least three criteria: first, whether the specific design information has entered the public domain through regulatory disclosure, publication, or independent development by third parties; second, whether the technology embodied in Company X's confidential submissions has been superseded to the point where the information no longer confers competitive advantage; and third, whether the passage of time, combined with material changes in the competitive landscape, renders the information commercially inert. Until all three conditions are satisfied, Engineer A's duty to protect Company X's confidential design information should be treated as continuing. This multi-factor standard is consistent with the perpetual confidentiality norm recognized in BER Case 85-4, while providing a principled mechanism for eventual expiration rather than imposing an indefinite and potentially unreasonable burden on Engineer A's professional mobility.

Does the government agency itself bear any ethical or institutional responsibility to establish formal revolving-door policies that protect the confidentiality of regulatory submissions, and does the absence of such a policy shift any moral burden onto Engineer A or Company Y?

AnalyticalThe Board's analysis does not address the systemic dimension of the revolving-door problem it implicitly resolves at the individual level. By permitting Engineer A's transition to Company Y subject only to individual confidentiality maintenance and pre-employment disclosure, the Board's conclusion, if generalized across the engineering profession, creates a structural incentive problem: government agencies that rely on confidential regulatory submissions from private companies will find that the value of those submissions as competitive intelligence makes their reviewing engineers attractive targets for competitor recruitment, and the individual confidentiality obligation - enforced only through professional ethics rather than institutional policy - is a weak safeguard against systematic erosion of regulatory integrity. The government agency itself bears an institutional responsibility, which the Board does not acknowledge, to establish formal revolving-door policies that restrict post-employment transitions to direct competitors of companies whose confidential submissions an engineer reviewed, at least for a defined cooling-off period. The absence of such a policy does not diminish Engineer A's individual ethical obligations, but it does mean that the ethical burden of protecting regulatory integrity is being borne entirely by individual engineers rather than by the institutional structures best positioned to enforce it. A complete ethical analysis would note that Engineer A's compliance with her individual obligations is necessary but not sufficient to protect the systemic integrity of the regulatory process, and that the Board's silence on institutional responsibility leaves a significant gap in the overall ethical framework governing government-to-private-sector transitions.
AnalyticalIn response to Q104, the government agency bears a distinct institutional responsibility to establish formal revolving-door policies governing engineers who have had access to confidential regulatory submissions. The absence of such policies does not diminish Engineer A's individual ethical obligations under the NSPE Code, but it does represent a systemic failure that increases the probability of inadvertent or deliberate misuse of confidential information across the broader population of government engineers transitioning to private practice. The moral burden is not transferred to Engineer A by the agency's omission - her duties under Sections II.4 and III.4 are independent of institutional policy - but the agency's failure to implement structural safeguards creates an environment in which compliance depends entirely on individual ethical judgment rather than enforceable institutional norms. Company Y also bears a derivative responsibility: knowing that Engineer A held government regulatory access, Company Y should not assign her to work that could exploit that access, regardless of whether any formal policy prohibits it.
Cross-cutting analytical questions (12)

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

Principle tension (4)

Does the Competitive Employment Freedom principle, which permits Engineer A to accept a position at Company Y, conflict with the Former Client Adversarial Participation Prohibition, which may effectively bar her from contributing to any work that competes directly with Company X, thereby rendering her employment value to Company Y structurally compromised?

AnalyticalIn response to Q201, the tension between Competitive Employment Freedom and the Former Client Adversarial Participation Prohibition is real and structural, not merely theoretical. While the Board correctly concludes that Engineer A may accept employment at Company Y, the practical scope of her permissible contributions at Company Y may be significantly constrained by the prohibition on participating in work that directly competes with or adversely affects Company X's interests using knowledge derived from regulatory access. If Company Y's primary business in the relevant facility design domain overlaps substantially with Company X's approved designs, Engineer A's effective utility to Company Y in that domain may be severely limited. This does not render the employment ethically impermissible, but it does mean that both Engineer A and Company Y must enter the employment relationship with clear-eyed awareness that her contribution scope will be bounded. The Board's conclusion permitting employment is therefore accurate but incomplete without acknowledging this structural limitation on Engineer A's role.
AnalyticalThe Board resolved the tension between Competitive Employment Freedom and the Confidentiality Obligation toward Company X's regulatory submissions not by subordinating one principle to the other, but by conditioning the former on strict compliance with the latter. This conditional resolution treats confidentiality as a threshold constraint rather than a competing value to be balanced: Engineer A retains the right to pursue private employment, but that right is structurally bounded by a non-negotiable duty to withhold Company X's proprietary design information. The practical effect is that Competitive Employment Freedom is preserved in form but significantly constrained in substance, because Engineer A's utility to Company Y in any work stream touching Company X's design domain is permanently diminished. This case teaches that when a principle rooted in public trust - here, the protection of confidential regulatory submissions - conflicts with a principle rooted in individual professional autonomy, the Board treats the public-trust principle as lexically prior: freedom of employment survives, but only in the space that remains after confidentiality obligations have been fully honored.

How does the Loyalty Obligation of Engineer A to Company Y within ethical limits conflict with the Faithful Agent Confidentiality Obligation grounding her duty to protect Company X's information, particularly when Company Y's competitive interests would be advanced by leveraging insights Engineer A gained through regulatory access?

AnalyticalThe interaction between the Faithful Agent Confidentiality Obligation and the Loyalty Obligation to Company Y within ethical limits reveals a structural asymmetry that the Board's conclusion leaves partially unresolved. As a faithful agent and trustee - first to the government agency and derivatively to Company X as a submitting party - Engineer A carries a confidentiality duty that predates and survives her relationship with Company Y. When these obligations collide, the faithful-agent duty to the prior principal functions as a hard ceiling on what Engineer A can legitimately offer Company Y. The Loyalty Obligation to Company Y is therefore not merely limited by ethics in the abstract; it is specifically and materially curtailed by the content of what Engineer A knows. This case teaches that loyalty to a current employer is always prospective and conditional, while confidentiality obligations to prior principals are retrospective and categorical. An engineer cannot discharge the former by simply intending not to disclose; she must actively structure her work at Company Y to ensure that the competitive intelligence value of her prior government access is never operationalized, even indirectly. The Board's conclusion gestures at this by requiring pre-employment disclosure, but does not fully articulate the ongoing affirmative conduct - including potential recusal from specific projects - that genuine reconciliation of these two principles demands.

Does the Conflict of Interest Disclosure Evolution Principle, which requires Engineer A to make her prior government access known to Company Y before accepting employment, tension with the Confidentiality Obligation toward Company X's regulatory submissions, insofar as the very act of disclosure to Company Y may reveal the nature or existence of Company X's proprietary information?

AnalyticalIn response to Q203, the Board's requirement that Engineer A disclose her prior government access to Company Y before accepting employment creates a genuine tension with her confidentiality obligation toward Company X. The very act of explaining the nature and scope of her access - necessary for Company Y to understand the conflict - risks revealing that Company X submitted confidential design information of a particular character, scope, or strategic significance. Engineer A must therefore calibrate her disclosure to Company Y with care: she should convey the existence and general subject-matter domain of her access without disclosing the substantive content, design details, or competitive implications of Company X's submissions. This calibrated disclosure approach is consistent with Section III.4.a, which requires consent of all interested parties before arranging employment that could disadvantage a former client. In practice, this means Engineer A's disclosure to Company Y should be framed in terms of the categories of information she cannot use, rather than the content of what she knows.

Does the Post-Public-Service Conflict Avoidance principle, which counsels Engineer A to avoid situations where her government access creates unfair competitive advantage, conflict with the Revolving Door Integrity principle, which is meant to preserve the ability of government engineers to transition to private practice without permanent career restriction, and how should the Board weigh these competing values when the confidential information is technical and long-lived?

AnalyticalIn response to Q204, the tension between Post-Public-Service Conflict Avoidance and Revolving Door Integrity is one of the most structurally difficult problems in engineering ethics for government-to-private transitions. The Board's resolution - permitting employment with a confidentiality constraint - represents a reasonable middle position, but it underweights the Post-Public-Service Conflict Avoidance principle when the confidential information is technical, long-lived, and directly relevant to the competitor's core business. Where the information Engineer A holds is not merely incidental but constitutes a sustained competitive advantage - as is plausible with facility design data that may remain valid for decades - the Revolving Door Integrity principle's goal of preserving career mobility must yield to a more robust application of conflict avoidance. In such cases, the ethical weight should shift toward requiring Engineer A to avoid not just active disclosure but any role at Company Y where her structural knowledge of Company X's design philosophy could influence project outcomes, even indirectly.
AnalyticalThe tension between the Post-Public-Service Conflict Avoidance principle and the Revolving Door Integrity principle exposes a deeper normative question the Board does not fully answer: how long must an engineer bear the competitive disadvantage imposed by prior government access to confidential information? The Board acknowledges the indeterminacy of the confidentiality obligation's duration - noting it persists without specifying when it ends - but declines to establish any mechanism for its expiration. This silence reflects an implicit prioritization of Regulatory Submission Confidentiality Protection over Revolving Door Integrity whenever the confidential information is technical and potentially long-lived. The case thus teaches that the revolving-door principle, while legitimate and important for sustaining a pipeline of experienced engineers between public and private sectors, cannot be invoked to erode confidentiality duties whose duration is tied to the competitive sensitivity of the underlying information rather than to the passage of calendar time. The ethical resolution is not a fixed time limit but a functional standard: Engineer A's confidentiality obligation persists as long as the design information she accessed retains competitive value in the marketplace - a standard that requires ongoing professional judgment rather than a one-time disclosure at the moment of employment transition. The absence of a formal revolving-door policy in the government agency's employment framework does not diminish this obligation; it merely shifts the burden of self-governance entirely onto Engineer A, reinforcing that ethical duties under the NSPE Code are independent of and supplementary to whatever contractual or regulatory mechanisms an employer has or has not established.
Theoretical (4)

From a deontological perspective, does Engineer A's duty as a faithful agent and trustee to the government agency create a categorical obligation to protect Company X's confidential design information that persists indefinitely after employment ends, regardless of whether disclosure would cause any measurable harm?

AnalyticalIn response to Q301, from a deontological perspective, Engineer A's duty as a faithful agent and trustee does generate a categorical obligation to protect Company X's confidential design information that is not contingent on demonstrable harm. The Kantian structure of the faithful-agent duty under Section II.4 treats the obligation of confidentiality as arising from the relationship of trust itself - the government agency's receipt of Company X's proprietary submissions created a duty of protection that Engineer A assumed by virtue of her role, independent of consequences. This means that even if disclosure would cause no measurable competitive harm to Company X - perhaps because the technology has been partially superseded - the categorical duty to refrain from using or disclosing the information persists until the information is genuinely in the public domain. The deontological analysis therefore supports a stricter reading of the confidentiality obligation than the Board's conclusion implies, one that does not permit Engineer A to rely on a harm-minimization calculus to justify reduced vigilance over time.

From a consequentialist perspective, does the Board's permissive conclusion - allowing Engineer A to join Company Y provided she withholds Company X's information - adequately account for the systemic harm to regulatory integrity if government engineers routinely transition to competitors with privileged knowledge of confidential submissions, even when individual disclosure is avoided?

AnalyticalIn response to Q302, from a consequentialist perspective, the Board's permissive conclusion is vulnerable to a systemic harm objection that individual-level analysis cannot fully address. If the ethical standard permits government engineers to transition to competitors of companies whose confidential submissions they reviewed - provided only that they personally refrain from disclosure - the aggregate effect across many such transitions may be a significant erosion of regulatory integrity. Companies submitting confidential design information to government agencies do so with an expectation that the information will be protected not merely from active disclosure but from the structural informational advantage that a knowledgeable former regulator brings to a competitor. A consequentialist analysis would require the Board to weigh not only the individual case but the rule-level effects of its conclusion: if the rule 'government engineers may join competitors with a confidentiality pledge' becomes standard practice, the chilling effect on candid regulatory submissions could undermine the quality of government oversight. The Board's conclusion is defensible at the individual level but requires supplementation with systemic safeguards - such as mandatory recusal protocols and agency-level revolving-door policies - to be consequentially sound.

From a virtue ethics perspective, does an engineer of genuine professional integrity merely refrain from disclosing confidential information, or does virtuous conduct require Engineer A to proactively recuse herself from any work at Company Y that could benefit from - even subconsciously - the structural knowledge of Company X's design approaches she accumulated during government service?

AnalyticalIn response to Q303, from a virtue ethics perspective, the standard of genuine professional integrity demands more than passive non-disclosure. An engineer of authentic virtue - one who has internalized the values of trustworthiness, fairness, and professional responsibility rather than merely complying with their letter - would recognize that the structural knowledge of Company X's design approaches accumulated during government service cannot be cleanly partitioned from her professional judgment. The virtue ethics tradition, which asks what a person of good character would do rather than what rules minimally require, supports proactive recusal from any work at Company Y that could benefit from this structural knowledge, even where the benefit would be subconscious or indirect. This is consistent with the capability identified as 'Engineer A Confidential Information Mental Segregation Impossibility Recognition' - the acknowledgment that cognitive compartmentalization of deeply internalized technical knowledge is not reliably achievable. Virtuous conduct therefore requires Engineer A to err on the side of broader recusal rather than narrower, accepting some limitation on her professional contribution as the price of genuine integrity.

From a deontological perspective, does Engineer A's obligation to disclose the conflict of interest to Company Y before accepting employment - as the Board requires - also entail a duty to disclose the same potential conflict to Company X, whose proprietary information is at risk, given that Company X is the party whose interests are most directly threatened by the employment transition?

AnalyticalIn response to Q304, from a deontological perspective, the duty to disclose a conflict of interest is not directionally limited to the party who benefits from the disclosure. If Engineer A's obligation to disclose to Company Y arises from the principle that parties affected by a conflict deserve notice - as grounded in Section II.4.a - then the same principle applies with equal or greater force to Company X, which is the party whose proprietary interests are most directly threatened. The deontological argument for disclosure to Company X is in fact stronger than for Company Y: Company Y is the beneficiary of Engineer A's expertise and can protect itself through contractual arrangements, whereas Company X is the vulnerable party with no contractual relationship with Engineer A and no independent means of learning about the transition. Failing to notify Company X treats that company merely as an object of the confidentiality obligation rather than as a rights-bearing party entitled to know that its information is now held by an employee of its direct competitor. The Board's silence on this point represents a gap in the deontological completeness of its analysis.
Counterfactual (4)

If Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and Company Y subsequently assigned her to a project directly competing with Company X's approved facility design, would the Board's analysis have shifted from a conditional permission to an outright prohibition - and what specific triggering threshold would mark that transition?

AnalyticalIn response to Q401, if Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and was subsequently assigned to a project directly competing with Company X's approved facility design, the Board's analysis would almost certainly shift from conditional permission to outright prohibition. The triggering threshold for that transition involves two compounding violations: first, the failure to disclose the conflict of interest to Company Y before accepting employment, which violates Section II.4.a independently; and second, the active participation in work that could exploit or be informed by Company X's confidential submissions, which violates Section III.4. The combination of non-disclosure and adversarial assignment would constitute a complete breach of Engineer A's ethical obligations, not merely a procedural deficiency. The specific threshold is therefore not a single act but the conjunction of concealment at hiring and subsequent assignment to conflicted work - either element alone might be remediable, but together they would place Engineer A in a position of irredeemable ethical violation under the NSPE Code.

What if the government agency had included an explicit revolving-door clause in Engineer A's employment contract prohibiting post-employment work for competitors of companies whose confidential submissions she reviewed - would Engineer A's ethical obligations under the NSPE Code have been strengthened, weakened, or simply made more legally enforceable, and does the absence of such a clause diminish her ethical duties?

AnalyticalIn response to Q402, the presence of an explicit revolving-door clause in Engineer A's government employment contract would not strengthen her underlying ethical obligations under the NSPE Code - those obligations exist independently of contractual provisions - but it would make them legally enforceable and would remove any ambiguity about their scope and duration. Conversely, the absence of such a clause does not diminish Engineer A's ethical duties: the NSPE Code's confidentiality and conflict-of-interest provisions operate as professional ethical standards that bind Engineer A regardless of what her employment contract does or does not specify. The practical effect of a contractual clause would be to align legal and ethical obligations, reducing the risk that Engineer A might rationalize reduced vigilance on the grounds that no formal prohibition exists. The absence of such a clause therefore represents an institutional gap - attributable to the government agency - that increases reliance on Engineer A's individual ethical judgment but does not alter the substance of what that judgment requires.

If, analogous to BER Case 85-4, Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked by Company Y to provide technical analysis drawing on her general expertise in the relevant facility design domain - without explicitly referencing Company X's confidential submissions - would the switching-sides prohibition recognized in BER Case 85-4 apply, and would Engineer A's claimed ignorance of the conflict serve as any mitigation?

AnalyticalThe Board's conditional permission for Engineer A to join Company Y does not adequately address the scenario - raised by analogy to BER Case 85-4 - in which Company Y later becomes involved in an adversarial regulatory or legal proceeding against Company X and Engineer A is asked to contribute technical analysis drawing on her domain expertise. In BER Case 85-4, the Board held that an engineer who had provided confidential information to one party in a proceeding could not ethically accept retention by the opposing party, and that claimed naivety about the conflict did not serve as mitigation. Applied to the current case, this precedent implies that if Company X and Company Y become adversaries in any regulatory, contractual, or legal proceeding involving the facility design domain in which Engineer A holds Company X's confidential information, Engineer A would be categorically barred from contributing to Company Y's position in that proceeding - regardless of whether she explicitly references Company X's confidential submissions or claims to rely only on general expertise. The structural knowledge she accumulated through regulatory access creates a conflict that cannot be neutralized by mental segregation alone. The Board's conclusion should have explicitly flagged this downstream adversarial participation risk as a constraint on Engineer A's permissible scope of work at Company Y, rather than leaving it to be inferred from prior BER precedent. Company Y should also be made aware of this constraint at the time of Engineer A's pre-employment disclosure, because it materially affects the range of assignments Engineer A can ethically accept.
AnalyticalIn response to Q403, if Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked to provide technical analysis drawing on her general expertise - without explicitly referencing Company X's confidential submissions - the switching-sides prohibition recognized in BER Case 85-4 would apply with substantial force. The critical insight from BER Case 85-4 is that the prohibition is not limited to cases where the engineer explicitly uses confidential information; it extends to situations where the engineer's prior access creates an appearance of impropriety or a structural conflict that cannot be neutralized by claimed ignorance of the connection. Engineer A's claimed ignorance that her general expertise was informed by her government-acquired knowledge of Company X's design approaches would provide no meaningful mitigation, consistent with the principle that naivety does not exculpate - as reflected in the constraint 'Engineer A Naivety Non-Exculpation - BER Case 85-4.' The adversarial context would trigger a categorical bar on Engineer A's participation, regardless of whether she consciously drew on Company X's confidential submissions.

What if Company Y had specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies - making the competitive intelligence value of her access an explicit factor in the hiring decision - would the Board's conclusion permitting the employment transition still hold, and what additional obligations would arise for both Engineer A and Company Y under the NSPE Code?

AnalyticalThe Board's conclusion implicitly assumes that the competitive intelligence value of Engineer A's government access is incidental to Company Y's hiring decision, but it does not address the ethically distinct scenario in which Company Y recruits Engineer A specifically because of her knowledge of Company X's design strategies. If Company Y's hiring motivation is explicitly or primarily the competitive intelligence value of Engineer A's regulatory access - rather than her general engineering expertise - then the employment transition is not merely a permissible revolving-door situation subject to confidentiality constraints, but a structured attempt to exploit the regulatory process for competitive advantage. In that scenario, both Engineer A and Company Y would bear heightened ethical obligations: Engineer A would be obligated to decline the position or, at minimum, to make explicit to Company Y that she cannot and will not provide any information derived from her government access, and Company Y would be obligated under the faithful agent and conflict of interest avoidance principles to refrain from assigning Engineer A to any work where her prior access could provide competitive advantage over Company X. The Board's silence on the motivational dimension of the hiring decision leaves open a significant ethical gap, because the same employment transition that is conditionally permissible when motivated by legitimate expertise recruitment becomes ethically impermissible when motivated by the desire to acquire competitive intelligence through the back channel of a former government reviewer.
AnalyticalIn response to Q404, if Company Y specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies - making competitive intelligence an explicit factor in the hiring decision - the Board's conditional permission to accept employment would not hold. This scenario transforms the employment transition from a permissible career move with incidental confidentiality obligations into a deliberate scheme to exploit confidential regulatory submissions for competitive advantage, which is precisely what Sections III.4 and III.4.a are designed to prevent. Under these circumstances, Engineer A would be ethically prohibited from accepting the position, because doing so would make her a willing instrument of the misappropriation of Company X's confidential information, regardless of whether she personally disclosed any specific design details. Company Y would bear independent ethical culpability for structuring a recruitment strategy around the exploitation of confidential government-access information. Both parties would be in violation of the NSPE Code, and Engineer A's obligation would be to decline the offer and, if appropriate, report the circumstances to the relevant professional or regulatory authorities.
Decisions & Arguments (6)
View Extraction

Should Engineer A accept employment at Company Y, and if so, what obligations must she fulfill before accepting?

Options considered:
O1 Accept the position at Company Y after proactively disclosing to Company Y, before acceptance, the nature, subject-matter domain, and scope of Engineer A's prior access to Company X's confidential regulatory submissions, framed in terms of what categories of information she cannot use rather than the substantive content of what she knows Board's choice
O2 Decline the position at Company Y entirely on the grounds that the competitive relationship between Company Y and Company X, combined with the depth and technical specificity of Engineer A's regulatory access, creates a conflict of interest too substantial to be managed through disclosure and confidentiality maintenance alone
O3 Accept the position at Company Y and disclose the prior government access only if Company Y directly assigns Engineer A to work involving Company X's facility designs, treating the conflict as a matter to be managed reactively through project-level recusal rather than proactively through pre-employment disclosure
Argument structure:
Warrants

The Post-Public-Service Competitor Employment Conflict Avoidance Obligation counsels that the revolving door from regulatory access to competitive employment creates inherent conflicts that cannot be managed through disclosure alone. Competing against this, the Competitive Employment Freedom principle holds that engineers are not unduly penalized for accepting positions with competitors of former clients, provided they do not disclose or use confidential information. The Conflict of Interest Disclosure to New Private Employer obligation requires that Engineer A inform Company Y of the nature and extent of her prior access before accepting.

Rebuttals

Uncertainty arises because the absence of a formal revolving-door provision in Engineer A's government employment contract leaves unclear whether the conflict is severe enough to preclude acceptance entirely or merely requires disclosure and ongoing confidentiality maintenance. The indeterminate duration of the confidentiality obligation further complicates whether the conflict is manageable or categorical.

Grounds

Engineer A worked for a government agency that received confidential and proprietary design information from Company X as part of a regulatory approval process. Engineer A accumulated direct knowledge of Company X's confidential submissions. Engineer A then resigned from the agency and was offered an engineering position at Company Y, a direct competitor of Company X.

Post-Public-Service Competitor Employment Conflict Avoidance Obligation Competitive Employment Freedom With Confidentiality Constraint

Does Engineer A's confidentiality obligation require only passive non-disclosure of Company X's information, or does it also require proactive recusal from assignments at Company Y where her structural knowledge could, even subconsciously, inform her technical judgments?

Options considered:
O1 Formalize recusal in writing at the outset of employment, specifying the subject-matter domains from which Engineer A is excluded due to prior government access, and provide that documentation to Company Y's project managers so that inadvertent assignment to conflicted work is structurally prevented Board's choice
O2 Refrain from actively disclosing or referencing Company X's confidential submissions in any work product or internal deliberation, relying on Engineer A's individual professional judgment to police the boundary between general expertise and privileged knowledge on a case-by-case basis without formal written recusal
O3 Recuse from assignments that explicitly reference or directly replicate Company X's approved facility designs, while participating in general domain work in the same technical area on the grounds that general expertise in the field is legitimately deployable and broader recusal would impose disproportionate career restriction
Argument structure:
Warrants

The Post-Public-Employment Confidential Information Non-Use Obligation prohibits Engineer A from using, disclosing, or exploiting Company X's confidential information in any form. The Confidential Information Mental Segregation Impossibility Recognition Capability, grounded in BER Case 85-4, establishes that once an engineer has been exposed to confidential information, it is not realistically possible to mentally segregate that knowledge when performing work for a competing party. The Competitive Employment Freedom principle, however, holds that Engineer A should not be unduly penalized and that her general engineering expertise remains legitimately deployable.

Rebuttals

Uncertainty arises because the boundary between Engineer A's general engineering expertise and her government-acquired structural knowledge of Company X's specific design approaches is practically indeterminate. If the recusal obligation extends to all competitive work touching Company X's technical domain rather than only direct adversarial assignments, Engineer A's effective utility to Company Y may be severely and disproportionately constrained.

Grounds

Engineer A has accepted employment at Company Y and holds structural knowledge of Company X's confidential facility design submissions acquired through government regulatory review. Company Y operates in the same facility design domain as Company X and may assign Engineer A to projects that directly or indirectly compete with Company X's approved designs. Engineer A cannot reliably partition her accumulated technical knowledge from her professional judgment in this domain.

Post-Public-Employment Confidential Information Non-Use Obligation Confidential Information Mental Segregation Impossibility Recognition Capability

Should Engineer A disclose her conflict only to Company Y before accepting employment, or must she also notify Company X that its confidential regulatory submission data is now held by an employee of a direct competitor?

Options considered:
O1 Before accepting employment, disclose to Company Y the existence, subject-matter domain, and general scope of Engineer A's prior access to Company X's confidential regulatory submissions, framed in terms of what conflict-management measures Company Y should implement. No affirmative notification is made to Company X. Board's choice
O2 Before accepting employment, notify both Company Y and Company X that Engineer A holds Company X's confidential regulatory submission data and is transitioning to a direct competitor, giving each party the opportunity to implement protective measures or object to the transition.
O3 Treat the confidentiality obligation to Company X as the dominant duty and notify Company X first, before or instead of disclosing to Company Y, on the grounds that Company X's proprietary regulatory data is the asset most directly threatened by the employment transition.
Argument structure:
Warrants

The Conflict of Interest Disclosure obligation requires Engineer A to notify Company Y before accepting employment so that Company Y can implement conflict management measures. The Regulatory Submission Confidentiality Protection Obligation and the faithful-agent standard under II.4 create an affirmative duty of trust running toward Company X as the submitting party, not merely a prohibition on disclosure. The Former Client Confidentiality Perpetuation Obligation establishes that the duty of trust toward Company X survives the termination of Engineer A's government employment. The tension arises because the very act of disclosing to Company Y the nature and scope of Engineer A's access may itself reveal information about Company X's submissions.

Rebuttals

Uncertainty is created by the absence of any established NSPE Code provision explicitly requiring reverse notification to the original submitter of confidential information when a government engineer transitions to a competitor. Additionally, notifying Company X risks revealing the existence and character of Engineer A's access in ways that could themselves constitute a confidentiality breach or trigger adverse competitive responses by Company X.

Grounds

Engineer A holds Company X's confidential regulatory submission data and is transitioning to Company Y, a direct competitor of Company X. Company X submitted its proprietary design information to the government agency with a reasonable expectation that the regulatory process would protect it from competitive exploitation. Company X has no contractual relationship with Engineer A and no independent means of learning about her employment transition.

Conflict of Interest Disclosure to New Private Employer Regarding Prior Government Access Obligation Former Client Confidentiality Perpetuation Obligation

How should Engineer A assess the duration of her confidentiality obligation toward Company X's design information, and by what standard, if any, may she treat that obligation as having expired?

Options considered:
O1 Treat the confidentiality obligation as continuing indefinitely until Engineer A can affirmatively demonstrate: against a multi-factor standard assessing public domain entry, technological supersession, and commercial inertness, that Company X's design information no longer retains competitive sensitivity, placing the burden of proof on Engineer A rather than on the passage of time Board's choice
O2 Treat the confidentiality obligation as expiring after a defined cooling-off period, calibrated to the typical competitive lifecycle of facility design information in the relevant industry, after which Engineer A may exercise professional judgment about whether specific information retains sensitivity without bearing a formal burden of proof
O3 Treat the confidentiality obligation as coextensive with the period during which Company X's approved facility design remains operationally active and commercially relevant, after which the information may be treated as part of Engineer A's general professional knowledge base without further restriction
Argument structure:
Warrants

The Post-Employment Duty of Trust and Loyalty Duration Indeterminacy Constraint establishes that the confidentiality obligation persists for an indeterminate period after the professional relationship ends and cannot be discharged by the mere passage of time. The Confidentiality Duration Indeterminacy Principle holds that duration must be assessed contextually based on the nature of the information and the potential for harm. Competing against perpetual obligation, the Competitive Employment Freedom principle implies that indefinite career restriction disproportionate to any remaining protective interest is not ethically required. A deontological reading treats the duty as categorical and non-contingent on harm; a consequentialist reading would permit expiration when the information loses competitive sensitivity.

Rebuttals

Uncertainty is created by the absence of any agreed standard for measuring when design information loses competitive sensitivity, by the possibility that information considered obsolete by one metric retains value by another, and by the difficulty of distinguishing between information that has entered the public domain through regulatory approval and information that remains proprietary despite partial disclosure.

Grounds

Engineer A accumulated confidential and proprietary design information about Company X's facility designs during government regulatory employment. The Board acknowledges that the duration of the confidentiality obligation is indeterminate but declines to specify when it ends. Company X's facility design information may retain competitive sensitivity for an extended and uncertain period, particularly given the long operational lifecycles of the relevant facilities. The NSPE Code does not establish a fixed expiration for post-employment confidentiality duties.

Post-Employment Duty of Trust and Loyalty Duration Indeterminacy Constraint Confidentiality Duration Indeterminacy Principle

If Company X and Company Y become adversaries in a regulatory or legal proceeding, is Engineer A categorically barred from contributing technical analysis on Company Y's behalf, even analysis she characterizes as drawing only on general expertise, given her prior government access to Company X's confidential submissions?

Options considered:
O1 Recuse categorically from any technical contribution to Company Y's position in any adversarial regulatory or legal proceeding involving Company X, regardless of whether the contribution is characterized as drawing on general expertise rather than Company X's specific confidential submissions, and notify Company Y of this constraint at the outset of employment Board's choice
O2 Participate in Company Y's adversarial proceedings against Company X in a limited advisory capacity, reviewing general technical arguments without authoring expert opinions, on the grounds that passive review of publicly available information does not constitute the active switching-sides conduct prohibited by BER Case 85-4
O3 Participate in Company Y's adversarial proceedings against Company X only in domains where Engineer A can affirmatively demonstrate, through documented analysis, that her contribution draws exclusively on publicly available information and general engineering principles with no overlap with the specific design domains covered by Company X's confidential regulatory submissions
Argument structure:
Warrants

The Former Client Adversarial Participation Prohibition, grounded in BER Case 85-4, bars Engineer A from switching sides in any proceeding where her prior access to Company X's confidential information creates a structural conflict, regardless of whether she explicitly uses that information. The Confidential Information Mental Segregation Impossibility Recognition Capability establishes that cognitive compartmentalization of deeply internalized technical knowledge is not reliably achievable. The Loyalty Obligation to Company Y within ethical limits creates pressure to contribute to Company Y's position in adversarial proceedings, but that obligation is bounded by the categorical bar on adversarial participation against Company X.

Rebuttals

Uncertainty arises because the rebuttal condition, that Engineer A's analysis draws only on general expertise without referencing Company X's confidential submissions, is practically unverifiable given the impossibility of mental segregation. The scope of the adversarial participation prohibition is also indeterminate: if it extends to all technical work in the facility design domain rather than only direct adversarial testimony, Engineer A's effective utility to Company Y in any contested regulatory context may be categorically foreclosed.

Grounds

Engineer A holds structural knowledge of Company X's confidential facility design submissions. Company Y is a direct competitor of Company X. BER Case 85-4 established that an engineer who provided confidential information to one party in an adversarial proceeding cannot ethically accept retention by the opposing party, and that claimed naivety about the conflict does not serve as mitigation. If Company X and Company Y become adversaries in a regulatory or legal proceeding, Engineer A may be asked to contribute technical analysis drawing on her domain expertise without explicitly referencing Company X's confidential submissions.

Former Client Adversarial Participation Prohibition Invoked By Engineer A Company X Knowledge Confidential Information Mental Segregation Impossibility Recognition Capability

Does the ethical permissibility of Engineer A accepting employment at Company Y depend on Company Y's hiring motivation, specifically, whether Company Y recruited Engineer A primarily for her general expertise or primarily for the competitive intelligence value of her government-acquired knowledge of Company X's design strategies?

Options considered:
O1 Decline the position at Company Y if Engineer A has reasonable grounds to believe that the competitive intelligence value of her government-acquired knowledge of Company X's design strategies was a primary or explicit factor in Company Y's hiring decision, treating the motivational dimension of the recruitment as a threshold condition that transforms an otherwise permissible transition into an ethically impermissible one Board's choice
O2 Accept the position at Company Y regardless of hiring motivation, on the grounds that Engineer A's individual confidentiality maintenance obligation is the operative ethical constraint and that Company Y's internal motivations, which Engineer A cannot fully verify or control, do not alter the substance of what Engineer A is personally required to do or refrain from doing
O3 Accept the position at Company Y but require Company Y to provide written confirmation, before acceptance, that Engineer A's engagement is predicated on her general engineering expertise and that no assignment will be made that exploits her prior regulatory access to Company X's submissions, treating this written assurance as a necessary condition for the employment transition to remain ethically permissible
Argument structure:
Warrants

The Post-Public-Service Competitor Employment Conflict Avoidance Obligation holds that the revolving door from regulatory access to competitive employment creates conflicts that cannot be managed through disclosure alone when the confidential information is directly relevant to the competitive relationship. The Regulatory Submission Confidentiality Protection Obligation prohibits use of confidential regulatory submissions for competitive advantage. The Competitive Employment Freedom principle permits Engineer A to accept private employment, but only where the hiring motivation is legitimate expertise recruitment rather than competitive intelligence acquisition. When hiring motivation is explicitly the latter, both Engineer A and Company Y bear independent ethical culpability.

Rebuttals

Uncertainty arises because hiring motivation is rarely explicit and is difficult to verify from Engineer A's perspective alone. The rebuttal condition that would preserve the Board's permissive conclusion, that Engineer A's personal confidentiality maintenance is sufficient to neutralize Company Y's competitive intelligence motivation, is undermined when the structural knowledge Engineer A carries provides competitive advantage even without explicit disclosure.

Grounds

Engineer A is offered a position at Company Y, a direct competitor of Company X. The Board's baseline conclusion permits the employment transition subject to confidentiality maintenance and pre-employment disclosure. However, the Board does not address the scenario in which Company Y's hiring decision is explicitly motivated by the competitive intelligence value of Engineer A's government-acquired knowledge of Company X's design strategies, rather than by her general engineering qualifications. If Company Y recruited Engineer A specifically to exploit her regulatory access, the employment transition may constitute a structured attempt to misappropriate Company X's confidential submissions through the back channel of a former government reviewer.

Post-Public-Service Competitor Employment Conflict Avoidance Obligation Regulatory Submission Confidentiality Protection Obligation
Event Timeline (13)
13 sequenced 7 actions 6 events
Case timeline
Through a series of Board of Ethical Review decisions from 1974 through 1985 and beyond, a body of precedent addressing confidentiality and conflicts of interest in engineering practice comes into existence. This historical accumulation of decisions constitutes an exogenous contextual event that shapes the normative framework applicable to Engineer A's situation.
In the referenced BER Case 82-6, an engineer who had previously been retained by one party in a dispute is subsequently retained by the opposing party. This event, the retention by the opposing party, is an outcome that creates a direct conflict of interest and serves as a precedential analog to Engineer A's situation.
In the historical reference case BER 82-6, an engineer retained by the US government to study a dam failure accepted a subsequent retention by the contractor who had filed a claim against the government for additional compensation. The BER deemed this decision unethical.
Violates (3)
  • NSPE Code Section III.4.b, obligation not to accept employment adverse to former client without consent
  • Duty of faithful agency and trusteeship to former government client
  • Obligation to avoid conflicts of interest arising from prior professional relationships
In the historical reference case BER 85-4, the forensic engineer decided he could not provide an engineering and safety analysis report favorable to the plaintiff after completing his review and analysis, because the results indicated the plaintiff rather than the defendant was at fault.
Fulfills (3)
  • Obligation to provide honest and objective engineering analysis
  • Duty not to misrepresent engineering findings
  • Integrity in professional conduct
In the referenced BER Case 85-4, after Engineer A (the forensic engineer in that case) declines to produce a favorable report for the plaintiff, the opportunity to serve as the plaintiff's expert is effectively foreclosed. This is an outcome, the closing off of one professional path, that leads to the subsequent retention by the defendant's attorney.
In the historical reference case BER 85-4, after being terminated by the plaintiff's attorney, the forensic engineer agreed to provide a separate and independent engineering and safety analysis report for the defendant's attorney in the same case. The BER deemed this decision unethical.
Violates (5)
  • NSPE Code Section II.4.b, obligation to avoid conflicts of interest
  • Residual confidentiality obligation to former client (plaintiff's attorney)
  • Duty not to exploit information gained in confidence during prior engagement
  • Obligation to avoid circumstances that could appear to improperly influence professional judgment
  • Duty to fully discuss the ethical conflict with the former client before proceeding
Engineer A actively receives and handles confidential and proprietary design information submitted by Company X and other companies during her tenure at the government agency. This represents an ongoing, role-sanctioned decision to engage with sensitive third-party information in her official regulatory capacity.
Fulfills (3)
  • Duty to perform official government agency responsibilities
  • Duty to serve as faithful agent and trustee to the regulatory body
  • Duty to facilitate fair regulatory review of all submitting companies
Through repeated exposure to proprietary design submissions from Company X and other firms, Engineer A accumulates a body of sensitive technical knowledge. This accumulation is an emergent outcome of her routine regulatory duties rather than a discrete volitional act.
Engineer A voluntarily ends her employment with the government agency, a deliberate career decision that activates and crystallizes her post-employment ethical obligations regarding the confidential information she accumulated during her tenure.
Fulfills (1)
  • Right to professional mobility and freedom of employment
Engineer A makes the affirmative decision to accept an engineering position with Company Y, knowing it is a direct competitor of Company X, whose confidential and proprietary design information she accessed during her government tenure. This is the central ethical decision of the case.
Fulfills (2)
  • Legitimate exercise of professional mobility rights
  • Pursuit of career advancement consistent with engineering competence
Upon Engineer A accepting a position at Company Y, a direct competitor of Company X, a conflict of interest situation comes into existence as an automatic consequence of the employment transition. This is not a decision but the structural outcome of two facts coinciding: Engineer A's confidential knowledge and her new competitive employment context.
As a consequence of Engineer A's resignation and entry into competitive employment, her pre-existing confidentiality obligations, previously somewhat abstract, become concretely and urgently operative. The obligation does not newly arise but is triggered into active, high-stakes relevance by the changed employment context.
Engineer A must make continuous, ongoing decisions throughout her employment at Company Y not to disclose the confidential and proprietary design information she learned about Company X during her government tenure. This is framed by the BER as the primary and non-negotiable ethical obligation arising from the case.
Fulfills (3)
  • NSPE Code obligation not to disclose confidential information about former clients or employers without consent
  • Duty to serve as faithful agent and trustee respecting the trust placed in her by Company X through the regulatory process
  • Obligation to avoid conduct that could appear to improperly influence professional judgment
Violates (1)
  • Potential partial limitation of full faithful agency to new employer Company Y if withholding creates gaps in her contributions
No narrative data available. Run Phase 4 (Narrative Construction) on the Step 4 page first.

© Licensed under the GNU GPL v3 | Report Issue