Step 4: Full View

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.