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 disclose, without consent, confidential information concerning the business affairs or technical processes of any present or former client or employer, or public body on which they serve.

Engineers shall not, without the consent of all interested parties, promote or arrange for new employment or practice in connection with a specific project for which the engineer has gained particular and specialized knowledge.

Cited to illustrate a situation where an engineer's part-time consulting role for municipalities did not create divided loyalties, providing context for analyzing conflicting obligations to different clients.

Cited as an example where an engineer could not switch sides to represent an opposing party's interests without the former client's consent, illustrating the duty of loyalty and confidentiality to former clients.

Cited at length to explain that an engineer's ethical obligation of confidentiality and loyalty to a former client persists even after the professional relationship ends, and that merely terminating a relationship or claiming independence does not resolve the conflict of interest.

Engineer A is free to pursue employment with Company Y provided Engineer A does not disclose any confidential and proprietary design information Engineer A learned about Company X during Engineer A’s employment with the government agency and makes this obligation clear to Company Y before accepting employment.

The Board's conditional approval implies that Engineer A's confidentiality obligation to Company X survives indefinitely and is not tied to her employment status with the government agency—her duty attaches to the information itself, not to the employment relationship through which she acquired it. This means the passage of time alone does not extinguish the obligation; only changes in the underlying facts (e.g., the information becoming public, obsolete, or Company X consenting to disclosure) would alter her duty.

The Board's conclusion, while framed around disclosure, leaves unaddressed the more subtle risk of inadvertent or unconscious application of Company X's confidential design knowledge in Engineer A's work at Company Y. Because engineering judgment often draws on internalized expertise rather than discrete recallable facts, mere non-disclosure may be insufficient to fully insulate Company X's proprietary interests. This suggests that Company Y bears a shared responsibility to establish information barriers or project-assignment safeguards, and Engineer A may need to voluntarily recuse herself from projects that closely parallel Company X's submitted designs, even without any deliberate act of disclosure.

The Board's conditional permission reveals an inherent structural tension in Engineer A's new role: her duty as a faithful agent to Company Y (to apply her full expertise and knowledge in its interest) is fundamentally limited by her prior confidentiality obligation to Company X. This is not a tension the Board resolves through elimination but through prioritization—confidentiality duties arising from a prior fiduciary relationship take precedence over, and thus permissibly constrain, the scope of faithful service owed to a new employer. Company Y's acceptance of Engineer A's disclosure of this obligation before hiring her effectively means Company Y consents to a limited, rather than unconditional, faithful agency.

Regarding Q101, Engineer A's duty of confidentiality toward Company X's design information is best understood as indefinite rather than time-limited. The obligation under III.4 arises from the sensitive nature of the information itself, not from the duration of Engineer A's employment relationship with the government agency. Unless Company X's information becomes public knowledge or Company X consents to its release, the duty persists throughout Engineer A's career, including her tenure at Company Y and any subsequent employer.

In response to Q102, practical safeguards Company Y should consider include establishing an information barrier (ethical wall) that excludes Engineer A from projects directly overlapping with Company X's submissions, requiring her to sign a written acknowledgment of her confidentiality obligations, and instituting internal review protocols to verify that her design recommendations rely only on independently developed or publicly available information rather than knowledge gained from her government role.

On Q103, the Board's conclusion does not indicate any obligation for Engineer A to notify the government agency or Company X of her move to a competitor. Her ethical duty runs to protecting the confidentiality of the information itself, not to alerting the original submitting party about her subsequent employment. This is consistent with the precedent in BER Case No. 85-4, where the obligation was framed around nondisclosure rather than notification.

Regarding Q104, while the Board did not explicitly require recusal, a reasonable extension of its reasoning suggests that Engineer A should voluntarily withdraw from specific Company Y projects that closely parallel or directly compete with designs she reviewed at the government agency. Such recusal would reduce the risk of inadvertent disclosure and reinforce her faithful agent duty to both employers.

From a deontological perspective (Q301), Engineer A fulfills her duty of confidentiality not because of any ongoing contractual relationship with the government agency, but because confidentiality is a role-based moral obligation that survives the termination of employment. Kantian reasoning would hold that treating confidential information as disclosable simply because the employment relationship ended would fail to universalize as a rule, since it would undermine the trust necessary for any regulatory submission process to function.

On Q302, a consequentialist evaluation of the Board's conditional approval would depend on downstream outcomes rather than intent. If Engineer A's presence at Company Y later resulted in demonstrable harm to Company X's competitive position through inadvertent disclosure, the initial ethical justification for permitting her employment would be undermined in hindsight, even though the decision was reasonable given the information available at the time of her hiring.

Regarding Q303, Engineer A's proactive disclosure to Company Y before accepting employment reflects a virtue-based conception of professional integrity that exceeds the minimal requirements of the Code. Although II.4.a. only requires disclosure of conflicts that could influence judgment, Engineer A's voluntary transparency demonstrates the kind of conscientious conduct the Code aims to encourage among faithful agents.

In response to Q401, if Company X had explicitly consented to disclosure of its confidential design information to Company Y, the ethical constraint underlying the Board's conclusion would no longer apply, since III.4. explicitly conditions the confidentiality obligation on the absence of consent. In that scenario, Engineer A's employment with Company Y would be unconditionally permissible without the disclosure caveat.

On Q402, had Engineer A moved to a non-competing firm, the practical risk of harm from disclosure would be substantially reduced, but the underlying confidentiality obligation under III.4. would remain unchanged in principle, since the duty is tied to the sensitivity of the information rather than the competitive relationship between employers. The Board would likely still caution against disclosure, though the urgency and scrutiny attached to the conditional approval would probably be diminished.

Regarding Q403, if Engineer A had never actually accessed Company X's confidential submissions during her government tenure, there would be no confidentiality obligation to protect, and the Board's conditional approval—premised on the existence of such knowledge—would be unnecessary. Her employment with Company Y would then raise no distinct ethical issue beyond ordinary conflict-of-interest considerations.

The Board resolves the apparent conflict between Employment Mobility and Loyalty to Former Employer and Clients not by subordinating one to the other, but by making mobility conditional on continued confidentiality. Engineer A retains the right to pursue employment with a competitor, but that right is bounded by a persisting duty that survives the termination of the original employment relationship. This shows that mobility and confidentiality are treated as compatible rather than mutually exclusive principles, provided the engineer actively manages the boundary between them through disclosure to the new employer.

Conflict of Interest Avoidance is not treated as an absolute bar to working for a direct competitor; rather, the Board implicitly prioritizes behavioral safeguards (non-disclosure, transparency with the new employer) over structural avoidance (refusing the job). This indicates that in the Board's framework, conflict of interest concerns are satisfied through conduct-based mitigation rather than categorical exclusion, meaning the mere appearance of conflict from working for a competitor does not override Engineer A's employment mobility so long as confidentiality is preserved.

The Faithful Agent Duty owed to Company Y and the Confidentiality obligation owed to Company X are reconciled by scoping the faithful agent duty: Engineer A can fully serve Company Y using her general engineering skill and knowledge, but must exclude a specific subset of information (Company X's confidential design details) from that service. This demonstrates that loyalty to a new employer is not unlimited—it is implicitly bounded by pre-existing confidentiality obligations, meaning faithful agency is defined relative to permissible information use, not absolute knowledge transfer.

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

How long does Engineer A's duty of confidentiality regarding Company X's design information persist after leaving the government agency—does it expire, or is it indefinite?

What practical safeguards or information barriers should Company Y implement to ensure Engineer A does not inadvertently apply or disclose Company X's confidential information while working on competing projects?

Did Engineer A have any obligation to notify the government agency or Company X about her move to a competitor, given her prior access to their confidential submissions?

Should Engineer A recuse herself from specific projects at Company Y that directly involve or compete against designs she reviewed as a government employee, even absent explicit disclosure of information?

How should Engineer A's right to Employment Mobility be balanced against her ongoing duty of Loyalty to Former Employer and Clients, particularly regarding Company X's confidential information?

Does Conflict of Interest Avoidance by Engineer A conflict with her Employment Mobility, given that any position at a direct competitor like Company Y inherently raises appearance-of-conflict concerns even without actual disclosure?

How can Engineer A reconcile her Faithful Agent Duty to Company Y with the Confidentiality of Company X Design Information, if fully serving Company Y's design efforts might tempt or require drawing on knowledge gained from Company X?

Is there an inherent tension between Confidentiality of Company X Information and Engineer A's new Loyalty Duty to Company Y, since full loyalty to a new employer could implicitly pressure her to share competitive insights?

From a deontological perspective, did Engineer A fulfill her duty of confidentiality to Company X despite no longer being employed by the Government Agency?

Would the outcome of Engineer A accepting employment with Company Y still be justified from a consequentialist standpoint if Company X's competitive position were harmed by inadvertent disclosures over time?

Did Engineer A act with professional integrity by proactively informing Company Y of her confidentiality obligations before accepting employment, even though not explicitly required to volunteer this at the time of the job offer?

If Company X had consented to Engineer A's disclosure of its confidential design information to Company Y, would the Board's conclusion restricting Engineer A's conduct still apply?

If Engineer A had moved to a non-competing firm rather than Company Y, a direct competitor of Company X, would the Board still have imposed the same confidentiality-disclosure conditions on her employment?

If Engineer A had never had actual access to Company X's confidential design submissions during her government tenure, would the Board's conditional approval of her employment with Company Y still be necessary?

Engineer A's acceptance of government employment set up the causal chain leading to access of confidential information, meaning this initial action carries downstream normative weight even though it was not itself judged as fulfilling or violating any duty.

Company X's submission of confidential information to the government office directly caused the confidential information access that later became ethically significant, making this action a necessary precondition for the eventual adjudication conflict even though it is not itself assessed against a duty.

The termination of Engineer A's government employment causally enabled the acceptance of the competitor position, which later fed into the compromised board adjudication decision, so this transitional action matters as the link connecting prior government access to the later conflict of interest.

Accepting the competitor position was guided by the duty to be a faithful agent and trustee and to avoid the appearance of influenced judgment, which matters because this action combined with prior confidential information access to causally produce the adjudication decision that risked misusing that access.

The board adjudication decision fulfilled the duty of nondisclosure of former employer confidential information and was guided by faithful agency and confidentiality obligations, which is significant because it was the direct downstream product of both the earlier confidential access and the competitor position acceptance, showing Engineer A ultimately upheld nondisclosure despite the conflicted circumstances leading to that decision.

The question emerged because Engineer A's career move from a regulatory position with access to a competitor's confidential data into employment with that competitor creates a direct clash between confidentiality obligations to Company X and Engineer A's personal and professional right to change employers.

The question arises because the NSPE Code and BER precedents establish that confidentiality duties survive employment changes, but they do not specify a temporal boundary, leaving the Board uncertain whether the obligation is indefinite or bounded by practical relevance.

The question emerges because the transition of an engineer holding confidential information into a competitor's employ creates a practical gap between abstract confidentiality obligations and concrete organizational measures needed to enforce them.

The question arose because Engineer A's dual role history, first as a government engineer with access to Company X's confidential data, then as an employee of Company X's competitor, creates an unresolved tension between confidentiality obligations and the general principle of employment mobility, with no clear rule dictating whether disclosure to prior parties is required.

The question arises because Engineer A's career transition creates a structural conflict of interest that the NSPE Code and prior BER precedents address only through general principles, leaving unclear how far confidentiality duties extend when explicit disclosure is absent and duty duration is uncertain.

The question arises because a single career transition creates two legitimate but conflicting obligations, personal employment freedom versus continuing duty to a former employer's confidential information, and no clear rule specifies how long or how strictly the loyalty duty persists after employment ends.

The question arises because the facts of her employment transition satisfy the conditions for two competing obligations, loyalty and confidentiality on one hand and free employment mobility on the other, without a clear rule resolving which takes precedence when only an appearance of conflict exists.

The question arises because Engineer A's transition between employers created a situation where two legitimate obligations, loyalty to a current employer and confidentiality to a former one, point toward different actions regarding the same body of knowledge.

The question emerged because Engineer A's employment transition placed her under two simultaneous obligations whose demands could conflict, prompting the Board to examine whether new employer loyalty implicitly pressures disclosure of prior confidential knowledge.

The question arises because Engineer A's transition from a regulatory role with access to Company X's confidential submissions to a competitor position exposes a gap in the NSPE Code between duty grounded in employment status and duty grounded in the information itself, leaving unclear which warrant should govern her post-employment conduct.

The question arose because the ethical judgment about Engineer A's job acceptance was originally framed around foreseeable consequences, but the possibility of delayed or inadvertent harm to Company X exposes the fragility of consequentialist justification when outcomes are uncertain at the time of decision.

The question emerged because Engineer A's transition between employers with overlapping business interests placed her confidentiality obligations and her faithful agent obligations into direct contact, and the absence of an explicit rule mandating disclosure at the offer stage left it unclear whether her voluntary action exceeded, met, or was irrelevant to her ethical duties.

The question emerges because the Board's original ruling assumed lack of consent as a factual predicate for finding Engineer A's conduct improper, and altering that predicate (introducing consent) forces reexamination of whether the same warrant (confidentiality duty) still authorizes the same conclusion.

The question arises because the Board's imposition of confidentiality conditions could be justified either by the general duty to protect former employer information (which would apply regardless of new employer) or by heightened conflict of interest concerns specific to competitor employment (which would not apply if Engineer A joined a non-competing firm), and the case facts do not clarify which warrant actually drove the Board's decision.

The question arises because the Board's conditional approval rests ambiguously on either the fact of confidential access (a data-dependent warrant) or the structural conflict created by moving from regulator to competitor employee (a role-dependent warrant), and stripping away the access fact exposes which warrant is actually doing the work.

Given that Engineer A possessed confidential Company X information from her government role and sought employment at a competitor, the Board concluded that mobility could proceed only if confidentiality was preserved and disclosed as a condition to the new employer.

Because the duty under III.4 is grounded in the nature of the information rather than the employment status that produced it, the Board concluded that Engineer A's obligation persists indefinitely unless the underlying facts about the information's secrecy change.

Given that expertise can be applied unconsciously and that Engineer A may be placed on competing projects, the Board's silence on this risk implies that non-disclosure alone is insufficient and that Company Y and Engineer A should adopt additional barriers or recusal.

Because Engineer A's confidentiality duty to Company X predates and outweighs her new duty to Company Y, and because Company Y accepted her employment with that restriction disclosed, the Board treated her faithful agency to Company Y as inherently and legitimately limited.

Given that the duty under III.4 attaches to the information itself and that no public disclosure or consent occurred, the Board concluded that Engineer A's confidentiality obligation persists across her tenure at Company Y and any future employer, constraining but not eliminating her employment mobility.

Given that Engineer A moved to a direct competitor while holding confidential knowledge from her government role, the board concluded that practical barriers, acknowledgment, and review protocols were needed to prevent inadvertent disclosure without forcing her out of the position entirely.

Because BER 85-4 anchors the obligation in nondisclosure rather than notification, the board concluded that Engineer A had no duty to alert the agency or Company X about her move to Company Y, even though she held their confidential information.

Since certain Company Y projects directly paralleled designs Engineer A had reviewed as a government employee, the board reasoned that voluntary recusal from those specific projects would better serve her faithful agent duty, even though it stopped short of requiring it outright.

Given that Engineer A's government employment had ended but the confidentiality obligation was treated as role-based rather than contractual, the board concluded she still fulfilled her duty by keeping the information secret, since a Kantian rule permitting disclosure upon employment termination would undermine trust in the regulatory submission system.

Because the board's approval was conditional and based only on information available at the time of hiring, a consequentialist evaluation would judge that approval as ultimately undermined if later evidence showed real harm to Company X, even though it was reasonable when first made.

Given that Engineer A disclosed her prior access to Company X's information before accepting Company Y's offer, and given that the Code's II.4.a. only mandates disclosure of conflicts that could influence judgment, the board concluded her proactive step reflected conscientious professionalism exceeding minimal compliance.

Because III.4. textually conditions the nondisclosure duty on the absence of consent, the board reasoned that explicit consent from Company X would remove the predicate for the confidentiality constraint, making Engineer A's employment unconditionally permissible in that hypothetical.

Given that Company Y is a direct competitor in the actual facts, and given that the board reasoned confidentiality duties attach to information sensitivity rather than market rivalry, it concluded that a move to a non-competing firm would lessen practical risk without eliminating the underlying obligation.

Because the board's conditional approval rested on Engineer A having actually reviewed Company X's confidential submissions, it reasoned that in the absence of such access there would be no confidentiality obligation to protect, leaving only ordinary conflict-of-interest concerns.

Given that Engineer A's duty of confidentiality persists beyond her government tenure, and given that she disclosed this obligation to Company Y before accepting the position, the board concluded that mobility and confidentiality could coexist as compatible principles rather than requiring one to yield to the other.

Given that Engineer A had not disclosed any confidential information and her move to a competitor created only an appearance of conflict rather than an actual breach, the Board concluded that conflict of interest concerns could be satisfied through nondisclosure and transparency rather than by barring the job outright, a conclusion that would reverse if actual disclosure or unavoidable use of Company X's information occurred.

Because Engineer A's knowledge base separates into general engineering competence and Company X specific confidential details, the Board concluded she could act as a faithful agent to Company Y by fully applying the former while excluding the latter, a resolution that would fail if her assigned work could not be performed without relying on Company X's confidential designs.

Should Engineer A accept employment with Company Y only after disclosing her confidentiality obligation regarding Company X's information, or accept the position without such disclosure?

Should Engineer A exclude Company X's confidential design information from her decisions at Company Y, or may she apply that knowledge to serve Company Y's interests?

Should Engineer A voluntarily recuse herself from Company Y projects that closely parallel or compete with designs she reviewed at the government agency?

Must Engineer A notify the government agency or Company X of her acceptance of employment at Company Y?