Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.
NSPE Code Provisions Referenced
Section II. Rules of Practice 2 72 entities
Engineers shall act for each employer or client as faithful agents or trustees.
Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services.
Section III. Professional Obligations 2 97 entities
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.
Cross-Case Connections
View ExtractionExplicit Board-Cited Precedents 3 Lineage Graph
Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.
Principle Established:
A part-time consultant arrangement to municipalities by engineers in private practice did not preclude those same engineers from providing normal engineering services to the same municipalities, where the engineer's loyalties were not divided.
Citation Context:
The Board cited this case to illustrate a situation where a part-time consultant arrangement did not create divided loyalties, contrasting with situations where confidentiality obligations may conflict.
Principle Established:
An engineer who gains access to confidential information while working for one party retains an ethical obligation to protect that information even after the professional relationship ends, and cannot subsequently provide services to an adverse party who seeks to exploit that prior access.
Citation Context:
The Board cited this case extensively to establish that an engineer who gains access to confidential information from one party cannot subsequently work for an adverse party, even after the original relationship is terminated, because the duty of confidentiality and loyalty persists.
Principle Established:
It is not ethical for an engineer retained by the US government to subsequently be retained by a contractor filing a claim against that same government without the former client's consent, per NSPE Code Section III.4.b.
Citation Context:
The Board cited this case to establish that an engineer retained by one client cannot ethically agree to represent an adverse party without the former client's consent, illustrating the duty of loyalty and confidentiality to former clients.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions
View ExtractionWhat are Engineer A’s ethical obligations under these circumstances?
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 resolved the tension between Competitive Employment Freedom and the Confidentiality Obligation toward Company X's regulatory submissions not by subordinating one principle to the other, but by conditioning the former on strict compliance with the latter. This conditional resolution treats confidentiality as a threshold constraint rather than a competing value to be balanced: Engineer A retains the right to pursue private employment, but that right is structurally bounded by a non-negotiable duty to withhold Company X's proprietary design information. The practical effect is that Competitive Employment Freedom is preserved in form but significantly constrained in substance, because Engineer A's utility to Company Y in any work stream touching Company X's design domain is permanently diminished. This case teaches that when a principle rooted in public trust - here, the protection of confidential regulatory submissions - conflicts with a principle rooted in individual professional autonomy, the Board treats the public-trust principle as lexically prior: freedom of employment survives, but only in the space that remains after confidentiality obligations have been fully honored.
The interaction between the Faithful Agent Confidentiality Obligation and the Loyalty Obligation to Company Y within ethical limits reveals a structural asymmetry that the Board's conclusion leaves partially unresolved. As a faithful agent and trustee - first to the government agency and derivatively to Company X as a submitting party - Engineer A carries a confidentiality duty that predates and survives her relationship with Company Y. When these obligations collide, the faithful-agent duty to the prior principal functions as a hard ceiling on what Engineer A can legitimately offer Company Y. The Loyalty Obligation to Company Y is therefore not merely limited by ethics in the abstract; it is specifically and materially curtailed by the content of what Engineer A knows. This case teaches that loyalty to a current employer is always prospective and conditional, while confidentiality obligations to prior principals are retrospective and categorical. An engineer cannot discharge the former by simply intending not to disclose; she must actively structure her work at Company Y to ensure that the competitive intelligence value of her prior government access is never operationalized, even indirectly. The Board's conclusion gestures at this by requiring pre-employment disclosure, but does not fully articulate the ongoing affirmative conduct - including potential recusal from specific projects - that genuine reconciliation of these two principles demands.
The tension between the Post-Public-Service Conflict Avoidance principle and the Revolving Door Integrity principle exposes a deeper normative question the Board does not fully answer: how long must an engineer bear the competitive disadvantage imposed by prior government access to confidential information? The Board acknowledges the indeterminacy of the confidentiality obligation's duration - noting it persists without specifying when it ends - but declines to establish any mechanism for its expiration. This silence reflects an implicit prioritization of Regulatory Submission Confidentiality Protection over Revolving Door Integrity whenever the confidential information is technical and potentially long-lived. The case thus teaches that the revolving-door principle, while legitimate and important for sustaining a pipeline of experienced engineers between public and private sectors, cannot be invoked to erode confidentiality duties whose duration is tied to the competitive sensitivity of the underlying information rather than to the passage of calendar time. The ethical resolution is not a fixed time limit but a functional standard: Engineer A's confidentiality obligation persists as long as the design information she accessed retains competitive value in the marketplace - a standard that requires ongoing professional judgment rather than a one-time disclosure at the moment of employment transition. The absence of a formal revolving-door policy in the government agency's employment framework does not diminish this obligation; it merely shifts the burden of self-governance entirely onto Engineer A, reinforcing that ethical duties under the NSPE Code are independent of and supplementary to whatever contractual or regulatory mechanisms an employer has or has not established.
Is the Board's conclusion sufficient in only requiring disclosure to Company Y before accepting employment, or should Engineer A also be required to notify Company X that its confidential information is now held by an employee of a direct competitor?
The Board's conclusion requires Engineer A to disclose her prior government access to Company Y before accepting employment, but it does not address whether Company X - the party whose proprietary information is most directly at risk - bears any right to notification or whether Engineer A or Company Y bears any corresponding duty to provide it. This omission is ethically significant. Under the faithful agent and trustee standard, Engineer A's confidentiality obligation runs not merely as a prohibition on disclosure but as an affirmative duty of trust toward the interests of those whose information she holds. Company X submitted its confidential design information to the government agency with a reasonable expectation that the regulatory process would protect it from competitive exploitation. That expectation is materially threatened when an engineer with direct access to those submissions transitions to a direct competitor. While the NSPE Code does not explicitly require notification to Company X, the principle that engineers shall not promote or arrange for new employment to the detriment of a client or employer - read in conjunction with the faithful agent standard - supports the conclusion that Engineer A should at minimum consider whether Company X's interests require some form of protective notice, particularly if Engineer A is assigned to work that directly competes with Company X's approved or pending facility designs. The Board's silence on this point leaves Company X without any procedural protection beyond Engineer A's individual conscience, which is an insufficient safeguard given the structural competitive asymmetry created by the employment transition.
In response to Q102, the Board's conclusion is incomplete in limiting its disclosure requirement solely to Company Y. Because Company X is the party whose proprietary regulatory submissions are most directly at risk from Engineer A's transition to a direct competitor, basic principles of fairness and the faithful-agent obligation suggest that Company X also has a legitimate interest in knowing that an individual with access to its confidential design information has joined a competing firm. While the NSPE Code does not explicitly mandate notification to the originating company, the spirit of Section III.4 - which protects confidential information concerning the business affairs of clients - implies that Engineer A should at minimum consider whether Company X's consent or awareness is warranted. Notification to Company X would allow that company to assess whether any protective measures are necessary, such as seeking additional assurances or adjusting its ongoing regulatory submissions. The absence of a mandatory notification requirement in the Board's conclusion leaves a structural gap that could undermine the very confidentiality protections the Code is designed to enforce.
Does Engineer A have an obligation to proactively recuse herself from any work at Company Y that directly involves Company X, even if Company Y never explicitly asks her to contribute such knowledge, and how should that recusal be structured and documented?
Beyond the Board's finding that Engineer A may join Company Y provided she withholds Company X's confidential information and discloses the conflict before accepting employment, the Board's conclusion is structurally incomplete because it addresses only the threshold moment of employment acceptance and not the ongoing conduct obligations that persist throughout Engineer A's tenure at Company Y. Engineer A's ethical duties do not terminate once she discloses the conflict and accepts the position; rather, they generate a continuing affirmative obligation to recuse herself from any project, assignment, or internal deliberation at Company Y that directly involves Company X's facility designs, regulatory submissions, or competitive positioning in domains where her government access gave her privileged structural knowledge. This recusal obligation should be documented formally - through written notice to Company Y's management and project assignment records - so that the boundary between permissible general expertise and impermissible use of confidential regulatory knowledge is institutionally traceable and not left to Engineer A's individual judgment alone. The absence of such a documented recusal mechanism creates a structural gap in the Board's otherwise sound conditional permission, because the risk of inadvertent or subconscious use of confidential knowledge is highest precisely in the ongoing work environment where competitive pressures are constant and the line between general expertise and privileged knowledge is difficult to police without formal procedures.
The Board's conditional permission for Engineer A to join Company Y does not adequately address the scenario - raised by analogy to BER Case 85-4 - in which Company Y later becomes involved in an adversarial regulatory or legal proceeding against Company X and Engineer A is asked to contribute technical analysis drawing on her domain expertise. In BER Case 85-4, the Board held that an engineer who had provided confidential information to one party in a proceeding could not ethically accept retention by the opposing party, and that claimed naivety about the conflict did not serve as mitigation. Applied to the current case, this precedent implies that if Company X and Company Y become adversaries in any regulatory, contractual, or legal proceeding involving the facility design domain in which Engineer A holds Company X's confidential information, Engineer A would be categorically barred from contributing to Company Y's position in that proceeding - regardless of whether she explicitly references Company X's confidential submissions or claims to rely only on general expertise. The structural knowledge she accumulated through regulatory access creates a conflict that cannot be neutralized by mental segregation alone. The Board's conclusion should have explicitly flagged this downstream adversarial participation risk as a constraint on Engineer A's permissible scope of work at Company Y, rather than leaving it to be inferred from prior BER precedent. Company Y should also be made aware of this constraint at the time of Engineer A's pre-employment disclosure, because it materially affects the range of assignments Engineer A can ethically accept.
In response to Q101, Engineer A's ethical obligations extend beyond merely refraining from active disclosure of Company X's confidential design information. A genuinely compliant posture requires Engineer A to proactively recuse herself from any assignment at Company Y that involves competing directly with Company X's approved or pending facility designs, particularly where her government-acquired structural knowledge of Company X's design approaches could - even subconsciously - inform her technical judgments. This recusal should be formalized in writing at the outset of employment, specifying the subject-matter domains from which Engineer A is excluded, and should be documented in a manner accessible to Company Y's project managers so that inadvertent assignment can be prevented. The recusal record also serves a protective function for Engineer A herself, creating a contemporaneous audit trail demonstrating good-faith compliance with her confidentiality obligations. Without such structural safeguards, the Board's conditional permission to accept employment risks becoming a nominal constraint that is practically unenforceable.
The interaction between the Faithful Agent Confidentiality Obligation and the Loyalty Obligation to Company Y within ethical limits reveals a structural asymmetry that the Board's conclusion leaves partially unresolved. As a faithful agent and trustee - first to the government agency and derivatively to Company X as a submitting party - Engineer A carries a confidentiality duty that predates and survives her relationship with Company Y. When these obligations collide, the faithful-agent duty to the prior principal functions as a hard ceiling on what Engineer A can legitimately offer Company Y. The Loyalty Obligation to Company Y is therefore not merely limited by ethics in the abstract; it is specifically and materially curtailed by the content of what Engineer A knows. This case teaches that loyalty to a current employer is always prospective and conditional, while confidentiality obligations to prior principals are retrospective and categorical. An engineer cannot discharge the former by simply intending not to disclose; she must actively structure her work at Company Y to ensure that the competitive intelligence value of her prior government access is never operationalized, even indirectly. The Board's conclusion gestures at this by requiring pre-employment disclosure, but does not fully articulate the ongoing affirmative conduct - including potential recusal from specific projects - that genuine reconciliation of these two principles demands.
Given that the Board acknowledges the indeterminacy of the confidentiality obligation's duration, what mechanism or standard should govern when, if ever, Engineer A's duty to protect Company X's confidential design information expires, particularly as technology and competitive landscapes evolve?
The Board acknowledges that the duration of Engineer A's confidentiality obligation is indeterminate but declines to establish any standard or mechanism for when, if ever, that obligation expires. This indeterminacy, left unresolved, creates a practical problem that undermines the workability of the Board's conditional permission over time. From a deontological perspective, the duty of trust that grounds Engineer A's confidentiality obligation does not automatically dissolve with the passage of time, because the obligation derives from the nature of the relationship and the act of entrusting - not from the continued commercial sensitivity of the information. However, from a consequentialist perspective, a perpetual and absolute confidentiality obligation that never accounts for changed circumstances - such as the public disclosure of Company X's facility design through regulatory approval, the obsolescence of the underlying technology, or Company X's own abandonment of the design - would impose career restrictions on Engineer A that are disproportionate to any remaining protective interest. A more analytically complete conclusion would hold that Engineer A's obligation persists as long as the information retains competitive or regulatory sensitivity that was not publicly disclosed through the approval process itself, and that the burden of demonstrating that sensitivity has lapsed falls on Engineer A before she may treat the information as freely usable. This standard preserves the protective purpose of the confidentiality obligation while providing Engineer A with a principled mechanism for assessing when her constraint has been lifted by changed circumstances rather than by the mere passage of time or her own convenience.
In response to Q103, the Board's acknowledgment of the indeterminacy of the confidentiality obligation's duration is ethically significant but practically insufficient without a governing standard. A workable framework should assess expiration of the confidentiality duty against at least three criteria: first, whether the specific design information has entered the public domain through regulatory disclosure, publication, or independent development by third parties; second, whether the technology embodied in Company X's confidential submissions has been superseded to the point where the information no longer confers competitive advantage; and third, whether the passage of time, combined with material changes in the competitive landscape, renders the information commercially inert. Until all three conditions are satisfied, Engineer A's duty to protect Company X's confidential design information should be treated as continuing. This multi-factor standard is consistent with the perpetual confidentiality norm recognized in BER Case 85-4, while providing a principled mechanism for eventual expiration rather than imposing an indefinite and potentially unreasonable burden on Engineer A's professional mobility.
The tension between the Post-Public-Service Conflict Avoidance principle and the Revolving Door Integrity principle exposes a deeper normative question the Board does not fully answer: how long must an engineer bear the competitive disadvantage imposed by prior government access to confidential information? The Board acknowledges the indeterminacy of the confidentiality obligation's duration - noting it persists without specifying when it ends - but declines to establish any mechanism for its expiration. This silence reflects an implicit prioritization of Regulatory Submission Confidentiality Protection over Revolving Door Integrity whenever the confidential information is technical and potentially long-lived. The case thus teaches that the revolving-door principle, while legitimate and important for sustaining a pipeline of experienced engineers between public and private sectors, cannot be invoked to erode confidentiality duties whose duration is tied to the competitive sensitivity of the underlying information rather than to the passage of calendar time. The ethical resolution is not a fixed time limit but a functional standard: Engineer A's confidentiality obligation persists as long as the design information she accessed retains competitive value in the marketplace - a standard that requires ongoing professional judgment rather than a one-time disclosure at the moment of employment transition. The absence of a formal revolving-door policy in the government agency's employment framework does not diminish this obligation; it merely shifts the burden of self-governance entirely onto Engineer A, reinforcing that ethical duties under the NSPE Code are independent of and supplementary to whatever contractual or regulatory mechanisms an employer has or has not established.
Does the government agency itself bear any ethical or institutional responsibility to establish formal revolving-door policies that protect the confidentiality of regulatory submissions, and does the absence of such a policy shift any moral burden onto Engineer A or Company Y?
The Board's analysis does not address the systemic dimension of the revolving-door problem it implicitly resolves at the individual level. By permitting Engineer A's transition to Company Y subject only to individual confidentiality maintenance and pre-employment disclosure, the Board's conclusion, if generalized across the engineering profession, creates a structural incentive problem: government agencies that rely on confidential regulatory submissions from private companies will find that the value of those submissions as competitive intelligence makes their reviewing engineers attractive targets for competitor recruitment, and the individual confidentiality obligation - enforced only through professional ethics rather than institutional policy - is a weak safeguard against systematic erosion of regulatory integrity. The government agency itself bears an institutional responsibility, which the Board does not acknowledge, to establish formal revolving-door policies that restrict post-employment transitions to direct competitors of companies whose confidential submissions an engineer reviewed, at least for a defined cooling-off period. The absence of such a policy does not diminish Engineer A's individual ethical obligations, but it does mean that the ethical burden of protecting regulatory integrity is being borne entirely by individual engineers rather than by the institutional structures best positioned to enforce it. A complete ethical analysis would note that Engineer A's compliance with her individual obligations is necessary but not sufficient to protect the systemic integrity of the regulatory process, and that the Board's silence on institutional responsibility leaves a significant gap in the overall ethical framework governing government-to-private-sector transitions.
In response to Q104, the government agency bears a distinct institutional responsibility to establish formal revolving-door policies governing engineers who have had access to confidential regulatory submissions. The absence of such policies does not diminish Engineer A's individual ethical obligations under the NSPE Code, but it does represent a systemic failure that increases the probability of inadvertent or deliberate misuse of confidential information across the broader population of government engineers transitioning to private practice. The moral burden is not transferred to Engineer A by the agency's omission - her duties under Sections II.4 and III.4 are independent of institutional policy - but the agency's failure to implement structural safeguards creates an environment in which compliance depends entirely on individual ethical judgment rather than enforceable institutional norms. Company Y also bears a derivative responsibility: knowing that Engineer A held government regulatory access, Company Y should not assign her to work that could exploit that access, regardless of whether any formal policy prohibits it.
Does the Competitive Employment Freedom principle, which permits Engineer A to accept a position at Company Y, conflict with the Former Client Adversarial Participation Prohibition, which may effectively bar her from contributing to any work that competes directly with Company X, thereby rendering her employment value to Company Y structurally compromised?
Beyond the Board's finding that Engineer A may join Company Y provided she withholds Company X's confidential information and discloses the conflict before accepting employment, the Board's conclusion is structurally incomplete because it addresses only the threshold moment of employment acceptance and not the ongoing conduct obligations that persist throughout Engineer A's tenure at Company Y. Engineer A's ethical duties do not terminate once she discloses the conflict and accepts the position; rather, they generate a continuing affirmative obligation to recuse herself from any project, assignment, or internal deliberation at Company Y that directly involves Company X's facility designs, regulatory submissions, or competitive positioning in domains where her government access gave her privileged structural knowledge. This recusal obligation should be documented formally - through written notice to Company Y's management and project assignment records - so that the boundary between permissible general expertise and impermissible use of confidential regulatory knowledge is institutionally traceable and not left to Engineer A's individual judgment alone. The absence of such a documented recusal mechanism creates a structural gap in the Board's otherwise sound conditional permission, because the risk of inadvertent or subconscious use of confidential knowledge is highest precisely in the ongoing work environment where competitive pressures are constant and the line between general expertise and privileged knowledge is difficult to police without formal procedures.
The Board's conclusion implicitly assumes that the competitive intelligence value of Engineer A's government access is incidental to Company Y's hiring decision, but it does not address the ethically distinct scenario in which Company Y recruits Engineer A specifically because of her knowledge of Company X's design strategies. If Company Y's hiring motivation is explicitly or primarily the competitive intelligence value of Engineer A's regulatory access - rather than her general engineering expertise - then the employment transition is not merely a permissible revolving-door situation subject to confidentiality constraints, but a structured attempt to exploit the regulatory process for competitive advantage. In that scenario, both Engineer A and Company Y would bear heightened ethical obligations: Engineer A would be obligated to decline the position or, at minimum, to make explicit to Company Y that she cannot and will not provide any information derived from her government access, and Company Y would be obligated under the faithful agent and conflict of interest avoidance principles to refrain from assigning Engineer A to any work where her prior access could provide competitive advantage over Company X. The Board's silence on the motivational dimension of the hiring decision leaves open a significant ethical gap, because the same employment transition that is conditionally permissible when motivated by legitimate expertise recruitment becomes ethically impermissible when motivated by the desire to acquire competitive intelligence through the back channel of a former government reviewer.
In response to Q201, the tension between Competitive Employment Freedom and the Former Client Adversarial Participation Prohibition is real and structural, not merely theoretical. While the Board correctly concludes that Engineer A may accept employment at Company Y, the practical scope of her permissible contributions at Company Y may be significantly constrained by the prohibition on participating in work that directly competes with or adversely affects Company X's interests using knowledge derived from regulatory access. If Company Y's primary business in the relevant facility design domain overlaps substantially with Company X's approved designs, Engineer A's effective utility to Company Y in that domain may be severely limited. This does not render the employment ethically impermissible, but it does mean that both Engineer A and Company Y must enter the employment relationship with clear-eyed awareness that her contribution scope will be bounded. The Board's conclusion permitting employment is therefore accurate but incomplete without acknowledging this structural limitation on Engineer A's role.
The Board resolved the tension between Competitive Employment Freedom and the Confidentiality Obligation toward Company X's regulatory submissions not by subordinating one principle to the other, but by conditioning the former on strict compliance with the latter. This conditional resolution treats confidentiality as a threshold constraint rather than a competing value to be balanced: Engineer A retains the right to pursue private employment, but that right is structurally bounded by a non-negotiable duty to withhold Company X's proprietary design information. The practical effect is that Competitive Employment Freedom is preserved in form but significantly constrained in substance, because Engineer A's utility to Company Y in any work stream touching Company X's design domain is permanently diminished. This case teaches that when a principle rooted in public trust - here, the protection of confidential regulatory submissions - conflicts with a principle rooted in individual professional autonomy, the Board treats the public-trust principle as lexically prior: freedom of employment survives, but only in the space that remains after confidentiality obligations have been fully honored.
How does the Loyalty Obligation of Engineer A to Company Y within ethical limits conflict with the Faithful Agent Confidentiality Obligation grounding her duty to protect Company X's information, particularly when Company Y's competitive interests would be advanced by leveraging insights Engineer A gained through regulatory access?
The interaction between the Faithful Agent Confidentiality Obligation and the Loyalty Obligation to Company Y within ethical limits reveals a structural asymmetry that the Board's conclusion leaves partially unresolved. As a faithful agent and trustee - first to the government agency and derivatively to Company X as a submitting party - Engineer A carries a confidentiality duty that predates and survives her relationship with Company Y. When these obligations collide, the faithful-agent duty to the prior principal functions as a hard ceiling on what Engineer A can legitimately offer Company Y. The Loyalty Obligation to Company Y is therefore not merely limited by ethics in the abstract; it is specifically and materially curtailed by the content of what Engineer A knows. This case teaches that loyalty to a current employer is always prospective and conditional, while confidentiality obligations to prior principals are retrospective and categorical. An engineer cannot discharge the former by simply intending not to disclose; she must actively structure her work at Company Y to ensure that the competitive intelligence value of her prior government access is never operationalized, even indirectly. The Board's conclusion gestures at this by requiring pre-employment disclosure, but does not fully articulate the ongoing affirmative conduct - including potential recusal from specific projects - that genuine reconciliation of these two principles demands.
Does the Conflict of Interest Disclosure Evolution Principle, which requires Engineer A to make her prior government access known to Company Y before accepting employment, tension with the Confidentiality Obligation toward Company X's regulatory submissions, insofar as the very act of disclosure to Company Y may reveal the nature or existence of Company X's proprietary information?
In response to Q203, the Board's requirement that Engineer A disclose her prior government access to Company Y before accepting employment creates a genuine tension with her confidentiality obligation toward Company X. The very act of explaining the nature and scope of her access - necessary for Company Y to understand the conflict - risks revealing that Company X submitted confidential design information of a particular character, scope, or strategic significance. Engineer A must therefore calibrate her disclosure to Company Y with care: she should convey the existence and general subject-matter domain of her access without disclosing the substantive content, design details, or competitive implications of Company X's submissions. This calibrated disclosure approach is consistent with Section III.4.a, which requires consent of all interested parties before arranging employment that could disadvantage a former client. In practice, this means Engineer A's disclosure to Company Y should be framed in terms of the categories of information she cannot use, rather than the content of what she knows.
Does the Post-Public-Service Conflict Avoidance principle, which counsels Engineer A to avoid situations where her government access creates unfair competitive advantage, conflict with the Revolving Door Integrity principle, which is meant to preserve the ability of government engineers to transition to private practice without permanent career restriction, and how should the Board weigh these competing values when the confidential information is technical and long-lived?
The Board acknowledges that the duration of Engineer A's confidentiality obligation is indeterminate but declines to establish any standard or mechanism for when, if ever, that obligation expires. This indeterminacy, left unresolved, creates a practical problem that undermines the workability of the Board's conditional permission over time. From a deontological perspective, the duty of trust that grounds Engineer A's confidentiality obligation does not automatically dissolve with the passage of time, because the obligation derives from the nature of the relationship and the act of entrusting - not from the continued commercial sensitivity of the information. However, from a consequentialist perspective, a perpetual and absolute confidentiality obligation that never accounts for changed circumstances - such as the public disclosure of Company X's facility design through regulatory approval, the obsolescence of the underlying technology, or Company X's own abandonment of the design - would impose career restrictions on Engineer A that are disproportionate to any remaining protective interest. A more analytically complete conclusion would hold that Engineer A's obligation persists as long as the information retains competitive or regulatory sensitivity that was not publicly disclosed through the approval process itself, and that the burden of demonstrating that sensitivity has lapsed falls on Engineer A before she may treat the information as freely usable. This standard preserves the protective purpose of the confidentiality obligation while providing Engineer A with a principled mechanism for assessing when her constraint has been lifted by changed circumstances rather than by the mere passage of time or her own convenience.
In response to Q204, the tension between Post-Public-Service Conflict Avoidance and Revolving Door Integrity is one of the most structurally difficult problems in engineering ethics for government-to-private transitions. The Board's resolution - permitting employment with a confidentiality constraint - represents a reasonable middle position, but it underweights the Post-Public-Service Conflict Avoidance principle when the confidential information is technical, long-lived, and directly relevant to the competitor's core business. Where the information Engineer A holds is not merely incidental but constitutes a sustained competitive advantage - as is plausible with facility design data that may remain valid for decades - the Revolving Door Integrity principle's goal of preserving career mobility must yield to a more robust application of conflict avoidance. In such cases, the ethical weight should shift toward requiring Engineer A to avoid not just active disclosure but any role at Company Y where her structural knowledge of Company X's design philosophy could influence project outcomes, even indirectly.
The tension between the Post-Public-Service Conflict Avoidance principle and the Revolving Door Integrity principle exposes a deeper normative question the Board does not fully answer: how long must an engineer bear the competitive disadvantage imposed by prior government access to confidential information? The Board acknowledges the indeterminacy of the confidentiality obligation's duration - noting it persists without specifying when it ends - but declines to establish any mechanism for its expiration. This silence reflects an implicit prioritization of Regulatory Submission Confidentiality Protection over Revolving Door Integrity whenever the confidential information is technical and potentially long-lived. The case thus teaches that the revolving-door principle, while legitimate and important for sustaining a pipeline of experienced engineers between public and private sectors, cannot be invoked to erode confidentiality duties whose duration is tied to the competitive sensitivity of the underlying information rather than to the passage of calendar time. The ethical resolution is not a fixed time limit but a functional standard: Engineer A's confidentiality obligation persists as long as the design information she accessed retains competitive value in the marketplace - a standard that requires ongoing professional judgment rather than a one-time disclosure at the moment of employment transition. The absence of a formal revolving-door policy in the government agency's employment framework does not diminish this obligation; it merely shifts the burden of self-governance entirely onto Engineer A, reinforcing that ethical duties under the NSPE Code are independent of and supplementary to whatever contractual or regulatory mechanisms an employer has or has not established.
From a deontological perspective, does Engineer A's duty as a faithful agent and trustee to the government agency create a categorical obligation to protect Company X's confidential design information that persists indefinitely after employment ends, regardless of whether disclosure would cause any measurable harm?
In response to Q301, from a deontological perspective, Engineer A's duty as a faithful agent and trustee does generate a categorical obligation to protect Company X's confidential design information that is not contingent on demonstrable harm. The Kantian structure of the faithful-agent duty under Section II.4 treats the obligation of confidentiality as arising from the relationship of trust itself - the government agency's receipt of Company X's proprietary submissions created a duty of protection that Engineer A assumed by virtue of her role, independent of consequences. This means that even if disclosure would cause no measurable competitive harm to Company X - perhaps because the technology has been partially superseded - the categorical duty to refrain from using or disclosing the information persists until the information is genuinely in the public domain. The deontological analysis therefore supports a stricter reading of the confidentiality obligation than the Board's conclusion implies, one that does not permit Engineer A to rely on a harm-minimization calculus to justify reduced vigilance over time.
From a consequentialist perspective, does the Board's permissive conclusion - allowing Engineer A to join Company Y provided she withholds Company X's information - adequately account for the systemic harm to regulatory integrity if government engineers routinely transition to competitors with privileged knowledge of confidential submissions, even when individual disclosure is avoided?
The Board's analysis does not address the systemic dimension of the revolving-door problem it implicitly resolves at the individual level. By permitting Engineer A's transition to Company Y subject only to individual confidentiality maintenance and pre-employment disclosure, the Board's conclusion, if generalized across the engineering profession, creates a structural incentive problem: government agencies that rely on confidential regulatory submissions from private companies will find that the value of those submissions as competitive intelligence makes their reviewing engineers attractive targets for competitor recruitment, and the individual confidentiality obligation - enforced only through professional ethics rather than institutional policy - is a weak safeguard against systematic erosion of regulatory integrity. The government agency itself bears an institutional responsibility, which the Board does not acknowledge, to establish formal revolving-door policies that restrict post-employment transitions to direct competitors of companies whose confidential submissions an engineer reviewed, at least for a defined cooling-off period. The absence of such a policy does not diminish Engineer A's individual ethical obligations, but it does mean that the ethical burden of protecting regulatory integrity is being borne entirely by individual engineers rather than by the institutional structures best positioned to enforce it. A complete ethical analysis would note that Engineer A's compliance with her individual obligations is necessary but not sufficient to protect the systemic integrity of the regulatory process, and that the Board's silence on institutional responsibility leaves a significant gap in the overall ethical framework governing government-to-private-sector transitions.
In response to Q302, from a consequentialist perspective, the Board's permissive conclusion is vulnerable to a systemic harm objection that individual-level analysis cannot fully address. If the ethical standard permits government engineers to transition to competitors of companies whose confidential submissions they reviewed - provided only that they personally refrain from disclosure - the aggregate effect across many such transitions may be a significant erosion of regulatory integrity. Companies submitting confidential design information to government agencies do so with an expectation that the information will be protected not merely from active disclosure but from the structural informational advantage that a knowledgeable former regulator brings to a competitor. A consequentialist analysis would require the Board to weigh not only the individual case but the rule-level effects of its conclusion: if the rule 'government engineers may join competitors with a confidentiality pledge' becomes standard practice, the chilling effect on candid regulatory submissions could undermine the quality of government oversight. The Board's conclusion is defensible at the individual level but requires supplementation with systemic safeguards - such as mandatory recusal protocols and agency-level revolving-door policies - to be consequentially sound.
From a virtue ethics perspective, does an engineer of genuine professional integrity merely refrain from disclosing confidential information, or does virtuous conduct require Engineer A to proactively recuse herself from any work at Company Y that could benefit from - even subconsciously - the structural knowledge of Company X's design approaches she accumulated during government service?
Beyond the Board's finding that Engineer A may join Company Y provided she withholds Company X's confidential information and discloses the conflict before accepting employment, the Board's conclusion is structurally incomplete because it addresses only the threshold moment of employment acceptance and not the ongoing conduct obligations that persist throughout Engineer A's tenure at Company Y. Engineer A's ethical duties do not terminate once she discloses the conflict and accepts the position; rather, they generate a continuing affirmative obligation to recuse herself from any project, assignment, or internal deliberation at Company Y that directly involves Company X's facility designs, regulatory submissions, or competitive positioning in domains where her government access gave her privileged structural knowledge. This recusal obligation should be documented formally - through written notice to Company Y's management and project assignment records - so that the boundary between permissible general expertise and impermissible use of confidential regulatory knowledge is institutionally traceable and not left to Engineer A's individual judgment alone. The absence of such a documented recusal mechanism creates a structural gap in the Board's otherwise sound conditional permission, because the risk of inadvertent or subconscious use of confidential knowledge is highest precisely in the ongoing work environment where competitive pressures are constant and the line between general expertise and privileged knowledge is difficult to police without formal procedures.
In response to Q303, from a virtue ethics perspective, the standard of genuine professional integrity demands more than passive non-disclosure. An engineer of authentic virtue - one who has internalized the values of trustworthiness, fairness, and professional responsibility rather than merely complying with their letter - would recognize that the structural knowledge of Company X's design approaches accumulated during government service cannot be cleanly partitioned from her professional judgment. The virtue ethics tradition, which asks what a person of good character would do rather than what rules minimally require, supports proactive recusal from any work at Company Y that could benefit from this structural knowledge, even where the benefit would be subconscious or indirect. This is consistent with the capability identified as 'Engineer A Confidential Information Mental Segregation Impossibility Recognition' - the acknowledgment that cognitive compartmentalization of deeply internalized technical knowledge is not reliably achievable. Virtuous conduct therefore requires Engineer A to err on the side of broader recusal rather than narrower, accepting some limitation on her professional contribution as the price of genuine integrity.
From a deontological perspective, does Engineer A's obligation to disclose the conflict of interest to Company Y before accepting employment - as the Board requires - also entail a duty to disclose the same potential conflict to Company X, whose proprietary information is at risk, given that Company X is the party whose interests are most directly threatened by the employment transition?
The Board's conclusion requires Engineer A to disclose her prior government access to Company Y before accepting employment, but it does not address whether Company X - the party whose proprietary information is most directly at risk - bears any right to notification or whether Engineer A or Company Y bears any corresponding duty to provide it. This omission is ethically significant. Under the faithful agent and trustee standard, Engineer A's confidentiality obligation runs not merely as a prohibition on disclosure but as an affirmative duty of trust toward the interests of those whose information she holds. Company X submitted its confidential design information to the government agency with a reasonable expectation that the regulatory process would protect it from competitive exploitation. That expectation is materially threatened when an engineer with direct access to those submissions transitions to a direct competitor. While the NSPE Code does not explicitly require notification to Company X, the principle that engineers shall not promote or arrange for new employment to the detriment of a client or employer - read in conjunction with the faithful agent standard - supports the conclusion that Engineer A should at minimum consider whether Company X's interests require some form of protective notice, particularly if Engineer A is assigned to work that directly competes with Company X's approved or pending facility designs. The Board's silence on this point leaves Company X without any procedural protection beyond Engineer A's individual conscience, which is an insufficient safeguard given the structural competitive asymmetry created by the employment transition.
In response to Q304, from a deontological perspective, the duty to disclose a conflict of interest is not directionally limited to the party who benefits from the disclosure. If Engineer A's obligation to disclose to Company Y arises from the principle that parties affected by a conflict deserve notice - as grounded in Section II.4.a - then the same principle applies with equal or greater force to Company X, which is the party whose proprietary interests are most directly threatened. The deontological argument for disclosure to Company X is in fact stronger than for Company Y: Company Y is the beneficiary of Engineer A's expertise and can protect itself through contractual arrangements, whereas Company X is the vulnerable party with no contractual relationship with Engineer A and no independent means of learning about the transition. Failing to notify Company X treats that company merely as an object of the confidentiality obligation rather than as a rights-bearing party entitled to know that its information is now held by an employee of its direct competitor. The Board's silence on this point represents a gap in the deontological completeness of its analysis.
If Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and Company Y subsequently assigned her to a project directly competing with Company X's approved facility design, would the Board's analysis have shifted from a conditional permission to an outright prohibition - and what specific triggering threshold would mark that transition?
In response to Q401, if Engineer A had accepted employment with Company Y without disclosing her prior government access to Company X's confidential design information, and was subsequently assigned to a project directly competing with Company X's approved facility design, the Board's analysis would almost certainly shift from conditional permission to outright prohibition. The triggering threshold for that transition involves two compounding violations: first, the failure to disclose the conflict of interest to Company Y before accepting employment, which violates Section II.4.a independently; and second, the active participation in work that could exploit or be informed by Company X's confidential submissions, which violates Section III.4. The combination of non-disclosure and adversarial assignment would constitute a complete breach of Engineer A's ethical obligations, not merely a procedural deficiency. The specific threshold is therefore not a single act but the conjunction of concealment at hiring and subsequent assignment to conflicted work - either element alone might be remediable, but together they would place Engineer A in a position of irredeemable ethical violation under the NSPE Code.
What if the government agency had included an explicit revolving-door clause in Engineer A's employment contract prohibiting post-employment work for competitors of companies whose confidential submissions she reviewed - would Engineer A's ethical obligations under the NSPE Code have been strengthened, weakened, or simply made more legally enforceable, and does the absence of such a clause diminish her ethical duties?
In response to Q402, the presence of an explicit revolving-door clause in Engineer A's government employment contract would not strengthen her underlying ethical obligations under the NSPE Code - those obligations exist independently of contractual provisions - but it would make them legally enforceable and would remove any ambiguity about their scope and duration. Conversely, the absence of such a clause does not diminish Engineer A's ethical duties: the NSPE Code's confidentiality and conflict-of-interest provisions operate as professional ethical standards that bind Engineer A regardless of what her employment contract does or does not specify. The practical effect of a contractual clause would be to align legal and ethical obligations, reducing the risk that Engineer A might rationalize reduced vigilance on the grounds that no formal prohibition exists. The absence of such a clause therefore represents an institutional gap - attributable to the government agency - that increases reliance on Engineer A's individual ethical judgment but does not alter the substance of what that judgment requires.
If, analogous to BER Case 85-4, Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked by Company Y to provide technical analysis drawing on her general expertise in the relevant facility design domain - without explicitly referencing Company X's confidential submissions - would the switching-sides prohibition recognized in BER Case 85-4 apply, and would Engineer A's claimed ignorance of the conflict serve as any mitigation?
The Board's conditional permission for Engineer A to join Company Y does not adequately address the scenario - raised by analogy to BER Case 85-4 - in which Company Y later becomes involved in an adversarial regulatory or legal proceeding against Company X and Engineer A is asked to contribute technical analysis drawing on her domain expertise. In BER Case 85-4, the Board held that an engineer who had provided confidential information to one party in a proceeding could not ethically accept retention by the opposing party, and that claimed naivety about the conflict did not serve as mitigation. Applied to the current case, this precedent implies that if Company X and Company Y become adversaries in any regulatory, contractual, or legal proceeding involving the facility design domain in which Engineer A holds Company X's confidential information, Engineer A would be categorically barred from contributing to Company Y's position in that proceeding - regardless of whether she explicitly references Company X's confidential submissions or claims to rely only on general expertise. The structural knowledge she accumulated through regulatory access creates a conflict that cannot be neutralized by mental segregation alone. The Board's conclusion should have explicitly flagged this downstream adversarial participation risk as a constraint on Engineer A's permissible scope of work at Company Y, rather than leaving it to be inferred from prior BER precedent. Company Y should also be made aware of this constraint at the time of Engineer A's pre-employment disclosure, because it materially affects the range of assignments Engineer A can ethically accept.
In response to Q403, if Company X later became involved in an adversarial regulatory or legal proceeding against Company Y and Engineer A was asked to provide technical analysis drawing on her general expertise - without explicitly referencing Company X's confidential submissions - the switching-sides prohibition recognized in BER Case 85-4 would apply with substantial force. The critical insight from BER Case 85-4 is that the prohibition is not limited to cases where the engineer explicitly uses confidential information; it extends to situations where the engineer's prior access creates an appearance of impropriety or a structural conflict that cannot be neutralized by claimed ignorance of the connection. Engineer A's claimed ignorance that her general expertise was informed by her government-acquired knowledge of Company X's design approaches would provide no meaningful mitigation, consistent with the principle that naivety does not exculpate - as reflected in the constraint 'Engineer A Naivety Non-Exculpation - BER Case 85-4.' The adversarial context would trigger a categorical bar on Engineer A's participation, regardless of whether she consciously drew on Company X's confidential submissions.
What if Company Y had specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies - making the competitive intelligence value of her access an explicit factor in the hiring decision - would the Board's conclusion permitting the employment transition still hold, and what additional obligations would arise for both Engineer A and Company Y under the NSPE Code?
The Board's conclusion implicitly assumes that the competitive intelligence value of Engineer A's government access is incidental to Company Y's hiring decision, but it does not address the ethically distinct scenario in which Company Y recruits Engineer A specifically because of her knowledge of Company X's design strategies. If Company Y's hiring motivation is explicitly or primarily the competitive intelligence value of Engineer A's regulatory access - rather than her general engineering expertise - then the employment transition is not merely a permissible revolving-door situation subject to confidentiality constraints, but a structured attempt to exploit the regulatory process for competitive advantage. In that scenario, both Engineer A and Company Y would bear heightened ethical obligations: Engineer A would be obligated to decline the position or, at minimum, to make explicit to Company Y that she cannot and will not provide any information derived from her government access, and Company Y would be obligated under the faithful agent and conflict of interest avoidance principles to refrain from assigning Engineer A to any work where her prior access could provide competitive advantage over Company X. The Board's silence on the motivational dimension of the hiring decision leaves open a significant ethical gap, because the same employment transition that is conditionally permissible when motivated by legitimate expertise recruitment becomes ethically impermissible when motivated by the desire to acquire competitive intelligence through the back channel of a former government reviewer.
In response to Q404, if Company Y specifically recruited Engineer A because of her government-acquired knowledge of Company X's design strategies - making competitive intelligence an explicit factor in the hiring decision - the Board's conditional permission to accept employment would not hold. This scenario transforms the employment transition from a permissible career move with incidental confidentiality obligations into a deliberate scheme to exploit confidential regulatory submissions for competitive advantage, which is precisely what Sections III.4 and III.4.a are designed to prevent. Under these circumstances, Engineer A would be ethically prohibited from accepting the position, because doing so would make her a willing instrument of the misappropriation of Company X's confidential information, regardless of whether she personally disclosed any specific design details. Company Y would bear independent ethical culpability for structuring a recruitment strategy around the exploitation of confidential government-access information. Both parties would be in violation of the NSPE Code, and Engineer A's obligation would be to decline the offer and, if appropriate, report the circumstances to the relevant professional or regulatory authorities.
Decisions & Arguments
View ExtractionCausal-Normative Links 7
- Post-Public-Service Competitor Employment Conflict Avoidance Obligation
- Engineer A Post-Public-Service Competitor Employment Conflict Avoidance
- Competitive Employment Acceptance With Confidentiality Constraint Obligation
- Engineer A Government-to-Private Competitive Employment Acceptance With Confidentiality Constraint
- Conflict of Interest Disclosure to New Private Employer Regarding Prior Government Access Obligation
- Engineer A Conflict of Interest Disclosure to Company Y Regarding Company X Access
- Post-Public-Service Competitor Employment Conflict Avoidance Obligation
- Engineer A Post-Public-Service Competitor Employment Conflict Avoidance
- Engineer A Former Regulatory Access Adversarial Non-Participation Company X
- Engineer A Post-Public-Employment Confidential Information Non-Use
- Engineer A Post-Public-Employment Confidential Information Non-Use Company X
- Engineer A Regulatory Submission Confidentiality Protection
- Engineer A Regulatory Submission Confidentiality Protection Company X
- Regulatory Submission Confidentiality Protection by Government Engineer Obligation
- Post-Public-Employment Confidential Information Non-Use Obligation
- Engineer A Former Regulatory Access Adversarial Non-Participation Company X
- Engineer A Former Regulatory Access Adversarial Non-Participation
- Former Regulatory Access Adversarial Non-Participation Obligation
- Company Y AE Firm Incumbent Advantage Non-Exploitation Regarding Company X Information
- Engineer A Former Client Confidentiality Perpetuation Post-Termination
- Former Client Confidentiality Perpetuation Obligation
- BER 82-6 Engineer US Government Dam Failure Switching Sides
- Switching Sides Forensic Expert Prohibition Obligation
- Engineer A Forensic Expert Switching Sides Prohibition
- Adversarial Retention Motivation Awareness Obligation
- Engineer A Adversarial Retention Motivation Awareness
- Switching Sides Full Discussion With Original Client Obligation
- Engineer A Full Discussion With Attorney Z Obligation
- Engineer A Former Client Confidentiality Perpetuation Post-Termination
- Former Client Confidentiality Perpetuation Obligation
- Engineer A Forensic Expert Switching Sides Prohibition
- Switching Sides Forensic Expert Prohibition Obligation
- Engineer A Forensic Expert Switching Sides Prohibition
- Former Client Confidentiality Perpetuation Obligation
- Engineer A Former Client Confidentiality Perpetuation Post-Termination
- Adversarial Retention Motivation Awareness Obligation
- Engineer A Adversarial Retention Motivation Awareness
- Switching Sides Full Discussion With Original Client Obligation
- Engineer A Full Discussion With Attorney Z Obligation
- BER 82-6 Engineer US Government Dam Failure Switching Sides
- Engineer A Regulatory Submission Confidentiality Protection
- Engineer A Regulatory Submission Confidentiality Protection Company X
- Regulatory Submission Confidentiality Protection by Government Engineer Obligation
- Engineer A Post-Public-Employment Confidential Information Non-Use
- Engineer A Post-Public-Employment Confidential Information Non-Use Company X
- Post-Public-Employment Confidential Information Non-Use Obligation
- Engineer A Former Regulatory Access Adversarial Non-Participation Company X
- Engineer A Former Regulatory Access Adversarial Non-Participation
- Former Regulatory Access Adversarial Non-Participation Obligation
- Engineer A Post-Public-Service Competitor Employment Conflict Avoidance
- Post-Public-Service Competitor Employment Conflict Avoidance Obligation
- Company Y AE Firm Incumbent Advantage Non-Exploitation Regarding Company X Information
- Engineer A Conflict of Interest Disclosure to Company Y Regarding Company X Access
Decision Points 6
Should Engineer A accept employment at Company Y, and if so, what obligations must she fulfill before accepting?
The Post-Public-Service Competitor Employment Conflict Avoidance Obligation counsels that the revolving door from regulatory access to competitive employment creates inherent conflicts that cannot be managed through disclosure alone. Competing against this, the Competitive Employment Freedom principle holds that engineers are not unduly penalized for accepting positions with competitors of former clients, provided they do not disclose or use confidential information. The Conflict of Interest Disclosure to New Private Employer obligation requires that Engineer A inform Company Y of the nature and extent of her prior access before accepting.
Uncertainty arises because the absence of a formal revolving-door provision in Engineer A's government employment contract leaves unclear whether the conflict is severe enough to preclude acceptance entirely or merely requires disclosure and ongoing confidentiality maintenance. The indeterminate duration of the confidentiality obligation further complicates whether the conflict is manageable or categorical.
Engineer A worked for a government agency that received confidential and proprietary design information from Company X as part of a regulatory approval process. Engineer A accumulated direct knowledge of Company X's confidential submissions. Engineer A then resigned from the agency and was offered an engineering position at Company Y, a direct competitor of Company X.
Does Engineer A's confidentiality obligation require only passive non-disclosure of Company X's information, or does it also require proactive recusal from assignments at Company Y where her structural knowledge could, even subconsciously, inform her technical judgments?
The Post-Public-Employment Confidential Information Non-Use Obligation prohibits Engineer A from using, disclosing, or exploiting Company X's confidential information in any form. The Confidential Information Mental Segregation Impossibility Recognition Capability, grounded in BER Case 85-4, establishes that once an engineer has been exposed to confidential information, it is not realistically possible to mentally segregate that knowledge when performing work for a competing party. The Competitive Employment Freedom principle, however, holds that Engineer A should not be unduly penalized and that her general engineering expertise remains legitimately deployable.
Uncertainty arises because the boundary between Engineer A's general engineering expertise and her government-acquired structural knowledge of Company X's specific design approaches is practically indeterminate. If the recusal obligation extends to all competitive work touching Company X's technical domain rather than only direct adversarial assignments, Engineer A's effective utility to Company Y may be severely and disproportionately constrained.
Engineer A has accepted employment at Company Y and holds structural knowledge of Company X's confidential facility design submissions acquired through government regulatory review. Company Y operates in the same facility design domain as Company X and may assign Engineer A to projects that directly or indirectly compete with Company X's approved designs. Engineer A cannot reliably partition her accumulated technical knowledge from her professional judgment in this domain.
Should Engineer A disclose her conflict only to Company Y before accepting employment, or must she also notify Company X that its confidential regulatory submission data is now held by an employee of a direct competitor?
The Conflict of Interest Disclosure obligation requires Engineer A to notify Company Y before accepting employment so that Company Y can implement conflict management measures. The Regulatory Submission Confidentiality Protection Obligation and the faithful-agent standard under II.4 create an affirmative duty of trust running toward Company X as the submitting party, not merely a prohibition on disclosure. The Former Client Confidentiality Perpetuation Obligation establishes that the duty of trust toward Company X survives the termination of Engineer A's government employment. The tension arises because the very act of disclosing to Company Y the nature and scope of Engineer A's access may itself reveal information about Company X's submissions.
Uncertainty is created by the absence of any established NSPE Code provision explicitly requiring reverse notification to the original submitter of confidential information when a government engineer transitions to a competitor. Additionally, notifying Company X risks revealing the existence and character of Engineer A's access in ways that could themselves constitute a confidentiality breach or trigger adverse competitive responses by Company X.
Engineer A holds Company X's confidential regulatory submission data and is transitioning to Company Y, a direct competitor of Company X. Company X submitted its proprietary design information to the government agency with a reasonable expectation that the regulatory process would protect it from competitive exploitation. Company X has no contractual relationship with Engineer A and no independent means of learning about her employment transition.
How should Engineer A assess the duration of her confidentiality obligation toward Company X's design information, and by what standard, if any, may she treat that obligation as having expired?
The Post-Employment Duty of Trust and Loyalty Duration Indeterminacy Constraint establishes that the confidentiality obligation persists for an indeterminate period after the professional relationship ends and cannot be discharged by the mere passage of time. The Confidentiality Duration Indeterminacy Principle holds that duration must be assessed contextually based on the nature of the information and the potential for harm. Competing against perpetual obligation, the Competitive Employment Freedom principle implies that indefinite career restriction disproportionate to any remaining protective interest is not ethically required. A deontological reading treats the duty as categorical and non-contingent on harm; a consequentialist reading would permit expiration when the information loses competitive sensitivity.
Uncertainty is created by the absence of any agreed standard for measuring when design information loses competitive sensitivity, by the possibility that information considered obsolete by one metric retains value by another, and by the difficulty of distinguishing between information that has entered the public domain through regulatory approval and information that remains proprietary despite partial disclosure.
Engineer A accumulated confidential and proprietary design information about Company X's facility designs during government regulatory employment. The Board acknowledges that the duration of the confidentiality obligation is indeterminate but declines to specify when it ends. Company X's facility design information may retain competitive sensitivity for an extended and uncertain period, particularly given the long operational lifecycles of the relevant facilities. The NSPE Code does not establish a fixed expiration for post-employment confidentiality duties.
If Company X and Company Y become adversaries in a regulatory or legal proceeding, is Engineer A categorically barred from contributing technical analysis on Company Y's behalf, even analysis she characterizes as drawing only on general expertise, given her prior government access to Company X's confidential submissions?
The Former Client Adversarial Participation Prohibition, grounded in BER Case 85-4, bars Engineer A from switching sides in any proceeding where her prior access to Company X's confidential information creates a structural conflict, regardless of whether she explicitly uses that information. The Confidential Information Mental Segregation Impossibility Recognition Capability establishes that cognitive compartmentalization of deeply internalized technical knowledge is not reliably achievable. The Loyalty Obligation to Company Y within ethical limits creates pressure to contribute to Company Y's position in adversarial proceedings, but that obligation is bounded by the categorical bar on adversarial participation against Company X.
Uncertainty arises because the rebuttal condition, that Engineer A's analysis draws only on general expertise without referencing Company X's confidential submissions, is practically unverifiable given the impossibility of mental segregation. The scope of the adversarial participation prohibition is also indeterminate: if it extends to all technical work in the facility design domain rather than only direct adversarial testimony, Engineer A's effective utility to Company Y in any contested regulatory context may be categorically foreclosed.
Engineer A holds structural knowledge of Company X's confidential facility design submissions. Company Y is a direct competitor of Company X. BER Case 85-4 established that an engineer who provided confidential information to one party in an adversarial proceeding cannot ethically accept retention by the opposing party, and that claimed naivety about the conflict does not serve as mitigation. If Company X and Company Y become adversaries in a regulatory or legal proceeding, Engineer A may be asked to contribute technical analysis drawing on her domain expertise without explicitly referencing Company X's confidential submissions.
Does the ethical permissibility of Engineer A accepting employment at Company Y depend on Company Y's hiring motivation, specifically, whether Company Y recruited Engineer A primarily for her general expertise or primarily for the competitive intelligence value of her government-acquired knowledge of Company X's design strategies?
The Post-Public-Service Competitor Employment Conflict Avoidance Obligation holds that the revolving door from regulatory access to competitive employment creates conflicts that cannot be managed through disclosure alone when the confidential information is directly relevant to the competitive relationship. The Regulatory Submission Confidentiality Protection Obligation prohibits use of confidential regulatory submissions for competitive advantage. The Competitive Employment Freedom principle permits Engineer A to accept private employment, but only where the hiring motivation is legitimate expertise recruitment rather than competitive intelligence acquisition. When hiring motivation is explicitly the latter, both Engineer A and Company Y bear independent ethical culpability.
Uncertainty arises because hiring motivation is rarely explicit and is difficult to verify from Engineer A's perspective alone. The rebuttal condition that would preserve the Board's permissive conclusion, that Engineer A's personal confidentiality maintenance is sufficient to neutralize Company Y's competitive intelligence motivation, is undermined when the structural knowledge Engineer A carries provides competitive advantage even without explicit disclosure.
Engineer A is offered a position at Company Y, a direct competitor of Company X. The Board's baseline conclusion permits the employment transition subject to confidentiality maintenance and pre-employment disclosure. However, the Board does not address the scenario in which Company Y's hiring decision is explicitly motivated by the competitive intelligence value of Engineer A's government-acquired knowledge of Company X's design strategies, rather than by her general engineering qualifications. If Company Y recruited Engineer A specifically to exploit her regulatory access, the employment transition may constitute a structured attempt to misappropriate Company X's confidential submissions through the back channel of a former government reviewer.