Step 4: Full View

Entities, provisions, decisions, and narrative

Selection of Firm—FOIA Request
Step 4 of 5

259

Entities

3

Provisions

1

Precedents

17

Questions

21

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
A multi-party ethical stalemate in which Engineer B's FOIA-based transparency right, Engineer A's competitive fairness interest, and the state agency's procurement integrity obligation each remain independently valid but structurally incompatible. The Board's conclusion that the FOIA request was 'ethical' applies only narrowly to the act of filing, while simultaneously preserving unresolved tensions about downstream use, timing impropriety, agency disclosure responsibility, and Engineer A's self-protection duty — none of which are definitively adjudicated or transferred to a resolving authority. The stalemate is institutionalized rather than resolved: the Board acknowledges the appearance of impropriety without declaring a violation, endorses a timing recommendation without making it a binding rule, and distributes ethical responsibility across all parties without specifying which obligation prevails when they conflict.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
Provision (e.g., I.1.) Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis Entity (hidden by default)
Edges:
informs answered by applies to
Provisions (3)
View Extraction
II.2.a. Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.
How this applies in the case (showing 3 of 20)
Obligation
Engineer A Present Case Public Procurement Qualifications Confidentiality Self-Protection
Engineer A's qualifications submission relates to demonstrating competence in specific technical fields, which is the subject of II.2.a.
Action
Engineer A Submits RFQ Qualifications
This provision governs whether Engineer A is qualified by education or experience for the assignment being sought through the RFQ submission.
State
Engineer A Qualifications Submitted to Public RFQ
The qualifications submission directly reflects whether Engineer A is undertaking assignments only when qualified in the specific technical fields involved.
Obligation (3)
  • Engineer A Present Case Public Procurement Qualifications Confidentiality Self-Protection
    Engineer A's qualifications submission relates to demonstrating competence in specific technical fields, which is the subject of II.2.a.
  • Engineer A Public Procurement Qualifications Confidentiality Self-Protection Obligation
    The qualifications submitted to the public agency reflect Engineer A's education and experience in specific technical fields as required by II.2.a.
  • Engineer B Present Case Public Procurement Misrepresentation Check Transparency Recognition
    The openness of the procurement process ensures that qualifications submissions accurately reflect engineers' competence as required by II.2.a.
Action (2)
  • Engineer A Submits RFQ Qualifications
    This provision governs whether Engineer A is qualified by education or experience for the assignment being sought through the RFQ submission.
  • Engineer B Submits Own Qualifications
    This provision governs whether Engineer B is qualified by education or experience for the assignment being sought through their own qualifications submission.
State (3)
  • Engineer A Qualifications Submitted to Public RFQ
    The qualifications submission directly reflects whether Engineer A is undertaking assignments only when qualified in the specific technical fields involved.
  • Engineer B Competitor Qualification FOIA Acquisition
    Engineer B reviewing competitor qualifications before submitting their own raises questions about whether Engineer B is ensuring their own qualifications meet the required technical standards.
  • Engineer B Asymmetric Competitive Advantage Post-FOIA
    Using competitor qualification details to shape one's own submission could allow an engineer to misrepresent or overstate qualifications relative to the specific technical fields required.
Constraint (2)
  • Engineer A Public Procurement Qualifications Confidentiality Self-Protection BER 10-8
    This provision requires engineers to be qualified for assignments, directly relating to the qualifications submission Engineer A must prepare honestly and accurately for the public agency.
  • Engineer A Public Procurement Submission FOIA Exposure Self-Protection Constraint Instance
    The requirement to submit genuine qualifications for specific technical fields means Engineer A must recognize those submissions are subject to public disclosure under FOIA.
Principle (3)
  • FOIA Competitor Intelligence Ethical Use Invoked By Engineer B
    Engineer B's review of competitor qualifications relates to assessing whether firms are qualified for the specific technical assignment.
  • Free and Open Competition Boundary Condition Invoked in Engineering Practice Context
    Qualification requirements for undertaking assignments are part of the broader framework governing legitimate competition in engineering practice.
  • Public Welfare Paramount Invoked as Rationale for Public Procurement System Design
    Ensuring engineers are qualified before undertaking assignments directly supports the public interest rationale underlying the procurement system design.
Role (2)
  • Engineer A Public RFQ Submitting Engineer
    Engineer A must ensure his qualifications submission accurately reflects competence in the technical fields required by the RFQ.
  • Engineer B Present Case Public Procurement Competitor
    Engineer B must ensure his own qualifications submission reflects genuine competence in the relevant technical fields when competing for the public contract.
Event (1)
  • Engineer A's Qualifications Exposed to Competitor
    The disclosure of Engineer A's qualifications directly relates to the assessment of whether the engineer is qualified for the specific technical assignment being competed for.
Resource (1)
  • Qualification-Based Selection Procurement Law - State RFQ Procedures
    The RFQ process directly evaluates whether firms are qualified, making this provision relevant to the submission of qualifications under state procurement law.
Capability (3)
  • Engineer B FOIA Competitive Ethics Assessment
    Engineer B must assess whether his FOIA conduct aligns with undertaking assignments only when qualified and competing fairly within that standard.
  • Engineer B Present Case Engineering Profession Free Competition Legal Framework Recognition
    Recognizing the legal and ethical framework for competition relates to understanding qualification-based assignment standards.
  • Engineer B Present Case Honorable Procurement Conduct Self-Regulation Capability Instance
    Honorable procurement conduct includes competing on the basis of genuine qualifications rather than improperly obtained competitor information.
II.4. Engineers shall act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 31)
Obligation
Engineer B BER 93-3 Client Confidentiality Instruction Faithful Agent Compliance
II.4. directly requires engineers to act as faithful agents or trustees, which is the basis of Engineer B's obligation to follow the client's confidentiality instruction.
Action
Engineer B Files FOIA Request
This provision applies because filing a FOIA request to obtain a competitor's qualifications may conflict with Engineer B's duty to act as a faithful agent or trustee to their employer or client.
State
BER 93-3 Franchiser-Engineer B Covert Transition Engagement
Engineer B's duty as faithful agent to the franchiser directly governs the propriety of engaging with a new client while another engineer's contract is still active.
Obligation (4)
  • Engineer B BER 93-3 Client Confidentiality Instruction Faithful Agent Compliance
    II.4. directly requires engineers to act as faithful agents or trustees, which is the basis of Engineer B's obligation to follow the client's confidentiality instruction.
  • Engineer B BER 93-3 Faithful Agent Client Interest Primacy Over Altruistic Disclosure
    II.4. requires Engineer B to prioritize the client's interests over personal impulses, directly grounding this obligation.
  • Engineer B Competitive Procurement Fairness Obligation
    Acting as a faithful agent includes conducting oneself fairly in procurement processes that affect client and public interests.
  • Engineer B Honorable Procurement Conduct Obligation
    II.4. requires honorable and trustworthy conduct toward clients and the broader process, directly supporting this obligation.
Action (2)
  • Engineer B Files FOIA Request
    This provision applies because filing a FOIA request to obtain a competitor's qualifications may conflict with Engineer B's duty to act as a faithful agent or trustee to their employer or client.
  • BER Case 93-3: Engineer B Discloses Relationship to Engineer A
    This provision governs Engineer B's obligation to act faithfully toward their client by disclosing any relationship with Engineer A that could affect their duties.
State (3)
  • BER 93-3 Franchiser-Engineer B Covert Transition Engagement
    Engineer B's duty as faithful agent to the franchiser directly governs the propriety of engaging with a new client while another engineer's contract is still active.
  • BER 93-3 Faithful Agent Duty Activation
    This entity directly describes Engineer B's faithful agent and trustee obligation to the franchiser, which is the core subject of provision II.4.
  • Public Procurement System Public Interest Alignment
    Acting as a faithful agent includes serving the public interest within the procurement system, linking Engineer B's conduct to broader obligations under II.4.
Constraint (2)
  • Engineer B BER 93-3 Faithful Agent Client Non-Disclosure Instruction Compliance
    This provision directly creates the faithful agent duty that constrains Engineer B to comply with the franchiser client's explicit instruction not to disclose information.
  • Engineer B BER 93-3 Altruistic Motive Faithful Agent Duty Non-Override
    This provision establishes the faithful agent duty that cannot be overridden by Engineer B's altruistic motivation to inform Engineer A of a new engagement.
Principle (5)
  • Client Interest Primacy Over Personal Advantage Invoked in BER 93-3 Analysis
    The faithful agent obligation requires prioritizing client interests over personal advantage, directly embodied in the BER 93-3 analysis.
  • Faithful Agent Obligation Invoked as Analogical Bridge to Present Case
    II.4 is the direct source of the faithful agent duty that the Board uses as an analogical bridge from BER 93-3 to the present case.
  • Client Loyalty Violated by Unauthorized Disclosure in BER 93-3
    Engineer B's unauthorized disclosure in BER 93-3 violated the faithful agent duty to the client embodied in II.4.
  • Benevolent Motive Non-Excuse Invoked in BER 93-3 Faithful Agent Analysis
    II.4 establishes that faithful agent duties apply regardless of the engineer's personal motivation, supporting the finding that good intent does not excuse the breach.
  • Good Intent Does Not Cure Procedural Impropriety Invoked in BER 93-3 Analogy
    The faithful agent standard under II.4 underpins the Board's conclusion that benevolent intent does not cure a violation of client loyalty obligations.
Role (4)
  • Engineer A BER 93-3 Incumbent Design Engineer
    Engineer A owed faithful agent duties to the franchiser client during the multi-year design engagement.
  • Engineer B BER 93-3 Replacement Design Engineer
    Engineer B owed faithful agent duties to the franchiser who retained him, including honoring confidentiality instructions regarding the engagement.
  • Engineer A Present Case Incumbent Engineer
    Engineer A must act as a faithful agent to the public agency client in the context of the ongoing procurement relationship.
  • Engineer B Present Case Public Procurement Competitor
    Engineer B's use of FOIA to obtain a competitor's submission raises questions about whether his conduct is consistent with faithful agency toward the public agency client.
Event (3)
  • State Provides FOIA Documents
    The release of confidential proposal documents by the state undermines the faithful agent relationship engineers expect when submitting proprietary information to a client.
  • Competitive Information Asymmetry Created
    The resulting information asymmetry harms the client-engineer trust relationship by allowing one competitor to benefit from another's confidential submission.
  • Engineer A's Qualifications Exposed to Competitor
    Exposing Engineer A's proprietary qualifications to a competitor breaches the duty of faithful agency owed to the engineer by the client entity managing the selection process.
Resource (4)
  • NSPE Code of Ethics
    The faithful agent and trustee duty is a core provision of the NSPE Code referenced as the primary normative authority in this case.
  • BER Case No. 93-3
    This precedent directly establishes the engineer's duty of loyalty as faithful agent and trustee, which is the substance of provision II.4.
  • Agent-Trustee Loyal Dealing Doctrine
    This doctrine is applied to define the scope of the loyalty obligation that II.4 imposes on engineers acting as faithful agents or trustees.
  • Competitor Conduct in Procurement Standard - FOIA Use Context
    Engineer B's FOIA use is evaluated against the faithful agent duty to determine whether it breaches loyalty obligations under II.4.
Capability (4)
  • Engineer B BER 93-3 Faithful Agent Client Benefit Primacy Capability Instance
    This capability directly addresses Engineer B's duty as faithful agent and trustee to prioritize client benefit over personal interests.
  • NSPE BER Board BER 93-3 to Present Case Faithful Agent Principle Cross-Context Application
    The Board applied the faithful agent principle from BER 93-3 to the present case, directly linking this provision across contexts.
  • Engineer B Present Case Public Procurement Integrity Public Interest Articulation Capability Instance
    Acting as a faithful agent to the public client requires understanding and upholding public procurement integrity.
  • State Agency Public Procurement Authority Procurement Integrity
    The state agency's duty to maintain procurement integrity reflects the faithful agent obligation owed to the public interest.
II.5. Engineers shall avoid deceptive acts.
How this applies in the case (showing 3 of 56)
Obligation
Engineer B FOIA Pre-Submission Timing Violation Obligation
Submitting a FOIA request before Engineer B's own submission to gain competitor intelligence constitutes a deceptive act prohibited by II.5.
Action
Engineer B Files FOIA Request
This provision applies because using a FOIA request to gain competitive advantage over another firm's qualifications could constitute a deceptive act.
State
Engineer B FOIA-Based Acquisition of Competitor Qualifications
Using a public records request to gain advance knowledge of a competitor's qualifications before submitting one's own could constitute a deceptive act in the procurement process.
Obligation (8)
  • Engineer B FOIA Pre-Submission Timing Violation Obligation
    Submitting a FOIA request before Engineer B's own submission to gain competitor intelligence constitutes a deceptive act prohibited by II.5.
  • Engineer B FOIA Content Non-Exploitation Obligation
    Using competitor qualifications obtained through FOIA to gain an unfair advantage constitutes a deceptive act under II.5.
  • Engineer B Good Intent Non-Justification Procurement Obligation
    II.5. prohibits deceptive acts regardless of intent, directly supporting the obligation that good intent does not justify improper conduct.
  • Engineer B Honorable Procurement Conduct Obligation
    II.5. requires avoidance of deceptive acts, which is central to the obligation to conduct oneself honorably beyond mere legal compliance.
  • Engineer B Present Case FOIA Pre-Submission Competitor Intelligence Abstention
    Obtaining competitor intelligence before submitting one's own qualifications is a deceptive act directly prohibited by II.5.
  • Engineer B Present Case Public Procurement FOIA Timing Appearance of Impropriety Avoidance
    II.5. requires avoiding deceptive acts, which includes structuring FOIA requests so their timing does not create an appearance of impropriety.
  • Engineer B Present Case Competitor Qualifications Content Non-Exploitation
    Exploiting a competitor's qualifications content obtained through FOIA to gain unfair advantage constitutes a deceptive act under II.5.
  • Engineer B Present Case Public Procurement Misrepresentation Check Transparency Recognition
    II.5. supports the obligation to recognize that procurement transparency serves as a check against misrepresentation and deceptive conduct.
Action (3)
  • Engineer B Files FOIA Request
    This provision applies because using a FOIA request to gain competitive advantage over another firm's qualifications could constitute a deceptive act.
  • BER Case 93-3: Engineer B Reviews Design Information
    This provision applies because reviewing confidential design information obtained through a FOIA request without disclosure could constitute a deceptive act.
  • BER Case 93-3: Engineer B Discloses Relationship to Engineer A
    This provision directly governs Engineer B's obligation to disclose their relationship to Engineer A to avoid deceptive conduct.
State (4)
  • Engineer B FOIA-Based Acquisition of Competitor Qualifications
    Using a public records request to gain advance knowledge of a competitor's qualifications before submitting one's own could constitute a deceptive act in the procurement process.
  • Engineer B Asymmetric Competitive Advantage Post-FOIA
    Exploiting an informational advantage derived from reviewing a competitor's submission without disclosure is directly relevant to the prohibition on deceptive acts.
  • BER 93-3 Franchiser-Engineer B Covert Transition Engagement
    Engineer B's covert engagement under instruction not to disclose the relationship to Engineer A raises direct concerns about deceptive conduct prohibited by II.5.
  • Confidential Information in Public Procurement Submission Risk
    The risk that firms include proprietary information in public submissions that competitors can exploit through FOIA relates to the potential for deceptive competitive practices under II.5.
Constraint (12)
  • Engineer B Public Procurement Misrepresentation Check Transparency Recognition BER 10-8
    The prohibition on deceptive acts directly relates to Engineer B's constraint to recognize that misrepresentation in the open public procurement process is prohibited.
  • Engineer B FOIA Pre-Submission Timing Constraint Instance
    Submitting a FOIA request before one's own submission to gain a competitive advantage constitutes a deceptive act that this provision prohibits.
  • Engineer B FOIA-Acquired Competitor Intelligence Ethical Use Constraint Instance
    This provision prohibits using FOIA-obtained competitor information to tailor or misrepresent one's own submission, directly creating this constraint.
  • Engineer B Competitive Procurement Honorable Conduct Constraint Instance
    The prohibition on deceptive acts underpins the requirement that Engineer B conduct all competitive activities honorably and without improper use of competitor intelligence.
  • Engineer B Appearance of Impropriety Avoidance in Public Procurement Constraint Instance
    The prohibition on deceptive acts extends to avoiding even the appearance of impropriety, directly creating this constraint on Engineer B's conduct.
  • Engineer B Competitive Procurement Fairness Constraint Instance
    Avoiding deceptive acts requires Engineer B to preserve equal competitive opportunity, directly linking this provision to the fairness constraint.
  • Engineer B Improper Competitive Method Prohibition Constraint Instance
    This provision directly prohibits the improper and questionable method of submitting a pre-submission FOIA request to gain unfair competitive advantage.
  • Engineer B Free and Open Competition Regulatory Deference BER 10-8
    The prohibition on deceptive acts aligns with acting within the legal framework governing free and open competition, as deception undermines that framework.
  • Engineer B FOIA Pre-Submission Timing Appearance of Impropriety BER 10-8
    This provision directly creates the constraint that Engineer B must not engage in the deceptive-appearing act of submitting a FOIA request before his own qualifications are submitted.
  • Engineer B FOIA-Acquired Competitor Intelligence Ethical Use BER 10-8
    The prohibition on deceptive acts constrains Engineer B to use FOIA-obtained information only for legitimate purposes and not to misrepresent his own qualifications.
  • Engineer B Present Case Procurement Honorable Conduct Constraint Instance
    This provision directly requires honorable and non-deceptive conduct throughout the public procurement process, creating this constraint on Engineer B.
  • Engineer B Present Case Appearance of Impropriety Avoidance Public Procurement
    The prohibition on deceptive acts extends to avoiding the appearance of impropriety, directly linking this provision to Engineer B's constraint in the present procurement case.
Principle (8)
  • FOIA Procurement Timing Integrity Invoked By Engineer B
    Submitting a FOIA request to obtain a competitor's qualifications before submitting one's own raises concerns about deceptive or unfair conduct in the procurement process.
  • Fairness in Professional Competition Implicated By Engineer B FOIA Conduct
    Creating information asymmetry through strategic FOIA timing potentially constitutes a deceptive act that undermines fair competition.
  • FOIA Procurement Timing Integrity Obligation Invoked for Engineer B Present Case
    The Board's concern about the timing of Engineer B's FOIA request directly implicates the obligation to avoid deceptive acts in professional competition.
  • FOIA-Based Competitor Intelligence Ethical Use Constraint Invoked in Public Procurement Review
    The constraint on using lawfully obtained competitor intelligence is grounded in the duty to avoid deceptive acts even when the underlying action is legal.
  • Good Intent Does Not Cure Procedural Impropriety Invoked Against Engineer B
    II.5 supports the finding that Engineer B's conduct may constitute a deceptive act regardless of the benign motivation behind the FOIA request.
  • Procurement Integrity in Public Engineering Implicated By State Agency Disclosure
    The deceptive acts provision is implicated when procurement integrity is compromised, even if the disclosure mechanism itself is legally permitted.
  • Public Procurement Confidentiality Self-Protection Obligation Invoked By Engineer A
    The risk of deceptive use of disclosed information supports the caution that engineers should protect confidential information in public submissions.
  • Public Procurement Confidentiality Self-Protection Obligation Invoked as Caution to Engineers
    The Board's caution against including proprietary information in public submissions relates to preventing its deceptive use by competitors under II.5.
Role (3)
  • Engineer B FOIA-Requesting Competing Engineer
    Engineer B's use of a FOIA request prior to the interview process to obtain a competitor's qualifications raises concerns about whether this constitutes a deceptive act in the procurement process.
  • Engineer B BER 93-3 Replacement Design Engineer
    Engineer B's concealment of his engagement from Engineer A while reviewing Engineer A's pending design concepts raises concerns about deceptive conduct.
  • Engineer B Present Case Public Procurement Competitor
    The timing and strategic use of the FOIA request by Engineer B to gain competitive advantage may constitute a deceptive act in the public procurement process.
Event (3)
  • Competitive Information Asymmetry Created
    Using confidential competitor information obtained through FOIA to gain an unfair advantage constitutes a deceptive act in the competitive selection process.
  • Interview Process Ongoing During Disclosure
    Participating in an ongoing interview process while possessing improperly obtained competitor information creates a deceptive competitive situation.
  • BER 93-3 Precedent Established
    The precedent addresses whether exploiting FOIA-obtained competitor information during selection constitutes a deceptive act under the code.
Resource (5)
  • State FOIA Statute
    Engineer B's use of the FOIA statute to access competitor qualifications is examined to determine whether it constitutes a deceptive act under II.5.
  • Competitor Conduct in Procurement Standard - FOIA Use Context
    This standard directly governs whether Engineer B's FOIA-based intelligence gathering constitutes a deceptive act prohibited by II.5.
  • Engineer Solicitation and Competition Ethics Standard - Competitive Advantage Limits
    This standard evaluates whether FOIA-based information gathering crosses into deceptive competitive conduct prohibited by II.5.
  • Public Procurement Fairness Standard - RFQ Informational Equity
    The asymmetric access to competitor information obtained via FOIA is assessed against the prohibition on deceptive acts in II.5.
  • Public Procurement Regulatory Framework (Free and Open Competition)
    The free and open competition framework is referenced to assess whether Engineer B's conduct undermines fair procurement in a manner constituting deception under II.5.
Capability (10)
  • Engineer B Improper Competitive Advantage Recognition
    Using a FOIA request to gain advance access to competitor qualifications constitutes a deceptive act by creating an unfair competitive advantage.
  • Engineer B FOIA Timing Ethics Compliance
    Submitting a FOIA request before one's own submission to gain strategic insight is a deceptive act that this capability requires recognizing and avoiding.
  • Engineer B Good Intent Non-Justification Recognition
    This capability requires recognizing that good intent does not justify conduct that is inherently deceptive in competitive procurement.
  • Engineer B BER 93-3 Good Intent Non-Justification Recognition Capability Instance
    Recognizing that benevolent motivation does not excuse deceptive conduct directly ties to the prohibition on deceptive acts.
  • Engineer B Present Case FOIA Timing Appearance of Impropriety Avoidance Capability Instance
    Avoiding the appearance of impropriety through FOIA timing directly relates to the duty to avoid deceptive acts.
  • Engineer B Present Case Public Procurement Open Process Misrepresentation Protection Recognition
    Protecting the open procurement process from misuse of FOIA disclosures directly relates to avoiding deceptive acts.
  • Engineer B Competitor Qualifications Content Non-Exploitation
    Exploiting competitor qualifications content obtained through a pre-submission FOIA request constitutes a deceptive competitive act.
  • Engineer B Present Case Competitor Qualifications Content Non-Exploitation Capability Instance
    This capability instance directly requires recognizing ethical boundaries that prevent deceptive use of lawfully obtained competitor information.
  • Engineer B Honorable Procurement Self-Regulation
    Self-regulating to ensure honorable procurement conduct is directly tied to the obligation to avoid deceptive acts in competition.
  • Engineer B Public Procurement Integrity Articulation
    Understanding the public interest rationale for procurement rules supports recognizing why deceptive competitive acts undermine those rules.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

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

Principle Established:

An engineer acting as a 'faithful agent and trustee' has a duty of loyalty to the client, and disclosing confidential client relationships or information in a manner that neglects the client's interests is not consistent with the NSPE Code of Ethics.

Citation Context:

The Board cited this case to illustrate the engineer's role as a 'faithful agent and trustee' to the client and the duty of loyalty and fair dealing in competitive situations between engineering firms. It is also distinguished from the present case due to differing facts.

Relevant Excerpts
discussion: "One example is BER Case No. 93-3 . In that case, Engineer A was retained by a major franchiser to provide engineering design services for a chain of stores throughout the United States."
discussion: "While the facts in BER Case No. 93-3 are somewhat different than the facts in the present case, Case No. 93-3 makes an important point which is relevant to the case at hand, the role of the engineer in serving the legitimate needs of the client and the role of the engineer as the employer or client's 'faithful agent and trustee.'"
Implicit Similar Cases 10 Similarity Network

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

Component Similarity 52% Facts Similarity 39% Discussion Similarity 67% Provision Overlap 71% Outcome Alignment 50% Tag Overlap 50%
Shared provisions: II.4, II.4.a, III.1, III.5, III.5.b View Synthesis
Component Similarity 53% Facts Similarity 36% Discussion Similarity 65% Provision Overlap 71% Outcome Alignment 50% Tag Overlap 29%
Shared provisions: II.4, II.4.a, III.1, III.5, III.5.b View Synthesis
Component Similarity 56% Facts Similarity 42% Discussion Similarity 56% Provision Overlap 30% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: II.4.a, III.1, III.5 Same outcome True View Synthesis
Component Similarity 54% Facts Similarity 34% Discussion Similarity 71% Provision Overlap 22% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: II.4.a, III.5 Same outcome True View Synthesis
Component Similarity 57% Facts Similarity 49% Discussion Similarity 56% Provision Overlap 50% Outcome Alignment 50% Tag Overlap 29%
Shared provisions: II.4, II.4.a, III.1, III.5 View Synthesis
Component Similarity 59% Facts Similarity 34% Discussion Similarity 59% Provision Overlap 7% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: III.5 Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 33% Discussion Similarity 68% Provision Overlap 29% Outcome Alignment 50% Tag Overlap 60%
Shared provisions: II.4, II.4.a View Synthesis
Component Similarity 54% Facts Similarity 40% Discussion Similarity 69% Provision Overlap 33% Outcome Alignment 50% Tag Overlap 60%
Shared provisions: II.4, II.4.a, III.5 View Synthesis
Component Similarity 50% Facts Similarity 40% Discussion Similarity 59% Provision Overlap 43% Outcome Alignment 50% Tag Overlap 50%
Shared provisions: II.4.a, III.5, III.5.b View Synthesis
Component Similarity 59% Facts Similarity 38% Discussion Similarity 81% Provision Overlap 27% Outcome Alignment 50% Tag Overlap 50%
Shared provisions: II.4.a, III.1, III.5 View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

Was it ethical for Engineer B to make the FOIA request in connection with the state’s procurement of engineering services?

Board conclusion It was ethical for Engineer B to make the FOIA request in connection with the state’s procurement of engineering services, pursuant to the State’s RFQ procedures.
Implicit (4)

Even if Engineer B's FOIA request was legally permissible, does the act of reviewing and incorporating insights from a competitor's qualifications submission before submitting his own constitute use of an improper competitive advantage that violates the spirit of fair procurement, regardless of the legality of the acquisition?

AnalyticalEven if Engineer B's FOIA request was legally permissible, reviewing and incorporating insights from a competitor's qualifications submission before submitting his own raises serious concerns about improper competitive advantage that violate the spirit of fair procurement. The legality of the acquisition does not sanitize the competitive distortion it creates. Engineer A submitted qualifications in good faith within a procurement framework that implicitly assumes informational parity among competing firms at the time of submission. Engineer B's pre-submission FOIA request shattered that parity by allowing him to calibrate his own submission against a competitor's already-disclosed strategy. The NSPE Code's prohibition on improper competitive methods is not limited to illegal acts; it encompasses conduct that, while technically lawful, undermines the integrity of the competitive process. The Board's own recommendation that Engineer B should have submitted his qualifications before filing the FOIA request implicitly acknowledges that the sequence of actions matters ethically, not merely the legal permissibility of the individual act. Accordingly, the informational advantage gained through pre-submission FOIA review constitutes a form of competitive impropriety even if no explicit rule was violated.
AnalyticalWhile the Board concluded that Engineer B's FOIA request was ethically permissible, the Board's reasoning implicitly distinguishes between the legality of obtaining competitor qualifications and the ethics of using them. The FOIA request itself may be defensible as an exercise of a public right, but the Board's caution that Engineer B should have submitted his own qualifications first signals that the ethical weight of the conduct shifts materially once the information is actually received and potentially incorporated. If Engineer B reviewed Engineer A's submission and tailored his own qualifications in response-even without copying protected expression-this would constitute use of an improper competitive advantage that undermines the fairness principles embedded in qualification-based selection procurement law. The Board's conclusion of compliance therefore applies narrowly to the act of filing the FOIA request, not to any downstream exploitation of the information obtained.

Does the state agency bear any ethical or procedural responsibility for disclosing a competitor's qualifications submission during an active procurement process, and should procurement regulations be revised to protect submitted qualifications from FOIA disclosure until after the selection process is complete?

AnalyticalThe Board's conclusion that Engineer B's FOIA request was ethical rests in part on the existence of a legally open competitive framework, but this reasoning exposes an unaddressed systemic vulnerability: the state agency's disclosure of Engineer A's qualifications during an active procurement process itself implicates procurement integrity. The state agency, as the public procurement authority, bears a co-responsibility for the informational equity of the selection process. By releasing a competitor's qualifications before the submission deadline had closed for all parties, the agency created a structural asymmetry that no individual engineer's ethical conduct alone could have prevented or remedied. This suggests that the Board's ethical analysis, while correctly focused on Engineer B's conduct, is incomplete without acknowledging that procurement regulations should be revised to exempt submitted qualifications from FOIA disclosure until after the selection process concludes, in order to protect the public interest in fair and competitive procurement outcomes.
AnalyticalThe state agency bears a meaningful ethical and procedural responsibility for disclosing a competitor's qualifications submission during an active procurement process. While the state may have been legally obligated to comply with the FOIA request under existing statute, the disclosure created a structural inequity in the procurement that undermines the public interest the procurement system is designed to serve. Procurement regulations should be revised to include a procurement-integrity exception to FOIA disclosure, shielding submitted qualifications from release until after the selection process is complete. Such an exception would align FOIA law with the fairness norms embedded in qualification-based selection frameworks, which presuppose that competing firms are evaluated on equal informational footing. The absence of such a protection is a regulatory gap, not an ethical endorsement of mid-process disclosure. The state agency's compliance with the FOIA request, while legally defensible, contributed to the competitive information asymmetry that the Board itself found troubling, and this implicates the agency's own procurement integrity obligations.

What affirmative steps, if any, is Engineer A obligated to take to protect the confidentiality of qualifications submitted to public procurement processes, and does failure to take such steps diminish Engineer A's standing to object to Engineer B's FOIA request?

AnalyticalEngineer A bears some affirmative responsibility to protect the confidentiality of qualifications submitted to public procurement processes, but the scope of that obligation is limited by the practical realities of public records law. Engineer A could have proactively requested that the state agency treat certain portions of the submission as proprietary or confidential, particularly trade-sensitive methodologies, staffing structures, or pricing frameworks, to the extent permitted by the applicable FOIA statute. Failure to take such steps does not eliminate Engineer A's standing to object to Engineer B's conduct, because the ethical wrong lies in Engineer B's exploitation of the timing asymmetry, not solely in Engineer A's failure to anticipate it. However, Engineer A's inaction does diminish the force of any claim that the procurement system failed him, since the self-protection obligation is a recognized caution in the NSPE framework. The ethical burden is shared: Engineer A should have been more proactive, but Engineer B should not have exploited the window of vulnerability that Engineer A's inaction created.

If Engineer B did in fact use the content of Engineer A's qualifications to tailor or strengthen his own submission, does that use constitute a deceptive act under the NSPE Code, even if the information was lawfully obtained through FOIA?

AnalyticalIf Engineer B did in fact use the content of Engineer A's qualifications to tailor or strengthen his own submission, that use would constitute a deceptive act under the NSPE Code even if the information was lawfully obtained through FOIA. The Code's prohibition on deceptive acts is not limited to misrepresentations of fact; it encompasses conduct that creates a false impression about the independent merit of one's own professional work product. A qualifications submission that has been calibrated against a competitor's submission without disclosure presents the submitting engineer's work as independently conceived when it is in part derivative of a competitor's strategy. This is a form of professional misrepresentation that violates the spirit of II.5. Furthermore, the lawfulness of the acquisition channel does not transform the downstream use into an ethical act. The analogy to BER 93-3 is instructive: just as good intent did not excuse Engineer B in that case from the consequences of a procedurally improper act, the legal availability of FOIA does not excuse Engineer B in the present case from the ethical consequences of exploiting a competitor's submission to gain an undisclosed advantage.
Cross-cutting analytical questions (12)

These questions consider the case as a whole rather than a specific board question above.

Principle tension (4)

Does the principle of Public Procurement Transparency as a Public Interest Protection Mechanism - which justifies FOIA access to government records - conflict with the principle of Fairness in Professional Competition, which demands that competitors not gain informational advantages unavailable to all parties during an active procurement?

AnalyticalThe principle of Public Procurement Transparency as a Public Interest Protection Mechanism and the principle of Fairness in Professional Competition are in genuine tension in this case, and the Board's resolution of that tension in favor of transparency is defensible but not without cost. FOIA exists to ensure government accountability and public access to government records, values that serve the public interest broadly. However, when FOIA is used not to scrutinize government conduct but to gain a competitive edge over a private party in an ongoing procurement, the transparency rationale is instrumentalized in a way that undermines the fairness norm it is supposed to coexist with. The two principles can be reconciled only if FOIA access is temporally constrained in procurement contexts, releasing competitor submissions only after the selection process concludes. Until such a reconciliation is achieved through regulatory reform, the Board's conclusion that Engineer B's FOIA request was ethical must be understood as a narrow legal compliance finding rather than a broad endorsement of the practice as consistent with professional fairness norms.
AnalyticalThe tension between Public Procurement Transparency as a Public Interest Protection Mechanism and Fairness in Professional Competition was resolved in this case by treating legal access as a necessary but insufficient condition for ethical conduct. The Board did not declare Engineer B's FOIA request unethical, but it declined to endorse the timing and sequence of his actions as fully honorable. This resolution reveals a layered principle hierarchy: transparency rights operate as a floor, not a ceiling, for ethical behavior. An engineer may lawfully invoke FOIA without that invocation automatically satisfying the higher standard of fair dealing expected in professional competition. The case teaches that when two legitimate principles collide - open records access and competitive equity - the ethical resolution does not simply defer to legality, but asks whether the actor's conduct would withstand scrutiny from the standpoint of a reasonable, honorable professional. The Board's implicit answer is that Engineer B's pre-submission timing failed that scrutiny even while his legal right to file the request was affirmed.

Does the principle that Good Intent Does Not Cure Procedural Impropriety - applied analogically from BER 93-3 - conflict with the principle of Free and Open Competition as a Boundary Condition in engineering practice, given that the Board ultimately found Engineer B's FOIA request ethical precisely because it occurred within a legally open competitive framework?

AnalyticalThe analogical transfer of the Faithful Agent Obligation from BER Case 93-3 to the present case reveals a significant principle extension: the duty to subordinate personal advantage to the integrity of a process is not confined to client relationships but extends, by analogy, to the integrity of public procurement systems in which engineers participate as competitors. In BER 93-3, the faithful agent principle constrained Engineer B from disclosing a new client relationship even with benevolent intent, because good intent does not cure procedural impropriety. Applied here, the same logic constrains Engineer B from exploiting a legal information-gathering mechanism to gain asymmetric competitive advantage, even if his intent was merely to be better informed. The principle synthesis that emerges is that the Benevolent Motive Non-Excuse principle and the Good Intent Does Not Cure Procedural Impropriety principle together form a meta-principle: the ethical evaluation of competitive conduct in engineering procurement is objective, not subjective. The actor's intent is irrelevant to whether the conduct created an unfair structural advantage. This case thus teaches that the faithful agent duty, while textually directed at client relationships under Code Section II.4, carries an analogical shadow obligation toward the fairness architecture of public procurement itself.

Does the FOIA Procurement Timing Integrity principle - which holds that Engineer B should have submitted his own qualifications before making the FOIA request - conflict with the principle of Public Procurement Confidentiality Self-Protection Obligation, which places the burden on Engineer A to safeguard sensitive submission content, thereby implying that the timing of Engineer B's request is Engineer A's risk to manage rather than Engineer B's obligation to defer?

AnalyticalThe tension between the FOIA Procurement Timing Integrity principle and the Public Procurement Confidentiality Self-Protection Obligation does not resolve cleanly in favor of either party. The Board's recommendation that Engineer B should have submitted his own qualifications before filing the FOIA request implies that the timing of the request is Engineer B's ethical responsibility to manage. However, the self-protection obligation imposed on Engineer A suggests that the risk of FOIA exposure is partly Engineer A's to bear. These two positions are not mutually exclusive: Engineer B had an obligation to sequence his actions to avoid creating an informational asymmetry, and Engineer A had an obligation to take reasonable steps to protect sensitive submission content. The ethical failure in this case is distributed, not singular. The Board's framing, which focuses primarily on Engineer B's timing, understates Engineer A's share of the responsibility while also understating the structural inadequacy of a procurement system that permits mid-process FOIA disclosure without any protective mechanism.
AnalyticalThe principle of Public Procurement Confidentiality Self-Protection Obligation - which places a burden on Engineer A to safeguard sensitive submission content - interacts with the FOIA Procurement Timing Integrity principle in a way that distributes ethical responsibility across multiple actors rather than concentrating it solely on Engineer B. The Board's implicit recognition that Engineer A bears some responsibility for protecting his own submission acknowledges that public procurement is a shared ethical ecosystem: the state agency, the submitting engineer, and the requesting competitor each carry distinct obligations. However, this distribution of responsibility does not dissolve Engineer B's independent obligation to conduct himself honorably. The principle synthesis here is one of concurrent rather than exclusive duty: Engineer A's failure to seek confidentiality protections does not license Engineer B to exploit the resulting vulnerability. Instead, both obligations coexist, and Engineer B's ethical standing is evaluated independently of whether Engineer A took adequate self-protective measures. This teaches that in engineering ethics, the availability of an opportunity to act improperly does not become an ethical permission simply because another party failed to foreclose that opportunity.

Does the principle of Faithful Agent Obligation - invoked as an analogical bridge from BER 93-3 to constrain engineers from exploiting informational advantages against client or competitor interests - conflict with the principle of FOIA-Based Competitor Intelligence Ethical Use, which the Board implicitly endorses as permissible within public procurement, raising the question of whether the faithful agent duty extends to competitive relationships or only to client relationships?

AnalyticalThe Board's analogical invocation of the faithful agent principle from BER Case 93-3 raises the question of whether that duty transfers to competitive relationships in public procurement. In BER 93-3, the faithful agent obligation ran from Engineer B to a private client, constraining Engineer B from acting in ways that prioritized personal interest over client welfare. In the present case, there is no private client relationship between Engineer B and Engineer A. However, the faithful agent principle can be extended analogically to the public procurement system itself: Engineer B, as a participant in a public procurement process, owes a duty of faithful dealing to the integrity of that process, which serves the public interest. This duty constrains Engineer B from exploiting procedural mechanisms in ways that undermine the fairness of the process, even in the absence of a direct client relationship with Engineer A. The Board's analogical transfer of the faithful agent principle is therefore defensible, but it should be understood as grounding a duty to the public procurement system rather than a duty to Engineer A as a competitor.
AnalyticalThe Board's analogical invocation of the faithful agent principle from BER Case 93-3 introduces a tension that the Board does not fully resolve. In BER 93-3, the faithful agent duty ran from an engineer to a private client, constraining the engineer from acting in ways that prioritized personal or altruistic motives over the client's interests. In the present case, the Board applies this principle analogically to suggest that Engineer B owed a duty of honorable conduct to the integrity of the public procurement process itself-a duty that is not grounded in a bilateral client relationship but in a broader professional obligation to the public. This extension is conceptually significant: it implies that the faithful agent principle under NSPE Code Section II.4 is not limited to private client relationships but also constrains engineers from exploiting informational advantages within public procurement systems, even when those advantages are legally obtained. However, the Board stops short of declaring this duty violated, leaving open whether the timing of Engineer B's FOIA request-after Engineer A submitted but before Engineer B submitted-constitutes a breach of this extended faithful agent obligation or merely an appearance of impropriety that falls short of an ethical violation. A more complete analysis would require the Board to specify whether the appearance of impropriety standard, standing alone, is sufficient to constitute an ethical violation under the NSPE Code, or whether actual exploitation of the competitor's information is required.
Theoretical (4)

From a deontological perspective, did Engineer B violate a categorical duty of fair dealing toward Engineer A by using a legal mechanism-the FOIA request-to obtain a competitive advantage that Engineer A had no opportunity to anticipate or consent to, regardless of whether the act was technically lawful?

AnalyticalFrom a deontological perspective, Engineer B's use of the FOIA mechanism to obtain a competitive advantage over Engineer A before submitting his own qualifications raises a serious question about categorical duty. The Kantian test asks whether the maxim underlying Engineer B's action could be universalized without contradiction. If every competing engineer routinely filed FOIA requests to obtain competitors' qualifications before submitting their own, the procurement system would collapse into a race to submit last, with each firm waiting to calibrate its submission against all others. This self-defeating universalization reveals that Engineer B's action, while individually rational, is categorically impermissible as a general rule of professional conduct. Engineer B's act treated Engineer A not as an equal participant in a fair process but as an unwitting source of competitive intelligence, instrumentalizing Engineer A's good-faith submission in a way that violates the duty of fair dealing that professional competition requires. The legal availability of FOIA does not discharge this categorical duty.

From a consequentialist perspective, does the long-term harm to public trust in engineering procurement processes-caused by normalizing pre-submission FOIA intelligence gathering-outweigh the short-term benefit of transparency and open records access that Engineer B's FOIA request ostensibly served?

AnalyticalFrom a consequentialist perspective, normalizing pre-submission FOIA intelligence gathering in engineering procurement would produce long-term systemic harms that outweigh the short-term transparency benefits of any individual FOIA request. If the practice becomes routine, firms will respond by submitting qualifications that are strategically vague to minimize the intelligence value of early disclosure, degrading the quality of information available to public agencies for selection decisions. Alternatively, firms may delay submission to preserve informational advantage, distorting procurement timelines. Public trust in the fairness of qualification-based selection processes would erode, as engineers and firms perceive the system as rewarding strategic information exploitation rather than genuine professional merit. The consequentialist calculus therefore supports the Board's implicit discomfort with Engineer B's timing even while the Board found the act technically ethical, and it supports regulatory reform to close the FOIA disclosure window during active procurement periods.

From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and honorable character expected of a licensed engineer by strategically timing a FOIA request to gain informational advantage over a competitor before submitting their own qualifications, even if no explicit rule prohibited this sequence?

AnalyticalFrom a virtue ethics perspective, Engineer B's strategic timing of the FOIA request to gain informational advantage over a competitor before submitting his own qualifications falls short of the professional integrity and honorable character expected of a licensed engineer. Virtue ethics asks not merely whether an act is permitted but whether it reflects the character of a person of good professional standing. An engineer of genuine integrity, confronted with the opportunity to review a competitor's qualifications before submitting his own, would recognize that the advantage gained is not earned through superior professional merit but through procedural exploitation. The virtuous engineer would either submit his own qualifications first or decline to use the competitor's submission as a calibration tool. The fact that no explicit rule prohibited Engineer B's sequence of actions does not resolve the virtue ethics question, because virtue ethics is precisely concerned with conduct in the spaces where rules are silent. Engineer B's conduct in this case reflects a disposition toward competitive advantage-seeking that is inconsistent with the honorable character the NSPE Code expects of its members.

From a deontological perspective, does the Board's analogical invocation of the faithful agent principle from BER Case 93-3 impose a transferable duty on Engineer B in the present case-specifically, a duty to subordinate personal competitive advantage to the integrity of the procurement process-even though Engineer B's relationship is to the public procurement system rather than to a private client?

Counterfactual (4)

If Engineer B had submitted his firm's own qualifications to the state agency before filing the FOIA request-as the Board recommends-would the competitive information asymmetry have been eliminated, or would Engineer B still have gained an unfair advantage by using Engineer A's disclosed qualifications to refine or supplement his submission during the interview process?

AnalyticalEven if Engineer B had submitted his own qualifications before filing the FOIA request, as the Board recommends, the competitive information asymmetry would not have been fully eliminated. Engineer B would still have had access to Engineer A's qualifications before the interview process concluded, and could have used that information to refine oral presentations, anticipate the agency's comparative questions, or identify weaknesses in Engineer A's submission to exploit during interviews. The Board's timing recommendation addresses the most visible form of the asymmetry, the pre-submission calibration problem, but does not address the downstream exploitation risk that persists throughout the selection process. A more complete ethical resolution would require Engineer B to refrain from using Engineer A's qualifications for any competitive purpose during the entire procurement process, not merely to submit his own qualifications first. This suggests that the Board's conclusion, while finding the FOIA request ethical, implicitly leaves open a residual ethical obligation of non-exploitation that extends beyond the timing question.

What if Engineer A had proactively requested that the state agency treat his submitted qualifications as confidential or proprietary prior to Engineer B's FOIA request-would the state have been obligated to withhold the documents, and would this have changed the ethical calculus for both Engineer B and the state agency?

AnalyticalIf Engineer A had proactively requested that the state agency treat his submitted qualifications as confidential or proprietary prior to Engineer B's FOIA request, the ethical calculus for both parties would have shifted significantly. Many FOIA statutes include exemptions for trade secrets or proprietary business information, and a timely confidentiality designation by Engineer A might have obligated the state to withhold the documents or at least to notify Engineer A before disclosure, allowing him to seek legal protection. Had the state withheld the documents on this basis, Engineer B's act of filing the FOIA request would not itself constitute an ethical violation, because the request would have been denied and no competitive harm would have resulted. The ethical weight of Engineer B's conduct depends in part on the actual acquisition and potential use of the information, not merely on the filing of the request. However, the act of filing a pre-submission FOIA request targeting a competitor's qualifications would still reflect a disposition toward competitive advantage-seeking that raises professional character concerns independent of whether the information was actually obtained.

If the state agency had declined to release Engineer A's qualifications under a procurement-integrity exception to the FOIA statute, would Engineer B's act of filing the request itself still constitute an ethical violation, or does the ethical weight of the conduct depend entirely on whether the information was actually obtained and used?

AnalyticalIf the state agency had declined to release Engineer A's qualifications under a procurement-integrity exception to the FOIA statute, Engineer B's act of filing the request would not constitute a clear ethical violation in isolation, but it would still warrant scrutiny. The ethical analysis of Engineer B's conduct cannot be reduced entirely to whether the information was actually obtained, because the intent behind the request, to gain competitive intelligence from a competitor's submission before submitting his own, reflects a disposition that is ethically problematic regardless of outcome. An engineer who attempts to exploit a procedural mechanism for competitive advantage but is thwarted by the system has not thereby demonstrated ethical compliance; he has merely been prevented from completing an ethically questionable act. The ethical weight of the conduct is diminished when no information is obtained, because no actual harm to the competitive process results, but the underlying intent and the appearance of impropriety it creates remain relevant to a full professional character assessment.

Had the BER Case 93-3 precedent not existed, would the Board have reached the same conclusion that Engineer B's pre-submission FOIA timing created an appearance of impropriety, or does the ethical reasoning in this case depend critically on the analogical transfer of the faithful agent principle from that prior case?

AnalyticalThe Board's reasoning in the present case does not depend critically on the analogical transfer from BER Case 93-3, but the absence of that precedent would likely have produced a less nuanced conclusion. Without BER 93-3, the Board would have lacked a ready framework for articulating why good intent, or the legal availability of FOIA, does not automatically render Engineer B's conduct ethical. The faithful agent principle from BER 93-3 provided the Board with a conceptual bridge to the idea that procedural propriety matters independently of outcome or intent. Without that bridge, the Board might have resolved the case more simply on the basis of legal permissibility, concluding that because FOIA access is lawful, the request was ethical, without the important qualification about timing and appearance of impropriety. The BER 93-3 precedent therefore enriched the Board's analysis by introducing a principle that constrains conduct even within legally permissible boundaries, and its absence would have left the ethical reasoning thinner and potentially more permissive than the facts warrant.
Decisions & Arguments (7)
View Extraction

Should Engineer B file the FOIA request to obtain Engineer A's qualifications before submitting his own firm's qualifications to the state agency, or should he submit his own qualifications first and only then file the FOIA request?

Options considered:
O1 Engineer B submits his firm's qualifications to the state agency before filing any FOIA request for Engineer A's submission, ensuring that the competitor intelligence obtained cannot have influenced the content of his own qualifications and thereby avoiding any appearance of impropriety in the procurement process. Board's choice
O2 Engineer B files the FOIA request before submitting his own qualifications, treating the legal availability of FOIA access as sufficient ethical authorization for the request regardless of timing, on the grounds that public procurement submissions are public records and no regulation prohibits this sequence.
O3 Engineer B refrains from filing any FOIA request for a competitor's qualifications during the active procurement window, before the selection process concludes, recognizing that any pre-selection access to a competitor's submission creates an informational asymmetry incompatible with fair competition, regardless of whether the request is filed before or after his own submission.
Argument structure:
Warrants

The FOIA Procurement Timing Integrity Obligation holds that Engineer B should submit his own qualifications before filing the FOIA request, so that the request cannot influence the content of his submission. The Public Procurement Transparency principle holds that FOIA access to government records is a legally recognized public right and that Engineer B acted within the legal framework. The Engineer B Competitive Procurement Fairness Obligation holds that Engineer B must ensure all competing firms have a fair opportunity to compete on equal informational footing. The Good Intent Does Not Cure Procedural Impropriety principle holds that even if Engineer B's motivation was legitimate competitive awareness rather than deliberate exploitation, the structural harm to procurement fairness is independent of his subjective intent.

Rebuttals

The appearance-of-impropriety concern is weakened if Engineer B had no knowledge that Engineer A had already submitted qualifications at the time of the FOIA request, or if the procurement regulations explicitly permitted mid-process FOIA access. The timing-integrity warrant also loses force if Engineer B can demonstrate that the FOIA request was motivated by a purpose independent of competitive advantage, such as auditing agency compliance, and that the timing was coincidental rather than strategic.

Grounds

Engineer B intends to respond to the same RFQ as Engineer A. Engineer A has already submitted qualifications to the state agency. Before submitting his own firm's qualifications, Engineer B files a FOIA request and receives Engineer A's qualifications from the state. Engineer B then submits his own firm's qualifications. The sequence, FOIA request before own submission, creates a window in which Engineer B could calibrate his submission against a competitor's already-disclosed strategy.

Engineer B FOIA Pre-Submission Timing Violation Obligation FOIA Procurement Timing Integrity Obligation

Should Engineer B use the substantive content of Engineer A's qualifications, obtained through the FOIA request, to calibrate or strengthen his own submission, or should he refrain from exploiting that content for any competitive purpose in the same procurement?

Options considered:
O1 Engineer B reviews Engineer A's qualifications only to understand the general competitive landscape and refrains from using any substantive content: project descriptions, personnel credentials, methodologies, or competitive differentiators, to tailor, improve, or strategically reposition his own qualifications submission for the same procurement. Board's choice
O2 Engineer B treats Engineer A's FOIA-disclosed qualifications as lawfully available competitive intelligence and uses insights from that submission to strengthen his own qualifications, on the grounds that public disclosure under FOIA renders the information freely usable and that competitive awareness is a legitimate professional purpose.
O3 Engineer B refrains from using Engineer A's qualifications to alter his written submission but uses the disclosed information to prepare for the interview stage, anticipating comparative questions and identifying competitive differentiators, on the grounds that the written submission is already finalized and the interview is a distinct evaluative phase.
Argument structure:
Warrants

The Competitor Qualifications Content Non-Exploitation Obligation holds that a licensed engineer who lawfully obtains a competitor's qualifications through FOIA must refrain from using the substantive content to tailor or improve his own submission, because such use converts a lawful public records request into an instrument of unfair competitive advantage. The FOIA-Based Competitor Intelligence Ethical Use Constraint holds that while FOIA access is lawful, the engineer must use obtained information only for legitimate purposes, such as understanding the competitive landscape, and must not reverse-engineer or misappropriate the competitor's competitively sensitive content. The Good Intent Does Not Cure Procedural Impropriety principle holds that even if Engineer B's motivation was competitive awareness rather than deliberate copying, the structural harm to procurement fairness is independent of intent. The Public Procurement Transparency principle holds that FOIA disclosure serves the public interest and that Engineer B acted within the legal framework, suggesting that use of publicly disclosed information is not inherently improper.

Rebuttals

The non-exploitation warrant loses force if Engineer B made no substantive changes to his submission after reviewing Engineer A's qualifications, or if the information obtained was so general that it could not have influenced the content of his submission. The deception claim is strongest when Engineer B's submission contains structural, strategic, or content elements that mirror Engineer A's qualifications in ways that would not have appeared absent the FOIA review; absent such evidence, the downstream use concern remains speculative. The warrant also weakens if the applicable procurement framework treats all FOIA-disclosed information as freely usable competitive intelligence.

Grounds

The state provides Engineer B with Engineer A's qualifications submission in response to the FOIA request. Engineer B thereafter submits his own firm's qualifications to the state agency for the same public project. The sequence creates a factual question about whether Engineer B reviewed Engineer A's submission and used its content: project descriptions, personnel credentials, methodologies, competitive differentiators, to calibrate his own submission. The Board found the FOIA request itself ethical but did not make a finding about downstream use of the information obtained.

Competitor Qualifications Content Non-Exploitation Obligation FOIA-Based Competitor Intelligence Ethical Use Constraint

Should Engineer A proactively request that the state agency treat sensitive portions of his qualifications submission as confidential or proprietary before the submission window closes, or should he submit without seeking such protections and accept the FOIA disclosure risk as an inherent feature of public procurement?

Options considered:
O1 Engineer A proactively requests that the state agency designate sensitive portions of his qualifications, including proprietary methodologies, staffing structures, and competitive differentiators, as confidential or proprietary prior to submission, invoking any available FOIA exemption for trade secrets or proprietary business information to reduce the risk of mid-process competitor disclosure. Board's choice
O2 Engineer A submits his qualifications without seeking any confidentiality designation, treating public procurement submissions as inherently public records and relying on the procurement system's fairness norms, rather than individual protective action, to prevent competitors from exploiting FOIA access during the active selection process.
O3 Engineer A omits proprietary methodologies, sensitive staffing details, and competitively differentiating content from his qualifications submission entirely, including only information he is prepared to have publicly disclosed, and reserves sensitive content for the interview stage where it is not subject to FOIA disclosure as a submitted document.
Argument structure:
Warrants

The Public Procurement Confidentiality Self-Protection Obligation holds that engineers who submit qualifications to public agencies must exercise informed judgment about the confidentiality risks of including proprietary or sensitive information, recognizing that public procurement submissions may be subject to mandatory FOIA disclosure, and that the engineer bears responsibility for protecting their own confidential information by choosing not to include it or by seeking confidential treatment. The Public Procurement Transparency principle holds that public procurement submissions are inherently subject to public disclosure as a feature of the open procurement system, and that Engineer A submitted into a framework where FOIA access is a known structural feature. The Fairness in Professional Competition principle holds that Engineer A's failure to seek confidentiality protections does not eliminate Engineer B's independent obligation to conduct himself honorably, and that the ethical burden is shared rather than transferred entirely to Engineer A.

Rebuttals

The self-protection warrant fails if the applicable state FOIA statute contains no exemption for procurement qualifications, making a confidentiality request legally futile and therefore not a genuine protective option available to Engineer A. The warrant also weakens if the procurement regulations provide no mechanism for engineers to request confidential treatment of submitted qualifications, or if the agency's standard practice is to treat all submissions as fully public records regardless of any confidentiality designation. In those circumstances, Engineer A's failure to seek protections that do not exist cannot diminish his standing to object to Engineer B's conduct.

Grounds

Engineer A submits qualifications to the state agency in response to an RFQ. The submission contains competitively sensitive information: project descriptions, personnel credentials, methodologies, and competitive differentiators. Engineer A does not request that the state agency treat any portion of the submission as confidential or proprietary. Engineer B subsequently files a FOIA request, and the state provides Engineer A's qualifications to Engineer B. The resulting competitive information asymmetry disadvantages Engineer A in the ongoing procurement.

Engineer A Present Case Public Procurement Qualifications Confidentiality Self-Protection Public Procurement Confidentiality Self-Protection Obligation

Should the state agency disclose Engineer A's submitted qualifications in response to Engineer B's FOIA request during the active procurement process, or should it withhold the documents under a procurement-integrity rationale and advocate for regulatory reform to close the disclosure window?

Options considered:
O1 The state agency declines to release Engineer A's qualifications during the active procurement period, invoking a procurement-integrity rationale or seeking legal guidance on whether an implied exemption applies, and simultaneously advocates for legislative or regulatory reform to create an explicit FOIA exemption protecting submitted qualifications until after the selection process concludes. Board's choice
O2 The state agency complies with the FOIA request as legally required but notifies Engineer A of the pending disclosure before releasing the documents, providing Engineer A an opportunity to seek legal protection or request confidential treatment of proprietary content, thereby partially mitigating the competitive harm while fulfilling the statutory obligation.
O3 The state agency releases Engineer A's qualifications in full compliance with the applicable FOIA statute, treating the open records obligation as controlling and deferring any policy concerns about competitive equity to the legislative process, without taking independent action to notify Engineer A or delay disclosure.
Argument structure:
Warrants

Competing obligations include: (1) Public Procurement Regulatory Deference Obligation, the state agency was legally obligated to comply with the FOIA request under existing statute, and regulatory deference requires compliance with applicable law absent a recognized exemption; (2) Public Procurement Transparency as a Public Interest Protection Mechanism, FOIA exists to ensure government accountability and public access to government records, and the agency's compliance served this public interest function; (3) Procurement Integrity in Public Engineering: the state agency, as the public procurement authority, bears a co-responsibility for the informational equity of the selection process, and mid-process disclosure of a competitor's qualifications implicates the agency's own procurement integrity obligations; (4) Structural Asymmetry as a Systemic Procurement Integrity Failure, individual engineer ethics alone cannot remedy agency-created informational imbalances, and the agency's disclosure created a structural inequity that no individual actor could have prevented or remedied unilaterally; (5) Public Interest in Fair and Competitive Procurement Outcomes, procurement regulations should be revised to include a procurement-integrity exception shielding submitted qualifications from FOIA release until after the selection process concludes.

Rebuttals

The agency's ethical responsibility is significantly diminished if no procurement exemption exists in the applicable state FOIA statute, leaving the agency with no legal basis to withhold the documents and making compliance the only legally defensible course of action. The regulatory reform argument also loses force if the state legislature has affirmatively considered and rejected procurement-integrity exemptions, treating mid-process FOIA access as a deliberate feature of the open government framework rather than an inadvertent gap. Additionally, the agency's co-responsibility argument is weakest when the agency had no practical mechanism to notify Engineer A before disclosure or to delay compliance pending Engineer A's opportunity to seek legal protection.

Grounds

The state agency received Engineer B's FOIA request targeting Engineer A's submitted qualifications during an active procurement process in which both engineers were competing for the same contract. The state provided the documents pursuant to the applicable FOIA statute. This disclosure created a structural competitive information asymmetry: Engineer B obtained access to Engineer A's submission before Engineer B had submitted his own qualifications, while Engineer A had no reciprocal access and no advance notice that his submission would be disclosed to a competitor. The state agency's disclosure was legally defensible under existing statute but contributed materially to the competitive inequity that the Board found troubling.

Public Procurement Regulatory Deference Obligation Public Procurement Misrepresentation Check Transparency Recognition Obligation

After receiving Engineer A's qualifications through the FOIA request, should Engineer B refrain from using that content to calibrate or strengthen his own submission, or may he incorporate insights from the disclosed qualifications into his competitive strategy?

Options considered:
O1 Decline to use any insights, structural elements, or strategic content from Engineer A's disclosed qualifications when finalizing or presenting Engineer B's own submission, treating the FOIA-obtained documents as off-limits for competitive calibration throughout the entire procurement process including interviews. Board's choice
O2 Treat Engineer A's lawfully obtained qualifications as legitimately available competitive intelligence within the open procurement framework, incorporating relevant insights to strengthen Engineer B's submission on the grounds that FOIA access is a public right that carries no downstream use restriction.
O3 Voluntarily disclose to the state agency that Engineer B obtained and reviewed Engineer A's qualifications through a FOIA request before submitting his own, allowing the agency to determine whether the informational asymmetry warrants remedial action such as requiring Engineer B to resubmit or recuse, thereby subordinating personal competitive advantage to the integrity of the procurement process.
Argument structure:
Warrants

Competing obligations: (1) Competitor Qualifications Content Non-Exploitation Obligation. Engineer B must not use the content of Engineer A's qualifications to calibrate or strengthen his own submission, because the lawfulness of acquisition does not sanitize downstream competitive exploitation; (2) FOIA-Based Competitor Intelligence Ethical Use Constraint, information lawfully obtained through FOIA may be reviewed but must not be used to create an unfair competitive advantage; (3) Good Intent Does Not Cure Procedural Impropriety: even if Engineer B's intent was merely to be better informed, using the competitor's submission as a calibration tool constitutes a deceptive act under NSPE Code II.5; (4) Free and Open Competition as a Boundary Condition, within a legally open competitive framework, FOIA-obtained information may be treated as legitimately available competitive intelligence.

Rebuttals

The non-exploitation claim is strongest when Engineer B's submission contains structural, strategic, or content elements that mirror Engineer A's qualifications in ways that would not have appeared absent the FOIA disclosure. Uncertainty collapses if Engineer B made no substantive changes to his submission after reviewing Engineer A's qualifications, or if Engineer B can demonstrate the FOIA request was motivated by a purpose independent of competitive advantage. The deception claim weakens if the information obtained was entirely generic and added no calibration value to Engineer B's submission.

Grounds

Engineer B has received Engineer A's qualifications through a FOIA request filed before submitting his own qualifications. Engineer B now possesses detailed knowledge of Engineer A's submission strategy, staffing structure, and project approach. BER Case 93-3 establishes that good intent does not cure procedural impropriety, and that an engineer who gains access to a competitor's information through a procedurally questionable sequence bears an obligation not to exploit that information for personal competitive advantage. The competitive information asymmetry created by the FOIA disclosure persists through the interview stage of the procurement.

Engineer B BER 93-3 Faithful Agent Client Interest Primacy Over Altruistic Disclosure Obligation Faithful Agent Client Interest Primacy Over Altruistic Disclosure Obligation

Should the state agency revise procurement regulations to exempt submitted qualifications from FOIA disclosure until after the selection process is complete, or should it continue to treat submitted qualifications as immediately disclosable public records under existing FOIA statute?

Options considered:
O1 Revise procurement regulations to include an exemption shielding submitted qualifications from FOIA disclosure until after the selection process is complete, aligning FOIA law with the fairness norms embedded in qualification-based selection frameworks and eliminating the structural asymmetry that mid-process disclosure creates. Board's choice
O2 Continue treating submitted qualifications as immediately disclosable public records under existing FOIA statute, on the grounds that government transparency obligations are categorical and that competitive equity concerns are the responsibility of individual engineers and procurement participants to manage through self-protective measures.
O3 Without awaiting statutory reform, adopt an administrative protocol requiring the agency to notify submitting engineers of pending FOIA requests targeting their qualifications and to impose a brief hold period allowing submitting engineers to seek legal protection or confidentiality designation before disclosure, balancing transparency obligations with procurement fairness.
Argument structure:
Warrants

Competing obligations: (1) Public Procurement Transparency as a Public Interest Protection Mechanism. FOIA exists to ensure government accountability and public access to government records, and the agency was legally obligated to comply with the request under existing statute; (2) FOIA Procurement Timing Integrity Obligation, the agency's mid-process disclosure created a structural inequity that undermines the public interest the procurement system is designed to serve, implicating the agency's own procurement integrity obligations; (3) Public Procurement Confidentiality Self-Protection Obligation, the absence of a confidentiality request from Engineer A limited the agency's legal basis to withhold; (4) Structural Equity in Qualification-Based Selection, procurement regulations should be revised to include a procurement-integrity exception shielding submitted qualifications from FOIA release until after selection concludes.

Rebuttals

The agency's ethical responsibility is diminished if no procurement exemption exists in the applicable state FOIA statute, leaving the agency with no legal basis to withhold. The structural-reform warrant loses force if FOIA transparency is treated as categorically overriding procurement confidentiality interests in the public sector. The agency's co-responsibility claim weakens if Engineer A failed to invoke any available confidentiality designation mechanism prior to the FOIA request, since the self-protection obligation is a recognized caution in the NSPE framework.

Grounds

The state agency received Engineer A's qualifications in response to an RFQ and subsequently disclosed those qualifications to Engineer B in response to a FOIA request filed before Engineer B had submitted his own qualifications. The disclosure created a structural competitive information asymmetry that no individual engineer's ethical conduct alone could have prevented. The interview process was ongoing at the time of disclosure, meaning the asymmetry persisted beyond the submission stage. No procurement-integrity exception to the FOIA statute existed at the time of disclosure.

Procurement Integrity in Public Engineering Implicated By State Agency Disclosure Public Procurement Regulatory Deference Obligation

Should Engineer B refrain from using the content of Engineer A's FOIA-obtained qualifications to calibrate or strengthen his own submission, or may he treat the lawfully obtained information as legitimate competitive intelligence to inform his own qualifications?

Options considered:
O1 Engineer B refrains from using any substantive content from Engineer A's qualifications to calibrate, tailor, or strengthen his own submission or interview preparation, treating the obtained documents as off-limits for competitive purposes throughout the entire procurement process. Board's choice
O2 Engineer B reviews Engineer A's qualifications and uses the insights gained to inform and strengthen his own submission, treating the lawfully obtained public records as legitimate competitive intelligence available within the open procurement framework, consistent with the legal permissibility of the FOIA request.
O3 Engineer B discloses to the state agency that he obtained and reviewed Engineer A's qualifications through a FOIA request before submitting his own, allowing the agency to assess whether the informational asymmetry warrants any remedial action in the procurement process, and thereby preserving transparency while acknowledging the potential competitive distortion.
Argument structure:
Warrants

The FOIA-Based Competitor Intelligence Ethical Use Constraint holds that lawful acquisition of information does not automatically legitimize its downstream competitive use. The Good Intent Does Not Cure Procedural Impropriety principle, drawn analogically from BER 93-3, establishes that Engineer B's benevolent or neutral motive in filing the FOIA request does not excuse the competitive distortion created by reviewing and potentially incorporating Engineer A's submission content. The Improper Competitive Methods Prohibition under the NSPE Code encompasses conduct that, while technically lawful, undermines the integrity of the competitive process. Conversely, Free and Open Competition as a Boundary Condition and Public Procurement Transparency as a Public Interest Protection Mechanism support the view that information lawfully obtained through public records channels may be used within the competitive framework.

Rebuttals

The exploitation concern collapses if Engineer B made no substantive changes to his submission after reviewing Engineer A's qualifications, or if the information obtained was so general as to provide no meaningful competitive calibration. Conversely, the concern is strongest if Engineer B's submission contains structural, strategic, or content elements that mirror Engineer A's qualifications in ways that would not have appeared absent the FOIA review. The analogy to BER 93-3 may also fail if the present case's public procurement context is sufficiently distinct from BER 93-3's private-client fiduciary relationship to defeat the analogical transfer.

Grounds

Engineer B obtained Engineer A's qualifications submission through a FOIA request filed before Engineer B submitted his own qualifications. Engineer B then reviewed the documents and subsequently submitted his own qualifications. The BER Case 93-3 precedent established that good intent does not cure procedural impropriety, and that an engineer who reviews a competitor's or client's confidential information bears an obligation not to exploit that information for personal competitive advantage. The sequence created a structural informational asymmetry in which Engineer B could calibrate his submission against Engineer A's disclosed strategy.

Engineer B Good Intent Non-Justification Procurement Obligation Competitor Qualifications Content Non-Exploitation Obligation
10 sequenced 5 actions 5 events
Case timeline
A prior Board of Ethical Review case (No. 93-3) involving a franchiser's transition from Engineer A to Engineer B under ethically questionable circumstances was adjudicated and its findings recorded, creating a precedent that the current Discussion section applies to evaluate Engineer B's conduct in the present case. This prior ruling functions as an exogenous normative reference point that shapes the ethical analysis.
In the referenced BER Case No. 93-3, Engineer B agrees to review Engineer A's design information on behalf of the franchiser client, despite being explicitly instructed by the franchiser not to disclose their new relationship to Engineer A. Engineer B proceeds with the review within a week of being retained.
At stake (1)
  • Implicit obligation to consider whether accepting the engagement under these conditions was itself ethically appropriate
Fulfills (2)
  • Compliance with client instruction to maintain confidentiality of new relationship
  • Responsiveness to client's request for design review services
Violates (3)
  • Duty to avoid conflicts of interest with another engineer's ongoing engagement
  • Obligation not to review or exploit a colleague's work product without appropriate disclosure
  • Fair dealing toward Engineer A as a professional colleague
In BER Case No. 93-3, Engineer B voluntarily notifies Engineer A of his new relationship with the franchiser and shares preliminary results of his design review, in direct contravention of the franchiser's explicit instruction not to disclose the relationship. The Board determined this disclosure constituted a neglect of client interests.
Fulfills (2)
  • Transparency and honesty toward a professional colleague
  • Professional courtesy to Engineer A as the incumbent engineer
Violates (4)
  • Duty of loyalty to client as faithful agent and trustee
  • Obligation to follow lawful client instructions regarding confidentiality
  • Duty to protect client's legitimate business interests
  • Obligation not to neglect client interests for the benefit of third parties
Engineer A voluntarily responds to a public Request for Qualifications by submitting his firm's engineering qualifications to a state agency through the public procurement process. This initiates his firm's participation in the competitive selection process.
Fulfills (3)
  • Participation in open and competitive public procurement process
  • Honest and accurate representation of firm qualifications to a public agency
  • Compliance with state public procurement procedures
Prior to the interview phase of the procurement process, Engineer B deliberately files a state Freedom of Information Act request to obtain a copy of competitor Engineer A's submitted qualifications. This action is legally permissible but strategically timed to gain competitive advantage before submitting his own qualifications.
Fulfills (2)
  • Compliance with the letter of state FOIA law
  • Participation within the legal framework of public procurement
Violates (4)
  • Fair dealing with a professional competitor
  • Spirit of open and honest competition without exploitation of procedural mechanisms for strategic gain
  • Duty to avoid actions that undermine colleagues' legitimate competitive interests
  • Implicit professional norms against using legal mechanisms opportunistically to disadvantage competitors in a shared procurement process
The state agency's interview process for the RFQ remains active and incomplete at the time Engineer B obtains Engineer A's qualifications, meaning the competitive selection has not yet concluded and Engineer A retains a live stake in the outcome. This temporal overlap is a critical contextual fact that heightens the ethical stakes of the FOIA disclosure.
The state agency releases Engineer A's submitted qualifications to Engineer B in response to the FOIA request, making confidential competitive information publicly disclosed. This is an automatic legal outcome triggered by the FOIA filing and applicable public records law.
As a consequence of the FOIA disclosure, Engineer A's proprietary competitive qualifications, including methodologies, experience claims, key personnel, and strategic positioning, are now in the hands of a direct competitor during an active procurement. This exposure is irreversible and cannot be remedied after the fact.
As a direct outcome of the FOIA disclosure, Engineer B possesses Engineer A's full qualifications while Engineer A has no equivalent knowledge of Engineer B's approach, creating an unequal competitive footing during an active procurement. This asymmetry persists through the remainder of the selection process.
After receiving Engineer A's qualifications through the FOIA disclosure, Engineer B proceeds to submit his own firm's engineering qualifications to the state agency for the same public project. This submission is informed by prior access to a competitor's submission.
Fulfills (3)
  • Compliance with state public procurement submission requirements
  • Honest representation of own firm's qualifications
  • Participation in legally sanctioned competitive process
Violates (3)
  • Fair dealing with professional competitor
  • Avoiding use of improperly or opportunistically obtained competitive intelligence to gain advantage
  • Spirit of equitable competition in public procurement
Narrative (2 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are Engineer B, a licensed engineer whose firm intends to respond to a state agency's public request for qualifications for an engineering project. The state has issued an RFQ and is accepting qualifications submissions through its public procurement procedures. Engineer A, a direct competitor, has already submitted his firm's qualifications to the state agency in response to the same RFQ. As a competitor in an active public procurement, you are weighing how to approach your own submission and what resources and information are available to you under state law. The decisions you make in the coming stages will have implications for professional conduct, competitive fairness, and the integrity of the procurement process.

Main characters (2)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Engineer B Roles in this case: FOIA-Requesting Competing EngineerBER 93-3 Replacement Design EngineerPresent Case Public Procurement Competitor

Guided by: Procurement Integrity in Public Engineering Implicated By State Agency Disclosure, Good Intent Does Not Cure Procedural Impropriety Invoked in BER 93-3 Analogy, FOIA-Based Competitor Intelligence Ethical Use Constraint

Engineer B has a legal right under FOIA to request public records at any time, yet exercising that right before competing submissions are finalized creates an unfair informational advantage. Fulfilling the duty to compete vigorously for the client conflicts directly with the duty to maintain a level competitive playing field. The timing of the FOIA request — pre-submission rather than post-award — transforms a legitimate transparency tool into a mechanism for competitive intelligence gathering, meaning that honoring one duty (zealous competition) structurally undermines the other (procurement fairness).

Attaches to role: FOIA-Requesting Competing Engineer

Once Engineer B has lawfully obtained Engineer A's qualification documents through FOIA, a genuine dilemma arises between the obligation not to exploit that content for competitive advantage and the practical reality that the information is now known and cannot be unknown. The constraint prohibits using FOIA-acquired intelligence to tailor or strengthen Engineer B's own submission, yet no enforcement mechanism prevents cognitive use of the information. Fulfilling the non-exploitation obligation requires Engineer B to self-police internal decision-making in a way that is nearly impossible to verify, creating a tension between the ethical duty and the structural impossibility of fully honoring it once disclosure has occurred.

Attaches to role: FOIA-Requesting Competing Engineer

Tension between Engineer B FOIA Pre-Submission Timing Violation Obligation and FOIA Procurement Timing Integrity Obligation

Attaches to role: FOIA-Requesting Competing Engineer

Tension between Engineer B Honorable Procurement Conduct Obligation and FOIA Procurement Timing Integrity Obligation

Attaches to role: FOIA-Requesting Competing Engineer

Tension between Engineer B Present Case Public Procurement FOIA Timing Appearance of Impropriety Avoidance and FOIA Procurement Timing Integrity Obligation

Attaches to role: FOIA-Requesting Competing Engineer

Tension between Engineer B Good Intent Non-Justification Procurement Obligation and Competitor Qualifications Content Non-Exploitation Obligation

Attaches to role: FOIA-Requesting Competing Engineer

Tension between Engineer B Present Case FOIA Pre-Submission Competitor Intelligence Abstention and Engineer B Present Case Public Procurement Regulatory Deference

Attaches to role: FOIA-Requesting Competing Engineer

Tension between Engineer B BER 93-3 Faithful Agent Client Interest Primacy Over Altruistic Disclosure Obligation and Faithful Agent Client Interest Primacy Over Altruistic Disclosure Obligation

Attaches to role: FOIA-Requesting Competing Engineer

In the BER 93-3 context, Engineer B acting as a replacement design engineer owes a faithful-agent duty to the franchiser client, including compliance with confidentiality instructions that restrict disclosure of information about the prior engineer's work. However, the public procurement transparency obligation requires that misrepresentations or material omissions in qualification submissions be surfaced to protect the integrity of the public selection process. These two duties collide when client confidentiality instructions would suppress information that the public agency needs to make an informed, fair procurement decision — meaning that serving the client faithfully may simultaneously compromise public procurement integrity.

Attaches to role: BER 93-3 Replacement Design Engineer
Engineer A Roles in this case: Public RFQ Submitting EngineerBER 93-3 Incumbent Design EngineerPresent Case Incumbent Engineer

Engineer B has a legal right under FOIA to request public records at any time, yet exercising that right before competing submissions are finalized creates an unfair informational advantage. Fulfilling the duty to compete vigorously for the client conflicts directly with the duty to maintain a level competitive playing field. The timing of the FOIA request — pre-submission rather than post-award — transforms a legitimate transparency tool into a mechanism for competitive intelligence gathering, meaning that honoring one duty (zealous competition) structurally undermines the other (procurement fairness).

Attaches to role: Public RFQ Submitting Engineer

Once Engineer B has lawfully obtained Engineer A's qualification documents through FOIA, a genuine dilemma arises between the obligation not to exploit that content for competitive advantage and the practical reality that the information is now known and cannot be unknown. The constraint prohibits using FOIA-acquired intelligence to tailor or strengthen Engineer B's own submission, yet no enforcement mechanism prevents cognitive use of the information. Fulfilling the non-exploitation obligation requires Engineer B to self-police internal decision-making in a way that is nearly impossible to verify, creating a tension between the ethical duty and the structural impossibility of fully honoring it once disclosure has occurred.

Attaches to role: Public RFQ Submitting Engineer

Tension between Engineer A Present Case Public Procurement Qualifications Confidentiality Self-Protection and Public Procurement Confidentiality Self-Protection Obligation

Attaches to role: Public RFQ Submitting Engineer

Tension between Engineer A Public Procurement Qualifications Confidentiality Self-Protection Obligation and Public Procurement Confidentiality Self-Protection Obligation

Attaches to role: Public RFQ Submitting Engineer

In the BER 93-3 context, Engineer B acting as a replacement design engineer owes a faithful-agent duty to the franchiser client, including compliance with confidentiality instructions that restrict disclosure of information about the prior engineer's work. However, the public procurement transparency obligation requires that misrepresentations or material omissions in qualification submissions be surfaced to protect the integrity of the public selection process. These two duties collide when client confidentiality instructions would suppress information that the public agency needs to make an informed, fair procurement decision — meaning that serving the client faithfully may simultaneously compromise public procurement integrity.

Attaches to role: BER 93-3 Incumbent Design Engineer

Other people involved in the case but not central to the opening narrative.

In the BER 93-3 context, Engineer B acting as a replacement design engineer owes a faithful-agent duty to the franchiser client, including compliance with confidentiality instructions that restrict disclosure of information about the prior engineer's work. However, the public procurement transparency obligation requires that misrepresentations or material omissions in qualification submissions be surfaced to protect the integrity of the public selection process. These two duties collide when client confidentiality instructions would suppress information that the public agency needs to make an informed, fair procurement decision — meaning that serving the client faithfully may simultaneously compromise public procurement integrity.


These tensions did not map cleanly to a single character.

Tension between Competitor Qualifications Content Non-Exploitation Obligation and FOIA-Based Competitor Intelligence Ethical Use Constraint

Tension between Procurement Integrity in Public Engineering Implicated By State Agency Disclosure and Public Procurement Regulatory Deference Obligation

Tension between Public Procurement Regulatory Deference Obligation and Public Procurement Misrepresentation Check Transparency Recognition Obligation

Opening States (10)
Engineer B FOIA-Based Acquisition of Competitor Qualifications Engineer B Asymmetric Competitive Advantage Post-FOIA Free and Open Competition Legal Framework Active State Competitor Qualification Visibility Advantage State Engineer A Qualifications Submitted to Public RFQ Confidential Information Submitted to Public Disclosure-Eligible Repository State Competitive Procurement Public Interest Alignment State Client Transition Overlap Engagement State Engineering Procurement Free Competition Legal Framework BER 93-3 Franchiser-Engineer B Covert Transition Engagement
Summary
  • Using legally available public records mechanisms like FOIA to obtain competitor information during procurement processes is ethically permissible for engineers, provided the request complies with established procedural rules.
  • The resolution as a 'stalemate' transformation indicates that competing ethical obligations were present but neither side was clearly dominant, suggesting that transparency laws and professional ethics can coexist without one automatically overriding the other.
  • Engineers must distinguish between the legality of obtaining competitor information through public channels and the ethical constraints governing how that information may subsequently be used in competitive contexts.