Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Selection of Firm—FOIA Request
Step 4 of 5

149

Entities

3

Provisions

1

Precedents

14

Questions

15

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
Engineer B and the procurement system remain trapped between two co-existing but incompatible normative demands: the legal/ethical permissibility of FOIA access versus the fairness concern of competitive informational asymmetry. The Board's resolution (recommend later timing) does not eliminate the underlying conflict—it only relocates it to a procedural formality, leaving the substantive competing-obligations problem intact for future similar cases.
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

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

II.2.a board + analysis 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 10)
Action
Qualifications Submission
Engineers must only submit qualifications for work they are competent to perform
State
Engineer B Procurement Conduct Compliance
Requires Engineer B to be qualified for the assignment sought through the procurement process
Principle
Free and Open Competition in Procurement
Engineers must be qualified for assignments which supports fair competition based on merit.
Action (2)
  • Qualifications Submission
    Engineers must only submit qualifications for work they are competent to perform
  • Competing Qualifications Submission
    Competing firms must only claim qualifications in fields where they are truly competent
State (1)
  • Engineer B Procurement Conduct Compliance
    Requires Engineer B to be qualified for the assignment sought through the procurement process
Principle (1)
  • Free and Open Competition in Procurement
    Engineers must be qualified for assignments which supports fair competition based on merit.
Role (2)
  • Engineer A Engineer
    Must only submit qualifications for work he is competent to perform
  • Engineer B Engineer
    Must only submit qualifications for work he is competent to perform
Event (1)
  • RFQ Issuance
    This event involves determining qualifications and technical fields for firm selection.
Resource (1)
  • Engineer A Qualifications Submission
    This provision requires that qualifications submitted match the specific technical fields of the project
Capability (2)
  • Engineer A Qualifications Submission
    Engineer A submitted qualifications implying he was qualified by education and experience for the project.
  • Engineer B Qualifications Submission
    Engineer B submitted qualifications implying he was qualified by education and experience for the project.
II.4 board + analysis Engineers shall act for each employer or client as faithful agents or trustees.
How this applies in the case (showing 3 of 16)
Obligation
Engineer B Procurement Compliance Duty
Acting as a faithful agent requires following procurement laws when requesting competitor information
Action
Information Release Decision
Deciding what information to release requires acting as a faithful agent to the client
State
Engineer B Procurement Conduct Compliance
Requires Engineer B to act faithfully within procurement rules rather than seeking improper advantage
Obligation (1)
  • Engineer B Procurement Compliance Duty
    Acting as a faithful agent requires following procurement laws when requesting competitor information
Action (2)
  • Information Release Decision
    Deciding what information to release requires acting as a faithful agent to the client
  • Code Provisions Removal
    Removing code provisions from public documents may violate the duty to act as a faithful trustee of information
State (3)
  • Engineer B Procurement Conduct Compliance
    Requires Engineer B to act faithfully within procurement rules rather than seeking improper advantage
  • Confidential Information Public Submission Risk
    Faithful agency obligations relate to protecting client confidential information from competitor exposure
  • Competitor Holds Rival Qualifications
    Acting as faithful agent limits using FOIA to gain insight into a competitor's submission
Constraint (1)
  • Board Procurement Rules Review Limit
    Faithful agency duties are exercised within the bounds of public procurement laws that the Board will not second guess
Principle (2)
  • Loyalty as Faithful Agent
    This provision directly requires engineers to act as faithful agents or trustees for their employer or client.
  • Public Interest in Procurement Openness
    Acting as a faithful agent supports the public interest in a procurement system that selects the most qualified engineer.
Role (1)
  • Engineer B Engineer
    Must act as a faithful agent when competing for a client contract rather than exploiting a competitors information
Event (1)
  • Regulatory Conflict Determination
    Acting as a faithful agent requires resolving conflicts of interest in regulatory matters.
Resource (2)
  • BER Case No. 93-3
    This prior case directly addresses the faithful agent and trustee duty invoked by this provision
  • NSPE Code of Ethics
    This provision is part of the Code section establishing the faithful agent and trustee duty
Capability (3)
  • Engineer B FOIA Request
    Using a FOIA request to obtain a competitor's qualifications raises questions about acting as a faithful agent in the competitive process.
  • Board Precedent Reasoning
    The Board applies the faithful agent and trustee standard from prior precedent to evaluate Engineer B's conduct.
  • Engineer B Regulatory Compliance Assessment
    The Board found Engineer B appears to have acted as a faithful agent by following public procurement rules.
II.5 board + analysis Engineers shall avoid deceptive acts.
How this applies in the case (showing 3 of 17)
Obligation
Engineer B Procurement Compliance Duty
Avoiding deceptive acts requires lawful and transparent use of FOIA requests in procurement
Action
Code Provisions Removal
Removing code provisions before releasing documents may constitute a deceptive act
State
Board Concern Over Request Timing
Timing of the FOIA request raises concern about deceptive intent to gain competitive advantage
Obligation (1)
  • Engineer B Procurement Compliance Duty
    Avoiding deceptive acts requires lawful and transparent use of FOIA requests in procurement
Action (4)
  • Code Provisions Removal
    Removing code provisions before releasing documents may constitute a deceptive act
  • Information Release Decision
    Deciding to withhold or alter information in response to a FOIA request could be deceptive
  • Qualifications Submission
    Submitting qualifications must avoid deceptive claims about expertise
  • Competing Qualifications Submission
    Competing submissions must not use deceptive practices to gain advantage
State (3)
  • Board Concern Over Request Timing
    Timing of the FOIA request raises concern about deceptive intent to gain competitive advantage
  • Pre-Interview Selection Window
    Seeking competitor qualifications before interviews could be a deceptive act in the selection process
  • FOIA Access To Submitted Qualifications
    Using public records access to gain unfair insight into a competitor may constitute a deceptive practice
Constraint (1)
  • Engineer A Confidential Submission Caution
    Avoiding disclosure of confidential information relates to avoiding deceptive or improper acts in submissions
Principle (2)
  • Public Interest in Procurement Openness
    Avoiding deceptive acts supports transparency and openness in the public procurement process.
  • Free and Open Competition in Procurement
    Deceptive acts would undermine fair and open competition among engineering firms.
Role (2)
  • Engineer B Competitor
    Using a FOIA request to obtain a competitors qualifications for competitive advantage constitutes a deceptive or unfair practice
  • Engineer B Engineer
    Basing his own submission on a competitors obtained qualifications could be a deceptive act in professional competition
Event (1)
  • Public Records Disclosure
    Avoiding deceptive acts relates directly to honest disclosure under public records requests.
Resource (2)
  • Engineer A Qualifications Submission
    This provision requires that the qualifications submission not contain deceptive statements
  • NSPE Code of Ethics
    This provision is part of the Code establishing the requirement to avoid deceptive acts
Capability (1)
  • Engineer B FOIA Request
    Obtaining a competitor's qualifications via FOIA before the interview process could be seen as a deceptive competitive tactic.
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 has a general duty of loyalty and fair dealing to a client, acting as a 'faithful agent and trustee,' and must not disclose information or act in a way that neglects the client's interests for personal advantage.

Citation Context:

The Board cited this earlier case to illustrate the principle that an engineer owes a duty of loyalty and fair dealing as a 'faithful agent and trustee' to a client, even though the specific facts differed from the current FOIA scenario.

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 62% Facts Similarity 55% Discussion Similarity 65% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 56%
Same outcome ethical View Synthesis
Component Similarity 57% Facts Similarity 41% Discussion Similarity 58% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 60%
Same outcome ethical View Synthesis
Component Similarity 56% Facts Similarity 34% Discussion Similarity 59% Outcome Alignment 100% Tag Overlap 22% Principle Overlap 66%
Same outcome ethical View Synthesis
Component Similarity 54% Facts Similarity 40% Discussion Similarity 69% Outcome Alignment 100% Tag Overlap 40% Principle Overlap 50%
Same outcome ethical View Synthesis
Component Similarity 60% Facts Similarity 55% Discussion Similarity 80% Outcome Alignment 100% Principle Overlap 59%
Same outcome ethical View Synthesis
Component Similarity 58% Facts Similarity 48% Discussion Similarity 70% Outcome Alignment 100% Principle Overlap 65%
Same outcome ethical View Synthesis
Component Similarity 55% Facts Similarity 43% Discussion Similarity 65% Outcome Alignment 100% Tag Overlap 17% Principle Overlap 61%
Same outcome ethical View Synthesis
Component Similarity 53% Facts Similarity 25% Discussion Similarity 54% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 59%
Same outcome ethical View Synthesis
Component Similarity 51% Facts Similarity 36% Discussion Similarity 64% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 51%
Same outcome ethical View Synthesis
Component Similarity 54% Facts Similarity 41% Discussion Similarity 67% Outcome Alignment 100% Principle Overlap 59%
Same outcome ethical 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. However, in order to avoid any appearance of impropriety, Engineer B should have made the FOIA request subsequent to Engineer B’s firm’s submitting its RFQ.
Resolved by: The board let the Public Interest in Procurement Openness and legal permissibility of the FOIA request prevail over the appearance concern, but tempered that outcome by recommending a sequencing change to preserve the appearance of fair competition. (confidence 0.85)
II.4. II.5. 3 principles 3 facts Conditions Narrative
Implicit (2)

Even though the FOIA request was legally permissible, did Engineer B's access to Engineer A's qualifications before submitting his own create an unfair informational advantage that undermines the integrity of the competitive process?

AnalyticalQ101: Although Engineer B's FOIA request was legally permissible and the qualifications data was public, obtaining Engineer A's submission before finalizing his own creates an informational asymmetry that, while not illegal, is ethically significant. The Board's recommendation that Engineer B should have waited until after submitting his own RFQ reflects an implicit recognition that pre-submission access—even to public information—can compromise the appearance of a level playing field, which is why the Board flagged it despite finding no violation.
Resolved by: The board implicitly balanced the openness principle, which supports broad FOIA access, against free and open competition, resolving the tension by permitting the request as legal while flagging its pre-submission timing as ethically significant. (confidence 0.80)
2 principles 3 facts Conditions Narrative
AnalyticalThe Board's remedy—requiring Engineer B to wait until after submitting his own qualifications before filing the FOIA request—addresses only the appearance of impropriety, not the underlying informational asymmetry problem. Even if Engineer B had waited, the same public records request would still have given him insight into Engineer A's submitted qualifications before the state's final selection or interview process, potentially informing how Engineer B could position his firm relative to Engineer A during interviews. The timing fix cures the sequencing optics but does not eliminate the competitive information advantage inherent in any pre-selection FOIA access to a rival's submission.
Resolved by: This critique treats the competitive fairness principle as under-weighted relative to the openness principle, since the board's timing fix satisfies appearance concerns without resolving the substantive informational asymmetry. (confidence 0.75)
2 principles 3 facts Conditions Narrative

Does the timing of Engineer B's FOIA request—before submitting his own qualifications—suggest an intent to gain competitive insight rather than merely exercise a public records right, and how should intent factor into the ethical evaluation separate from legality?

AnalyticalThe Board's finding treats the appearance of impropriety as curable purely through resequencing, without examining Engineer B's underlying intent in timing the request before submission. If Engineer B's purpose was in fact to review Engineer A's qualifications to strategically shape his own firm's submission, then merely reordering the same actions (filing FOIA after submission) would eliminate the appearance without altering the substantive intent-based concern. This suggests the Board's compliance finding rests on a narrower, procedural notion of propriety rather than a deeper evaluation of competitive fairness or motive under the faithful agent principle.
Resolved by: This critique weighs a deeper motive-based fairness standard against the board's narrower procedural propriety standard, suggesting the latter under-addresses faithful-agent and competitive-fairness concerns if intent was strategic. (confidence 0.70)
II.4. II.5. 2 principles 3 facts Conditions Narrative
AnalyticalQ104: The timing of Engineer B's FOIA request—made before his own firm's submission—does suggest a strategic motive to gain insight into a competitor's qualifications rather than a neutral exercise of a public records right. However, because NSPE's ethical evaluation under this case turns on the appearance of impropriety rather than provable intent, the Board's concern is best understood as a prophylactic standard: engineers should structure their conduct to avoid situations where intent could reasonably be questioned, regardless of what their actual motive was.
Resolved by: The Board balanced the difficulty of proving subjective intent against the profession's interest in avoiding even the appearance of strategic advantage, favoring a prophylactic standard over an intent-based inquiry. (confidence 0.80)
2 principles 3 facts Conditions Narrative
Principle tension (3)

How should the Public Interest in Procurement Openness, which supports broad FOIA access to submitted qualifications, be balanced against Free and Open Competition in Procurement, which could be undermined if one competitor gains insight into another's submission before finalizing their own?

AnalyticalThe Board resolved the tension between Public Interest in Procurement Openness and Free and Open Competition in Procurement by giving formal priority to openness—affirming that the FOIA request itself was lawful and ethical—while addressing the competitive fairness concern only through a softer, non-binding appearance-of-impropriety standard rather than a substantive rule against pre-submission access. This shows that when a legally sanctioned transparency mechanism (FOIA) intersects with competitive fairness concerns, the Board defers to the legal/procedural principle as controlling, relegating fairness concerns to a matter of prudential timing rather than a hard ethical constraint.
Resolved by: The Board gave formal priority to the legally sanctioned transparency principle over the competitive fairness principle, reducing the latter to a soft, non-binding appearance standard rather than a hard constraint. (confidence 0.80)
2 principles 3 facts Conditions Narrative

Does Engineer B's exercise of Free and Open Competition in Procurement through a pre-submission FOIA request conflict with the spirit of Loyalty as Faithful Agent, which underlies fair dealing between competing engineering firms in a shared procurement process?

AnalyticalLoyalty as Faithful Agent, though referenced via precedent (BER Case No. 93-3), does not squarely govern this case because Engineer B owed no fiduciary or agency duty to Engineer A; the two were merely competitors in a shared public procurement. The Board's implicit reliance on faithful-agency reasoning therefore functions more as an analogical borrowing to support a general norm of professional courtesy between competitors, rather than as a directly applicable principle—illustrating that agency-based loyalty concepts can be extended by analogy to shape appearance-of-propriety judgments even outside true client relationships.
Resolved by: The Board weighed the faithful-agent principle as only weakly applicable, using it analogically to support a general norm of professional courtesy rather than treating it as a controlling obligation between competitors. (confidence 0.75)
II.4. 2 principles 3 facts Conditions Narrative

How should the Board's concern over the timing of Engineer B's FOIA request be reconciled with the Public Interest in Procurement Openness principle, which does not itself impose any timing restriction on when public records may be requested?

AnalyticalThe case demonstrates a broader prioritization pattern: where an act is independently legal and procedurally authorized (FOIA request under RFQ rules), the Board treats legality as establishing the ethical floor, and reserves ethical critique for matters of timing, optics, and professional appearance rather than reclassifying the act itself as improper. This suggests that in procurement contexts, Free and Open Competition and Public Interest in Procurement Openness jointly outrank softer relational principles like collegial fairness or the appearance standard, which operate only as secondary, aspirational refinements once legality is settled.
Resolved by: The Board established legality as the ethical floor and subordinated softer relational principles like collegial fairness and appearance of impropriety to a secondary, aspirational role once legality was confirmed. (confidence 0.80)
2 principles 3 facts Conditions Narrative
Theoretical (3)

From a deontological perspective, did Engineer B fulfill the duty to avoid even the appearance of impropriety by submitting the FOIA request before his own firm's qualifications were submitted?

AnalyticalQ301: From a deontological standpoint grounded in the duty to avoid the appearance of impropriety, Engineer B did not fully satisfy this duty, since filing the FOIA request prior to submitting his own qualifications created a situation in which his conduct—regardless of legality—could reasonably be perceived as seeking unfair advantage. A duty-based analysis would hold that professional obligations under the Code extend beyond mere legal compliance to encompass how one's actions appear to third parties and to the profession's integrity.
Resolved by: The Board weighed legal permissibility against the deontological duty of appearance, concluding that the duty-based obligation to protect professional integrity outweighs mere legal compliance when the two diverge. (confidence 0.78)
II.4. 2 principles 3 facts Conditions Narrative

Did the outcome of Engineer B obtaining Engineer A's qualifications data justify the means used, given that the state's procurement process was ultimately preserved as open and lawful?

Did Engineer B act with professional integrity when he sought to obtain a rival's confidential-seeming qualifications data through legal channels immediately before competing for the same project?

AnalyticalQ303: Engineer B's use of a legal channel to obtain a rival's qualifications data does not itself demonstrate a lack of integrity, since the FOIA process is a legitimate and publicly sanctioned mechanism. However, professional integrity requires more than legal compliance; it requires conduct that reflects fair dealing among competitors. The ethically preferable path—submitting the FOIA request after Engineer B's own qualifications were filed—would have preserved both legality and the appearance of integrity simultaneously.
Resolved by: The Board distinguished legal compliance from professional integrity, holding that satisfying the former does not automatically satisfy the latter, and integrity required a standard of fair dealing beyond what FOIA law itself demanded. (confidence 0.75)
II.4. II.5. 3 principles 3 facts Conditions Narrative
Counterfactual (3)

If the state's FOIA law had exempted procurement qualifications submissions from public disclosure, would the Board still conclude that Engineer B's request was ethical under the state's RFQ procedures?

AnalyticalQ401: Had the state's FOIA law exempted procurement qualifications submissions from public disclosure, the state agency would not have been permitted to release Engineer A's materials, and Engineer B's request would have been legally barred rather than merely ethically questionable. In that scenario, the Board's analysis would likely shift from an appearance-of-impropriety concern to a straightforward finding that Engineer B's request was improper due to violating applicable procurement confidentiality rules, since the ethical evaluation is contingent on the underlying legal permissibility established by the state's FOIA framework.
Resolved by: The Board indicated that where legal permissibility is foreclosed by statute, the ethical inquiry collapses into a straightforward legal violation rather than a nuanced appearance-of-impropriety balancing. (confidence 0.72)
2 principles 3 facts Conditions Narrative

If Engineer A had not yet submitted his firm's qualifications to the state agency at the time Engineer B filed the FOIA request, would there have been any qualifications data for Engineer B to obtain, and would the Board's appearance-of-impropriety concern even arise?

AnalyticalQ402: If Engineer A had not yet submitted qualifications at the time of Engineer B's FOIA request, there would have been no responsive records for the state to disclose, and thus no informational advantage for Engineer B to obtain. This counterfactual clarifies that the Board's appearance-of-impropriety concern is specifically tied to the temporal sequence in which a competitor's submitted materials already exist and are retrievable before the requesting engineer's own submission is finalized—removing that sequence removes the ethical concern entirely.
Resolved by: The Board treated the sequencing fact as dispositive, so no competing obligation weighing was needed once the counterfactual removed the existence of retrievable records. (confidence 0.85)
2 principles 3 facts Conditions Narrative

If Engineer B had not been a competing firm for the same public project but an unrelated third party, would the Board's finding of an appearance of impropriety in the FOIA request still apply?

AnalyticalQ403: If Engineer B had been an unrelated third party rather than a competing firm for the same project, the Board's appearance-of-impropriety concern would not arise, because the ethical issue stems specifically from the competitive relationship between Engineer B and Engineer A within the same procurement process. A non-competitor's FOIA request for the same information would raise no comparable fairness concern, since there would be no risk of using the disclosed qualifications to gain a competitive edge in a shared selection process.
Resolved by: The Board weighed the fairness concern only against the specific competitive posture of the requester, finding no countervailing obligation implicated when that competitive relationship is absent. (confidence 0.85)
2 principles 3 facts Conditions Narrative
Analytical questions (2)

Questions the analysis generates beyond the board’s explicit questions: implicit issues, principle tensions, theoretical framings, and counterfactuals. A question with an identified source board question appears nested under that question above.

Implicit (2)

Should the state agency have adopted procurement rules delaying disclosure of RFQ submissions until after the selection process to prevent competitors from tailoring their submissions based on rivals' materials?

AnalyticalThe Board's conclusion implicitly places the ethical burden on the individual engineer's discretion (self-imposed timing restraint) rather than on the state agency's procurement design. A more robust systemic solution would be for the state agency to structure its RFQ and FOIA release procedures so that submitted qualifications are not disclosable until after the full selection process concludes, removing the opportunity for any competitor—regardless of intent—to gain sequential informational advantage. Relying on individual engineers to voluntarily delay legally available requests is a weaker safeguard than a procedural rule preventing the disclosure timing issue from arising at all.
Resolved by: This conclusion favors a systemic procedural safeguard over reliance on individual ethical restraint, arguing that agency-level disclosure timing rules would more reliably protect free and open competition than voluntary compliance. (confidence 0.70)
2 principles 3 facts Conditions Narrative

Did Engineer A have any reasonable expectation that qualifications submitted for a public procurement would remain shielded from competitors, and what precautions should engineers take when submitting potentially sensitive information into a public process?

AnalyticalQ103: Engineer A submitted qualifications into a process governed by public procurement law, and once submitted, such materials are generally subject to the state's FOIA regime absent a specific exemption. Engineers participating in public RFQ processes should therefore assume that non-proprietary qualifications information may become accessible to competitors and should avoid including trade-secret or genuinely confidential material unless the agency's procedures expressly protect it. The Board's implicit stance is that the burden falls on the submitting engineer and the agency's rules, not on the requesting engineer, to safeguard sensitive content.
Resolved by: The Board resolved the tension between an engineer's interest in confidentiality and the public's interest in procurement openness by defaulting to openness absent an express exemption, placing the protective burden on the submitter and the agency's rules rather than on the requester. (confidence 0.75)
2 principles 3 facts Conditions Narrative
Decisions & Arguments (4)
View Extraction

Should Engineer B file the FOIA request for Engineer A's qualifications before or after submitting his own firm's RFQ?

Options considered:
O1 Engineer B submits the FOIA request for Engineer A's qualifications prior to filing his own firm's RFQ, obtaining a competitor's materials before finalizing his own submission.
O2 Engineer B waits to submit the FOIA request until after his own firm's RFQ has been filed, eliminating the sequencing that suggests strategic advantage. Board's choice
Argument structure (Toulmin):
Grounds

Engineer B filed a FOIA request for Engineer A's qualifications before his own firm submitted its RFQ, and the request was legally permitted under the state's public records law.

Rebuttal

Would not apply if the timing had no plausible bearing on how Engineer B could tailor his submission, such as if the FOIA response could not have been received before his own submission deadline.

Avoid Appearance of Impropriety while Exercising Free and Open Competition

Should the state agency adopt procurement rules delaying disclosure of RFQ submissions until after the selection process concludes?

Options considered:
O1 Continue releasing submitted qualifications upon request during the active selection process, as occurred in this case.
O2 Leave the timing safeguard to individual engineers' voluntary discretion about when to file records requests, without changing agency procedure.
O3 Restructure RFQ and FOIA release procedures so submitted qualifications are not disclosable until after the full selection process concludes, removing the sequential informational advantage for any requester. Board's choice
Argument structure (Toulmin):
Grounds

The agency's immediate release of Engineer A's qualifications upon Engineer B's request enabled Engineer B to review a competitor's submission before finalizing his own, and this same asymmetry would recur under any pre-selection FOIA access regardless of an individual requester's intent.

Rebuttal

Would not apply if delaying disclosure itself conflicted with statutory FOIA timing requirements or undermined the public interest in contemporaneous procurement transparency.

Balance Public Interest in Procurement Transparency against Free and Open Competition

Should Engineer A submit qualifications without redaction, or take precautions to protect sensitive or proprietary information before submission?

Options considered:
O1 Engineer A submits complete qualifications materials into the RFQ process without identifying or shielding any sensitive or proprietary content.
O2 Engineer A requests that the agency treat specific proprietary or trade-secret portions of the submission as exempt from FOIA disclosure, where agency procedures allow such protection.
O3 Engineer A proactively avoids including trade-secret or genuinely confidential material in the RFQ submission, assuming non-proprietary content may become accessible to competitors absent an express exemption. Board's choice
Argument structure (Toulmin):
Grounds

Engineer A's qualifications were submitted into a process governed by public procurement law and were subsequently released to Engineer B under the state's FOIA regime without objection or exemption claim.

Rebuttal

Would not apply if the agency's rules guaranteed confidentiality of RFQ submissions during the active selection period, removing any need for individual precaution.

Reasonable Expectation of Confidentiality in Public Procurement Submissions

Should the state agency release Engineer A's qualifications in response to Engineer B's FOIA request during the active selection process?

Options considered:
O1 The agency discloses Engineer A's qualifications to Engineer B promptly upon request, in compliance with applicable FOIA law and its existing RFQ procedures. Board's choice
O2 The agency declines to release Engineer A's qualifications during the active selection process, citing competitive fairness concerns absent an express statutory exemption.
O3 The agency postpones disclosure of Engineer A's qualifications until the selection process concludes, without a formal rule authorizing such delay.
Argument structure (Toulmin):
Grounds

The agency released Engineer A's submitted qualifications upon Engineer B's request under the state's public records law, and no exemption for procurement qualifications existed at the time.

Rebuttal

Would not apply if the FOIA statute or agency procurement rules contained an exemption protecting RFQ submissions from disclosure prior to selection, in which case release would have been legally improper.

Compliance with FOIA Laws and Regulations
Event Timeline (8)
8 sequenced 5 actions 3 events
Case timeline
Government regulators deemed certain NSPE Code provisions, such as prohibitions on advertising and competitive bidding, to conflict with free and open competition, a determination external to the case agents that preceded NSPE's removal of those provisions.
NSPE removed provisions from its Code of Ethics that prohibited advertising and competitive bidding, after government regulators deemed them to conflict with free and open competition.
Causal-normative reasoning(confidence 0.60)
A1's removal of code provisions, guided by Free and Open Competition but stemming from a regulatory conflict determination, matters because it reshapes the very procurement rules under which subsequent actions like Qualifications Submission and Competing Qualifications Submission occur, even though it itself fulfills or violates no specific obligation.
A state agency issues a public request for qualifications for an engineering project, opening the public procurement process to which both Engineer A and Engineer B respond.
State changes (1)
  • began: Public Procurement Procedures In Force
Engineer A submits his firm's engineering qualifications to the state agency in response to the public RFQ using the state's public procurement procedures.
Fulfills (1)
  • Compliance with Public Procurement Procedures
Causal-normative reasoning(confidence 0.75)
A2 fulfills Compliance with Public Procurement Procedures and is guided by Free and Open Competition, which matters because this initial submission sets in motion the causal chain leading to Engineer B's FOIA request and eventual competing submission, so its procedural legitimacy anchors the fairness of everything that follows.
State changes (1)
  • began: Confidential Information Public Submission Risk
Engineer B, a competitor intending to respond to the same RFQ, files a state FOIA request to obtain a copy of the qualifications information Engineer A submitted, prior to the interview process. The Board flags the timing of this request as a concern.
Causal-normative reasoning(confidence 0.75)
A3, guided by both Free and Open Competition and Public Interest in Procurement Transparency, matters because it is the trigger that causally produces the Public Records Disclosure, meaning Engineer B's transparency-driven request is what makes possible the later competitive response and any downstream fairness concerns.
State changes (1)
  • began: Board Concern Over Request Timing
The state agency releases Engineer A's submitted qualifications information to Engineer B in response to the FOIA request.
Fulfills (1)
  • Compliance with FOIA Laws and Regulations
Causal-normative reasoning(confidence 0.75)
A4 fulfills Compliance with FOIA Laws and Regulations and is guided by Public Interest in Procurement Transparency, which matters because the agency's decision to release information directly causes the disclosure that enables Engineer B to submit competing qualifications, tying legal compliance to a real competitive outcome.
State changes (1)
  • began: FOIA Access To Submitted Qualifications
The state provides Engineer A's submitted qualifications information to Engineer B pursuant to the FOIA request, an outcome flowing from the public records system operating under applicable disclosure laws and regulations.
State changes (1)
  • began: FOIA Access To Submitted Qualifications
After receiving and reviewing Engineer A's materials, Engineer B submits his own firm's engineering qualifications to the state agency for the same public project.
Fulfills (1)
  • Compliance with Public Procurement Procedures
Causal-normative reasoning(confidence 0.70)
A5 fulfills Compliance with Public Procurement Procedures and is guided by Free and Open Competition, which matters because it is the culmination of the disclosed information being used to submit a competing bid, so its procedural validity determines whether the transparency-driven disclosure chain resulted in fair rather than exploitative competition.
State changes (1)
  • began: Competitor Holds Rival Qualifications
Narrative (3 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 State Agency, responsible for administering a public procurement process for a state infrastructure project. You issued a request for qualifications (RFQ) inviting engineering firms to submit their credentials for consideration, and Engineer A's firm submitted its qualifications package by the stated deadline. Your jurisdiction's Freedom of Information Act allows members of the public, including competing firms, to request copies of documents submitted to your office, and this access applies during the period before you complete your interviews and selection. Engineer B, whose firm also intends to respond to the same RFQ, has filed a FOIA request seeking the qualifications materials that Engineer A submitted. Your procurement procedures do not currently specify whether such requests must be honored while the selection process is still underway or only after a firm has been chosen. Several decisions lie ahead regarding how your agency handles this request, what procurement safeguards may need to be considered, and how the involved engineers approach the timing and content of their submissions.

Main characters (3)

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

Engineer A Roles in this case: Engineer

Guided by: Loyalty as Faithful Agent, Public Interest in Procurement Openness, Free and Open Competition in Procurement

The state agency's legal duty to comply with public records requests under FOIA can conflict directly with Engineer A's caution to keep proprietary or competitively sensitive submission content confidential. A FOIA request from Engineer B or another party could force disclosure of information Engineer A intended to protect, creating a direct clash between transparency obligations and confidentiality interests.

Engineer B's duty to follow the procurement agency's rules, which may require disclosure or use of competitor submission details during the bidding or review process, sits in tension with Engineer A's caution to keep its own submission materials confidential from competitors. If procurement compliance requires sharing evaluation materials or responding to inquiries that touch on Engineer A's submission, Engineer B's compliance duty could inadvertently compromise the confidentiality Engineer A sought to protect.

Engineer B Roles in this case: EngineerCompetitor

The state agency's legal duty to comply with public records requests under FOIA can conflict directly with Engineer A's caution to keep proprietary or competitively sensitive submission content confidential. A FOIA request from Engineer B or another party could force disclosure of information Engineer A intended to protect, creating a direct clash between transparency obligations and confidentiality interests.

Attaches to role: Competitor

Engineer B's duty to follow the procurement agency's rules, which may require disclosure or use of competitor submission details during the bidding or review process, sits in tension with Engineer A's caution to keep its own submission materials confidential from competitors. If procurement compliance requires sharing evaluation materials or responding to inquiries that touch on Engineer A's submission, Engineer B's compliance duty could inadvertently compromise the confidentiality Engineer A sought to protect.

Attaches to role: Engineer
State Agency Roles in this case: Procurement Agency

The state agency's legal duty to comply with public records requests under FOIA can conflict directly with Engineer A's caution to keep proprietary or competitively sensitive submission content confidential. A FOIA request from Engineer B or another party could force disclosure of information Engineer A intended to protect, creating a direct clash between transparency obligations and confidentiality interests.

Engineer B's duty to follow the procurement agency's rules, which may require disclosure or use of competitor submission details during the bidding or review process, sits in tension with Engineer A's caution to keep its own submission materials confidential from competitors. If procurement compliance requires sharing evaluation materials or responding to inquiries that touch on Engineer A's submission, Engineer B's compliance duty could inadvertently compromise the confidentiality Engineer A sought to protect.

The NSPE Board of Ethical Review's limited mandate to review only ethical conduct, not procurement law or FOIA compliance itself, constrains its ability to fully resolve the underlying tension between the state agency's disclosure obligations and the engineers' competing interests. This creates a gap where the Board can comment on professional conduct but cannot adjudicate or remedy the legal compliance question driving the ethical dispute.

The Board’s deliberation

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

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. However, in order to avoid any appearance of impropriety, Engineer B should have made the FOIA request subsequent to Engineer B’s firm’s submitting its RFQ.
Opening States (8)
Public Procurement Procedures In Force Pre-Interview Selection Window FOIA Access To Submitted Qualifications Engineer B Procurement Conduct Compliance Board Authority Limit On Procurement Rules Board Concern Over Request Timing Competitor Holds Rival Qualifications Confidential Information Public Submission Risk
Summary
  • Using a legal mechanism like FOIA to obtain a competitor's proposal information is ethically permissible when it operates within the transparency rules the procuring agency itself established.
  • Engineers who submit proposals to public agencies should understand that public records laws may expose their submissions to competitor scrutiny regardless of confidentiality preferences.
  • The Board can affirm that an action was ethical while still recommending additional steps to preserve the appearance of propriety, showing that legal permissibility and full ethical comfort are not identical.

© Licensed under the GNU GPL v3