Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.
Provisions (2)
View Extraction-
Firm A Developer Client Inspection Objectivity Preservation
II.4.d. prohibits engineers in public service from participating in decisions related to their private practice, directly requiring objectivity when inspecting developer clients.
-
Firm A Faithful Agent City Client Interest Primacy
II.4.d. requires engineers in public roles to avoid conflicts that would compromise their duty to act faithfully on behalf of the governmental body they serve.
-
Firm A Public Role Marketing Exploitation Prohibition
II.4.d. prohibits using a public service position to benefit private practice, which encompasses exploiting the city engineer role as a marketing tool.
-
Firm A Dual-Service Private Developer Prohibition
II.4.d. directly prohibits participating in public decisions regarding services also provided in private practice, making simultaneous dual service to developers impermissible.
-
Firm A Developer Client Conflict Disclosure to City
II.4.d. implies that conflicts arising from private relationships must be disclosed to avoid improper participation in public decisions.
-
Firm A Competitive Fairness Non-Exploitation of City Contract
II.4.d. prohibits leveraging a public service role to benefit private engineering practice, which includes gaining unfair competitive advantage.
-
Firm A City Infrastructure Standard Primacy in Inspection
II.4.d. requires that public service decisions be made free from private practice interests, ensuring city standards govern all inspection decisions.
-
BER-62-7 County Commission Engineer Conflict of Interest Non-Engagement
II.4.d. directly applies to the precedent case where the county commission consultant was prohibited from simultaneously serving in approval and private roles.
-
BER-62-7 County Commission Engineer Divided Loyalty Recognition
II.4.d. is the basis for recognizing that divided loyalty between public commission service and private interests is ethically impermissible.
-
BER-82-4 Engineer A Multi-Role Review-Recommendation Non-Decision Boundary
II.4.d. is the provision that defines the boundary between permissible review and impermissible decision-making when serving in multiple public and private roles.
-
BER-82-4 Engineer A No Influence on Decisions Abstention Compliance
II.4.d. directly requires that engineers in public service not participate in or influence decisions related to their private practice services.
-
BER-75-7 Commission Member Engineer Abstention Compliance
II.4.d. is the provision requiring abstention from decisions involving private clients when serving in a public commission role.
-
BER-67-12 Part-Time County Engineer Private Plan Approval Recommendation Non-Issuance
II.4.d. prohibits the part-time county engineer from issuing approvals on plans submitted in a private capacity, as this constitutes participating in decisions related to private practice.
-
Firm A City-Retained Engineer Multi-Role Conflict Non-Engagement
II.4.d. directly prohibits the scenario of preparing private drawings and then reviewing those same drawings in a public capacity.
-
Firm A Multi-Hat Adequate Representation Impossibility
II.4.d. underlies the recognition that wearing multiple simultaneous hats across public and private roles creates impermissible conflicts of interest.
-
Firm A Compensating-Party Benefiting-Party Misalignment Non-Engagement
II.4.d. prohibits arrangements where private developers compensate an engineer for services that should be rendered solely in the public interest.
-
Firm A City Position Marketing Non-Exploitation
II.4.d. prohibits using a public service position to solicit or market private engineering services to prospective clients.
-
Firm A Self-Design-Review Prohibition
II.4.d. directly prohibits an engineer in public service from reviewing in that public capacity the same work they prepared in private practice.
-
Firm A Inspection Quality Non-Subordination to Developer Approval Incentive
II.4.d. requires that public inspection decisions not be influenced by private practice interests such as maintaining developer client relationships.
-
Firm A Developer Client Conflict Proactive Disclosure to City
II.4.d. implies affirmative disclosure obligations when private relationships create conflicts with public service participation.
-
Firm A Competitive Fairness Non-Exploitation of City Position
II.4.d. prohibits using a public service position to gain competitive advantages for private engineering practice.
-
Firm A Markets City Role to Developers
This provision prohibits engineers in public service from leveraging their governmental role to solicit private clients, which is exactly what marketing the city role to developers entails.
-
Engineer Serves Dual Clients Simultaneously (BER 62-7)
This provision governs engineers who simultaneously hold public roles while providing private engineering services, directly addressing dual client conflicts.
-
Municipal Engineer Accepts Private Firm Role (BER 74-2)
This provision prohibits a municipal engineer from participating in decisions related to services they provide in private practice, which applies when accepting a private firm role.
-
Commission Engineer Abstains from Conflicted Vote (BER 75-7)
This provision directly governs the requirement that engineers in public roles not participate in decisions where they have a private interest, making abstention the required conduct.
-
County Engineer Withholds Recommendation on Own Plans (BER 67-12)
This provision prohibits a public engineer from participating in decisions regarding services they themselves provide, which applies to withholding recommendations on their own plans.
-
Engineer A Accepts Multiple Public and Private Roles (BER 82-4)
This provision directly governs engineers who hold public positions while simultaneously engaging in private engineering practice for related clients.
-
City Engages Firm A
This provision applies because it governs the propriety of a firm serving in a public engineering capacity while also soliciting or providing private services.
-
Firm A Accepts Developer Clients Concurrently
This provision prohibits a firm serving as city engineer from simultaneously providing private engineering services to developers subject to city oversight.
-
Firm A Multi-Role Structural Conflict. Design, Review, and Inspection for Same Parties
Firm A's simultaneous design, review, and inspection roles for the same parties directly implicates the prohibition on participating in decisions regarding services provided by their own organization.
-
BER Case 62-7 County Commission Engineer Dual-Role Conflict
The county commission engineer passing judgment on work in which they personally participated as a private consultant is the exact scenario addressed by this provision.
-
BER Cases 62-7 and 74-2 Precedent Irreconcilability
Both cases are based on the identical code language of this provision, making their reconciliation directly relevant to its application.
-
BER Case 67-12 Part-Time County Engineer Private Plan Submission Non-Recommendation Obligation
The prohibition on a part-time county engineer offering recommendations on their own privately submitted plans directly reflects this provision's restriction on participating in decisions about one's own services.
-
Firm A Dual Role City Engineer and Private Developer Consultant
Firm A serving simultaneously as city review engineer and private consultant to developers within the same city is precisely the dual-role conflict this provision prohibits.
-
Firm A Public Role Marketing Tool Exploitation
Using a public engineering position to market private services to developers exploits the governmental role in a manner inconsistent with this provision's intent to prevent conflicts of interest.
-
Ordinance-Scoped Inspection Dual-Interest Structural Conflict
Holding a city inspection mandate scoped to city interests while also serving developers creates the structural conflict of participating in decisions about one's own privately rendered services.
-
Conflict of Interest State. Firm A City and Developer Dual Engagement
Firm A's financial interest in developer clients competing with its impartiality obligation as city engineer is the core conflict of interest this provision is designed to prevent.
-
Firm A Developer-Compensated Public Review and Inspection Services
Receiving compensation from developers for services rendered on behalf of the city directly violates this provision's prohibition on participating in decisions regarding services provided by one's own organization.
-
Firm A Public-Role Marketing to Developer Prospects
Using the city engineer position to market services to prospective developer clients constitutes leveraging a public role for private gain, contrary to this provision.
-
Firm A Reduced-Scope Public Service Marketing Suspicion
Suspected offering of a reduced review scope to attract developer clients represents a failure of impartiality in public decisions, directly addressed by this provision.
-
BER Case 74-2 Small Municipality Consulting Municipal Engineer Permissibility
This case tests the boundaries of permissible dual engagement under the same code language as this provision, making it directly relevant.
-
BER Case 82-4 Multi-Role County-City-Airport-Grant Administrator Permissibility
Engineer A's multiple simultaneous public and private roles are evaluated against this provision's restrictions on participating in decisions about one's own services.
-
BER Case 75-7 Commission Member Private Service Abstention Mitigation
The abstention mechanism used to mitigate the conflict of a commission member providing private services to applicants is a direct response to the obligations imposed by this provision.
-
Firm A Self-Design-Review Conflict Prohibition
II.4.d. directly prohibits engineers in public service from participating in decisions about services they provide privately, which is exactly the self-review conflict described.
-
Firm A Dual-Service Developer Inspection Conflict Non-Acceptance
II.4.d. prohibits simultaneous public and private service roles that create conflicts, directly governing Firm A's dual role as city inspector and private design engineer.
-
Firm A Developer-Compensated Public Inspection Dual-Interest Structural Conflict
II.4.d. creates the prohibition against participating in public decisions while privately serving the same parties, establishing this structural conflict constraint.
-
Firm A Developer-Compensated Public Review Conflict
II.4.d. directly applies to the conflict of performing public review while being compensated by the private developer subject to that review.
-
Firm A NSPE Code Section II.4.d Violation Reaffirmation
This entity explicitly reaffirms that Firm A's circumstances constitute a violation of II.4.d., making the link direct and explicit.
-
BER-62-7 County Commission Engineer Self-Review Conflict Prohibition
II.4.d. is the code provision underlying the BER-62-7 precedent prohibiting an engineer from reviewing plans in a public role while privately serving developers.
-
BER-62-7 Divided Loyalty Dual-Client Impossibility Recognition
II.4.d. establishes the prohibition on divided loyalty between public and private clients that BER-62-7 recognized as impossible to reconcile.
-
BER Case 62-7 County Commission Engineer Dual-Role Conflict Precedent Application
II.4.d. is the code basis for the BER-62-7 precedent being applied to assess Firm A's dual-role conflict.
-
Firm A Multi-Hat Dual-Client Adequate Representation Impossibility
II.4.d. prohibits the participation in public decisions regarding privately provided services, which underlies the impossibility of adequate representation in multiple simultaneous roles.
-
BER-67-12 Part-Time County Engineer Private Plan Recommendation Prohibition
II.4.d. is the code provision that prohibits the part-time county engineer from recommending private plans in a public capacity, as addressed in BER-67-12.
-
BER-74-2 Small Municipality Public Interest Dual-Role Permissibility
II.4.d. is the identical code language on which BER-74-2 was based, making it directly linked to this precedent's permissibility finding.
-
BER-74-2 and BER-62-7 Precedent Irreconcilability Acknowledged
II.4.d. is the single code provision underlying both BER-62-7 and BER-74-2, making it the source of the acknowledged irreconcilability between those precedents.
-
BER-82-4 Engineer A Review-Recommendation Non-Decision Permissibility
II.4.d. governs the conditions under which simultaneous public and private roles are permissible, which BER-82-4 addressed through the non-decision distinction.
-
BER-82-4 Engineer A No-Influence Abstention Compliance
II.4.d. requires non-participation in decisions about privately provided services, and BER-82-4 conditioned permissibility on abstention from influence, directly linking to this provision.
-
BER-75-7 Commission Engineer Abstention-Conditioned Private Services
II.4.d. is the provision that requires abstention from public decisions involving private services, which BER-75-7 applied as a condition for permissibility.
-
BER Cumulative Precedent Integration. Firm A Conflict Assessment
II.4.d. is the common code provision underlying all the BER precedents being integrated to assess Firm A's conflict.
-
Firm A Developer Client Conflict Proactive Disclosure to City
II.4.d. underlies the obligation to avoid undisclosed conflicts between public duties and private engagements, supporting the disclosure requirement.
-
Firm A Ordinance-Scoped Inspection City-Interest-Only Fidelity
II.4.d. requires that public service engineers act solely in the public interest without private conflicts, directly supporting the city-interest-only fidelity constraint.
-
Firm A Developer Fee-Payment Impartiality Non-Compromise
II.4.d. establishes that public service obligations are not diminished by private compensation arrangements, directly relating to this impartiality constraint.
-
Compensating-Party Benefiting-Party Misalignment Identified for Firm A
This provision prohibits public engineers from participating in decisions about services they privately provide, directly addressing the misalignment where Firm A is paid by developers to review work it is supposed to oversee on behalf of the city.
-
Public Position Marketing Exploitation Prohibition Applied to Firm A
The provision bars engineers in public service from leveraging their governmental role for private gain, which is exactly what Firm A does by marketing its city engineer position to attract developer clients.
-
Objectivity Compromised by Dual-Client Self-Interest in BER 62-7
The provision directly addresses the conflict where a public engineer's self-interest from private retention compromises objectivity in governmental decisions, as seen in BER 62-7.
-
Public Welfare Paramount Invoked in Firm A Multi-Role Assessment
The provision exists to protect public welfare by preventing engineers in public roles from making decisions skewed toward private clients rather than the public interest.
-
Disclosure Insufficiency for Structural Conflict Affirmed in Firm A
The provision establishes a structural prohibition on participation in decisions, implying that disclosure alone cannot cure the conflict that Firm A's dual role creates.
-
Dual-Role Conflict Invoked by Firm A City Inspection Engagement
The provision directly prohibits the dual-role arrangement where Firm A simultaneously serves as city inspector and private engineer for the same developers whose work it inspects.
-
Structural Conflict Non-Curable by Disclosure. Firm A Marketing
The provision's absolute prohibition on participation in decisions about privately provided services confirms that the structural conflict cannot be resolved merely through disclosure.
-
Non-Self-Serving Obligation Violated by Firm A Marketing Conduct
The provision embodies the principle that public engineering roles must not be used as platforms for private commercial gain, which Firm A violates by marketing its city position.
-
Fairness in Competition Violated by Firm A Cost-Savings Promise
The provision prohibits using a public engineering position to benefit private practice, which underlies the unfair competitive advantage Firm A gains by promising developer cost savings derived from its city contract.
-
Client Interest Primacy Violated. City as Firm A's Principal
The provision requires that engineers in public service not let private interests interfere with their public duties, directly addressing Firm A's breach of its agency obligation to the city.
-
Public Welfare Paramount. Infrastructure Inspection Integrity
The provision protects the public by ensuring that engineers performing governmental inspection functions are not simultaneously serving the private interests of those being inspected.
-
Objectivity Compromised. Firm A Inspection of Private Developer Clients
The provision directly addresses the inability of Firm A to objectively perform city inspection duties when it has a private commercial relationship with the developers being inspected.
-
Public Position Marketing Exploitation. Firm A 50% Savings Promise
The provision prohibits engineers in public service from using their governmental position to solicit or benefit private practice, which Firm A does by advertising cost savings tied to its city contract.
-
Divided Loyalty Irreconcilability Invoked in BER 62-7 County Commission Engineer
The provision directly targets the divided loyalty situation where a public engineer cannot faithfully serve both the governmental body and a private client with interests before that body.
-
Small Municipality Public Interest Justification Invoked in BER 74-2
The provision is the code language at issue in BER 74-2, where the Board weighed whether the small municipality exception justified permitting the dual-role arrangement.
-
Review-Recommendation vs Decision Distinction Applied in BER 82-4
The provision's use of the term decisions was the basis for the BER 82-4 distinction between reviewing and recommending versus making final decisions.
-
Abstention-Based Conflict Mitigation Applied in BER 75-7
The provision's prohibition on participation in decisions was the standard against which the Board measured whether abstention could ethically resolve the conflict in BER 75-7.
-
Part-Time County Engineer Plan Submission Recommendation Prohibition in BER 67-12
The provision is the basis for prohibiting the part-time county engineer from submitting private developer plans to the county for approval, as this constitutes participation in decisions about privately provided services.
-
Dual-Role Conflict of Interest Affirmed for Firm A City Engineer Inspection Role
The provision is the primary code basis for the Board's reaffirmation that Firm A's simultaneous public and private roles constitute an impermissible conflict of interest.
-
Precedent Reconciliation Obligation Acknowledged by Board
The provision is the identical code language underlying both BER 62-7 and BER 74-2, making its interpretation central to the Board's acknowledged difficulty in reconciling those precedents.
-
Firm A Conflict-Exploiting Dual-Role Engineering Firm
Firm A participates in decisions regarding its own private services by using its city engineer position to market and deliver inspection services to private developers, directly violating this provision.
-
Firm A City-Retained Development Inspection Engineer
As a city-retained engineer conducting inspections, Firm A is in a public service role where it must not participate in decisions about services it also provides privately to developers.
-
BER 74-2 Municipal Engineer Consulting Firm Principal
This engineer served as municipal engineer while also having the firm retained for capital improvements, placing them in a public role where decisions about their own private services arise.
-
BER 62-7 County Commission Engineering Consultant
This engineer served the county commission in a quasi-governmental advisory capacity while also providing private engineering services to a developer subject to county oversight.
-
Engineer A BER 82-4 Multi-Jurisdiction Dual-Role Municipal Engineer
Retained simultaneously as county engineer, city engineer, and project administrator, this engineer held multiple public service roles where decisions about their own private services could arise.
-
BER 75-7 Commission Member Private Services Engineer
This engineer served on a governmental commission with permit authority while providing private services to parties appearing before that same commission, directly implicating this provision.
-
BER 67-12 Part-Time County Engineer Private Plan Submitter
This engineer served as part-time county engineer while submitting private developer plans to the county for approval, placing them in a public role deciding on their own private work.
-
Dual-Role Conflict Materializes
This provision directly prohibits engineers in public service from participating in decisions regarding services they privately provide, which is the core of the dual-role conflict.
-
Ordinance Establishes Mandatory Review
The ordinance creates the governmental decision-making context in which II.4.d. becomes applicable by requiring review services that the city engineer also privately provides.
-
Section II.4.d Violation Confirmed
This event is the direct confirmation that the engineer's conduct violated II.4.d., making the provision explicitly linked to this outcome.
-
Municipal Engineer Dual Role Ethics Standard. Firm A Application
II.4.d. directly governs engineers in public roles who participate in decisions about their own private services, which is the core issue of Firm A's dual role.
-
Public Official Conflict of Interest Standard. Firm A Application
II.4.d. is the specific conflict of interest provision that applies when Firm A uses its public city engineer position to gain private commercial advantage.
-
BER Case 62-7
BER Case 62-7 is a precedent interpreting conflict of interest in dual public-private engineering roles directly relevant to II.4.d.
-
BER Case 74-2
BER Case 74-2 interprets whether a municipal engineer consultant relationship triggers II.4.d. obligations.
-
BER Case 82-4
BER Case 82-4 directly interprets amended Code Section II.4.d. in the context of simultaneous public engineering roles.
-
BER Case 75-7
BER Case 75-7 addresses whether an engineer on a public board may provide private services to that body, directly implicating II.4.d.
-
BER Case 67-12
BER Case 67-12 establishes precedent on a part-time public engineer submitting private developer plans for approval, directly implicating II.4.d.
-
NSPE Code Section II.4.d - Conflict of Interest in Dual Public-Private Roles
This entity is the direct codification and interpretive elaboration of the II.4.d. provision itself.
-
Dual Public-Private Employment Ethics Standard. Firm A Application
II.4.d. is the governing provision for the ethical obligations Firm A holds in simultaneously serving public and private roles.
-
Engineer Solicitation and Competition Ethics Standard. Firm A Marketing Practice
II.4.d. applies to Firm A's use of its public city engineer position as a marketing tool to solicit private clients, which constitutes participation in decisions regarding its own private services.
-
Local Land Development Ordinance
II.4.d. applies because the ordinance creates the decision-making framework in which Firm A, as city engineer, reviews and approves plans submitted by its own private clients.
-
NSPE Code of Ethics
II.4.d. is a provision within the NSPE Code of Ethics, which is the primary normative authority governing Firm A's obligations.
-
Firm A Dual-Role Irreconcilable Conflict Identification
II.4.d. directly prohibits engineers in public service from participating in decisions about services they provide privately, which is the core conflict Firm A failed to identify.
-
Firm A Public Agency Role Commercial Exploitation Recognition
II.4.d. prohibits using a public engineering role to benefit private practice, which is exactly the exploitation Firm A failed to recognize.
-
Firm A Dual-Role City Engineer Conflict of Interest Recognition
II.4.d. requires engineers in public roles to avoid decisions involving their private services, directly requiring the conflict recognition Firm A lacked.
-
Firm A Developer-Client Inspection Objectivity Preservation
II.4.d. requires separation of public decision-making from private financial interests, which is the objectivity Firm A failed to preserve.
-
Firm A Multi-Client Simultaneous Representation Feasibility Assessment
II.4.d. prohibits simultaneous public and private service roles in the same decisions, making feasibility assessment of such arrangements directly required.
-
Firm A Incumbent Multi-Contract Structural Conflict Proactive Disclosure to City
II.4.d. implies engineers must not participate in conflicted decisions, which requires proactive disclosure of private relationships to the public body.
-
Firm A Disclosure Insufficiency Recognition for Developer-Client Inspection Conflict
II.4.d. sets a standard that mere disclosure may be insufficient when the structural conflict involves participating in public decisions about private clients.
-
Firm A Improper Competitive Advantage Recognition in City Inspection Role
II.4.d. prohibits leveraging a public engineering position for private benefit, which is the competitive advantage Firm A failed to recognize as improper.
-
Firm A Competing Stakeholder Interest Faithful Agent Boundary
II.4.d. establishes the boundary between public service obligations and private practice interests that Firm A failed to maintain.
-
Firm A Developer-Client Marketing Exploitation Prohibition Self-Application
II.4.d. prohibits using a public engineering position to solicit or benefit private practice, which Firm A violated by marketing inspection cost savings.
-
Firm A BER Dual-Precedent Municipal Engineer Dual-Role Permissibility Synthesis
II.4.d. is the governing provision whose application to dual-role municipal engineers required the precedent synthesis Firm A failed to perform.
-
BER 75-7 Commission Member Abstention-Conditioned Private Services Self-Assessment
II.4.d. is the provision that the BER 75-7 engineer addressed by conditioning private services on abstention from related public decisions.
-
Engineer A BER 82-4 Review-Recommendation Non-Decision Boundary Application
II.4.d. is the provision Engineer A in BER 82-4 navigated by structuring activities to avoid participating in decisions about his own private services.
-
BER 67-12 Part-Time County Engineer Private Plan Approval Recommendation Non-Issuance
II.4.d. is the provision violated in BER 67-12 when the county engineer submitted private plans for county approval without recusing himself.
-
Firm A BER Five-Precedent Dual-Role Conflict Spectrum Synthesis
II.4.d. is the central provision the BER synthesized across five precedent cases to determine permissibility of dual-role municipal engineer arrangements.
-
Firm A Compensating-Party Benefiting-Party Misalignment Recognition
II.4.d. prohibits arrangements where private compensation creates conflicts with public decision-making duties, which is the misalignment Firm A failed to recognize.
-
Firm A Inspection Quality Non-Subordination to Developer Approval Incentive
II.4.d. requires that public inspection duties not be compromised by private financial interests, which Firm A failed to maintain.
-
Firm A Multi-Hat Adequate Representation Impossibility Self-Recognition Deficit
II.4.d. prohibits the multi-hat arrangement Firm A engaged in, making self-recognition of its impossibility directly required by this provision.
-
Firm A Public Agency Position Private Marketing Non-Exploitation Self-Monitoring Deficit
II.4.d. prohibits using a public agency position to benefit private practice, requiring the self-monitoring Firm A failed to exercise.
-
Firm A Dual-Role City Engineer Conflict of Interest Recognition Deficit
II.4.d. directly requires recognition of the conflict created by serving as both public reviewer and private consultant, which Firm A lacked.
-
Firm A Self-Design-Review Prohibition Recognition Deficit
II.4.d. prohibits participating in public decisions about one's own private services, which includes reviewing and inspecting one's own designs.
-
BER 62-7 County Commission Engineer Divided Loyalty Conflict Recognition
II.4.d. is the provision whose violation the BER 62-7 engineer failed to recognize when simultaneously serving the commission and private clients before it.
-
BER 74-2 Small Municipality Dual-Role Public Interest Justification Recognition
II.4.d. is the provision BER 74-2 addressed by recognizing that small municipality circumstances could justify limited dual-role arrangements under specific conditions.
-
BER Board BER 62-7 74-2 Precedent Irreconcilability Acknowledgment
II.4.d. is the provision at the center of the irreconcilable tension between BER 62-7 and BER 74-2 that the Board acknowledged.
-
Firm A Faithful Agent City Client Interest Primacy
III.8.a. requires conformance with state registration laws, which typically mandate faithful service and ethical conduct in engineering practice on behalf of clients.
-
Firm A City-Retained Engineer Multi-Role Conflict Non-Engagement
III.8.a. requires conformance with state registration laws that may directly regulate or prohibit conflicted multi-role engineering arrangements.
-
BER-74-2 Municipal Engineer Small Municipality Public Interest Dual-Role
III.8.a. is relevant to the BER 74-2 precedent as state registration laws governing municipal engineers may permit or restrict dual-role service arrangements.
-
BER-74-2 BER-62-7 Precedent Reconciliation Acknowledgment
III.8.a. is relevant because differing state registration law requirements may partly explain the different conclusions reached in BER 62-7 and BER 74-2.
-
City Engages Firm A
This provision requires that the firm engaged to perform city engineering services must conform with state registration laws applicable to public engineering practice.
-
Municipal Engineer Accepts Private Firm Role (BER 74-2)
This provision requires engineers accepting public or private engineering roles to comply with state registration laws governing such practice.
-
Engineer A Accepts Multiple Public and Private Roles (BER 82-4)
This provision requires that engineers practicing in multiple public and private capacities conform with all applicable state registration requirements.
-
Firm A Dual Role City Engineer and Private Developer Consultant
Firm A's simultaneous public and private engineering roles must conform to state registration laws governing the practice of engineering in both capacities.
-
BER Case 74-2 Small Municipality Consulting Municipal Engineer Permissibility
This case explicitly involves a state law requiring municipalities to retain a municipal engineer, making conformance with state registration and practice laws directly relevant.
-
BER Case 82-4 Multi-Role County-City-Airport-Grant Administrator Permissibility
Engineer A's multiple simultaneous engineering roles across governmental bodies must each conform to state registration laws governing engineering practice.
-
Firm A Marketing Exploitation of City Engineer Position
III.8.a. requires conformance with state registration laws, which may govern the scope and manner of engineering practice including marketing conduct tied to a licensed public role.
-
Firm A City Engineer Position Marketing Exploitation Prohibition
III.8.a. requires conformance with state registration laws that govern the boundaries of licensed engineering practice, including improper use of a public engineering position for private solicitation.
-
Firm A Improper Competitive Method, 50% Cost Savings Advertisement
III.8.a. requires conformance with state registration laws that may prohibit misleading or improper advertising by registered engineers.
-
Firm A Improper Competitive Method. City Position Marketing
III.8.a. requires conformance with state registration laws governing proper competitive conduct by licensed engineers in public roles.
-
Firm A Competitive Fairness Non-Exploitation of City Contract Position
III.8.a. requires conformance with state registration laws that establish standards for fair competitive practice among licensed engineers.
-
Firm A Reduced-Scope Inspection Marketing Incentive Prohibition
III.8.a. requires conformance with state registration laws that govern the scope of inspection services a registered engineer may offer or advertise.
-
Dual-Role Conflict Invoked by Firm A City Inspection Engagement
State registration laws governing engineering practice provide the regulatory backdrop within which Firm A's dual-role arrangement must be evaluated for compliance.
-
Dual-Role Conflict of Interest Affirmed for Firm A City Engineer Inspection Role
Conformance with state registration laws is relevant to whether Firm A's combined public and private engineering practice is conducted within legally and ethically permissible boundaries.
-
Firm A City-Retained Development Inspection Engineer
As a consulting firm providing engineering services to the city, Firm A must conform with state registration laws governing the practice of engineering in that jurisdiction.
-
BER 74-2 Municipal Engineer Consulting Firm Principal
State law required every municipality to retain a municipal engineer, making compliance with state registration laws directly applicable to this role.
-
BER 62-7 County Commission Engineering Consultant
This engineer performed all engineering and advisory services for the county commission, requiring conformance with state registration laws governing engineering practice.
-
Engineer A BER 82-4 Multi-Jurisdiction Dual-Role Municipal Engineer
Retained as engineer across multiple jurisdictions including county and city roles, this engineer must conform with state registration laws applicable to each area of practice.
-
BER 67-12 Part-Time County Engineer Private Plan Submitter
Serving as part-time county engineer and submitting plans as a private consultant requires conformance with state registration laws governing engineering practice in both capacities.
-
Ordinance Establishes Mandatory Review
The ordinance mandating engineering review services implicates state registration law compliance, which III.8.a. requires engineers to conform with in their practice.
-
NSPE Code of Ethics
III.8.a. is a provision of the NSPE Code of Ethics, which is the primary normative authority governing Firm A's professional obligations including registration compliance.
-
Municipal Engineer Dual Role Ethics Standard. Firm A Application
III.8.a. requires conformance with state registration laws, which may govern the legal conditions under which Firm A may serve simultaneously as city engineer and private consultant.
-
BER Case 74-2
BER Case 74-2 addresses the consultant-as-municipal-engineer relationship under state law, directly implicating III.8.a. regarding registration and legal compliance.
-
Firm A Dual-Role Irreconcilable Conflict Identification
III.8.a. requires conformance with state registration laws, which typically govern the scope and conditions of engineering practice including dual-role arrangements.
-
Firm A BER Dual-Precedent Municipal Engineer Dual-Role Permissibility Synthesis
III.8.a. requires conformance with state registration laws that may define permissible boundaries for municipal engineer dual-role arrangements.
-
Firm A BER Five-Precedent Dual-Role Conflict Spectrum Synthesis
III.8.a. is relevant to the BER synthesis because state registration laws governing engineering practice scope inform the permissibility of dual-role arrangements.
-
BER 74-2 Small Municipality Dual-Role Public Interest Justification Recognition
III.8.a. is relevant because state registration laws may define conditions under which small municipality dual-role arrangements are legally permissible.
Cross-Case Connections
View ExtractionExplicit Board-Cited Precedents 1 Lineage Graph
Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.
Principle Established:
A consultant serving as municipal engineer and providing engineering services to the municipality is not necessarily unethical, as public interest may be best served by providing small municipalities with the most competent engineering services available.
Citation Context:
The Board cited this case as a contrasting precedent where a consultant serving as municipal engineer was not found unethical, though the Board acknowledged difficulty reconciling it with BER Case 62-7.
Principle Established:
An engineer who passes judgment on behalf of a public client on work in which the engineer also participated for a private client has a conflict of interest due to divided loyalties and self-interest.
Citation Context:
The Board cited this case to establish that an engineer acting as staff for a public body while also serving a private developer with opposing interests creates a conflict of interest, even with good intentions.
Principle Established:
An engineer serving as both city and county engineer for a retainer fee may provide private engineering consulting services to the city and county, provided the engineer's role involves reviewing and recommending rather than making formal decisions, and no improper influence is exerted.
Citation Context:
The Board cited this case twice to illustrate that an engineer serving as both city and county engineer who reviews, recommends, and oversees plans rather than making formal 'decisions' does not violate the amended Code, and that no improper influence was exerted.
Principle Established:
An engineer serving on a commission may ethically provide services to private owners if the engineer abstains from discussion and votes on related permit applications and takes no action to influence favorable decisions.
Citation Context:
The Board cited this case to establish that an engineer serving on a local board or commission may ethically provide services to private owners only if the engineer abstains from relevant discussions and votes and takes no action to influence favorable decisions.
Principle Established:
When an engineer serves as a part-time county engineer and as a private consultant, submitting plans of a private developer to the county for approval, the engineer should not offer any recommendation for their approval, as it is contrary to the Code's requirement to represent the best interests of the client.
Citation Context:
The Board cited this case to establish that a part-time county engineer acting as a private consultant must not offer recommendations for approval of plans submitted to the county on behalf of private developers.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions (1 board)
View ExtractionWas it ethical for Engineer A to serve as city engineer and also provide review and inspection services for private developers within the city?
Implicit (4)
Does the fact that developers directly compensate Firm A for city-mandated review and inspection services create a financial dependency that structurally compromises Firm A's impartiality toward the city, independent of any separate private consulting relationship?
When Firm A also designs infrastructure for a private developer and then inspects that same infrastructure on the city's behalf, does the self-review prohibition apply, and should the Board have explicitly addressed this scenario as a distinct and aggravated form of the dual-role conflict?
Should the city bear any institutional responsibility for establishing an ordinance structure that foreseeably creates a compensating-party conflict of interest by requiring developers to pay the city's engineer directly, and does that structural flaw affect the ethical analysis of Firm A's conduct?
Is Firm A's active marketing of a 50% cost savings to prospective developer clients an independently sufficient basis for an ethics violation, even if the underlying dual-role engagement were otherwise permissible under a BER 74-2 type analysis?
Cross-cutting analytical questions (12)
These questions consider the case as a whole rather than a specific board question above.
Show 12 cross-cutting questionsPrinciple tension (4)
Does the Small Municipality Public Interest Justification invoked in BER 74-2 - which permits a consulting firm to serve as municipal engineer while also performing private work - irreconcilably conflict with the Divided Loyalty Irreconcilability principle invoked in BER 62-7, and if so, which principle should govern when a firm actively exploits its public role to solicit private clients within the same jurisdiction?
Does the Abstention-Based Conflict Mitigation principle applied in BER 75-7 - which permits an engineer serving on a commission to provide private services so long as they abstain from conflicted votes - conflict with the Structural Conflict Non-Curable by Disclosure principle affirmed for Firm A, and what distinguishes the two cases such that abstention is sufficient in one context but insufficient in the other?
Does the Review-Recommendation versus Decision Distinction applied in BER 82-4 - which permits an engineer to hold multiple public roles when they only recommend rather than decide - conflict with the Objectivity Compromised principle applied to Firm A's inspection role, given that inspection findings are functionally determinative of whether developer infrastructure is accepted by the city even if formally labeled as recommendations?
Does the Public Welfare Paramount principle - which might support permitting Firm A to serve as city engineer to ensure competent infrastructure oversight in a resource-constrained municipality - conflict with the Client Interest Primacy principle requiring Firm A to act as faithful agent to the city, when Firm A's private developer engagements create financial incentives to approve rather than rigorously scrutinize developer-submitted plans?
Theoretical (4)
From a deontological perspective, did Firm A violate its categorical duty of loyalty to the city as its principal client by simultaneously accepting compensation from private developers for services rendered ostensibly on the city's behalf, regardless of whether any actual harm to inspection quality resulted?
From a consequentialist perspective, did the aggregate harm produced by Firm A's dual-role arrangement - including compromised inspection integrity, distorted competition among engineering firms, and erosion of public trust in municipal oversight - outweigh any efficiency benefits the city or developers may have gained from consolidated engineering services?
From a virtue ethics perspective, did Firm A demonstrate the professional integrity expected of a public-serving engineer when it openly advertised its city engineer position as a marketing tool promising developers a 50% cost savings, thereby subordinating the virtue of impartiality to commercial self-interest?
From a deontological perspective, does the structural impossibility of Firm A simultaneously fulfilling its duty to the city - requiring rigorous, uncompromised inspection - and its duty to developer clients - whose approval interests may conflict with full enforcement of city standards - constitute an irreconcilable breach of professional duty that no amount of disclosure or procedural safeguard can remedy?
Counterfactual (4)
If Firm A had proactively disclosed to the city every instance in which a prospective private developer client was also subject to Firm A's city inspection authority, and the city had formally consented to each such engagement, would that disclosure and consent have been sufficient to cure the structural conflict of interest, or would the underlying divided loyalty have persisted regardless?
If Firm A had adopted the abstention model applied in BER Case 75-7 - recusing itself from city review and inspection of any development project for which it also served as the developer's private engineer - would that structural separation have been sufficient to render the dual-role arrangement ethical, or would the residual marketing exploitation of the city engineer position have remained an independent ethical violation?
If the local ordinance had explicitly prohibited the city's retained engineering firm from providing any services to private developers subject to that firm's review and inspection authority, would Firm A's conduct have been unambiguously unethical from the outset, and does the absence of such an explicit prohibition in the actual ordinance diminish or eliminate Firm A's independent professional obligation to avoid the conflict?
If Firm A had never marketed its city engineer position to prospective developer clients and had instead obtained its private developer engagements through entirely independent channels, would the dual-role arrangement have been ethically permissible under the precedent established in BER Case 74-2, or would the structural conflict between city inspection duties and developer client interests have rendered it unethical even without the marketing exploitation?
Decisions & Arguments (8)
View ExtractionShould Firm A accept private developer clients within the same jurisdiction where it serves as the city's retained plan review and construction inspection engineer, or must it structurally separate those roles to preserve its impartiality toward the city?
The City-Retained Inspection Engineer Private Developer Dual-Service Prohibition Obligation and the Developer-Compensated Public Inspection Dual-Interest Non-Acceptance Constraint both prohibit this arrangement: Firm A cannot adequately represent the city's interests while simultaneously serving private developer clients whose approval interests conflict with rigorous public oversight, and the developer-direct fee-payment structure creates a financial dependency that structurally compromises impartiality regardless of any separate consulting relationship. The Regulated-Party Fee-Payment Public Review Impartiality Non-Compromise Constraint further establishes that the developer's status as fee-payer does not diminish Firm A's obligation of impartiality to the city. Against this, BER 74-2's Small Municipality Public Interest Justification permits a consulting firm to serve as municipal engineer while also performing private work where small municipalities require access to competent engineering services, and the Firm A City Infrastructure Standard Primacy in Inspection obligation could theoretically be honored through procedural safeguards.
Uncertainty is created by the acknowledged difficulty of reconciling BER 62-7 and BER 74-2 under identical code language. If the municipality genuinely lacks alternative engineering resources, BER 74-2's permissive framework could rebut the prohibition. Additionally, if the city knowingly consented to the arrangement and no concrete inspection failure can be demonstrated, the argument that no actual harm occurred could weaken the structural conflict finding. The Regulated-Party Fee-Payment Public Review Impartiality Non-Compromise Constraint itself acknowledges the tension by framing the developer's fee-payer status as not diminishing, rather than automatically defeating, the impartiality obligation.
The city retained Firm A to perform mandatory plan review and construction inspection of private developer projects under a local ordinance, with developers paying Firm A's fees directly for those services. Firm A simultaneously accepted private design and inspection engagements from those same developers whose projects it was charged with reviewing and inspecting on the city's behalf. The developer-direct compensation structure meant Firm A's revenue was partially contingent on developer satisfaction, independent of any separate private consulting relationship.
When Firm A both designs infrastructure for a private developer and then inspects that same infrastructure on the city's behalf, should Firm A treat this self-review scenario as a distinct and irreconcilable conflict requiring role separation, or may it proceed under the review-recommendation framework of BER 82-4 on the basis that its inspection findings are formally advisory rather than final decisions?
The Multi-Hat Dual-Client Adequate Representation Impossibility Recognition Obligation establishes that the cumulative multiplicity of roles, designer, reviewer, and inspector for the same infrastructure, creates a conflict so fundamental that adequate representation of the city's separate interests becomes impossible and is not curable through disclosure or consent. The City-Retained Engineer Self-Design-Review Prohibition Obligation independently prohibits self-review because an inspector who designed the work has a reputational and financial interest in validating prior design decisions rather than identifying deficiencies, eliminating the independent engineering judgment the city's review function is designed to provide. The BER 62-7 County Commission Engineer Self-Review Conflict Prohibition reinforces this by condemning an engineer who passes judgment on behalf of a public client on work the engineer itself performed. Against this, BER 82-4's Review-Recommendation Non-Decision Permissibility framework found that an engineer holding multiple public and private roles did not violate ethics where the engineer only reviewed, recommended, and oversaw plans rather than making final decisions.
Uncertainty is generated by the degree to which the city actually exercises independent substantive review of Firm A's inspection findings. If the city routinely overrides or independently verifies those findings through its own staff, the functional-equivalence-to-decision argument weakens and BER 82-4's permissive framework gains traction. Additionally, if Firm A's design role and inspection role are performed by different personnel within the firm with genuine internal separation, the self-review prohibition's force may be attenuated. The BER 82-4 precedent creates genuine ambiguity because it was decided under identical code language and reached a permissive conclusion based on the review-versus-decision distinction.
Firm A regularly prepares drawings for private developers and simultaneously reviews those same drawings on the city's behalf, then performs construction inspection of the resulting infrastructure at developer expense. This creates a self-review scenario in which Firm A evaluates the adequacy of its own prior professional design judgments in its capacity as the city's inspection agent. The city, lacking in-house engineering expertise, relies on Firm A's inspection findings as functionally determinative of whether developer infrastructure is accepted, even if those findings are formally characterized as recommendations.
Should Firm A use its position as the city's retained inspection engineer as a marketing tool, openly advertising to prospective developer clients that retaining Firm A for private services yields a 50% reduction in inspection costs, or must it refrain from commercially exploiting its publicly conferred authority as a competitive differentiator?
The Firm A Public Role Marketing Exploitation Prohibition and the Firm A Competitive Fairness Non-Exploitation of City Contract obligation both prohibit using the city engineer position as a marketing instrument: a publicly conferred advantage may not be weaponized as a commercial differentiator against competitors who lack access to the same publicly conferred position. The Non-Self-Serving Advisory Obligation independently prohibits engineers from structuring their commercial conduct to serve their own financial interests at the expense of the public client's interests. The Fairness in Competition principle establishes that the marketing conduct distorts the competitive market for engineering services because competing firms cannot offer equivalent cost savings without holding the city contract. Even under the most permissive reading of BER 74-2, which tolerates dual municipal and private roles in small municipalities, no precedent sanctions affirmative exploitation of a public role as a private marketing instrument.
Uncertainty arises because if Firm A's advertised cost savings were genuine and derived from legitimate economies of scale, such as reduced mobilization costs from already being on-site, rather than from reduced inspection rigor or preferential treatment, the rebuttal condition that 'commercial advertising of genuine efficiency gains is not inherently improper' could apply. Additionally, if the BER 74-2 framework permits the underlying dual-role arrangement, it is arguable that communicating the financial consequences of that permissible arrangement to prospective clients is not independently prohibited. The absence of any BER precedent directly addressing whether marketing of cost savings derived from a public role constitutes an independently actionable ethics violation creates genuine uncertainty about whether this conduct is a separate violation or merely evidence of the underlying structural conflict.
Firm A openly advertised to prospective private developer clients that they could save 50% on inspection costs by retaining Firm A for private services, with the cost savings made possible exclusively by Firm A's position as the city's retained inspection engineer. This marketing practice converted Firm A's publicly conferred regulatory authority into a commercial selling proposition, creating a competitive advantage unavailable to other engineering firms who did not hold the city inspection contract. The marketing conduct was not incidental but affirmative and systematic, signaling to the market that access to streamlined inspection outcomes was bundled with retention of Firm A as a private consultant.
Should Firm A actively market its city engineer appointment to prospective developer clients by advertising a 50% cost savings, or refrain from using its public position as a commercial differentiator in soliciting private engagements?
The Non-Self-Serving Advisory Obligation prohibits engineers in public service from using their public position for private commercial advantage. The Fairness in Competition principle requires that competitive advantages in the engineering market derive from technical capability and efficiency rather than from publicly conferred regulatory authority. The Public Position Marketing Exploitation Prohibition independently condemns the conversion of a public appointment into a sales proposition, separate from any structural conflict-of-interest analysis. Even the most permissive reading of BER 74-2, which tolerates dual municipal and private roles in small municipalities, does not sanction affirmative exploitation of a public role as a private marketing instrument.
Uncertainty arises because no BER precedent directly addresses whether marketing cost savings derived from a public role constitutes an independently actionable ethics violation when the underlying dual-role arrangement might otherwise be permissible. If Firm A's advertised cost savings were genuine and derived from legitimate economies of scale rather than from reduced inspection rigor or regulatory favoritism, the rebuttal condition that 'commercial communication of genuine efficiency gains is permissible' could apply. Additionally, if the city was aware of and consented to Firm A's marketing practices, the question of whether the public client's acquiescence affects the ethical analysis remains open.
Firm A openly marketed its city engineer appointment to prospective private developer clients, advertising that retaining Firm A as their private engineer would yield a 50% reduction in inspection costs, a savings made possible exclusively by Firm A's publicly conferred inspection authority. This marketing conduct occurred concurrently with Firm A's acceptance of developer clients whose projects were subject to its city inspection role. Competing engineering firms without the city inspection contract could not offer equivalent cost savings regardless of their technical capability or efficiency.
Should Firm A treat proactive disclosure of each dual engagement to the city and formal city consent as sufficient to cure the structural conflict of interest, or must Firm A achieve complete role separation by declining developer engagements regardless of disclosure?
The Disclosure Insufficiency for Structural Conflict principle holds that when divided loyalty inheres in the role relationship itself rather than arising from particular circumstances, no disclosure or consent mechanism can dissolve the conflict because the city's consent would mean only that it knowingly accepted a compromised inspection regime, not that inspection would in fact be uncompromised. The Divided Loyalty Irreconcilability principle from BER 62-7 holds that simultaneous conflicting loyalties cannot be reconciled by procedural means. The Abstention-Based Conflict Mitigation Permissibility Principle from BER 75-7 supports the view that disclosure paired with recusal from discrete conflicted decisions can be sufficient where roles are separable and substitutable decision-makers exist. The Compensating-Party–Benefiting-Party Misalignment Conflict Principle identifies that the city's meaningful informed consent is structurally limited by its dependence on Firm A.
Uncertainty is generated by the BER 75-7 abstention precedent, which suggests that consent-plus-recusal can cure commission-level conflicts, creating the rebuttal condition that if disclosure is paired with a robust recusal mechanism and the city has genuine capacity to engage substitute inspectors for conflicted projects, the structural conflict may be manageable rather than irreconcilable. If the city routinely exercises independent substantive review of Firm A's inspection findings, the functional equivalence of recommendations to decisions may not hold, weakening the case for treating the conflict as non-curable. The acknowledged irreconcilability between BER 62-7 and BER 74-2 under identical code language means the boundary between curable and non-curable conflicts remains contested in the precedential record.
Firm A served as city-retained inspection engineer while simultaneously accepting private developer clients whose projects were subject to its city inspection authority. Developers compensated Firm A directly for inspection services. The city, lacking in-house engineering expertise, was dependent on Firm A's professional judgment and not positioned to independently evaluate or override Firm A's inspection conclusions. BER 75-7 established that a commission member engineer may provide private services so long as they recuse from conflicted votes, suggesting that disclosure-plus-abstention can cure commission-level conflicts. The Board affirmed that disclosure is insufficient to cure the structural conflict in Firm A's situation.
Should Firm A accept simultaneous roles as city-retained engineer and private consultant to developers whose work it inspects, or decline the private developer engagements to preserve its fidelity to the city as principal client?
BER 74-2 permits a consulting firm to serve as municipal engineer while also performing private work in the same jurisdiction under a public interest justification for small municipalities lacking alternative engineering resources. BER 62-7 condemns divided loyalty when a firm serves clients with potentially conflicting interests, finding irreconcilability in dual-client arrangements. BER 82-4's review-recommendation versus decision distinction permits multiple public roles when the engineer only recommends rather than decides, but this distinction collapses where the city lacks independent capacity to evaluate or override Firm A's inspection findings. The developer-direct compensation structure creates a compensating-party misalignment independent of any separate consulting relationship.
Uncertainty arises because BER 74-2 and BER 62-7 rest on identical code language yet reach different conclusions, leaving unresolved when the public interest justification defeats the divided loyalty principle. The functional equivalence of Firm A's inspection recommendations to decisions depends on the degree to which the city actually exercises independent substantive review. If the city knowingly consented to the arrangement and no concrete inspection failure can be demonstrated, the consequentialist rebuttal that 'no harm occurred' creates pressure toward permissibility under BER 74-2.
The city retained Firm A as its engineer under an ordinance requiring mandatory review and inspection of developer-submitted infrastructure. Simultaneously, Firm A accepted private developer clients within the same jurisdiction whose projects were subject to Firm A's city inspection authority. Developers directly compensated Firm A for the city-mandated review and inspection services. BER precedents 74-2, 62-7, and 82-4 establish competing frameworks for evaluating dual-role municipal engineering arrangements.
Should Firm A perform city-mandated inspection of developer infrastructure that Firm A itself designed, or must it recuse from self-review and arrange for independent inspection of its own design work?
The self-review prohibition holds that an engineer cannot objectively inspect or evaluate its own prior design work because reputational and financial interests in validating prior design decisions are structurally irreconcilable with the objectivity required by the inspecting client. This prohibition is analytically distinct from the broader divided-loyalty concern: even if Firm A had no private consulting relationship with the developer, the act of inspecting one's own design eliminates the possibility of independent professional judgment. No disclosure, consent, or procedural safeguard can restore objectivity that is categorically absent when an engineer evaluates its own work. The self-review scenario constitutes a distinctly aggravated and independently sufficient form of the dual-role conflict beyond the general inspection-client conflict.
Uncertainty arises because the Board's existing precedents address dual-role conflicts in terms of client loyalty and compensation but do not explicitly resolve whether the self-review prohibition applies as a categorically separate violation. If the city retained independent authority to override Firm A's inspection findings, or if a separate city official conducted substantive review of Firm A's recommendations, the self-review concern might be partially mitigated. The ordinance's silence on this scenario could be interpreted as legislative acquiescence rather than prohibition.
Firm A served as city-retained engineer with inspection authority over developer-submitted infrastructure. In at least some instances, Firm A also designed that same infrastructure for the private developer before being called upon to inspect it on the city's behalf. The ordinance establishing mandatory review did not explicitly address the self-review scenario. BER 62-7 addresses dual-client conflicts but does not explicitly resolve whether the self-review prohibition applies as a categorically distinct violation beyond the general divided loyalty concern.
When Firm A has designed infrastructure for a private developer, should Firm A recuse itself entirely from city inspection of that same infrastructure, or may it proceed with inspection under disclosure and consent protocols?
The Self-Review Prohibition establishes that an engineer cannot objectively inspect or evaluate its own prior design work because reputational and financial interests in validating prior design decisions are structurally irreconcilable with the objectivity required by the inspecting client. The Structural Conflict Non-Curable by Disclosure principle holds that no disclosure, consent, or procedural safeguard can restore objectivity that is categorically absent when an engineer evaluates its own work. The BER 62-7 Divided Loyalty Irreconcilability principle applies with heightened force in the self-review scenario because the conflict is not merely between two client loyalties but between the engineer's duty to the city and its reputational interest in its own prior professional judgments. The Functional Equivalence Doctrine treats Firm A's inspection findings as decisions rather than recommendations given the city's total reliance.
The Board's primary opinion addressed the dual-role conflict in general terms without explicitly identifying the self-review scenario as a distinct and aggravated violation, leaving uncertainty about whether the self-review prohibition applies categorically or only where actual bias can be demonstrated. BER 82-4's review-recommendation distinction could be invoked to argue that Firm A's inspection findings remain formally advisory and subject to city override, preserving a theoretical separation between design and inspection functions. If the city retained an independent third-party reviewer for projects where Firm A served as designer, the self-review concern might be structurally addressed without requiring full recusal.
Firm A served as private design engineer for developers within the city and simultaneously held the city engineer appointment under an ordinance requiring mandatory review and inspection of developer-submitted infrastructure. In at least some instances, Firm A designed the infrastructure it was subsequently charged with inspecting on the city's behalf. The city lacked in-house engineering expertise sufficient to independently evaluate Firm A's inspection findings, making those findings functionally determinative of whether developer infrastructure was accepted.
Event Timeline (13)
Case timeline
- Duty to avoid conflicts of interest
- Obligation not to pass engineering judgment on one's own work
- Duty of undivided loyalty to each client
- Prohibition against self-dealing in a position of public trust
- Maintaining integrity of the public engineering review function
- Avoiding self-assessment of own professional work
- Upholding impartiality in county engineering role
- Serving the public interest by providing competent engineering to municipalities lacking in-house capacity
- Complying with state law requiring municipal engineer retention
- Strict avoidance of conflict of interest situations (in tension with BER 62-7 standard)
- Duty to avoid self-assessment of own firm's work
- Avoiding participation in decisions where self-interest was implicated
- Transparency about conflict through abstention
- Duty not to use positional authority to benefit private clients
- Operating within the letter of the amended Code provisions distinguishing decisions from recommendations
- Not directly participating in final approval decisions on work in which he had a private interest
- Providing engineering services across multiple public entities
- Spirit of conflict of interest avoidance (arguably)
- Duty to avoid situations creating appearance of impropriety across overlapping roles
- Failure to establish structural safeguards preventing Firm A from serving conflicting clients
- Failure to ensure impartiality of the review and inspection function
- Providing infrastructure oversight for public benefit
- Ensuring development meets city design standards
- Technically providing contracted engineering services to multiple clients
- Duty of loyalty to the city as primary client (NSPE Code Section II.4.d)
- Obligation to disclose conflicts of interest to all affected clients
- Obligation to avoid situations where self-interest divides professional loyalty
- Duty to represent the separate and differing interests of each client adequately
- Obligation not to accept compensation from multiple parties on the same project without full disclosure and consent
- Obligation not to exploit a public trust role for private commercial gain (NSPE Code Section II.4.d)
- Duty to avoid conduct that creates the appearance of impropriety or compromises impartiality
- Obligation to provide developers the full range of independent inspection services they require
- Duty not to use confidential or positional information from one client engagement to benefit another
- Obligation to act in the public interest, not personal financial interest
- Prohibition against solicitation of clients through misleading or ethically compromised representations
Narrative (2 main characters)
View ExtractionOpening Context
Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.
You are Engineer A, a principal at Firm A, a private consulting engineering firm retained by a city to provide design review and construction inspection services under a local land development ordinance. Private developers within the city are required to submit plans to the city for review, and to pay the city's costs for having Firm A perform that review. During construction, developers must also pay for Firm A's inspection services on the city's behalf, with those inspections limited by ordinance to verifying that infrastructure destined for city ownership meets the city's design standards. Firm A also takes on design and inspection work directly for private developers operating within that same city, and has been openly telling prospective developer clients that retaining Firm A for private services can reduce their inspection costs by 50 percent. The decisions ahead concern how Firm A should structure and represent these overlapping roles.
Main characters (2)
Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.
Tension between Firm A City-Retained Engineer Multi-Role Conflict Non-Engagement and Firm A Inspection Quality Non-Subordination to Developer Approval Incentive
Tension between Firm A Self-Design-Review Conflict Prohibition and Firm A Developer Client Inspection Objectivity Preservation
Firm A simultaneously owes undivided faithful agency to the City as its inspection client and a duty of objectivity to the developer client it is also serving. These duties are structurally incompatible: the City's interest is rigorous, arms-length inspection enforcement, while the developer's interest is expedient approval and cost minimization. Any inspection judgment Firm A renders is shadowed by a financial incentive to satisfy the developer, making genuine fidelity to the City logically impossible to guarantee. Fulfilling one obligation fully necessarily degrades the other — the engineer cannot be both a zealous city agent and an objective developer advisor on the same regulated project.
Firm A's obligation to proactively disclose its developer-client conflict to the City stands in direct tension with its apparent business strategy of advertising 50% cost savings to developers — a marketing claim that is only credible if Firm A exploits its insider position as the City's inspection engineer to promise reduced scrutiny or streamlined approvals. Fulfilling the disclosure obligation would expose and terminate the very commercial arrangement that makes the 50% savings claim viable. Conversely, sustaining the marketing strategy requires concealing or downplaying the conflict from the City, directly violating the disclosure duty. This tension reveals that the firm's competitive method is structurally dependent on non-disclosure.
The obligation to hold City infrastructure standards as paramount in every inspection decision is placed under structural pressure by the fact that the developer — the regulated party — is also paying Firm A fees for private services. The fee-payment relationship creates a financial dependency that the constraint recognizes as inherently corrosive to impartiality. Even if the engineer intends to uphold standards, the economic reality that a failed inspection or enforcement action harms a paying client creates a systematic bias risk. The tension is not merely hypothetical: the constraint exists precisely because the payment structure makes impartial standard primacy unreliable, meaning the obligation and the constraint together identify an arrangement that cannot be ethically sustained.
Tension between Firm A Public Role Marketing Exploitation Prohibition and Developer-Compensated Public Inspection Dual-Interest Non-Acceptance Constraint
Tension between Firm A Dual-Service Private Developer Prohibition and Firm A Developer Client Conflict Proactive Disclosure to City
The obligation to hold City infrastructure standards as paramount in every inspection decision is placed under structural pressure by the fact that the developer — the regulated party — is also paying Firm A fees for private services. The fee-payment relationship creates a financial dependency that the constraint recognizes as inherently corrosive to impartiality. Even if the engineer intends to uphold standards, the economic reality that a failed inspection or enforcement action harms a paying client creates a systematic bias risk. The tension is not merely hypothetical: the constraint exists precisely because the payment structure makes impartial standard primacy unreliable, meaning the obligation and the constraint together identify an arrangement that cannot be ethically sustained.
Other people involved in the case but not central to the opening narrative.
Tension between City-Retained Inspection Engineer Private Developer Dual-Service Prohibition Obligation and Developer-Compensated Public Inspection Dual-Interest Non-Acceptance Constraint
Firm A simultaneously owes undivided faithful agency to the City as its inspection client and a duty of objectivity to the developer client it is also serving. These duties are structurally incompatible: the City's interest is rigorous, arms-length inspection enforcement, while the developer's interest is expedient approval and cost minimization. Any inspection judgment Firm A renders is shadowed by a financial incentive to satisfy the developer, making genuine fidelity to the City logically impossible to guarantee. Fulfilling one obligation fully necessarily degrades the other — the engineer cannot be both a zealous city agent and an objective developer advisor on the same regulated project.
Firm A's obligation to proactively disclose its developer-client conflict to the City stands in direct tension with its apparent business strategy of advertising 50% cost savings to developers — a marketing claim that is only credible if Firm A exploits its insider position as the City's inspection engineer to promise reduced scrutiny or streamlined approvals. Fulfilling the disclosure obligation would expose and terminate the very commercial arrangement that makes the 50% savings claim viable. Conversely, sustaining the marketing strategy requires concealing or downplaying the conflict from the City, directly violating the disclosure duty. This tension reveals that the firm's competitive method is structurally dependent on non-disclosure.
The obligation to hold City infrastructure standards as paramount in every inspection decision is placed under structural pressure by the fact that the developer — the regulated party — is also paying Firm A fees for private services. The fee-payment relationship creates a financial dependency that the constraint recognizes as inherently corrosive to impartiality. Even if the engineer intends to uphold standards, the economic reality that a failed inspection or enforcement action harms a paying client creates a systematic bias risk. The tension is not merely hypothetical: the constraint exists precisely because the payment structure makes impartial standard primacy unreliable, meaning the obligation and the constraint together identify an arrangement that cannot be ethically sustained.
Tension between Firm A Dual-Service Private Developer Prohibition and Firm A Developer Client Conflict Proactive Disclosure to City
Firm A simultaneously owes undivided faithful agency to the City as its inspection client and a duty of objectivity to the developer client it is also serving. These duties are structurally incompatible: the City's interest is rigorous, arms-length inspection enforcement, while the developer's interest is expedient approval and cost minimization. Any inspection judgment Firm A renders is shadowed by a financial incentive to satisfy the developer, making genuine fidelity to the City logically impossible to guarantee. Fulfilling one obligation fully necessarily degrades the other — the engineer cannot be both a zealous city agent and an objective developer advisor on the same regulated project.
Firm A's obligation to proactively disclose its developer-client conflict to the City stands in direct tension with its apparent business strategy of advertising 50% cost savings to developers — a marketing claim that is only credible if Firm A exploits its insider position as the City's inspection engineer to promise reduced scrutiny or streamlined approvals. Fulfilling the disclosure obligation would expose and terminate the very commercial arrangement that makes the 50% savings claim viable. Conversely, sustaining the marketing strategy requires concealing or downplaying the conflict from the City, directly violating the disclosure duty. This tension reveals that the firm's competitive method is structurally dependent on non-disclosure.
The obligation to hold City infrastructure standards as paramount in every inspection decision is placed under structural pressure by the fact that the developer — the regulated party — is also paying Firm A fees for private services. The fee-payment relationship creates a financial dependency that the constraint recognizes as inherently corrosive to impartiality. Even if the engineer intends to uphold standards, the economic reality that a failed inspection or enforcement action harms a paying client creates a systematic bias risk. The tension is not merely hypothetical: the constraint exists precisely because the payment structure makes impartial standard primacy unreliable, meaning the obligation and the constraint together identify an arrangement that cannot be ethically sustained.
Show 2 other tensions
These tensions did not map cleanly to a single character.
Tension between City-Retained Inspection Engineer Developer Client Inspection Objectivity Preservation Obligation and City-Retained Inspection Engineer Competitive Fairness Non-Exploitation Obligation
Tension between Review-Recommendation Non-Decision Dual-Role Permissibility Boundary Obligation and Inspection Quality Non-Subordination to Developer Approval Incentive Obligation
Opening States (10)
Summary
- A firm's deliberate marketing of a public inspection role as a cost-reduction tool for private developer clients constitutes an independent ethics violation, separate from any actual conflict of interest that may or may not materialize.
- The structural arrangement of being compensated by a developer while simultaneously serving as the city's inspection engineer creates an irreconcilable dual-interest problem that cannot be resolved through disclosure alone.
- Public engineering roles carry an inherent obligation to competitive fairness that prohibits leveraging governmental authority or access to attract private clients, even when no explicit quid pro quo is demonstrated.