Step 4: Review

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.

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.

Cited to discuss the general ethical framework for engineer moonlighting cases involving dual employment, noting that no violation was found where both employers were aware of and did not object to the dual role, but distinguishing the present facts due to the foreseeable conflict of interest between the engineer's state highway duties and private airport consulting work involving the same municipalities.

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.

The Board's finding of unethical conduct rests primarily on the appearance of conflict rather than a demonstrable direct conflict, since the State DOT has no formal role in selecting or contracting with municipal airport consultants. This suggests that Engineer A's dual role would be problematic even absent any concrete instance of him reviewing his own or his firm's work, because his position as a DOT employee inherently creates a perception that municipalities dependent on DOT airport grants might favor his firm to maintain goodwill with the funding agency. This appearance-based rationale extends beyond the specific facts of plan review overlap and implicates the broader public trust dimension of the engineering profession.

Even though Engineer A's traffic signal review duties and airport consulting work are technically distinct engineering functions, the Board's conclusion implicitly recognizes that Engineer A's institutional identity as a DOT employee cannot be functionally separated from his private consulting identity in the eyes of municipalities. Municipalities that deal with Engineer A in his DOT capacity (e.g., for traffic signal matters) and simultaneously as a private airport design consultant may reasonably perceive an entanglement of interests, regardless of whether the specific contracts or reviews overlap. This suggests the faithful agent duty under II.4 extends to safeguarding the integrity of the employer-employee relationship as a whole, not merely to avoiding conflicts within a single narrow task.

The Board's conclusion leaves unaddressed whether disclosure to the State DOT of the part-time consulting offer, prior to acceptance, could have mitigated the ethical concern or whether the conflict is so inherent to the dual role that no disclosure could cure it. Given that II.4.a. requires disclosure of known or potential conflicts of interest, the Board's silence suggests that in this case, the conflict is treated as categorically incompatible with continued DOT employment, rather than as a disclosable and manageable risk, implying that disclosure alone is an insufficient remedy for certain classes of overlapping public-private engineering roles.

Even though the State DOT has no formal contractual role in selecting municipal airport consultants, Engineer A's dual position creates an appearance of influence: municipalities depend on State DOT grant funding for airport projects, and Engineer A's visible status as a State DOT employee could be perceived by municipal officials as carrying implicit institutional weight or insider advantage for his former consulting firm. This appearance-based risk is sufficient to trigger conflict-of-interest concerns even absent any formal selection authority.

Consistent with the disclosure duty in II.4.a., Engineer A should have disclosed the part-time consulting offer to the State DOT before accepting it, rather than relying on the technical absence of a direct contractual link between DOT and municipal airport consultants. Disclosure would allow the employer to assess potential conflicts proactively rather than after relationships with municipalities have already formed, and reliance on the technicality does not discharge the affirmative disclosure obligation.

Although traffic signal review and airport design are technically distinct engineering functions, Engineer A's continuing duty to impartially review outside firms' traffic signal contracts for municipalities creates a risk of blurred loyalties if some of those same municipalities become his private airport-design clients. The overlap in the municipal client base, even across different project types, undermines the perception of undivided faithful agency owed to the State DOT.

Beyond formal decision-making authority, Engineer A's DOT position likely affords him privileged insight into grant funding timing, priorities, and municipal infrastructure needs. Such informational advantages, even if never formally shared, could improperly benefit his private consulting pursuits and constitute a subtler but still real conflict of interest not captured by analysis focused solely on contractual authority.

From a deontological standpoint, Engineer A's plan to pursue part-time airport consulting while remaining a State DOT employee violates the duty to avoid conflicts of interest under II.4 and II.4.a. as a matter of principle, independent of whether actual harm or plan-review overlap ever materializes. The duty is triggered by the structural possibility of divided loyalty, not by proof of consequent injury.

From a consequentialist perspective, the fact that Engineer A would never actually review his former firm's airport plans (since DOT does not review municipal airport consultant contracts) does not fully justify permitting the dual role, because the harm at issue is reputational and systemic (erosion of public trust in the impartiality of DOT engineers) rather than solely transactional. The absence of direct plan-review conflict mitigates but does not eliminate the ethical concern.

Viewed through a virtue-ethics lens, Engineer A's willingness to seriously entertain the part-time consulting role—despite owing impartial oversight duties to municipalities funded by his own agency—reflects a lapse in the professional virtue of prudence and integrity, since a virtuous engineer would recognize the conflict potential and decline or seek clearance before any actual plan-review conflict arose.

If Engineer A's former consulting firm currently performed traffic signal work on the state highway system, the Board's finding would rest on a clearer, direct faithful-agent violation, since Engineer A would then be reviewing plans submitted by a firm he simultaneously assists in seeking other municipal contracts—an unambiguous conflict rather than one resting primarily on appearance.

If the State DOT were directly involved in selecting or contracting with municipalities' airport consultants, the Board's conclusion would shift from an appearance-of-conflict finding to a finding of actual, direct conflict of interest, since Engineer A's dual role would then place him in a position to influence or benefit from decisions affecting his own private client relationships.

If Engineer A had no prior employment relationship with the approaching firm, the conflict-of-interest concern would be somewhat weakened, since the loyalty tie to a former employer would be absent; however, the core structural conflict—simultaneous private airport consulting for municipalities that receive State DOT grant funding while employed by the DOT—would likely still be regarded as ethically problematic under II.4 and III.6.b.

The Board resolved the tension between Engineer A's right to pursue permissible outside employment and his Faithful Agent Loyalty in Dual Employment to the State DOT by subordinating the former to the latter: even though III.1.c and III.6.b generally permit part-time work, the appearance-based Conflict of Interest in Municipal Relations was treated as controlling whenever the private client base (municipalities) overlaps with populations affected by the engineer's public duties, regardless of whether the two roles technically intersect.

The case demonstrates that appearance of impropriety functions as an independent, freestanding ground for a conflict-of-interest finding, capable of overriding a strictly formalist reading of authority. Despite the state's non-involvement in municipal airport consultant selection, the Board prioritized the perception that Engineer A's dual DOT/consultant status could improperly influence or appear to influence municipalities dependent on DOT grant funding, showing that the Faithful Agent principle incorporates duties of perceived as well as actual loyalty.

This case illustrates a prioritization rule for engineers in dual public/private roles: when a conflict-of-interest concern and a permissible-outside-employment principle collide, the disclosure obligation under II.4.a should have been treated as a necessary precondition rather than an optional courtesy—Engineer A's failure to proactively disclose the offer to DOT before evaluating or accepting it meant the Faithful Agent principle was never given the chance to be reconciled with his outside employment rights.

Would it be ethical 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?

Even though the State DOT has no formal role in selecting airport consultants, does Engineer A's position give the former consulting firm an unfair advantage or the appearance of influence over municipalities that depend on DOT grant funding?

Should Engineer A be required to disclose to the State DOT the part-time consulting offer and any resulting relationships with municipalities before accepting the work, rather than relying on the absence of a direct contractual link between DOT and the airport consultants?

Does Engineer A's ongoing role reviewing outside firms' traffic signal contracts and plans for the State DOT create a risk of blurred loyalties when some of the same municipalities may also be his private airport-design clients, even though the two engineering functions (traffic signals vs. airport design) are technically distinct?

What internal knowledge or influence might Engineer A possess from his DOT position (e.g., about grant timing, funding priorities, or municipal needs) that could improperly benefit his private consulting pursuits, independent of any formal decision-making authority?

How should Engineer A's Faithful Agent Loyalty in Dual Employment to the State DOT be balanced against his personal and professional right to pursue permissible part-time engineering work under the Code's provisions on outside employment?

Does the Conflict of Interest in Municipal Relations principle come into direct tension with Faithful Agent Loyalty in Dual Employment when the same municipalities that receive State DOT airport grants would also be Engineer A's private clients, even though DOT itself does not select or contract with the airport consultants?

How should the appearance-of-impropriety concern embedded in Conflict of Interest in Municipal Relations be weighed against the technical absence of any formal state involvement in municipal consultant selection?

From a deontological perspective, did Engineer A's plan to pursue part-time airport consulting work while remaining a faithful agent of the State DOT violate the duty to avoid conflicts of interest under II.4 and II.4.a, regardless of whether any actual harm occurred?

From a consequentialist perspective, would the practical outcome that Engineer A never actually reviews his former firm's airport plans (since the DOT does not review municipal airport consultant contracts) justify permitting the dual role despite the appearance of conflict?

Did Engineer A act with professional integrity, in a virtue-ethical sense, by seriously entertaining a part-time consulting role with the same municipalities his agency funds and to which he owes duties of impartial oversight, even before any actual plan review conflict materialized?

If Engineer A's former consulting firm currently performed traffic signal work on the state highway system (rather than none), would the Board's finding of unethical conduct rest on an even clearer, direct violation of the faithful agent duty rather than primarily on appearance of conflict?

If the State DOT were directly involved in selecting or contracting with municipalities' airport consultants (rather than only funding via grant agreements without involvement in consultant selection), would the Board's conclusion shift from an appearance-of-conflict finding to a finding of an actual, direct conflict of interest?

If Engineer A had never previously worked for the consulting firm (i.e., the approach came from an entirely unfamiliar firm with no prior employment relationship), would the Board still find the dual-role arrangement unethical, or would the absence of a prior loyalty tie weaken the conflict-of-interest concern?

Engineer A's prior consulting employment set up the ongoing relationship that later led the firm to extend a part time offer, so although it carries no normative weight itself, it is the seed of the conflict that eventually surfaces downstream.

Accepting public employment placed Engineer A under the Faithful Agent and Trustee duty to the state, and this obligation is precisely what guided the later contract plan review, making the acceptance the normative starting point for everything that follows in the public role.

The part time employment offer, caused by the prior consulting relationship, is the direct antecedent that made dual employment possible, so its significance lies entirely in enabling the subsequent conflict rather than in any obligation of its own.

Because the contract plan review was performed under and fulfilled the Faithful Agent and Trustee duty owed from public employment, it represents Engineer A properly discharging public responsibilities even as the same engineer was simultaneously engaged in outside work that would soon conflict with that duty.

Accepting dual employment violated the Faithful Agent and Trustee obligation and directly caused the conflict potential to emerge, which combined with the state's grant agreement to produce the eventual ethics violation finding, showing how this single choice cascades into the case's central wrongdoing.

The question arose because Engineer A's proposed private consulting work directly overlaps with the subject matter and municipal relationships connected to his public employer's grant program, creating a structural risk of divided loyalty even though no actual misconduct has occurred yet.

The question arose because the structural separation between DOT's grant role and its lack of formal consultant selection authority creates a gap where actual conflict of interest and perceived conflict of interest diverge, forcing scrutiny of whether appearance alone triggers an ethical violation.

The question arises because the absence of a formal contractual tie between DOT and the airport consultants creates a technical defense against disclosure, even though the underlying faithful agent principle suggests a broader duty to reveal potential conflicts before they materialize.

The question arises because Engineer A's regulatory review authority and his private consulting client base intersect at the level of the same municipalities, even though the subject matter differs, raising an appearance of conflict that the formal job description does not resolve.

The question arises because Engineer A occupies a dual position where his day job as a DOT traffic engineer intersects informationally with municipal airport grants that could feed his private consulting opportunities, creating an appearance of conflict even absent formal authority.

The question emerged because Engineer A's public DOT position and his prospective private consulting role both touch on transportation infrastructure funded partly through DOT grants, creating a factual overlap that makes the boundary between permissible outside work and disloyal dual employment ambiguous.

The question arises because Engineer A's dual employment creates an overlapping client relationship between his public and private roles, and it is unclear whether the absence of direct DOT involvement in consultant selection is enough to dissolve the conflict of interest concern or whether the mere appearance of entanglement is sufficient to violate faithful agency.

The question arises because the State DOT Airport Grant Agency ties Engineer A's public duties to the same municipal clients his private consulting would serve, creating a structural appearance problem that persists even though no formal state authority governs the municipal consultant selection process itself.

The question arose because the deontological duty to avoid conflicts of interest is stated categorically in the Code, yet the facts show no demonstrated harm or actual overlap in decision making, forcing a determination of whether the mere structural potential for conflict, independent of consequences, is itself sufficient to constitute a violation.

The question arises because the absence of a formal review mechanism satisfies a narrow procedural safeguard, yet it does not resolve the broader ethical warrant requiring undivided loyalty and avoidance of even the appearance of conflict, creating tension between outcome-based and duty-based justifications.

The question arose because virtue ethics asks about character and appearance rather than only actual harm, so the mere consideration of a role with entities the engineer oversees raises integrity concerns independent of whether a concrete conflict ever occurs.

The question emerges because the Board's finding rests on the specific fact that the consulting firm was outside the traffic signal review scope, and altering that fact would shift the ethical violation from an appearance based judgment to a direct faithful agent breach.

This question arose because the Board's appearance-of-conflict conclusion rests specifically on State Consultant Selection Non-Involvement, so altering that factual predicate tests whether the warrant justifying a lesser appearance-based finding still applies.

The question arises because the original case combines two distinct sources of ethical risk, an existing loyalty tie from prior employment and an inherent dual role conflict, and it is unclear which of these the Board's warrant actually rests on, so removing one variable tests whether the ethical judgment would change.

Given that Engineer A's prospective municipal clients depend on State DOT grant funding for airport projects, the board concluded that continuing DOT employment while pursuing the part-time consulting arrangement created an unacceptable conflict of interest under the faithful agent standard, regardless of the absence of direct contractual overlap.

Because DOT's grant relationship with municipalities could reasonably be perceived as giving Engineer A's firm insider advantage, the board found the appearance of conflict alone sufficient to sustain an unethical conduct finding, independent of any concrete instance of self-review.

Even though traffic signal review and airport design are technically distinct, the board reasoned that because the same municipalities could encounter Engineer A in both roles, his faithful agent duty extends to protecting the overall integrity of the DOT relationship rather than being confined to task-specific conflicts.

Because the board never addressed whether disclosing the consulting offer to DOT beforehand would resolve the ethical issue, its silence suggests that in this case the dual role was viewed as inherently incompatible, treating disclosure as insufficient rather than as a curative step.

Given that municipalities rely on DOT airport grants and Engineer A's DOT employment was visible to them, the board concluded that this visibility alone created a sufficient appearance of influence to raise conflict-of-interest concerns, even without any formal selection role for DOT.

Given that Engineer A's DOT role involves grant relationships with municipalities and he received a consulting offer touching those same municipalities, the board concluded he should have disclosed the offer beforehand rather than resting on the technicality that DOT does not directly contract with airport consultants.

Given that Engineer A's plan-review duties for traffic signals and his prospective airport consulting could both involve the same municipalities, the board concluded that the risk of blurred loyalties survives even though the two project types are technically unrelated.

Given that Engineer A's DOT role affords him insider knowledge of grant timing and municipal needs, the board concluded that this informational asymmetry creates a conflict of interest not captured by analysis limited to his formal authority.

Given that Engineer A's plan to hold dual roles created a structural possibility of divided loyalty, the board concluded from a deontological standpoint that the conflict-of-interest duty was violated as a matter of principle, independent of whether any harm actually occurred.

Given that DOT does not review municipal airport consultant contracts, the board acknowledged the absence of a direct plan-review conflict but concluded from a consequentialist view that the reputational and systemic harm to public trust in DOT impartiality still justified concern.

Given that Engineer A owed impartial oversight duties to the very municipalities he was considering as private clients, and that he entertained the offer without seeking clearance, the board concluded through a virtue-ethics lens that this reflected a lapse in prudence and integrity rather than a violation requiring actual harm.

Because in the actual case the former firm did no traffic signal work subject to Engineer A's review, the board's finding rested on appearance, but reasoned that if such work existed the same facts would establish an unambiguous direct conflict.

Since the State DOT's role in the actual case is limited to grant funding without consultant-selection involvement, the board treated the issue as an appearance-of-conflict, but reasoned that direct DOT involvement in consultant selection would convert this into an actual conflict.

Because Engineer A had a prior employment tie to the approaching firm in the actual case, the board treated this as reinforcing the conflict, but reasoned that even without such a tie the structural overlap between private airport clients and DOT-funded municipalities would likely still raise ethical concerns.

Given that the municipalities Engineer A sought as clients also received State DOT grant funding tied to his employer, the board concluded that the appearance-of-conflict concern controlled over the generally permissive outside-employment provisions, even though no direct contractual link between DOT and the airport consultants existed.

Given that municipalities rely on DOT grants and Engineer A's former firm sought his help winning their airport work, the Board concluded that the mere perception of leverage over grant-dependent municipalities was enough to find a conflict, even though DOT formally plays no role in selecting airport consultants.

Because Engineer A evaluated and moved toward accepting the consulting offer without first informing DOT, the Board concluded that his outside-employment right could not be exercised faithfully, since the Code makes disclosure a precondition for permissible dual employment rather than a discretionary afterthought.

Should Engineer A accept the part-time consulting offer to seek municipal airport-design contracts while continuing his State DOT employment, or decline it?

Should Engineer A disclose the part-time consulting offer to the State DOT before accepting it, or proceed without disclosure since DOT has no formal role in selecting airport consultants?

Should Engineer A recuse himself from plan-review duties involving municipalities that are also his private airport-consulting clients, or continue the standard review process for all municipalities?

Should Engineer A proceed with the dual role by relying on DOT's formal non-involvement in municipal consultant selection, or withdraw because of the appearance of influence over grant-dependent municipalities?

Should Engineer A maintain a strict firewall against using DOT-derived knowledge of grant timing and municipal priorities in his private consulting work, or treat such knowledge as ordinary professional experience he may freely use?