Step 4: Full View

Entities, provisions, decisions, and narrative

Conflict Of Interest—Public Employee Serving As Part-Time Consultant
Step 4 of 5

265

Entities

4

Provisions

1

Precedents

17

Questions

25

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
Engineer A is caught between two simultaneously valid but mutually defeating obligation sets: (1) the NSPE Code Section II.4 Faithful Agent Trustee duty owed to the State DOT, which prohibits any private conduct that creates divided loyalty toward the municipal stakeholders the DOT funds and regulates, and (2) the Section III.6.b Moonlighting Contextual Assessment permission and Competitive Employment Freedom, which recognizes a licensed engineer's legitimate interest in private professional work. The Board's resolution does not transfer the ethical burden to another party, nor does it sequence the obligations temporally — it finds that no procedural mechanism (disclosure, recusal, employer approval, domain separation) can collapse the stalemate, and therefore issues a categorical prohibition. The tension between the two obligation sets remains analytically present and unresolved in the framework; the Board escapes the stalemate only by declaring one obligation lexically prior rather than by dissolving the competing duty.
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 32)
Obligation
Engineer A Faithful Agent Trustee DOT Employer Structural Conflict
This provision directly requires engineers to act as faithful agents or trustees, which is the core obligation Engineer A owed to the State DOT employer.
Action
Reviewing Private Firm Contracts
Engineers must act as faithful agents, which governs how they handle reviewing contracts where dual employment creates loyalty obligations to both employers.
State
Engineer A Adjacent Domain Dual Employment Conflict. Highways vs. Airports
Engineer A must act as a faithful agent to both employers, which is directly challenged by his dual roles in adjacent infrastructure domains.
Obligation (5)
  • Engineer A Faithful Agent Trustee DOT Employer Structural Conflict
    This provision directly requires engineers to act as faithful agents or trustees, which is the core obligation Engineer A owed to the State DOT employer.
  • Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary
    This provision directly mandates faithful agent loyalty to the employer, which is the basis for limiting private consulting that compromises DOT interests.
  • Engineer A Employer Awareness Non-Sufficiency Structural Conflict DOT Airport
    This provision establishes the faithful agent duty that persists even when both employers are aware, supporting the obligation to decline the engagement.
  • Engineer A Cross-Domain Same-Client DOT Highway Airport Municipal Conflict
    This provision requires faithful agency to the DOT employer, which is undermined by accepting private work for the same municipal clients Engineer A reviews for DOT.
  • Cross-Domain Same-Client Conflict Non-Engagement Engineer A Municipal Airport Consulting
    This provision requires acting as a faithful agent, which is violated by accepting consulting work for the same municipal clients served through DOT employment.
Action (2)
  • Reviewing Private Firm Contracts
    Engineers must act as faithful agents, which governs how they handle reviewing contracts where dual employment creates loyalty obligations to both employers.
  • Monitoring and Addressing Emerging Conflicts
    Acting as a faithful agent requires ongoing vigilance to ensure neither employer's interests are compromised by the dual role.
State (3)
  • Engineer A Adjacent Domain Dual Employment Conflict. Highways vs. Airports
    Engineer A must act as a faithful agent to both employers, which is directly challenged by his dual roles in adjacent infrastructure domains.
  • Engineer A Shared Municipal Stakeholder Dual Role Conflict
    Serving the same municipalities in both a state DOT capacity and as a private consultant undermines Engineer A's ability to act as a faithful agent to each employer.
  • Engineer A Employer-Aware Dual Employment Insufficient Mitigation
    Employer awareness alone does not fulfill the faithful agent obligation, as the Board finds the dual role still compromises Engineer A's loyalty to each employer.
Constraint (4)
  • Former Employer Re-Engagement Government Position Faithful Agent Non-Compromise Engineer A
    II.4 requires Engineers to act as faithful agents, directly creating the constraint that prior employment with the firm does not entitle re-engagement without compromising that duty.
  • Engineer A Employer Non-Objection Insufficient Faithful Agent DOT Airport
    II.4 establishes the faithful agent duty that persists even when employers do not object, making mutual non-objection insufficient to satisfy ethical obligations.
  • Dual Public-Private Role Interrelated Domain Conflict Engineer A DOT Airport Consulting
    II.4 requires faithful agency to each employer, which is violated when Engineer A holds conflicting public and private roles serving the same municipalities.
  • Engineer A Dual Public-Private Interrelated Domain Conflict DOT Highway Airport
    II.4 creates the obligation to act as a faithful agent that is undermined by simultaneously holding interrelated public and private roles.
Principle (4)
  • Faithful Agent Obligation Invoked for Engineer A State DOT Loyalty
    This provision directly establishes the faithful agent duty that Engineer A owes to the State DOT as employer.
  • Faithful Agent Trustee Obligation Violated by Structural Conflict
    The BER grounded its ethical violation finding in this exact provision requiring faithful agent and trustee service to the employer.
  • Dual-Role Public-Private Conflict Invoked for Engineer A Airport Consulting
    Engineer A's simultaneous public and private roles undermine his ability to act as a faithful agent to the State DOT.
  • Employer Awareness Non-Sufficient to Cure Structural Conflict in Engineer A Case
    The faithful agent obligation persists structurally even when the employer is aware of the outside work, as this provision imposes an ongoing duty.
Role (3)
  • Engineer A State DOT Traffic Engineer
    Engineer A must act as a faithful agent to the State DOT while reviewing plans, requiring undivided loyalty in his primary role.
  • Engineer A State DOT Airport Consultant
    Engineer A must act as a faithful agent to both the State DOT and any municipal clients if he accepts the part-time consulting role.
  • Case 97-1 Engineer A Dual-Role Government-Private Engineer
    The precedent engineer's dual-role situation directly implicated the faithful agent obligation to both government and private employers.
Event (2)
  • Dual Role Conflict Condition Crystallized
    The duty to act as a faithful agent is directly implicated when the engineer simultaneously holds roles creating competing loyalties.
  • Former Firm Re-Engagement Approach Occurs
    Re-engaging with a former firm while employed by DOT tests whether the engineer is acting faithfully toward the current employer.
Resource (4)
  • Agent-Trustee-Loyalty-Obligation-Standard
    This provision directly establishes the faithful agent and trustee obligation that the Board invokes as the normative basis for finding an ethical violation.
  • Dual-Public-Private-Employment-Ethics-Standard
    This provision governs Engineer A's loyalty obligations to both his public DOT employer and any private consulting client simultaneously.
  • NSPE-Code-of-Ethics
    This provision is part of the NSPE Code of Ethics governing Engineer A's obligations as a licensed engineer in dual employment.
  • NSPE-Code-of-Ethics-General
    This provision is the primary normative authority invoked to evaluate Engineer A's dual employment loyalty obligations.
Capability (5)
  • Dual-Role Faithful Agent Breach Self-Recognition Engineer A DOT Airport Consulting
    This provision requires faithful agency, directly addressed by the capability to recognize that dual employment would breach that duty.
  • Engineer A Dual-Role Faithful Agent Breach Self-Recognition DOT Airport Municipal Clients
    This provision requires acting as a faithful agent, which this capability addresses by recognizing the breach of that duty toward both employers.
  • Engineer A Dual Employment Professional Liability Risk Awareness DOT Airport
    Acting as a faithful agent requires awareness of adverse effects the dual arrangement could have on the quality of services rendered.
  • Cross-Domain Shared-Client Government-Private Conflict Boundary Recognition Engineer A Municipal Overlap
    Faithful agency to the State DOT is undermined by the shared municipal client relationship this capability requires recognizing.
  • Governmental Employee Private Consulting Domain Overlap Conflict Recognition Engineer A Airport Traffic
    Faithful agency is directly implicated when the private consulting domain overlaps with governmental responsibilities, as this capability addresses.
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 56)
Obligation
State DOT Employer Prior Approval Disclosure Engineer A Airport Consulting Solicitation
This provision directly requires disclosure of known or potential conflicts of interest, which mandates proactive disclosure of the solicitation to the DOT employer.
Action
Disclosing Dual Employment to Employers
This provision directly requires disclosure of known or potential conflicts of interest, which applies to informing both employers of the dual employment arrangement.
State
Engineer A Adjacent Domain Dual Employment Conflict. Highways vs. Airports
Engineer A is required to disclose the potential conflict arising from his simultaneous highway and airport roles to all relevant parties.
Obligation (6)
  • State DOT Employer Prior Approval Disclosure Engineer A Airport Consulting Solicitation
    This provision directly requires disclosure of known or potential conflicts of interest, which mandates proactive disclosure of the solicitation to the DOT employer.
  • Engineer A Professional Liability Awareness DOT Airport Dual Employment
    This provision requires awareness and disclosure of conflicts that could influence judgment, directly relating to assessing adverse effects of dual employment.
  • Conflict of Interest Recusal Traffic Signal Review Engineer A Municipal Airport Clients
    This provision requires disclosure of conflicts of interest, which underpins the obligation to recuse from traffic signal reviews involving airport consulting clients.
  • Dual Role Appearance of Impropriety Avoidance Engineer A Municipal Overlap
    This provision covers conflicts that could appear to influence judgment, directly relating to the appearance of impropriety from overlapping municipal roles.
  • Engineer A Moonlighting Multi-Factor Assessment DOT Airport Consulting
    This provision requires identifying and disclosing potential conflicts, which is a key component of the multi-factor assessment obligation before accepting outside work.
  • Engineer A Cross-Domain Interrelated Infrastructure Conflict DOT Highway Airport
    This provision requires disclosure of conflicts that could appear to influence judgment, applicable when highway and airport domains are interrelated through shared municipal clients.
Action (3)
  • Disclosing Dual Employment to Employers
    This provision directly requires disclosure of known or potential conflicts of interest, which applies to informing both employers of the dual employment arrangement.
  • Transition to State DOT
    Upon transitioning to the State DOT, the engineer must disclose the existing private firm relationship as a potential conflict of interest.
  • Monitoring and Addressing Emerging Conflicts
    This provision requires ongoing disclosure of any newly arising conflicts that could influence the engineer's judgment in either role.
State (6)
  • Engineer A Adjacent Domain Dual Employment Conflict. Highways vs. Airports
    Engineer A is required to disclose the potential conflict arising from his simultaneous highway and airport roles to all relevant parties.
  • Engineer A Employer-Aware Dual Employment Insufficient Mitigation
    While both employers are aware of the dual role, the Board finds this disclosure insufficient to fully satisfy the conflict of interest disclosure obligation.
  • Engineer A Shared Municipal Stakeholder Dual Role Conflict
    The overlap in municipal stakeholders between Engineer A's state and private roles represents a known conflict that must be disclosed under this provision.
  • Engineer A Adjacent Domain Dual Employment Latent Conflict
    The latent conflict between Engineer A's DOT traffic role and proposed airport consulting role is precisely the type of potential conflict this provision requires to be disclosed.
  • Engineer A Ethical Appearance Conflict. Highway-Airport Dual Role
    This provision covers conflicts that could appear to influence judgment, directly addressing the visible appearance of conflict created by Engineer A's dual roles.
  • Engineer A No Formal Revolving Door Prohibition
    The absence of a statutory prohibition does not eliminate the ethical disclosure obligation under this provision when a conflict of interest exists.
Constraint (10)
  • Engineer A Moonlighting Multi-Factor Pre-Acceptance Assessment DOT Airport
    II.4.a requires disclosure of all known or potential conflicts, directly mandating the comprehensive pre-acceptance assessment before taking the consulting engagement.
  • Grant-Administering Government Engineer Private Consulting Municipal Client Prohibition Engineer A
    II.4.a requires disclosure of conflicts of interest, which includes the conflict arising from administering grants to municipalities while privately consulting for them.
  • Engineer A Appearance of Impropriety Municipal Dual Role Highway Airport
    II.4.a addresses conflicts that could appear to influence judgment, directly relating to the appearance of impropriety from serving the same municipalities in dual roles.
  • Revolving Door Ethics Constraint Engineer A Former Firm Re-Engagement
    II.4.a requires disclosure of potential conflicts, which encompasses the conflict created by re-engaging with a former employer while holding a government oversight role.
  • State DOT Prior Approval Disclosure Procedural Constraint Engineer A Airport Consulting
    II.4.a mandates disclosure of conflicts before accepting outside employment, directly underpinning the procedural disclosure requirement to the State DOT.
  • Appearance of Impropriety Avoidance Public Procurement Engineer A Municipal Airport QBS
    II.4.a explicitly covers conflicts that could appear to influence judgment, directly creating the constraint to avoid the appearance of impropriety in public procurement.
  • Engineer A No Formal Revolving Door Provision Non-Exculpation DOT Airport
    II.4.a imposes a disclosure and conflict-avoidance duty independent of formal contractual provisions, so the absence of a revolving door clause does not excuse non-compliance.
  • No Formal Revolving Door Provision Gap Non-Exculpation Engineer A DOT Airport
    II.4.a creates an ethical conflict-disclosure obligation that exists regardless of whether a formal revolving door provision is present in the employment agreement.
  • Adjacent Domain Dual Employment Shared-Client Conflict Non-Acceptance Engineer A Traffic Airport
    II.4.a requires disclosure of conflicts that could appear to influence judgment, which applies when shared municipal clients create a conflict even across technically distinct engineering domains.
  • Engineer A Grant Authority Non-Exploitation Municipal Airport Consulting
    II.4.a requires disclosure of conflicts arising from grant administration authority that could appear to influence private consulting relationships with grant recipients.
Principle (8)
  • Cross-Domain Same-Client Conflict Invoked for Engineer A Municipal Overlap
    Engineer A must disclose the conflict arising from reviewing the same class of municipalities he would privately consult for.
  • Objectivity Obligation Invoked for Engineer A DOT Review Impartiality
    This provision requires disclosure of conflicts that could compromise Engineer A's objectivity in reviewing municipal traffic signal plans.
  • Dual Role Appearance of Impropriety Invoked for Municipal Client Overlap
    The appearance of impropriety from Engineer A's dual role is precisely the kind of potential conflict this provision requires to be disclosed.
  • Conflict of Interest Recusal Obligation Invoked for Municipal Traffic Review
    Disclosure of the conflict is a prerequisite to the recusal obligation that would arise if Engineer A accepted the private consulting role.
  • Government Grant Authority Non-Exploitation Invoked for Airport Grant Municipalities
    The structural power relationship created by DOT grant authority over municipalities constitutes a known conflict requiring disclosure.
  • Cross-Domain Same-Client Conflict Applied to Engineer A Highway-Airport Roles
    The overlap between Engineer A's governmental review role and private consulting targets is a conflict that must be disclosed under this provision.
  • Appearance of Impropriety in Engineer A Dual Role
    This provision directly addresses conflicts that could appear to influence judgment, which is the core appearance issue identified by the BER.
  • Competitive Employment Freedom Constraint Invoked for Former Firm Solicitation
    Engineer A's freedom to accept work with the former firm is constrained by the disclosure and conflict-avoidance requirements of this provision.
Role (4)
  • Engineer A State DOT Traffic Engineer
    Engineer A must disclose any potential conflict of interest arising from part-time consulting work to his State DOT employer.
  • Engineer A State DOT Airport Consultant
    Engineer A must disclose to all relevant parties the conflict created by simultaneously reviewing DOT submissions and consulting for municipalities receiving DOT grants.
  • Case 97-1 Engineer A Dual-Role Government-Private Engineer
    The precedent engineer was required to disclose conflicts of interest stemming from holding simultaneous government and private engineering positions.
  • Municipalities Submitting Traffic Signal Plans
    Municipalities interacting with Engineer A are directly affected by his obligation to disclose conflicts since they submit plans he reviews and may also employ him as a consultant.
Event (4)
  • Dual Role Conflict Condition Crystallized
    The crystallization of a dual-role conflict is precisely the situation requiring disclosure of known or potential conflicts of interest.
  • Former Firm Re-Engagement Approach Occurs
    Approaching or being approached by a former firm for consulting work represents a potential conflict that must be disclosed to the employer.
  • Contract Review Authority Activated
    Exercising contract review authority over a firm with which the engineer has a financial relationship is a conflict that must be disclosed.
  • Infrastructure Interconnection Overlap Recognized
    Recognizing overlap between airport design experience and current DOT review duties signals a potential conflict requiring disclosure.
Resource (6)
  • Public-Official-Conflict-of-Interest-Standard
    This provision directly requires disclosure of conflicts of interest, which applies to Engineer A's role reviewing private contracts while potentially consulting for a private firm.
  • Dual-Public-Private-Employment-Ethics-Standard
    This provision requires Engineer A to disclose the conflict arising from simultaneously working for the DOT and a private consulting firm.
  • Revolving-Door-Employment-Policy-DOT
    This provision requires disclosure of conflicts relevant to Engineer A re-engaging with his former private employer while at the DOT.
  • NSPE-Code-of-Ethics
    This provision is part of the NSPE Code governing Engineer A's disclosure obligations regarding known or potential conflicts of interest.
  • NSPE-Code-of-Ethics-General
    This provision is a key normative authority for evaluating whether Engineer A properly disclosed his conflict of interest in dual employment.
  • BER-Case-97-1
    This precedent case addresses dual employment conflict of interest situations to which this disclosure provision is analogically applied.
Capability (9)
  • State DOT Prior Approval Proactive Disclosure Engineer A Airport Consulting Solicitation
    This provision requires disclosure of known or potential conflicts, which this capability directly addresses by requiring proactive disclosure to the State DOT.
  • Engineer A Employer Awareness Non-Sufficiency Structural Conflict DOT Airport
    This provision requires disclosure of conflicts, and this capability recognizes that mere employer awareness is insufficient to satisfy that disclosure obligation.
  • Conflict of Interest Recognition and Recusal Engineer A Traffic Review Airport Consulting Municipalities
    This provision requires disclosing conflicts that could influence judgment, directly tied to recognizing the conflict arising from prior employment and dual roles.
  • Revolving Door Conflict Recognition Engineer A Former Firm Airport Solicitation
    This provision requires disclosure of potential conflicts, and this capability addresses recognizing the conflict created by the former firm leveraging prior relationships.
  • Dual Role Appearance of Impropriety Recognition Engineer A Municipal Airport Traffic
    This provision covers conflicts that could appear to influence judgment, which this capability addresses by recognizing the appearance of impropriety in the dual role.
  • Engineer A Dual Role Appearance of Impropriety Recognition DOT Airport Municipal Overlap
    This provision requires disclosure of conflicts that appear to influence judgment, directly linked to recognizing the appearance of impropriety in simultaneous roles.
  • Government Grant Authority Non-Exploitation Recognition Engineer A Airport Municipalities
    This provision requires disclosing conflicts of interest, and this capability addresses recognizing the conflict created by the State DOT grant relationship with municipalities.
  • FAA QBS Consultant Selection Non-Interference Engineer A Airport Consulting Solicitation
    This provision requires disclosure of conflicts that could influence judgment, relevant to the conflict created by participating in FAA QBS procurement processes.
  • Revolving Door Regulatory Gap Navigation Engineer A State DOT Ethics Statutes
    This provision requires disclosure even when not explicitly prohibited, directly addressed by the capability to recognize ethical obligations beyond regulatory gaps.
III.1.c. Engineers shall not accept outside employment to the detriment of their regular work or interest. Before accepting any outside engineering employment, they will notify their employers.
How this applies in the case (showing 3 of 48)
Obligation
State DOT Employer Prior Approval Disclosure Engineer A Airport Consulting Solicitation
This provision requires notifying employers before accepting outside engineering employment, directly supporting the obligation to disclose and seek prior approval from DOT.
Action
Accepting Part-Time Moonlighting Approach
This provision directly governs acceptance of outside employment by requiring notification to the primary employer before taking on part-time work.
State
Engineer A Former Employer Part-Time Re-Engagement Solicitation
Engineer A being solicited for part-time work by his former employer while holding a government position directly triggers the obligation to notify his current employer before accepting.
Obligation (6)
  • State DOT Employer Prior Approval Disclosure Engineer A Airport Consulting Solicitation
    This provision requires notifying employers before accepting outside engineering employment, directly supporting the obligation to disclose and seek prior approval from DOT.
  • Engineer A Governmental Procedure Compliance DOT Airport Dual Employment
    This provision requires notifying employers before outside work, which aligns with the obligation to follow DOT procedures governing dual employment.
  • Governmental Procedure Policy Compliance Engineer A Dual Employment Outside Work
    This provision requires employer notification before outside employment, directly relating to compliance with DOT policies and state ethics statutes on dual employment.
  • Engineer A Moonlighting Multi-Factor Assessment DOT Airport Consulting
    This provision requires assessing detriment to regular work before accepting outside employment, which is a key factor in the multi-factor assessment obligation.
  • Engineer A Faithful Agent Trustee DOT Employer Structural Conflict
    This provision prohibits outside employment detrimental to regular work, supporting the obligation to decline the private consulting role that conflicts with DOT duties.
  • Engineer A Public Resources Non-Use DOT Airport Private Work
    This provision prohibits outside work to the detriment of regular employment, which encompasses the obligation not to use DOT public resources for private work.
Action (3)
  • Accepting Part-Time Moonlighting Approach
    This provision directly governs acceptance of outside employment by requiring notification to the primary employer before taking on part-time work.
  • Disclosing Dual Employment to Employers
    This provision mandates notifying employers before accepting outside engineering employment, making disclosure a prerequisite to the arrangement.
  • Reviewing Private Firm Contracts
    This provision prohibits outside employment that is detrimental to regular work, which is directly relevant when the engineer reviews contracts involving the private firm.
State (5)
  • Engineer A Former Employer Part-Time Re-Engagement Solicitation
    Engineer A being solicited for part-time work by his former employer while holding a government position directly triggers the obligation to notify his current employer before accepting.
  • Engineer A DOT Employment State
    Engineer A's active DOT employment relationship is the primary employment that could be detrimentally affected by accepting outside consulting work.
  • Engineer A Employer-Aware Dual Employment Insufficient Mitigation
    While notification to the employer occurred, this provision also requires that outside work not be to the detriment of regular work, which the Board finds is not fully satisfied.
  • Engineer A Public Resource Use in Private Work Prohibition
    Using state resources for private work would constitute a direct detriment to the regular employer, which this provision prohibits.
  • Engineer A Adjacent Domain Dual Employment Latent Conflict
    The latent conflict between Engineer A's DOT role and proposed consulting work raises the concern that outside employment could be detrimental to his regular state position.
Constraint (8)
  • Engineer A Moonlighting Multi-Factor Pre-Acceptance Assessment DOT Airport
    III.1.c requires notification to employers before accepting outside engineering employment, directly mandating the pre-acceptance assessment and notification process.
  • State DOT Prior Approval Disclosure Procedural Constraint Engineer A Airport Consulting
    III.1.c explicitly requires notifying employers before accepting outside employment, which is the basis for the procedural compliance constraint with State DOT policies.
  • Engineer A Government Procedure Policy Compliance DOT Outside Employment
    III.1.c requires compliance with employer notification requirements before accepting outside work, directly creating the constraint to follow State DOT procedures governing outside employment.
  • Engineer A Professional Liability Adverse Effect Avoidance DOT Airport Dual Employment
    III.1.c prohibits outside employment to the detriment of regular work, which includes assessing adverse effects on professional liability from dual employment arrangements.
  • Dual Public-Private Role Interrelated Domain Conflict Engineer A DOT Airport Consulting
    III.1.c prohibits outside employment detrimental to regular work, directly applying to the conflict created by the interrelated public and private roles.
  • Engineer A Dual Public-Private Interrelated Domain Conflict DOT Highway Airport
    III.1.c prohibits accepting outside work detrimental to regular employment, which is violated when highway and airport responsibilities create an interrelated domain conflict.
  • Government Employer Resource Non-Use Private Consulting Engineer A DOT Airport
    III.1.c prohibits outside employment to the detriment of the regular employer, which encompasses the prohibition on using government employer resources for private consulting.
  • Engineer A Government Resource Non-Use Private Airport Consulting
    III.1.c prohibits outside work detrimental to the regular employer, directly supporting the constraint against using State DOT materials or resources for private consulting.
Principle (6)
  • Moonlighting Contextual Assessment Applied to Engineer A Airport Consulting
    This provision is the basis for the multi-factor moonlighting assessment applied to Engineer A's proposed part-time airport consulting.
  • Faithful Agent Obligation Invoked for Engineer A State DOT Loyalty
    This provision reinforces the faithful agent duty by prohibiting outside employment that detriments the regular employer and requiring prior notification.
  • Comparative Case Precedent Distinguishing in Engineer A Moonlighting Analysis
    The BER's distinction from Case 97-1 centers on whether outside employment is detrimental to the employer, which is the standard set by this provision.
  • Employer Awareness Non-Sufficient to Cure Structural Conflict in Engineer A Case
    While notification to the employer is required, this provision implies that notification alone does not cure a structurally detrimental conflict.
  • Government Procedure Compliance Caution to Engineer A
    The requirement to notify employers before accepting outside work aligns with the caution to follow all applicable government procedures.
  • Dual-Role Public-Private Conflict Invoked for Engineer A Airport Consulting
    Engineer A's dual role creates exactly the kind of detriment to regular work that this provision is designed to prevent.
Role (4)
  • Engineer A State DOT Traffic Engineer
    Engineer A must notify the State DOT before accepting outside consulting work and ensure it does not detract from his primary DOT responsibilities.
  • Engineer A State DOT Airport Consultant
    This provision directly governs whether Engineer A may accept the part-time airport consulting role without harming his regular DOT employment duties.
  • Case 97-1 Engineer A Dual-Role Government-Private Engineer
    The precedent engineer's acceptance of outside private employment while holding a government position is the core scenario this provision addresses.
  • Former Consulting Firm Soliciting Engineer A
    The firm's solicitation of Engineer A for outside work places it in the context of this provision governing Engineer A's obligations before accepting such employment.
Event (3)
  • Former Firm Re-Engagement Approach Occurs
    Accepting outside work from a former firm requires prior notification to the current employer before engagement.
  • DOT Traffic Engineer Role Established
    The existence of a primary salaried role at DOT sets the baseline against which outside employment must be evaluated for detriment.
  • Dual Role Conflict Condition Crystallized
    The conflict condition reflects the risk that outside employment is operating to the detriment of the regular DOT position.
Resource (5)
  • Dual-Public-Private-Employment-Ethics-Standard
    This provision directly governs Engineer A's obligation to notify his DOT employer before accepting outside private consulting employment.
  • Transitional-Employment-Ethics-Framework-DOT
    This provision is relevant to evaluating Engineer A's transition and whether outside employment would be to the detriment of his DOT work.
  • NSPE-Code-of-Ethics
    This provision is part of the NSPE Code requiring notification to employers before accepting outside engineering employment.
  • NSPE-Code-of-Ethics-General
    This provision is invoked as normative authority to evaluate whether Engineer A properly notified his DOT employer about potential outside work.
  • BER-Case-97-1
    This precedent case involves dual employment situations where outside employment notification and detriment obligations are analogically applied.
Capability (8)
  • Engineer A Moonlighting Multi-Factor Pre-Acceptance Assessment DOT Airport
    This provision requires assessment before accepting outside employment, directly addressed by the multi-factor pre-acceptance assessment capability.
  • State DOT Prior Approval Proactive Disclosure Engineer A Airport Consulting Solicitation
    This provision requires notifying employers before accepting outside engineering employment, directly addressed by the proactive disclosure capability.
  • Engineer A Governmental Procedure Policy Compliance DOT Airport Dual Employment
    This provision requires notifying employers and avoiding detriment to regular work, addressed by the capability to comply with all applicable DOT policies and procedures.
  • Governmental Procedure Policy Dual Employment Compliance Engineer A State DOT Outside Work
    This provision requires notification and non-detriment conditions for outside work, directly addressed by this compliance capability.
  • Engineer A BER Moonlighting Precedent Permissibility Boundary Distinction DOT Airport Case 97-1
    This provision governs outside employment conditions, and this capability requires correctly applying BER Case 97-1 to determine permissibility boundaries.
  • Case 97-1 Engineer A BER Dual-Role Precedent Permissible Moonlighting Baseline
    This provision defines conditions for permissible outside employment, and Case 97-1 establishes the baseline scenario where those conditions were met.
  • BER Escalating Dual-Role Precedent Severity Triangulation Engineer A Airport Traffic DOT
    This provision governs outside employment acceptability, addressed by the capability to apply the escalating severity spectrum of BER precedents to assess detriment.
  • Competitive Procurement Fairness Assessment Former Consulting Firm FAA QBS Airport Contracts
    This provision concerns detriment to regular work from outside employment, relevant to assessing whether the solicitation arrangement undermines the DOT role.
III.6.b. Engineers in salaried positions shall accept part-time engineering work only to the extent consistent with policies of the employer and in accordance with ethical considerations.
How this applies in the case (showing 3 of 52)
Obligation
Engineer A Moonlighting Multi-Factor Assessment DOT Airport Consulting
This provision directly governs part-time engineering work for salaried employees, requiring consistency with employer policies and ethical considerations assessed in the multi-factor evaluation.
Action
Accepting Part-Time Moonlighting Approach
This provision directly governs salaried engineers accepting part-time work, requiring it to be consistent with employer policies and ethical considerations.
State
Engineer A DOT Employment State
Engineer A's salaried state DOT position means any part-time work must be consistent with the DOT's policies under this provision.
Obligation (7)
  • Engineer A Moonlighting Multi-Factor Assessment DOT Airport Consulting
    This provision directly governs part-time engineering work for salaried employees, requiring consistency with employer policies and ethical considerations assessed in the multi-factor evaluation.
  • Governmental Procedure Policy Compliance Engineer A Dual Employment Outside Work
    This provision requires part-time work to be consistent with employer policies, directly supporting the obligation to comply with DOT policies and regulations on dual employment.
  • Engineer A Governmental Procedure Compliance DOT Airport Dual Employment
    This provision specifically addresses salaried engineers accepting part-time work within employer policy bounds, directly relating to the obligation to follow DOT government procedures.
  • Engineer A Employer Awareness Non-Sufficiency Structural Conflict DOT Airport
    This provision requires part-time work to accord with ethical considerations beyond mere employer awareness, supporting the obligation that awareness alone does not suffice to permit the engagement.
  • FAA QBS Selection Integrity Non-Interference Engineer A Airport Consultant Solicitation
    This provision requires part-time work to be consistent with ethical considerations, which includes not interfering with FAA qualification-based selection processes through outside consulting.
  • Government Grant Authority Non-Exploitation Engineer A Airport Grant Municipalities
    This provision requires part-time work to be consistent with employer policies and ethics, which prohibits exploiting DOT grant authority through private airport consulting for grant-receiving municipalities.
  • Engineer A Government Grant Authority Non-Exploitation DOT Airport Municipalities
    This provision requires part-time work to align with ethical considerations, directly supporting the obligation to refrain from exploiting State DOT grant relationships through private consulting.
Action (2)
  • Accepting Part-Time Moonlighting Approach
    This provision directly governs salaried engineers accepting part-time work, requiring it to be consistent with employer policies and ethical considerations.
  • Transition to State DOT
    Once in a salaried State DOT position, this provision governs whether the engineer can continue part-time private firm work in accordance with DOT policies.
State (6)
  • Engineer A DOT Employment State
    Engineer A's salaried state DOT position means any part-time work must be consistent with the DOT's policies under this provision.
  • Engineer A Former Employer Part-Time Re-Engagement Solicitation
    The solicitation for part-time work directly invokes this provision requiring that such work be consistent with employer policies and ethical considerations.
  • Engineer A Employer-Aware Dual Employment Insufficient Mitigation
    Employer awareness does not automatically make the part-time arrangement consistent with ethical considerations as required by this provision.
  • Engineer A No Formal Revolving Door Prohibition
    The absence of a formal prohibition does not mean the part-time arrangement meets the ethical considerations standard required by this provision.
  • Engineer A Regulatory Compliance State - FAA QBS Guidelines
    Compliance with FAA qualifications-based selection guidelines is part of the ethical considerations that must be satisfied for Engineer A's part-time consulting to be permissible.
  • Engineer A Shared Municipal Stakeholder Dual Role Conflict
    The shared municipal stakeholder conflict raises ethical considerations that must be resolved for the part-time arrangement to be permissible under this provision.
Constraint (8)
  • Engineer A Moonlighting Multi-Factor Pre-Acceptance Assessment DOT Airport
    III.6.b requires that part-time work be consistent with employer policies and ethical considerations, directly mandating the multi-factor assessment before accepting the engagement.
  • State DOT Prior Approval Disclosure Procedural Constraint Engineer A Airport Consulting
    III.6.b requires part-time work to be consistent with employer policies, directly underpinning the procedural requirement to identify and comply with State DOT policies before accepting outside work.
  • Engineer A Government Procedure Policy Compliance DOT Outside Employment
    III.6.b explicitly conditions part-time work on consistency with employer policies, directly creating the constraint to comply with all applicable State DOT procedures and policies.
  • FAA QBS Guideline Dissemination Role Private Airport Consulting Solicitation Prohibition Engineer A
    III.6.b requires part-time work to be consistent with ethical considerations, which prohibits soliciting private contracts in a domain where Engineer A holds a public QBS oversight role.
  • Engineer A FAA QBS Selection Integrity Non-Interference Airport Consultant Solicitation
    III.6.b requires part-time work to accord with ethical considerations, directly prohibiting participation in soliciting contracts that would interfere with QBS selection integrity.
  • Adjacent Domain Dual Employment Shared-Client Conflict Non-Acceptance Engineer A Traffic Airport
    III.6.b requires part-time work to be consistent with ethical considerations, which bars acceptance of roles creating shared-client conflicts even across adjacent engineering domains.
  • Engineer A Employer Non-Objection Insufficient Faithful Agent DOT Airport
    III.6.b requires consistency with ethical considerations beyond mere employer non-objection, directly supporting the constraint that mutual awareness does not satisfy ethical obligations.
  • Engineer A Professional Liability Adverse Effect Avoidance DOT Airport Dual Employment
    III.6.b conditions part-time work on consistency with ethical considerations, which includes assessing and avoiding adverse effects on professional liability from dual employment.
Principle (7)
  • Moonlighting Contextual Assessment Applied to Engineer A Airport Consulting
    This provision directly governs salaried engineers accepting part-time work and is the framework for the BER's moonlighting assessment of Engineer A.
  • Cross-Domain Infrastructure Linkage Defeating Domain-Separation Defense
    The ethical considerations standard in this provision supports the BER's rejection of domain-separation as a defense for part-time work acceptance.
  • Public Welfare Paramount Invoked for Public Trust in DOT Review Function
    The ethical considerations requirement in this provision encompasses the public interest in impartial governmental review functions.
  • Dual-Role Public-Private Conflict Invoked for Engineer A Airport Consulting
    This provision directly applies to Engineer A as a salaried DOT employee seeking to accept part-time airport consulting work.
  • Government Grant Authority Non-Exploitation Applied to Engineer A DOT-Municipality Relationship
    The ethical considerations standard bars part-time work that exploits the structural power relationship Engineer A holds over municipalities through grant authority.
  • Public Resource Non-Exploitation Caution to Engineer A
    The ethical considerations requirement in this provision underpins the BER's caution against using public resources in private work.
  • Comparative Case Precedent Distinguishing in Engineer A Moonlighting Analysis
    The BER's distinction from Case 97-1 is grounded in whether the part-time work is consistent with ethical considerations as required by this provision.
Role (4)
  • Engineer A State DOT Traffic Engineer
    As a salaried State DOT employee, Engineer A may only accept part-time engineering work consistent with DOT policies and ethical considerations.
  • Engineer A State DOT Airport Consultant
    This provision directly governs the conditions under which Engineer A can ethically take on the part-time airport consulting role while salaried by the DOT.
  • Case 97-1 Engineer A Dual-Role Government-Private Engineer
    The precedent engineer's dual salaried and part-time private employment situation is the type of arrangement this provision is designed to regulate.
  • State DOT Employer Authority
    The State DOT's policies on outside employment are the benchmark against which Engineer A's part-time work must be evaluated under this provision.
Event (4)
  • Former Firm Re-Engagement Approach Occurs
    Accepting part-time work from a former firm must be consistent with DOT employer policies and ethical considerations.
  • DOT Traffic Engineer Role Established
    The salaried DOT position triggers the specific ethical standard governing what part-time engineering work is permissible.
  • Dual Role Conflict Condition Crystallized
    The dual-role conflict indicates the part-time arrangement may not be consistent with employer policy or ethical standards.
  • Prior Airport Design Experience Accumulated
    Prior specialized experience is the basis for the part-time consulting opportunity, making its ethical permissibility subject to employer policy review.
Resource (5)
  • Dual-Public-Private-Employment-Ethics-Standard
    This provision directly governs Engineer A's acceptance of part-time private consulting work consistent with DOT employer policies and ethical considerations.
  • Public-Official-Conflict-of-Interest-Standard
    This provision requires that part-time work be consistent with employer policies, directly relevant to Engineer A's public official role at the DOT.
  • NSPE-Code-of-Ethics
    This provision is part of the NSPE Code specifically addressing salaried engineers accepting part-time work, directly applicable to Engineer A's situation.
  • NSPE-Code-of-Ethics-General
    This provision is a key normative authority for evaluating the permissibility of Engineer A's part-time consulting arrangement under DOT employment policies.
  • BER-Case-97-1
    This precedent case is cited for analogical reasoning about the ethical limits of part-time private work for salaried public employees.
Capability (9)
  • Engineer A Moonlighting Multi-Factor Pre-Acceptance Assessment DOT Airport
    This provision requires part-time work to be consistent with employer policies and ethics, directly addressed by the multi-factor pre-acceptance assessment capability.
  • Engineer A Employer Awareness Non-Sufficiency Structural Conflict DOT Airport
    This provision requires consistency with employer policies, and this capability recognizes that employer awareness alone does not satisfy that ethical requirement.
  • Governmental Procedure Policy Dual Employment Compliance Engineer A State DOT Outside Work
    This provision requires part-time work to comply with employer policies and ethical considerations, directly addressed by this compliance capability.
  • Engineer A Governmental Procedure Policy Compliance DOT Airport Dual Employment
    This provision requires adherence to employer policies for part-time work, directly addressed by the capability to identify and comply with all applicable DOT policies.
  • Engineer A BER Moonlighting Precedent Permissibility Boundary Distinction DOT Airport Case 97-1
    This provision sets ethical boundaries for part-time work, and this capability requires distinguishing when those boundaries are crossed relative to Case 97-1.
  • Case 97-1 Engineer A BER Dual-Role Precedent Permissible Moonlighting Baseline
    This provision defines the ethical standard for salaried part-time work, and Case 97-1 represents the baseline permissible scenario under that standard.
  • BER Escalating Dual-Role Precedent Severity Triangulation Engineer A Airport Traffic DOT
    This provision requires part-time work to be ethically consistent, addressed by the capability to triangulate escalating BER precedent severity for this case.
  • Revolving Door Regulatory Gap Navigation Engineer A State DOT Ethics Statutes
    This provision requires ethical consistency beyond mere policy compliance, directly addressed by the capability to navigate gaps between regulations and ethical obligations.
  • Engineer A Interrelated Infrastructure Domain Cross-Conflict Recognition DOT Highway Airport
    This provision requires part-time work to be ethically consistent with the primary role, addressed by recognizing the functional interrelation between highway and airport domains.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1

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

Principle Established:

An engineer holding a full-time governmental position and a part-time private engineering position does not necessarily violate ethics if both employers are aware and do not object, but any arising conflict of interest must be addressed consistent with NSPE Code provisions.

Citation Context:

The Board cited Case 97-1 to establish the framework for evaluating engineer moonlighting situations, noting that dual employment can be ethical when both employers are aware and do not object, but conflicts of interest must be carefully managed.

Relevant Excerpts
discussion: "The Board noted in Case 97-1 that these cases frequently raise the question of whether an engineer can ethically devote sufficient attention to the responsibilities involved."
discussion: "In Case 97-1, Engineer A held a full-time engineering position with a governmental agency and was also employed on a part-time basis by an engineering firm."
discussion: "While as we noted in Case 97-1, with regard to Engineer A's dual role as an governmental employee and a private employee, assuming both the state governmental agency and the engineering firm are aware of Engineer A's activities"
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 44% Facts Similarity 46% Discussion Similarity 66% Provision Overlap 67% Outcome Alignment 100% Tag Overlap 67%
Shared provisions: II.4.d, III.1.c, III.5, III.6.b Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 58% Discussion Similarity 57% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: II.4.d, III.5 Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 53% Discussion Similarity 56% Provision Overlap 20% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: II.4.d Same outcome True View Synthesis
Component Similarity 48% Facts Similarity 50% Discussion Similarity 68% Provision Overlap 17% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: II.4.d, III.5 Same outcome True View Synthesis
Component Similarity 45% Facts Similarity 43% Discussion Similarity 60% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: III.5 Same outcome True View Synthesis
Component Similarity 41% Facts Similarity 36% Discussion Similarity 47% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: II.4.d Same outcome True View Synthesis
Component Similarity 48% Facts Similarity 43% Discussion Similarity 46% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 30%
Shared provisions: III.5 Same outcome True View Synthesis
Component Similarity 41% Facts Similarity 47% Discussion Similarity 64% Provision Overlap 11% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: III.5 Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 54% Discussion Similarity 70% Provision Overlap 22% Outcome Alignment 50% Tag Overlap 33%
Shared provisions: II.4.d, III.5 View Synthesis
Component Similarity 53% Facts Similarity 58% Discussion Similarity 58% Provision Overlap 15% Outcome Alignment 50% Tag Overlap 50%
Shared provisions: II.4.d, III.5 View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

) while continuing to work as an employee with the State DOT?

Board conclusion It would be unethical for Engineer A to serve on a part-time basis in seeking contracts with municipalities for design work associated with the airport improvements (master plans, runway extensions, etc.) while continuing to work as an employee with the State DOT.
Implicit (4)

Does the mere act of soliciting airport consulting contracts from municipalities that also receive State DOT grant funding constitute a conflict of interest, even before any actual design work is performed or any traffic signal review involving those municipalities occurs?

AnalyticalBeyond the Board's finding that the dual role is unethical, the structural conflict arises not merely from Engineer A's technical review authority over traffic signal plans but from the shared municipal stakeholder relationship itself. Because the State DOT funds municipal airport improvements through grant agreements, and Engineer A would be soliciting those same municipalities for private airport consulting contracts on behalf of his former firm, the conflict is present at the moment of solicitation - before any design work is performed, before any traffic signal plan is reviewed, and regardless of whether any specific municipality ever submits a traffic signal plan to Engineer A for review. The Board's conclusion therefore rests on a broader foundation than technical domain overlap: it rests on the fact that Engineer A's government employer has an ongoing financial and regulatory relationship with the very clients Engineer A would be privately soliciting, creating an inherent tension between Engineer A's duty of loyalty to the State DOT and his private commercial interest in securing consulting contracts from those municipalities.
AnalyticalIn response to Q101: The mere act of soliciting airport consulting contracts from municipalities that also receive State DOT grant funding constitutes a conflict of interest even before any design work is performed or any traffic signal review involving those municipalities occurs. The conflict crystallizes at the moment Engineer A begins representing his former firm's interests to municipal clients who simultaneously exist within the State DOT's grant administration network. Because Engineer A's DOT role gives him ongoing awareness of which municipalities are receiving or seeking airport grant funding, and because those same municipalities may submit traffic signal plans for his review, the solicitation activity itself creates a structural misalignment of loyalties that is independent of whether any specific adverse act ever takes place. The NSPE Code's faithful agent obligation under Section II.4 is not contingent on harm having materialized; it requires that the engineer avoid placing himself in a position where private interests could influence - or appear to influence - the discharge of public duties. Solicitation is precisely such a position-taking act.

Would Engineer A's ethical exposure change materially if the State DOT were to adopt an explicit revolving-door or outside-employment policy, and does the current absence of such a formal prohibition create a false sense of permissibility that itself poses a systemic risk to public trust?

AnalyticalThe Board's conclusion implicitly rejects a domain-separation defense - the argument that because airport design and highway traffic engineering are technically distinct disciplines, no conflict of interest can arise. This rejection is analytically sound and should be made explicit: the ethical conflict in this case is not generated by technical overlap between the two engineering domains but by the identity of the shared client base. Highways and airports are interrelated components of a state transportation infrastructure system, and the State DOT's grant authority over municipal airports means that Engineer A's government employer exercises a funding and oversight relationship over the same municipalities that Engineer A's former firm would be soliciting for airport consulting work. Even if Engineer A never reviewed a single traffic signal plan submitted by a municipality his former firm was simultaneously soliciting, the appearance of preferential access, informational advantage, and divided loyalty would persist. The domain-separation argument therefore fails not because the technical fields are identical but because the client relationships are structurally inseparable from the government role.
AnalyticalIn response to Q102: Engineer A's ethical exposure would not be materially eliminated by the adoption of an explicit State DOT revolving-door or outside-employment policy, though such a policy would clarify the procedural landscape. The current absence of a formal prohibition does create a false sense of permissibility that poses systemic risk to public trust, because engineers in government positions may incorrectly treat the silence of institutional policy as ethical authorization. However, the NSPE Code's ethical obligations are self-executing and do not depend on employer policy to activate. The faithful agent obligation under Section II.4 and the part-time work consistency requirement under Section III.6.b impose duties that exist regardless of whether the State DOT has codified them in an employment handbook. The absence of a formal revolving-door provision is therefore non-exculpatory: it shifts the burden of ethical self-governance entirely onto the engineer, making proactive disclosure and voluntary restraint more - not less - important. A formal policy would reduce systemic risk by making the prohibition legible to all engineers in similar positions, but its absence does not create a permissive ethical space.

To what extent does Engineer A's role in disseminating FAA qualifications-based selection guidelines to municipalities create an informational advantage for his former firm that would compromise the integrity of competitive procurement, even if Engineer A never directly selects or approves airport consultants?

AnalyticalIn response to Q103: Engineer A's role in disseminating FAA qualifications-based selection guidelines to municipalities creates an independent and significant informational advantage for his former firm that compromises competitive procurement integrity even if Engineer A never directly selects or approves airport consultants. By virtue of his DOT position, Engineer A has privileged access to which municipalities are actively pursuing airport improvements, what the applicable selection criteria are, and how those criteria are being interpreted and communicated at the state level. When Engineer A simultaneously solicits those same municipalities on behalf of his former firm, he is effectively converting government-acquired knowledge and institutional access into a private commercial advantage. This is precisely the conduct that the government grant authority non-exploitation principle prohibits. The harm to competitive procurement fairness does not require that Engineer A manipulate any specific selection decision; the asymmetric informational position itself distorts the competitive environment in ways that disadvantage other consulting firms who lack a government insider simultaneously advocating for their interests at the municipal level.
AnalyticalThe Board's conclusion has systemic implications beyond Engineer A's individual case: it establishes that a government engineer who administers grant relationships with municipalities and disseminates federal consultant selection guidelines to those municipalities occupies a position of structural influence over the competitive procurement environment in which private consulting firms operate, and that this structural influence - not merely direct contract award authority - is sufficient to render part-time private consulting for firms competing in that environment unethical. This principle is significant because it extends the conflict-of-interest analysis beyond the narrow question of whether the government engineer has formal authority to select or approve private consultants. Even where, as here, the State DOT does not directly contract with airport consultants and is not formally involved in their selection, Engineer A's role in shaping the informational and procedural environment through FAA guideline dissemination creates an indirect but real competitive advantage for any firm he simultaneously represents in soliciting those same municipalities. Public trust in the integrity of qualifications-based selection procedures depends on the assurance that government officials who shape those procedures are not simultaneously positioned to benefit from them through private employment, and the Board's conclusion appropriately protects that trust.

If Engineer A were to recuse himself from every traffic signal review involving municipalities for which his former firm is simultaneously seeking airport consulting contracts, would that recusal be sufficient to cure the structural conflict, or would the cumulative pattern of recusals itself impair Engineer A's ability to fulfill his primary duties to the State DOT?

AnalyticalThe Board's conclusion carries an important but unstated implication regarding the sufficiency of employer disclosure and recusal as curative measures. Even if Engineer A were to disclose the proposed part-time engagement to the State DOT and commit to recusing himself from every traffic signal review involving municipalities his former firm was simultaneously soliciting for airport contracts, those procedural steps would not eliminate the structural conflict. First, the recusal obligation would expand in proportion to the former firm's solicitation activity: the more municipalities the firm approached, the more reviews Engineer A would be unable to perform, progressively impairing his ability to fulfill his primary duties to the State DOT. Second, Engineer A's role in disseminating FAA qualifications-based selection guidelines to municipalities creates an informational and procedural advantage for his former firm that recusal from traffic signal reviews cannot neutralize, because the advantage flows from Engineer A's government position itself rather than from any specific act of review. Third, the absence of a formal revolving-door or outside-employment prohibition in State DOT policy does not create ethical permissibility; it merely means that the ethical obligation must be derived from the NSPE Code's faithful agent and conflict-of-interest provisions rather than from an explicit regulatory rule. Employer non-objection following disclosure is therefore insufficient to cure the underlying structural conflict.
AnalyticalIn response to Q104: Recusal from every traffic signal review involving municipalities that Engineer A's former firm is simultaneously soliciting for airport consulting work would not be sufficient to cure the structural conflict, and the cumulative pattern of recusals would itself impair Engineer A's ability to fulfill his primary duties to the State DOT. The structural conflict in this case is not reducible to discrete, identifiable review events that can be cleanly excised through recusal. Rather, it pervades Engineer A's entire relationship with the municipal stakeholder population that forms the operational environment of his DOT role. As the number of municipalities being solicited by the former firm grows - a natural consequence of an active business development effort - the proportion of Engineer A's caseload requiring recusal would expand correspondingly, hollowing out his capacity to perform the core functions for which the State DOT employs him. This outcome would itself constitute a detriment to his regular work within the meaning of Section III.1.c. Furthermore, recusal addresses only the direct review conflict; it does not address the informational advantage, the appearance of impropriety in the grant administration relationship, or the faithful agent obligation that runs to the State DOT as an institution rather than merely to individual review decisions.
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 Moonlighting Contextual Assessment principle - which permits part-time private engineering work under appropriate conditions - conflict with the Faithful Agent Trustee Obligation principle when the private work involves the same municipal stakeholders that the engineer's government employer funds through grant agreements, even if the technical domains differ?

AnalyticalIn response to Q201: The Moonlighting Contextual Assessment principle does conflict with the Faithful Agent Trustee Obligation principle in this case, and the latter must prevail. While the Moonlighting Contextual Assessment principle correctly recognizes that part-time private engineering work is not categorically prohibited, it operates as a permissive baseline that is subject to override when the specific conditions of the private engagement create a structural loyalty conflict with the engineer's primary employer. Here, the shared municipal stakeholder population - municipalities that are simultaneously grant recipients under State DOT airport funding agreements and prospective clients of Engineer A's former firm - means that Engineer A cannot serve both principals without the interests of one potentially influencing his conduct toward the other. The fact that the technical domains differ (highways versus airports) does not dissolve this conflict because the conflict's source is the shared client relationship, not technical overlap. The Faithful Agent Trustee Obligation is not domain-specific; it runs to the employer as an institution and encompasses all conduct that could compromise the engineer's undivided loyalty, including conduct in technically distinct fields when the same municipal clients are involved.
AnalyticalThe Faithful Agent Trustee Obligation and the Moonlighting Contextual Assessment principle are not inherently incompatible, but this case demonstrates that the shared-municipal-stakeholder relationship collapses the domain-separation buffer that ordinarily makes part-time private engineering work permissible. In cases where the engineer's government employer funds, regulates, or maintains grant relationships with the very municipalities the engineer would privately solicit, the Moonlighting Contextual Assessment principle cannot be satisfied on its own terms - the 'appropriate conditions' prerequisite fails structurally, not merely procedurally. The Board resolved this tension by treating the Faithful Agent Trustee Obligation as lexically prior: once a structural conflict of interest is identified at the level of shared clients and overlapping institutional authority, no amount of domain-separation argument (highways versus airports) can rehabilitate the moonlighting permission. This case teaches that the Moonlighting Contextual Assessment principle is a conditional permission, not a freestanding right, and that the Faithful Agent Trustee Obligation functions as the gating condition that must be satisfied before the conditional permission activates.

How should the Competitive Employment Freedom Constraint principle - which recognizes an engineer's right to pursue legitimate private professional opportunities - be weighed against the Dual Role Appearance of Impropriety principle when the engineer holds a government position that, even indirectly, shapes the regulatory and funding environment in which the private work would occur?

AnalyticalIn response to Q202: The Competitive Employment Freedom Constraint principle must yield to the Dual Role Appearance of Impropriety principle in this case because Engineer A's government position does not merely create an indirect background influence on the regulatory environment - it creates a direct, operational relationship with the specific municipal entities that would be the targets of his private solicitation. An engineer's right to pursue legitimate private professional opportunities is a genuine and important interest, but it is not absolute when the engineer occupies a government role that shapes the funding, procedural, and informational environment in which those private opportunities arise. The appearance of impropriety standard does not require proof of actual bias; it requires only that a reasonable observer, aware of the full facts, would question whether Engineer A's government conduct could be influenced by his private commercial interests. Given that Engineer A reviews traffic signal submissions from municipalities, administers FAA guideline dissemination to those same municipalities, and would simultaneously be soliciting them for airport consulting contracts through his former firm, the appearance of impropriety is not merely plausible - it is structurally inevitable.
AnalyticalThe Competitive Employment Freedom Constraint and the Dual Role Appearance of Impropriety principle exist in genuine tension in this case, and the Board's resolution reveals an important prioritization rule: when an engineer occupies a government position that shapes - even indirectly - the regulatory and funding environment in which private work would occur, the Appearance of Impropriety principle is not merely a reputational concern but a structural integrity concern that overrides the engineer's individual interest in pursuing private professional opportunities. The key analytical move is that the Dual Role Appearance of Impropriety principle does not require proof of actual interference or actual favoritism; the structural overlap between Engineer A's DOT grant-administration role and the municipalities Engineer A would solicit for airport consulting is itself the disqualifying condition. This means the Competitive Employment Freedom Constraint is not defeated by a showing of bad intent but by a showing of institutional architecture - the government position's reach into the private market is sufficient. The case thus teaches that appearance-of-impropriety analysis in government-employment contexts is objective and structural, not subjective and intent-dependent.

Does the Cross-Domain Infrastructure Linkage principle - which defeats a domain-separation defense by recognizing that highways and airports are interrelated infrastructure systems - stand in tension with the Comparative Case Precedent Distinguishing principle, which might otherwise permit moonlighting in a technically distinct engineering domain, and how should the Board resolve that tension when the shared client relationship is the primary source of conflict rather than technical overlap?

AnalyticalIn response to Q203: The Cross-Domain Infrastructure Linkage principle and the Comparative Case Precedent Distinguishing principle are in genuine tension, but the Board correctly resolves that tension by identifying the shared municipal client relationship - rather than technical domain overlap - as the primary source of the conflict. The Comparative Case Precedent Distinguishing principle would, in isolation, support a finding that moonlighting in a technically distinct engineering domain (airports versus highways) is permissible, as prior BER cases have allowed engineers to perform private work in fields unrelated to their government employer's technical mandate. However, the Cross-Domain Infrastructure Linkage principle defeats this defense not primarily by arguing that highways and airports are interrelated infrastructure systems in an abstract engineering sense, but by demonstrating that the same municipal entities who are Engineer A's government-side stakeholders would become his private-side clients. When the shared-client relationship is the primary conflict vector, technical domain separation provides no meaningful ethical insulation. The Board's resolution is therefore analytically sound: domain distinction is relevant to conflict analysis only when it also produces stakeholder separation, and here it does not.
AnalyticalThe Cross-Domain Infrastructure Linkage principle defeating the domain-separation defense stands in productive but ultimately subordinate tension with the Comparative Case Precedent Distinguishing principle. The Board's implicit reasoning suggests that even if one were to accept the domain-separation argument - treating highway traffic engineering and airport design as sufficiently distinct technical fields - the shared-municipal-stakeholder relationship independently generates a conflict that the domain-separation defense cannot address. This means the Cross-Domain Infrastructure Linkage principle and the Comparative Case Precedent Distinguishing principle are not directly in conflict so much as they operate at different levels of analysis: technical domain overlap is one pathway to finding a conflict, but shared client relationships constitute a parallel and independent pathway. The case teaches that an engineer cannot defeat a conflict-of-interest finding by demonstrating technical distinctiveness alone when the conflict arises from institutional relationships rather than technical overlap. Furthermore, the Employer Awareness Non-Sufficient to Cure Structural Conflict principle interacts critically with the Government Procedure Compliance Caution principle to establish that procedural disclosure to the State DOT - even if it produced no objection - would not dissolve the underlying ethical obligation, because the structural conflict is not a procedural deficiency curable by notice but a substantive incompatibility between the two roles. This interaction warns against conflating procedural compliance with ethical permissibility, a distinction that is especially consequential in government-employment contexts where formal policies may be silent on specific dual-employment scenarios.

Does the Employer Awareness Non-Sufficient to Cure Structural Conflict principle conflict with the Government Procedure Compliance Caution principle in cases where State DOT policy neither explicitly prohibits nor explicitly authorizes outside employment, such that an engineer who discloses and receives no objection from the employer might reasonably but incorrectly conclude that procedural compliance has resolved the underlying ethical obligation?

AnalyticalIn response to Q204: The Employer Awareness Non-Sufficient to Cure Structural Conflict principle and the Government Procedure Compliance Caution principle do conflict in the specific scenario where State DOT policy neither explicitly prohibits nor explicitly authorizes outside employment, and this conflict creates a genuine risk of reasonable but incorrect ethical self-assessment by the engineer. An engineer who discloses the proposed part-time engagement to the State DOT and receives no objection may plausibly but incorrectly conclude that procedural compliance has resolved the underlying ethical obligation. This conclusion is incorrect because the NSPE Code's ethical duties are not delegable to the employer's silence. The faithful agent obligation under Section II.4 requires the engineer to independently assess whether the private engagement compromises his loyalty and objectivity, regardless of whether the employer raises an objection. Employer non-objection is relevant evidence that the employer does not perceive an institutional conflict, but it does not substitute for the engineer's own ethical judgment about whether the structural conditions for a conflict exist. The absence of a formal policy thus creates a systemic vulnerability: engineers may treat procedural disclosure as ethical absolution, when in fact the ethical analysis must proceed independently of the employer's response.
Theoretical (4)

From a deontological perspective, did Engineer A fulfill their duty as a faithful agent and trustee to the State DOT by even entertaining the part-time solicitation from their former firm, given that the State DOT's grant relationships with municipalities structurally overlap with the municipalities Engineer A would be soliciting for airport consulting work?

AnalyticalIn response to Q301: From a deontological perspective, Engineer A failed to fulfill the duty of a faithful agent and trustee to the State DOT by entertaining the part-time solicitation without proactively identifying and disclosing the structural conflict. Deontological ethics requires that duties be discharged not merely in their formal observance but in their spirit, and the faithful agent duty under Section II.4 imposes an affirmative obligation to protect the employer's interests from being compromised by the engineer's private conduct. The structural overlap between the State DOT's grant relationships with municipalities and the municipalities Engineer A would be soliciting for airport consulting work was ascertainable at the moment the solicitation was received. A deontologically compliant engineer would have recognized this overlap immediately, disclosed it to the State DOT without being asked, and declined the engagement pending a determination that no conflict existed. The mere act of entertaining the solicitation - weighing its attractiveness, considering its feasibility - without first performing this conflict identification and disclosure represents a failure to treat the faithful agent duty as a categorical obligation rather than a factor to be balanced against personal professional interest.

From a consequentialist perspective, what cumulative harms to public trust, competitive procurement fairness, and FAA qualifications-based selection integrity would likely result if Engineer A accepted the part-time role, even if no single act of direct interference with state highway decisions could be identified?

AnalyticalIn response to Q302: From a consequentialist perspective, the cumulative harms to public trust, competitive procurement fairness, and FAA qualifications-based selection integrity that would likely result from Engineer A accepting the part-time role are substantial and systemic, even if no single act of direct interference with state highway decisions could be identified. First, public trust in the State DOT's impartiality in administering airport grant agreements would be undermined if it became known that a DOT employee was simultaneously soliciting those grant recipients for private consulting work. Second, competitive procurement fairness would be distorted because Engineer A's former firm would enjoy an informational and relational advantage over competing airport consultants who lack a government insider with access to municipal stakeholders. Third, FAA qualifications-based selection integrity would be compromised because the guidelines Engineer A disseminates to municipalities would be perceived - and may in fact function - as a tool for positioning his former firm favorably in the consultant selection process. These harms compound over time: each municipality solicited, each guideline disseminated, and each grant agreement administered while the dual role persists adds to the cumulative erosion of institutional integrity. The consequentialist calculus strongly supports the Board's conclusion that the engagement is unethical.

From a virtue ethics perspective, does Engineer A's willingness to accept the part-time solicitation without proactively identifying and disclosing the structural conflict to the State DOT reflect a failure of professional integrity, even in the absence of an explicit statutory prohibition on such dual employment?

AnalyticalFrom a virtue ethics perspective, the Board's conclusion reveals a failure of proactive professional integrity that extends beyond the specific act of accepting the part-time role. Engineer A's willingness to entertain the solicitation from his former firm without first independently identifying and disclosing the structural conflict to the State DOT suggests an insufficient internalization of the faithful agent obligation. A professionally virtuous engineer in Engineer A's position would have recognized, without external prompting, that the combination of government grant authority over municipal airports, personal involvement in disseminating FAA consultant selection guidelines, and a former employer's interest in securing airport consulting contracts from those same municipalities created a conflict requiring immediate disclosure and likely declination. The absence of an explicit statutory prohibition does not diminish this obligation; rather, it heightens the importance of the engineer's own ethical judgment as the primary safeguard. The NSPE Code's faithful agent and conflict-of-interest provisions are designed precisely to operate in the space where formal rules are silent, and Engineer A's apparent reliance on the absence of an explicit prohibition as a basis for entertaining the solicitation reflects a compliance-oriented rather than integrity-oriented approach to professional ethics.
AnalyticalIn response to Q303: From a virtue ethics perspective, Engineer A's willingness to accept the part-time solicitation without proactively identifying and disclosing the structural conflict to the State DOT reflects a failure of professional integrity, even in the absence of an explicit statutory prohibition. Virtue ethics evaluates conduct not merely by its compliance with rules but by whether it reflects the character dispositions - honesty, prudence, integrity, and practical wisdom - that define a professional of good character. A virtuous engineer in Engineer A's position would have recognized, without being prompted by a rule, that the solicitation created a structural tension between private interest and public duty. The virtuous response would have been immediate, voluntary disclosure to the State DOT, accompanied by a request for guidance and a willingness to decline the engagement if the conflict could not be resolved. The absence of a statutory prohibition does not diminish this obligation; virtue ethics holds that good character requires doing the right thing precisely when no external rule compels it. Engineer A's failure to proactively surface the conflict suggests that professional integrity was being subordinated to personal professional opportunity, which is a character failure independent of any rule violation.

From a deontological perspective, does the fact that Engineer A's State DOT role involves disseminating FAA qualifications-based selection guidelines to municipalities create an independent duty not to exploit that informational and procedural authority by simultaneously soliciting those same municipalities for private airport consulting contracts?

AnalyticalIn response to Q304: From a deontological perspective, Engineer A's role in disseminating FAA qualifications-based selection guidelines to municipalities does create an independent duty not to exploit that informational and procedural authority by simultaneously soliciting those same municipalities for private airport consulting contracts. This duty arises from two intersecting deontological obligations: the faithful agent duty owed to the State DOT, which prohibits using government-acquired authority and information for private benefit, and a duty of non-exploitation owed to the municipalities themselves, who receive the FAA guidelines in their capacity as grant recipients relying on the State DOT's impartial guidance. When Engineer A disseminates selection guidelines while simultaneously representing a firm that would benefit from those guidelines being interpreted favorably, he converts a public informational function into a private commercial tool. Deontologically, this is impermissible regardless of whether Engineer A intends any manipulation, because the duty not to exploit institutional authority is categorical and does not depend on subjective intent. The informational authority vested in Engineer A by his DOT role must be exercised exclusively in the public interest, and any private use of that authority - including using it to position a former employer advantageously in consultant selection - constitutes a breach of this independent duty.
Counterfactual (4)

Would the Board's conclusion have differed if Engineer A had proactively disclosed the solicitation to the State DOT, obtained explicit employer approval, and committed to recusing themselves from any DOT review or grant activity involving municipalities they were simultaneously soliciting for airport consulting work?

AnalyticalIn response to Q401: The Board's conclusion would likely not have differed materially even if Engineer A had proactively disclosed the solicitation to the State DOT, obtained explicit employer approval, and committed to recusing himself from any DOT review or grant activity involving municipalities being simultaneously solicited for airport consulting work. While proactive disclosure and employer approval are necessary conditions for any permissible moonlighting arrangement, they are not sufficient conditions when the structural conflict is as pervasive as it is here. Employer approval addresses the institutional dimension of the faithful agent obligation but does not resolve the appearance of impropriety that arises from the shared municipal stakeholder relationship, nor does it eliminate the informational advantage that Engineer A's government position confers on his former firm. Furthermore, as analyzed in response to Q104, the cumulative pattern of recusals required to operationalize the conflict management commitment would itself impair Engineer A's ability to perform his primary DOT duties, creating a detriment to regular work under Section III.1.c. Disclosure and approval are ethically significant mitigating steps that would reflect better professional character, but they cannot transform a structurally conflicted engagement into a permissible one.

What if Engineer A's former consulting firm had no existing or prospective relationships with any municipality that also received State DOT airport grant funding or submitted traffic signal plans for DOT review - would the shared-municipal-stakeholder conflict dissolve entirely, and would part-time engagement then be permissible under the NSPE Code?

AnalyticalIn response to Q402: If Engineer A's former consulting firm had no existing or prospective relationships with any municipality that also received State DOT airport grant funding or submitted traffic signal plans for DOT review, the shared-municipal-stakeholder conflict would dissolve as the primary basis for the Board's ethical finding, and part-time engagement might then be permissible under the NSPE Code subject to the standard moonlighting conditions. The Board's analysis in this case rests fundamentally on the overlap between the State DOT's municipal grant relationships and the municipalities Engineer A would be soliciting for private airport consulting work. If that overlap were entirely absent - if the former firm operated exclusively in municipalities with no State DOT airport grant relationships and no traffic signal submissions pending before Engineer A - the faithful agent concern would be substantially reduced, the appearance of impropriety would be far less acute, and the cross-domain same-client conflict would not arise. The remaining considerations - such as the general appearance of a government engineer doing private consulting work - would need to be evaluated under the standard moonlighting framework of Sections III.1.c and III.6.b, and might well be resolved in Engineer A's favor. This counterfactual confirms that the shared municipal stakeholder relationship is the load-bearing element of the Board's ethical analysis, not the mere fact of dual employment.

Would the ethical analysis change if Engineer A had fully transitioned out of State DOT employment before accepting the part-time role with the former firm, and if so, what minimum cooling-off period or scope limitation would be necessary to eliminate the revolving-door and faithful-agent concerns identified by the Board?

AnalyticalIn response to Q403: The ethical analysis would change significantly if Engineer A had fully transitioned out of State DOT employment before accepting the part-time role with the former firm, because the faithful agent obligation and the shared-stakeholder conflict are both contingent on the existence of the concurrent government employment relationship. Once Engineer A is no longer a State DOT employee, he no longer owes a faithful agent duty to the DOT, no longer reviews traffic signal submissions from municipalities, and no longer disseminates FAA guidelines in an official capacity. However, a cooling-off period would still be ethically necessary to address residual revolving-door concerns: Engineer A would retain, for some period after departure, government-acquired knowledge about which municipalities are pursuing airport improvements, the status of their grant relationships, and the internal workings of the DOT's consultant selection guidance function. A minimum cooling-off period of one to two years - consistent with common revolving-door standards in government ethics frameworks - combined with a scope limitation prohibiting Engineer A from soliciting municipalities with whom he had direct official contact during his DOT tenure, would be necessary to adequately mitigate these residual concerns. The precise duration and scope of any cooling-off requirement would depend on the nature and recency of Engineer A's official contacts with specific municipalities.

If Engineer A's role at the State DOT had been limited strictly to internal administrative functions with no contract review authority over private firms and no involvement in disseminating FAA consultant selection guidelines, would the structural conflict identified by the Board still be sufficient to render the part-time airport consulting engagement unethical?

AnalyticalIn response to Q404: If Engineer A's role at the State DOT had been limited strictly to internal administrative functions with no contract review authority over private firms and no involvement in disseminating FAA consultant selection guidelines, the structural conflict identified by the Board would be substantially weakened but would not entirely dissolve. The shared municipal stakeholder relationship - the fact that the State DOT administers airport grant agreements with the same municipalities Engineer A would be soliciting for private consulting work - would remain as a residual basis for an appearance of impropriety concern, because Engineer A's government employer would still have an ongoing financial and regulatory relationship with his private clients. However, without the contract review authority and the FAA guideline dissemination role, the specific mechanisms by which Engineer A could exploit his government position for private advantage would be largely eliminated, and the faithful agent concern would be considerably attenuated. In this more limited scenario, the ethical analysis would likely turn on whether the appearance of impropriety arising solely from the grant administration relationship - without any direct review or informational authority - is sufficient to render the engagement impermissible. The Board's reasoning suggests that the grant relationship alone would still raise concerns, but the case for prohibition would be materially weaker and might be resolved through disclosure, employer approval, and appropriate scope limitations rather than outright prohibition.
Decisions & Arguments (6)
View Extraction

Should Engineer A accept the part-time airport consulting solicitation from the former firm, or decline it on the basis that the shared municipal client relationship creates an irreconcilable structural conflict with the State DOT employment?

Options considered:
O1 Refuse the former firm's solicitation on the grounds that the shared municipal client base creates a structural conflict of interest with the State DOT employment that cannot be cured by disclosure, recusal, or employer approval, and that the faithful agent obligation requires declining the engagement regardless of technical domain distinction. Board's choice
O2 Accept the part-time role after proactively disclosing the arrangement to the State DOT and obtaining employer approval, committing to recuse from any DOT review or grant activity involving municipalities simultaneously being solicited for airport consulting work, on the theory that procedural safeguards adequately manage the conflict.
O3 Accept the part-time role on the basis that airport design and highway traffic engineering are technically distinct disciplines with no formal overlap, that the former firm does no competing state highway work, and that the absence of an explicit outside-employment prohibition at the State DOT renders the dual engagement permissible under the standard moonlighting framework.
Argument structure:
Warrants

The Faithful Agent Trustee Obligation (II.4) requires Engineer A to act as a loyal agent of the State DOT and avoid placing private commercial interests in structural tension with public duties. The Cross-Domain Same-Client Government-Private Consulting Non-Engagement Obligation prohibits accepting private consulting for the same entities the engineer reviews or oversees in the governmental role, regardless of technical domain distinction. The Moonlighting Contextual Assessment principle permits part-time private work under appropriate conditions but operates only as a conditional permission gated by the faithful agent obligation. The Competitive Employment Freedom Constraint recognizes Engineer A's legitimate interest in pursuing private professional opportunities, particularly in a domain (airports) where the former firm does no competing state highway work.

Rebuttals

Uncertainty arises because airport design and highway traffic engineering are technically distinct disciplines, and prior BER cases have permitted moonlighting in fields unrelated to the government employer's technical mandate. The former firm does no traffic signal work in the state highway system, which could be read as eliminating direct competitive conflict. The absence of a formal revolving-door or outside-employment prohibition at the State DOT creates a regulatory gap that engineers may plausibly interpret as implicit permission. The domain-separation defense has genuine force if one treats the shared municipal client relationship as incidental rather than structurally determinative.

Grounds

Engineer A is a State DOT traffic engineering employee who reviews private firm contracts and traffic signal plans submitted by municipalities and developers for work on the state highway system. The State DOT also administers FAA airport improvement grant agreements with those same municipalities and disseminates FAA qualifications-based selection guidelines to them. Engineer A's former consulting firm, which currently does no traffic signal work in the state highway system, has approached Engineer A to solicit airport consulting contracts (master plans, runway extensions) from municipalities on a part-time basis. The municipalities targeted for solicitation are the same entities that submit traffic signal plans to Engineer A's DOT division for review and that receive airport grant funding administered by Engineer A's employer.

Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary Adjacent Domain Dual Employment Shared-Client Conflict Non-Acceptance Constraint

If Engineer A were to proceed with the dual role, should Engineer A treat employer disclosure and a recusal commitment as sufficient ethical safeguards, or must Engineer A recognize that the structural conflict cannot be cured by procedural measures and decline the engagement regardless of employer non-objection?

Options considered:
O1 Recognize that employer disclosure and non-objection are necessary but not sufficient conditions for ethical permissibility, and decline the engagement on the independent ground that the structural conflict: shared municipal stakeholders, expanding recusal obligations, and informational advantage from FAA guideline dissemination, cannot be cured by procedural measures regardless of employer consent. Board's choice
O2 Proceed with the dual role after obtaining explicit State DOT approval and implementing a systematic recusal protocol, treating the employer's informed non-objection as the authoritative institutional judgment that the conflict is manageable and that the engineer's independent ethical obligation is thereby satisfied.
O3 Accept the engagement with a narrowly scoped recusal protocol limited to municipalities where active airport consulting contracts exist (rather than mere solicitation), subject to periodic review by the State DOT ethics officer, on the theory that a targeted and supervised recusal regime adequately manages the conflict without requiring full declination.
Argument structure:
Warrants

The Employer Awareness Non-Sufficiency to Cure Structural Dual-Employment Conflict Obligation establishes that mutual employer awareness and non-objection is a necessary but not sufficient condition for ethical permissibility, the engineer must independently assess whether the structural conflict exists and decline if it does, regardless of employer consent. The Conflict of Interest Recusal Obligation requires Engineer A to recuse from reviewing any traffic signal plans submitted by municipalities for which private airport consulting is simultaneously being performed. The Faithful Agent Trustee Obligation is violated by the structural conflict itself, not merely by specific acts of biased review. The State DOT Employer Prior Approval and Disclosure Obligation requires proactive disclosure as a precondition but does not render the engagement permissible once disclosed.

Rebuttals

Uncertainty is created by the policy gap: where State DOT policy neither explicitly prohibits nor explicitly authorizes outside employment, an engineer who discloses and receives no objection may reasonably but incorrectly conclude that procedural compliance has resolved the underlying ethical obligation. The recusal mechanism has genuine force as a conflict-management tool in cases where the overlap is limited and discrete. If the number of municipalities requiring recusal were small and manageable, the cumulative impairment argument would be weaker. Employer approval is not ethically irrelevant, it reflects the institutional judgment of the entity whose interests are at stake.

Grounds

Both the State DOT and the former consulting firm are assumed to be aware of Engineer A's proposed dual employment and do not object. Engineer A reviews traffic signal plans and contracts submitted by municipalities for work on the state highway system. Engineer A's DOT division also disseminates FAA qualifications-based selection guidelines to those same municipalities. If Engineer A accepts the part-time role, the number of municipalities requiring recusal from traffic signal review would expand in proportion to the former firm's solicitation activity. The State DOT has no explicit revolving-door or outside-employment prohibition policy.

Employer Awareness Non-Sufficiency to Cure Structural Dual-Employment Conflict Obligation Competitive Employment Freedom Constraint Invoked for Former Firm Solicitation

Should Engineer A treat the conflict of interest as arising at the moment of solicitation activity, requiring immediate declination, or as arising only upon execution of a consulting contract or a specific act of biased governmental review, permitting Engineer A to explore the opportunity while monitoring for concrete conflicts?

Options considered:
O1 Treat the conflict of interest as arising at the moment the former firm's solicitation is received, because the structural overlap between DOT grant municipalities and the municipalities to be solicited is immediately ascertainable, and decline the engagement without proceeding to contract negotiation, on the ground that the faithful agent obligation prohibits position-taking that places private interests in tension with public duties regardless of whether any specific harm has yet occurred. Board's choice
O2 Proceed with exploring the part-time opportunity while implementing a real-time monitoring protocol that triggers recusal from any DOT review or grant activity the moment a specific municipality becomes a target of the former firm's solicitation, treating the conflict as transactional and manageable rather than structural and categorical.
O3 Pause before accepting or declining the solicitation, proactively disclose the former firm's approach to the State DOT ethics officer and the NSPE Board of Ethical Review, and request a formal advisory opinion on whether the structural overlap is sufficient to prohibit the engagement, treating the timing question as genuinely uncertain and requiring authoritative resolution before any solicitation activity begins.
Argument structure:
Warrants

The Government Grant Authority Non-Exploitation Private Consulting Solicitation Prohibition Obligation establishes that the conflict arises at the solicitation stage because the DOT's grant authority over municipalities creates a structural power asymmetry that could be, or appear to be, exploited to obtain private consulting work, independent of whether any specific grant decision is influenced. The Dual Role Appearance of Impropriety Avoidance Obligation requires Engineer A to recognize that the shared municipal client base creates an interrelated conflict at the moment Engineer A begins representing the former firm's interests to those municipalities. The FAA QBS Consultant Selection Integrity Non-Interference Obligation prohibits participating as a candidate consultant in selection processes governed by guidelines Engineer A disseminates, which is implicated from the first solicitation contact. The Faithful Agent Trustee Obligation is not contingent on harm having materialized but on the engineer placing himself in a position where private interests could influence public duties.

Rebuttals

Uncertainty is created by the temporal ambiguity of when a conflict of interest legally and ethically materializes: whether at the moment of solicitation, at contract award, or only upon actual exercise of biased governmental authority. A monitoring-and-avoidance approach has genuine force: if Engineer A could identify and recuse from specific conflicts as they crystallize, the harm-prevention rationale for early prohibition would be weakened. The solicitation stage conflict argument depends on the assumption that the municipal overlap is substantial; if only a small number of municipalities were involved on both sides, the structural argument would be less compelling. Deontological duty-at-entertainment analysis may be seen as overly expansive if it prohibits even preliminary exploration of professional opportunities.

Grounds

Engineer A's former firm has approached Engineer A to seek airport consulting contracts from municipalities. Those municipalities are the same entities that submit traffic signal plans to Engineer A's DOT division for review and that receive State DOT airport improvement grant funding. Engineer A's DOT role includes disseminating FAA qualifications-based selection guidelines to those municipalities. No airport consulting contract has yet been executed, and no specific traffic signal review involving a solicited municipality has yet occurred. The structural overlap between the DOT's municipal grant relationships and the municipalities the former firm would target is ascertainable at the moment the solicitation is received.

Cross-Domain Same-Client Government-Private Consulting Non-Engagement Obligation Adjacent Domain Dual Employment Shared-Client Conflict Non-Acceptance Constraint

Should Engineer A accept the part-time role soliciting municipal airport consulting contracts for his former firm while remaining a State DOT employee, or decline the engagement on the basis of structural conflict of interest?

Options considered:
O1 Decline the former firm's solicitation on the basis that the shared municipal stakeholder relationship between the State DOT's grant administration function and the municipalities to be solicited creates a structural conflict of interest that cannot be cured by disclosure or recusal while concurrent DOT employment continues. Board's choice
O2 Accept the part-time role after disclosing the dual employment to both the State DOT and the former firm, and commit to recusing from every DOT traffic signal review or grant activity involving municipalities simultaneously solicited for airport consulting work, treating procedural safeguards as sufficient to manage the conflict.
O3 Accept the part-time role on the grounds that airport design and highway traffic engineering are technically distinct disciplines, that Engineer A has no formal authority to select or approve airport consultants, and that the absence of an explicit State DOT outside-employment prohibition renders the engagement permissible under the standard moonlighting framework.
Argument structure:
Warrants

The Moonlighting Contextual Assessment principle (III.1.c, III.6.b) permits part-time private engineering work under appropriate conditions, recognizing engineers' legitimate interest in pursuing private professional opportunities (Competitive Employment Freedom Constraint). However, the Faithful Agent Trustee Obligation (II.4) requires undivided loyalty to the State DOT and prohibits placing private interests in a position to influence, or appear to influence, public duties. The shared municipal stakeholder population (DOT grant recipients who are also prospective private clients) collapses the domain-separation buffer that ordinarily makes moonlighting permissible. The Cross-Domain Infrastructure Linkage principle further defeats any highway-versus-airport technical distinction defense because the conflict source is the shared client relationship, not technical overlap.

Rebuttals

Uncertainty arises because the absence of a formal State DOT outside-employment prohibition could be read as implicit permission, and because the Moonlighting Contextual Assessment principle has been applied in prior BER cases to allow private work in technically distinct domains. A reasonable engineer might conclude that disclosure to both employers, combined with a commitment to recuse from any DOT review involving municipalities simultaneously solicited by the former firm, would adequately manage the conflict without requiring full declination. The Competitive Employment Freedom Constraint also provides genuine justification for accepting the role, particularly given that Engineer A's airport design expertise is a legitimate professional asset.

Grounds

Engineer A holds a State DOT traffic engineering position that includes reviewing private firm traffic signal contracts and disseminating FAA qualifications-based selection guidelines to municipalities. His former consulting firm approaches him to solicit municipal airport consulting contracts (master plans, runway extensions) on a part-time basis. The same municipalities that receive State DOT airport grant funding and submit traffic signal plans for Engineer A's review would be the targets of the private solicitation. No formal State DOT revolving-door or outside-employment prohibition exists. Engineer A has prior airport design experience from his former firm.

Moonlighting Conflict of Interest Multi-Factor Contextual Assessment Before Acceptance Obligation Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary

Should Engineer A continue performing his State DOT duties, including reviewing private firm traffic signal contracts and disseminating FAA qualifications-based selection guidelines to municipalities, while simultaneously soliciting those same municipalities for private airport consulting contracts, or must he treat the cross-domain same-client overlap as independently disqualifying regardless of domain separation?

Options considered:
O1 Treat the cross-domain same-client overlap as independently disqualifying and refrain from any private solicitation of municipalities that receive State DOT airport grant funding or submit traffic signal plans for DOT review, recognizing that the informational and procedural advantage from the FAA guideline dissemination role cannot be neutralized by recusal or disclosure alone. Board's choice
O2 Continue both DOT duties and private solicitation activity, but implement a systematic recusal protocol under which Engineer A abstains from reviewing any traffic signal plans or grant activities involving municipalities simultaneously being solicited by his former firm, treating targeted recusal as sufficient to manage the specific conflict events as they arise.
O3 Continue DOT duties without modification but restrict the former firm's solicitation activity to municipalities that have no current or pending State DOT airport grant relationships and no traffic signal submissions before Engineer A, thereby eliminating the shared-stakeholder overlap while preserving Engineer A's ability to perform his primary DOT functions and pursue legitimate private professional opportunities.
Argument structure:
Warrants

The Cross-Domain Same-Client Government-Private Consulting Non-Engagement Obligation prohibits Engineer A from simultaneously serving government-side and private-side roles with respect to the same municipal clients, even when the technical domains differ. The Government Grant Authority Non-Exploitation principle prohibits converting government-acquired knowledge and institutional access into private commercial advantage. The FAA QBS Selection Integrity Non-Interference Obligation requires that engineers who shape the procedural environment for qualifications-based selection not simultaneously be positioned to benefit from it through private employment. The Objectivity Obligation requires impartiality in DOT contract reviews that cannot be maintained when the reviewed firms' municipal clients are also Engineer A's private solicitation targets.

Rebuttals

Uncertainty arises from the difficulty of establishing a causal link between Engineer A's guideline dissemination and any competitive advantage accruing to his former firm, and from the argument that Engineer A's role is informational rather than decisional, he disseminates guidelines but does not select or approve airport consultants. A reasonable engineer might conclude that the technical domain separation (highways versus airports) and the absence of formal contract award authority over airport consultants mean that the informational overlap is too attenuated to constitute a disqualifying conflict, particularly if recusal from specific municipal reviews is offered as a mitigation measure.

Grounds

Engineer A's State DOT role includes reviewing traffic signal plans submitted by private firms and disseminating FAA qualifications-based selection guidelines to municipalities that receive State DOT airport grant funding. These same municipalities are the prospective clients his former firm would solicit for airport consulting contracts. Engineer A has privileged access to which municipalities are actively pursuing airport improvements, the applicable FAA selection criteria, and how those criteria are being interpreted at the state level. No single act of direct manipulation of a consultant selection decision has occurred or is alleged.

Cross-Domain Same-Client Conflict Non-Engagement Engineer A Municipal Airport Consulting Engineer A Cross-Domain Same-Client DOT Highway Airport Municipal Conflict

Should Engineer A treat proactive disclosure to the State DOT and receipt of employer non-objection as sufficient ethical authorization to proceed with the part-time role, or must Engineer A independently conclude that the structural conflict is irresolvable regardless of the employer's response?

Options considered:
O1 Perform an independent ethical assessment under the NSPE Code's faithful agent and conflict-of-interest provisions, conclude that the structural overlap between DOT grant relationships and the municipalities to be privately solicited renders the engagement impermissible regardless of employer response, and decline the part-time role without relying on the State DOT's silence as authorization. Board's choice
O2 Proactively disclose the proposed part-time engagement to the State DOT in full detail, request explicit guidance or approval, and treat the employer's informed response, whether approval, conditional approval, or non-objection, as the authoritative determination of whether the engagement is institutionally permissible, supplementing that determination with personal recusal commitments.
O3 Disclose the proposed engagement to the State DOT and simultaneously seek an advisory opinion from the NSPE Board of Ethical Review or a comparable professional ethics body before accepting or declining, treating the absence of a formal State DOT policy as a gap that warrants external ethical guidance rather than unilateral resolution by either the engineer or the employer.
Argument structure:
Warrants

The Employer Awareness Non-Sufficiency to Cure Structural Dual-Employment Conflict Obligation holds that employer disclosure and non-objection do not discharge the engineer's independent ethical obligation: the NSPE Code's duties are not delegable to the employer's silence. The Faithful Agent Trustee Obligation requires the engineer's own independent ethical assessment of whether the private engagement compromises loyalty and objectivity. The Government Procedure Compliance Caution principle warns that procedural disclosure is necessary but not sufficient to resolve underlying structural conflicts, and that treating institutional silence as ethical authorization creates systemic risk to public trust. The absence of a formal revolving-door provision is non-exculpatory: it shifts the burden of ethical self-governance entirely onto the engineer.

Rebuttals

Uncertainty is created by the policy gap itself: a reasonable engineer who discloses the proposed engagement and receives no objection from the State DOT may plausibly conclude that the employer, who is best positioned to assess institutional risk, has determined that no conflict exists. The Government Procedure Compliance Caution principle would be unambiguously rebutted if explicit policy prohibited the outside work, but the absence of explicit prohibition creates genuine ambiguity about whether the engineer's independent ethical judgment must override an employer's implicit acquiescence. Additionally, requiring engineers to second-guess employer non-objection may undermine the institutional role of employer oversight in managing conflicts of interest.

Grounds

No formal State DOT revolving-door or outside-employment prohibition exists. Engineer A could disclose the proposed part-time engagement to the State DOT and receive no objection, either because the DOT lacks a formal policy to apply or because administrators do not perceive an institutional conflict. The NSPE Code's faithful agent obligation under Section II.4 and the part-time work consistency requirement under Section III.1.c impose duties that exist regardless of whether the State DOT has codified them in employment policy. The structural conflict, shared municipal stakeholders, FAA guideline dissemination role, contract review authority, persists independently of whether the employer raises an objection.

Engineer A Employer Awareness Non-Sufficiency Structural Conflict DOT Airport State DOT Employer Prior Approval Disclosure Engineer A Airport Consulting Solicitation
11 sequenced 5 actions 6 events
Case timeline
Engineer A accumulated specialized airport design expertise during employment at the consulting firm, establishing a professional background that would later create both opportunity and conflict. This experience forms the foundational condition enabling the future dual-role dilemma.
Engineer A made a deliberate career decision to leave private consulting and accept full-time employment as a traffic engineer with the State DOT traffic engineering division. This transition fundamentally shifted his professional obligations and created a new set of fiduciary duties to a public employer.
Fulfills (3)
  • Commitment to new employer as faithful agent and trustee (NSPE Code III.6.b)
  • Acceptance of public service role with attendant ethical responsibilities
  • Transparent departure from prior private employment
Upon completing the transition to the State DOT, Engineer A's new professional role as a traffic engineer becomes formally operative, conferring specific public-sector responsibilities including review authority over private firm contracts and traffic signal plans on the state highway system. This role establishment is the outcome of the transition action.
As a direct and ongoing consequence of his DOT role, Engineer A regularly exercises governmental review authority over contracts submitted by private engineering firms, including potentially his former employer. This creates a structural condition of regulatory power over parties with whom he has prior professional relationships.
As part of his ongoing duties, Engineer A reviews contracts and traffic signal plans, specifications, and estimates submitted by outside entities (developers and municipalities) for traffic signal work on the state highway system. This is a continuous professional duty exercised in his capacity as a public employee with regulatory authority over private entities.
Fulfills (3)
  • Faithful agent and trustee to public employer (NSPE Code III.6.b)
  • Protection of public safety through rigorous plan review
  • Objective and impartial exercise of regulatory authority
The consulting firm's decision to approach Engineer A for part-time work constitutes an exogenous event from Engineer A's perspective, an external actor initiating contact that places him in an ethically charged situation he did not seek. The approach itself immediately activates conflict-of-interest considerations regardless of Engineer A's response.
Engineer A entertains and engages with his former consulting firm's proposal to work part-time seeking municipal airport contracts while maintaining his full-time DOT position. The very act of seriously considering and not immediately declining this arrangement constitutes a volitional decision point with ethical implications.
At stake (1)
  • Obligation to disclose potential conflicts to employer before proceeding
Fulfills (2)
  • Legitimate professional interest in maintaining and applying prior expertise
  • Consideration of part-time work that is facially distinct from primary employment domain
Violates (3)
  • Faithful agent and trustee obligation to State DOT employer (NSPE Code III.6.b)
  • Obligation to avoid conflicts of interest (NSPE Code II.4.d)
  • Obligation to avoid conduct that compromises professional integrity or creates appearance of impropriety (NSPE Code II.4.e)
Upon Engineer A's acceptance of the part-time arrangement, a concrete and irresolvable structural conflict of interest comes into existence: Engineer A simultaneously holds regulatory review authority over private engineering firms at the DOT and serves as a paid consultant to one such firm seeking government contracts. This is not merely a risk of conflict but an actual conflict state.
The discussion section establishes as a factual finding that highway and airport infrastructure are operationally interconnected, meaning Engineer A's DOT traffic engineering role and his airport consulting work cannot be cleanly separated into non-overlapping domains. This recognition transforms the perceived scope of the conflict from narrow to systemic.
Should Engineer A proceed with the part-time arrangement, he would be obligated to proactively disclose the dual employment to both the State DOT and the consulting firm, and obtain their informed consent before commencing outside work. This disclosure action is a conditional but ethically mandatory step identified by the BER as a minimum threshold requirement derived from Case 97-1 precedent.
Fulfills (3)
  • Transparency and honesty with employer (NSPE Code III.6.b)
  • Disclosure of potential conflicts of interest (NSPE Code II.4.d)
  • Good faith compliance with Case 97-1 procedural requirements
Violates (2)
  • Underlying conflict of interest obligation remains violated even after disclosure per BER analysis (NSPE Code II.4.e)
  • Faithful agent obligation is not fully cured by disclosure alone given the structural conflict
If dual employment were to proceed, Engineer A would be obligated to continuously monitor his activities in both roles for emerging conflicts of interest and take affirmative steps to address them, including recusal from state highway decisions that could affect municipalities he simultaneously serves as a private consultant. This is an ongoing volitional obligation identified by the BER as a conditional but mandatory professional duty.
Fulfills (3)
  • Proactive conflict-of-interest management (NSPE Code II.4.d)
  • Faithful agent obligation through active recusal and disclosure when conflicts arise (NSPE Code III.6.b)
  • Avoidance of conduct that compromises professional integrity (NSPE Code II.4.e)
Violates (2)
  • BER finds the structural conflict cannot be fully managed through monitoring alone; the underlying ethical violation persists
  • Obligation to avoid placing oneself in a position where conflicts are structurally foreseeable and recurring
Narrative (1 main characters)
View Extraction
Opening Context

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

You are Engineer A, a traffic engineer employed by the State DOT, where your responsibilities include reviewing private engineering firm contracts and traffic signal plans, specifications, and estimates submitted by developers and municipalities for work on the state highway system. Before joining the DOT's traffic engineering division, you worked at a consulting firm doing airport design, and that firm currently performs no traffic signal work on the state highway system. The State DOT funds municipal airport improvements through direct grant agreements with municipalities, provides FAA qualifications-based selection guidelines to those municipalities, but does not contract directly with or select the consultants municipalities hire for airport work. Your former consulting firm has now approached you about working part-time to help solicit municipal airport design contracts, covering master plans and runway extensions, while you remain a full-time DOT employee. Several decisions about how to proceed are before you.

Main characters (1)

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

Engineer A Roles in this case: State DOT Traffic EngineerState DOT Airport Consultant

Tension between Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary and Adjacent Domain Dual Employment Shared-Client Conflict Non-Acceptance Constraint

Attaches to role: State DOT Traffic Engineer

Tension between Cross-Domain Same-Client Conflict Non-Engagement Engineer A Municipal Airport Consulting and Engineer A Cross-Domain Same-Client DOT Highway Airport Municipal Conflict

Attaches to role: State DOT Traffic Engineer

Engineer A's duty to act as a faithful agent and trustee to the State DOT requires undivided professional loyalty and avoidance of any arrangement that compromises DOT interests. Simultaneously, the structural prohibition against a grant-administering government engineer providing private consulting to the very municipal clients receiving those grants creates an irresolvable conflict: even if Engineer A sincerely intends to serve DOT faithfully, the dual role structurally corrupts the integrity of both relationships. Accepting the airport consulting role means Engineer A would privately benefit from municipalities whose grant applications and compliance Engineer A evaluates in a government capacity, making genuine faithful agency to DOT impossible regardless of subjective intent.

Attaches to role: State DOT Traffic Engineer

Engineer A holds a government role that includes disseminating FAA Qualifications-Based Selection guidelines to municipalities, which creates an informational and procedural authority over the consultant selection process. The obligation to preserve QBS selection integrity prohibits any interference with that merit-based process. However, Engineer A's former firm is soliciting Engineer A to become a private airport consultant — the very type of consultant selected through the QBS process Engineer A administers. This creates a direct tension: Engineer A cannot simultaneously protect the integrity of a selection system and position themselves (or be positioned by a former employer) as a beneficiary of that same system, since insider knowledge of QBS procedures and municipal relationships constitutes an unfair competitive advantage that corrupts the process by design.

Attaches to role: State DOT Airport Consultant

Tension between Engineer A Employer Awareness Non-Sufficiency Structural Conflict DOT Airport and State DOT Employer Prior Approval Disclosure Engineer A Airport Consulting Solicitation

Attaches to role: State DOT Traffic Engineer

Tension between Moonlighting Conflict of Interest Multi-Factor Contextual Assessment Before Acceptance Obligation and Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary

Attaches to role: State DOT Traffic Engineer

Engineer A's obligation to refrain from exploiting government grant authority for private consulting gain conflicts with the revolving door ethics constraint triggered by re-engagement with a former employer. The former firm's solicitation of Engineer A is itself ethically suspect because the firm's commercial interest in securing airport consulting contracts is directly served by Engineer A's insider government position — knowledge of which municipalities are receiving grants, what their compliance needs are, and how selection processes work. The revolving door constraint recognizes that re-engagement with a former employer under these conditions transforms Engineer A's government role into a pipeline for private commercial advantage, undermining public trust in both the grant administration system and the engineer's professional independence. Fulfilling the non-exploitation obligation requires refusing the engagement, but the absence of a formal revolving door provision creates ambiguity that the former firm may exploit to pressure Engineer A.

Attaches to role: State DOT Airport Consultant

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

Engineer A holds a government role that includes disseminating FAA Qualifications-Based Selection guidelines to municipalities, which creates an informational and procedural authority over the consultant selection process. The obligation to preserve QBS selection integrity prohibits any interference with that merit-based process. However, Engineer A's former firm is soliciting Engineer A to become a private airport consultant — the very type of consultant selected through the QBS process Engineer A administers. This creates a direct tension: Engineer A cannot simultaneously protect the integrity of a selection system and position themselves (or be positioned by a former employer) as a beneficiary of that same system, since insider knowledge of QBS procedures and municipal relationships constitutes an unfair competitive advantage that corrupts the process by design.

Engineer A's obligation to refrain from exploiting government grant authority for private consulting gain conflicts with the revolving door ethics constraint triggered by re-engagement with a former employer. The former firm's solicitation of Engineer A is itself ethically suspect because the firm's commercial interest in securing airport consulting contracts is directly served by Engineer A's insider government position — knowledge of which municipalities are receiving grants, what their compliance needs are, and how selection processes work. The revolving door constraint recognizes that re-engagement with a former employer under these conditions transforms Engineer A's government role into a pipeline for private commercial advantage, undermining public trust in both the grant administration system and the engineer's professional independence. Fulfilling the non-exploitation obligation requires refusing the engagement, but the absence of a formal revolving door provision creates ambiguity that the former firm may exploit to pressure Engineer A.

Engineer A's duty to act as a faithful agent and trustee to the State DOT requires undivided professional loyalty and avoidance of any arrangement that compromises DOT interests. Simultaneously, the structural prohibition against a grant-administering government engineer providing private consulting to the very municipal clients receiving those grants creates an irresolvable conflict: even if Engineer A sincerely intends to serve DOT faithfully, the dual role structurally corrupts the integrity of both relationships. Accepting the airport consulting role means Engineer A would privately benefit from municipalities whose grant applications and compliance Engineer A evaluates in a government capacity, making genuine faithful agency to DOT impossible regardless of subjective intent.


These tensions did not map cleanly to a single character.

Tension between Cross-Domain Same-Client Government-Private Consulting Non-Engagement Obligation and Adjacent Domain Dual Employment Shared-Client Conflict Non-Acceptance Constraint

Tension between Employer Awareness Non-Sufficiency to Cure Structural Dual-Employment Conflict Obligation and Competitive Employment Freedom Constraint Invoked for Former Firm Solicitation

Potential tension between Employer Awareness Non-Sufficiency to Cure Structural Dual-Employment Conflict Obligation and Cross-Domain Same-Client Government-Private Consulting Non-Engagement Obligation

Opening States (10)
Engineer A Adjacent Domain Dual Employment Conflict - Highways vs. Airports Engineer A Employer-Aware Dual Employment Insufficient Mitigation Engineer A Regulatory Compliance State - FAA QBS Guidelines Former Employer Part-Time Re-Engagement Solicitation State Shared Municipal Stakeholder Dual Role Conflict State Engineer A DOT Employment State Engineer A Adjacent Domain Dual Employment Latent Conflict Engineer A Former Employer Part-Time Re-Engagement Solicitation Engineer A Shared Municipal Stakeholder Dual Role Conflict Engineer A No Formal Revolving Door Prohibition
Summary
  • A government engineer who administers grant relationships with municipalities cannot simultaneously provide private consulting services to those same municipalities, regardless of whether the employer is aware of the dual employment arrangement.
  • Structural conflicts of interest in dual-employment scenarios cannot be cured merely by employer awareness or disclosure alone; the underlying relational architecture itself must be severed.
  • The prohibition on cross-domain same-client engagement extends beyond direct solicitation to encompass any adjacent consulting work where the engineer's governmental role creates an inherent informational or positional advantage over the private client relationship.