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
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
NSPE Code Provisions Referenced
Section II. Rules of Practice 3 107 entities

Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.

Applies To (20)
Role
Engineer A Public RFQ Submitting Engineer Engineer A must ensure his qualifications submission accurately reflects competence in the technical fields required by the RFQ.
Role
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.
Principle
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.
Principle
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.
Principle
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.
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.
Obligation
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.
Obligation
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.
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.
State
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.
State
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.
Resource
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.
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.
Action
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.
Event
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.
Capability
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.
Capability
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.
Capability
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.
Constraint
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.
Constraint
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.

Engineers shall act for each employer or client as faithful agents or trustees.

Applies To (31)
Role
Engineer A BER 93-3 Incumbent Design Engineer Engineer A owed faithful agent duties to the franchiser client during the multi-year design engagement.
Role
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.
Role
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.
Role
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.
Principle
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.
Principle
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.
Principle
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.
Principle
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.
Principle
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.
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.
Obligation
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.
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.
Obligation
Engineer B Honorable Procurement Conduct Obligation II.4. requires honorable and trustworthy conduct toward clients and the broader process, directly supporting this obligation.
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.
State
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.
State
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.
Resource
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.
Resource
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.
Resource
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.
Resource
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.
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.
Action
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.
Event
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.
Event
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.
Event
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.
Capability
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.
Capability
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.
Capability
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.
Capability
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.
Constraint
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.
Constraint
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.

Engineers shall avoid deceptive acts.

Applies To (56)
Role
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.
Role
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.
Role
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.
Principle
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.
Principle
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.
Principle
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.
Principle
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.
Principle
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.
Principle
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.
Principle
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.
Principle
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.
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.
Obligation
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.
Obligation
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.
Obligation
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.
Obligation
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.
Obligation
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.
Obligation
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.
Obligation
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.
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.
State
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.
State
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.
State
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.
Resource
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.
Resource
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.
Resource
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.
Resource
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.
Resource
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.
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.
Action
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.
Action
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.
Event
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.
Event
Interview Process Ongoing During Disclosure Participating in an ongoing interview process while possessing improperly obtained competitor information creates a deceptive competitive situation.
Event
BER 93-3 Precedent Established The precedent addresses whether exploiting FOIA-obtained competitor information during selection constitutes a deceptive act under the code.
Capability
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.
Capability
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.
Capability
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.
Capability
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.
Capability
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.
Capability
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.
Capability
Engineer B Competitor Qualifications Content Non-Exploitation Exploiting competitor qualifications content obtained through a pre-submission FOIA request constitutes a deceptive competitive act.
Capability
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.
Capability
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.
Capability
Engineer B Public Procurement Integrity Articulation Understanding the public interest rationale for procurement rules supports recognizing why deceptive competitive acts undermine those rules.
Constraint
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.
Constraint
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.
Constraint
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.
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.
Constraint
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.
Constraint
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.
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.
Constraint
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.
Constraint
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.
Constraint
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.
Constraint
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.
Constraint
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.
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
View Extraction
Each question is shown with its corresponding conclusion(s). Board questions are expanded by default.
Decisions & Arguments
View Extraction
Causal-Normative Links 5
Fulfills
  • Public Procurement Regulatory Deference Obligation
  • Engineer B Present Case Public Procurement Regulatory Deference
  • Engineer B Present Case Public Procurement Misrepresentation Check Transparency Recognition
Violates
  • Competitor Qualifications Content Non-Exploitation Obligation
  • Engineer B FOIA Content Non-Exploitation Obligation
  • Engineer B Honorable Procurement Conduct Obligation
  • Engineer B Present Case Competitor Qualifications Content Non-Exploitation
  • Engineer B Competitive Procurement Fairness Obligation
Fulfills None
Violates
  • Client Confidentiality Instruction Faithful Agent Compliance Obligation
  • Faithful Agent Client Interest Primacy Over Altruistic Disclosure Obligation
  • Engineer B BER 93-3 Client Confidentiality Instruction Faithful Agent Compliance
  • Engineer B BER 93-3 Faithful Agent Client Interest Primacy Over Altruistic Disclosure
Fulfills None
Violates
  • FOIA Pre-Submission Competitor Intelligence Abstention Obligation
  • Competitor Qualifications Content Non-Exploitation Obligation
  • Public Procurement FOIA Timing Appearance of Impropriety Avoidance Obligation
  • Engineer B FOIA Pre-Submission Timing Violation Obligation
  • Engineer B FOIA Content Non-Exploitation Obligation
  • Engineer B Good Intent Non-Justification Procurement Obligation
  • Engineer B Honorable Procurement Conduct Obligation
  • Engineer B Present Case FOIA Pre-Submission Competitor Intelligence Abstention
  • Engineer B Present Case Public Procurement FOIA Timing Appearance of Impropriety Avoidance
  • Engineer B Present Case Competitor Qualifications Content Non-Exploitation
  • Engineer B Competitive Procurement Fairness Obligation
Fulfills
  • Public Procurement Regulatory Deference Obligation
Violates
  • Engineer A Present Case Public Procurement Qualifications Confidentiality Self-Protection
Fulfills None
Violates
  • Client Confidentiality Instruction Faithful Agent Compliance Obligation
  • Faithful Agent Client Interest Primacy Over Altruistic Disclosure Obligation
  • Engineer B BER 93-3 Client Confidentiality Instruction Faithful Agent Compliance
  • Engineer B BER 93-3 Faithful Agent Client Interest Primacy Over Altruistic Disclosure
Decision Points 11

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:
Submit Own Qualifications First, Then File FOIA Board's choice 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.
File FOIA Before Own Submission as Permitted by Law 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.
Decline to File FOIA During Active Procurement 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.
Toulmin Summary:
Warrants II.4 II.5

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.

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:
Refrain from Using Competitor Content to Calibrate Submission Board's choice 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.
Use Disclosed Information as Lawful Competitive Intelligence 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.
Use Competitor Information Only for Interview Preparation 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.
Toulmin Summary:
Warrants II.4 II.5

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.

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:
Request Confidential Treatment Before Submitting Board's choice 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.
Submit Without Confidentiality Designation and Accept FOIA Risk 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.
Exclude Sensitive Content from Public Submission 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.
Toulmin Summary:
Warrants II.4

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.

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

Options:
Submit Own Qualifications Before Filing FOIA Board's choice Engineer B submits his firm's own qualifications to the state agency first, then exercises his FOIA rights to obtain Engineer A's submission, ensuring that his own submission was independently conceived and that no pre-submission informational asymmetry was created.
File FOIA Before Submitting Own Qualifications Engineer B exercises his legally available FOIA rights before submitting his own qualifications, treating the public records framework as an open competitive resource available to all participants and relying on the state's disclosure decision as the relevant ethical boundary.
Abstain from FOIA During Active Procurement Engineer B refrains entirely from filing any FOIA request targeting competitor qualifications while the procurement selection process remains active, deferring any public records inquiry until after the agency has made its selection decision.
Toulmin Summary:
Warrants II.4 II.5 III.2

Competing obligations include: (1) Public Procurement Transparency as a Public Interest Protection Mechanism. FOIA access to government records is a legally recognized public right that Engineer B was entitled to exercise; (2) Free and Open Competition as a Boundary Condition, ethical conduct is assessed within the legally open competitive framework, and Engineer B broke no explicit rule; (3) FOIA Procurement Timing Integrity Obligation. Engineer B should have submitted his own qualifications before filing the FOIA request to avoid creating an informational asymmetry and the appearance of impropriety; (4) Engineer B Competitive Procurement Fairness Obligation, competitors in a qualification-based selection process are entitled to assume informational parity at the time of submission; (5) Faithful Agent Obligation extended by analogy from BER 93-3. Engineer B owes a duty of honorable dealing to the integrity of the public procurement process itself, constraining exploitation of legal mechanisms for asymmetric competitive advantage.

Rebuttals

The ethical question is most uncertain 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 to submitted qualifications. The timing-integrity warrant also loses force if the public procurement system's FOIA accessibility is treated as a structural feature that eliminates any engineer's reasonable expectation of submission confidentiality, placing the entire risk of disclosure on the submitting engineer rather than on the requesting competitor.

Grounds

Engineer B filed a FOIA request and obtained Engineer A's already-submitted qualifications before Engineer B had submitted his own firm's qualifications to the state agency under the RFQ. The state provided the documents pursuant to the applicable FOIA statute. Engineer B then submitted his own qualifications, creating a competitive information asymmetry in which Engineer B had access to Engineer A's submission strategy while Engineer A had no reciprocal access. BER Case 93-3 established a precedent regarding the faithful agent principle and the principle that good intent does not cure procedural impropriety.

Should Engineer A proactively request that the state agency treat his submitted qualifications as confidential or proprietary before the submission deadline, or is it sufficient to rely on the procurement system's general framework without seeking specific confidentiality protections?

Options:
Request Confidential Treatment Before Submitting Board's choice Engineer A proactively designates sensitive portions of his qualifications submission, including methodologies, staffing structures, and strategic frameworks, as proprietary or confidential before or at the time of submission, invoking any available FOIA exemption to reduce the risk of mid-process competitor disclosure.
Submit Without Confidentiality Designation Engineer A submits his qualifications without requesting confidential treatment, relying on the procurement system's general framework and the implicit assumption that competing firms will not exploit FOIA mechanisms to access submissions before the deadline has closed for all parties.
Redact Sensitive Content Before Submitting Engineer A submits a version of his qualifications that omits or generalizes the most competitively sensitive content, such as proprietary methodologies or staffing strategies, so that even if the submission is disclosed under FOIA, the information available to competitors is limited in its strategic value.
Toulmin Summary:
Warrants II.1.c III.4

Competing obligations include: (1) Public Procurement Confidentiality Self-Protection Obligation. Engineer A bears an affirmative responsibility to seek confidential treatment of sensitive submission content, particularly trade-sensitive methodologies, staffing structures, or strategic frameworks, to the extent permitted by the applicable FOIA statute; (2) Public Procurement Transparency as a Public Interest Protection Mechanism, documents submitted to public agencies are presumptively public records, and Engineer A assumed this risk by submitting to a public procurement process without seeking protection; (3) Fairness in Professional Competition. Engineer A submitted in good faith within a framework that implicitly assumes competitors cannot access each other's submissions pre-deadline, and the ethical burden should not fall entirely on Engineer A to anticipate and foreclose FOIA exploitation; (4) Distributed Ethical Responsibility, the ethical failure in this case is shared among Engineer B, the state agency, and Engineer A, and Engineer A's inaction is one contributing factor rather than the sole cause.

Rebuttals

The self-protection obligation loses force if the applicable state FOIA statute contains no exemption for procurement qualifications, making a confidentiality request legally futile and therefore not a genuine professional obligation. The question is also most acute when the procurement regulations provide a specific mechanism for engineers to request confidential treatment but Engineer A did not invoke it; if no such mechanism exists, Engineer A's failure to act cannot be characterized as a breach of a recognized professional duty. Additionally, Engineer A's failure to seek confidentiality protections does not eliminate Engineer B's independent obligation to conduct himself honorably, since the availability of an opportunity to exploit a vulnerability does not become an ethical permission simply because another party failed to foreclose it.

Grounds

Engineer A submitted qualifications to the state agency in response to an RFQ without requesting that any portion of the submission be treated as confidential or proprietary. Engineer B subsequently filed a FOIA request and the state agency disclosed Engineer A's qualifications. Engineer A's submission was thereby exposed to a competitor before Engineer B had submitted his own qualifications, creating a competitive information asymmetry. Many FOIA statutes include exemptions for trade secrets or proprietary business information that submitting engineers may invoke, and the applicable procurement regulations may have provided a mechanism for requesting confidential treatment.

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:
Withhold Documents and Advocate Regulatory Reform Board's choice 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.
Comply with FOIA and Notify Submitting Engineer 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.
Comply Fully with FOIA as Legally Required 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.
Toulmin Summary:
Warrants I.1 III.2

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.

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

Options:
File FOIA After Own Submission Board's choice Submit the firm's own qualifications to the state agency first, then file the FOIA request to obtain Engineer A's qualifications, eliminating the pre-submission informational asymmetry and satisfying the Board's appearance-of-impropriety standard.
File FOIA Before Own Submission File the FOIA request before submitting the firm's own qualifications, treating FOIA access as a legally open public right that imposes no sequencing obligation on the requesting engineer, and relying on the state's legal duty to disclose as the operative ethical boundary.
Abstain from FOIA During Active Procurement Decline to file any FOIA request targeting competitor qualifications until after the selection process is complete, treating the procurement period as a domain where competitive equity overrides general public disclosure rights regardless of the legal availability of FOIA.
Toulmin Summary:
Warrants II.4 III.2

Competing obligations: (1) Public Procurement Transparency as a Public Interest Protection Mechanism. FOIA access to government records is a legally recognized public right that Engineer B may lawfully invoke; (2) FOIA Procurement Timing Integrity Obligation, Engineer B should have submitted his own qualifications before filing the FOIA request to avoid creating an informational asymmetry; (3) Free and Open Competition as a Boundary Condition: ethical conduct is assessed within the legally open competitive framework, which permits FOIA access; (4) Fairness in Professional Competition, competitors must not gain informational advantages unavailable to all parties during an active procurement.

Rebuttals

The ethical question is most acute when Engineer B had actual knowledge that Engineer A had already submitted qualifications at the time of the FOIA request. Uncertainty collapses in Engineer B's favor if procurement regulations explicitly permit mid-process FOIA access to submitted qualifications, or if Engineer B had no knowledge of Engineer A's prior submission. The timing-integrity warrant loses force if the public procurement system's FOIA accessibility is treated as a structural feature that eliminates any engineer's reasonable expectation of submission confidentiality.

Grounds

Engineer B files a FOIA request with the state agency after Engineer A has already submitted qualifications in response to an RFQ, but before Engineer B has submitted his own firm's qualifications. The state provides the requested documents, creating a competitive information asymmetry: Engineer B can review Engineer A's submission strategy before finalizing his own. BER Case 93-3 establishes that good intent does not cure procedural impropriety in analogous competitive contexts.

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:
Refrain from Using Competitor Content Board's choice 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.
Use FOIA Content as Competitive Intelligence 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.
Disclose FOIA Review to Procuring Agency 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.
Toulmin Summary:
Warrants II.4 II.5 III.2

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.

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:
Adopt Procurement-Integrity FOIA Exemption Board's choice 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.
Maintain Full FOIA Disclosure Compliance 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.
Implement Notice-and-Hold Disclosure Protocol 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.
Toulmin Summary:
Warrants I.1 III.2

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.

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

Options:
Submit Own Qualifications First, Then File FOIA Board's choice Engineer B submits his firm's own qualifications to the state agency before filing any FOIA request, ensuring that no competitive information asymmetry is created by the sequence of actions and that the appearance of impropriety is avoided.
File FOIA Before Submitting Own Qualifications Engineer B files the FOIA request and reviews Engineer A's qualifications before submitting his own, relying on the legal permissibility of FOIA access as sufficient justification and treating the public records framework as an open competitive resource available to all participants.
File FOIA But Decline to Review Competitor Content Engineer B files the FOIA request for general procurement transparency purposes but refrains from reviewing the substantive content of Engineer A's qualifications submission, thereby preserving the legal exercise of public records access while avoiding exploitation of the competitive information asymmetry.
Toulmin Summary:
Warrants II.4 II.5

Public Procurement Transparency as a Public Interest Protection Mechanism supports Engineer B's legal right to access government records via FOIA. However, the FOIA Procurement Timing Integrity Obligation holds that Engineer B should have submitted his own qualifications first to avoid creating an informational asymmetry. The Appearance of Impropriety Standard further requires that engineers sequence their actions to avoid conduct that, while legally permissible, undermines the fairness architecture of competitive procurement. Free and Open Competition as a Boundary Condition supports the view that ethical conduct is assessed within the legally open competitive framework, potentially permitting the request.

Rebuttals

The ethical question is most acute if Engineer B knew Engineer A had already submitted at the time of the FOIA request. If Engineer B had no such knowledge, or if procurement regulations explicitly permitted mid-process FOIA access without restriction, the timing concern is diminished. Additionally, if Engineer B made no substantive changes to his submission after reviewing Engineer A's qualifications, the competitive harm is reduced.

Grounds

Engineer B filed a FOIA request and obtained Engineer A's already-submitted qualifications before Engineer B submitted his own firm's qualifications to the same state RFQ. The state provided the documents pursuant to the FOIA request. This sequence created a competitive information asymmetry in which Engineer B could review and potentially calibrate his submission against Engineer A's disclosed strategy.

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:
Refrain From Using Competitor Content Competitively Board's choice 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.
Use FOIA Information as Legitimate Competitive Intelligence 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.
Disclose FOIA Review to Procuring Agency 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.
Toulmin Summary:
Warrants II.4 II.5

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.

10 sequenced 5 actions 5 events
Action (volitional) Event (occurrence) Associated decision points
DP1
Engineer B, a competitor of Engineer A in the same public RFQ, files a FOIA requ...
Submit Own Qualifications First, Then Fi... File FOIA Before Own Submission as Permi... Decline to File FOIA During Active Procu...
Full argument
DP2
Having lawfully obtained Engineer A's qualifications through the FOIA request, E...
Refrain from Using Competitor Content to... Use Disclosed Information as Lawful Comp... Use Competitor Information Only for Inte...
Full argument
DP4
Engineer B's FOIA Timing and Competitive Conduct Obligation: Whether Engineer B ...
Submit Own Qualifications Before Filing ... File FOIA Before Submitting Own Qualific... Abstain from FOIA During Active Procurem...
Full argument
DP6
State Agency Procurement Integrity and Regulatory Reform Obligation: Whether the...
Withhold Documents and Advocate Regulato... Comply with FOIA and Notify Submitting E... Comply Fully with FOIA as Legally Requir...
Full argument
DP7
Engineer B: FOIA Request Timing Relative to Own Submission in Active Procurement
File FOIA After Own Submission File FOIA Before Own Submission Abstain from FOIA During Active Procurem...
Full argument
DP9
State Agency and Engineer A: Systemic Procurement Integrity - Whether Submitted ...
Adopt Procurement-Integrity FOIA Exempti... Maintain Full FOIA Disclosure Compliance Implement Notice-and-Hold Disclosure Pro...
Full argument
DP10
Engineer B's FOIA Timing and Appearance of Impropriety: Whether Engineer B shoul...
Submit Own Qualifications First, Then Fi... File FOIA Before Submitting Own Qualific... File FOIA But Decline to Review Competit...
Full argument
DP11
Engineer B's Use of Competitor Qualifications Content: Whether Engineer B, havin...
Refrain From Using Competitor Content Co... Use FOIA Information as Legitimate Compe... Disclose FOIA Review to Procuring Agency
Full argument
2 BER Case 93-3: Engineer B Reviews Design Information Within the week following retention by franchiser, before Engineer A's contract expired
3 BER Case 93-3: Engineer B Discloses Relationship to Engineer A Following completion of design review, several weeks before Engineer A's contract expired
DP3
Engineer A submitted qualifications to a public agency in response to an RFQ wit...
Request Confidential Treatment Before Su... Submit Without Confidentiality Designati... Exclude Sensitive Content from Public Su...
Full argument
DP5
Engineer A's Affirmative Self-Protection Obligation: Whether Engineer A was obli...
Request Confidential Treatment Before Su... Submit Without Confidentiality Designati... Redact Sensitive Content Before Submitti...
Full argument
5 Engineer A Submits RFQ Qualifications Initial submission phase, prior to interview process
DP8
Engineer B: Use of Competitor's Qualifications Content After FOIA Disclosure
Refrain from Using Competitor Content Use FOIA Content as Competitive Intellig... Disclose FOIA Review to Procuring Agency
Full argument
7 Competitive Information Asymmetry Created Immediately following state's release of documents; during ongoing interview process
8 Interview Process Ongoing During Disclosure Concurrent with FOIA filing and disclosure; prior to Engineer B's submission
9 BER 93-3 Precedent Established Prior to present case; referenced in Discussion section as established precedent
10 Engineer A's Qualifications Exposed to Competitor Upon state's release of documents to Engineer B; persists through remainder of procurement
Causal Flow
  • Engineer A Submits RFQ Qualifications Engineer B Files FOIA Request
  • Engineer B Files FOIA Request Engineer B Submits Own Qualifications
  • Engineer B Submits Own Qualifications BER_Case_93-3:_Engineer_B_Reviews_Design_Information
  • BER_Case_93-3:_Engineer_B_Reviews_Design_Information BER_Case_93-3:_Engineer_B_Discloses_Relationship_to_Engineer_A
  • BER_Case_93-3:_Engineer_B_Discloses_Relationship_to_Engineer_A State Provides FOIA Documents
Opening Context
View Extraction

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.

From the perspective of Engineer A Public RFQ Submitting Engineer
Characters (9)
stakeholder

A strategically opportunistic competitor who leverages public records law as a competitive intelligence tool to gain an informational advantage before entering the same procurement process.

Ethical Stance: 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
Motivations:
  • To gain insight into a rival's qualifications submission and tailor his own firm's proposal accordingly, maximizing his chances of winning the public contract.
stakeholder

An established service provider facing involuntary contract termination who must navigate the professional and ethical complexities of a transition period while a successor engineer is introduced to his client relationship.

Motivations:
  • To fulfill remaining contractual obligations professionally and protect accumulated proprietary project knowledge while managing the reputational and financial impact of client loss.
  • To protect sensitive business and design information developed during the prior engagement while seamlessly transitioning to a new engineering relationship without operational disruption.
protagonist

A good-faith participant in a public procurement process who submits qualifications under the reasonable assumption of procedural fairness, only to find his proprietary submission exposed to a direct competitor.

Motivations:
  • To win a public contract through merit-based competition while protecting the confidential methodologies and firm capabilities disclosed in his qualifications submission.
authority

A government body bound by dual and potentially conflicting statutory obligations — public transparency through FOIA and fair competitive procurement — that mechanically fulfills disclosure requests without apparent consideration of competitive timing implications.

Motivations:
  • To comply with statutory public records obligations while administering a legally defensible and procedurally compliant engineering selection process.
protagonist

Retained by franchiser for multi-year engineering design services for a chain of stores; contract terminated with notice of non-renewal; subject to replacement by Engineer B during the transition period

stakeholder

Retained by franchiser to replace Engineer A; explicitly instructed to keep the engagement confidential from Engineer A; reviewed pending design concerns; then disclosed the relationship to Engineer A contrary to client instructions; later retained as permanent design engineer

stakeholder

Competing engineer in the present case who submitted qualifications to a public agency under public procurement procedures and whose timing of the FOIA/qualifications review request raised concern; found to have acted consistently with applicable laws and regulations

protagonist

Incumbent engineer in the present case whose qualifications submission to a public agency was subject to review by competing Engineer B under public procurement and FOIA laws; analogous to Engineer A in BER 93-3 as the party whose representations were scrutinized

stakeholder

The public entity administering the procurement process; the referenced public procurement system designed to advance the public interest in obtaining the most qualified engineering services

Ethical Tensions (14)

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

Obligation Vs Constraint
Affects: Engineer B FOIA Pre-Submission Timing Violation Obligation
Moral Intensity (Jones 1991):
Magnitude: high Probability: high immediate direct concentrated

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

Obligation Vs Constraint
Affects: Engineer B Competitive Procurement Fairness Obligation
Moral Intensity (Jones 1991):
Magnitude: high Probability: high immediate direct concentrated

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

Obligation Vs Constraint
Affects: Engineer A Present Case Public Procurement Qualifications Confidentiality Self-Protection

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

Obligation Vs Constraint
Affects: Engineer

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

Obligation Vs Constraint
Affects: Engineer

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

Obligation Vs Constraint
Affects: Public
Moral Intensity (Jones 1991):
Magnitude: high Probability: medium near-term direct diffuse

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

Obligation Vs Constraint
Affects: 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

Obligation Vs Constraint
Affects: Engineer

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

Obligation Vs Constraint
Affects: Client

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

Obligation Vs Constraint
Affects: Engineer

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

Obligation Vs Constraint
Affects: 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).

Obligation Vs Obligation
Affects: Engineer B FOIA-Requesting Competing Engineer Engineer A Public RFQ Submitting Engineer State Agency Public Procurement Authority Engineer B Present Case Public Procurement Competitor
Moral Intensity (Jones 1991):
Magnitude: high Probability: high immediate direct concentrated

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.

Obligation Vs Constraint
Affects: Engineer B FOIA-Requesting Competing Engineer Engineer A Public RFQ Submitting Engineer Public Procurement Qualifications Reviewer Engineer State Agency Public Procurement Authority
Moral Intensity (Jones 1991):
Magnitude: high Probability: high immediate direct concentrated

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.

Obligation Vs Obligation
Affects: Franchiser Client BER 93-3 Engineer B BER 93-3 Replacement Design Engineer Confidentiality-Directed Replacement Design Engineer State Agency Public Procurement Authority Engineer A BER 93-3 Incumbent Design Engineer
Moral Intensity (Jones 1991):
Magnitude: high Probability: medium near-term direct diffuse
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
Key Takeaways
  • 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.