Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Conflict of Interest—Peer Reviewer Participating on Subsequent Joint Venture
Step 4 of 5

136

Entities

5

Provisions

2

Precedents

15

Questions

10

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's peer-review-era duty of objectivity/confidentiality is discharged and effectively transferred to the State Agency, which absorbs the fairness-guaranteeing function by publishing the review's substantive findings in the RFP and by exercising procurement-level approval authority over ABC Engineering's later participation as a commercial bidder.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The 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.

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (5)
View Extraction

All 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.

II.4 board + analysis Engineers shall act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 14)
Obligation
ABC Engineering Faithful Agent Duty
ABC Engineering must act as a faithful agent to the state agency during the peer review
Action
Joint Venture Participation Decision
Engineer must act as faithful agent when deciding to join the venture after peer review work
State
Confidential Information Advantage
Faithful agency is compromised when confidential information from prior work gives advantage in a new role
Obligation (2)
  • ABC Engineering Faithful Agent Duty
    ABC Engineering must act as a faithful agent to the state agency during the peer review
  • Engineer A Peer Review Objectivity Duty
    Engineer A must act as a faithful agent by conducting the review independently and objectively
Action (2)
  • Joint Venture Participation Decision
    Engineer must act as faithful agent when deciding to join the venture after peer review work
  • Lead Reviewer Role Acceptance
    Accepting the reviewer role requires faithful agency to the original client
State (2)
  • Confidential Information Advantage
    Faithful agency is compromised when confidential information from prior work gives advantage in a new role
  • Pending Joint Venture Invitation
    Acting as faithful agent requires evaluating whether joining the venture breaches trust owed to prior client
Constraint (1)
  • Engineer A Peer Review Nondisclosure
    Acting as a faithful agent requires Engineer A to keep the reviewed agency's confidential information protected
Principle (1)
  • Conflict of Interest in Design-Build Venture
    Acting as a faithful agent is compromised when the peer reviewer later joins the venture it reviewed
Role (2)
  • Engineer A Lead Peer Review Engineer
    Must act as a faithful agent to the state agency and later to XYZ Construction as clients.
  • ABC Engineering Provider Firm
    As the retained firm it owes trustee duties to its clients including the state agency.
Event (1)
  • Information Advantage Emergence
    Faithful agency duty is compromised when insider information creates an advantage for subsequent work
Resource (1)
  • BER Case 94-5
    The city engineer conflict involves failing to act solely as a faithful agent for the city.
Capability (2)
  • Engineer A Review Objectivity Maintenance
    Acting as a faithful agent requires maintaining independence and objectivity during the peer review
  • Engineer A Confidentiality Judgment
    Faithful agency requires proper handling of confidential information gained during service
II.4.a board + analysis Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services.
How this applies in the case (showing 3 of 17)
Obligation
ABC Engineering Faithful Agent Duty
ABC Engineering must disclose any conflicts of interest that could affect its objectivity as reviewer
Action
Joint Venture Invitation
Receiving the invitation creates a potential conflict that must be disclosed
State
No Confidentiality Agreement On Project
Absence of a confidentiality agreement does not remove the duty to disclose potential conflicts
Obligation (2)
  • ABC Engineering Faithful Agent Duty
    ABC Engineering must disclose any conflicts of interest that could affect its objectivity as reviewer
  • Engineer A Peer Review Objectivity Duty
    Engineer A must disclose any known or potential conflicts that could influence the peer review
Action (2)
  • Joint Venture Invitation
    Receiving the invitation creates a potential conflict that must be disclosed
  • Joint Venture Participation Decision
    Deciding to participate requires disclosure of the potential conflict of interest
State (4)
  • No Confidentiality Agreement On Project
    Absence of a confidentiality agreement does not remove the duty to disclose potential conflicts
  • Pending Joint Venture Invitation
    The engineer must disclose the potential conflict created by joining the joint venture after peer review
  • Confidential Information Advantage
    Any advantage gained from prior confidential knowledge must be disclosed to all parties
  • Peer Review Project Knowledge
    Specialized knowledge gained during peer review creates a potential conflict that must be disclosed
Constraint (1)
  • Engineer A Peer Review Nondisclosure
    Disclosure obligations relate directly to the nondisclosure duty formed during the peer review
Principle (1)
  • Conflict of Interest in Design-Build Venture
    The engineer must disclose the potential conflict arising from prior peer review involvement before joining the venture
Role (2)
  • Engineer A Lead Peer Review Engineer
    Must disclose the potential conflict arising from prior peer review work when joining the joint venture proposal.
  • ABC Engineering Provider Firm
    Must disclose its prior peer review role to XYZ Construction and the state agency before joining the joint venture.
Event (1)
  • Information Advantage Emergence
    The engineer must disclose the potential conflict arising from gaining special insight during peer review
Resource (2)
  • BER Case 96-8
    The peer reviewer must disclose potential conflicts arising from safety issues found during review.
  • BER Case 94-5
    The city engineer must disclose conflicts from serving private developers in the same city.
Capability (2)
  • Engineer A Review Objectivity Maintenance
    Engineer A must disclose potential conflicts that could influence his objectivity in the review
  • Board Precedent Reasoning
    The Board's reasoning addresses disclosure of conflicts based on prior case precedents
II.4.b board + analysis Engineers shall not accept compensation, financial or otherwise, from more than one party for services on the same project, or for services pertaining to the same project, unless the circumstances are fully disclosed and agreed to by all interested parties.
How this applies in the case (showing 3 of 12)
Obligation
ABC Engineering Faithful Agent Duty
ABC Engineering cannot accept compensation from another party on the same project without disclosure and consent
Action
Joint Venture Participation Decision
Accepting compensation from the joint venture after being paid for peer review requires disclosure and consent
State
Pending Joint Venture Invitation
Receiving compensation from a new joint venture on a related project requires disclosure and consent of all parties
Obligation (1)
  • ABC Engineering Faithful Agent Duty
    ABC Engineering cannot accept compensation from another party on the same project without disclosure and consent
Action (1)
  • Joint Venture Participation Decision
    Accepting compensation from the joint venture after being paid for peer review requires disclosure and consent
State (2)
  • Pending Joint Venture Invitation
    Receiving compensation from a new joint venture on a related project requires disclosure and consent of all parties
  • Post Peer Review Phase
    Compensation for subsequent work related to the same project requires disclosure to prior and new parties
Constraint (1)
  • Engineer A Peer Review Nondisclosure
    Compensation from multiple parties on the same project could conflict with the confidentiality obligation from the peer review
Principle (1)
  • Conflict of Interest in Design-Build Venture
    Receiving compensation from both the peer review role and the later joint venture on the same project creates a prohibited dual compensation situation
Role (2)
  • Engineer A Lead Peer Review Engineer
    Cannot accept compensation from both the state agency and XYZ Construction on the same project without full disclosure and consent.
  • ABC Engineering Provider Firm
    Cannot accept compensation from both the state agency and XYZ Construction for related project services without disclosure and agreement.
Event (1)
  • Review Findings Incorporation
    Accepting compensation from a joint venture based on findings developed during paid peer review creates dual compensation on the same project
Resource (1)
  • BER Case 94-5
    The firm accepting compensation from both the city and private developers on related projects raises this issue.
Capability (2)
  • Engineer A Review Objectivity Maintenance
    Accepting compensation from a subsequent related party on the same project requires disclosure and agreement
  • Board Precedent Reasoning
    The multiple-client conflict rationale from prior cases directly relates to compensation from multiple parties on the same project
II.4.d board + analysis Engineers in public service as members, advisors, or employees of a governmental or quasi-governmental body or department shall not participate in decisions with respect to services solicited or provided by them or their organizations in private or public engineering practice.
How this applies in the case (showing 3 of 4)
State
Limited Scope Peer Review
Engineers serving in a review capacity must not later participate in decisions related to that same review
Principle
Conflict of Interest in Design-Build Venture
Participation in decisions related to a project the engineer previously reviewed mirrors the prohibition on public service conflicts
Role
State Agency Procurement Authority
Governs the agency's obligation not to let prior service providers improperly participate in decisions on solicited services.
State (1)
  • Limited Scope Peer Review
    Engineers serving in a review capacity must not later participate in decisions related to that same review
Principle (1)
  • Conflict of Interest in Design-Build Venture
    Participation in decisions related to a project the engineer previously reviewed mirrors the prohibition on public service conflicts
Role (1)
  • State Agency Procurement Authority
    Governs the agency's obligation not to let prior service providers improperly participate in decisions on solicited services.
Resource (1)
  • BER Case 94-5
    This provision directly addresses engineers in public service like a city engineer deciding on their own private practice matters.
III.4.a board + analysis Engineers shall not, without the consent of all interested parties, promote or arrange for new employment or practice in connection with a specific project for which the engineer has gained particular and specialized knowledge.
How this applies in the case (showing 3 of 19)
Obligation
Engineer A Peer Review Objectivity Duty
Engineer A must not arrange new employment on the same project without consent of all interested parties
Action
Joint Venture Invitation
Arranging new employment tied to the reviewed project requires consent of interested parties
State
Peer Review Project Knowledge
Specialized knowledge gained from the peer review cannot be used to arrange new employment without consent
Obligation (2)
  • Engineer A Peer Review Objectivity Duty
    Engineer A must not arrange new employment on the same project without consent of all interested parties
  • Engineer A Peer Review Confidentiality Duty
    Engineer A gained specialized knowledge during the review that constrains subsequent employment arrangements
Action (3)
  • Joint Venture Invitation
    Arranging new employment tied to the reviewed project requires consent of interested parties
  • Joint Venture Participation Decision
    Joining the venture uses specialized knowledge gained from the peer review without consent
  • Lead Reviewer Role Acceptance
    The reviewer role gave specialized knowledge later leveraged for new employment
State (3)
  • Peer Review Project Knowledge
    Specialized knowledge gained from the peer review cannot be used to arrange new employment without consent
  • Pending Joint Venture Invitation
    Arranging new practice on a related project requires consent of all interested parties
  • Confidential Information Advantage
    Using specialized project knowledge for personal advantage in new employment violates this provision without consent
Constraint (1)
  • Engineer A Peer Review Nondisclosure
    Using specialized knowledge gained during peer review for new employment relates to the nondisclosure constraint
Principle (2)
  • Conflict of Interest in Design-Build Venture
    Arranging new employment on a project where specialized knowledge was gained during peer review requires consent of all parties
  • Confidentiality in Peer Review
    Specialized knowledge gained under confidential peer review cannot be used to arrange subsequent employment without consent
Role (3)
  • Engineer A Lead Peer Review Engineer
    Cannot arrange new employment on the same project without consent given specialized knowledge gained during peer review.
  • ABC Engineering Provider Firm
    Cannot pursue new project involvement without consent of all parties due to specialized knowledge from the peer review engagement.
  • XYZ Construction Contractor
    Seeks to engage ABC Engineering for the same project, implicating consent requirements under this provision.
Event (2)
  • Peer Review Completion
    The engineer must not use specialized knowledge gained from the peer review to arrange subsequent employment without consent
  • Information Advantage Emergence
    The specialized knowledge gained creates an unfair advantage for pursuing the joint venture without consent of interested parties
Resource (1)
  • BER Case 96-8
    The peer reviewer later joining a venture using specialized knowledge from the review matches this provision.
Capability (2)
  • Engineer A Confidentiality Judgment
    Arranging new employment using specialized knowledge gained from the project requires consent of interested parties
  • Board Precedent Reasoning
    The confidentiality rationale from Case 96-8 relates to restrictions on subsequent employment involving specialized project knowledge
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 2 Lineage Graph

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

A peer reviewer who discovers work that may violate safety codes and endanger public health, safety, and welfare must first attempt to resolve the issue with the reviewed engineer, and if unresolved, must notify the proper authorities.

Citation Context:

Cited to illustrate the principle of confidentiality in peer-review programs and the appropriate steps a peer reviewer must take upon discovering safety violations, though it is distinguished from the present facts where no confidentiality agreement existed.

Relevant Excerpts
discussion: "This principle was illustrated in BER Case 96-8. In this case, Engineer A served as a peer reviewer as part of an organized peer-review program developed to assist engineers in improving their professional practice."

Principle Established:

An engineer or firm cannot ethically serve multiple, potentially conflicting interests (e.g., a city and private developers) simultaneously, as this compromises the ability to adequately represent each client's separate interests.

Citation Context:

Cited to address the potential for conflicts of interest when an engineer serves multiple parties with differing interests, but distinguished because the current case does not present the same multi-client conflict.

Relevant Excerpts
discussion: "In BER Case 94-5, a city engaged the services of a private consulting engineering firm, Firm A, to provide design review and construction inspection."
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 59% Facts Similarity 56% Discussion Similarity 44% Outcome Alignment 100% Tag Overlap 75% Principle Overlap 70%
Same outcome unethical View Synthesis
Component Similarity 56% Facts Similarity 59% Discussion Similarity 42% Outcome Alignment 100% Tag Overlap 75% Principle Overlap 67%
Same outcome unethical View Synthesis
Component Similarity 55% Facts Similarity 60% Discussion Similarity 38% Outcome Alignment 100% Tag Overlap 40% Principle Overlap 67%
Same outcome unethical View Synthesis
Component Similarity 58% Facts Similarity 65% Discussion Similarity 47% Outcome Alignment 100% Tag Overlap 22% Principle Overlap 68%
Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 58% Discussion Similarity 39% Outcome Alignment 100% Tag Overlap 40% Principle Overlap 67%
Same outcome unethical View Synthesis
Component Similarity 53% Facts Similarity 55% Discussion Similarity 42% Outcome Alignment 100% Tag Overlap 14% Principle Overlap 70%
Same outcome unethical View Synthesis
Component Similarity 54% Facts Similarity 56% Discussion Similarity 33% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 51%
Same outcome unethical View Synthesis
Component Similarity 51% Facts Similarity 57% Discussion Similarity 40% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 54%
Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 58% Discussion Similarity 41% Outcome Alignment 100% Tag Overlap 22% Principle Overlap 55%
Same outcome unethical View Synthesis
Component Similarity 48% Facts Similarity 46% Discussion Similarity 31% Outcome Alignment 100% Tag Overlap 20% Principle Overlap 71%
Same outcome unethical View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

Would it be ethical for Engineer A and his firm, ABC Engineering, to participate in a design-build joint venture and submit a proposal for the major road transportation project?

Board conclusion It would not be unethical for Engineer A and his firm ABC Engineering to participate in a design-build joint venture and submit a proposal for the major road transportation project, as long as the state agency approves and the work complies with state laws and regulations.
Resolved by: The Board weighed ABC Engineering's faithful agent duty to the state agency against its commercial interest in the joint venture, and found the conflict resolved because the informational advantage was neutralized by public disclosure through the RFP. (confidence 0.50)
II.4.a. II.4.d. III.4.a. 2 principles 3 facts Conditions Narrative
Implicit (4)

Does Engineer A's prior access to detailed knowledge of the transportation project's design during the peer review create an unfair informational advantage for ABC Engineering in the design-build proposal, even though no formal confidentiality agreement existed?

AnalyticalThe Board's conclusion that ABC Engineering may ethically join the design-build joint venture rests heavily on the fact that the peer review's findings were incorporated into the publicly issued RFP, which effectively converts Engineer A's prior insider knowledge into information equally available to all bidders. This suggests the real safeguard against unfair advantage is not the absence of a confidentiality agreement or the passage of time, but rather the degree to which the peer review's substantive content became part of the public record before competitors were asked to bid. Any residual advantage would stem not from confidential information but from Engineer A's deeper contextual familiarity with the underlying design rationale and clarifications, which competitors reviewing only the RFP would lack.
Resolved by: The Board implicitly weighed the risk of informational advantage against the fact that public incorporation of findings equalized access, treating disclosure to all bidders as outweighing residual contextual knowledge. (confidence 0.50)
II.4.a. 2 principles 3 facts Conditions Narrative
AnalyticalBecause the peer review was expressly limited in scope to clarifications and refinements of existing plans, rather than a full independent assessment of the design, Engineer A's exposure to project information was bounded and largely duplicative of what any competent bidder could glean from the RFP itself, which incorporated those same clarifications. This limits the informational advantage that might otherwise justify treating ABC Engineering's later participation as a conflict of interest, even absent a formal confidentiality agreement.
Resolved by: The Board weighed the scope of Engineer A's exposure to project information against the informational baseline available to all bidders via the RFP, concluding the advantage was bounded and largely duplicative. (confidence 0.50)
II.4.a. 2 principles 3 facts Conditions Narrative

Should the state agency be required to explicitly evaluate and approve ABC Engineering's participation in the joint venture before the RFP process proceeds, rather than the ethical propriety resting on the agency's implicit consent?

AnalyticalThe Board's finding is conditioned on state agency approval and compliance with state law, but the Board does not specify what affirmative steps the agency should take to confirm that no unfair advantage exists before approving ABC Engineering's participation. A more complete ethical framework would require ABC Engineering to proactively disclose its prior peer review role to the agency and to competing bidders (consistent with II.4.a.'s disclosure duty), and would require the agency to make an explicit, documented determination -- rather than relying on implicit or passive consent -- that ABC Engineering's earlier involvement does not compromise the fairness of the design-build competition.
Resolved by: The Board balanced procedural completeness against practical brevity, favoring a conditional approval standard over a detailed disclosure and verification protocol. (confidence 0.50)
II.4.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C302

Does the one-year gap between completion of the peer review and issuance of the RFP meaningfully reduce any conflict of interest concern, or is the underlying informational advantage unaffected by the passage of time?

AnalyticalThe one-year gap between completion of the peer review and issuance of the RFP does not, by itself, cure any informational advantage Engineer A may have possessed, since the technical content of a limited-scope peer review does not meaningfully degrade over such a short period. What matters more than elapsed time is whether the peer review findings were fully disclosed to all subsequent bidders through incorporation into the public RFP, which appears to have neutralized any residual advantage regardless of the time elapsed.
Resolved by: The board subordinated the temporal-distance argument to the disclosure argument, treating elapsed time alone as insufficient to cure an informational advantage while treating full public disclosure as sufficient regardless of timing. (confidence 0.75)
II.4.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C101

How should the fact that peer review findings were directly incorporated into the RFP specifications affect the ethical analysis of ABC Engineering later bidding on the resulting design-build work?

AnalyticalThe fact that peer review findings were directly incorporated into the RFP specifications is ethically significant: it converts what might have been private, asymmetric knowledge held only by Engineer A and ABC Engineering into public information equally available to all prospective design-build bidders. This transformation from private insight to public specification is likely the single most important fact underlying the Board's conclusion that no unfair advantage existed.
Resolved by: The board weighed the risk of private, asymmetric knowledge against the curative effect of public disclosure, concluding that converting review findings into public specifications outweighed the residual concern about Engineer A's prior access. (confidence 0.80)
II.4.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C101
Principle tension (4)

How should the duty of Confidentiality in Peer Review be balanced against the potential Conflict of Interest in Design-Build Venture when Engineer A transitions from an independent, objective reviewer to a self-interested competitor on the same project?

AnalyticalThe Board effectively resolved the tension between Confidentiality in Peer Review and Conflict of Interest in Design-Build Venture by treating them as sequential rather than overlapping duties: because the peer review was limited in scope, produced no confidential information beyond what was ultimately made public in the RFP, and involved no formal nondisclosure agreement, Engineer A's earlier objectivity duty as reviewer was deemed fully discharged before ABC Engineering's later self-interested role as bidder began. This shows that the Board prioritizes the absence of a persisting informational or fiduciary obligation over the mere appearance of role transition, allowing a firm to move from independent reviewer to commercial competitor on the same project without an automatic conflict, provided the review's scope and outputs were effectively public.
Resolved by: The board avoided balancing the two duties concurrently by treating the objectivity duty as temporally prior and fully discharged, so the later self-interested bidder role did not have to be weighed against an ongoing confidentiality obligation. (confidence 0.75)
II.4. II.4.a. 2 principles 3 facts Conditions Narrative

Does Engineer A's Peer Review Objectivity Duty, exercised during the independent review, conflict with ABC Engineering's later pursuit of commercial self-interest through the design-build joint venture?

Also discussed in: C301

How do the requirements of II.4.d (engineers in public service avoiding conflicts) and III.4.a (consent of interested parties before new employment) interact when applied to Engineer A's shift from peer reviewer to joint-venture bidder on the same project?

AnalyticalThe Board's silence on how II.4.d. and III.4.a. interact leaves open whether Engineer A's peer review work for the state agency should be characterized as 'public service' triggering a heightened conflict-of-interest standard under II.4.d., which would then require the consent of all interested parties (including competing bidders or the agency's procurement stakeholders) under III.4.a. before Engineer A transitions to a private commercial role on the same project. Treating the peer review as ordinary client work rather than public service, as the Board implicitly does, avoids this stricter standard but is not explicitly justified in the Board's reasoning.
Resolved by: The Board implicitly weighed the heightened public-service conflict standard against an ordinary client-relationship standard, favoring the latter without explicit justification. (confidence 0.50)
II.4.d. III.4.a. 2 principles 3 facts Conditions Narrative
AnalyticalThe interaction between II.4.d (avoiding conflicts of interest in public service roles) and III.4.a (requiring consent of interested parties before pursuing new employment) is reconciled in this case by locating the safeguard not in Engineer A's individual conduct but in the state agency's procurement authority: because the agency itself issued the RFP and implicitly permits ABC Engineering's participation, the 'consent of interested parties' contemplated by III.4.a is satisfied through the agency's structural approval of the design-build process rather than through an explicit conflict-of-interest waiver tied to the peer review. This suggests that when a public procurement process is transparent and agency-controlled, it can substitute for individualized consent mechanisms, effectively subordinating III.4.a's employee-level consent requirement to II.4.d's agency-level oversight function.
Resolved by: The board subordinated III.4.a's individualized consent requirement to II.4.d's agency-level oversight function, locating the safeguard in the transparency of the procurement process rather than in a specific waiver. (confidence 0.70)
II.4.d. III.4.a. 2 principles 3 facts Conditions Narrative

Because state law on conflicts of interest varies, how should the principle of Conflict of Interest in Design-Build Venture be reconciled with jurisdictions that may impose stricter or laxer confidentiality expectations than the Confidentiality in Peer Review principle implies?

Theoretical (3)

From a deontological perspective, did Engineer A fulfill his duty of confidentiality and objectivity as a peer reviewer even though no formal confidentiality agreement existed on the project?

Also discussed in: C301

Did the ultimate outcome -- a limited-scope peer review whose findings were simply incorporated into a public RFP -- justify allowing ABC Engineering to later join a design-build proposal for the same project?

AnalyticalThis case illustrates a general prioritization rule for engineering ethics: when a peer review is narrow, incorporated transparently into a public solicitation document, and separated from subsequent bidding by a meaningful time gap, the principle of Conflict of Interest in Design-Build Venture is treated as dormant rather than triggered, effectively giving procedural transparency (public RFP incorporation) priority over abstract concerns about informational advantage. However, this prioritization is contingent -- the Board's reasoning implies that a broader-scope review, a shorter or absent time gap, or an actual confidentiality agreement would shift the balance toward finding a conflict, showing that principle prioritization here is fact-sensitive rather than categorical.
Resolved by: The board gave procedural transparency priority over abstract informational-advantage concerns only under this particular combination of facts, explicitly treating the prioritization as contingent rather than categorical. (confidence 0.80)
II.4.a. II.4.d. 2 principles 3 facts Conditions Narrative

Did Engineer A act with professional integrity in accepting the joint venture invitation, given that his prior peer review role could be perceived as giving ABC Engineering an unfair information advantage over competing bidders?

Counterfactual (3)

If a confidentiality agreement had existed governing ABC Engineering's peer review work, would the Board still have concluded that Engineer A and ABC Engineering could ethically join the design-build joint venture?

Also discussed in: C303

If the peer review had been a full, unrestricted review of the entire design (rather than a limited-scope review focused only on clarifications and refinements), would the Board still find no conflict of interest in ABC Engineering's later participation in the design-build proposal?

Also discussed in: C201 C303

If the design-build RFP had been issued immediately after (rather than approximately one year after) ABC Engineering completed the peer review, would the Board still have concluded that participation in the joint venture was not unethical?

Also discussed in: C303
Decisions & Arguments (5)
View Extraction

Should Engineer A and ABC Engineering join the design build joint venture and submit a proposal for the transportation project, or decline participation to avoid any appearance of conflict of interest?

Options considered:
O1 Engineer A and ABC Engineering accept XYZ Construction's invitation and submit a design build proposal for the project, relying on the RFP's public disclosure of peer review findings to neutralize any advantage. Board's choice
O2 Engineer A and ABC Engineering decline the joint venture invitation entirely to eliminate any appearance of conflict arising from the prior peer review role.
O3 Engineer A and ABC Engineering formally request the state agency's explicit written approval of their participation before submitting a proposal, rather than relying on implicit consent.
Argument structure (Toulmin):
Grounds

ABC Engineering completed a limited scope peer review of the agency's design; the review findings were incorporated into the publicly issued RFP approximately one year later; XYZ Construction then invited ABC Engineering to join a design build joint venture and submit a proposal.

Warrant

Engineers must avoid conflicts of interest that could compromise professional judgment, but this duty is discharged once the earlier reviewer role has fully ended and no confidential advantage persists, permitting a firm to pursue new commercial opportunities once prior fiduciary obligations to a client have been satisfied.

Rebuttal

Would not apply if the peer review had been broader in scope, if a formal confidentiality agreement restricted subsequent use of the information, or if the RFP had issued immediately after the review such that no independent public disclosure had intervened.

ABC Engineering Faithful Agent Duty Engineer A Peer Review Nondisclosure

Should ABC Engineering proactively disclose its prior peer review role to the state agency and competing bidders before joining the joint venture, or rely on the agency's implicit consent through issuance of the RFP?

Options considered:
O1 ABC Engineering formally notifies the state agency and competing bidders of its earlier peer review role and requests an explicit conflict determination before submitting a proposal. Board's choice
O2 ABC Engineering treats the agency's issuance of the RFP, which incorporated the peer review findings, as sufficient implicit consent and proceeds without separate disclosure.
O3 ABC Engineering takes no proactive disclosure action and addresses the prior peer review role only if the agency or a competing bidder specifically raises it.
Argument structure (Toulmin):
Grounds

The state agency retained ABC Engineering for the peer review; the agency later issued the RFP without any documented conflict determination; ABC Engineering was invited into the joint venture without an explicit agency review of its prior role.

Warrant

Engineers shall disclose all known or potential conflicts of interest to their clients or employers, and reliance on passive or implicit consent does not satisfy the affirmative disclosure duty owed to a client making a procurement decision.

Rebuttal

Would not apply if the agency's issuance of the RFP incorporating the peer review findings is itself treated as sufficient constructive disclosure, or if state procurement law does not require individualized conflict disclosure in design build competitions.

ABC Engineering Faithful Agent Duty Engineer A Peer Review Nondisclosure

Should Engineer A refrain from using any residual knowledge gained during the peer review in preparing the joint venture proposal, or may he rely on that knowledge because its substance was incorporated into the public RFP?

Options considered:
O1 Engineer A limits his proposal preparation to information contained in the public RFP, treating peer review derived knowledge as fully absorbed into that public document. Board's choice
O2 Engineer A deliberately excludes any contextual insight from the peer review beyond what is stated in the RFP, erring on the side of strict confidentiality.
O3 Engineer A uses his deeper contextual familiarity with the design rationale gained during the peer review, beyond what is stated in the RFP, to strengthen the joint venture's proposal.
Argument structure (Toulmin):
Grounds

The peer review was limited in scope to clarifications and refinements of existing plans; its findings were incorporated into the RFP; the RFP was issued to all prospective bidders approximately one year after the review's completion; no formal confidentiality agreement governed the review.

Warrant

Engineers must protect confidential, nonpublic client information gained in a position of trust, but this duty dissolves once the information has been made public through the client's own disclosure, since no continuing informational asymmetry remains to protect.

Rebuttal

Would not apply if the review had been full and unrestricted rather than limited in scope, since broader access to design details would generate a more substantial and less deniable informational advantage not fully captured by the RFP's public disclosures.

Engineer A Peer Review Confidentiality Duty Engineer A Peer Review Nondisclosure

Should Engineer A treat his peer review work for the state agency as public service requiring the consent of all interested parties before pursuing the joint venture, or as ordinary private client work not subject to that heightened standard?

Options considered:
O1 Engineer A proceeds on the understanding that the peer review was a private contractual engagement, not public service, so no special consent under III.4.a is required before joining the joint venture. Board's choice
O2 Engineer A seeks the consent of all interested parties, including the agency and competing bidders, before joining the joint venture, on the view that the peer review constituted public service under II.4.d.
O3 Engineer A asks the state agency to formally classify the peer review engagement as either public service or private consulting before deciding whether III.4.a consent is required.
Argument structure (Toulmin):
Grounds

ABC Engineering was retained directly by the state agency under a private contract to perform an independent external peer review of limited scope; Engineer A served as lead reviewer; he later accepted an invitation from XYZ Construction to join a design build joint venture on the same project.

Warrant

Engineers in public service must avoid conflicts of interest under II.4.d, and III.4.a requires consent of interested parties before accepting new employment that could conflict with prior duties, but these heightened standards apply specifically to engineers occupying public service roles rather than private contractors retained on a fee basis.

Rebuttal

Would not apply if the peer review role is properly characterized as public service because Engineer A acted on behalf of the state agency in a quasi regulatory oversight capacity, in which case III.4.a's consent requirement would attach and the Board's silence on this classification would leave the analysis incomplete.

Engineer A Peer Review Objectivity Duty

Should ABC Engineering wait until the peer review findings have been publicly disclosed before joining the design build joint venture, or may it join immediately regardless of timing?

Options considered:
O1 ABC Engineering joins the joint venture only after the agency has publicly issued the RFP incorporating the peer review findings, ensuring competitors have equal access to that information. Board's choice
O2 ABC Engineering accepts the joint venture invitation immediately upon completing the peer review, without waiting for public disclosure of the review's findings.
O3 ABC Engineering adopts a policy of waiting a fixed period of time, such as one year, after any peer review engagement before pursuing related commercial work on the same project, regardless of whether findings have been publicly disclosed.
Argument structure (Toulmin):
Grounds

ABC Engineering completed the peer review roughly one year before the RFP issued; the RFP incorporated the review's findings; XYZ Construction invited ABC Engineering into the joint venture only after RFP issuance.

Warrant

Engineers must avoid situations where private knowledge gained in a position of trust could confer an unfair competitive advantage, and public disclosure of that knowledge through an intervening procurement document, rather than mere passage of time, is what discharges this obligation and permits subsequent competitive participation.

Rebuttal

Would not apply if the RFP had been issued immediately after the peer review's completion, since a short interval would make it harder to demonstrate that the informational advantage had been meaningfully neutralized by public disclosure, independent of elapsed time itself.

Engineer A Peer Review Confidentiality Duty Engineer A Peer Review Nondisclosure
Event Timeline (9)
9 sequenced 6 actions 3 events
Case timeline
The state agency retains ABC Engineering to participate in an independent external peer review of the design of a major state-funded transportation project, without requiring a confidentiality agreement.
Causal-normative reasoning(confidence 0.60)
By retaining the firm as lead reviewer, the state agency set in motion the chain that gave Engineer A privileged design information, so this action's normative weight lies in enabling the later information advantage and conflict of interest that had to be managed.
State changes (2)
  • began: Limited Scope Peer Review
  • began: No Confidentiality Agreement On Project
Engineer A accepts the assignment to serve as lead engineer on the independent external review of the design of the major road transportation project prepared by the agency.
At stake (1)
  • Independent Peer Review Obligation
Causal-normative reasoning(confidence 0.65)
Accepting the lead reviewer role is pivotal because it is the step that produces the peer review performance and the resulting information advantage, meaning any failure to recognize the obligations tied to this role directly seeds the later conflict of interest dilemma in the joint venture decision.
ABC Engineering, led by Engineer A, performs and completes the limited-scope peer review focused on clarifications and refinements of the existing construction plans and specifications, which are ultimately incorporated into the RFP.
Fulfills (1)
  • Independent Peer Review Obligation
Causal-normative reasoning(confidence 0.75)
Engineer A's performance of the peer review fulfills the independent peer review obligation, yet this same faithful execution generates an information advantage that becomes the seed of the later conflict of interest when the joint venture opportunity arises, showing that even fully compliant conduct can create downstream ethical risk if not managed once the review concludes.
State changes (1)
  • began: Peer Review Project Knowledge
ABC Engineering finishes the limited-scope independent external peer review of the construction plans and specifications for the major road transportation project.
State changes (2)
  • began: Peer Review Project Knowledge
  • began: Post Peer Review Phase
Through the peer review, Engineer A gains access to confidential, nonpublic project information that could provide competitive advantages in a subsequent proposal.
State changes (1)
  • began: Confidential Information Advantage
The clarifications and refinements produced by the peer review are incorporated into the Request for Proposal soliciting design-build services for the project.
Approximately one year after the peer review, the state agency issues a Request for Proposal soliciting proposals for design-build services to complete the major road transportation project.
Causal-normative reasoning(confidence 0.55)
Issuing the RFP is what causally triggers XYZ Construction's joint venture invitation to Engineer A, so its significance rests on opening the door to the very opportunity that later required a conflict of interest judgment.
XYZ Construction invites ABC Engineering to participate in a design-build joint venture and submit a proposal for the major road transportation project that ABC previously peer reviewed.
Causal-normative reasoning(confidence 0.60)
The joint venture invitation matters because it directly forces Engineer A's participation decision, converting the prior peer review information advantage into a live conflict of interest problem that must be resolved.
State changes (1)
  • began: Pending Joint Venture Invitation
Engineer A must decide whether ABC Engineering will participate with XYZ Construction in the design-build joint venture on the project it previously peer reviewed. The BER concludes this participation does not raise a conflict of interest, while noting that state laws may vary.
Causal-normative reasoning(confidence 0.70)
Because this decision is explicitly guided by the norm of avoiding conflict of interest, and it arises only after Engineer A gained privileged review knowledge and received the joint venture invitation, choosing to participate or decline determines whether the information advantage becomes an actionable ethical violation.
State changes (2)
  • began: No Conflict In Joint Venture
  • ended: Pending Joint Venture Invitation
Narrative (4 main characters)
View Extraction
Opening 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 professional engineer and owner of ABC Engineering. Your firm was retained by a state agency to serve as the lead independent external peer reviewer for the design of a major state-funded transportation project. The peer review was limited in scope, focused on clarifications and refinements to existing construction plans and specifications, and no confidentiality agreement was executed as part of that engagement. Those plans and specifications were later incorporated into a Request for Proposal soliciting design-build services to complete the project. Approximately one year after ABC Engineering completed its peer review work, the state agency issued that RFP. XYZ Construction has now invited ABC Engineering to join a design-build joint venture and submit a proposal for the same transportation project. You must now consider how your prior peer review role should factor into a series of decisions about participation, disclosure, and use of the knowledge you gained.

Main characters (4)

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.

Engineer A Roles in this case: Lead Peer Review Engineer

Guided by: Confidentiality in Peer Review, Conflict of Interest in Design-Build Venture

Engineer A is expected to render an objective, independent technical judgment as peer reviewer, but as an employee of ABC Engineering, Engineer A also owes a duty of loyalty and favorable representation to that firm. If the peer review implicates ABC Engineering's own work quality or commercial interests, objectivity and faithful agency can pull in opposite directions, since a fully candid review might disadvantage the employer while a loyal one might compromise the integrity of the review.

Tension between ABC Engineering Faithful Agent Duty and Engineer A Peer Review Nondisclosure

Maintaining confidentiality of peer review deliberations may require withholding information from ABC Engineering that the firm would want as part of Engineer A's duty of loyal agency, creating a conflict between professional confidentiality obligations and internal reporting expectations.

Tension between Engineer A Peer Review Confidentiality Duty and Engineer A Peer Review Nondisclosure

A rigorous, objective peer review may surface findings that the nondisclosure constraint prevents Engineer A from sharing with parties who need the information, such as the State Agency Client or XYZ Construction Contractor, undermining the practical value and public benefit of an objective review.

ABC Engineering Roles in this case: Provider Firm

Engineer A is expected to render an objective, independent technical judgment as peer reviewer, but as an employee of ABC Engineering, Engineer A also owes a duty of loyalty and favorable representation to that firm. If the peer review implicates ABC Engineering's own work quality or commercial interests, objectivity and faithful agency can pull in opposite directions, since a fully candid review might disadvantage the employer while a loyal one might compromise the integrity of the review.

Tension between ABC Engineering Faithful Agent Duty and Engineer A Peer Review Nondisclosure

Maintaining confidentiality of peer review deliberations may require withholding information from ABC Engineering that the firm would want as part of Engineer A's duty of loyal agency, creating a conflict between professional confidentiality obligations and internal reporting expectations.

State Agency Roles in this case: ClientProcurement Authority

Engineer A is expected to render an objective, independent technical judgment as peer reviewer, but as an employee of ABC Engineering, Engineer A also owes a duty of loyalty and favorable representation to that firm. If the peer review implicates ABC Engineering's own work quality or commercial interests, objectivity and faithful agency can pull in opposite directions, since a fully candid review might disadvantage the employer while a loyal one might compromise the integrity of the review.

Attaches to role: Client

A rigorous, objective peer review may surface findings that the nondisclosure constraint prevents Engineer A from sharing with parties who need the information, such as the State Agency Client or XYZ Construction Contractor, undermining the practical value and public benefit of an objective review.

Attaches to role: Client
XYZ Construction Roles in this case: Contractor

A rigorous, objective peer review may surface findings that the nondisclosure constraint prevents Engineer A from sharing with parties who need the information, such as the State Agency Client or XYZ Construction Contractor, undermining the practical value and public benefit of an objective review.

The Board’s deliberation

How the Board of Ethical Review resolved the case, verbatim from its published conclusions.

It would not be unethical for Engineer A and his firm ABC Engineering to participate in a design-build joint venture and submit a proposal for the major road transportation project, as long as the state agency approves and the work complies with state laws and regulations.
Opening States (8)
No Confidentiality Agreement On Project Limited Scope Peer Review Peer Review Project Knowledge Post Peer Review Phase Pending Joint Venture Invitation No Conflict In Joint Venture Confidential Information Advantage Varying State Law On Conflict
Summary
  • An engineer who serves on a peer review committee must keep confidential information learned in that role separate from the competitive interests of his own firm.
  • A firm can ethically pursue a design build joint venture on a public project even if one of its engineers had earlier access to related confidential information, provided proper safeguards and disclosures are in place.
  • Faithful agency to one's employer does not override the duty of nondisclosure owed to a peer review process, so engineers must actively manage these dual obligations rather than assume one automatically trumps the other.

© Licensed under the GNU GPL v3