Step 2: Normative Requirements Pass (Discussion Section)

Extract principles, obligations, constraints, and capabilities from the discussion section

Post-Public Employment - City Engineer Transitioning to Consultant
Step 2 of 5

Discussion Section

Section Content:
Discussion:
This case has to do with what are commonly called “revolving door” constraints governing the ethics of high-level government employees (federal, state, municipal) who leave public employment to enter the private sector.
Such persons are – or can be – viewed as being in a position to unfairly profit from or otherwise trade upon the contacts, associations, influence, and special knowledge they acquired during their tenure as public servants.
Practices of concern include but are not limited to involvement in the solicitation of continuing contracts, assuming the management and oversight for active projects, participating in the solicitation of new work for which the employee had been directly involved as a public-sector employee, and related professional matters.
We start the discussion by reviewing the first case the Board of Ethical Review published, BER Case 58-1 .
In that case a foreign government agency invited proposals to complete a design and supervise construction of a hydroelectric project.
The basic plans for the project were in place and were prepared by a team of engineers working for a US government agency.
Several of those engineers negotiated with at least two AE firms with the intent of taking part in the design and supervision of the work.
The engineers formed a corporation to be part of a joint venture to design the hydroelectric project.
At about the time the various contract negotiations were wrapping up, the engineers resigned from their US government positions and entered into a contract with the foreign government to work on the hydroelectric project.
The Board was asked, “Was it a violation of the Canons of Ethics or the Rules of Professional Conduct for employees of the US Government, while still employed, to organize a new private company and negotiate a contract to take part in the design of a project for which they had prepared preliminary plans as employees of the Government?” In Case 58-1 , the Board began by noting “there can be no question of the basic right of an American citizen to resign from one position and accept another or initiate a business of his own.” The Board noted that they were not able to call witnesses to understand the exact circumstances of the case, but they pointed out, “It seems axiomatic that the personal and intimate knowledge of the project which the employees gained from their work on the preliminary design of the project and the acquaintance they made with the representatives of the owner of the project gave them many distinct advantages over any other firms who may have considered the offering of their services to the owner.
The crucial question is, therefore, ‘Were these advantages used unfairly?’” Said the Board: …They (the advantages) might have been used and in any case the possibility of the existence of one or more of these facets raises a cloud of doubt as to the purity of the enterprise.
It becomes a matter which might be considered under Section 19 of the Canons, which states: "The engineer will endeavor to protect the engineering profession collectively and individually from misrepresentation and misunderstanding." The Board concluded, “The… [engineers] in question have violated the spirit of the Canons and Rules, although the evidence does not prove them to be in violation of specific paragraph (sic), as now worded.” They went on to state, “it tends to bring dishonor to the profession of engineering if the [engineer] devotes his energies, while still employed, to promote his future practice or employment on the basis of having inside information which would lead to greater profits, if he can secure a position or enter into contract to work on further details of the identical project.” Case 58-1 included a dissent: The guiding principle behind the phrasing of the "Rules" is that the words mean exactly what they say-that there is no concealed, hidden, or obscure "intent." In my opinion the "Conclusion" of the report should be, "The Board believes that the [engineers] in question have not violated the Canons or Rules as they currently exist." This could be followed by a "Recommendation" that the Ethical Practices Committee be instructed to consider the desirability of adding another Rule… to make unethical a situation similar to the one considered, as well as for a situation where the employees were other than Government.
Since that first case, the Board has considered multiple situations where a professional engineer in private practice or an engineering firm also serves as a city, town, or county engineer.
While such cases are more directly concerned with dual employment, the situations are pertinent relative to many ethical considerations of transitional employment.
Three cases are illustrative.
In BER Case 63-5 , a small community retained a professional engineer, Engineer B, on a part-time basis to serve as city engineer.
Engineer B was engaged in full-time private practice and treated his part-time service to the community as a public service.
In addition to general advisory services to the city, Engineer B was selected by the city council for the preparation of plans and specifications for a city project.
In such cases, Engineer B was compensated on a normal professional fee basis over and above his monthly retainer.
The Board ruled that it is ethical for a professional engineer retained by a community on a part-time basis as a city engineer to prepare plans and specifications for a project for the same community, but in so acting the engineer must be scrupulously careful that his advice is not influenced by his secondary interest as the engineer likely to be retained for the design of the project.
The Board noted that “it is axiomatic that a professional person may not take action or make decisions which would divide his loyalties or interests from those of his employer or client.” Among the issues the Board considered in BER Case No. 63-5 was the practical question of the engineer passing on the adequacy of his own plans in his capacity as city engineer.
The Board noted that there is no requirement in the NSPE Code that an engineer’s plans for a client must be reviewed by an engineer employed or retained by the client.
The Board noted that the client had the right of review by its own engineer, but it may waive its right, as it did in Case 63-5 , and under those circumstances, the engineer was acting in a dual capacity but not a divided one.
In BER Case 74-2 , the Board considered a case involving a state law that required that every municipality have a municipal engineer whose duties and compensation were to be fixed by a municipal ordinance.
But many of the smaller communities in the state did not have and could not afford full-time municipal engineers or supporting staff personnel for a full-time office.
In such instances the smaller communities retained the services of a consulting firm in private practice and appointed a principal of the firm as the municipal engineer.
Such a municipal engineer was paid either on a cost-plus basis or a flat monthly retainer—usually a relatively low amount.
The municipal engineer’s firm was thereafter usually retained for engineering services for capital improvement projects needed by the municipality.
In deciding that it was ethical for the engineer – who was not a municipal employee, but whose compensation was paid on a retainer or fee basis -- to serve as municipal engineer and participate in a consulting firm providing engineering services to the same municipality under the stated conditions, the Board determined that the public interest was best served by providing the small municipalities with the most competent engineering services which they can acquire.
It was assumed by the Board that the state law was intended to achieve this end.
More recently, BER Case 11-12 considered the situation of Engineer A, who served as the part-time town engineer for Smithtown and also had a consulting engineering practice.
With Engineer A's advice and concurrence, Smithtown selected Engineer B to provide design services for a local road project.
Following the selection and after Engineer B began to perform preliminary design services, Engineer A, in his role as town engineer, reviewed Engineer B’s preliminary work and became convinced Engineer B’s performance on the contract did not meet the standards as outlined in Engineer B’s contract.
Following the termination of Engineer B under the terms and conditions of his contract with the town, Engineer A offered, and Smithtown agreed, that Engineer A's firm should perform the design work for the local road project for Smithtown.
In determining it would not be ethical for Engineer A to offer and agree to perform the work for Smithtown, the Board observed that serious ethical constraints would preclude the selection of Engineer A by the town to perform the road design work.
Because Engineer A was an officer or principal of his engineering firm, according to NSPE Code of Ethics Section II.4.e, Engineer A was not eligible to provide engineering services to Smithtown for the local road project.
This conclusion is based upon the language of Code Section II.4.e and is irrespective of whether the town’s procurement laws were scrupulously followed.
The Board further opined that the disclosure of any further circumstances would not be sufficient to avoid a conflict of interest or the appearance of a conflict of interest.
Conflicts of interest feature prominently in transitional employment situations.
BER Case 14-8 for example – which is in many ways the converse of the situation Engineer D faces in the present case – describes how Engineer A worked for a private company and stamped a water rights analysis for a client, and that analysis was working its way through the court system.
During the legal review, Engineer A resigned from their firm and went to work for the State – the State being an objector to the analysis Engineer A prepared.
The Board was asked to weigh in on Engineer A’s ethical obligations.
The case discussion noted Engineer A’s ongoing duty both to their former employer and the private client.
Engineer A could not have disclosed, participated in or represented the State's interest in connection with this proceeding unless Engineer A first obtained the permission/consent of Engineer A's former private firm employer and also the client.
The BER discussion and conclusion recommended: Engineer A should be assigned other duties by the State, remain isolated from the State's water rights case involving Engineer A's former employer and its client—and the State should recognize and respect Engineer A's ethical obligations in this matter.
Any involvement by Engineer A in the State's case could potentially compromise the interests of all parties—the former employer, the private client, and the State—as Engineer A's dual role and his professional opinion/judgment—as an employee of the private firm and now as a State employee—could be called into question—by one of the parties, the public, or the media.
As a final example, BER Case 15-8 offers direct guidance on the ethics of transitional employment.
Engineer P is a “top” official in State X highway department who would like to leave and become an executive in an architecture/engineering (AE) firm.
Engineer P requested permission from the State X highway department to accept the new position; however, the State X highway department refused to grant permission, noting that, in accepting the position, Engineer P would be in violation of the state law that requires top State X highway officials to wait a year after leaving the highway department before accepting positions with firms with which the department does business.
In response, Engineer P left the State X highway department and joined the AE firm not as an “employee” but as an “independent contractor.” The board was asked if it was ethical for Engineer P to leave the State X highway department and join the AE firm in this way.
The BER pointed out a potential conflict of interest existed between Engineer P’s obligations to his former employer—the State X highway department—and the party with which Engineer P was now contracting, the AE firm.
They also noted that while disclosure of a desired new employment relationship had been made, disclosure alone was not sufficient.
The BER stated, “the agreement for a one-year hiatus after leaving government service before accepting related employment is not supported by disguising the employment as ‘independent contracting’.” The BER concluded: The fact that Engineer P proceeded to join the architecture/engineering firm as an “independent contractor” instead of as an “executive employee” was an apparent way of circumventing state law.
The Board of Ethical Review believes that Engineer P’s actions were unethical.
We now turn to the present case, the situation of Engineer D who resigned the position as City Engineer in a mid-sized municipality, and shortly thereafter accepted the position of “associate” at Firm AE&R, a consultant with whom Engineer D would have regularly interacted during tenure with the City.
The facts of the case specifically note Engineer A's employment contract with the City did not include a revolving door prohibition such as Engineer P faced in Case 15-8 .
Thus, on the face of the matter, it would seem there is no legal barrier to Engineer A accepting employment with Firm AE&R.
Case 58-1 and other cases since then support the engineer’s right of employment.
But that does not mean such employment would exempt Engineer A from the ethical requirements and obligations of the NSPE Code of Ethics.
What are some of these ethical requirements and obligations?
Among the most obvious are Code Sections II.4.c and III.6 which prohibit engineers from advancing their professional careers by any improper or questionable method.
Likewise, Code Section II.5.b would prohibit the principals of Firm AE&R from inducing Engineer A to join the firm as a way of influencing the awarding of city contracts for improper reasons not related to Engineer A’s qualifications and experience.
The facts of the case are silent on these matters, and the Board takes this to mean no violation occurred.
Some might assert that because Engineer A's employment contract with the City did not include a revolving door prohibition, nothing more needs to be said.
But the BER does not hold this perspective.
Case 58-1 speaks of the “purity of the enterprise”, of avoiding “dishonor to the profession,” and how engineers must consider not only the letter but the spirit of the ethics code.
Consistent with Fundamental Canon 1.6, such values form the context of an engineer’s professional relationships and apply in this case.
Though revolving door prohibitions are not specifically in effect, the spirit of such provisions can guide multiple aspects of Engineer D’s employment activities.
For example, the BER believes Engineer D’s prior responsibilities with the City for projects currently under contract by D’s new employer would raise concerns about objectivity and fairness if Firm AE&R directly placed Engineer D in responsible charge of those projects as a consultant.
In this situation, disclosure by Engineer D and acceptance by the City may cure the matter.
Alternatively, Engineer D can follow the recommendations in Case 14-8 and remain isolated from former projects until those contracts lapse.
Confidentiality is another ethical obligation that continues after one severs employment (Code Section III.4).
Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties or employment with the City.
That is, Engineer D should not be allowed to breach confidentiality for personal gain.
Third, as a public official who transitions to private practice, Engineer D should not unfairly profit from or otherwise trade upon the contacts, associations, and special knowledge she acquired during tenure as a public servant.
In particular this would apply to direct procurement activities.
But does this mean Engineer D is automatically precluded from using D’s professional knowledge and expertise to serve the City in a consulting role?
The Board sees room for accommodation.
Past BER cases affirm that full disclosure by the engineer (i.e., Engineer D) coupled with careful and thoughtful acceptance by the client (i.e., the City) can be sufficient to cure “known or potential conflicts of interest that could influence or appear to influence the engineer’s judgment or the quality of their services” (II.4.a).
In evaluating disclosed information, important factors include avoiding divided interests by the engineer, advancing the best interests of the client, and complying with procurement requirements.
While approval through disclosure is not automatic, ample precedent has shown that within many contexts the parties directly involved are in the best position to serve the public interest by providing the most competent engineering services available.
What about marginal situations, or conditions where a known or potential conflict would be prohibitive or too complex to set aside?
Here, as was done in Case 15-8 , an embargo or "cooling off" period, often one-year duration, can ameliorate such concerns.
That is, as appropriate and prudent, Engineer D could voluntarily abstain from participation in procurement matters before the City, or before any other agency for which the City is or was the approving authority, for an agreed period of say, one year after she leaves the public job.
These transitional employment practices, in the spirit of NSPE Code of Ethics, are intended to help Engineer D engage only in conduct that is honorable, responsible, ethical, and lawful so as to enhance the honor, reputation, and usefulness of the engineering profession.
Principles Extraction
LLM Prompt
DUAL PRINCIPLE EXTRACTION - Ethical Principles Analysis THEORETICAL CONTEXT (Chapter 2.2.2): - Principles are ABSTRACT ethical foundations requiring extensional definition through cases - They function like constitutional principles - open-textured and requiring interpretation - Principles mediate moral ideals into concrete reality through context-specific application - They cannot be applied deductively but require balancing and interpretation EXISTING PRINCIPLE CLASSES IN ONTOLOGY: - Competence Principle: Balances professional autonomy with recognition of limitations and need for collaboration. - Confidentiality Principle: Must be balanced against public safety obligations and legal disclosure requirements. - Domain-Specific Principle: Examples: Environmental Stewardship (engineering), Patient Autonomy (medicine), Academic Freedom (education). These address domain-specific ethical ch - Environmental Stewardship Principle: Bridges engineering practice with broader environmental and societal responsibilities. - Ethical Principle: Legacy synonym for Principle. Use :Principle for new concepts. - Fundamental Ethical Principle: Examples: Public Welfare Paramount, Respect for Persons, Justice, Beneficence. These require extensive interpretation and balancing in specific contex - Integrity Principle: Central to professional identity formation and trust maintenance in professional relationships. - Principle: An information content entity representing ethical values and guidelines for conduct. This is the P component of the formal specification D=(R,P,O,S,R - Principle Argument: An argument based on fundamental ethical principles or values. - Principle Refinement: Capability to evolve principles as inconsistencies are resolved and new cases are added (GenEth system, Anderson & Anderson 2018) - Professional Virtue Principle: Examples: Integrity, Competence, Honesty, Professional Courage, Accountability. These shape professional character and decision-making. - Public Welfare Principle: Requires contextual interpretation to balance against client confidentiality and employer loyalty when public safety is at risk. - Relational Principle: Examples: Confidentiality, Loyalty, Fairness, Transparency, Respect for Autonomy. These govern interpersonal professional dynamics. - Transparency Principle: Essential for maintaining trust and enabling stakeholder participation in professional decisions. === TASK === From the following case text (discussion section), extract information at TWO levels: LEVEL 1 - NEW PRINCIPLE CLASSES: Identify ethical principles that appear to be NEW types not covered by existing classes above. Look for: - Fundamental ethical values being invoked - Abstract moral ideals guiding decisions - Constitutional-like principles requiring interpretation - Values that transcend specific rules or obligations For each NEW principle class, provide: - label: Clear principle name (e.g., "Environmental Stewardship", "Professional Autonomy") - definition: What moral ideal this principle represents - abstract_nature: The abstract ethical foundation (justice, welfare, autonomy, etc.) - extensional_examples: Concrete cases/situations where this principle applies - value_basis: Core moral value underlying the principle - application_context: Professional domains or situations where relevant - operationalization: How this abstract principle becomes concrete in practice - balancing_requirements: What other principles it typically must be balanced against - examples_from_case: How this principle appears in the case text LEVEL 2 - PRINCIPLE INDIVIDUALS: Identify specific instances where principles are invoked or applied. For each instance: - identifier: Unique identifier for this principle instance (e.g., "PublicSafety_Case8_Discussion") - principle_class: Which principle class it instantiates (use existing classes when possible) - concrete_expression: EXACT text showing how the principle is expressed - invoked_by: Who invokes or appeals to this principle - applied_to: What decision/situation/dilemma it applies to - interpretation: How the principle is interpreted in this specific context - balancing_with: Other principles that must be balanced against it - tension_resolution: How conflicts between principles are resolved - case_relevance: Why this principle matters in this specific case IMPORTANT: - Focus on ABSTRACT ethical foundations, not specific rules or procedures - Principles are broader than obligations - they generate obligations in context - Use EXACT quotes from case text where principles are expressed - Distinguish between the abstract principle CLASS and its concrete APPLICATION CASE TEXT: This case has to do with what are commonly called “revolving door” constraints governing the ethics of high-level government employees (federal, state, municipal) who leave public employment to enter the private sector. Such persons are – or can be – viewed as being in a position to unfairly profit from or otherwise trade upon the contacts, associations, influence, and special knowledge they acquired during their tenure as public servants. Practices of concern include but are not limited to involvement in the solicitation of continuing contracts, assuming the management and oversight for active projects, participating in the solicitation of new work for which the employee had been directly involved as a public-sector employee, and related professional matters. We start the discussion by reviewing the first case the Board of Ethical Review published, BER Case 58-1 . In that case a foreign government agency invited proposals to complete a design and supervise construction of a hydroelectric project. The basic plans for the project were in place and were prepared by a team of engineers working for a US government agency. Several of those engineers negotiated with at least two AE firms with the intent of taking part in the design and supervision of the work. The engineers formed a corporation to be part of a joint venture to design the hydroelectric project. At about the time the various contract negotiations were wrapping up, the engineers resigned from their US government positions and entered into a contract with the foreign government to work on the hydroelectric project. The Board was asked, “Was it a violation of the Canons of Ethics or the Rules of Professional Conduct for employees of the US Government, while still employed, to organize a new private company and negotiate a contract to take part in the design of a project for which they had prepared preliminary plans as employees of the Government?” In Case 58-1 , the Board began by noting “there can be no question of the basic right of an American citizen to resign from one position and accept another or initiate a business of his own.” The Board noted that they were not able to call witnesses to understand the exact circumstances of the case, but they pointed out, “It seems axiomatic that the personal and intimate knowledge of the project which the employees gained from their work on the preliminary design of the project and the acquaintance they made with the representatives of the owner of the project gave them many distinct advantages over any other firms who may have considered the offering of their services to the owner. The crucial question is, therefore, ‘Were these advantages used unfairly?’” Said the Board: …They (the advantages) might have been used and in any case the possibility of the existence of one or more of these facets raises a cloud of doubt as to the purity of the enterprise. It becomes a matter which might be considered under Section 19 of the Canons, which states: "The engineer will endeavor to protect the engineering profession collectively and individually from misrepresentation and misunderstanding." The Board concluded, “The… [engineers] in question have violated the spirit of the Canons and Rules, although the evidence does not prove them to be in violation of specific paragraph (sic), as now worded.” They went on to state, “it tends to bring dishonor to the profession of engineering if the [engineer] devotes his energies, while still employed, to promote his future practice or employment on the basis of having inside information which would lead to greater profits, if he can secure a position or enter into contract to work on further details of the identical project.” Case 58-1 included a dissent: The guiding principle behind the phrasing of the "Rules" is that the words mean exactly what they say-that there is no concealed, hidden, or obscure "intent." In my opinion the "Conclusion" of the report should be, "The Board believes that the [engineers] in question have not violated the Canons or Rules as they currently exist." This could be followed by a "Recommendation" that the Ethical Practices Committee be instructed to consider the desirability of adding another Rule… to make unethical a situation similar to the one considered, as well as for a situation where the employees were other than Government. Since that first case, the Board has considered multiple situations where a professional engineer in private practice or an engineering firm also serves as a city, town, or county engineer. While such cases are more directly concerned with dual employment, the situations are pertinent relative to many ethical considerations of transitional employment. Three cases are illustrative. In BER Case 63-5 , a small community retained a professional engineer, Engineer B, on a part-time basis to serve as city engineer. Engineer B was engaged in full-time private practice and treated his part-time service to the community as a public service. In addition to general advisory services to the city, Engineer B was selected by the city council for the preparation of plans and specifications for a city project. In such cases, Engineer B was compensated on a normal professional fee basis over and above his monthly retainer. The Board ruled that it is ethical for a professional engineer retained by a community on a part-time basis as a city engineer to prepare plans and specifications for a project for the same community, but in so acting the engineer must be scrupulously careful that his advice is not influenced by his secondary interest as the engineer likely to be retained for the design of the project. The Board noted that “it is axiomatic that a professional person may not take action or make decisions which would divide his loyalties or interests from those of his employer or client.” Among the issues the Board considered in BER Case No. 63-5 was the practical question of the engineer passing on the adequacy of his own plans in his capacity as city engineer. The Board noted that there is no requirement in the NSPE Code that an engineer’s plans for a client must be reviewed by an engineer employed or retained by the client. The Board noted that the client had the right of review by its own engineer, but it may waive its right, as it did in Case 63-5 , and under those circumstances, the engineer was acting in a dual capacity but not a divided one. In BER Case 74-2 , the Board considered a case involving a state law that required that every municipality have a municipal engineer whose duties and compensation were to be fixed by a municipal ordinance. But many of the smaller communities in the state did not have and could not afford full-time municipal engineers or supporting staff personnel for a full-time office. In such instances the smaller communities retained the services of a consulting firm in private practice and appointed a principal of the firm as the municipal engineer. Such a municipal engineer was paid either on a cost-plus basis or a flat monthly retainer—usually a relatively low amount. The municipal engineer’s firm was thereafter usually retained for engineering services for capital improvement projects needed by the municipality. In deciding that it was ethical for the engineer – who was not a municipal employee, but whose compensation was paid on a retainer or fee basis -- to serve as municipal engineer and participate in a consulting firm providing engineering services to the same municipality under the stated conditions, the Board determined that the public interest was best served by providing the small municipalities with the most competent engineering services which they can acquire. It was assumed by the Board that the state law was intended to achieve this end. More recently, BER Case 11-12 considered the situation of Engineer A, who served as the part-time town engineer for Smithtown and also had a consulting engineering practice. With Engineer A's advice and concurrence, Smithtown selected Engineer B to provide design services for a local road project. Following the selection and after Engineer B began to perform preliminary design services, Engineer A, in his role as town engineer, reviewed Engineer B’s preliminary work and became convinced Engineer B’s performance on the contract did not meet the standards as outlined in Engineer B’s contract. Following the termination of Engineer B under the terms and conditions of his contract with the town, Engineer A offered, and Smithtown agreed, that Engineer A's firm should perform the design work for the local road project for Smithtown. In determining it would not be ethical for Engineer A to offer and agree to perform the work for Smithtown, the Board observed that serious ethical constraints would preclude the selection of Engineer A by the town to perform the road design work. Because Engineer A was an officer or principal of his engineering firm, according to NSPE Code of Ethics Section II.4.e, Engineer A was not eligible to provide engineering services to Smithtown for the local road project. This conclusion is based upon the language of Code Section II.4.e and is irrespective of whether the town’s procurement laws were scrupulously followed. The Board further opined that the disclosure of any further circumstances would not be sufficient to avoid a conflict of interest or the appearance of a conflict of interest. Conflicts of interest feature prominently in transitional employment situations. BER Case 14-8 for example – which is in many ways the converse of the situation Engineer D faces in the present case – describes how Engineer A worked for a private company and stamped a water rights analysis for a client, and that analysis was working its way through the court system. During the legal review, Engineer A resigned from their firm and went to work for the State – the State being an objector to the analysis Engineer A prepared. The Board was asked to weigh in on Engineer A’s ethical obligations. The case discussion noted Engineer A’s ongoing duty both to their former employer and the private client. Engineer A could not have disclosed, participated in or represented the State's interest in connection with this proceeding unless Engineer A first obtained the permission/consent of Engineer A's former private firm employer and also the client. The BER discussion and conclusion recommended: Engineer A should be assigned other duties by the State, remain isolated from the State's water rights case involving Engineer A's former employer and its client—and the State should recognize and respect Engineer A's ethical obligations in this matter. Any involvement by Engineer A in the State's case could potentially compromise the interests of all parties—the former employer, the private client, and the State—as Engineer A's dual role and his professional opinion/judgment—as an employee of the private firm and now as a State employee—could be called into question—by one of the parties, the public, or the media. As a final example, BER Case 15-8 offers direct guidance on the ethics of transitional employment. Engineer P is a “top” official in State X highway department who would like to leave and become an executive in an architecture/engineering (AE) firm. Engineer P requested permission from the State X highway department to accept the new position; however, the State X highway department refused to grant permission, noting that, in accepting the position, Engineer P would be in violation of the state law that requires top State X highway officials to wait a year after leaving the highway department before accepting positions with firms with which the department does business. In response, Engineer P left the State X highway department and joined the AE firm not as an “employee” but as an “independent contractor.”  The board was asked if it was ethical for Engineer P to leave the State X highway department and join the AE firm in this way. The BER pointed out a potential conflict of interest existed between Engineer P’s obligations to his former employer—the State X highway department—and the party with which Engineer P was now contracting, the AE firm. They also noted that while disclosure of a desired new employment relationship had been made, disclosure alone was not sufficient. The BER stated, “the agreement for a one-year hiatus after leaving government service before accepting related employment is not supported by disguising the employment as ‘independent contracting’.” The BER concluded: The fact that Engineer P proceeded to join the architecture/engineering firm as an “independent contractor” instead of as an “executive employee” was an apparent way of circumventing state law. The Board of Ethical Review believes that Engineer P’s actions were unethical. We now turn to the present case, the situation of Engineer D who resigned the position as City Engineer in a mid-sized municipality, and shortly thereafter accepted the position of “associate” at Firm AE&R, a consultant with whom Engineer D would have regularly interacted during tenure with the City. The facts of the case specifically note Engineer A's employment contract with the City did not include a revolving door prohibition such as Engineer P faced in Case 15-8 . Thus, on the face of the matter, it would seem there is no legal barrier to Engineer A accepting employment with Firm AE&R. Case 58-1 and other cases since then support the engineer’s right of employment. But that does not mean such employment would exempt Engineer A from the ethical requirements and obligations of the NSPE Code of Ethics. What are some of these ethical requirements and obligations? Among the most obvious are Code Sections II.4.c and III.6 which prohibit engineers from advancing their professional careers by any improper or questionable method. Likewise, Code Section II.5.b would prohibit the principals of Firm AE&R from inducing Engineer A to join the firm as a way of influencing the awarding of city contracts for improper reasons not related to Engineer A’s qualifications and experience.  The facts of the case are silent on these matters, and the Board takes this to mean no violation occurred. Some might assert that because Engineer A's employment contract with the City did not include a revolving door prohibition, nothing more needs to be said. But the BER does not hold this perspective. Case 58-1 speaks of the “purity of the enterprise”, of avoiding “dishonor to the profession,” and how engineers must consider not only the letter but the spirit of the ethics code. Consistent with Fundamental Canon 1.6, such values form the context of an engineer’s professional relationships and apply in this case. Though revolving door prohibitions are not specifically in effect, the spirit of such provisions can guide multiple aspects of Engineer D’s employment activities. For example, the BER believes Engineer D’s prior responsibilities with the City for projects currently under contract by D’s new employer would raise concerns about objectivity and fairness if Firm AE&R directly placed Engineer D in responsible charge of those projects as a consultant. In this situation, disclosure by Engineer D and acceptance by the City may cure the matter. Alternatively, Engineer D can follow the recommendations in Case 14-8 and remain isolated from former projects until those contracts lapse. Confidentiality is another ethical obligation that continues after one severs employment (Code Section III.4). Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties or employment with the City. That is, Engineer D should not be allowed to breach confidentiality for personal gain. Third, as a public official who transitions to private practice, Engineer D should not unfairly profit from or otherwise trade upon the contacts, associations, and special knowledge she acquired during tenure as a public servant. In particular this would apply to direct procurement activities.  But does this mean Engineer D is automatically precluded from using D’s professional knowledge and expertise to serve the City in a consulting role? The Board sees room for accommodation. Past BER cases affirm that full disclosure by the engineer (i.e., Engineer D) coupled with careful and thoughtful acceptance by the client (i.e., the City) can be sufficient to cure “known or potential conflicts of interest that could influence or appear to influence the engineer’s judgment or the quality of their services” (II.4.a). In evaluating disclosed information, important factors include avoiding divided interests by the engineer, advancing the best interests of the client, and complying with procurement requirements. While approval through disclosure is not automatic, ample precedent has shown that within many contexts the parties directly involved are in the best position to serve the public interest by providing the most competent engineering services available. What about marginal situations, or conditions where a known or potential conflict would be prohibitive or too complex to set aside? Here, as was done in Case 15-8 , an embargo or "cooling off" period, often one-year duration, can ameliorate such concerns. That is, as appropriate and prudent, Engineer D could voluntarily abstain from participation in procurement matters before the City, or before any other agency for which the City is or was the approving authority, for an agreed period of say, one year after she leaves the public job. These transitional employment practices, in the spirit of NSPE Code of Ethics, are intended to help Engineer D engage only in conduct that is honorable, responsible, ethical, and lawful so as to enhance the honor, reputation, and usefulness of the engineering profession. Respond with valid JSON in this format: { "new_principle_classes": [ { "label": "Sustainable Development", "definition": "Principle that engineering solutions must balance current needs with long-term environmental and societal impacts", "abstract_nature": "Intergenerational justice and environmental stewardship", "extensional_examples": ["Green building design", "Renewable energy projects", "Resource conservation"], "value_basis": "Responsibility to future generations", "application_context": ["Infrastructure projects", "Environmental engineering", "Urban planning"], "operationalization": "Through environmental impact assessments, lifecycle analysis, sustainable design criteria", "balancing_requirements": ["Economic feasibility", "Immediate safety needs", "Client requirements"], "examples_from_case": ["Engineer considered long-term environmental impacts", "balanced immediate needs with sustainability"], "source_text": "Engineer considered long-term environmental impacts and balanced immediate needs with sustainability" } ], "principle_individuals": [ { "identifier": "PublicSafety_Case8_Facts", "principle_class": "Public Safety", "concrete_expression": "the safety of the public must be held paramount", "invoked_by": ["Engineer L"], "applied_to": ["stormwater management system design"], "interpretation": "Safety considerations override cost savings in drainage design", "source_text": "the safety of the public must be held paramount", "balancing_with": ["Cost Efficiency", "Client Interests"], "tension_resolution": "Safety takes precedence even if it increases project costs", "case_relevance": "Critical for evaluating adequacy of proposed drainage solution" } ] }
Saved: 2025-12-20 13:54
LLM Response
```json
{
    "new_principle_classes": [
        {
            "label": "Purity of Enterprise",
            "definition": "Principle that professional transitions and business arrangements must be free from improper advantage, undue influence, or exploitation of public position",
            "abstract_nature": "Fairness and legitimacy in professional transitions",
            "extensional_examples": ["Government employees transitioning to private sector", "Public officials joining firms they previously regulated", "Engineers moving between competing firms"],
            "value_basis": "Fairness, equal opportunity, and prevention of corruption",
            "application_context": ["Revolving door situations", "Public-private transitions", "Employment transitions involving regulatory relationships"],
            "operationalization": "Through cooling-off periods, disclosure requirements, recusal from specific projects, avoiding unfair use of insider knowledge",
            "balancing_requirements": ["Right to employment", "Professional autonomy", "Public trust", "Economic opportunity"],
            "examples_from_case": ["Case 58-1 speaks of the 'purity of the enterprise'", "avoiding situations that raise 'a cloud of doubt as to the purity of the enterprise'"],
            "source_text": "The crucial question is, therefore, 'Were these advantages used unfairly?'... the possibility of the existence of one or more of these facets raises a cloud of doubt as to the purity of the enterprise"
        },
        {
            "label": "Professional Honor",
            "definition": "Principle that engineers must avoid conduct that brings dishonor to the profession, maintaining both the letter and spirit of ethical standards",
            "abstract_nature": "Collective professional reputation and dignity",
            "extensional_examples": ["Avoiding appearance of impropriety", "Maintaining professional dignity in transitions", "Upholding profession's reputation in public service"],
            "value_basis": "Professional dignity, collective reputation, public trust",
            "application_context": ["Employment transitions", "Public-private sector moves", "Situations involving potential conflicts of interest"],
            "operationalization": "Through adherence to both letter and spirit of ethics codes, avoiding questionable arrangements, maintaining transparency",
            "balancing_requirements": ["Individual rights", "Economic opportunities", "Legal compliance"],
            "examples_from_case": ["it tends to bring dishonor to the profession of engineering", "engage only in conduct that is honorable, responsible, ethical"],
            "source_text": "it tends to bring dishonor to the profession of engineering if the [engineer] devotes his energies, while still employed, to promote his future practice or employment"
        }
    ],
    "principle_individuals": [
        {
            "identifier": "RightToEmployment_Case58-1",
            "principle_class": "Professional Autonomy",
            "concrete_expression": "there can be no question of the basic right of an American citizen to resign from one position and accept another or initiate a business of his own",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Engineers transitioning from government to private sector"],
            "interpretation": "Fundamental right to change employment cannot be denied but must be exercised ethically",
            "source_text": "there can be no question of the basic right of an American citizen to resign from one position and accept another or initiate a business of his own",
            "balancing_with": ["Purity of Enterprise", "Public Trust", "Fairness"],
            "tension_resolution": "Right exists but must be exercised without unfair use of advantages",
            "case_relevance": "Establishes baseline that employment transitions are permitted but subject to ethical constraints"
        },
        {
            "identifier": "PublicWelfare_Case74-2",
            "principle_class": "Public Welfare Principle",
            "concrete_expression": "the public interest was best served by providing the small municipalities with the most competent engineering services which they can acquire",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Dual role of consulting engineers as municipal engineers"],
            "interpretation": "Public welfare may justify dual roles when it ensures competent engineering services for resource-limited communities",
            "source_text": "the public interest was best served by providing the small municipalities with the most competent engineering services which they can acquire",
            "balancing_with": ["Conflict of Interest concerns", "Divided Loyalty concerns"],
            "tension_resolution": "Public benefit of competent services outweighs potential conflicts with proper safeguards",
            "case_relevance": "Demonstrates how public welfare can justify arrangements that might otherwise raise concerns"
        },
        {
            "identifier": "Confidentiality_EngineerD",
            "principle_class": "Confidentiality Principle",
            "concrete_expression": "Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties or employment with the City",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Engineer D's transition from City Engineer to private consultant"],
            "interpretation": "Confidentiality obligations survive employment termination and prohibit use for personal gain",
            "source_text": "Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties or employment with the City",
            "balancing_with": ["Professional Autonomy", "Right to use professional knowledge"],
            "tension_resolution": "Confidential information cannot be used even in new employment",
            "case_relevance": "Establishes continuing obligation that constrains Engineer D's activities at new firm"
        },
        {
            "identifier": "Transparency_Disclosure",
            "principle_class": "Transparency Principle",
            "concrete_expression": "full disclosure by the engineer (i.e., Engineer D) coupled with careful and thoughtful acceptance by the client (i.e., the City) can be sufficient to cure known or potential conflicts of interest",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Managing conflicts in Engineer D's transition"],
            "interpretation": "Transparency through disclosure can remedy conflicts when coupled with informed consent",
            "source_text": "full disclosure by the engineer (i.e., Engineer D) coupled with careful and thoughtful acceptance by the client (i.e., the City) can be sufficient to cure 'known or potential conflicts of interest'",
            "balancing_with": ["Conflict of Interest concerns", "Professional Autonomy"],
            "tension_resolution": "Disclosure plus acceptance can permit otherwise problematic arrangements",
            "case_relevance": "Provides pathway for Engineer D to work on City matters with proper disclosure"
        },
        {
            "identifier": "PurityEnterprise_Case58-1",
            "principle_class": "Purity of Enterprise",
            "concrete_expression": "the possibility of the existence of one or more of these facets raises a cloud of doubt as to the purity of the enterprise",
            "invoked_by": ["Board of Ethical Review in Case 58-1"],
            "applied_to": ["Government engineers forming company while employed"],
            "interpretation": "Even appearance of unfair advantage violates principle of pure/clean professional transitions",
            "source_text": "the possibility of the existence of one or more of these facets raises a cloud of doubt as to the purity of the enterprise",
            "balancing_with": ["Right to Employment", "Professional Autonomy"],
            "tension_resolution": "Appearance of impropriety alone sufficient to find ethical violation",
            "case_relevance": "Establishes precedent that appearance matters in transitional employment"
        },
        {
            "identifier": "ProfessionalHonor_Conclusion",
            "principle_class": "Professional Honor",
            "concrete_expression": "engage only in conduct that is honorable, responsible, ethical, and lawful so as to enhance the honor, reputation, and usefulness of the engineering profession",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Engineer D's transitional employment practices"],
            "interpretation": "Professional transitions must enhance, not diminish, the profession's honor and reputation",
            "source_text": "engage only in conduct that is honorable, responsible, ethical, and lawful so as to enhance the honor, reputation, and usefulness of the engineering profession",
            "balancing_with": ["Individual economic interests", "Right to employment"],
            "tension_resolution": "Professional honor takes precedence over individual advantage",
            "case_relevance": "Overarching principle guiding all of Engineer D's transition decisions"
        },
        {
            "identifier": "Fairness_UnfairAdvantage",
            "principle_class": "Relational Principle",
            "concrete_expression": "Engineer D should not unfairly profit from or otherwise trade upon the contacts, associations, and special knowledge she acquired during tenure as a public servant",
            "invoked_by": ["Board of Ethical Review"],
            "applied_to": ["Engineer D's use of knowledge from City position"],
            "interpretation": "Fairness prohibits exploiting public position for private gain",
            "source_text": "Engineer D should not unfairly profit from or otherwise trade upon the contacts, associations, and special knowledge she acquired during tenure as a public servant",
            "balancing_with": ["Right to use professional expertise", "Professional Autonomy"],
            "tension_resolution": "Distinguishes between legitimate use of expertise and unfair exploitation",
            "case_relevance": "Key constraint on how Engineer D can leverage past position"
        }
    ]
}
```
Obligations Extraction
LLM Prompt
You are an expert in professional ethics analyzing a case for obligations (professional duties and requirements). Based on the literature: - Obligations are CONCRETE PROFESSIONAL DUTIES derived from abstract principles (Hallamaa & Kalliokoski 2022) - They specify what professionals MUST, SHOULD, or MUST NOT do (Dennis et al. 2016) - Obligations have deontic force and are enforceable (Wooldridge & Jennings 1995) - They operationalize principles in specific contexts (Kong et al. 2020) Your task is to: 1. Identify NEW OBLIGATION CLASSES not in the existing ontology 2. Extract SPECIFIC OBLIGATION INDIVIDUALS from the case EXISTING OBLIGATIONS IN ONTOLOGY (check if your identified obligations match these before creating new classes): - Attribution Obligation: Duty to properly cite and acknowledge all sources, tools, and methods used in creating professional deliverables - Collegial Obligation: Duties toward professional peers including respect, fairness, and credit for work - Competence Obligation: Requirement to perform services only in areas of competence (NSPE II.2) - Conditional Obligation: Obligations that apply only when specific conditions are met - Confidentiality Obligation: Duty to protect confidential information of clients or employers (NSPE III.4) - Defeasible Obligation: Obligations that admit justified exceptions under specified conditions (Ganascia 2007) - Disclosure Obligation: Requirement to inform stakeholders about conflicts, limitations, or risks (NSPE II.3.a) - Ethical Obligation: Obligations arising from ethical principles beyond legal requirements - Legal Obligation: Obligations arising from legal requirements and regulations - Mandatory Obligation: Obligations that MUST be fulfilled (deontic force: mandatory) - Obligation: An information content entity expressing required actions or behaviors in professional contexts. This is the O component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs). - Prima Facie Obligation: Obligations that hold at first appearance but may be overridden by stronger duties (Anderson & Anderson) - Professional Obligation: A duty or responsibility arising from professional role or standards - Quality Assurance Obligation: Requirement to implement appropriate review and verification processes for all professional deliverables before submission - Reporting Obligation: Duty to report violations or unsafe conditions to appropriate authorities - Responsible Charge Obligation: Duty to maintain active engagement and personal decision-making authority throughout engineering process from conception to completion - Safety Obligation: Duty to hold paramount the safety, health, and welfare of the public (NSPE I.1) - Technology Competence Obligation: Requirement to understand and verify the capabilities, limitations, and risks of technological tools used in professional practice - Technology Verification Obligation: Requirement to thoroughly verify and validate outputs from technological tools including AI before incorporating them into professional work Analyze this discussion section: This case has to do with what are commonly called “revolving door” constraints governing the ethics of high-level government employees (federal, state, municipal) who leave public employment to enter the private sector. Such persons are – or can be – viewed as being in a position to unfairly profit from or otherwise trade upon the contacts, associations, influence, and special knowledge they acquired during their tenure as public servants. Practices of concern include but are not limited to involvement in the solicitation of continuing contracts, assuming the management and oversight for active projects, participating in the solicitation of new work for which the employee had been directly involved as a public-sector employee, and related professional matters. We start the discussion by reviewing the first case the Board of Ethical Review published, BER Case 58-1 . In that case a foreign government agency invited proposals to complete a design and supervise construction of a hydroelectric project. The basic plans for the project were in place and were prepared by a team of engineers working for a US government agency. Several of those engineers negotiated with at least two AE firms with the intent of taking part in the design and supervision of the work. The engineers formed a corporation to be part of a joint venture to design the hydroelectric project. At about the time the various contract negotiations were wrapping up, the engineers resigned from their US government positions and entered into a contract with the foreign government to work on the hydroelectric project. The Board was asked, “Was it a violation of the Canons of Ethics or the Rules of Professional Conduct for employees of the US Government, while still employed, to organize a new private company and negotiate a contract to take part in the design of a project for which they had prepared preliminary plans as employees of the Government?” In Case 58-1 , the Board began by noting “there can be no question of the basic right of an American citizen to resign from one position and accept another or initiate a business of his own.” The Board noted that they were not able to call witnesses to understand the exact circumstances of the case, but they pointed out, “It seems axiomatic that the personal and intimate knowledge of the project which the employees gained from their work on the preliminary design of the project and the acquaintance they made with the representatives of the owner of the project gave them many distinct advantages over any other firms who may have considered the offering of their services to the owner. The crucial question is, therefore, ‘Were these advantages used unfairly?’” Said the Board: …They (the advantages) might have been used and in any case the possibility of the existence of one or more of these facets raises a cloud of doubt as to the purity of the enterprise. It becomes a matter which might be considered under Section 19 of the Canons, which states: "The engineer will endeavor to protect the engineering profession collectively and individually from misrepresentation and misunderstanding." The Board concluded, “The… [engineers] in question have violated the spirit of the Canons and Rules, although the evidence does not prove them to be in violation of specific paragraph (sic), as now worded.” They went on to state, “it tends to bring dishonor to the profession of engineering if the [engineer] devotes his energies, while still employed, to promote his future practice or employment on the basis of having inside information which would lead to greater profits, if he can secure a position or enter into contract to work on further details of the identical project.” Case 58-1 included a dissent: The guiding principle behind the phrasing of the "Rules" is that the words mean exactly what they say-that there is no concealed, hidden, or obscure "intent." In my opinion the "Conclusion" of the report should be, "The Board believes that the [engineers] in question have not violated the Canons or Rules as they currently exist." This could be followed by a "Recommendation" that the Ethical Practices Committee be instructed to consider the desirability of adding another Rule… to make unethical a situation similar to the one considered, as well as for a situation where the employees were other than Government. Since that first case, the Board has considered multiple situations where a professional engineer in private practice or an engineering firm also serves as a city, town, or county engineer. While such cases are more directly concerned with dual employment, the situations are pertinent relative to many ethical considerations of transitional employment. Three cases are illustrative. In BER Case 63-5 , a small community retained a professional engineer, Engineer B, on a part-time basis to serve as city engineer. Engineer B was engaged in full-time private practice and treated his part-time service to the community as a public service. In addition to general advisory services to the city, Engineer B was selected by the city council for the preparation of plans and specifications for a city project. In such cases, Engineer B was compensated on a normal professional fee basis over and above his monthly retainer. The Board ruled that it is ethical for a professional engineer retained by a community on a part-time basis as a city engineer to prepare plans and specifications for a project for the same community, but in so acting the engineer must be scrupulously careful that his advice is not influenced by his secondary interest as the engineer likely to be retained for the design of the project. The Board noted that “it is axiomatic that a professional person may not take action or make decisions which would divide his loyalties or interests from those of his employer or client.” Among the issues the Board considered in BER Case No. 63-5 was the practical question of the engineer passing on the adequacy of his own plans in his capacity as city engineer. The Board noted that there is no requirement in the NSPE Code that an engineer’s plans for a client must be reviewed by an engineer employed or retained by the client. The Board noted that the client had the right of review by its own engineer, but it may waive its right, as it did in Case 63-5 , and under those circumstances, the engineer was acting in a dual capacity but not a divided one. In BER Case 74-2 , the Board considered a case involving a state law that required that every municipality have a municipal engineer whose duties and compensation were to be fixed by a municipal ordinance. But many of the smaller communities in the state did not have and could not afford full-time municipal engineers or supporting staff personnel for a full-time office. In such instances the smaller communities retained the services of a consulting firm in private practice and appointed a principal of the firm as the municipal engineer. Such a municipal engineer was paid either on a cost-plus basis or a flat monthly retainer—usually a relatively low amount. The municipal engineer’s firm was thereafter usually retained for engineering services for capital improvement projects needed by the municipality. In deciding that it was ethical for the engineer – who was not a municipal employee, but whose compensation was paid on a retainer or fee basis -- to serve as municipal engineer and participate in a consulting firm providing engineering services to the same municipality under the stated conditions, the Board determined that the public interest was best served by providing the small municipalities with the most competent engineering services which they can acquire. It was assumed by the Board that the state law was intended to achieve this end. More recently, BER Case 11-12 considered the situation of Engineer A, who served as the part-time town engineer for Smithtown and also had a consulting engineering practice. With Engineer A's advice and concurrence, Smithtown selected Engineer B to provide design services for a local road project. Following the selection and after Engineer B began to perform preliminary design services, Engineer A, in his role as town engineer, reviewed Engineer B’s preliminary work and became convinced Engineer B’s performance on the contract did not meet the standards as outlined in Engineer B’s contract. Following the termination of Engineer B under the terms and conditions of his contract with the town, Engineer A offered, and Smithtown agreed, that Engineer A's firm should perform the design work for the local road project for Smithtown. In determining it would not be ethical for Engineer A to offer and agree to perform the work for Smithtown, the Board observed that serious ethical constraints would preclude the selection of Engineer A by the town to perform the road design work. Because Engineer A was an officer or principal of his engineering firm, according to NSPE Code of Ethics Section II.4.e, Engineer A was not eligible to provide engineering services to Smithtown for the local road project. This conclusion is based upon the language of Code Section II.4.e and is irrespective of whether the town’s procurement laws were scrupulously followed. The Board further opined that the disclosure of any further circumstances would not be sufficient to avoid a conflict of interest or the appearance of a conflict of interest. Conflicts of interest feature prominently in transitional employment situations. BER Case 14-8 for example – which is in many ways the converse of the situation Engineer D faces in the present case – describes how Engineer A worked for a private company and stamped a water rights analysis for a client, and that analysis was working its way through the court system. During the legal review, Engineer A resigned from their firm and went to work for the State – the State being an objector to the analysis Engineer A prepared. The Board was asked to weigh in on Engineer A’s ethical obligations. The case discussion noted Engineer A’s ongoing duty both to their former employer and the private client. Engineer A could not have disclosed, participated in or represented the State's interest in connection with this proceeding unless Engineer A first obtained the permission/consent of Engineer A's former private firm employer and also the client. The BER discussion and conclusion recommended: Engineer A should be assigned other duties by the State, remain isolated from the State's water rights case involving Engineer A's former employer and its client—and the State should recognize and respect Engineer A's ethical obligations in this matter. Any involvement by Engineer A in the State's case could potentially compromise the interests of all parties—the former employer, the private client, and the State—as Engineer A's dual role and his professional opinion/judgment—as an employee of the private firm and now as a State employee—could be called into question—by one of the parties, the public, or the media. As a final example, BER Case 15-8 offers direct guidance on the ethics of transitional employment. Engineer P is a “top” official in State X highway department who would like to leave and become an executive in an architecture/engineering (AE) firm. Engineer P requested permission from the State X highway department to accept the new position; however, the State X highway department refused to grant permission, noting that, in accepting the position, Engineer P would be in violation of the state law that requires top State X highway officials to wait a year after leaving the highway department before accepting positions with firms with which the department does business. In response, Engineer P left the State X highway department and joined the AE firm not as an “employee” but as an “independent contractor.”  The board was asked if it was ethical for Engineer P to leave the State X highway department and join the AE firm in this way. The BER pointed out a potential conflict of interest existed between Engineer P’s obligations to his former employer—the State X highway department—and the party with which Engineer P was now contracting, the AE firm. They also noted that while disclosure of a desired new employment relationship had been made, disclosure alone was not sufficient. The BER stated, “the agreement for a one-year hiatus after leaving government service before accepting related employment is not supported by disguising the employment as ‘independent contracting’.” The BER concluded: The fact that Engineer P proceeded to join the architecture/engineering firm as an “independent contractor” instead of as an “executive employee” was an apparent way of circumventing state law. The Board of Ethical Review believes that Engineer P’s actions were unethical. We now turn to the present case, the situation of Engineer D who resigned the position as City Engineer in a mid-sized municipality, and shortly thereafter accepted the position of “associate” at Firm AE&R, a consultant with whom Engineer D would have regularly interacted during tenure with the City. The facts of the case specifically note Engineer A's employment contract with the City did not include a revolving door prohibition such as Engineer P faced in Case 15-8 . Thus, on the face of the matter, it would seem there is no legal barrier to Engineer A accepting employment with Firm AE&R. Case 58-1 and other cases since then support the engineer’s right of employment. But that does not mean such employment would exempt Engineer A from the ethical requirements and obligations of the NSPE Code of Ethics. What are some of these ethical requirements and obligations? Among the most obvious are Code Sections II.4.c and III.6 which prohibit engineers from advancing their professional careers by any improper or questionable method. Likewise, Code Section II.5.b would prohibit the principals of Firm AE&R from inducing Engineer A to join the firm as a way of influencing the awarding of city contracts for improper reasons not related to Engineer A’s qualifications and experience.  The facts of the case are silent on these matters, and the Board takes this to mean no violation occurred. Some might assert that because Engineer A's employment contract with the City did not include a revolving door prohibition, nothing more needs to be said. But the BER does not hold this perspective. Case 58-1 speaks of the “purity of the enterprise”, of avoiding “dishonor to the profession,” and how engineers must consider not only the letter but the spirit of the ethics code. Consistent with Fundamental Canon 1.6, such values form the context of an engineer’s professional relationships and apply in this case. Though revolving door prohibitions are not specifically in effect, the spirit of such provisions can guide multiple aspects of Engineer D’s employment activities. For example, the BER believes Engineer D’s prior responsibilities with the City for projects currently under contract by D’s new employer would raise concerns about objectivity and fairness if Firm AE&R directly placed Engineer D in responsible charge of those projects as a consultant. In this situation, disclosure by Engineer D and acceptance by the City may cure the matter. Alternatively, Engineer D can follow the recommendations in Case 14-8 and remain isolated from former projects until those contracts lapse. Confidentiality is another ethical obligation that continues after one severs employment (Code Section III.4). Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties or employment with the City. That is, Engineer D should not be allowed to breach confidentiality for personal gain. Third, as a public official who transitions to private practice, Engineer D should not unfairly profit from or otherwise trade upon the contacts, associations, and special knowledge she acquired during tenure as a public servant. In particular this would apply to direct procurement activities.  But does this mean Engineer D is automatically precluded from using D’s professional knowledge and expertise to serve the City in a consulting role? The Board sees room for accommodation. Past BER cases affirm that full disclosure by the engineer (i.e., Engineer D) coupled with careful and thoughtful acceptance by the client (i.e., the City) can be sufficient to cure “known or potential conflicts of interest that could influence or appear to influence the engineer’s judgment or the quality of their services” (II.4.a). In evaluating disclosed information, important factors include avoiding divided interests by the engineer, advancing the best interests of the client, and complying with procurement requirements. While approval through disclosure is not automatic, ample precedent has shown that within many contexts the parties directly involved are in the best position to serve the public interest by providing the most competent engineering services available. What about marginal situations, or conditions where a known or potential conflict would be prohibitive or too complex to set aside? Here, as was done in Case 15-8 , an embargo or "cooling off" period, often one-year duration, can ameliorate such concerns. That is, as appropriate and prudent, Engineer D could voluntarily abstain from participation in procurement matters before the City, or before any other agency for which the City is or was the approving authority, for an agreed period of say, one year after she leaves the public job. These transitional employment practices, in the spirit of NSPE Code of Ethics, are intended to help Engineer D engage only in conduct that is honorable, responsible, ethical, and lawful so as to enhance the honor, reputation, and usefulness of the engineering profession. Extract obligations following this JSON structure: { "new_obligation_classes": [ { "label": "Clear, specific obligation class name", "definition": "What this type of obligation requires professionals to do", "derived_from_principle": "Which principle this operationalizes (e.g., 'Public Safety', 'Honesty')", "duty_type": "professional|legal|ethical|societal", "enforcement_mechanism": "How this obligation is typically enforced", "violation_consequences": "What happens when this obligation is violated", "examples_from_case": ["Example 1 from the case", "Example 2"], "source_text": "EXACT text snippet from case where this obligation is identified (max 200 characters)", "confidence": 0.0-1.0, "reasoning": "Why this is a new class not in existing ontology" } ], "obligation_individuals": [ { "identifier": "Unique name for this specific obligation instance", "obligation_class": "Name of the obligation class (new or existing)", "obligated_party": "Who has this obligation (e.g., 'Engineer L', 'All Licensed PEs')", "obligation_statement": "The specific duty statement (e.g., 'Report safety risks to authorities')", "derived_from": "Source principle or law (e.g., 'NSPE Code', 'State Law')", "enforcement_context": "How enforced in this case", "temporal_scope": "When this obligation applies", "compliance_status": "met|unmet|unclear|pending", "case_context": "How this obligation manifests in the specific case", "source_text": "EXACT text snippet from case where this obligation is mentioned (max 200 characters)", "is_existing_class": true/false, "confidence": 0.0-1.0 } ] } Focus on: 1. NEW obligation types that represent novel professional duties 2. Specific obligation instances showing how duties apply in this case 3. The relationship between obligations and the principles they operationalize 4. Enforcement mechanisms and compliance status Return ONLY the JSON structure, no additional text.
Saved: 2025-12-20 13:55
LLM Response
```json
{
  "new_obligation_classes": [
    {
      "label": "Post-Employment Restriction Obligation",
      "definition": "Duty to observe waiting periods and restrictions on employment activities after leaving public service positions",
      "derived_from_principle": "Public Trust and Fairness",
      "duty_type": "ethical",
      "enforcement_mechanism": "State laws, professional codes, employment contracts",
      "violation_consequences": "Legal sanctions, professional censure, loss of reputation",
      "examples_from_case": ["one-year hiatus after leaving government service", "revolving door constraints"],
      "source_text": "state law that requires top State X highway officials to wait a year after leaving the highway department before accepting positions",
      "confidence": 0.9,
      "reasoning": "Distinct from existing obligations - specifically addresses temporal restrictions on post-public employment activities not covered by general conflict of interest obligations"
    },
    {
      "label": "Fair Advantage Obligation",
      "definition": "Duty not to unfairly exploit insider knowledge, contacts, or influence gained from previous positions for personal or professional gain",
      "derived_from_principle": "Fairness and Integrity",
      "duty_type": "ethical",
      "enforcement_mechanism": "Professional review boards, ethics committees",
      "violation_consequences": "Professional censure, reputational damage, contract nullification",
      "examples_from_case": ["not unfairly profit from contacts and special knowledge", "advantages used unfairly"],
      "source_text": "Engineer D should not unfairly profit from or otherwise trade upon the contacts, associations, and special knowledge",
      "confidence": 0.85,
      "reasoning": "Goes beyond confidentiality to address unfair competitive advantages from insider position - not covered by existing obligation classes"
    },
    {
      "label": "Isolation Obligation",
      "definition": "Duty to remain separated from specific projects or matters where prior involvement creates conflicts of interest",
      "derived_from_principle": "Impartiality and Objectivity",
      "duty_type": "professional",
      "enforcement_mechanism": "Employer policies, professional standards",
      "violation_consequences": "Reassignment, termination, ethics violations",
      "examples_from_case": ["remain isolated from former projects", "assigned other duties by the State"],
      "source_text": "Engineer D can follow the recommendations in Case 14-8 and remain isolated from former projects until those contracts lapse",
      "confidence": 0.8,
      "reasoning": "Specific operational duty to physically/organizationally separate from certain work - distinct from general conflict of interest obligations"
    }
  ],
  "obligation_individuals": [
    {
      "identifier": "EngineerD_PostEmployment_Isolation",
      "obligation_class": "Isolation Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Must remain isolated from City projects currently under contract by Firm AE&R",
      "derived_from": "NSPE Code spirit and BER Case 14-8",
      "enforcement_context": "Firm AE&R internal policies and City oversight",
      "temporal_scope": "Until existing City contracts lapse",
      "compliance_status": "pending",
      "case_context": "Engineer D joined Firm AE&R after serving as City Engineer",
      "source_text": "Engineer D can follow the recommendations in Case 14-8 and remain isolated from former projects until those contracts lapse",
      "is_existing_class": false,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerD_Confidentiality_PostEmployment",
      "obligation_class": "Confidentiality Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Must not use or disclose confidential information acquired during City employment",
      "derived_from": "NSPE Code Section III.4",
      "enforcement_context": "Professional ethics enforcement",
      "temporal_scope": "Perpetual after leaving City employment",
      "compliance_status": "unclear",
      "case_context": "Engineer D transitioned from City Engineer to private consultant",
      "source_text": "Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerD_FairAdvantage_Procurement",
      "obligation_class": "Fair Advantage Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Must not unfairly profit from contacts and knowledge acquired as City Engineer",
      "derived_from": "NSPE Fundamental Canon 1.6",
      "enforcement_context": "Professional review and public scrutiny",
      "temporal_scope": "Ongoing after leaving City position",
      "compliance_status": "unclear",
      "case_context": "Engineer D's new role at firm that contracts with City",
      "source_text": "Engineer D should not unfairly profit from or otherwise trade upon the contacts, associations, and special knowledge",
      "is_existing_class": false,
      "confidence": 0.9
    },
    {
      "identifier": "EngineerD_Disclosure_ConflictsCure",
      "obligation_class": "Disclosure Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Must fully disclose potential conflicts to City regarding former responsibilities",
      "derived_from": "NSPE Code Section II.4.a",
      "enforcement_context": "City approval process",
      "temporal_scope": "When engaging in City-related work at Firm AE&R",
      "compliance_status": "pending",
      "case_context": "Potential conflicts from prior City Engineer role",
      "source_text": "disclosure by Engineer D and acceptance by the City may cure the matter",
      "is_existing_class": true,
      "confidence": 0.9
    },
    {
      "identifier": "FirmAER_ProperInducement",
      "obligation_class": "Professional Obligation",
      "obligated_party": "Principals of Firm AE&R",
      "obligation_statement": "Must not induce Engineer D's employment for improper influence on City contracts",
      "derived_from": "NSPE Code Section II.5.b",
      "enforcement_context": "Professional ethics review",
      "temporal_scope": "During recruitment and employment of Engineer D",
      "compliance_status": "met",
      "case_context": "Firm AE&R hiring former City Engineer",
      "source_text": "Code Section II.5.b would prohibit the principals of Firm AE&R from inducing Engineer A to join the firm",
      "is_existing_class": true,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerD_VoluntaryEmbargo",
      "obligation_class": "Post-Employment Restriction Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Should voluntarily abstain from City procurement matters for one year",
      "derived_from": "Spirit of NSPE Code and BER precedent",
      "enforcement_context": "Voluntary compliance and professional honor",
      "temporal_scope": "One year after leaving City position",
      "compliance_status": "unclear",
      "case_context": "No legal revolving door prohibition exists",
      "source_text": "Engineer D could voluntarily abstain from participation in procurement matters before the City...for an agreed period",
      "is_existing_class": false,
      "confidence": 0.75
    },
    {
      "identifier": "EngineerD_ResponsibleCharge_Restriction",
      "obligation_class": "Responsible Charge Obligation",
      "obligated_party": "Engineer D",
      "obligation_statement": "Must not take responsible charge of City projects previously overseen as City Engineer",
      "derived_from": "NSPE Code spirit regarding objectivity",
      "enforcement_context": "Firm AE&R project assignments",
      "temporal_scope": "For duration of existing City contracts",
      "compliance_status": "pending",
      "case_context": "Projects under contract during Engineer D's City tenure",
      "source_text": "raise concerns about objectivity and fairness if Firm AE&R directly placed Engineer D in responsible charge",
      "is_existing_class": true,
      "confidence": 0.8
    }
  ]
}
```
Constraints Extraction
LLM Prompt
You are an expert in professional ethics analyzing a case for constraints (boundaries, limitations, and restrictions). Based on the literature: - Constraints are INVIOLABLE BOUNDARIES that limit acceptable actions (Dennis et al. 2016) - They differ from obligations by being restrictions rather than requirements - Constraints can be legal, physical, resource-based, or procedural - They define the space within which ethical decisions must be made Your task is to: 1. Identify NEW CONSTRAINT CLASSES not in the existing ontology 2. Extract SPECIFIC CONSTRAINT INDIVIDUALS from the case EXISTING CONSTRAINTS IN ONTOLOGY (check if your identified constraints match these before creating new classes): - Attribution Constraint: Requirements and limitations regarding the disclosure and citation of tools, methods, or sources used in professional work products - Competence Constraint: Boundaries defined by agent capabilities and technical limitations (Hallamaa & Kalliokoski 2022) - Confidentiality Constraint: Boundaries on information disclosure and privacy (Dennis et al. 2016) - Constraint: An information content entity expressing limitations or restrictions on professional actions or decisions. This is the Cs component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs). - Defeasible Constraint: Constraints that admit justified exceptions under specified conditions (Ganascia 2007) - Ethical Constraint: Professional ethical boundaries beyond legal requirements (Benzmüller et al. 2020) - Inviolable Constraint: Absolute constraints that cannot be overridden under any circumstances (Dennis et al. 2016) - Jurisdictional Constraint: Boundaries of authority and geographical or organizational scope (Dennis et al. 2016) - Legal Constraint: Constraints arising from legal requirements and statutes that establish inviolable boundaries (Kroll 2020, Stenseke 2024) - Priority Constraint: Constraints establishing precedence when multiple requirements conflict (Scheutz & Malle 2014) - Procedural Constraint: Requirements for following specific processes or protocols (Furbach et al. 2014) - Regulatory Constraint: Constraints from regulatory bodies and professional standards organizations (Taddeo et al. 2024) - Resource Constraint: Limitations on available time, budget, materials, or human resources (Ganascia 2007) - Safety Constraint: Constraints ensuring safety requirements are met (Arkin 2008) - Technology Substitution Constraint: Boundaries preventing technology from replacing professional judgment and human oversight in critical decision-making Analyze this discussion section: This case has to do with what are commonly called “revolving door” constraints governing the ethics of high-level government employees (federal, state, municipal) who leave public employment to enter the private sector. Such persons are – or can be – viewed as being in a position to unfairly profit from or otherwise trade upon the contacts, associations, influence, and special knowledge they acquired during their tenure as public servants. Practices of concern include but are not limited to involvement in the solicitation of continuing contracts, assuming the management and oversight for active projects, participating in the solicitation of new work for which the employee had been directly involved as a public-sector employee, and related professional matters. We start the discussion by reviewing the first case the Board of Ethical Review published, BER Case 58-1 . In that case a foreign government agency invited proposals to complete a design and supervise construction of a hydroelectric project. The basic plans for the project were in place and were prepared by a team of engineers working for a US government agency. Several of those engineers negotiated with at least two AE firms with the intent of taking part in the design and supervision of the work. The engineers formed a corporation to be part of a joint venture to design the hydroelectric project. At about the time the various contract negotiations were wrapping up, the engineers resigned from their US government positions and entered into a contract with the foreign government to work on the hydroelectric project. The Board was asked, “Was it a violation of the Canons of Ethics or the Rules of Professional Conduct for employees of the US Government, while still employed, to organize a new private company and negotiate a contract to take part in the design of a project for which they had prepared preliminary plans as employees of the Government?” In Case 58-1 , the Board began by noting “there can be no question of the basic right of an American citizen to resign from one position and accept another or initiate a business of his own.” The Board noted that they were not able to call witnesses to understand the exact circumstances of the case, but they pointed out, “It seems axiomatic that the personal and intimate knowledge of the project which the employees gained from their work on the preliminary design of the project and the acquaintance they made with the representatives of the owner of the project gave them many distinct advantages over any other firms who may have considered the offering of their services to the owner. The crucial question is, therefore, ‘Were these advantages used unfairly?’” Said the Board: …They (the advantages) might have been used and in any case the possibility of the existence of one or more of these facets raises a cloud of doubt as to the purity of the enterprise. It becomes a matter which might be considered under Section 19 of the Canons, which states: "The engineer will endeavor to protect the engineering profession collectively and individually from misrepresentation and misunderstanding." The Board concluded, “The… [engineers] in question have violated the spirit of the Canons and Rules, although the evidence does not prove them to be in violation of specific paragraph (sic), as now worded.” They went on to state, “it tends to bring dishonor to the profession of engineering if the [engineer] devotes his energies, while still employed, to promote his future practice or employment on the basis of having inside information which would lead to greater profits, if he can secure a position or enter into contract to work on further details of the identical project.” Case 58-1 included a dissent: The guiding principle behind the phrasing of the "Rules" is that the words mean exactly what they say-that there is no concealed, hidden, or obscure "intent." In my opinion the "Conclusion" of the report should be, "The Board believes that the [engineers] in question have not violated the Canons or Rules as they currently exist." This could be followed by a "Recommendation" that the Ethical Practices Committee be instructed to consider the desirability of adding another Rule… to make unethical a situation similar to the one considered, as well as for a situation where the employees were other than Government. Since that first case, the Board has considered multiple situations where a professional engineer in private practice or an engineering firm also serves as a city, town, or county engineer. While such cases are more directly concerned with dual employment, the situations are pertinent relative to many ethical considerations of transitional employment. Three cases are illustrative. In BER Case 63-5 , a small community retained a professional engineer, Engineer B, on a part-time basis to serve as city engineer. Engineer B was engaged in full-time private practice and treated his part-time service to the community as a public service. In addition to general advisory services to the city, Engineer B was selected by the city council for the preparation of plans and specifications for a city project. In such cases, Engineer B was compensated on a normal professional fee basis over and above his monthly retainer. The Board ruled that it is ethical for a professional engineer retained by a community on a part-time basis as a city engineer to prepare plans and specifications for a project for the same community, but in so acting the engineer must be scrupulously careful that his advice is not influenced by his secondary interest as the engineer likely to be retained for the design of the project. The Board noted that “it is axiomatic that a professional person may not take action or make decisions which would divide his loyalties or interests from those of his employer or client.” Among the issues the Board considered in BER Case No. 63-5 was the practical question of the engineer passing on the adequacy of his own plans in his capacity as city engineer. The Board noted that there is no requirement in the NSPE Code that an engineer’s plans for a client must be reviewed by an engineer employed or retained by the client. The Board noted that the client had the right of review by its own engineer, but it may waive its right, as it did in Case 63-5 , and under those circumstances, the engineer was acting in a dual capacity but not a divided one. In BER Case 74-2 , the Board considered a case involving a state law that required that every municipality have a municipal engineer whose duties and compensation were to be fixed by a municipal ordinance. But many of the smaller communities in the state did not have and could not afford full-time municipal engineers or supporting staff personnel for a full-time office. In such instances the smaller communities retained the services of a consulting firm in private practice and appointed a principal of the firm as the municipal engineer. Such a municipal engineer was paid either on a cost-plus basis or a flat monthly retainer—usually a relatively low amount. The municipal engineer’s firm was thereafter usually retained for engineering services for capital improvement projects needed by the municipality. In deciding that it was ethical for the engineer – who was not a municipal employee, but whose compensation was paid on a retainer or fee basis -- to serve as municipal engineer and participate in a consulting firm providing engineering services to the same municipality under the stated conditions, the Board determined that the public interest was best served by providing the small municipalities with the most competent engineering services which they can acquire. It was assumed by the Board that the state law was intended to achieve this end. More recently, BER Case 11-12 considered the situation of Engineer A, who served as the part-time town engineer for Smithtown and also had a consulting engineering practice. With Engineer A's advice and concurrence, Smithtown selected Engineer B to provide design services for a local road project. Following the selection and after Engineer B began to perform preliminary design services, Engineer A, in his role as town engineer, reviewed Engineer B’s preliminary work and became convinced Engineer B’s performance on the contract did not meet the standards as outlined in Engineer B’s contract. Following the termination of Engineer B under the terms and conditions of his contract with the town, Engineer A offered, and Smithtown agreed, that Engineer A's firm should perform the design work for the local road project for Smithtown. In determining it would not be ethical for Engineer A to offer and agree to perform the work for Smithtown, the Board observed that serious ethical constraints would preclude the selection of Engineer A by the town to perform the road design work. Because Engineer A was an officer or principal of his engineering firm, according to NSPE Code of Ethics Section II.4.e, Engineer A was not eligible to provide engineering services to Smithtown for the local road project. This conclusion is based upon the language of Code Section II.4.e and is irrespective of whether the town’s procurement laws were scrupulously followed. The Board further opined that the disclosure of any further circumstances would not be sufficient to avoid a conflict of interest or the appearance of a conflict of interest. Conflicts of interest feature prominently in transitional employment situations. BER Case 14-8 for example – which is in many ways the converse of the situation Engineer D faces in the present case – describes how Engineer A worked for a private company and stamped a water rights analysis for a client, and that analysis was working its way through the court system. During the legal review, Engineer A resigned from their firm and went to work for the State – the State being an objector to the analysis Engineer A prepared. The Board was asked to weigh in on Engineer A’s ethical obligations. The case discussion noted Engineer A’s ongoing duty both to their former employer and the private client. Engineer A could not have disclosed, participated in or represented the State's interest in connection with this proceeding unless Engineer A first obtained the permission/consent of Engineer A's former private firm employer and also the client. The BER discussion and conclusion recommended: Engineer A should be assigned other duties by the State, remain isolated from the State's water rights case involving Engineer A's former employer and its client—and the State should recognize and respect Engineer A's ethical obligations in this matter. Any involvement by Engineer A in the State's case could potentially compromise the interests of all parties—the former employer, the private client, and the State—as Engineer A's dual role and his professional opinion/judgment—as an employee of the private firm and now as a State employee—could be called into question—by one of the parties, the public, or the media. As a final example, BER Case 15-8 offers direct guidance on the ethics of transitional employment. Engineer P is a “top” official in State X highway department who would like to leave and become an executive in an architecture/engineering (AE) firm. Engineer P requested permission from the State X highway department to accept the new position; however, the State X highway department refused to grant permission, noting that, in accepting the position, Engineer P would be in violation of the state law that requires top State X highway officials to wait a year after leaving the highway department before accepting positions with firms with which the department does business. In response, Engineer P left the State X highway department and joined the AE firm not as an “employee” but as an “independent contractor.”  The board was asked if it was ethical for Engineer P to leave the State X highway department and join the AE firm in this way. The BER pointed out a potential conflict of interest existed between Engineer P’s obligations to his former employer—the State X highway department—and the party with which Engineer P was now contracting, the AE firm. They also noted that while disclosure of a desired new employment relationship had been made, disclosure alone was not sufficient. The BER stated, “the agreement for a one-year hiatus after leaving government service before accepting related employment is not supported by disguising the employment as ‘independent contracting’.” The BER concluded: The fact that Engineer P proceeded to join the architecture/engineering firm as an “independent contractor” instead of as an “executive employee” was an apparent way of circumventing state law. The Board of Ethical Review believes that Engineer P’s actions were unethical. We now turn to the present case, the situation of Engineer D who resigned the position as City Engineer in a mid-sized municipality, and shortly thereafter accepted the position of “associate” at Firm AE&R, a consultant with whom Engineer D would have regularly interacted during tenure with the City. The facts of the case specifically note Engineer A's employment contract with the City did not include a revolving door prohibition such as Engineer P faced in Case 15-8 . Thus, on the face of the matter, it would seem there is no legal barrier to Engineer A accepting employment with Firm AE&R. Case 58-1 and other cases since then support the engineer’s right of employment. But that does not mean such employment would exempt Engineer A from the ethical requirements and obligations of the NSPE Code of Ethics. What are some of these ethical requirements and obligations? Among the most obvious are Code Sections II.4.c and III.6 which prohibit engineers from advancing their professional careers by any improper or questionable method. Likewise, Code Section II.5.b would prohibit the principals of Firm AE&R from inducing Engineer A to join the firm as a way of influencing the awarding of city contracts for improper reasons not related to Engineer A’s qualifications and experience.  The facts of the case are silent on these matters, and the Board takes this to mean no violation occurred. Some might assert that because Engineer A's employment contract with the City did not include a revolving door prohibition, nothing more needs to be said. But the BER does not hold this perspective. Case 58-1 speaks of the “purity of the enterprise”, of avoiding “dishonor to the profession,” and how engineers must consider not only the letter but the spirit of the ethics code. Consistent with Fundamental Canon 1.6, such values form the context of an engineer’s professional relationships and apply in this case. Though revolving door prohibitions are not specifically in effect, the spirit of such provisions can guide multiple aspects of Engineer D’s employment activities. For example, the BER believes Engineer D’s prior responsibilities with the City for projects currently under contract by D’s new employer would raise concerns about objectivity and fairness if Firm AE&R directly placed Engineer D in responsible charge of those projects as a consultant. In this situation, disclosure by Engineer D and acceptance by the City may cure the matter. Alternatively, Engineer D can follow the recommendations in Case 14-8 and remain isolated from former projects until those contracts lapse. Confidentiality is another ethical obligation that continues after one severs employment (Code Section III.4). Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties or employment with the City. That is, Engineer D should not be allowed to breach confidentiality for personal gain. Third, as a public official who transitions to private practice, Engineer D should not unfairly profit from or otherwise trade upon the contacts, associations, and special knowledge she acquired during tenure as a public servant. In particular this would apply to direct procurement activities.  But does this mean Engineer D is automatically precluded from using D’s professional knowledge and expertise to serve the City in a consulting role? The Board sees room for accommodation. Past BER cases affirm that full disclosure by the engineer (i.e., Engineer D) coupled with careful and thoughtful acceptance by the client (i.e., the City) can be sufficient to cure “known or potential conflicts of interest that could influence or appear to influence the engineer’s judgment or the quality of their services” (II.4.a). In evaluating disclosed information, important factors include avoiding divided interests by the engineer, advancing the best interests of the client, and complying with procurement requirements. While approval through disclosure is not automatic, ample precedent has shown that within many contexts the parties directly involved are in the best position to serve the public interest by providing the most competent engineering services available. What about marginal situations, or conditions where a known or potential conflict would be prohibitive or too complex to set aside? Here, as was done in Case 15-8 , an embargo or "cooling off" period, often one-year duration, can ameliorate such concerns. That is, as appropriate and prudent, Engineer D could voluntarily abstain from participation in procurement matters before the City, or before any other agency for which the City is or was the approving authority, for an agreed period of say, one year after she leaves the public job. These transitional employment practices, in the spirit of NSPE Code of Ethics, are intended to help Engineer D engage only in conduct that is honorable, responsible, ethical, and lawful so as to enhance the honor, reputation, and usefulness of the engineering profession. Extract constraints following this JSON structure: { "new_constraint_classes": [ { "label": "Clear, specific constraint class name", "definition": "What this type of constraint limits or restricts", "constraint_type": "legal|physical|resource|temporal|procedural", "flexibility": "hard|soft|negotiable", "violation_impact": "What happens if this constraint is violated", "mitigation_possible": "Whether and how this constraint can be mitigated", "examples_from_case": ["Example 1 from the case", "Example 2"], "source_text": "EXACT text snippet from case where this constraint is identified (max 200 characters)", "confidence": 0.0-1.0, "reasoning": "Why this is a new class not in existing ontology" } ], "constraint_individuals": [ { "identifier": "Unique name for this specific constraint instance", "constraint_class": "Name of the constraint class (new or existing)", "constrained_entity": "What or who is constrained (e.g., 'Engineer L', 'Project')", "constraint_statement": "The specific limitation (e.g., 'Cannot exceed budget of $X')", "source": "Origin of constraint (e.g., 'Client budget', 'Environmental law')", "enforcement_mechanism": "How this constraint is enforced", "temporal_scope": "When this constraint applies", "severity": "critical|major|minor", "case_context": "How this constraint manifests in the specific case", "source_text": "EXACT text snippet from case where this constraint is mentioned (max 200 characters)", "is_existing_class": true/false, "confidence": 0.0-1.0 } ] } Focus on: 1. NEW constraint types that represent novel limitations or boundaries 2. Specific constraint instances showing how limitations apply in this case 3. The difference between constraints (boundaries) and obligations (duties) 4. Impact and severity of constraints on decision-making Return ONLY the JSON structure, no additional text.
Saved: 2025-12-20 13:56
LLM Response
```json
{
  "new_constraint_classes": [
    {
      "label": "Revolving Door Constraint",
      "definition": "Temporal and functional limitations on former government employees accepting private sector positions with entities they previously regulated or contracted with",
      "constraint_type": "temporal",
      "flexibility": "negotiable",
      "violation_impact": "Legal penalties, ethics violations, appearance of impropriety, damage to professional reputation",
      "mitigation_possible": "Through cooling-off periods, disclosure, recusal from specific projects, or restructuring employment terms",
      "examples_from_case": ["State law requiring one-year waiting period", "Engineer P's attempt to circumvent as 'independent contractor'"],
      "source_text": "state law that requires top State X highway officials to wait a year after leaving the highway department before accepting positions",
      "confidence": 0.95,
      "reasoning": "This represents a specific temporal boundary on post-government employment not captured in existing constraint classes"
    },
    {
      "label": "Unfair Advantage Constraint",
      "definition": "Boundaries preventing the exploitation of insider knowledge, contacts, or influence gained from previous positions for improper competitive advantage",
      "constraint_type": "procedural",
      "flexibility": "soft",
      "violation_impact": "Ethics violations, undermining fair competition, loss of public trust",
      "mitigation_possible": "Through disclosure, abstention from specific activities, or limiting scope of new role",
      "examples_from_case": ["Engineers using inside information on hydroelectric project", "Engineer D's special knowledge from City position"],
      "source_text": "personal and intimate knowledge of the project which the employees gained from their work on the preliminary design",
      "confidence": 0.90,
      "reasoning": "Distinct from confidentiality constraints as it addresses competitive fairness rather than information protection"
    },
    {
      "label": "Dual Role Constraint",
      "definition": "Limitations on simultaneously holding or sequentially transitioning between positions that create divided loyalties or conflicting interests",
      "constraint_type": "procedural",
      "flexibility": "hard",
      "violation_impact": "Conflict of interest, compromised judgment, inability to serve either party effectively",
      "mitigation_possible": "Through clear separation of duties, disclosure, or avoiding one of the roles",
      "examples_from_case": ["Engineer B as both city engineer and consultant", "Engineer A reviewing own work"],
      "source_text": "a professional person may not take action or make decisions which would divide his loyalties or interests",
      "confidence": 0.85,
      "reasoning": "Goes beyond general ethical constraints to specifically address role-based limitations"
    }
  ],
  "constraint_individuals": [
    {
      "identifier": "EngineerD_CityProjectParticipation",
      "constraint_class": "Revolving Door Constraint",
      "constrained_entity": "Engineer D",
      "constraint_statement": "Cannot take responsible charge of City projects previously overseen without disclosure and acceptance",
      "source": "Professional ethics standards and spirit of revolving door provisions",
      "enforcement_mechanism": "Professional ethics review, potential legal action",
      "temporal_scope": "After leaving City employment",
      "severity": "major",
      "case_context": "Engineer D joining Firm AE&R after resigning as City Engineer",
      "source_text": "Engineer D's prior responsibilities with the City for projects currently under contract by D's new employer would raise concerns",
      "is_existing_class": false,
      "confidence": 0.90
    },
    {
      "identifier": "EngineerD_CityConfidentialInfo",
      "constraint_class": "Confidentiality Constraint",
      "constrained_entity": "Engineer D",
      "constraint_statement": "Cannot use or disclose confidential information acquired during City employment",
      "source": "NSPE Code Section III.4",
      "enforcement_mechanism": "Professional sanctions, legal action for breach",
      "temporal_scope": "Perpetual after employment ends",
      "severity": "critical",
      "case_context": "Engineer D's transition from City to private consulting",
      "source_text": "Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerP_StateEmploymentWaiting",
      "constraint_class": "Legal Constraint",
      "constrained_entity": "Engineer P",
      "constraint_statement": "Must wait one year before accepting positions with firms doing business with State X highway department",
      "source": "State X law",
      "enforcement_mechanism": "Legal penalties, employment prohibition",
      "temporal_scope": "One year after leaving state employment",
      "severity": "critical",
      "case_context": "Engineer P attempting to circumvent by becoming 'independent contractor'",
      "source_text": "state law that requires top State X highway officials to wait a year after leaving the highway department",
      "is_existing_class": true,
      "confidence": 1.0
    },
    {
      "identifier": "USEngineers_HydroProjectAdvantage",
      "constraint_class": "Unfair Advantage Constraint",
      "constrained_entity": "US Government engineers",
      "constraint_statement": "Cannot use insider knowledge and contacts from preliminary design work to secure follow-on contracts",
      "source": "NSPE Canons of Ethics",
      "enforcement_mechanism": "Professional ethics review",
      "temporal_scope": "While still employed and after resignation",
      "severity": "major",
      "case_context": "Engineers negotiating contracts while still government employees",
      "source_text": "intimate knowledge of the project which the employees gained from their work on the preliminary design",
      "is_existing_class": false,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerA_DualRepresentation",
      "constraint_class": "Dual Role Constraint",
      "constrained_entity": "Engineer A (Case 14-8)",
      "constraint_statement": "Cannot represent State's interests against analysis previously prepared for private client",
      "source": "Professional ethics obligations",
      "enforcement_mechanism": "Recusal, reassignment of duties",
      "temporal_scope": "During State employment while case is pending",
      "severity": "critical",
      "case_context": "Engineer A moving from private firm to State during ongoing litigation",
      "source_text": "Engineer A should be assigned other duties by the State, remain isolated from the State's water rights case",
      "is_existing_class": false,
      "confidence": 0.90
    },
    {
      "identifier": "EngineerD_ProcurementAbstention",
      "constraint_class": "Procedural Constraint",
      "constrained_entity": "Engineer D",
      "constraint_statement": "Should voluntarily abstain from City procurement matters for cooling-off period",
      "source": "Professional ethics best practices",
      "enforcement_mechanism": "Voluntary compliance, professional monitoring",
      "temporal_scope": "One year suggested after leaving City position",
      "severity": "major",
      "case_context": "Engineer D's transition to private consulting firm",
      "source_text": "Engineer D could voluntarily abstain from participation in procurement matters before the City",
      "is_existing_class": true,
      "confidence": 0.80
    }
  ]
}
```
Capabilities Extraction
LLM Prompt
You are an expert in professional ethics analyzing a case for capabilities (competencies and skills required for professional practice). Based on the literature: - Capabilities are COMPETENCIES that enable norm compliance (Hallamaa & Kalliokoski 2022) - They represent the skills needed to fulfill professional obligations (Dennis et al. 2016) - Capabilities include technical, ethical, communicative, and analytical competencies - They constitute "norm competence" - the ability to act ethically (Kong et al. 2020) Your task is to: 1. Identify NEW CAPABILITY CLASSES not in the existing ontology 2. Extract SPECIFIC CAPABILITY INDIVIDUALS from the case EXISTING CAPABILITIES IN ONTOLOGY (check if your identified capabilities match these before creating new classes): - AI Tool Evaluation Capability: The competency to assess, validate, and appropriately use AI-generated content in professional work - Capability: A realizable entity that can be realized by specific types of actions or processes in professional contexts. This is the Ca component of the formal specification D=(R,P,O,S,Rs,A,E,Ca,Cs). - Capability Type: Meta-class for specific capability types recognized by the ProEthica system - Data Privacy Protection Capability: The competency to safeguard confidential client information when using digital tools and platforms - Justification Capability: Capability to trace reasoning paths connecting decisions to authoritative sources (McLaren 2003, Anderson & Anderson 2018) - Regulatory Compliance Capability: The competency to ensure designs and documents meet local regulations and safety standards - Responsible Charge Capability: The competency to maintain active engagement and supervisory control from conception to completion of engineering work - Technical Capability: A specialized technical skill or competency in a professional domain - Technical Writing Capability: The competency to produce clear, accurate, and professional technical documentation and reports - Technology Integration Capability: The competency to appropriately integrate new technologies while maintaining professional judgment Analyze this discussion section: This case has to do with what are commonly called “revolving door” constraints governing the ethics of high-level government employees (federal, state, municipal) who leave public employment to enter the private sector. Such persons are – or can be – viewed as being in a position to unfairly profit from or otherwise trade upon the contacts, associations, influence, and special knowledge they acquired during their tenure as public servants. Practices of concern include but are not limited to involvement in the solicitation of continuing contracts, assuming the management and oversight for active projects, participating in the solicitation of new work for which the employee had been directly involved as a public-sector employee, and related professional matters. We start the discussion by reviewing the first case the Board of Ethical Review published, BER Case 58-1 . In that case a foreign government agency invited proposals to complete a design and supervise construction of a hydroelectric project. The basic plans for the project were in place and were prepared by a team of engineers working for a US government agency. Several of those engineers negotiated with at least two AE firms with the intent of taking part in the design and supervision of the work. The engineers formed a corporation to be part of a joint venture to design the hydroelectric project. At about the time the various contract negotiations were wrapping up, the engineers resigned from their US government positions and entered into a contract with the foreign government to work on the hydroelectric project. The Board was asked, “Was it a violation of the Canons of Ethics or the Rules of Professional Conduct for employees of the US Government, while still employed, to organize a new private company and negotiate a contract to take part in the design of a project for which they had prepared preliminary plans as employees of the Government?” In Case 58-1 , the Board began by noting “there can be no question of the basic right of an American citizen to resign from one position and accept another or initiate a business of his own.” The Board noted that they were not able to call witnesses to understand the exact circumstances of the case, but they pointed out, “It seems axiomatic that the personal and intimate knowledge of the project which the employees gained from their work on the preliminary design of the project and the acquaintance they made with the representatives of the owner of the project gave them many distinct advantages over any other firms who may have considered the offering of their services to the owner. The crucial question is, therefore, ‘Were these advantages used unfairly?’” Said the Board: …They (the advantages) might have been used and in any case the possibility of the existence of one or more of these facets raises a cloud of doubt as to the purity of the enterprise. It becomes a matter which might be considered under Section 19 of the Canons, which states: "The engineer will endeavor to protect the engineering profession collectively and individually from misrepresentation and misunderstanding." The Board concluded, “The… [engineers] in question have violated the spirit of the Canons and Rules, although the evidence does not prove them to be in violation of specific paragraph (sic), as now worded.” They went on to state, “it tends to bring dishonor to the profession of engineering if the [engineer] devotes his energies, while still employed, to promote his future practice or employment on the basis of having inside information which would lead to greater profits, if he can secure a position or enter into contract to work on further details of the identical project.” Case 58-1 included a dissent: The guiding principle behind the phrasing of the "Rules" is that the words mean exactly what they say-that there is no concealed, hidden, or obscure "intent." In my opinion the "Conclusion" of the report should be, "The Board believes that the [engineers] in question have not violated the Canons or Rules as they currently exist." This could be followed by a "Recommendation" that the Ethical Practices Committee be instructed to consider the desirability of adding another Rule… to make unethical a situation similar to the one considered, as well as for a situation where the employees were other than Government. Since that first case, the Board has considered multiple situations where a professional engineer in private practice or an engineering firm also serves as a city, town, or county engineer. While such cases are more directly concerned with dual employment, the situations are pertinent relative to many ethical considerations of transitional employment. Three cases are illustrative. In BER Case 63-5 , a small community retained a professional engineer, Engineer B, on a part-time basis to serve as city engineer. Engineer B was engaged in full-time private practice and treated his part-time service to the community as a public service. In addition to general advisory services to the city, Engineer B was selected by the city council for the preparation of plans and specifications for a city project. In such cases, Engineer B was compensated on a normal professional fee basis over and above his monthly retainer. The Board ruled that it is ethical for a professional engineer retained by a community on a part-time basis as a city engineer to prepare plans and specifications for a project for the same community, but in so acting the engineer must be scrupulously careful that his advice is not influenced by his secondary interest as the engineer likely to be retained for the design of the project. The Board noted that “it is axiomatic that a professional person may not take action or make decisions which would divide his loyalties or interests from those of his employer or client.” Among the issues the Board considered in BER Case No. 63-5 was the practical question of the engineer passing on the adequacy of his own plans in his capacity as city engineer. The Board noted that there is no requirement in the NSPE Code that an engineer’s plans for a client must be reviewed by an engineer employed or retained by the client. The Board noted that the client had the right of review by its own engineer, but it may waive its right, as it did in Case 63-5 , and under those circumstances, the engineer was acting in a dual capacity but not a divided one. In BER Case 74-2 , the Board considered a case involving a state law that required that every municipality have a municipal engineer whose duties and compensation were to be fixed by a municipal ordinance. But many of the smaller communities in the state did not have and could not afford full-time municipal engineers or supporting staff personnel for a full-time office. In such instances the smaller communities retained the services of a consulting firm in private practice and appointed a principal of the firm as the municipal engineer. Such a municipal engineer was paid either on a cost-plus basis or a flat monthly retainer—usually a relatively low amount. The municipal engineer’s firm was thereafter usually retained for engineering services for capital improvement projects needed by the municipality. In deciding that it was ethical for the engineer – who was not a municipal employee, but whose compensation was paid on a retainer or fee basis -- to serve as municipal engineer and participate in a consulting firm providing engineering services to the same municipality under the stated conditions, the Board determined that the public interest was best served by providing the small municipalities with the most competent engineering services which they can acquire. It was assumed by the Board that the state law was intended to achieve this end. More recently, BER Case 11-12 considered the situation of Engineer A, who served as the part-time town engineer for Smithtown and also had a consulting engineering practice. With Engineer A's advice and concurrence, Smithtown selected Engineer B to provide design services for a local road project. Following the selection and after Engineer B began to perform preliminary design services, Engineer A, in his role as town engineer, reviewed Engineer B’s preliminary work and became convinced Engineer B’s performance on the contract did not meet the standards as outlined in Engineer B’s contract. Following the termination of Engineer B under the terms and conditions of his contract with the town, Engineer A offered, and Smithtown agreed, that Engineer A's firm should perform the design work for the local road project for Smithtown. In determining it would not be ethical for Engineer A to offer and agree to perform the work for Smithtown, the Board observed that serious ethical constraints would preclude the selection of Engineer A by the town to perform the road design work. Because Engineer A was an officer or principal of his engineering firm, according to NSPE Code of Ethics Section II.4.e, Engineer A was not eligible to provide engineering services to Smithtown for the local road project. This conclusion is based upon the language of Code Section II.4.e and is irrespective of whether the town’s procurement laws were scrupulously followed. The Board further opined that the disclosure of any further circumstances would not be sufficient to avoid a conflict of interest or the appearance of a conflict of interest. Conflicts of interest feature prominently in transitional employment situations. BER Case 14-8 for example – which is in many ways the converse of the situation Engineer D faces in the present case – describes how Engineer A worked for a private company and stamped a water rights analysis for a client, and that analysis was working its way through the court system. During the legal review, Engineer A resigned from their firm and went to work for the State – the State being an objector to the analysis Engineer A prepared. The Board was asked to weigh in on Engineer A’s ethical obligations. The case discussion noted Engineer A’s ongoing duty both to their former employer and the private client. Engineer A could not have disclosed, participated in or represented the State's interest in connection with this proceeding unless Engineer A first obtained the permission/consent of Engineer A's former private firm employer and also the client. The BER discussion and conclusion recommended: Engineer A should be assigned other duties by the State, remain isolated from the State's water rights case involving Engineer A's former employer and its client—and the State should recognize and respect Engineer A's ethical obligations in this matter. Any involvement by Engineer A in the State's case could potentially compromise the interests of all parties—the former employer, the private client, and the State—as Engineer A's dual role and his professional opinion/judgment—as an employee of the private firm and now as a State employee—could be called into question—by one of the parties, the public, or the media. As a final example, BER Case 15-8 offers direct guidance on the ethics of transitional employment. Engineer P is a “top” official in State X highway department who would like to leave and become an executive in an architecture/engineering (AE) firm. Engineer P requested permission from the State X highway department to accept the new position; however, the State X highway department refused to grant permission, noting that, in accepting the position, Engineer P would be in violation of the state law that requires top State X highway officials to wait a year after leaving the highway department before accepting positions with firms with which the department does business. In response, Engineer P left the State X highway department and joined the AE firm not as an “employee” but as an “independent contractor.”  The board was asked if it was ethical for Engineer P to leave the State X highway department and join the AE firm in this way. The BER pointed out a potential conflict of interest existed between Engineer P’s obligations to his former employer—the State X highway department—and the party with which Engineer P was now contracting, the AE firm. They also noted that while disclosure of a desired new employment relationship had been made, disclosure alone was not sufficient. The BER stated, “the agreement for a one-year hiatus after leaving government service before accepting related employment is not supported by disguising the employment as ‘independent contracting’.” The BER concluded: The fact that Engineer P proceeded to join the architecture/engineering firm as an “independent contractor” instead of as an “executive employee” was an apparent way of circumventing state law. The Board of Ethical Review believes that Engineer P’s actions were unethical. We now turn to the present case, the situation of Engineer D who resigned the position as City Engineer in a mid-sized municipality, and shortly thereafter accepted the position of “associate” at Firm AE&R, a consultant with whom Engineer D would have regularly interacted during tenure with the City. The facts of the case specifically note Engineer A's employment contract with the City did not include a revolving door prohibition such as Engineer P faced in Case 15-8 . Thus, on the face of the matter, it would seem there is no legal barrier to Engineer A accepting employment with Firm AE&R. Case 58-1 and other cases since then support the engineer’s right of employment. But that does not mean such employment would exempt Engineer A from the ethical requirements and obligations of the NSPE Code of Ethics. What are some of these ethical requirements and obligations? Among the most obvious are Code Sections II.4.c and III.6 which prohibit engineers from advancing their professional careers by any improper or questionable method. Likewise, Code Section II.5.b would prohibit the principals of Firm AE&R from inducing Engineer A to join the firm as a way of influencing the awarding of city contracts for improper reasons not related to Engineer A’s qualifications and experience.  The facts of the case are silent on these matters, and the Board takes this to mean no violation occurred. Some might assert that because Engineer A's employment contract with the City did not include a revolving door prohibition, nothing more needs to be said. But the BER does not hold this perspective. Case 58-1 speaks of the “purity of the enterprise”, of avoiding “dishonor to the profession,” and how engineers must consider not only the letter but the spirit of the ethics code. Consistent with Fundamental Canon 1.6, such values form the context of an engineer’s professional relationships and apply in this case. Though revolving door prohibitions are not specifically in effect, the spirit of such provisions can guide multiple aspects of Engineer D’s employment activities. For example, the BER believes Engineer D’s prior responsibilities with the City for projects currently under contract by D’s new employer would raise concerns about objectivity and fairness if Firm AE&R directly placed Engineer D in responsible charge of those projects as a consultant. In this situation, disclosure by Engineer D and acceptance by the City may cure the matter. Alternatively, Engineer D can follow the recommendations in Case 14-8 and remain isolated from former projects until those contracts lapse. Confidentiality is another ethical obligation that continues after one severs employment (Code Section III.4). Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties or employment with the City. That is, Engineer D should not be allowed to breach confidentiality for personal gain. Third, as a public official who transitions to private practice, Engineer D should not unfairly profit from or otherwise trade upon the contacts, associations, and special knowledge she acquired during tenure as a public servant. In particular this would apply to direct procurement activities.  But does this mean Engineer D is automatically precluded from using D’s professional knowledge and expertise to serve the City in a consulting role? The Board sees room for accommodation. Past BER cases affirm that full disclosure by the engineer (i.e., Engineer D) coupled with careful and thoughtful acceptance by the client (i.e., the City) can be sufficient to cure “known or potential conflicts of interest that could influence or appear to influence the engineer’s judgment or the quality of their services” (II.4.a). In evaluating disclosed information, important factors include avoiding divided interests by the engineer, advancing the best interests of the client, and complying with procurement requirements. While approval through disclosure is not automatic, ample precedent has shown that within many contexts the parties directly involved are in the best position to serve the public interest by providing the most competent engineering services available. What about marginal situations, or conditions where a known or potential conflict would be prohibitive or too complex to set aside? Here, as was done in Case 15-8 , an embargo or "cooling off" period, often one-year duration, can ameliorate such concerns. That is, as appropriate and prudent, Engineer D could voluntarily abstain from participation in procurement matters before the City, or before any other agency for which the City is or was the approving authority, for an agreed period of say, one year after she leaves the public job. These transitional employment practices, in the spirit of NSPE Code of Ethics, are intended to help Engineer D engage only in conduct that is honorable, responsible, ethical, and lawful so as to enhance the honor, reputation, and usefulness of the engineering profession. Extract capabilities following this JSON structure: { "new_capability_classes": [ { "label": "Clear, specific capability class name", "definition": "What competency or skill this capability represents", "capability_type": "technical|ethical|communicative|analytical", "norm_competence_related": "Which professional obligations this capability enables", "skill_level": "basic|intermediate|advanced|expert", "acquisition_method": "How this capability is typically acquired (education, training, experience)", "examples_from_case": ["Example 1 from the case", "Example 2"], "source_text": "EXACT text snippet from case where this capability is identified (max 200 characters)", "confidence": 0.0-1.0, "reasoning": "Why this is a new class not in existing ontology" } ], "capability_individuals": [ { "identifier": "Unique name for this specific capability instance", "capability_class": "Name of the capability class (new or existing)", "possessed_by": "Who has this capability (e.g., 'Engineer L', 'All Licensed PEs')", "capability_statement": "The specific competency (e.g., 'Design stormwater systems')", "demonstrated_through": "How shown in the case (e.g., 'Years of experience', 'Professional license')", "proficiency_level": "basic|intermediate|advanced|expert", "enables_obligations": "Which obligations this capability enables", "temporal_aspect": "When this capability is relevant", "case_context": "How this capability manifests in the specific case", "source_text": "EXACT text snippet from case where this capability is mentioned (max 200 characters)", "is_existing_class": true/false, "confidence": 0.0-1.0 } ] } Focus on: 1. NEW capability types that represent novel competencies 2. Specific capability instances showing professional competencies in this case 3. The relationship between capabilities and norm competence 4. How capabilities enable fulfillment of professional obligations Return ONLY the JSON structure, no additional text.
Saved: 2025-12-20 13:56
LLM Response
```json
{
  "new_capability_classes": [
    {
      "label": "Conflict of Interest Recognition Capability",
      "definition": "The competency to identify, evaluate, and manage potential or actual conflicts of interest in professional transitions and dual roles",
      "capability_type": "ethical",
      "norm_competence_related": "Enables compliance with obligations to avoid divided loyalties, maintain objectivity, and preserve professional integrity",
      "skill_level": "advanced",
      "acquisition_method": "Professional experience, ethics training, case study analysis",
      "examples_from_case": ["Recognizing when dual roles create divided interests", "Identifying when prior knowledge creates unfair advantages"],
      "source_text": "serious ethical constraints would preclude the selection of Engineer A by the town to perform the road design work",
      "confidence": 0.9,
      "reasoning": "Distinct from general ethical capabilities - specifically focuses on recognizing and managing conflicts in transitional employment contexts"
    },
    {
      "label": "Professional Transition Management Capability",
      "definition": "The competency to ethically navigate career transitions between public and private sectors while maintaining professional obligations",
      "capability_type": "ethical",
      "norm_competence_related": "Enables fulfillment of continuing duties to former employers/clients while assuming new professional roles",
      "skill_level": "expert",
      "acquisition_method": "Senior-level experience, mentorship, regulatory training",
      "examples_from_case": ["Managing revolving door constraints", "Implementing cooling-off periods"],
      "source_text": "Engineer D could voluntarily abstain from participation in procurement matters before the City...for an agreed period",
      "confidence": 0.85,
      "reasoning": "Specific to managing employment transitions ethically - not covered by existing regulatory compliance or general ethical capabilities"
    },
    {
      "label": "Disclosure and Transparency Capability",
      "definition": "The competency to properly disclose potential conflicts and obtain appropriate consent from affected parties",
      "capability_type": "communicative",
      "norm_competence_related": "Enables transparent professional relationships and informed consent processes",
      "skill_level": "intermediate",
      "acquisition_method": "Professional training, legal education, organizational policies",
      "examples_from_case": ["Full disclosure by the engineer", "Obtaining permission/consent from former employers"],
      "source_text": "full disclosure by the engineer (i.e., Engineer D) coupled with careful and thoughtful acceptance by the client",
      "confidence": 0.8,
      "reasoning": "While related to communication, this is specifically about disclosure protocols in conflict situations - distinct from general technical writing"
    }
  ],
  "capability_individuals": [
    {
      "identifier": "EngineerD_ConflictRecognition",
      "capability_class": "Conflict of Interest Recognition Capability",
      "possessed_by": "Engineer D",
      "capability_statement": "Recognize conflicts arising from transition from City Engineer to consultant role",
      "demonstrated_through": "Understanding need to avoid projects previously overseen",
      "proficiency_level": "intermediate",
      "enables_obligations": "Maintaining objectivity and avoiding divided interests per Code Section II.4",
      "temporal_aspect": "Post-employment transition period",
      "case_context": "Must recognize conflicts with projects under contract during City tenure",
      "source_text": "Engineer D's prior responsibilities with the City for projects currently under contract by D's new employer",
      "is_existing_class": false,
      "confidence": 0.85
    },
    {
      "identifier": "EngineerD_ConfidentialityProtection",
      "capability_class": "Data Privacy Protection Capability",
      "possessed_by": "Engineer D",
      "capability_statement": "Protect confidential City information after employment termination",
      "demonstrated_through": "Continuing obligation under Code Section III.4",
      "proficiency_level": "advanced",
      "enables_obligations": "Maintaining confidentiality of former employer's information",
      "temporal_aspect": "Perpetual post-employment",
      "case_context": "Must not disclose City confidential information for personal gain",
      "source_text": "Engineer D should not use or disclose confidential information acquired during the course of or by reason of duties",
      "is_existing_class": true,
      "confidence": 0.9
    },
    {
      "identifier": "EngineerA_ResponsibleCharge",
      "capability_class": "Responsible Charge Capability",
      "possessed_by": "Engineer A (Case 11-12)",
      "capability_statement": "Maintain supervisory control as town engineer while having consulting practice",
      "demonstrated_through": "Reviewing Engineer B's work and identifying deficiencies",
      "proficiency_level": "expert",
      "enables_obligations": "Ensuring quality of municipal engineering services",
      "temporal_aspect": "During dual employment",
      "case_context": "Reviewed and terminated Engineer B's contract for performance issues",
      "source_text": "Engineer A, in his role as town engineer, reviewed Engineer B's preliminary work",
      "is_existing_class": true,
      "confidence": 0.95
    },
    {
      "identifier": "EngineerP_TransitionManagement",
      "capability_class": "Professional Transition Management Capability",
      "possessed_by": "Engineer P (Case 15-8)",
      "capability_statement": "Navigate employment transition from State highway department to AE firm",
      "demonstrated_through": "Attempted disclosure and permission request",
      "proficiency_level": "basic",
      "enables_obligations": "Compliance with revolving door provisions",
      "temporal_aspect": "One-year cooling-off period",
      "case_context": "Failed to properly manage transition by circumventing state law",
      "source_text": "Engineer P requested permission from the State X highway department to accept the new position",
      "is_existing_class": false,
      "confidence": 0.8
    },
    {
      "identifier": "FirmAER_ComplianceCapability",
      "capability_class": "Regulatory Compliance Capability",
      "possessed_by": "Firm AE&R",
      "capability_statement": "Ensure hiring practices comply with ethics codes and regulations",
      "demonstrated_through": "Avoiding improper inducement under Code Section II.5.b",
      "proficiency_level": "advanced",
      "enables_obligations": "Maintaining ethical hiring practices",
      "temporal_aspect": "During recruitment and hiring",
      "case_context": "Must not induce Engineer D improperly to influence city contracts",
      "source_text": "Code Section II.5.b would prohibit the principals of Firm AE&R from inducing Engineer A to join the firm",
      "is_existing_class": true,
      "confidence": 0.85
    }
  ]
}
```