Step 4: Full View

Entities, provisions, decisions, and narrative

Professional Selection—Receipt of Submission Beyond the Published Deadline
Step 4 of 5

251

Entities

3

Provisions

1

Precedents

17

Questions

23

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
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 2 55 entities

Engineers shall issue public statements only in an objective and truthful manner.

Applies To (21)
Role
Engineer A QBS Review Team Point of Contact Engineer A must issue objective and truthful public statements when administering the QBS process and communicating decisions about submittal acceptance.
Role
Engineer A Prior RFQ Submitter Engineer A must ensure any public statements related to the qualifications submission are objective and truthful.
Principle
Transparency Principle Invoked for Firm B Submittal Disposition Issuing public statements objectively and truthfully aligns with the requirement that Engineer A transparently document and communicate the disposition of Firm B's submittal.
Principle
Procurement Integrity in Public Engineering. QBS Process Administration Objective and truthful public statements support the lawful and fair administration of the public QBS process.
Principle
Public Welfare Paramount. QBS Process Integrity Serves Public Interest Truthful and objective public communication upholds the integrity of the QBS process that serves the public interest.
Obligation
Engineer A Public Procurement Qualifications Confidentiality Self-Protection State RFQ The provision requiring objective and truthful public statements relates to Engineer A's obligation to ensure qualifications submissions contain only appropriate non-confidential information presented accurately.
Obligation
Engineer A Procurement Integrity Public Interest QBS Administration Issuing objective and truthful public statements connects to administering the QBS process transparently and equitably in the public interest.
State
Conflict of Interest - Engineer A QBS Evaluator with Known Firm Engineer A must issue objective and truthful statements in the evaluator role despite prior relationship with Firm B.
State
Firm B Late Submission Procurement Integrity Tension Engineer A's public statements or communications about the late submission decision must be objective and truthful.
State
Prior Favorable Relationship - Engineer A and Firm B Engineer A's prior favorable relationship risks compromising the objectivity required when making public statements about the procurement outcome.
Resource
NSPE Code of Ethics The provision on issuing objective and truthful public statements is part of the NSPE Code of Ethics governing Engineer A's conduct.
Resource
NSPE_Code_of_Ethics The provision on issuing objective and truthful public statements is directly contained within this normative ethical framework document.
Resource
City X RFQ and Pre-Submittal Meeting Documentation Engineer A's public statements about the procurement process and deadline requirements must be objective and truthful as communicated in the RFQ documentation.
Action
Engineer A Decides on Late Submittal Engineer A must issue any public or professional statement about accepting or rejecting the late submission in an objective and truthful manner.
Event
Engineer A Discovers Submittal Engineer A must issue objective and truthful public statements about the discovery of the late submittal and how it was handled.
Event
QBS Evaluation Period Affected Any public statements made regarding the impact on the QBS evaluation process must be objective and truthful.
Capability
Engineer A Procurement Fairness Appearance Management II.3 requires objective and truthful public statements, directly relevant to Engineer A managing the appearance of impartiality when personally receiving Firm B's envelope.
Capability
Engineer A Public Procurement Integrity Public Interest Articulation City X II.3 requires objectivity in public statements, which connects to Engineer A's need to articulate the public interest rationale for strict QBS enforcement truthfully.
Capability
Engineer B Honorable Procurement Conduct Self-Regulation II.3 requires objective and truthful conduct in public matters, which applies to Engineer B's obligation to conduct himself honorably in procurement.
Constraint
Public Procurement Open Free Process Non-Deception Constraint City X QBS The provision requiring objective and truthful public statements directly constrains firms from making misleading or deceptive representations in their qualifications submissions.
Constraint
Engineer A Confidential Information Self-Exclusion Public Procurement Submission Issuing public statements only in an objective and truthful manner relates to Engineer A's obligation to avoid including confidential or proprietary information in a public procurement submission.

Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.

Applies To (34)
Role
Engineer A QBS Review Team Point of Contact Engineer A must be objective and truthful in professional reports or statements regarding the QBS review process and the handling of Firm B's late submittal.
Role
Engineer A Prior RFQ Submitter Engineer A must be objective and truthful in the qualifications submitted to the state agency, including all relevant and pertinent information.
Role
Engineer B FOIA Requesting Competitor Engineer B must be objective and truthful in any professional statements or reports derived from the qualifications obtained via FOIA request.
Principle
Transparency Principle Invoked for Firm B Submittal Disposition The requirement to include all relevant information in reports and statements directly supports transparent documentation of Firm B's late and misdirected submittal in the procurement record.
Principle
Procurement Integrity Invoked by Engineer A QBS Administration Objective and complete reporting in professional statements supports Engineer A's obligation to administer the QBS process lawfully and fairly.
Principle
FOIA Procurement Timing Integrity. Engineer B Pre-Submission Request The obligation to be truthful and include all relevant information in professional reports relates to the ethical concern about Engineer B using FOIA-obtained information in a manner that compromises procurement integrity.
Principle
Public Procurement Confidentiality Self-Protection. Engineer A Qualifications Submission The provision's emphasis on accurate and complete professional reports underscores the caution that engineers should avoid including confidential information in publicly accessible submissions.
Obligation
Engineer A Public Procurement Qualifications Confidentiality Self-Protection State RFQ The requirement for objective and truthful professional reports with all relevant information directly relates to Engineer A's obligation regarding what information to include in the firm's qualifications submission.
Obligation
Engineer A Procurement Integrity Public Interest QBS Administration Being objective and truthful in professional statements supports Engineer A's obligation to administer the QBS process with integrity and fairness.
Obligation
Engineer B FOIA Post-Submission Timing Obligation State RFQ The obligation to be truthful and avoid conflicts in professional conduct relates to Engineer B's obligation to submit the FOIA request only after submitting the firm's own qualifications to avoid improper advantage.
State
Conflict of Interest - Engineer A QBS Evaluator with Known Firm Engineer A's professional reports or evaluations must be objective and include all relevant information despite the conflict of interest.
State
Late SOQ Submission - Firm B Engineer A's professional reporting on Firm B's late submission must accurately reflect all pertinent facts including timing and location of receipt.
State
Prior Favorable Relationship - Engineer A and Firm B Engineer A must include all relevant information in evaluation reports, including disclosure of the prior favorable relationship with Firm B.
State
Engineer A Prior Favorable Relationship with Firm B Objective and complete professional reporting requires Engineer A to disclose documented prior positive experience that could bias the procurement evaluation.
State
Late SOQ Submission Outside Formal Process Engineer A's professional statements about the submission must truthfully reflect that it was received late and at the wrong location.
State
Public QBS Procurement Integrity Context Professional reports within the QBS process must be objective, truthful, and include all pertinent procedural facts to maintain procurement integrity.
Resource
NSPE Code of Ethics The requirement for objective and truthful professional reports and statements is a core provision within the NSPE Code of Ethics.
Resource
NSPE_Code_of_Ethics This sub-provision requiring truthful professional reports with relevant information is directly part of this ethical framework document.
Resource
City X RFQ and Pre-Submittal Meeting Documentation Engineer A's professional reports or statements regarding the procurement must include all relevant pertinent information as established in the RFQ documentation.
Resource
BER_Case_10-8 The precedent case involves professional reporting and statements about procurement compliance that must meet the objectivity and truthfulness standard.
Action
Engineer A Decides on Late Submittal Engineer A's professional determination regarding the late SOQ must be objective, truthful, and include all relevant information such as the timeline of events.
Event
Submittal Arrives Wrong Office Professional reports or statements about where the submittal arrived must be objective, truthful, and include all relevant information.
Event
Engineer A Discovers Submittal Engineer A's professional reporting of discovering the submittal must be truthful and include all pertinent details such as timing and circumstances.
Event
Deadline Passes Unmet Any professional statement or report regarding the missed deadline must accurately reflect all relevant facts including dates and circumstances.
Event
Pre-Submittal Meeting Held Reports or statements referencing what was communicated at the pre-submittal meeting must include all pertinent information about deadline requirements.
Capability
Engineer A QBS Submittal Deadline Enforcement II.3.a requires truthful and objective professional statements, directly applicable to Engineer A's obligation to accurately report and enforce the submittal deadline.
Capability
Engineer A Misdirected Submittal Procedural Triage II.3.a requires inclusion of all relevant information in professional reports, applicable to Engineer A accurately documenting and addressing the misdirected submittal.
Capability
Engineer A Procurement Fairness Appearance Management II.3.a requires objective and truthful professional conduct, relevant to Engineer A's need to transparently manage the appearance of his personal receipt of Firm B's envelope.
Capability
Engineer A Informal Information Sharing Restraint II.3.a requires truthful and objective handling of professional information, directly relevant to Engineer A refraining from informally processing a non-compliant submittal.
Capability
Engineer A Confidential Submission Self-Protection State RFQ II.3.a requires that professional reports and statements bear accurate dates and relevant information, applicable to Engineer A recognizing that his own submitted qualifications carry date-sensitive confidentiality concerns.
Capability
Engineer B FOIA Timing Ethics Compliance State RFQ II.3.a requires truthful and objective professional conduct, directly applicable to Engineer B's obligation to honestly assess the ethics of using a FOIA request to obtain a competitor's qualifications before submitting his own.
Constraint
Public Procurement Open Free Process Non-Deception Constraint City X QBS The requirement to be objective and truthful in professional reports and statements directly prohibits misleading or deceptive representations in QBS qualification submissions.
Constraint
Engineer A Confidential Information Self-Exclusion Public Procurement Submission The obligation to include all relevant and pertinent information truthfully constrains Engineer A from submitting confidential or proprietary information that would distort the public procurement record.
Constraint
FOIA Competitor Intelligence Ethical Use - Engineer B RFQ Response The requirement for objectivity and truthfulness in professional statements constrains how Engineer B may ethically use FOIA-obtained competitor information in preparing its own RFQ response.
Section III. Professional Obligations 1 74 entities

Engineers shall be guided in all their relations by the highest standards of honesty and integrity.

Applies To (74)
Role
Engineer A QBS Review Team Point of Contact Engineer A must act with the highest standards of honesty and integrity when deciding whether to accept or reject Firm B's late submittal.
Role
Engineer A Prior RFQ Submitter Engineer A must conduct relations with the state agency and competitors with the highest standards of honesty and integrity.
Role
Engineer B FOIA Requesting Competitor Engineer B must act with honesty and integrity in using FOIA-obtained competitor qualifications rather than gaining an unfair competitive advantage.
Principle
Procurement Integrity Invoked by Engineer A QBS Administration The highest standards of honesty and integrity directly underpin Engineer A's obligation to administer the QBS process lawfully and fairly.
Principle
QBS Submittal Deadline Integrity Invoked for Firm B Late Submittal Honesty and integrity require that Engineer A enforce the published deadline without exception or favoritism.
Principle
Misdirected Submittal Non-Acceptance Obligation Invoked by Engineer A Integrity demands that Engineer A not accept a submittal delivered to the wrong location, regardless of circumstances.
Principle
Prior Performance Non-Consideration Invoked in Firm B Compliance Determination Highest standards of integrity require that Engineer A's decision not be influenced by Firm B's prior performance record.
Principle
Good Intent Does Not Cure Procedural Impropriety Invoked for Administrative Assistant Action Integrity principles hold that well-intentioned actions cannot justify accepting a procedurally non-compliant submittal.
Principle
Fairness in Professional Competition Invoked for All 14 Pre-Submittal Firms Honesty and integrity require equal treatment of all competing firms who received identical notice of requirements.
Principle
Faithful Agent Obligation Invoked for Engineer A QBS Administration Role The highest standards of honesty and integrity are the foundation of Engineer A's faithful agent obligation to administer the QBS process properly.
Principle
Good Intent Does Not Cure Procedural Impropriety. Engineer A Sympathy for Firm B Integrity requires Engineer A to set aside sympathy and apply procurement rules consistently and honestly.
Principle
Prior Performance Non-Consideration. Engineer A Awareness of Firm B History Integrity prohibits Engineer A from allowing awareness of Firm B's past performance to justify accepting a non-compliant submittal.
Principle
FOIA-Based Competitor Intelligence Ethical Use Constraint Invoked by Engineer B The highest standards of honesty and integrity constrain Engineer B from exploiting FOIA access to gain an unfair competitive advantage.
Principle
Procurement Integrity Over Qualification Merit Balancing. Engineer A QBS Administration Integrity requires Engineer A to uphold procurement rules even when doing so may conflict with selecting the most qualified firm.
Principle
Equal Access to Bid Information Invoked in QBS Deadline Enforcement Honesty and integrity demand consistent enforcement of equally communicated requirements for all participating firms.
Principle
Formal Channel Requirement Invoked for QBS Submittal Receipt Integrity requires adherence to formally designated submission channels as publicly announced.
Principle
Public Welfare Paramount. QBS Process Integrity Serves Public Interest The highest standards of honesty and integrity are essential to maintaining a QBS process that genuinely serves the public interest.
Obligation
Engineer A QBS Deadline Strict Enforcement Firm B Rejection The highest standards of honesty and integrity require Engineer A to enforce the published deadline consistently without exception.
Obligation
Engineer A Prior Performance Non-Consideration Firm B Compliance Determination Integrity demands that Engineer A not allow prior favorable impressions of Firm B to influence an objective compliance determination.
Obligation
Engineer A Harmless Error Non-Exception Firm B Submittal Honesty and integrity require consistent rule application regardless of whether a violation appears harmless or unintentional.
Obligation
Engineer A Good Intent Non-Justification Firm B Sympathy Procurement The highest standards of integrity mean that good intentions or sympathy cannot justify deviating from established procurement rules.
Obligation
Engineer A Procurement Integrity Public Interest QBS Administration Guiding all relations by honesty and integrity directly underpins the obligation to administer the QBS process with full procurement integrity.
Obligation
City Manager Administrative Assistant Non-Facilitation Misdirected Submittal Integrity standards apply to all parties in the process, including the administrative assistant who must not facilitate a procedurally improper submittal.
Obligation
Engineer B FOIA Post-Submission Timing Obligation State RFQ The highest standards of honesty and integrity require Engineer B to sequence the FOIA request so as not to gain an unfair competitive advantage.
State
Conflict of Interest - Engineer A QBS Evaluator with Known Firm Highest standards of honesty and integrity require Engineer A to disclose and recuse from evaluating a firm with whom a prior favorable relationship exists.
State
Firm B Late Submission Procurement Integrity Tension Honesty and integrity demand Engineer A apply procurement rules consistently regardless of personal familiarity with Firm B.
State
Prior Favorable Relationship - Engineer A and Firm B Integrity requires Engineer A to acknowledge the prior relationship and avoid allowing it to influence the procurement decision.
State
Regulatory Compliance State - QBS Deadline Enforcement Integrity obligates Engineer A to uphold published QBS rules including deadline and location requirements without exception for favored firms.
State
Engineer A Prior Favorable Relationship with Firm B The highest standards of honesty require Engineer A to transparently address how the documented prior relationship affects impartiality.
State
Late SOQ Submission Outside Formal Process Integrity requires honest and consistent enforcement of submission rules regardless of which firm submitted late.
State
Public QBS Procurement Integrity Context The public QBS system depends on engineers acting with the highest honesty and integrity to maintain fair and lawful procurement processes.
State
Client Relationship Established - Engineer A and City X Engineer A's duty of honesty and integrity to City X as client requires transparent disclosure of any conflict affecting the QBS evaluation.
Resource
NSPE Code of Ethics The standard of honesty and integrity in all relations is a foundational provision within the NSPE Code of Ethics governing Engineer A.
Resource
NSPE_Code_of_Ethics This provision requiring the highest standards of honesty and integrity is directly contained within this normative ethical framework.
Resource
Public Official Conflict of Interest Standard - QBS Administration Engineer A's obligation to act with honesty and integrity directly applies to impartial administration of the QBS process free from conflicts of interest.
Resource
Public Procurement Fairness Standard - QBS Deadline Enforcement Enforcing the deadline uniformly across all 14 firms reflects the highest standards of honesty and integrity required by this provision.
Resource
SOQ_Submittal_Deadline_Compliance_Standard Honest and integrity-driven administration requires consistent enforcement of submittal deadline compliance standards without favoritism.
Action
City Establishes Submission Rules The city's published rules create an integrity standard that must be upheld honestly and consistently in the selection process.
Action
Firm B Submits SOQ Late Firm B's act of submitting after the deadline raises questions of honesty and integrity in adhering to established professional selection rules.
Action
Engineer A Decides on Late Submittal Engineer A must act with the highest honesty and integrity when deciding whether to accept or reject the late submission in accordance with published rules.
Event
Engineer A Discovers Submittal Engineer A must act with honesty and integrity when deciding how to handle the discovered late submittal.
Event
QBS Evaluation Period Affected Integrity requires honest handling of how the late submittal is treated during the QBS evaluation period.
Event
Deadline Passes Unmet Honesty and integrity require transparent acknowledgment of the missed deadline and consistent application of the rules.
Capability
Engineer A Prior Relationship Non-Favoritism Assessment III.1 requires the highest standards of honesty and integrity, directly applicable to Engineer A resisting favoritism based on Firm B's prior relationship with City X.
Capability
Engineer A QBS Submittal Deadline Enforcement III.1 requires integrity in all relations, directly applicable to Engineer A honestly enforcing the published deadline without exception.
Capability
Engineer A Misdirected Submittal Procedural Triage III.1 requires honesty and integrity, applicable to Engineer A honestly addressing the procedural irregularity of the misdirected submittal.
Capability
Engineer A Competitive Procurement Fairness Assessment III.1 requires the highest standards of integrity, directly applicable to Engineer A assessing whether accepting the late submittal would undermine procurement fairness.
Capability
Engineer A Procurement Process Integrity Preservation III.1 requires integrity in all relations, directly applicable to Engineer A preserving the integrity of the procurement process by rejecting the non-compliant submittal.
Capability
Engineer A Procurement Fairness Appearance Management III.1 requires the highest standards of honesty and integrity, applicable to Engineer A managing the appearance of fairness when personally receiving Firm B's envelope.
Capability
Engineer B FOIA Request Competitive Ethics Assessment III.1 requires honesty and integrity in all relations, directly applicable to Engineer B honestly assessing whether a FOIA request for a competitor's qualifications is ethically appropriate.
Capability
Engineer B Improper Competitive Advantage Recognition III.1 requires the highest standards of integrity, directly applicable to Engineer B recognizing that using a FOIA request for competitive advantage violates integrity standards.
Capability
Engineer B Honorable Procurement Conduct Self-Regulation III.1 requires the highest standards of honesty and integrity, directly applicable to Engineer B's obligation to self-regulate and conduct himself honorably in procurement.
Capability
Firm B QBS Submittal Location Requirement Compliance III.1 requires integrity in all relations, applicable to Firm B's obligation to honestly comply with published submittal location requirements.
Capability
City Manager Administrative Assistant Submittal Intermediary Procurement Awareness III.1 requires integrity in all relations, applicable to the administrative assistant's obligation to handle the misdirected submittal with integrity rather than facilitating a non-compliant submission.
Capability
Engineer A Procurement Law Knowledge Application III.1 requires honesty and integrity, applicable to Engineer A honestly applying QBS procurement requirements without exception or rationalization.
Capability
Engineer A Informal Information Sharing Restraint III.1 requires the highest standards of integrity, directly applicable to Engineer A refraining from informally processing a non-compliant submittal.
Capability
Engineer A Procurement Rationalization Resistance III.1 requires the highest standards of integrity, directly applicable to Engineer A resisting rationalizations that would compromise procurement integrity.
Capability
Engineer A Procurement Integrity Balance Judgment City X QBS III.1 requires integrity in all relations, directly applicable to Engineer A balancing sympathy against the integrity of the procurement process.
Capability
Engineer A Procurement Challenge Vulnerability Assessment City X QBS III.1 requires integrity, applicable to Engineer A recognizing that accepting a non-compliant submittal would expose the procurement to legal challenge and undermine integrity.
Capability
Engineer B FOIA Timing Ethics Compliance State RFQ III.1 requires the highest standards of honesty and integrity, directly applicable to Engineer B recognizing that using a FOIA request before submitting his own qualifications violates integrity standards.
Capability
Engineer A Public Procurement Integrity Public Interest Articulation City X III.1 requires integrity in all relations, directly applicable to Engineer A articulating and upholding the public interest rationale for strict procurement integrity.
Capability
Engineer A Confidential Submission Self-Protection State RFQ III.1 requires honesty and integrity, applicable to Engineer A honestly recognizing and protecting the integrity of his own confidential qualification submission.
Capability
Engineer A Procurement Rationalization Resistance Firm B Sympathy III.1 requires the highest standards of integrity, directly applicable to Engineer A resisting sympathy-based rationalizations that would compromise procurement integrity.
Capability
Engineer A Competitive Procurement Fairness Assessment City X QBS III.1 requires integrity in all relations, directly applicable to Engineer A honestly assessing whether accepting the misdirected submittal would provide an unfair competitive advantage.
Capability
City Manager Administrative Assistant Non-Facilitation Misdirected Submittal Honorable Conduct III.1 requires the highest standards of honesty and integrity, directly applicable to the administrative assistant's obligation to avoid facilitating a non-compliant submittal forwarding process.
Constraint
Procurement Honorable Conduct - Engineer A QBS Administration The highest standards of honesty and integrity directly require Engineer A to administer the QBS procurement process honorably, responsibly, and fairly.
Constraint
Appearance of Impropriety - Engineer A Prior Relationship Firm B QBS Decision Honesty and integrity standards constrain Engineer A from taking any action regarding Firm B's late submission that could create a reasonable appearance of favoritism.
Constraint
Conflict of Interest - Engineer A Evaluator Prior Favorable Relationship Firm B The highest standards of honesty and integrity require Engineer A to disclose the prior favorable relationship with Firm B and recuse from related evaluation decisions.
Constraint
Engineer A Prior Favorable Relationship Firm B Procurement Recusal Disclosure Constraint Integrity standards directly create the obligation for Engineer A to either disclose or recuse from decisions affected by the prior favorable relationship with Firm B.
Constraint
Competitive Procurement Fairness - 14 Firm Equal Treatment QBS City X The highest standards of honesty and integrity require Engineer A to treat all 14 participating firms equally under the published QBS procurement rules.
Constraint
Engineer A Prior Performance Non-Consideration Firm B Procurement Decision Integrity standards constrain Engineer A from allowing Firm B's prior satisfactory performance to improperly influence the determination of whether its late submission should be accepted.
Constraint
FOIA Competitor Intelligence Ethical Use - Engineer B RFQ Response The highest standards of honesty and integrity constrain Engineer B from using FOIA-obtained competitor intelligence in a manner that is unfair or dishonest in the procurement process.
Constraint
Engineer B FOIA Pre-Submission Timing Appearance of Impropriety State RFQ Integrity standards constrain Engineer B from submitting a FOIA request to obtain a competitor's submission before Engineer B's own firm has submitted, as this creates an appearance of impropriety.
Constraint
City Manager Administrative Assistant Non-Facilitation Misdirected Submittal Constraint The highest standards of honesty and integrity constrain the city manager's administrative assistant from facilitating acceptance of a misdirected submittal that would undermine fair procurement procedures.
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:

In public engineering procurement processes, engineers must act consistently with applicable laws and regulations; the public procurement system is designed to be free and open to advance the public interest, and engineers should avoid actions that could undermine the integrity of that process or create an appearance of impropriety.

Citation Context:

The Board cited this case to establish that a balance must be struck between selecting the most qualified engineering firm and strict adherence to public procurement rules, and to support the principle that the integrity of the public QBS/RFQ process must be maintained.

Relevant Excerpts
discussion: "The NSPE Board of Ethical Review has previously examined ethical issues relating to the selection of engineering services in the public arena. For example, in BER Case 10-8"
discussion: "Turning to the facts of the present case, it is the Board's view, consistent with BER Case 10-8, that a balance needs to be struck between the objective of selecting the most qualified engineering firm"
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 56% Facts Similarity 58% Discussion Similarity 49% Provision Overlap 42% Outcome Alignment 100% Tag Overlap 57%
Shared provisions: I.1, II.1.c, II.4.a, II.4.b, III.1.a Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 49% Discussion Similarity 66% Provision Overlap 27% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: II.4.a, III.1.a, III.3.a Same outcome True View Synthesis
Component Similarity 63% Facts Similarity 67% Discussion Similarity 79% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 22%
Shared provisions: I.1, III.1.a Same outcome True View Synthesis
Component Similarity 44% Facts Similarity 42% Discussion Similarity 66% Provision Overlap 33% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.5, II.4.a, III.1.a, III.3.a Same outcome True View Synthesis
Component Similarity 41% Facts Similarity 32% Discussion Similarity 71% Provision Overlap 36% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.5, II.1.c, II.4.a, III.1.a Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 51% Discussion Similarity 67% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: II.4.a, II.4.b Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 46% Discussion Similarity 73% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: I.1, III.1.a Same outcome True View Synthesis
Component Similarity 50% Facts Similarity 49% Discussion Similarity 68% Provision Overlap 13% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.1, II.1.c Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 53% Discussion Similarity 63% Provision Overlap 7% Outcome Alignment 100% Tag Overlap 22%
Shared provisions: II.4.a Same outcome True View Synthesis
Component Similarity 50% Facts Similarity 49% Discussion Similarity 74% Provision Overlap 14% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: II.4.a, II.4.b Same outcome True 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 3
Fulfills
  • QBS Submittal Deadline Strict Enforcement Obligation
  • Misdirected QBS Submittal Rejection Documentation Obligation
  • Engineer A Procurement Integrity Public Interest QBS Administration
Violates None
Fulfills None
Violates
  • QBS Submittal Deadline Strict Enforcement Obligation
  • Harmless Error Non-Exception in QBS Procurement Compliance Obligation
  • Engineer A Harmless Error Non-Exception Firm B Submittal
  • City Manager Administrative Assistant Non-Facilitation Misdirected Submittal
Fulfills
  • QBS Submittal Deadline Strict Enforcement Obligation
  • Misdirected QBS Submittal Rejection Documentation Obligation
  • Prior Performance Non-Consideration in QBS Compliance Determination Obligation
  • Harmless Error Non-Exception in QBS Procurement Compliance Obligation
  • Engineer A QBS Deadline Strict Enforcement Firm B Rejection
  • Engineer A Prior Performance Non-Consideration Firm B Compliance Determination
  • Engineer A Harmless Error Non-Exception Firm B Submittal
  • Engineer A Good Intent Non-Justification Firm B Sympathy Procurement
  • Engineer A Procurement Integrity Public Interest QBS Administration
Violates
  • Engineer A Prior Performance Non-Consideration Firm B Compliance Determination
Decision Points 6

Should Engineer A return Firm B's late and misdirected submittal unopened, or accept it into the QBS evaluation on the grounds that the procedural error was minor and Firm B has a strong prior performance record with City X?

Options:
Return Submittal and Document Rejection Board's choice Return Firm B's submittal unopened with written notice to Firm B that the SOQ was received after the published deadline and at the wrong location, and document the rejection in the procurement record
Accept Submittal as Minor Irregularity Accept Firm B's submittal into the evaluation pool on the grounds that the envelope arrived within the same governmental entity on the same day, treating the misdirection as a minor administrative irregularity that caused no demonstrable harm to other competing firms
Escalate Decision to City Attorney Escalate the disposition decision to the city attorney or procurement officer rather than acting unilaterally, presenting the full chain-of-custody facts and requesting an official ruling on whether the city manager's office acceptance constitutes a valid city receipt that tolls the deadline
Toulmin Summary:
Warrants III.2.b III.4

The QBS Submittal Deadline Strict Enforcement Obligation requires Engineer A to reject submittals that arrive late or at the wrong location regardless of apparent harmlessness or the firm's prior performance record. The Harmless Error Non-Exception principle establishes that procedural non-compliance cannot be excused by the absence of demonstrable harm. The Procurement Integrity Over Qualification Merit Balancing Principle holds that procedural integrity is not subordinate to the goal of selecting the most qualified firm. The Prior Performance Non-Consideration Obligation bars Engineer A from allowing Firm B's track record on prior city projects to influence the compliance determination. Competing against these, the Public Welfare Paramount principle raises the question of whether strict rejection could produce a worse public outcome if Firm B is the most qualified firm for a safety-critical building project.

Rebuttals

Uncertainty arises if the misdirection was caused or materially contributed to by the city manager's administrative assistant's acceptance and four-hour retention of the envelope, which could support an equitable argument that city-side conduct partially caused the non-compliance. Additionally, if Firm B is demonstrably the most qualified firm for a public safety-critical project and all other submittals are materially weaker, a consequentialist argument for acceptance gains surface plausibility, though the board rejected this on systemic grounds. The harmless error rebuttal is further weakened by the fact that Engineer A cannot make a reliable comparative quality judgment before evaluating the 13 compliant submittals.

Grounds

Firm B delivered its SOQ to the city manager's office rather than the city clerk's office as required by the published RFQ. The envelope was date- and time-stamped at 2:05 pm on January 30, more than four hours after the 10:00 am deadline. The deadline and submission location were published on the city's RFQ webpage, stated in the hard copy agenda distributed at the mandatory pre-submittal meeting, and communicated to all 14 interested firms. Engineer A, as QBS review team point of contact, received the envelope from the city manager's administrative assistant upon returning to his office that afternoon.

Before taking any action on Firm B's envelope, should Engineer A disclose his prior favorable relationship with Firm B to a supervisor or procurement authority, or is Engineer A's confidence in his own impartiality sufficient to proceed with the rejection decision unilaterally?

Options:
Disclose Relationship Before Taking Action Board's choice Immediately disclose the prior favorable relationship with Firm B to a procurement supervisor or the city attorney before taking any action on the envelope, and request supervisory ratification of the rejection decision
Act on Rules Then Document Relationship Proceed with returning the envelope unopened based on the unambiguous published rules, then document the prior relationship and the action taken in the procurement record as a contemporaneous disclosure, treating the correct substantive outcome as sufficient to demonstrate impartiality
Recuse and Transfer to Another Official Recuse entirely from any further involvement in the Firm B submittal disposition and all subsequent QBS evaluation steps involving Firm B, transferring the envelope and the rejection decision to another city official without taking any personal action on it
Toulmin Summary:
Warrants II.4 III.2

The Prior Favorable Relationship Procurement Recusal or Disclosure Constraint requires that an engineer with a documented prior favorable relationship with a competing firm either recuse from evaluation decisions affecting that firm or make full disclosure to procurement supervisors before exercising unilateral discretion. The Appearance of Impropriety principle establishes that structural conflicts of interest obligate disclosure even when the conflicted party acts correctly, because procurement integrity requires demonstrably impartial processes, not only impartial results. The deontological duty of honesty and transparency for public officials exercising discretionary procurement authority is not contingent on whether the engineer believes the relationship influenced the decision. Competing against disclosure, the Procurement Honorable Conduct principle suggests that if Engineer A's prior relationship was routine and transactional, and the substantive decision is unambiguously correct, mandatory disclosure may be disproportionate.

Rebuttals

The recusal or disclosure warrant would be weakened if Engineer A's prior relationship with Firm B was so routine and arms-length that no reasonable observer would perceive it as creating favoritism risk. Additionally, if the only permissible action, returning the envelope unopened, is so clearly mandated by published rules that no genuine discretion exists, the argument that disclosure is required before exercising 'discretionary' authority loses force. Uncertainty also arises from the question of whether disclosure after the fact, combined with accurate documentation, adequately cures the appearance concern without requiring pre-action escalation.

Grounds

Firm B had performed well on several other engineering design projects for City X, creating a documented prior favorable professional relationship between Engineer A and Firm B. Engineer A is the designated point of contact on the City X QBS review team. When the city manager's administrative assistant intercepted Engineer A with Firm B's envelope, Engineer A was placed in the position of making a unilateral procedural determination, whether to return or accept the submittal, affecting a firm with which he had a prior positive working relationship. The decision to return the envelope, while substantively correct, was made without disclosure to any supervisor or procurement authority.

Should Engineer A document the full chain of custody of Firm B's misdirected envelope, including the four-hour retention by the city manager's administrative assistant, or limit the record to a standard deadline-rejection entry?

Options:
Document Full Chain-of-Custody Details Board's choice Create a comprehensive contemporaneous written record documenting the full chain of custody, including the city manager's office receipt timestamp, the administrative assistant's identity and role, the four-hour retention period, the basis for rejection, and the return of the envelope unopened, to protect City X from future procurement challenges.
Record Standard Deadline Rejection Only Create a standard rejection record documenting the deadline non-compliance and the return of the envelope unopened, without separately documenting the administrative assistant's four-hour retention or the misdirected delivery to the city manager's office.
Document Rejection and Seek Legal Guidance Record the rejection and chain-of-custody details in the procurement file, then consult City X's legal counsel to determine whether the four-hour retention by the city manager's office creates any additional documentation or disclosure obligations beyond Engineer A's standard record-keeping practice.
Toulmin Summary:
Warrants II.2.a III.2.b

The Misdirected QBS Submittal Rejection Documentation Obligation requires Engineer A to document the basis for rejection, the time and location of receipt, the chain of custody, and communication of the rejection to Firm B. The Faithful Agent Obligation requires Engineer A to protect City X from foreseeable legal exposure by creating a defensible evidentiary record. The Transparency Principle requires that the complete sequence of events, including the city manager's office receipt, be accurately reflected in the procurement record, and that omission or minimization of the administrative assistant's role to insulate the city from legal risk would itself constitute deception violating Engineer A's professional obligations. The Procurement Challenge Vulnerability Assessment Capability requires Engineer A to recognize that the four-hour chain of custody creates a basis for legal challenge that documentation can mitigate but concealment would worsen.

Rebuttals

The documentation obligation warrant would be weakened if City X's procurement rules contain no explicit record-keeping requirement for rejected submittals and the action taken is unambiguously correct under published rules, making formal documentation a best practice rather than an ethical mandate. Uncertainty also arises from the tension between full transparency about the administrative assistant's conduct, which could expose the city to legal challenge from Firm B, and the obligation to document accurately, suggesting that consultation with City X's legal counsel may be required before Engineer A determines the appropriate scope and form of the documentation.

Grounds

The envelope bearing Firm B's SOQ was date- and time-stamped at 2:05 pm on January 30 in the city manager's office, more than four hours after the 10:00 am deadline and at the wrong location. The city manager's administrative assistant retained the envelope for the entire intervening period before intercepting Engineer A upon his return to the office. This four-hour chain of custody through a non-designated city office is not procedurally neutral: it creates a factual record that Firm B could use to argue city-side complicity in the misdirection. Engineer A's faithful agent duty to City X and the public procurement transparency standard both require that all procurement actions be fully accountable.

Should the city manager's administrative assistant have immediately notified the city clerk's office and alerted Firm B of the delivery error, physically transferred the envelope to the city clerk's office without notifying Firm B, or simply routed the envelope to the named recipient without making a procurement compliance determination?

Options:
Notify Clerk's Office and Alert Firm B Board's choice Upon receiving the misdirected envelope, immediately contact the city clerk's office to report the delivery error and separately notify Firm B's representative that the submittal was delivered to the wrong location, allowing Firm B to take corrective action before any deadline passed.
Route Envelope to Named Recipient Route the envelope to Engineer A as the named recipient, treating the delivery as ordinary internal city mail and deferring any procurement compliance determination to Engineer A rather than making an independent procedural judgment.
Transfer Envelope to City Clerk's Office Physically carry the envelope to the city clerk's office immediately upon receipt, treating the misdirected delivery as a correctable internal routing error without separately notifying Firm B or flagging the compliance implications of the late transfer.
Toulmin Summary:
Warrants III.2

The Misdirected Submittal Non-Acceptance Obligation establishes that a public agency employee who receives a procurement submittal at the wrong office must treat it as non-compliant and may not accept it on behalf of the procuring agency, because the designated submission location is a material procurement requirement. Public procurement integrity norms impose on all city employees handling procurement materials an obligation to avoid actions that could compromise the fairness of a competitive process, not only on licensed engineers. The Good Intent Does Not Cure Procedural Impropriety principle applies with equal force to city-side administrative confusion: the assistant's acceptance of the envelope did not transform a non-compliant submittal into a compliant one, and the four-hour retention period is itself a procedural irregularity that complicates the chain-of-custody record and could form the basis of a legal challenge by Firm B arguing city-side complicity.

Rebuttals

The independent ethical responsibility warrant would be weakened if the administrative assistant had no training in or notice of QBS procurement rules, had no authority to make procurement compliance determinations, and acted in good faith by routing the envelope to the named recipient. Uncertainty also arises from the question of whether the assistant's conduct, accepting and forwarding rather than opening or altering the envelope, rises to the level of a procurement irregularity or is simply a ministerial act of internal mail routing that does not constitute city ratification of the late submittal. The fairness obligation to the 13 compliant firms may outweigh equitable sympathy for Firm B arising from the assistant's conduct regardless of how the assistant's responsibility is characterized.

Grounds

The city manager's administrative assistant received a large envelope bearing Engineer A's name and Firm B's letterhead at the city manager's office, not the designated city clerk's office, on January 30. The envelope was date- and time-stamped at 2:05 pm, indicating it was retained in the city manager's office for over four hours before Engineer A returned and was intercepted. The assistant then forwarded the envelope to Engineer A rather than immediately notifying Firm B of the delivery error, returning the envelope to the courier, or contacting the city clerk's office. The published RFQ unambiguously required submission at the city clerk's office by 10:00 am.

Should Engineer A reject Firm B's submittal based solely on procedural non-compliance without weighing prior performance, or accept the submittal into evaluation by treating Firm B's demonstrated competence as a mitigating factor in the compliance determination?

Options:
Reject Based Solely on Procedural Non-Compliance Board's choice Reject Firm B's submittal as procedurally non-compliant without considering Firm B's prior performance record, treating the compliance determination as categorically separate from any merit evaluation and preserving equal treatment of all submitting firms.
Accept and Weigh Prior Performance as Mitigation Accept Firm B's submittal into the evaluation pool while documenting the procedural irregularity, treating Firm B's demonstrated competence on prior City X projects as a mitigating factor that, in combination with public safety considerations, justifies inclusion despite the late delivery.
Reject but Flag Public Welfare Concerns Reject Firm B's submittal as procedurally non-compliant, but formally document for City X procurement authorities that the rejection was made without weighing prior performance and that public welfare implications of the reduced qualified-firm pool warrant their attention, leaving any remedial action to the procuring authority rather than the QBS administrator.
Toulmin Summary:
Warrants I.1 II.2 III.2.b

The Prior Performance Non-Consideration Obligation bars Engineer A from allowing Firm B's track record to influence the compliance determination, recognizing that prior performance is irrelevant to procedural compliance and that allowing it to influence the determination undermines equal treatment of all competing firms. The Procurement Integrity Over Qualification Merit Balancing Principle establishes that procedural integrity is not subordinate to the substantive goal of selecting the most qualified firm, both values must be pursued simultaneously. The QBS framework itself is a public welfare instrument: it exists to ensure that public agencies select engineering firms through a process that is transparent, competitive, and resistant to favoritism, and allowing merit-based exceptions to deadlines would erode competitive procurement integrity for all future procurements. From a consequentialist perspective, the systemic costs of deadline non-enforcement, erosion of procurement integrity, legal vulnerability for City X, unfairness to 13 compliant firms, and precedent-setting effects, outweigh the speculative individual benefit of Firm B's participation.

Rebuttals

The prior performance non-consideration warrant is most strongly challenged by the consequentialist argument that if Firm B is demonstrably the most qualified firm for a public safety-critical building and all other submittals are materially weaker, strict rejection may produce a worse public outcome. This rebuttal is undermined by the fact that Engineer A cannot make a reliable comparative quality judgment before evaluating the 13 compliant submittals, the premise that strict rejection necessarily produces a less capable outcome is speculative and factually unsupported at the time of decision. Additionally, the Faithful Agent Obligation to City X could be invoked to argue that City X's institutional interest in retaining a high-performing firm justifies leniency, but the board rejected this on the grounds that accepting a late submittal would expose City X to legal challenge from the 13 compliant firms, potentially invalidating the entire procurement.

Grounds

Firm B had performed well on several other engineering design projects for City X, creating a documented institutional record of satisfactory prior performance. The project at issue involves a public building, raising the question of whether public safety considerations could justify procedural leniency toward a demonstrably capable firm. Engineer A, as QBS point of contact, was positioned to make a unilateral determination about whether to accept or return the late submittal before evaluating any of the 13 compliant submittals. The published QBS rules established that all submittals must be received at the city clerk's office by 10:00 am, with no exception provision for prior performance or demonstrated competence.

Should Engineer A proactively notify all 13 other pre-submittal firms that Firm B's late, misdirected submittal was returned unopened, or is the transparency obligation satisfied by maintaining an accurate procurement record and responding truthfully to direct inquiries?

Options:
Maintain Accurate Record, Answer Inquiries Board's choice Satisfy the transparency obligation by creating a complete and accurate procurement record of Firm B's submittal disposition and responding truthfully to any direct inquiry from competing firms, without initiating unsolicited notification to all 13 pre-submittal attendees.
Notify All Competing Firms Proactively Proactively notify all 13 other pre-submittal firms in writing that one SOQ was received after the deadline and at the wrong location and was returned unopened, treating broad notification as the mechanism for ensuring equal access to information about the procurement outcome.
Disclose Only Upon Formal Public Records Request Limit disclosure of Firm B's submittal disposition to responses to formal public records requests, on the grounds that proactive notification could constitute a procedural irregularity and that procurement confidentiality rules govern communications until a final award decision is made.
Toulmin Summary:
Warrants II.3 III.2.b III.4

The Transparency Principle requires Engineer A to openly and accurately account for Firm B's submittal disposition in the procurement record. The QBS Submittal Deadline Integrity and Equal Treatment Obligation requires that all competing firms be treated equally, which includes equal access to information about the procurement's progress. The Faithful Agent Obligation requires Engineer A to protect City X from foreseeable legal exposure, but the ethical duty of objectivity and truthfulness prohibits omission or minimization of the administrative assistant's role to insulate the city from legal risk, because such omission would itself constitute deception. The Procurement Challenge Vulnerability Assessment Capability requires Engineer A to recognize that allowing Firm B's submittal to be considered, or failing to document its rejection accurately, would open the procurement to challenge or create a climate of non-adherence to public procurement rules.

Rebuttals

The broad proactive notification obligation would be rebutted if City X's QBS procurement rules specify that submittal disposition communications are confidential until a final award decision, or if notifying competitors of Firm B's failure could itself constitute a procedural irregularity by drawing attention to a competitor's failure in a manner not contemplated by the QBS process rules. The tension between full transparency and legal exposure is sharpened by the fact that transparency obligations are typically understood to operate without regard to legal exposure consequences, but the specific context of public procurement, where full disclosure of city-side administrative failure could be used by Firm B to challenge the rejection, creates genuine uncertainty about whether consultation with legal counsel is required before Engineer A determines the scope of the documentation.

Grounds

The city conducted a mandatory pre-submittal meeting attended by representatives of 14 interested firms. All 14 firms had constructive notice of the 10:00 am deadline and city clerk's office submission location through the pre-submittal meeting agenda, the city's RFQ webpage, and the published RFQ documentation. Firm B's submittal was received late and at the wrong location and was returned unopened. The 13 other firms that complied with the published requirements have a legitimate interest in knowing the number and status of submittals received. The city manager's administrative assistant's four-hour retention of the envelope creates a chain-of-custody record that, if fully disclosed, could provide Firm B with a basis to argue city-side complicity in the late delivery.

8 sequenced 3 actions 5 events
Action (volitional) Event (occurrence) Associated decision points
DP4
The city manager's administrative assistant's independent procedural and quasi-e...
Notify Clerk's Office and Alert Firm B Route Envelope to Named Recipient Transfer Envelope to City Clerk's Office
Full argument
DP1
Engineer A's obligation to strictly enforce the published QBS submittal deadline...
Return Submittal and Document Rejection Accept Submittal as Minor Irregularity Escalate Decision to City Attorney
Full argument
DP2
Engineer A's obligation to disclose his prior favorable professional relationshi...
Disclose Relationship Before Taking Acti... Act on Rules Then Document Relationship Recuse and Transfer to Another Official
Full argument
DP3
Engineer A's obligation to create a formal, contemporaneous documentation record...
Document Full Chain-of-Custody Details Record Standard Deadline Rejection Only Document Rejection and Seek Legal Guidan...
Full argument
DP5
The resolution of the apparent tension between the Procurement Integrity Over Qu...
Reject Based Solely on Procedural Non-Co... Accept and Weigh Prior Performance as Mi... Reject but Flag Public Welfare Concerns
Full argument
DP6
Engineer A's transparency obligation regarding the disposition of Firm B's submi...
Maintain Accurate Record, Answer Inquiri... Notify All Competing Firms Proactively Disclose Only Upon Formal Public Records...
Full argument
4 Pre-Submittal Meeting Held Prior to January 30 (exact date unspecified, before SOQ deadline)
5 Deadline Passes Unmet January 30, 10:00 am
6 Submittal Arrives Wrong Office January 30, 2:05 pm
7 Engineer A Discovers Submittal January 30, afternoon (after 2:05 pm, exact time unspecified)
8 QBS Evaluation Period Affected January 30, afternoon onward (following Engineer A's discovery)
Causal Flow
  • City Establishes Submission Rules Firm B Submits SOQ Late
  • Firm B Submits SOQ Late Engineer A Decides on Late Submittal
  • Engineer A Decides on Late Submittal Submittal Arrives Wrong Office
Opening Context
View Extraction

You are Engineer A, the point of contact on City X's QBS review team for the selection of an engineering firm to design a new public building. City X published a clear submittal deadline of 10:00 am on January 30, listing the date, time, and required delivery location in the RFQ and at the mandatory pre-submittal meeting attended by 14 firms. Returning to your office that afternoon, you are intercepted by the city manager's administrative assistant, who hands you a large envelope from Firm B, date- and time-stamped at 2:05 pm in the city manager's office, nearly four hours past the published deadline. Firm B participated in the pre-submittal meeting and has a record of strong performance on prior City X engineering projects. The decisions you face now concern how to handle the late submittal, what disclosures and documentation your role requires, and what obligations you carry toward the other 13 firms that submitted on time.

From the perspective of Engineer A QBS Review Team Point of Contact
Characters (6)
stakeholder

A public agency administering a qualifications-based selection process for a new building project, bound by procurement regulations and obligations of fairness to all competing firms.

Motivations:
  • To secure the most qualified engineering firm through a legally defensible, impartial process that protects the city from liability and maintains public trust in government procurement.
protagonist

A designated procurement administrator overseeing the QBS submission process who must now decide whether to accept or reject a late, misdirected submittal from a firm with a favorable prior relationship with the city.

Motivations:
  • To uphold the integrity of the procurement process and treat all competitors equitably, while navigating the professional and relational pressure created by Firm B's established track record with the city.
stakeholder

An engineering firm with a demonstrated history of successful city projects that submitted its Statement of Qualifications four hours late and to the wrong office, creating a compliance failure despite its strong prior standing.

Motivations:
  • To remain competitive for city contracts and potentially leverage its prior relationship with the city to gain consideration despite a procedurally non-compliant submission.
decision-maker

An administrative staff member who inadvertently became a key figure in the procurement dispute by receiving and date-stamping Firm B's misdirected submittal and then directly presenting it to Engineer A.

Motivations:
  • To fulfill routine administrative duties responsibly by documenting receipt and ensuring the envelope reached the appropriate decision-maker, without awareness of the full ethical implications of the handoff.
decision-maker

Submitted firm's engineering qualifications to a state agency in response to a public RFQ; the submitted qualifications were subsequently obtained by competitor Engineer B via a FOIA request prior to Engineer B's own submission.

stakeholder

Submitted a FOIA request to obtain Engineer A's qualifications submission before submitting his own firm's qualifications to the same state agency for the same RFQ; the Board found the FOIA request ethical but cautioned that it should have been made after Engineer B's own submission.

Ethical Tensions (9)

Tension between QBS Submittal Deadline Strict Enforcement Obligation and City Manager Administrative Assistant Non-Facilitation Misdirected Submittal Constraint

Obligation Vs Constraint
Affects: Faithful Agent Obligation Invoked for Engineer A QBS Administration Role

Tension between Prior Favorable Relationship Procurement Recusal or Disclosure Constraint and Appearance of Impropriety - Engineer A Prior Relationship Firm B QBS Decision

Obligation Vs Constraint
Affects: Conflict of Interest - Engineer A QBS Evaluator with Known Firm

Tension between Misdirected QBS Submittal Rejection Documentation Obligation and City Manager Administrative Assistant Non-Facilitation Misdirected Submittal Honorable Conduct

Obligation Vs Constraint
Affects: Procurement Honorable Conduct - Engineer A QBS Administration

Tension between Misdirected Submittal Non-Acceptance Obligation in Public Procurement and Good Intent Does Not Cure Procedural Impropriety Invoked for Administrative Assistant Action

Obligation Vs Constraint
Affects: City Manager Administrative Assistant Non-Facilitation Misdirected Submittal

Tension between Prior Performance Non-Consideration in QBS Compliance Determination Obligation and Competitive Procurement Fairness - 14 Firm Equal Treatment QBS City X

Obligation Vs Constraint
Affects: Engineer A Prior Performance Non-Consideration Firm B Compliance Determination

Tension between QBS Submittal Deadline Integrity and Equal Treatment Obligation and Competitive Procurement Fairness - 14 Firm Equal Treatment QBS City X

Obligation Vs Constraint
Affects: Fairness in Professional Competition Invoked for All 14 Pre-Submittal Firms

Engineer A is obligated to reject Firm B's submittal without any harmless-error exception, yet the public interest may be better served by evaluating a qualified firm whose late or misdirected delivery caused no competitive prejudice to the other 13 firms. Strict rule adherence eliminates a potentially superior firm from consideration, which may produce a worse outcome for the public client (City X) than a flexible reading would. The tension is genuine because both positions are grounded in legitimate procurement values: procedural integrity and equal treatment on one side, best-value public service on the other.

Obligation Vs Constraint
Affects: Engineer A QBS Review Team Point of Contact Firm B Late Submittal QBS Competitor City X Municipal Infrastructure Client Late Submittal QBS Competing Firm
Moral Intensity (Jones 1991):
Magnitude: high Probability: high immediate direct concentrated

Engineer A has a prior favorable relationship with Firm B and is simultaneously the QBS Review Team Point of Contact responsible for ruling on Firm B's submittal compliance. The obligation to administer the procurement with full integrity for the public interest conflicts with the constraint that a prior favorable relationship creates an appearance of impropriety and potentially a disqualifying conflict of interest. If Engineer A rules strictly against Firm B, the decision may appear retaliatory or performatively impartial; if Engineer A shows any leniency, it appears biased. Either path is ethically compromised unless Engineer A recuses or discloses, yet no recusal mechanism is described, leaving the integrity obligation impossible to fully satisfy.

Obligation Vs Constraint
Affects: Engineer A QBS Review Team Point of Contact Firm B Late Submittal QBS Competitor City X Municipal Infrastructure Client QBS Review Team Point of Contact Engineer
Moral Intensity (Jones 1991):
Magnitude: high Probability: high immediate direct concentrated

Engineer B is obligated to time any FOIA request for competitor qualification data only after submission deadlines have passed, so as not to gain an unfair pre-submission advantage. However, the constraint on ethical use of FOIA-acquired intelligence extends beyond timing: even post-submission, using detailed knowledge of competitors' qualifications to retroactively tailor or supplement one's own submittal, or to inform future competitive strategy in the same procurement cycle, may constitute an unfair advantage. The tension arises because satisfying the timing obligation (waiting until after submission) does not automatically satisfy the ethical-use constraint, yet the obligation implies that post-submission use is permissible. The boundary between legitimate public-records access and exploitative competitive intelligence is genuinely unclear.

Obligation Vs Constraint
Affects: FOIA-Requesting Competing Engineer Public RFQ Submitting Engineer Engineer A Prior RFQ Submitter City X Municipal Infrastructure Client
Moral Intensity (Jones 1991):
Magnitude: medium Probability: medium near-term indirect diffuse
Opening States (10)
Conflict of Interest - Engineer A QBS Evaluator with Known Firm BER Case 10-8 FOIA Competitor Intelligence Acquisition Late SOQ Submission Received Outside Formal Process State Prior Favorable Relationship with Competing Firm State QBS Law Applicable - City X Public Building Project Late SOQ Submission - Firm B Prior Favorable Relationship - Engineer A and Firm B Regulatory Compliance State - QBS Deadline Enforcement Client Relationship Established - Engineer A and City X Procurement Rule Strict Adherence vs. Harmless Error Tension State
Key Takeaways
  • Procedural integrity in competitive procurement must be maintained uniformly, even when administrative errors by third parties create sympathetic circumstances for a disadvantaged firm.
  • Engineers in procurement oversight roles must treat misdirected or late submittals with the same strict standards regardless of prior relationships with submitting firms, to avoid both actual and perceived favoritism.
  • The ethical resolution of returning the submittal unopened preserves the engineer's neutrality by preventing any informational advantage while simultaneously documenting the procedural failure transparently.