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 ExtractionAll provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.
-
Firm A Faithful Agent Duty to City
This provision restricts participation in decisions involving services the engineer provides, directly shaping the faithful agent duty to the city.
-
Firm A Faithful Agent Duty
The conflict of interest rule governs how Firm A must balance city and developer interests without improper influence.
-
Firm A Proper Solicitation Duty
The prohibition on participating in decisions about self-solicited services relates to how Firm A must ethically solicit developer clients.
-
Dual Client Engagement
This provision prohibits engineers from serving both public and private clients in conflicting roles
-
Dual Position Marketing
Marketing dual city engineer and inspection services violates the prohibition on conflicting roles
-
Abstention from Deliberation
The provision requires abstention from decisions involving services the engineer provides
-
Violation Determination
The finding of violation is based on the conflict of interest this provision prohibits
-
Precedent Conflict Finding
This precedent directly interprets and applies the conflict of interest prohibition
-
Precedent Abstention Ruling
This precedent enforces the abstention requirement from the provision
-
Precedent Permissive Ruling
This precedent addresses the boundaries of when dual service is permissible under the provision
-
Precedent Decisions Ruling
This precedent governs decision making conduct restricted by the provision
-
Firm A Dual Service Conflict
This provision directly prohibits the dual role conflict of serving as both city engineer and inspection provider
-
Firm A Section II.4.d Violation
This entity explicitly names the violation of this provision
-
Firm A Marketing Position Advantage
The provision addresses using public position to gain advantage in soliciting private engineering work
-
Firm A Cross Client Compensation
The provision covers conflicts arising from being compensated by multiple parties in decisions involving public duties
-
Firm A Inadequate Service Risk
The provision aims to prevent compromised service quality resulting from conflicting roles
-
Firm A Dual Service Decision Limit
This provision directly prohibits Firm A from participating in city decisions on services it provides.
-
Firm A Multiple Client Representation Limit
The provision restricts engineers from reviewing work they or their organization also prepared for private clients.
-
Firm A Official Position Marketing Limit
The provision prevents leveraging a public role for private engineering solicitation.
-
Firm A Inspection Purpose Limit
The provision limits the scope of public service duties to avoid conflicts with private engineering interests.
-
Firm A Cross Client Compensation Limit
The provision addresses conflicts arising from serving one client while being compensated by another.
-
Loyalty in Dual City Developer Service
This provision directly addresses the prohibition on participating in decisions involving services the engineer provides both publicly and privately.
-
Conflict of Interest in Dual Client Service
This provision addresses the conflict of preparing and reviewing drawings for both city and developer roles.
-
Client Best Interest Loyalty
This provision relates to the inability to serve dual roles without compromising public service duties.
-
Proper Solicitation in City Engineer Marketing
This provision restricts engineers from leveraging public roles to influence private business decisions.
-
Proper Solicitation via City Position
This provision prohibits using a public engineering role to solicit or influence private engineering services.
-
Firm A City Engineer
This role acts as an employee of a governmental body while also providing private engineering services subject to its own review
-
Firm A Private Developer Consultant
This role provides private engineering services that are then reviewed by the same firm acting as city engineer
-
Conflict of Interest Emergence
This provision directly prohibits the dual role that creates the conflict of interest
-
Cross-Compensation Activation
The provision addresses engineers participating in decisions on services they provide, which relates to receiving compensation from both roles
-
BER Case 62-7
This case addresses an engineer participating in decisions involving both public commission duties and private developer services.
-
BER Case 74-2
This case examines whether a municipal engineer can also provide consulting services to the same municipality without conflict.
-
BER Case 82-4
This case directly evaluates whether dual public and private roles constitute prohibited participation in decisions.
-
BER Case 75-7
This case involves a commission member abstaining from votes to avoid participating in decisions affecting private clients.
-
BER Case 67-12
This case involves a county engineer avoiding recommending approval of plans submitted in his private consulting role.
-
Firm A Design Review
Firm A acts as city engineer reviewing developer drawings which creates a conflict when it also serves those developers.
-
Firm A Construction Inspection
Firm A inspects infrastructure on the city's behalf while potentially having a private interest in the same projects.
-
Firm A Developer Design Services
Firm A provides private design services to developers whose projects it also reviews and inspects for the city, violating the prohibition on participating in decisions involving services it provides.
-
Firm A Faithful Agent Duty to City
Compliance with registration laws underlies the legitimacy of Firm A's engineering practice for the city.
-
Developers Plan Submission Duty
Plan submission under local ordinance requires adherence to state registration laws governing engineering practice.
-
Consultant Retention
Retaining a consultant must conform with state registration laws governing engineering practice
-
Land Development Ordinance Requirements
This provision requires conformance with state and local registration and practice laws such as land development ordinances
-
Firm A City Engineer
As a practicing engineer performing city engineering duties it must conform to state registration laws
-
Firm A Private Developer Consultant
As a practicing engineer offering design and inspection services it must conform to state registration laws
-
Firm A Design Review
Reviewing engineering drawings under city ordinance requires conformance with state registration and practice laws.
-
Firm A Construction Inspection
Providing inspection services as engineer of record requires adherence to state engineering registration laws.
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:
Where an engineer serves as a consultant (not a bona fide employee) municipal engineer under a state mandate, providing engineering services to that same municipality is not necessarily unethical, as public interest is served by acquiring competent engineering services.
Citation Context:
Cited as a contrasting precedent where a municipal engineer required by state law was found not to be a bona fide employee but a consultant, so it was not unethical for him to also provide consulting services to the municipality.
Principle Established:
An engineer who passes judgment on behalf of a public client on work or contracts in which he himself participated has divided loyalties and a conflict of interest exists, regardless of good intentions.
Citation Context:
Cited as an example where an engineer serving as county commission's consultant also performed private design work for a developer negotiating with that commission, creating a conflict of interest.
Principle Established:
An engineer who serves as both city and county engineer for a retainer fee may provide private engineering consulting services to the city and county if his role involves reviewing, recommending, and overseeing rather than making binding 'decisions,' and he takes no action to influence outcomes.
Citation Context:
Cited to illustrate that under the amended Code, an engineer serving as both city and county engineer who merely reviews, recommends, and oversees plans (without making binding 'decisions') and who took no action to influence decisions, does not violate the conflict of interest provision.
Principle Established:
An engineer serving on a commission may ethically provide private services to owners before that commission if he abstains from discussion and voting and takes no action to influence a favorable decision.
Citation Context:
Cited to address whether an engineer serving on a local board/commission could provide private services to that board, concluding it was ethical because the engineer abstained from discussion and voting on relevant matters.
Principle Established:
When an engineer serves as part-time county engineer and also as a private consultant submitting plans for county approval, he should not offer any recommendation for their approval, since an engineer will not submit work he does not believe serves his client's best interests.
Citation Context:
Cited to support the principle that an engineer acting as part-time county engineer should not offer approval recommendations on plans he submitted in his private capacity, since doing so would be a useless and self-serving act.
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 (3)
Does Firm A's practice of marketing its inspection services at a discount specifically because of its city engineer role constitute improper solicitation of business, independent of the dual-service conflict itself?
Can developers actually receive inspection services that protect their own interests when the same firm's inspection role is defined by ordinance solely to verify compliance with the city's design standards?
Should the city's ordinance structure itself be reconsidered, given that it channels developers into paying the very firm that also serves as the city's gatekeeper, effectively eliminating developer choice of inspector?
Principle tension (3)
How should Conflict of Interest in Dual Client Service be balanced against Client Best Interest Loyalty when the same firm must simultaneously enforce the city's standards and protect the developer's separate interests?
Does Proper Solicitation via City Position inherently conflict with Proper Solicitation in City Engineer Marketing, given that Firm A openly uses its public role to advertise discounted private services?
How should Loyalty in Dual City Developer Service be reconciled with the Conflict of Interest in Dual Client Service when Firm A's obligations to the city and to developers are structurally opposed by the ordinance itself?
Theoretical (3)
From a deontological perspective, did Engineer A fulfill their duty as a faithful agent to the City when simultaneously serving as a paid consultant to private developers regulated by that same city?
Did the fact that developers received competent inspection services and infrastructure met city standards justify Firm A's dual-client arrangement, even though the arrangement created a structural conflict of interest?
Did Engineer A act with professional integrity in advertising a 50% cost savings to private developers based on the firm's official city position, or does this reveal a character failing in prioritizing self-interest over impartial public service?
Counterfactual (3)
If Firm A had not marketed its position as city engineer to private developers or advertised a 50% cost savings on inspection services, would the Board still have concluded that the dual-service arrangement was unethical?
If Firm A provided only city engineering services and did not also offer design and inspection services to private developers within the city, would the Board still find a conflict of interest under Section II.4.d?
If the local ordinance had not required developers to pay separately for inspection services to protect their own interests, would the Board's finding that Firm A's dual role created a conflict of interest still hold?
Analytical questions (1)
Questions the analysis generates beyond the board’s explicit questions: implicit issues, principle tensions, theoretical framings, and counterfactuals. A question with an identified source board question appears nested under that question above.
Show 1 analytical questionImplicit (1)
Does Firm A's cross-client compensation arrangement, where developers effectively subsidize services tied to the firm's public role, create a hidden financial dependency that compromises its faithful agent duty to the city?
Decisions & Arguments (4)
View ExtractionShould Engineer A accept and continue dual employment as both city engineer and paid private consultant to developers within the same jurisdiction?
Engineer A held the official city engineer position responsible for verifying developer compliance with city design standards, while Firm A also contracted directly with those same developers for paid review and inspection services.
An engineer acting as a faithful agent for one principal must not simultaneously accept compensation from a second principal whose interests may be adverse to the first, absent full disclosure and consent.
Would not apply if Engineer A had obtained express informed consent from both the city and each developer to the dual arrangement, or if competent outcomes were treated as sufficient, but the Board rejected outcome-based justification.
Should Firm A market a discounted inspection rate to developers by explicitly citing its city engineer role as the basis for the savings?
Firm A explicitly marketed a 50 percent cost savings on inspection services to developers, stating the savings derived from its position as city engineer.
Engineers must not use a public position or privileged access gained through public office to secure unfair commercial advantage over competitors in private practice.
Would not apply if the cost savings arose from genuine efficiencies unrelated to the public role rather than from leveraging the office itself, but the case shows the savings was explicitly tied to the city position.
Should the city ordinance combine compliance verification and developer inspection in the city engineer's role, or structurally separate them to preserve developer choice?
The ordinance defines Firm A's inspection role solely as verification of compliance with city design standards, yet developers must pay Firm A for this inspection with no alternative inspector available, despite the ordinance's stated purpose of protecting developer interests.
Public bodies must design regulatory structures that avoid creating unavoidable conflicts of interest and must not represent a service as protecting a party's interests when the structure cannot deliver that protection.
Would not apply if developers were clearly informed that inspection served only city compliance interests and a separate mechanism existed for protecting their private interests, but no such mechanism or disclosure is shown in the case.
Should Firm A accept compensation from developers that is structurally tied to its city engineer role, creating financial dependency on the regulated parties?
A significant portion of Firm A's revenue derived from developer payments tied to its city-engineer role under the ordinance's cross-compensation activation, rather than from independent city funding.
An engineer serving as a public agent must not accept a compensation structure that makes the agent financially dependent on the party being regulated, since this risks compromising impartial judgment owed to the principal.
Would not apply if developer payments were structured through a neutral escrow or city-administered fund that eliminated any direct financial relationship or incentive between Firm A and individual developers.
Event Timeline (13)
Case timeline
- Section II.4.d Conflict of Interest Prohibition
- Duty to Represent the Best Interest of Clients
- Section II.4.d Conflict of Interest Prohibition
- began: Firm A Dual Service Conflict
- began: Firm A Cross Client Compensation
- Duty to Represent the Best Interest of Clients
- began: Firm A Inadequate Service Risk
- began: Firm A Dual Service Conflict
- began: Firm A Section II.4.d Violation
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 Firm A, a private consulting engineering firm retained by the city to provide design review and construction inspection services for land development projects. Under the city's land development ordinance, private developers submitting plans for approval must pay the city's costs for having you review their drawings, and during construction they must also pay for inspection services performed by your firm on the city's behalf. The ordinance specifies that these city-side inspection services exist solely to confirm that infrastructure being built for eventual turnover to the city meets municipal design standards, and that developers must arrange separate inspection if they want their own interests protected. At the same time, your firm independently markets design and inspection services directly to developers working within the same city, and your sales approach openly tells prospective clients they can cut inspection costs by 50 percent by hiring your firm, since you already function as the city engineer. Decisions about how this dual role is structured, marketed, and compensated are now in front of you.
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.
Firm A owes a faithful agent duty to the developer as its private consulting client, but the constraint limiting inspections to their proper regulatory purpose means the firm cannot use its inspection role to advance the developer's private interests or shortcut the City's review requirements. Trying to satisfy the developer's expectations of favorable treatment while honoring the inspection purpose limit creates a direct role conflict for the same individuals performing both functions.
Firm A's duty to serve the City faithfully as its engineer is undermined when the firm simultaneously represents private developers whose projects fall under the City's regulatory review. The firm cannot fully serve the City's interest in impartial oversight while also being paid to advance a developer's interest in expedited or favorable review, so the multiple client representation limit directly cuts against the faithful agent duty owed to the City.
The obligation to solicit private consulting work through proper, ethical channels is in tension with the practical reality that Firm A's standing as the City Engineer gives it privileged access and credibility with developers seeking approvals. Even without explicit intent, the firm's official position functions as an implicit marketing tool, so satisfying the proper solicitation duty requires actively resisting the leverage the official role naturally provides, which the marketing limit constraint exists to prevent.
Firm A owes a faithful agent duty to the developer as its private consulting client, but the constraint limiting inspections to their proper regulatory purpose means the firm cannot use its inspection role to advance the developer's private interests or shortcut the City's review requirements. Trying to satisfy the developer's expectations of favorable treatment while honoring the inspection purpose limit creates a direct role conflict for the same individuals performing both functions.
Firm A's duty to serve the City faithfully as its engineer is undermined when the firm simultaneously represents private developers whose projects fall under the City's regulatory review. The firm cannot fully serve the City's interest in impartial oversight while also being paid to advance a developer's interest in expedited or favorable review, so the multiple client representation limit directly cuts against the faithful agent duty owed to the City.
The obligation to solicit private consulting work through proper, ethical channels is in tension with the practical reality that Firm A's standing as the City Engineer gives it privileged access and credibility with developers seeking approvals. Even without explicit intent, the firm's official position functions as an implicit marketing tool, so satisfying the proper solicitation duty requires actively resisting the leverage the official role naturally provides, which the marketing limit constraint exists to prevent.
Other people involved in the case but not central to the opening narrative.
Firm A owes a faithful agent duty to the developer as its private consulting client, but the constraint limiting inspections to their proper regulatory purpose means the firm cannot use its inspection role to advance the developer's private interests or shortcut the City's review requirements. Trying to satisfy the developer's expectations of favorable treatment while honoring the inspection purpose limit creates a direct role conflict for the same individuals performing both functions.
Firm A's duty to serve the City faithfully as its engineer is undermined when the firm simultaneously represents private developers whose projects fall under the City's regulatory review. The firm cannot fully serve the City's interest in impartial oversight while also being paid to advance a developer's interest in expedited or favorable review, so the multiple client representation limit directly cuts against the faithful agent duty owed to the City.
The obligation to solicit private consulting work through proper, ethical channels is in tension with the practical reality that Firm A's standing as the City Engineer gives it privileged access and credibility with developers seeking approvals. Even without explicit intent, the firm's official position functions as an implicit marketing tool, so satisfying the proper solicitation duty requires actively resisting the leverage the official role naturally provides, which the marketing limit constraint exists to prevent.
The Board’s deliberation
How the Board of Ethical Review resolved the case, verbatim from its published conclusions.
Opening States (6)
Summary
- Serving as a public agency's engineer while also consulting for private parties regulated by that same agency creates an unavoidable conflict of interest, regardless of the individual engineer's good intentions.
- Holding an official regulatory position inherently generates marketing leverage with regulated parties, so simply avoiding explicit solicitation does not eliminate the appearance or reality of using public office for private gain.
- When a single role requires simultaneously advancing a private client's interests and impartially enforcing public oversight, no amount of internal separation or good faith can fully reconcile the two duties, making the dual role itself the ethical defect rather than any specific act within it.