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 chainNode Types & Relationships
→ Question answered by Conclusion
→ Provision applies to Entity
NSPE Code Provisions Referenced
View ExtractionII.4. II.4.
Full Text:
Engineers shall act for each employer or client as faithful agents or trustees.
Applies To:
II.4.a. II.4.a.
Full Text:
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.
Applies To:
II.4.b. II.4.b.
Full Text:
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.
Applies To:
II.4.d. II.4.d.
Full Text:
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.
Applies To:
III.4.a. III.4.a.
Full Text:
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.
Applies To:
Cited Precedent Cases
View ExtractionBER Case 96-8 analogizing linked
Principle Established:
When a peer reviewer discovers work that may violate safety requirements and endanger public health, safety, and welfare, the engineer must first discuss the issues with the reviewed engineer, and if unresolved, must notify proper authorities, even if bound by a confidentiality agreement.
Citation Context:
The Board cited this case to illustrate the principle of confidentiality in peer-review programs and the tension between confidentiality obligations and the duty to protect public health, safety, and welfare.
Relevant Excerpts:
"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."
"In reviewing the facts, the BER decided that if Engineer A determined that Engineer B's work is or may be in violation of state and local safety requirements and endangers the public health, safety, and welfare, the appropriate action would be for Engineer A to immediately discuss these issues with Engineer B"
BER Case 94-5 distinguishing linked
Principle Established:
An engineer cannot ethically serve multiple conflicting interests simultaneously, such as acting as a city engineer while also providing design and inspection services for private developers within the same city, as this creates an irreconcilable conflict of interest.
Citation Context:
The Board cited this case to address the potential for conflict of interest when an engineer serves multiple roles or interests, ultimately distinguishing it from the current case where no such conflict was found.
Relevant Excerpts:
"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."
"In determining that it was unethical for Engineer A to serve as city engineer and provide review and inspection services for private developers within the city, the BER noted that it could not see how an engineer can wear multiple hats and ethically serve multiple interests"
Questions & Conclusions
View ExtractionQuestion 1 Board Question
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?
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.
Question 2 Implicit
Does the absence of a formal confidentiality agreement eliminate ABC Engineering's ethical obligation to avoid exploiting insider knowledge gained during the peer review, or does the ethical duty persist independently of any contractual arrangement?
Beyond the Board's conditional approval, the absence of a confidentiality agreement does not extinguish ABC Engineering's ethical obligation to refrain from exploiting insider knowledge gained during the peer review. The ethical duty of faithful agency under Code Section II.4 runs independently of any contractual instrument: ABC Engineering was retained by the state agency as a trusted advisor, and that trust relationship generates a non-waivable obligation to treat privileged design information as confidential regardless of whether a formal agreement was signed. The absence of a confidentiality agreement is a procedural gap in the engagement structure, not a substantive license to leverage proprietary knowledge for competitive gain. Accordingly, even with state agency approval, ABC Engineering bears a continuing affirmative duty to ensure that no design-specific knowledge acquired during the peer review - including the clarifications and refinements it helped shape - is used to inform or advantage its design-build proposal. The Board's conditional approval implicitly assumes this duty will be honored, but the analysis would have been strengthened by making that assumption explicit.
In response to Q101: The absence of a formal confidentiality agreement does not eliminate ABC Engineering's ethical obligation to avoid exploiting insider knowledge gained during the peer review. The ethical duty to act as a faithful agent and trustee to the state agency client arises from the professional relationship itself, not from any contractual instrument. When the state agency retained ABC Engineering to conduct an independent external peer review, it extended a form of privileged access grounded in professional trust. That trust creates an independent ethical obligation - rooted in NSPE Code Section II.4 - to refrain from leveraging privileged design knowledge for subsequent competitive advantage. A confidentiality agreement would formalize and reinforce this duty, but its absence does not dissolve it. The ethical obligation persists because the informational asymmetry created by the peer review role is real and material regardless of whether it is contractually acknowledged.
In response to Q301: From a deontological perspective, ABC Engineering has a strong prima facie categorical duty to refrain from competing in a procurement process it helped shape through its peer review role, and this duty is not dissolved by the absence of a confidentiality agreement or by state agency approval. Deontological ethics grounds obligations in the nature of the act and the relationship, not in consequences or permissions. The peer review relationship created a duty of faithful agency to the state client - a duty that includes refraining from using privileged access for self-interested competitive purposes. This duty is categorical in the sense that it applies regardless of whether a confidentiality agreement was signed, because the ethical obligation flows from the professional relationship and the trust it entails. Agency approval may shift moral responsibility partially to the approving party, but it does not eliminate ABC Engineering's independent duty to avoid exploiting its advisory role. A strict deontological analysis would therefore require either categorical abstention or, at minimum, robust disclosure and remediation measures that go beyond mere agency consent.
Question 3 Implicit
Is a one-year gap between completion of the peer review and submission of a design-build proposal a sufficient cooling-off period to neutralize the competitive advantage ABC Engineering gained from its privileged access to the project's design details?
The Board's analysis does not adequately grapple with the structural peculiarity that the peer review was specifically limited to clarifications and refinements that were directly incorporated into the design-build RFP. This narrow scope creates a stronger and more durable conflict of interest than a broad, general design review would have, because ABC Engineering's contributions did not merely inform its general understanding of the project - they literally shaped the procurement documents under which it now seeks to compete. This means ABC Engineering possesses not just background knowledge of the project but specific, formative insight into the evaluative criteria, technical specifications, and design trade-offs embedded in the RFP itself. A one-year cooling-off period may neutralize the staleness of general project familiarity, but it cannot neutralize the structural advantage of having authored portions of the competitive framework. The Board should have conditioned approval not only on state agency consent but also on a rigorous assessment of whether ABC Engineering's specific peer review contributions created an informational asymmetry so fundamental that no cooling-off period could adequately remediate it.
In response to Q102: A one-year cooling-off period is a relevant mitigating factor but is not categorically sufficient to neutralize the competitive advantage ABC Engineering gained from its peer review role. The adequacy of any cooling-off period must be assessed in relation to the nature and specificity of the insider knowledge acquired. In this case, the peer review was narrowly scoped to clarifications and refinements that were directly incorporated into the design-build RFP - meaning ABC Engineering's privileged knowledge was not general or abstract but was specifically embedded in the very procurement documents it now seeks to compete under. This tight nexus between the peer review outputs and the RFP content means that the passage of one year does not erase the informational advantage; the design details, specification choices, and refinement rationale that ABC Engineering helped shape remain embedded in the RFP regardless of elapsed time. The cooling-off period analysis is therefore necessary but insufficient on its own - it must be weighed alongside the scope-to-procurement nexus, the degree of informational asymmetry, and whether the state agency has been fully informed of the conflict before granting approval.
In response to Q104: The narrow, RFP-specific scope of the peer review creates a stronger and more durable conflict of interest than a broader, more general review would have. When a peer review is limited to clarifications and refinements that are directly incorporated into a procurement document, the reviewing firm's knowledge is not merely background familiarity with a project type or general design approach - it is precise, actionable intelligence about the specific technical choices, trade-offs, and specification language that define the competitive landscape of the RFP. A broader review might yield general impressions that dissipate over time and are less directly translatable into competitive advantage. By contrast, ABC Engineering's contributions were surgically embedded into the RFP itself, meaning that its proposal team would approach the procurement with an insider's understanding of why particular specifications were written as they were, what alternatives were considered and rejected, and where the design has known vulnerabilities or opportunities. This specificity makes the conflict of interest more acute, not less, and strengthens the case for heightened disclosure obligations and more rigorous agency scrutiny before participation is approved.
In response to Q402: If the peer review had been broader in scope - encompassing full design development rather than limited clarifications and refinements - the Board would likely have faced a more difficult case for permitting ABC Engineering's participation, but the analytical framework would remain the same. A broader review would have given ABC Engineering deeper and more comprehensive knowledge of the project's design philosophy, technical constraints, and cost drivers, potentially creating an even more substantial informational advantage in the design-build competition. However, the critical ethical variable is not the absolute breadth of the review but the specificity and direct relevance of the knowledge gained to the competitive procurement at issue. In the present case, the narrow scope of the review is actually more problematic in one respect: the peer review outputs were directly incorporated into the RFP, creating a precise and traceable nexus between ABC Engineering's advisory contributions and the competitive documents. A broader review might have produced more diffuse knowledge that dissipates more readily over time. The Board's analysis should therefore focus on the scope-to-procurement nexus rather than scope breadth alone as the primary determinant of conflict severity.
In response to Q403: If the RFP had been issued immediately after the peer review was completed - with no cooling-off period - the Board would almost certainly have concluded that participation was unethical, as the informational advantage would have been at its maximum and the appearance of impropriety most acute. The one-year gap is therefore a relevant and potentially dispositive factor in the Board's permissive conclusion, but its significance depends on what changed during that year. If the design details, specifications, and refinements that ABC Engineering contributed to the peer review remained substantially unchanged in the RFP - as appears to be the case given the narrow, incorporation-focused scope of the review - then the passage of time does not meaningfully diminish the competitive advantage. The cooling-off period analysis is most meaningful when it corresponds to a period during which the insider knowledge becomes stale, publicly available, or otherwise neutralized. In this case, the one-year period may have been sufficient to satisfy a formal threshold but insufficient to eliminate the substantive informational asymmetry, suggesting that the Board's reliance on the cooling-off period as a key mitigating factor deserves more critical scrutiny.
Question 4 Implicit
Should Engineer A have proactively disclosed to the state agency, at the time of accepting the peer review engagement, any foreseeable interest in future procurement opportunities related to the same project, rather than waiting until an RFP was issued?
The Board's reliance on state agency approval as a sufficient ethical safeguard is analytically incomplete because the state agency occupies a structurally compromised position when making that approval decision. As both the client that retained ABC Engineering for the peer review and the procuring authority issuing the design-build RFP, the agency has an institutional interest in the success of the procurement that may bias its willingness to exclude a technically qualified firm. Approval by a conflicted approving authority cannot fully substitute for independent ethical scrutiny. The more ethically robust framework would require ABC Engineering to proactively disclose the conflict at the earliest moment - ideally when XYZ Construction extended the design-build invitation, and arguably even earlier, at the time of accepting the peer review engagement if future procurement interest was foreseeable - and to seek approval from a disinterested party or through a transparent public process. Code Section II.4.a's disclosure obligation is designed precisely to surface these conflicts before they become entrenched, not merely to ratify participation after the fact. The Board's conditional approval, while not incorrect, understates the proactive disclosure burden that Code Section II.4.a places on Engineer A.
In response to Q103: Engineer A had an ethical obligation to proactively disclose any foreseeable interest in future procurement opportunities related to the same project at the time of accepting the peer review engagement, not merely upon receipt of an RFP. NSPE Code Section II.4.a requires disclosure of all known or potential conflicts of interest that could influence or appear to influence professional judgment. At the moment ABC Engineering accepted the peer review role, the possibility that the same project would proceed to a design-build procurement was not speculative - the peer review was explicitly scoped to clarifications and refinements feeding into a design-build RFP. If Engineer A or ABC Engineering had any foreseeable interest in design-build work on this project, that interest constituted a potential conflict of interest that should have been disclosed upfront. Waiting until an RFP is issued before disclosing the conflict allows the informational advantage to accumulate unchecked and deprives the state agency of the opportunity to impose conditions, require recusals, or select a different peer reviewer at the outset. Early disclosure would have been both ethically cleaner and more protective of the peer review program's integrity.
In response to Q401: If ABC Engineering had proactively disclosed the potential conflict of interest to the state agency at the moment XYZ Construction extended the design-build invitation - rather than waiting for the agency to discover and evaluate it independently - the Board's ethical analysis would likely have been more straightforwardly permissive and the appearance of impropriety substantially reduced. Proactive disclosure signals that the disclosing party is prioritizing transparency and the client's interests over its own competitive advantage, which is precisely the disposition that NSPE Code Section II.4.a requires. It also gives the state agency the opportunity to impose conditions, require information firewalls, or otherwise structure ABC Engineering's participation in a way that mitigates the informational asymmetry before it is exploited. The ethical weight of disclosure timing is significant: a firm that discloses immediately upon receiving a conflicting invitation demonstrates that it is managing the conflict rather than concealing it, which is a materially different ethical posture from one that relies on the agency to independently identify and evaluate the conflict. Proactive disclosure would not eliminate the underlying conflict, but it would substantially satisfy the faithful agency obligation and reduce the appearance of impropriety.
Question 5 Implicit
Does the scope of the peer review - limited to clarifications and refinements that were directly incorporated into the design-build RFP - create a stronger or more durable conflict of interest than a broader, more general review would have, given that ABC Engineering's specific contributions shaped the very procurement documents it now seeks to compete under?
The Board's analysis does not adequately grapple with the structural peculiarity that the peer review was specifically limited to clarifications and refinements that were directly incorporated into the design-build RFP. This narrow scope creates a stronger and more durable conflict of interest than a broad, general design review would have, because ABC Engineering's contributions did not merely inform its general understanding of the project - they literally shaped the procurement documents under which it now seeks to compete. This means ABC Engineering possesses not just background knowledge of the project but specific, formative insight into the evaluative criteria, technical specifications, and design trade-offs embedded in the RFP itself. A one-year cooling-off period may neutralize the staleness of general project familiarity, but it cannot neutralize the structural advantage of having authored portions of the competitive framework. The Board should have conditioned approval not only on state agency consent but also on a rigorous assessment of whether ABC Engineering's specific peer review contributions created an informational asymmetry so fundamental that no cooling-off period could adequately remediate it.
In response to Q102: A one-year cooling-off period is a relevant mitigating factor but is not categorically sufficient to neutralize the competitive advantage ABC Engineering gained from its peer review role. The adequacy of any cooling-off period must be assessed in relation to the nature and specificity of the insider knowledge acquired. In this case, the peer review was narrowly scoped to clarifications and refinements that were directly incorporated into the design-build RFP - meaning ABC Engineering's privileged knowledge was not general or abstract but was specifically embedded in the very procurement documents it now seeks to compete under. This tight nexus between the peer review outputs and the RFP content means that the passage of one year does not erase the informational advantage; the design details, specification choices, and refinement rationale that ABC Engineering helped shape remain embedded in the RFP regardless of elapsed time. The cooling-off period analysis is therefore necessary but insufficient on its own - it must be weighed alongside the scope-to-procurement nexus, the degree of informational asymmetry, and whether the state agency has been fully informed of the conflict before granting approval.
In response to Q104: The narrow, RFP-specific scope of the peer review creates a stronger and more durable conflict of interest than a broader, more general review would have. When a peer review is limited to clarifications and refinements that are directly incorporated into a procurement document, the reviewing firm's knowledge is not merely background familiarity with a project type or general design approach - it is precise, actionable intelligence about the specific technical choices, trade-offs, and specification language that define the competitive landscape of the RFP. A broader review might yield general impressions that dissipate over time and are less directly translatable into competitive advantage. By contrast, ABC Engineering's contributions were surgically embedded into the RFP itself, meaning that its proposal team would approach the procurement with an insider's understanding of why particular specifications were written as they were, what alternatives were considered and rejected, and where the design has known vulnerabilities or opportunities. This specificity makes the conflict of interest more acute, not less, and strengthens the case for heightened disclosure obligations and more rigorous agency scrutiny before participation is approved.
In response to Q402: If the peer review had been broader in scope - encompassing full design development rather than limited clarifications and refinements - the Board would likely have faced a more difficult case for permitting ABC Engineering's participation, but the analytical framework would remain the same. A broader review would have given ABC Engineering deeper and more comprehensive knowledge of the project's design philosophy, technical constraints, and cost drivers, potentially creating an even more substantial informational advantage in the design-build competition. However, the critical ethical variable is not the absolute breadth of the review but the specificity and direct relevance of the knowledge gained to the competitive procurement at issue. In the present case, the narrow scope of the review is actually more problematic in one respect: the peer review outputs were directly incorporated into the RFP, creating a precise and traceable nexus between ABC Engineering's advisory contributions and the competitive documents. A broader review might have produced more diffuse knowledge that dissipates more readily over time. The Board's analysis should therefore focus on the scope-to-procurement nexus rather than scope breadth alone as the primary determinant of conflict severity.
Question 6 Principle Tension
Does the principle of Fairness in Professional Competition - which supports allowing qualified firms to compete for public contracts - conflict with the principle of Independent Review Integrity Non-Exploitation, which holds that knowledge gained in a privileged advisory role must not be leveraged for subsequent competitive advantage?
In response to Q201: There is a genuine and unresolved tension between the principle of Fairness in Professional Competition - which holds that qualified firms should not be arbitrarily excluded from public procurement - and the principle of Independent Review Integrity Non-Exploitation, which holds that knowledge gained in a privileged advisory role must not be leveraged for subsequent competitive advantage. The Board's conditional approval attempts to reconcile these principles by delegating the resolution to the state agency, but this approach does not fully resolve the tension. Fairness in competition is not merely about formal eligibility; it encompasses substantive equality of informational access among competing firms. When ABC Engineering enters a design-build competition with insider knowledge of the RFP's technical foundations that no other competitor possesses, the competitive field is structurally unequal regardless of whether ABC Engineering is formally permitted to participate. The principle of Independent Review Integrity Non-Exploitation therefore imposes a constraint that cannot be fully satisfied by agency approval alone - it requires either categorical abstention or robust remedial measures that genuinely level the informational playing field.
The Board resolved the tension between Fairness in Professional Competition and Independent Review Integrity Non-Exploitation not by declaring one principle categorically superior, but by subordinating both to a procedural mechanism: agency disclosure and approval. This resolution is pragmatic rather than principled. It treats the state agency's consent as a proxy for ethical legitimacy, effectively converting a substantive conflict-of-interest question into a procedural compliance question. The danger of this approach is that it does not address whether the agency's approval is itself compromised by its own procurement interests - the agency may benefit from having a technically informed firm compete, creating an incentive to approve participation that has nothing to do with fairness to other competitors. The case therefore teaches that when two substantive principles conflict, routing resolution through a third procedural principle (agency approval) can obscure rather than resolve the underlying ethical tension.
Question 7 Principle Tension
How should the tension between the Agency Disclosure and Approval Obligation - which conditionally permits participation with agency consent - and the Peer Review Independence and Integrity principle - which may require categorical abstention regardless of agency approval - be resolved when the agency's own procurement interests may bias its approval decision?
The Board's reliance on state agency approval as a sufficient ethical safeguard is analytically incomplete because the state agency occupies a structurally compromised position when making that approval decision. As both the client that retained ABC Engineering for the peer review and the procuring authority issuing the design-build RFP, the agency has an institutional interest in the success of the procurement that may bias its willingness to exclude a technically qualified firm. Approval by a conflicted approving authority cannot fully substitute for independent ethical scrutiny. The more ethically robust framework would require ABC Engineering to proactively disclose the conflict at the earliest moment - ideally when XYZ Construction extended the design-build invitation, and arguably even earlier, at the time of accepting the peer review engagement if future procurement interest was foreseeable - and to seek approval from a disinterested party or through a transparent public process. Code Section II.4.a's disclosure obligation is designed precisely to surface these conflicts before they become entrenched, not merely to ratify participation after the fact. The Board's conditional approval, while not incorrect, understates the proactive disclosure burden that Code Section II.4.a places on Engineer A.
In response to Q202: The tension between the Agency Disclosure and Approval Obligation and the Peer Review Independence and Integrity principle is not fully resolved by the Board's conditional approval framework, particularly because the state agency's own procurement interests may compromise the objectivity of its approval decision. The state agency has an interest in attracting qualified design-build proposals and may view ABC Engineering's technical familiarity with the project as an asset rather than a disqualifying conflict. This creates a structural bias in the agency's approval calculus that undermines the reliability of its consent as an ethical safeguard. A more robust resolution would require that the approval decision be made by a party independent of the procurement - such as an ethics board, inspector general, or independent procurement officer - rather than by the agency that both commissioned the peer review and issued the RFP. Absent such independence, the agency's approval is a necessary but not sufficient ethical condition for ABC Engineering's participation.
The Board resolved the tension between Fairness in Professional Competition and Independent Review Integrity Non-Exploitation not by declaring one principle categorically superior, but by subordinating both to a procedural mechanism: agency disclosure and approval. This resolution is pragmatic rather than principled. It treats the state agency's consent as a proxy for ethical legitimacy, effectively converting a substantive conflict-of-interest question into a procedural compliance question. The danger of this approach is that it does not address whether the agency's approval is itself compromised by its own procurement interests - the agency may benefit from having a technically informed firm compete, creating an incentive to approve participation that has nothing to do with fairness to other competitors. The case therefore teaches that when two substantive principles conflict, routing resolution through a third procedural principle (agency approval) can obscure rather than resolve the underlying ethical tension.
Question 8 Principle Tension
Does the Dual Role Appearance of Impropriety Avoidance principle - which guards against the perception of unfair advantage from sequential roles - conflict with the Jurisdiction-Specific Compliance Obligation principle, given that state law may explicitly permit such participation and thereby legally sanction what ethics might otherwise prohibit?
In response to Q203: The tension between the Dual Role Appearance of Impropriety Avoidance principle and the Jurisdiction-Specific Compliance Obligation principle reflects a broader conflict between ethical standards and legal permissibility that the Board does not fully resolve. State law may explicitly permit design-build participation by prior peer reviewers, and the Board correctly notes that compliance with applicable law is a necessary condition. However, legal permissibility does not establish ethical sufficiency. The NSPE Code of Ethics imposes obligations that frequently exceed minimum legal requirements, and the appearance of impropriety created by ABC Engineering's sequential roles - first as independent reviewer, then as competitive bidder on the same project - is not neutralized by statutory authorization. Engineers are held to a standard of conduct that preserves public trust in the profession, and that standard requires avoiding not only actual conflicts of interest but also situations that would cause a reasonable observer to question the integrity of the professional process. State law compliance is therefore a floor, not a ceiling, for ethical conduct in this context.
The interaction between the Dual Role Appearance of Impropriety Avoidance principle and the Jurisdiction-Specific Compliance Obligation principle reveals a persistent gap in the Board's reasoning: legal permissibility and ethical permissibility are treated as substantially convergent when they are analytically distinct. The Board conditions its approval on compliance with state laws and regulations, implying that legal authorization substantially satisfies the ethical inquiry. However, the Dual Role Appearance of Impropriety Avoidance principle operates independently of legal authorization - it is concerned with how sequential roles appear to the public and to competing firms, not merely whether they are legally sanctioned. A state law that explicitly permits post-review competition does not eliminate the reasonable perception that ABC Engineering held an informational advantage derived from its privileged advisory role. The case teaches that when jurisdiction-specific legal compliance is invoked to resolve an appearance-of-impropriety concern, the ethical analysis must still independently assess whether the appearance of unfairness persists even after legal authorization is confirmed, and that the two inquiries cannot be collapsed into one without sacrificing the integrity of the appearance standard.
Question 9 Principle Tension
Does the Peer Review Program Collegial Improvement Purpose principle - which frames peer review as a cooperative, trust-based professional activity - conflict with the Post-Review Conflict of Interest Avoidance principle when a firm uses the access afforded by that collegial trust to position itself competitively in a subsequent procurement, even after a cooling-off period?
The Peer Review Program Collegial Improvement Purpose principle and the Post-Review Conflict of Interest Avoidance principle exist in structural tension that the Board's conditional approval does not fully resolve. Peer review programs are premised on a collegial, trust-based exchange in which a reviewing firm gains privileged access to design details precisely because it is understood to be acting in a disinterested advisory capacity. When that same firm subsequently leverages the access afforded by that collegial trust to position itself competitively - even after a one-year cooling-off period - it retroactively reframes the peer review engagement as a market intelligence exercise. The Board's approval, conditioned on agency consent and legal compliance, does not address this systemic corrosion: if firms routinely accept peer review roles with an eye toward subsequent procurement opportunities, the collegial foundation of peer review programs is undermined regardless of whether any individual instance is technically permissible. The case teaches that short-term conditional permissibility can be in tension with long-term institutional integrity, and that consequentialist concerns about systemic effects deserve greater weight in principle prioritization than the Board's analysis affords them.
From a deontological perspective, does ABC Engineering have a categorical duty to refrain from competing in a procurement process it helped shape through its peer review role, regardless of whether a confidentiality agreement was signed or whether the state agency grants approval?
In response to Q301: From a deontological perspective, ABC Engineering has a strong prima facie categorical duty to refrain from competing in a procurement process it helped shape through its peer review role, and this duty is not dissolved by the absence of a confidentiality agreement or by state agency approval. Deontological ethics grounds obligations in the nature of the act and the relationship, not in consequences or permissions. The peer review relationship created a duty of faithful agency to the state client - a duty that includes refraining from using privileged access for self-interested competitive purposes. This duty is categorical in the sense that it applies regardless of whether a confidentiality agreement was signed, because the ethical obligation flows from the professional relationship and the trust it entails. Agency approval may shift moral responsibility partially to the approving party, but it does not eliminate ABC Engineering's independent duty to avoid exploiting its advisory role. A strict deontological analysis would therefore require either categorical abstention or, at minimum, robust disclosure and remediation measures that go beyond mere agency consent.
From a virtue ethics perspective, does Engineer A's decision to accept the design-build joint venture invitation reflect the professional character of an engineer who genuinely prioritizes public trust and objectivity, or does it reveal a disposition to exploit an advisory role for competitive gain?
From a virtue ethics perspective, the Board's analysis focuses on procedural compliance - agency approval, cooling-off period, state law conformity - but does not address whether Engineer A's decision to accept the design-build joint venture invitation reflects the professional character expected of an engineer who has served in a position of public trust. An engineer of genuine integrity, upon receiving the design-build invitation from XYZ Construction, would not merely ask whether participation is permissible but whether it is consistent with the spirit of the independent peer review role. The peer review program's foundational purpose is collegial improvement of public infrastructure design through disinterested expert scrutiny. An engineer who treats that advisory access as a stepping stone to competitive advantage - even after a cooling-off period and with agency approval - risks eroding the trust that makes peer review programs function. The Board's conclusion is legally and procedurally defensible, but a more complete ethical analysis would acknowledge that the virtuous course of action may have been for Engineer A to decline the invitation entirely, or at minimum to impose upon himself structural safeguards - such as recusal from proposal sections drawing on peer review knowledge - that go beyond what the Board required.
In response to Q303: From a virtue ethics perspective, Engineer A's decision to accept the design-build joint venture invitation raises legitimate questions about professional character that the Board's conditional approval does not fully address. A virtuous engineer - one who genuinely internalizes the values of objectivity, public trust, and professional integrity - would approach the design-build invitation with heightened caution precisely because of the prior peer review role, not merely seek agency approval as a procedural clearance. The virtue ethics question is not whether participation is permissible under the rules, but whether it reflects the disposition of an engineer who prioritizes the integrity of the advisory relationship over competitive opportunity. The fact that ABC Engineering's peer review contributions were directly incorporated into the RFP it now seeks to compete under creates a situation where a virtuous professional would at minimum question whether participation - even if approved - is consistent with the spirit of the peer review engagement. Virtue ethics would counsel Engineer A to err on the side of abstention or to impose self-directed constraints beyond what the agency requires, as an expression of genuine professional integrity rather than mere rule compliance.
From a deontological perspective, does the absence of a confidentiality agreement eliminate ABC Engineering's ethical duty to treat insider knowledge gained during the peer review as privileged, or does the duty of faithful agency to the state client persist independently of any contractual instrument?
Beyond the Board's conditional approval, the absence of a confidentiality agreement does not extinguish ABC Engineering's ethical obligation to refrain from exploiting insider knowledge gained during the peer review. The ethical duty of faithful agency under Code Section II.4 runs independently of any contractual instrument: ABC Engineering was retained by the state agency as a trusted advisor, and that trust relationship generates a non-waivable obligation to treat privileged design information as confidential regardless of whether a formal agreement was signed. The absence of a confidentiality agreement is a procedural gap in the engagement structure, not a substantive license to leverage proprietary knowledge for competitive gain. Accordingly, even with state agency approval, ABC Engineering bears a continuing affirmative duty to ensure that no design-specific knowledge acquired during the peer review - including the clarifications and refinements it helped shape - is used to inform or advantage its design-build proposal. The Board's conditional approval implicitly assumes this duty will be honored, but the analysis would have been strengthened by making that assumption explicit.
In response to Q101: The absence of a formal confidentiality agreement does not eliminate ABC Engineering's ethical obligation to avoid exploiting insider knowledge gained during the peer review. The ethical duty to act as a faithful agent and trustee to the state agency client arises from the professional relationship itself, not from any contractual instrument. When the state agency retained ABC Engineering to conduct an independent external peer review, it extended a form of privileged access grounded in professional trust. That trust creates an independent ethical obligation - rooted in NSPE Code Section II.4 - to refrain from leveraging privileged design knowledge for subsequent competitive advantage. A confidentiality agreement would formalize and reinforce this duty, but its absence does not dissolve it. The ethical obligation persists because the informational asymmetry created by the peer review role is real and material regardless of whether it is contractually acknowledged.
In response to Q301: From a deontological perspective, ABC Engineering has a strong prima facie categorical duty to refrain from competing in a procurement process it helped shape through its peer review role, and this duty is not dissolved by the absence of a confidentiality agreement or by state agency approval. Deontological ethics grounds obligations in the nature of the act and the relationship, not in consequences or permissions. The peer review relationship created a duty of faithful agency to the state client - a duty that includes refraining from using privileged access for self-interested competitive purposes. This duty is categorical in the sense that it applies regardless of whether a confidentiality agreement was signed, because the ethical obligation flows from the professional relationship and the trust it entails. Agency approval may shift moral responsibility partially to the approving party, but it does not eliminate ABC Engineering's independent duty to avoid exploiting its advisory role. A strict deontological analysis would therefore require either categorical abstention or, at minimum, robust disclosure and remediation measures that go beyond mere agency consent.
From a consequentialist perspective, does the Board's conditional approval - contingent on state agency consent - adequately protect the long-term integrity of public peer review programs, or does permitting post-review competition create systemic incentives that undermine the independence of future peer reviewers?
The Board's conclusion that participation is permissible with state agency approval and legal compliance leaves unresolved a systemic consequentialist risk: if engineers routinely accept peer review engagements with the understanding that they may later compete in procurements shaped by those reviews - provided a cooling-off period elapses and the agency consents - the independence and credibility of public peer review programs will be structurally undermined over time. Future peer reviewers may unconsciously or consciously calibrate their review recommendations to position their firms favorably in anticipated procurements, and state agencies may face pressure to approve post-review participation from firms whose technical expertise makes them attractive design-build partners. The Board's case-by-case conditional approval framework does not address these systemic incentive effects. A more complete analysis would recommend that engineering professional societies and public agencies adopt categorical prospective conflict-of-interest rules - analogous to cooling-off statutes in government ethics law - that prohibit peer reviewers from competing in procurements directly derived from their review work, regardless of agency approval, thereby protecting the institutional integrity of peer review as a public good.
In response to Q302: From a consequentialist perspective, the Board's conditional approval framework - contingent on state agency consent - creates systemic incentive risks that may undermine the long-term integrity of public peer review programs. If engineering firms understand that participation in a peer review does not categorically preclude subsequent competition for the same project, rational self-interest will incentivize firms to seek peer review roles strategically, using them as intelligence-gathering opportunities rather than as genuine exercises in independent professional judgment. Over time, this dynamic would erode the independence and credibility of peer review programs, reduce the willingness of agencies to commission external reviews, and ultimately harm the public interest that peer review is designed to serve. A consequentialist analysis therefore suggests that the Board's permissive conditional approach, while reasonable in the individual case, may produce negative systemic consequences that outweigh the benefit of allowing any single qualified firm to compete. A categorical prohibition on post-review competition, or at minimum a longer and more rigorously defined cooling-off period tied to the specificity of the review, would better protect the systemic integrity of peer review as a public institution.
The Peer Review Program Collegial Improvement Purpose principle and the Post-Review Conflict of Interest Avoidance principle exist in structural tension that the Board's conditional approval does not fully resolve. Peer review programs are premised on a collegial, trust-based exchange in which a reviewing firm gains privileged access to design details precisely because it is understood to be acting in a disinterested advisory capacity. When that same firm subsequently leverages the access afforded by that collegial trust to position itself competitively - even after a one-year cooling-off period - it retroactively reframes the peer review engagement as a market intelligence exercise. The Board's approval, conditioned on agency consent and legal compliance, does not address this systemic corrosion: if firms routinely accept peer review roles with an eye toward subsequent procurement opportunities, the collegial foundation of peer review programs is undermined regardless of whether any individual instance is technically permissible. The case teaches that short-term conditional permissibility can be in tension with long-term institutional integrity, and that consequentialist concerns about systemic effects deserve greater weight in principle prioritization than the Board's analysis affords them.
Question 14 Counterfactual
If ABC Engineering had proactively disclosed the potential conflict of interest to the state agency at the moment XYZ Construction extended the design-build invitation - rather than relying on the agency to discover and approve it - would the Board's ethical analysis have been more straightforwardly permissive, and would the appearance of impropriety have been substantially reduced?
In response to Q401: If ABC Engineering had proactively disclosed the potential conflict of interest to the state agency at the moment XYZ Construction extended the design-build invitation - rather than waiting for the agency to discover and evaluate it independently - the Board's ethical analysis would likely have been more straightforwardly permissive and the appearance of impropriety substantially reduced. Proactive disclosure signals that the disclosing party is prioritizing transparency and the client's interests over its own competitive advantage, which is precisely the disposition that NSPE Code Section II.4.a requires. It also gives the state agency the opportunity to impose conditions, require information firewalls, or otherwise structure ABC Engineering's participation in a way that mitigates the informational asymmetry before it is exploited. The ethical weight of disclosure timing is significant: a firm that discloses immediately upon receiving a conflicting invitation demonstrates that it is managing the conflict rather than concealing it, which is a materially different ethical posture from one that relies on the agency to independently identify and evaluate the conflict. Proactive disclosure would not eliminate the underlying conflict, but it would substantially satisfy the faithful agency obligation and reduce the appearance of impropriety.
Question 15 Counterfactual
If the peer review had been broader in scope - encompassing full design development rather than limited clarifications and refinements - would the Board have reached a different conclusion about ABC Engineering's eligibility to compete in the subsequent design-build procurement?
In response to Q402: If the peer review had been broader in scope - encompassing full design development rather than limited clarifications and refinements - the Board would likely have faced a more difficult case for permitting ABC Engineering's participation, but the analytical framework would remain the same. A broader review would have given ABC Engineering deeper and more comprehensive knowledge of the project's design philosophy, technical constraints, and cost drivers, potentially creating an even more substantial informational advantage in the design-build competition. However, the critical ethical variable is not the absolute breadth of the review but the specificity and direct relevance of the knowledge gained to the competitive procurement at issue. In the present case, the narrow scope of the review is actually more problematic in one respect: the peer review outputs were directly incorporated into the RFP, creating a precise and traceable nexus between ABC Engineering's advisory contributions and the competitive documents. A broader review might have produced more diffuse knowledge that dissipates more readily over time. The Board's analysis should therefore focus on the scope-to-procurement nexus rather than scope breadth alone as the primary determinant of conflict severity.
Question 16 Counterfactual
If the RFP had been issued immediately after the peer review was completed - rather than one year later - would the one-year cooling-off period analysis have been dispositive, and would the Board have concluded that participation was unethical absent a longer interval?
In response to Q403: If the RFP had been issued immediately after the peer review was completed - with no cooling-off period - the Board would almost certainly have concluded that participation was unethical, as the informational advantage would have been at its maximum and the appearance of impropriety most acute. The one-year gap is therefore a relevant and potentially dispositive factor in the Board's permissive conclusion, but its significance depends on what changed during that year. If the design details, specifications, and refinements that ABC Engineering contributed to the peer review remained substantially unchanged in the RFP - as appears to be the case given the narrow, incorporation-focused scope of the review - then the passage of time does not meaningfully diminish the competitive advantage. The cooling-off period analysis is most meaningful when it corresponds to a period during which the insider knowledge becomes stale, publicly available, or otherwise neutralized. In this case, the one-year period may have been sufficient to satisfy a formal threshold but insufficient to eliminate the substantive informational asymmetry, suggesting that the Board's reliance on the cooling-off period as a key mitigating factor deserves more critical scrutiny.
Question 17 Counterfactual
If a competing firm had formally challenged ABC Engineering's participation in the design-build RFP on the grounds of unfair informational advantage, would the state agency's approval of ABC Engineering's participation have been sufficient to resolve the ethical and legal conflict, or would additional remedial measures - such as information firewalls or recusal of Engineer A from proposal development - have been required?
In response to Q404: If a competing firm had formally challenged ABC Engineering's participation in the design-build RFP on grounds of unfair informational advantage, the state agency's approval alone would not have been sufficient to resolve the ethical and legal conflict. The agency's approval addresses the question of whether participation is administratively authorized, but it does not resolve the substantive question of whether the competitive process is fair to other bidders who lack equivalent insider knowledge. A formal challenge would likely require the agency - or an independent reviewing authority - to assess whether additional remedial measures are necessary to level the competitive playing field. Such measures might include: requiring ABC Engineering to disclose to all competing firms the specific design details and refinements it contributed during the peer review; imposing information firewalls between the peer review team and the proposal development team within ABC Engineering; requiring Engineer A to recuse himself from proposal development given his role as lead peer reviewer; or commissioning an independent assessment of whether the informational asymmetry is material and remediable. Agency approval is a necessary but not sufficient condition for ethical participation when a formal challenge raises substantive fairness concerns that affect third-party competitors.
Rich Analysis Results
View ExtractionCausal-Normative Links 5
Accept Peer Review Lead Role
- Peer Review Program Collegial Improvement Participation Obligation
- Engineer A Lead Peer Reviewer Conflict of Interest Disclosure to Retaining Attorney or Agency
- Peer Review Confidentiality Agreement Signing Obligation
- Engineer A Peer Review Confidentiality Agreement Signing BER 96-8
- Engineer A Peer Review Program Collegial Improvement Participation BER 96-8
- ABC Engineering Post-Review Design-Build Participation Conflict Disclosure to Agency
- ABC Engineering Post-Peer-Review Design-Build Participation Conflict Assessment
- Post-Peer-Review Design-Build Participation Conflict of Interest Assessment Obligation
Complete and Submit Peer Review
- Peer Review Program Collegial Improvement Participation Obligation
- Engineer A Peer Review Program Collegial Improvement Participation BER 96-8
- Engineer A Peer Review Safety Code Violation Sequential Escalation BER 96-8
- Peer Review Safety Code Violation Sequential Escalation Obligation
- ABC Engineering Peer Review Privileged Access Non-Exploitation in Design-Build Procurement
- ABC Engineering Peer Review Privileged Access Non-Exploitation Design-Build
- ABC Engineering Post-Review Design-Build Participation Conflict Disclosure to Agency
- ABC Engineering No-Confidentiality-Agreement Conflict Management Non-Waiver
- Post-Peer-Review Design-Build Participation Conflict of Interest Assessment Obligation
Accept Design-Build Joint Venture Invitation
- ABC Engineering Post-Review Design-Build Participation Conflict Disclosure to Agency
- ABC Engineering Post-Peer-Review Design-Build Participation Conflict Assessment
- ABC Engineering Post-Review Design-Build Participation Agency Approval Prerequisite
- Post-Review Design-Build Participation Conflict Disclosure Obligation
- Peer Review Privileged Access Non-Exploitation in Competitive Procurement Obligation
- ABC Engineering Peer Review Privileged Access Non-Exploitation in Design-Build Procurement
- ABC Engineering Peer Review Privileged Access Non-Exploitation Design-Build
- No-Confidentiality-Agreement Peer Review Conflict Management Obligation
- ABC Engineering No-Confidentiality-Agreement Conflict Management Non-Waiver
- One-Year Cooling-Off Period Assessment for Post-Review Competitive Participation Obligation
- ABC Engineering One-Year Cooling-Off Period Sufficiency Assessment
- ABC Engineering Jurisdiction-Specific Conflict of Interest Law Verification
- Jurisdiction-Specific Conflict of Interest Law Verification Obligation
- State Agency Procurement Integrity Preservation in Design-Build RFP
Operate Dual Role as City Engineer and Private Developer Consultant
- Dual-Role City Engineer Private Developer Service Conflict Prohibition Obligation
- Firm A Dual-Role City Engineer Private Developer Service Conflict BER 94-5
- Public Agency Role Marketing Exploitation Prohibition Obligation
- Firm A Public Agency Role Marketing Exploitation BER 94-5
Decide Whether to Breach Confidentiality to Report Safety Violations
- Engineer A Peer Review Safety Code Violation Sequential Escalation BER 96-8
- Peer Review Safety Code Violation Sequential Escalation Obligation
- Peer Review Confidentiality Agreement Signing Obligation
- Engineer A Peer Review Confidentiality Agreement Signing BER 96-8
Question Emergence 17
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Information Asymmetry Established
- BER Precedent Cases Referenced
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Independent Review Integrity Non-Exploitation Invoked by ABC Engineering Post-Peer-Review Commercial Decision Agency Disclosure and Approval Obligation Invoked by ABC Engineering Pre-Participation Decision
- Peer Review Independence and Integrity Invoked by ABC Engineering Post-Review Commercial Decision Fairness in Professional Competition Invoked by State Agency Procurement Integrity Concern
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Design-Build_Invitation_Received
- Information Asymmetry Established
- BER Precedent Cases Referenced
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Agency Disclosure and Approval Obligation Before Post-Review Competitive Participation Post-Review Conflict of Interest Avoidance in Design-Build Procurement
- Procurement Integrity in Public Engineering Invoked by State Agency Design-Build RFP Process Conflict of Interest Disclosure Evolution Principle Invoked by ABC Engineering Post-Review Participation Assessment
- Peer Review Program Integrity and Collegial Improvement Purpose Fairness in Professional Competition Invoked by State Agency Procurement Integrity Concern
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- Information Asymmetry Established
- RFP Issuance by State Agency
- Design-Build_Invitation_Received
- BER Precedent Cases Referenced
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Post-Review Conflict of Interest Avoidance in Design-Build Procurement ABC Engineering Peer Review Scope-to-Procurement Nexus Assessment
- Independent Review Integrity and Non-Exploitation of Privileged Access Peer Review Program Integrity and Collegial Improvement Purpose
- ABC Engineering Insider Knowledge Competitive Advantage Prohibition in Design-Build RFP Conflict of Interest Disclosure Evolution Principle Invoked by ABC Engineering Post-Review Participation Assessment
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Information Asymmetry Established
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- ABC Engineering Peer Review Privileged Access Non-Exploitation in Design-Build Procurement
- One-Year Cooling-Off Period Assessment for Post-Review Competitive Participation Obligation Post-Peer-Review Design-Build Participation Conflict of Interest Assessment Obligation
- ABC Engineering No-Confidentiality-Agreement Conflict Management Non-Waiver ABC Engineering Post-Review Design-Build Participation Agency Approval Prerequisite
Triggering Events
- Design-Build_Invitation_Received
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- Information Asymmetry Established
- BER Precedent Cases Referenced
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Objectivity Invoked by Engineer A Independent External Peer Review Role Independent Review Integrity and Non-Exploitation of Privileged Access
- Conflict of Interest Disclosure in Advisory Engagements Invoked by Engineer A Peer Review Role Dual Role Appearance of Impropriety Avoidance Invoked by ABC Engineering Sequential Role Transition
- Post-Review Conflict of Interest Avoidance Invoked for ABC Engineering Design-Build Participation Fairness in Professional Competition Invoked by State Agency Procurement Integrity Concern
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- Information Asymmetry Established
- Design-Build_Invitation_Received
- BER Precedent Cases Referenced
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Peer Review Confidentiality Agreement Obligation No-Confidentiality-Agreement Peer Review Conflict Management Obligation
- ABC Engineering No-Confidentiality-Agreement Conflict Management Non-Waiver Agency Disclosure and Approval Obligation Before Post-Review Competitive Participation
- Peer Review Program Integrity and Collegial Improvement Purpose Independent Review Integrity and Non-Exploitation of Privileged Access
Triggering Events
- Design-Build_Invitation_Received
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Information Asymmetry Established
- BER Precedent Cases Referenced
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Agency Disclosure and Approval Obligation Before Post-Review Competitive Participation Conflict of Interest Disclosure Evolution Principle Invoked by ABC Engineering Post-Review Participation Assessment
- ABC Engineering Post-Review Design-Build Conflict Disclosure to State Agency Dual Role Appearance of Impropriety Avoidance Invoked by ABC Engineering Sequential Role Transition
- Post-Review Conflict of Interest Avoidance Invoked for ABC Engineering Design-Build Participation Procurement Integrity in Public Engineering Invoked by State Agency Design-Build RFP Process
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Information Asymmetry Established
- Design-Build_Invitation_Received
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Peer Review Program Collegial Improvement Purpose Invoked in Case Discussion Post-Review Conflict of Interest Avoidance Invoked for ABC Engineering Design-Build Participation
Triggering Events
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Design-Build_Invitation_Received
- Information Asymmetry Established
Triggering Actions
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- ABC Engineering Peer Review Privileged Access Non-Exploitation in Design-Build Procurement
- Cooling-Off Period Sufficiency Assessment Constraint Insider Knowledge Competitive Advantage Prohibition Constraint
Triggering Events
- State Agency Retains ABC Engineering
- RFP Issuance by State Agency
- Design-Build_Invitation_Received
Triggering Actions
- Accept Peer Review Lead Role
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Engineer A Lead Peer Reviewer Conflict of Interest Disclosure to Retaining Attorney or Agency Post-Review Design-Build Participation Conflict Disclosure Obligation
- Agency Disclosure and Approval Obligation Before Post-Review Competitive Participation Conflict of Interest Disclosure Evolution Principle Invoked by ABC Engineering Post-Review Participation Assessment
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Design-Build_Invitation_Received
- Information Asymmetry Established
- BER Precedent Cases Referenced
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Post-Review Conflict of Interest Avoidance in Design-Build Procurement ABC Engineering Post-Review Design-Build Participation Agency Approval Prerequisite
- Independent Review Integrity and Non-Exploitation of Privileged Access Fairness in Professional Competition Invoked by State Agency Procurement Integrity Concern
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- Information Asymmetry Established
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
Competing Warrants
- ABC Engineering No-Confidentiality-Agreement Ethical Obligation Persistence Constraint Peer Review Confidentiality Agreement Binding Constraint
- No-Confidentiality-Agreement Peer Review Conflict Management Obligation Peer Review Confidentiality Agreement Obligation
Triggering Events
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Information Asymmetry Established
- Design-Build_Invitation_Received
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- ABC Engineering Peer Review Scope-to-Procurement Nexus Assessment Post-Review Conflict of Interest Avoidance Invoked by ABC Engineering Design-Build Participation Decision
- Independent Review Integrity Non-Exploitation Invoked by ABC Engineering Post-Peer-Review Commercial Decision Procurement Integrity in Public Engineering Invoked by State Agency Design-Build RFP Process
Triggering Events
- RFP Issuance by State Agency
- Information Asymmetry Established
- Peer Review Completion Outcome
- BER Precedent Cases Referenced
Triggering Actions
- Accept Peer Review Lead Role
- Accept_Design-Build_Joint_Venture_Invitation
- Complete and Submit Peer Review
Competing Warrants
- Dual Role Appearance of Impropriety Avoidance Invoked by ABC Engineering Sequential Role Transition Jurisdiction-Specific Compliance Obligation Invoked for State Law Variability
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Information Asymmetry Established
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- Fairness in Professional Competition Invoked by State Agency Procurement Integrity Concern Independent Review Integrity Non-Exploitation Invoked by ABC Engineering Post-Peer-Review Commercial Decision
Triggering Events
- State Agency Retains ABC Engineering
- RFP Issuance by State Agency
- Information Asymmetry Established
- Peer Review Completion Outcome
Triggering Actions
- Accept Peer Review Lead Role
- Accept_Design-Build_Joint_Venture_Invitation
- Complete and Submit Peer Review
Competing Warrants
- Agency Disclosure and Approval Obligation Invoked by ABC Engineering Pre-Participation Decision Peer Review Independence and Integrity Invoked by ABC Engineering Post-Review Commercial Decision
Triggering Events
- State Agency Retains ABC Engineering
- Peer Review Completion Outcome
- RFP Issuance by State Agency
- Design-Build_Invitation_Received
- Information Asymmetry Established
- BER Precedent Cases Referenced
Triggering Actions
- Accept Peer Review Lead Role
- Complete and Submit Peer Review
- Accept_Design-Build_Joint_Venture_Invitation
Competing Warrants
- State Agency Procurement Integrity Preservation in Design-Build RFP ABC Engineering Post-Review Design-Build Participation Agency Approval Prerequisite
- Agency Disclosure and Approval Obligation Before Post-Review Competitive Participation Fairness in Professional Competition Invoked by State Agency Procurement Integrity Concern
- ABC Engineering Conflict of Interest Disclosure to State Agency Before Design-Build Participation ABC Engineering Peer Review Privileged Access Non-Exploitation Design-Build
- Conflict of Interest Disclosure Evolution Principle Invoked by ABC Engineering Post-Review Participation Assessment Post-Review Conflict of Interest Avoidance in Design-Build Procurement
Resolution Patterns 23
Determinative Principles
- Peer Review Program Collegial Improvement Purpose
- Post-Review Conflict of Interest Avoidance
- Systemic Consequentialist Integrity of Peer Review Programs
Determinative Facts
- ABC Engineering gained privileged access to design details through its peer review advisory role
- The Board's conditional approval was premised on agency consent and legal compliance rather than structural prohibition
- A one-year cooling-off period elapsed before the design-build proposal was submitted
Determinative Principles
- Dual Role Appearance of Impropriety Avoidance
- Jurisdiction-Specific Compliance Obligation
- Analytical Distinctness of Legal and Ethical Permissibility
Determinative Facts
- The Board conditioned approval on compliance with state laws and regulations
- State law may explicitly permit post-review competition without eliminating the appearance of informational advantage
- ABC Engineering held a privileged advisory role that created a reasonable public perception of unfair competitive advantage
Determinative Principles
- Virtue Ethics and Professional Character of Engineers in Public Trust Roles
- Spirit vs. Letter of Independent Peer Review Purpose
- Proactive Structural Safeguard Obligation Beyond Minimum Compliance
Determinative Facts
- Engineer A accepted the design-build joint venture invitation from XYZ Construction after completing the peer review
- The Board's analysis focused on procedural compliance — agency approval, cooling-off period, and state law conformity — rather than character
- The peer review program's foundational purpose is disinterested expert scrutiny for collegial improvement of public infrastructure
Determinative Principles
- Systemic Consequentialist Risk to Public Peer Review Program Integrity
- Case-by-Case Conditional Approval Framework Inadequacy
- Categorical Prospective Conflict-of-Interest Rule Necessity
Determinative Facts
- The Board's approval framework is conditional and case-by-case rather than categorical or prospective
- Future peer reviewers may unconsciously calibrate review recommendations to position their firms favorably in anticipated procurements
- State agencies may face pressure to approve post-review participation from technically attractive firms, biasing the approval mechanism itself
Determinative Principles
- Scope-to-procurement nexus: the tightness of the link between peer review outputs and RFP content determines the durability of informational advantage
- Cooling-off period necessity but insufficiency: elapsed time alone cannot neutralize advantage when privileged knowledge is structurally embedded in procurement documents
- Holistic conflict assessment: cooling-off period must be weighed alongside informational asymmetry, nexus specificity, and agency disclosure
Determinative Facts
- The peer review was narrowly scoped to clarifications and refinements that were directly incorporated into the design-build RFP
- One year elapsed between completion of the peer review and submission of the design-build proposal
- ABC Engineering's specific contributions — design details, specification choices, and refinement rationale — remain embedded in the RFP regardless of elapsed time
Determinative Principles
- Specificity of insider knowledge: narrowly scoped reviews produce precise, actionable competitive intelligence rather than general background familiarity
- Durability of conflict: the more directly peer review outputs are embedded in procurement documents, the more durable and acute the resulting conflict of interest
- Heightened disclosure and scrutiny obligation: greater specificity of conflict demands more rigorous agency review before participation is approved
Determinative Facts
- The peer review was limited to clarifications and refinements that were directly incorporated into the design-build RFP, not a broad or general design review
- ABC Engineering's contributions were surgically embedded in the RFP, giving it insider knowledge of why specifications were written as they were, what alternatives were rejected, and where design vulnerabilities or opportunities exist
- A broader review would have yielded general impressions that dissipate over time and are less directly translatable into competitive advantage
Determinative Principles
- Fairness in Professional Competition: qualified firms should not be arbitrarily excluded from public procurement, and formal eligibility matters
- Independent Review Integrity Non-Exploitation: knowledge gained in a privileged advisory role must not be leveraged for subsequent competitive advantage
- Substantive equality of informational access: true competitive fairness requires not merely formal permission to participate but genuine parity of information among competitors
Determinative Facts
- ABC Engineering enters the design-build competition with insider knowledge of the RFP's technical foundations that no other competitor possesses
- The board's conditional approval delegates resolution to the state agency but does not structurally equalize the informational playing field
- The competitive field is structurally unequal regardless of whether ABC Engineering is formally permitted to participate
Determinative Principles
- Scope-to-procurement nexus as primary determinant of conflict severity
- Independent Review Integrity Non-Exploitation
- Informational advantage specificity over breadth
Determinative Facts
- The peer review was narrowly scoped to clarifications and refinements that were directly incorporated into the RFP
- A broader review might have produced more diffuse knowledge that dissipates over time, whereas narrow outputs were precisely traceable to competitive documents
- ABC Engineering's specific contributions shaped the very procurement documents it sought to compete under
Determinative Principles
- Agency approval as necessary but not sufficient condition for ethical participation
- Fairness in Professional Competition as a third-party right
- Peer Review Independence and Integrity requiring potential categorical abstention
Determinative Facts
- The state agency's approval addresses administrative authorization but not substantive fairness to competing bidders
- A formal challenge would require assessment of whether additional remedial measures are necessary to level the competitive playing field
- Possible remedies include disclosure of peer review contributions to all competitors, information firewalls, and recusal of Engineer A from proposal development
Determinative Principles
- Agency Disclosure and Approval Obligation conditionally permitting participation
- Jurisdiction-Specific Compliance Obligation
- Fairness in Professional Competition supporting qualified firm access to public contracts
Determinative Facts
- The state agency approved ABC Engineering's participation in the design-build joint venture
- The work complies with applicable state laws and regulations
- A one-year cooling-off period elapsed between the peer review and the design-build proposal submission
Determinative Principles
- Agency Disclosure and Approval Obligation as procedural resolution mechanism
- Fairness in Professional Competition
- Independent Review Integrity Non-Exploitation
Determinative Facts
- The board resolved the conflict between two substantive principles by routing resolution through a third procedural principle — agency approval
- The agency may have its own procurement interests that bias its approval decision, compromising the neutrality of the procedural mechanism
- Treating agency consent as a proxy for ethical legitimacy converts a substantive conflict-of-interest question into a procedural compliance question
Determinative Principles
- Proactive and timely disclosure obligation: conflicts must be disclosed at the moment they are foreseeable, not merely when they become concrete
- Prevention over remediation: early disclosure preserves the agency's ability to impose conditions or select a different reviewer before the advantage accumulates
- Peer review program integrity: the independence and trustworthiness of the peer review process depends on upfront transparency about competing interests
Determinative Facts
- The peer review was explicitly scoped to clarifications and refinements feeding into a design-build RFP, making future procurement interest foreseeable at the time of engagement acceptance
- ABC Engineering waited until an RFP was issued before disclosing the conflict, allowing informational advantage to accumulate unchecked
- Early disclosure would have given the state agency the opportunity to impose conditions, require recusals, or select a different peer reviewer at the outset
Determinative Principles
- Faithful Agent and Trustee Duty to Client
- Ethical Obligation Independent of Contractual Formalization
- Informational Asymmetry as Material Ethical Harm Regardless of Agreement
Determinative Facts
- No formal confidentiality agreement was signed between ABC Engineering and the state agency
- The state agency extended privileged access to design details grounded in professional trust when retaining ABC Engineering for the peer review
- The informational asymmetry created by the peer review role is real and material regardless of whether it is contractually acknowledged
Determinative Principles
- Agency Disclosure and Approval Obligation: participation may be conditionally permitted with informed agency consent
- Peer Review Independence and Integrity: the integrity of the peer review process may require categorical abstention regardless of agency approval
- Independence of approval authority: the objectivity of consent as an ethical safeguard depends on the approving party being free from conflicting procurement interests
Determinative Facts
- The state agency has an interest in attracting qualified design-build proposals and may view ABC Engineering's technical familiarity as an asset rather than a disqualifying conflict
- This structural bias in the agency's approval calculus undermines the reliability of its consent as an ethical safeguard
- The agency both commissioned the peer review and issued the RFP, creating a dual role that compromises its objectivity as an approving authority
Determinative Principles
- Dual Role Appearance of Impropriety Avoidance
- Jurisdiction-Specific Compliance Obligation
- NSPE Code obligations exceeding minimum legal requirements
Determinative Facts
- State law may explicitly permit design-build participation by prior peer reviewers
- ABC Engineering served sequentially as independent reviewer and then as competitive bidder on the same project
- Legal permissibility was treated as a necessary but not sufficient condition for ethical conduct
Determinative Principles
- Deontological duty of faithful agency
- Categorical obligation independent of contractual instruments
- Prohibition on exploiting privileged advisory access for competitive self-interest
Determinative Facts
- No confidentiality agreement was signed between ABC Engineering and the state agency
- The state agency granted approval for ABC Engineering's participation
- The peer review relationship itself — not any contract — was the source of the ethical duty
Determinative Principles
- Systemic integrity of public peer review programs
- Consequentialist evaluation of long-term incentive structures
- Conditional approval as insufficient protection against strategic exploitation of advisory roles
Determinative Facts
- The board's framework conditionally permits post-review competition contingent on state agency consent
- Rational self-interest would incentivize firms to seek peer review roles strategically as intelligence-gathering opportunities
- A categorical prohibition or longer cooling-off period tied to review specificity would better protect systemic integrity
Determinative Principles
- Virtue ethics standard of professional character
- Genuine internalization of objectivity and public trust over rule compliance
- Self-directed constraint as expression of professional integrity
Determinative Facts
- ABC Engineering's peer review contributions were directly incorporated into the RFP it now seeks to compete under
- Engineer A accepted the design-build joint venture invitation rather than declining or imposing self-directed constraints
- The board's conditional approval framework addresses procedural permissibility but not dispositional character
Determinative Principles
- Proactive disclosure as expression of faithful agency
- Disclosure timing as ethically material to appearance of impropriety
- Transparency and client-interest prioritization over competitive advantage
Determinative Facts
- ABC Engineering did not proactively disclose the conflict at the moment XYZ Construction extended the design-build invitation
- Proactive disclosure would have given the state agency the opportunity to impose conditions or information firewalls before any informational asymmetry was exploited
- NSPE Code Section II.4.a requires disclosure of known or potential conflicts of interest
Determinative Principles
- Cooling-off period validity contingent on knowledge becoming stale or neutralized
- Dual Role Appearance of Impropriety Avoidance
- Informational asymmetry persistence despite temporal gap
Determinative Facts
- The RFP was issued one year after the peer review was completed, which the board treated as a relevant mitigating factor
- The design details and specifications ABC Engineering contributed during the peer review remained substantially unchanged in the RFP
- The one-year period may have satisfied a formal threshold without eliminating the substantive informational asymmetry
Determinative Principles
- Faithful Agency (ethical duty of trust persists independently of contractual instruments)
- Non-waivable confidentiality obligation arising from privileged advisory relationship
- Procedural gap versus substantive license distinction
Determinative Facts
- No formal confidentiality agreement was signed between ABC Engineering and the state agency
- ABC Engineering was retained as a trusted advisor in a peer review capacity, creating a trust relationship
- The Board's conditional approval implicitly assumed confidentiality would be honored but did not make that assumption explicit
Determinative Principles
- Structural conflict of interest created by authoring the competitive framework itself, not merely gaining general project familiarity
- Informational asymmetry that a cooling-off period cannot neutralize when contributions are formative rather than incidental
- Post-Review Conflict of Interest Avoidance requiring rigorous assessment of whether remediation is even possible
Determinative Facts
- The peer review was specifically limited to clarifications and refinements that were directly incorporated into the design-build RFP
- ABC Engineering's contributions shaped the evaluative criteria, technical specifications, and design trade-offs embedded in the RFP itself
- A one-year cooling-off period elapsed between completion of the peer review and submission of the design-build proposal
Determinative Principles
- Proactive and timely disclosure obligation under Code Section II.4.a, triggered at the earliest foreseeable moment of conflict
- Structural compromise of the approving authority when the agency has dual roles as peer review client and procurement issuer
- Independent ethical scrutiny requirement when the consenting party is itself conflicted
Determinative Facts
- The state agency served simultaneously as the client that retained ABC Engineering for the peer review and as the procuring authority issuing the design-build RFP
- Engineer A did not disclose the potential conflict at the time of accepting the peer review engagement, nor when XYZ Construction extended the design-build invitation, but only after the RFP was issued
- The agency has an institutional interest in the success of the procurement that may bias its willingness to exclude a technically qualified firm
Decision Points
View ExtractionShould Engineer A and ABC Engineering disclose their prior peer review role to the state agency immediately upon receiving XYZ Construction's invitation, wait to disclose during the formal proposal submission, or treat the original peer review acceptance as the point at which disclosure was required?
- Disclose Immediately Upon Receiving Invitation
- Disclose During Proposal Submission
- Disclose At Peer Review Acceptance
Is it ethical for Engineer A and ABC Engineering to participate in the design-build joint venture with XYZ Construction and submit a proposal for the major road transportation project, given that the peer review outputs were directly incorporated into the RFP and approximately one year elapsed between completion of the review and issuance of the RFP?
- Accept With Disclosure And Agency Approval
- Decline Due To Structural Informational Advantage
- Accept With Disclosure Without Extra Measures
Should Engineer A and ABC Engineering treat their non-exploitation obligation as fully binding despite the absence of a confidentiality agreement — segregating peer review knowledge from proposal development — apply it only as a best-practice standard, or decline participation entirely because the absence of a formal agreement makes the knowledge boundary unenforceable?
- Treat Obligation As Binding Without Agreement
- Treat Obligation As Best-Practice Standard
- Decline Without Confidentiality Agreement
Should Engineer A and ABC Engineering accept the design-build joint venture invitation and submit a proposal for the same project they peer-reviewed, given the informational asymmetry created by their privileged advisory access?
- Disclose Immediately And Seek Approval
- Decline Due To Informational Asymmetry
- Proceed Relying On Elapsed Time
At what point was Engineer A obligated to disclose a foreseeable interest in future procurement opportunities related to the same project — at the moment of accepting the peer review engagement, or only upon receipt of the design-build invitation after the RFP was issued?
- Disclose At Peer Review Acceptance
- Disclose Upon Receiving Invitation
- Disclose Only At Proposal Submission
Is state agency approval — from an authority that is both the peer review client and the design-build procurement issuer — a sufficient ethical safeguard to permit ABC Engineering's post-review competitive participation, or must additional independent remediation measures be imposed to protect the integrity of the procurement and the fairness of competition?
- Obtain Agency Approval And Proceed
- Obtain Approval And Add Remedial Measures
- Seek Independent Authority Approval
Should Engineer A have disclosed any foreseeable interest in future design-build procurement at the time of accepting the peer review engagement and again upon receiving the invitation, or only upon receiving the invitation when the conflict became concrete?
- Disclose At Engagement And Upon Invitation
- Disclose Only Upon Receiving Invitation
- Treat Peer Review Acceptance As Sufficient
Would it be ethical for Engineer A and ABC Engineering to accept the design-build joint venture invitation and submit a proposal for the major road transportation project, given that ABC Engineering's peer review contributions — scoped to clarifications and refinements — were directly incorporated into the RFP under which it now seeks to compete, and that one year elapsed between completion of the peer review and issuance of the RFP?
- Accept With Full Disclosure And Firewalls
- Accept Relying On Cooling-Off Period
- Decline Due To Structural Conflict
When the state agency receives ABC Engineering's disclosure that it served as lead peer reviewer on the same project for which it now seeks to compete in a design-build procurement, what approval standard and remedial conditions — if any — should the agency impose to preserve procurement integrity and protect competing firms from the informational asymmetry created by ABC Engineering's privileged advisory access?
- Approve With Mandatory Conditions And Firewalls
- Approve Based On Disclosure Alone
- Refer To Independent Ethics Review
Should Engineer A disclose the peer review conflict immediately upon receiving the design-build invitation and seek agency approval before proceeding, disclose within the formal proposal submission, or decline the joint venture entirely?
- Disclose Immediately And Impose Firewalls
- Decline Due To RFP Conflict
- Disclose Within Proposal Submission
At what point was Engineer A obligated to disclose any foreseeable interest in future procurement opportunities related to the same project — at the time of accepting the peer review engagement, or only upon receipt of the design-build RFP — and does the absence of a formal confidentiality agreement affect the scope or timing of that disclosure duty?
- Disclose Upfront At Engagement Acceptance
- Accept Without Upfront Disclosure
- Disclose Upon Receiving Invitation
Is state agency approval a sufficient ethical safeguard for ABC Engineering's post-peer-review design-build participation, given that the agency occupies a structurally compromised position as both the peer review client and the procurement authority, and given the systemic risk that conditional permissibility creates for the long-term integrity of public peer review programs?
- Seek Approval With Enhanced Safeguards
- Seek Standard Agency Approval
- Decline Due To Agency Conflict Of Interest
Case Narrative
Phase 4 narrative construction results for Case 96
Opening Context
You are a licensed engineer at ABC Engineering, a firm that has secured a position of significant public trust as the city's designated peer review authority for private development projects. What began as a straightforward professional arrangement has evolved into something far more complicated: your firm simultaneously collects fees from the very developers whose work you are officially tasked with independently evaluating. Now, in the course of a routine peer review, you have uncovered a serious safety violation — and the weight of that discovery is compounded by the uncomfortable reality that the responsible party is also a paying client.
Characters (10)
An engineering firm occupying a compromised dual position as both the city's designated engineer for development oversight and a paid service provider to the very private developers it was tasked with reviewing, creating an irreconcilable conflict of interest.
- To leverage its authoritative city engineer role as a competitive marketing advantage to attract and retain private developer clients, prioritizing business growth over the impartial public-service obligations inherent to its municipal appointment.
- To maintain firm reputation and operational continuity while ideally cooperating with Engineer A to correct identified deficiencies and avoid regulatory or public exposure of the violations.
- To fulfill professional peer review responsibilities while navigating the ethical conflict between honoring a signed confidentiality agreement and upholding the overriding obligation to report conditions that could endanger the public.
Engineer B's firm was the subject of a peer review visit by Engineer A, during which technical documentation revealed potential violations of state and local safety code requirements, triggering obligations for Engineer A to discuss findings with Engineer B and seek resolution before escalating to authorities.
Firm A was engaged by the city to provide design review and construction inspection for private development projects while simultaneously providing design and inspection services to those same private developers, using its city engineer position as a marketing tool and creating an irreconcilable conflict of interest between its obligations to the city and to private developer clients.
An engineering firm that, having previously conducted an independent external peer review of a project, subsequently agreed to join a design-build joint venture for that same project, raising serious ethical questions about the exploitation of confidential information gained during the review.
- To capitalize on established project familiarity and a pre-existing relationship with XYZ Construction to secure a lucrative design-build contract, while bearing the ethical obligation to disclose and resolve the conflict of interest arising from its prior privileged access.
XYZ Construction invited ABC Engineering — a firm that previously conducted an independent external peer review — to join a design-build joint venture, leveraging the engineering firm's prior project familiarity while generating ethical obligations for ABC Engineering regarding conflict-of-interest disclosure and agency approval.
The city engaged Firm A to provide design review and construction inspection for private development projects under local ordinance, bearing authority over the plan review process and obligations to ensure impartial, conflict-free oversight of private development in the public interest.
Engineer A, as owner of ABC Engineering, is assigned as lead engineer on the independent external peer review of the major state-funded transportation project design, and later is invited by XYZ Construction to participate in a design-build joint venture for the same project, generating conflict-of-interest obligations.
ABC Engineering, having completed the independent external peer review of the state transportation project, is invited by XYZ Construction to join a design-build joint venture and submit a proposal for the same project, bearing obligations to obtain agency approval, comply with conflict-of-interest laws, and ensure prior review knowledge does not confer unfair competitive advantage.
The state agency retains ABC Engineering for an independent external peer review of its major transportation project design, then approximately one year later issues a design-build RFP for the same project, creating the procurement context in which ABC Engineering's prior reviewer role generates a conflict-of-interest concern.
XYZ Construction invites ABC Engineering to participate in a design-build joint venture and submit a proposal for the major road transportation project for which ABC Engineering previously served as independent external peer reviewer, triggering the conflict-of-interest analysis.
States (10)
Event Timeline (27)
| # | Event | Type |
|---|---|---|
| 1 | The case centers on Engineer A, who faces a complex ethical dilemma involving the discovery of safety violations during a peer review process while simultaneously holding dual professional roles. This conflict of interest between public safety obligations and professional confidentiality forms the core tension of the case. | state |
| 2 | Engineer A accepts the responsibility of leading a peer review, taking on a formal oversight role that carries significant professional and ethical obligations. This decision places Engineer A in a position of trust, requiring impartial evaluation of another engineer's work. | action |
| 3 | Engineer A finalizes and submits the peer review findings, fulfilling the immediate professional obligation of the assignment. The submission marks a critical juncture, as any identified deficiencies or safety concerns now become part of the official record. | action |
| 4 | Engineer A agrees to join a design-build joint venture as a consultant, adding a private sector role to existing professional responsibilities. This decision introduces a potential conflict of interest that will complicate Engineer A's ability to act impartially in subsequent situations. | action |
| 5 | Engineer A simultaneously serves as a City Engineer in a public capacity while consulting for a private developer, creating an inherently conflicted dual role. This arrangement raises serious ethical concerns about divided loyalties, as Engineer A's decisions could benefit private interests at the expense of public welfare. | action |
| 6 | Engineer A must weigh the ethical duty to protect public safety against the professional obligation to maintain peer review confidentiality after discovering safety violations. This pivotal decision forces a direct confrontation between two fundamental engineering ethics principles, with potentially serious consequences either way. | action |
| 7 | The Board of Ethical Review references prior case precedents to provide a consistent and principled framework for evaluating Engineer A's situation. These precedents serve as critical guideposts, helping to establish how established ethical standards apply to the specific conflicts present in this case. | automatic |
| 8 | A state agency formally engages ABC Engineering firm, establishing an official professional relationship that adds another layer of accountability to the case. This retention is significant because it introduces institutional oversight and further defines the professional boundaries within which the engineers involved must operate. | automatic |
| 9 | Peer Review Completion Outcome | automatic |
| 10 | RFP Issuance by State Agency | automatic |
| 11 | Design-Build Invitation Received | automatic |
| 12 | Information Asymmetry Established | automatic |
| 13 | Tension between Post-Review Design-Build Participation Conflict Disclosure Obligation and Insider Knowledge Competitive Advantage Prohibition Constraint | automatic |
| 14 | Tension between One-Year Cooling-Off Period Assessment for Post-Review Competitive Participation Obligation and Cooling-Off Period Sufficiency Assessment Constraint | automatic |
| 15 | Should Engineer A and ABC Engineering proactively disclose to the state agency their prior peer review role — including the privileged access to construction plans and specifications obtained during that review — before accepting XYZ Construction's design-build invitation, and should that disclosure have occurred at the moment the invitation was received rather than at a later stage? | decision |
| 16 | Is it ethical for Engineer A and ABC Engineering to participate in the design-build joint venture with XYZ Construction and submit a proposal for the major road transportation project, given that the peer review outputs were directly incorporated into the RFP and approximately one year elapsed between completion of the review and issuance of the RFP? | decision |
| 17 | Does the absence of a formal confidentiality agreement eliminate ABC Engineering's ethical duty to treat privileged design knowledge gained during the peer review as non-exploitable in a subsequent competitive procurement, or does that duty persist independently of any contractual instrument — and what affirmative steps must ABC Engineering take to honor that duty even if agency approval is granted? | decision |
| 18 | Should Engineer A and ABC Engineering accept the design-build joint venture invitation and submit a proposal for the same project they peer-reviewed, given the informational asymmetry created by their privileged advisory access? | decision |
| 19 | At what point was Engineer A obligated to disclose a foreseeable interest in future procurement opportunities related to the same project — at the moment of accepting the peer review engagement, or only upon receipt of the design-build invitation after the RFP was issued? | decision |
| 20 | Is state agency approval — from an authority that is both the peer review client and the design-build procurement issuer — a sufficient ethical safeguard to permit ABC Engineering's post-review competitive participation, or must additional independent remediation measures be imposed to protect the integrity of the procurement and the fairness of competition? | decision |
| 21 | Should Engineer A proactively disclose to the state agency, at the time of accepting the peer review engagement and again upon receiving the design-build invitation from XYZ Construction, any foreseeable or actual interest in future procurement opportunities related to the same project — rather than relying on the agency to independently identify and evaluate the conflict? | decision |
| 22 | Would it be ethical for Engineer A and ABC Engineering to accept the design-build joint venture invitation and submit a proposal for the major road transportation project, given that ABC Engineering's peer review contributions — scoped to clarifications and refinements — were directly incorporated into the RFP under which it now seeks to compete, and that one year elapsed between completion of the peer review and issuance of the RFP? | decision |
| 23 | When the state agency receives ABC Engineering's disclosure that it served as lead peer reviewer on the same project for which it now seeks to compete in a design-build procurement, what approval standard and remedial conditions — if any — should the agency impose to preserve procurement integrity and protect competing firms from the informational asymmetry created by ABC Engineering's privileged advisory access? | decision |
| 24 | Should Engineer A and ABC Engineering participate in the design-build joint venture and submit a proposal for the major road transportation project, given that ABC Engineering conducted the peer review whose outputs were directly incorporated into the RFP, and if so, under what conditions? | decision |
| 25 | At what point was Engineer A obligated to disclose any foreseeable interest in future procurement opportunities related to the same project — at the time of accepting the peer review engagement, or only upon receipt of the design-build RFP — and does the absence of a formal confidentiality agreement affect the scope or timing of that disclosure duty? | decision |
| 26 | Is state agency approval a sufficient ethical safeguard for ABC Engineering's post-peer-review design-build participation, given that the agency occupies a structurally compromised position as both the peer review client and the procurement authority, and given the systemic risk that conditional permissibility creates for the long-term integrity of public peer review programs? | decision |
| 27 | The Peer Review Program Collegial Improvement Purpose principle and the Post-Review Conflict of Interest Avoidance principle exist in structural tension that the Board's conditional approval does not | outcome |
Decision Moments (12)
- Immediately disclose to the state agency, upon receiving XYZ Construction's invitation, the full scope of the prior peer review role — including the nature of privileged access to construction plans and specifications and the direct incorporation of peer review outputs into the RFP — and refrain from accepting the invitation until the agency provides informed approval Actual outcome
- Disclose the prior peer review role to the state agency as part of the formal proposal submission process, treating the RFP's public issuance as the appropriate trigger for conflict disclosure rather than the private receipt of XYZ Construction's invitation, on the grounds that the conflict only becomes procurement-relevant once a proposal is formally contemplated
- Disclose the prior peer review role to the state agency at the time of accepting the original peer review engagement — before any design-build procurement is announced — on the grounds that the peer review scope was explicitly tied to RFP preparation, making future procurement interest foreseeable from the outset and requiring upfront transparency to preserve the independence of the review
- Accept the design-build joint venture invitation and submit a proposal after disclosing the prior peer review role to the state agency, obtaining the agency's informed approval, confirming compliance with applicable state conflict-of-interest law, and implementing internal information safeguards — such as recusing Engineer A from proposal sections directly drawing on peer review knowledge — to mitigate the informational asymmetry Actual outcome
- Decline the design-build joint venture invitation entirely, on the grounds that the narrow scope of the peer review — with its outputs directly incorporated into the RFP — created a structural informational advantage that no cooling-off period or agency approval can adequately remediate, and that participation would undermine the integrity of both the procurement and the peer review program regardless of procedural clearances
- Accept the design-build joint venture invitation and submit a proposal after disclosing the prior peer review role to the state agency and confirming state law compliance, without imposing additional internal safeguards beyond what the agency requires, on the grounds that the one-year cooling-off period and the limited scope of the peer review are sufficient to neutralize any competitive advantage and that agency approval constitutes adequate ethical clearance
- Treat the ethical non-exploitation obligation as fully operative regardless of the absence of a confidentiality agreement — affirmatively segregating peer review knowledge from proposal development through documented internal information barriers, recusing Engineer A from proposal sections that draw on peer review findings, and disclosing to the state agency the specific nature of the informational asymmetry so the agency can assess whether additional remediation is required before approving participation Actual outcome
- Treat the non-exploitation obligation as a best-practice standard rather than a binding ethical duty in the absence of a confidentiality agreement — applying ordinary firm-wide conflict-of-interest screening protocols to the design-build proposal without imposing additional peer-review-specific restrictions, on the grounds that the absence of a formal agreement means the information is not legally privileged and that standard professional judgment is sufficient to manage any residual ethical concern
- Decline to participate in the design-build joint venture on the grounds that, without a confidentiality agreement to define and limit the scope of privileged information, the boundary between permissible general project familiarity and impermissible exploitation of insider knowledge is too uncertain to manage reliably — and that the integrity of the peer review program and the firm's professional reputation are better protected by categorical abstention than by attempting to self-police an undefined non-exploitation obligation
- Disclose the peer review conflict to the state agency immediately upon receiving the design-build invitation, seek explicit agency approval, and implement internal information firewalls separating the peer review team from the proposal development team before submitting a design-build proposal Actual outcome
- Decline the design-build joint venture invitation entirely on the grounds that the peer review's direct contributions to the RFP create an informational asymmetry that no cooling-off period or agency approval can adequately remediate, thereby preserving the integrity of the advisory relationship and the peer review program
- Accept the design-build invitation and proceed with proposal development in reliance on the one-year elapsed period and the absence of a formal confidentiality agreement, treating the peer review engagement as concluded and the information gained as no longer conferring a material competitive advantage
- Disclose to the state agency any foreseeable interest in future design-build procurement opportunities on the same project at the moment of accepting the peer review engagement, before any privileged design information is accessed
- Disclose the conflict of interest to the state agency immediately upon receiving the design-build joint venture invitation from XYZ Construction, before taking any further steps toward proposal development, and seek explicit agency approval as a condition of participation Actual outcome
- Treat the disclosure obligation as triggered only upon formal submission of a design-build proposal, relying on the one-year elapsed period and the public nature of the RFP as sufficient to neutralize any prior informational advantage, and disclose the peer review history in the proposal documents themselves
- Obtain state agency approval and proceed with design-build proposal submission, treating the agency's informed consent and compliance with applicable state law as sufficient ethical authorization for participation Actual outcome
- Obtain state agency approval and additionally implement self-directed remedial measures — including an information firewall between the peer review team and the proposal development team, recusal of Engineer A from proposal sections drawing on peer review knowledge, and voluntary disclosure to all competing firms of the specific design clarifications and refinements ABC Engineering contributed — before submitting a design-build proposal
- Seek approval from an independent reviewing authority — such as a state ethics board, inspector general, or independent procurement officer with no stake in the design-build outcome — rather than relying solely on the state agency's consent, given the agency's structurally compromised dual role as both peer review client and procurement issuer
- Disclose to the state agency at the time of accepting the peer review engagement any foreseeable interest in future design-build procurement on the same project, and again immediately upon receiving the design-build invitation from XYZ Construction, seeking explicit informed agency approval before proceeding Actual outcome
- Disclose the conflict to the state agency upon receiving the design-build invitation — treating that moment as the point at which the conflict becomes concrete and actionable — and seek agency approval before submitting any proposal
- Decline the design-build joint venture invitation entirely, treating the peer review role as categorically precluding subsequent competitive participation on the same project regardless of agency approval or elapsed time
- Accept the design-build joint venture invitation, disclose the peer review conflict fully to the state agency, obtain explicit agency approval, and implement internal information firewalls separating the peer review team from the proposal development team before submitting any proposal Actual outcome
- Accept the design-build joint venture invitation and disclose the peer review role to the state agency, relying on the one-year cooling-off period and agency consent as sufficient ethical safeguards without imposing additional internal structural constraints on proposal development
- Decline the design-build joint venture invitation on the grounds that ABC Engineering's peer review contributions were directly incorporated into the RFP, creating a structural informational asymmetry that no cooling-off period or agency approval can adequately remediate
- Approve ABC Engineering's participation conditioned on mandatory information firewalls between the peer review team and the proposal development team, disclosure of ABC Engineering's specific peer review contributions to all competing firms, and recusal of Engineer A from proposal sections directly drawing on peer review knowledge Actual outcome
- Approve ABC Engineering's participation on the basis of the one-year cooling-off period and ABC Engineering's disclosure alone, treating informed agency consent as a sufficient procedural safeguard without imposing additional structural remediation requirements
- Refer the approval decision to an independent procurement officer or ethics board with no stake in the design-build outcome, and withhold agency approval pending that independent determination, on the grounds that the agency's dual role as peer review client and procurement authority structurally compromises its ability to render an objective consent decision
- Proactively disclose the peer review conflict to the state agency immediately upon receiving the design-build invitation, seek explicit written agency approval before proceeding, and impose internal information firewalls separating the peer review team from the proposal development team Actual outcome
- Decline the design-build joint venture invitation entirely on the grounds that ABC Engineering's peer review contributions were directly incorporated into the RFP, creating a structural conflict of interest that no cooling-off period or agency approval can adequately remediate
- Accept the design-build invitation and disclose the prior peer review role to the state agency in the proposal submission itself, relying on the one-year elapsed period and the agency's own familiarity with the engagement as constructive notice sufficient to satisfy the disclosure obligation without seeking separate pre-participation approval
- Disclose to the state agency, at the time of accepting the peer review engagement, any foreseeable firm interest in future design-build procurement opportunities on the same project, and request the agency's acknowledgment of that potential conflict as a condition of proceeding Actual outcome
- Accept the peer review engagement without upfront disclosure of potential future procurement interest, on the grounds that no specific design-build opportunity exists at that time and that disclosure obligations under Code Section II.4.a are triggered only by known or concrete conflicts rather than speculative future interests
- Accept the peer review engagement and disclose the potential conflict only upon receipt of the design-build invitation from XYZ Construction, treating that moment as the point at which the conflict becomes sufficiently concrete to trigger the Code Section II.4.a disclosure obligation
- Seek state agency approval for design-build participation, disclose the full scope of peer review contributions to the agency, and accept participation only if the agency's approval is granted through a procurement officer or process independent of the design-build procurement decision
- Seek and obtain state agency approval for design-build participation through the agency's standard procurement authorization process, treating that approval — combined with state law compliance and the one-year cooling-off period — as sufficient ethical authorization to proceed Actual outcome
- Decline the design-build joint venture invitation on the grounds that the state agency's structural conflict of interest as both peer review client and procurement authority renders its approval an unreliable ethical safeguard, and that the systemic risk to peer review program integrity requires categorical abstention regardless of agency consent
Sequential action-event relationships. See Analysis tab for action-obligation links.
- Accept Peer Review Lead Role Complete and Submit Peer Review
- Complete and Submit Peer Review Accept_Design-Build_Joint_Venture_Invitation
- Accept_Design-Build_Joint_Venture_Invitation Operate Dual Role as City Engineer and Private Developer Consultant
- Operate Dual Role as City Engineer and Private Developer Consultant Decide Whether to Breach Confidentiality to Report Safety Violations
- Decide Whether to Breach Confidentiality to Report Safety Violations BER Precedent Cases Referenced
- conflict_1 decision_1
- conflict_1 decision_2
- conflict_1 decision_3
- conflict_1 decision_4
- conflict_1 decision_5
- conflict_1 decision_6
- conflict_1 decision_7
- conflict_1 decision_8
- conflict_1 decision_9
- conflict_1 decision_10
- conflict_1 decision_11
- conflict_1 decision_12
- conflict_2 decision_1
- conflict_2 decision_2
- conflict_2 decision_3
- conflict_2 decision_4
- conflict_2 decision_5
- conflict_2 decision_6
- conflict_2 decision_7
- conflict_2 decision_8
- conflict_2 decision_9
- conflict_2 decision_10
- conflict_2 decision_11
- conflict_2 decision_12
Key Takeaways
- Participation in peer review programs creates inherent competitive intelligence asymmetries that cooling-off periods alone cannot fully neutralize, leaving a structural ethical gap that procedural remedies incompletely address.
- The collegial improvement purpose of peer review is fundamentally undermined when reviewed organizations must weigh disclosure risks against the competitive consequences of granting rivals privileged access to their operational knowledge.
- Conditional approvals in ethics stalemates often defer rather than resolve the core tension, creating precedent ambiguity that can incentivize strategic manipulation of review participation for competitive gain.