Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.
NSPE Code Provisions Referenced
Section II. Rules of Practice 2 88 entities
Engineers shall act for each employer or client as faithful agents or trustees.
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.
Section III. Professional Obligations 2 100 entities
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.
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.
Cross-Case Connections
View ExtractionExplicit 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.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions
View Extraction) while continuing to work as an employee with the State DOT?
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.
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?
The 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.
In 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?
The 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.
In 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.
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?
Beyond 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.
In 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.
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?
The 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.
In 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.
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?
The 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.
In 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.
The 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 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?
In 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.
The 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?
In 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.
The 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.
The 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?
The 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.
In 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.
The 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.
The 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.
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?
In 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 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?
From 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.
In 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?
In 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.
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?
The 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.
In 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.
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?
In 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.
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?
In 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.
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?
In 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.
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?
In 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
View ExtractionCausal-Normative Links 5
- Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary
- Governmental Procedure Policy Compliance Engineer A Dual Employment Outside Work
- Engineer A Governmental Procedure Compliance DOT Airport Dual Employment
- Engineer A Cross-Domain Interrelated Infrastructure Conflict DOT Highway Airport
- Engineer A Cross-Domain Same-Client DOT Highway Airport Municipal Conflict
- Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary
- FAA QBS Consultant Selection Integrity Non-Interference Obligation
- FAA QBS Selection Integrity Non-Interference Engineer A Airport Consultant Solicitation
- Government Grant Authority Non-Exploitation Engineer A Airport Grant Municipalities
- Conflict of Interest Recusal Traffic Signal Review Engineer A Municipal Airport Clients
- Dual Role Appearance of Impropriety Avoidance Engineer A Municipal Overlap
- Engineer A Faithful Agent Trustee DOT Employer Structural Conflict
- Cross-Domain Same-Client Government-Private Consulting Non-Engagement Obligation
- Engineer A Cross-Domain Same-Client DOT Highway Airport Municipal Conflict
- Government Grant Authority Non-Exploitation Private Consulting Solicitation Prohibition Obligation
- State DOT Employer Prior Approval and Disclosure Obligation for Outside Employment
- State DOT Employer Prior Approval Disclosure Engineer A Airport Consulting Solicitation
- Engineer A Professional Liability Awareness DOT Airport Dual Employment
- Dual Employment Professional Liability Risk Awareness Obligation
- Governmental Procedure Policy Compliance Engineer A Dual Employment Outside Work
- Engineer A Governmental Procedure Compliance DOT Airport Dual Employment
- Employer Awareness Non-Sufficiency to Cure Structural Dual-Employment Conflict Obligation
- Engineer A Employer Awareness Non-Sufficiency Structural Conflict DOT Airport
- Conflict of Interest Recusal Traffic Signal Review Engineer A Municipal Airport Clients
- Dual Role Appearance of Impropriety Avoidance Engineer A Municipal Overlap
- Engineer A Moonlighting Multi-Factor Assessment DOT Airport Consulting
- Moonlighting Conflict of Interest Multi-Factor Contextual Assessment Before Acceptance Obligation
- FAA QBS Consultant Selection Integrity Non-Interference Obligation
- FAA QBS Selection Integrity Non-Interference Engineer A Airport Consultant Solicitation
- Government Grant Authority Non-Exploitation Engineer A Airport Grant Municipalities
- Engineer A Government Grant Authority Non-Exploitation DOT Airport Municipalities
- Engineer A Public Resources Non-Use DOT Airport Private Work
- Engineer A Governmental Procedure Compliance DOT Airport Dual Employment
- Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary
- Moonlighting Conflict of Interest Multi-Factor Contextual Assessment Before Acceptance Obligation
- Engineer A Moonlighting Multi-Factor Assessment DOT Airport Consulting
- Cross-Domain Same-Client Government-Private Consulting Non-Engagement Obligation
- Engineer A Cross-Domain Same-Client DOT Highway Airport Municipal Conflict
- Engineer A Cross-Domain Interrelated Infrastructure Conflict DOT Highway Airport
- Dual Role Appearance of Impropriety Avoidance Engineer A Municipal Overlap
- Engineer A Faithful Agent Trustee DOT Employer Structural Conflict
- Employer Awareness Non-Sufficiency to Cure Structural Dual-Employment Conflict Obligation
- Engineer A Employer Awareness Non-Sufficiency Structural Conflict DOT Airport
- Government Grant Authority Non-Exploitation Private Consulting Solicitation Prohibition Obligation
- Engineer A Government Grant Authority Non-Exploitation DOT Airport Municipalities
- FAA QBS Consultant Selection Integrity Non-Interference Obligation
- Conflict of Interest Recusal Traffic Signal Review Engineer A Municipal Airport Clients
Decision Points 6
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
Event Timeline
Causal Flow
- Transition to State DOT Reviewing Private Firm Contracts
- Reviewing Private Firm Contracts Accepting_Part-Time_Moonlighting_Approach
- Accepting_Part-Time_Moonlighting_Approach Disclosing Dual Employment to Employers
- Disclosing Dual Employment to Employers Monitoring and Addressing Emerging Conflicts
- Monitoring and Addressing Emerging Conflicts Prior Airport Design Experience Accumulated
Opening Context
View ExtractionYou 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.
Characters (7)
A precedent engineer whose permissible moonlighting arrangement — characterized by full mutual employer awareness and an absence of client or subject-matter overlap — establishes the ethical baseline against which Engineer A's more conflicted situation is unfavorably distinguished.
- Motivated to expand professional engagement and income while operating transparently within ethical boundaries, serving as the compliant counterexample that highlights where Engineer A's situation diverges.
- Motivated by professional opportunity and financial gain, but structurally unable to serve both principals without compromising his faithful agent obligations to his public employer.
- Motivated to maintain regulatory integrity, public trust, and impartial contract oversight, with an institutional interest in ensuring its engineers remain undivided in their professional loyalty.
- Likely motivated by supplemental income and professional continuity with his former firm, while underestimating or rationalizing the ethical exposure created by his dual-client overlap.
The State DOT employs Engineer A as a traffic engineer and contracts with municipalities via grant agreements for airport improvements. It also receives traffic signal plans and contracts from municipalities and developers for review, making it the public employer whose interests Engineer A must faithfully serve.
State highway employee who was solicited by a former employer to perform part-time airport consulting for municipalities that also interact with his state DOT employer on highway matters; the Board finds a violation of the NSPE Code based on conflict-of-interest and faithful agent/trustee obligations.
Precedent engineer from BER Case 97-1 who held a full-time government agency position while also employed part-time by a private engineering firm; cited to establish the general ethical framework for moonlighting engineers where both employers are aware and no conflict exists.
Engineer A's former consulting engineering firm, which currently does no traffic signal work in the state highway system, approaches Engineer A to perform part-time airport design consulting work for municipalities that also interact with Engineer A's current DOT employer on highway matters.
Municipalities submit traffic signal plans and contracts to Engineer A's DOT division for review, and separately receive state DOT grant funding for airport improvements for which they independently hire consultants. Their dual relationship with the DOT — as regulated entities on highways and as grant recipients for airports — is central to the conflict-of-interest analysis.
Private developers submit traffic signal plans, specifications, and estimates to Engineer A's DOT division for review as part of state highway system work. They are regulated entities whose submissions Engineer A evaluates in his public role.
Tension between Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary 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
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 Moonlighting Conflict of Interest Multi-Factor Contextual Assessment Before Acceptance Obligation and Faithful Agent DOT Employer Loyalty Engineer A Private Consulting Boundary
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
Tension between Engineer A Employer Awareness Non-Sufficiency Structural Conflict DOT Airport and State DOT Employer Prior Approval Disclosure Engineer A Airport Consulting 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
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.
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.
Opening States (10)
Key Takeaways
- 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.