Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe 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.
Provisions (3)
View ExtractionAll 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.
-
Engineer A Procurement Rules Adherence Duty
Engineer A must remain objective and truthful when addressing the misdelivered submittal rather than acting on personal bias.
-
Deadline Publication
Publishing deadline terms is a public statement that must be objective and truthful
-
Late Submittal Rejection
Rejection decision must be communicated objectively and truthfully
-
Engineer A Harmless Error View
Engineer A must communicate this judgment objectively and truthfully to the selection committee
-
Firm B Late Misdirected Submittal
Any public statement regarding the late submittal must be objective and truthful
-
Engineer A Submittal Consideration Bar
Objective public statements require not misrepresenting the late SOQ as validly submitted
-
Procurement Integrity in QBS Submittal
Objective and truthful public statements require not misrepresenting how submissions were handled
-
Public Confidence in QBS Process
Truthful public statements about the process help maintain public confidence in procurement fairness
-
Engineer A QBS Review Engineer
As a licensed engineer reviewing submissions he must communicate about the process objectively and truthfully
-
Firm B Competing Firm
As a professional engineering firm making a qualifications submission it must present statements truthfully and objectively
-
Submittal Time Stamping
Requires objective and truthful documentation of when the submittal was received
-
Late Submittal Discovery
Requires truthful public disclosure regarding the late submittal finding
-
Engineer A Procurement Rules Application
Engineer A must handle and report the misdelivered submittal matter in an objective and truthful manner
-
Firm B Submittal Deadline Duty
The Statement of Qualifications must truthfully and completely reflect Firm B's qualifications as of the submission date.
-
Late Submittal Rejection
Decision to reject must be based on complete and accurate information about timing
-
Deadline Publication
Published deadline must include all relevant details to be truthful
-
Firm B Late Misdirected Submittal
The circumstances of the late submittal must be fully and truthfully disclosed to the selection committee
-
Engineer A Late Receipt Knowledge
Engineer A must include all relevant information about the late receipt in any report or statement
-
Firm B Prior Performance Record
Prior performance information must be objectively and truthfully reported if used in evaluation
-
Firm B SOQ Receipt Boundary
Truthful reporting requires accurately noting the SOQ was received outside the required time and place
-
Engineer A Submittal Consideration Bar
Truthful and complete reporting requires disclosing the late and misdelivered nature of the submission
-
Procurement Integrity in QBS Submittal
All relevant facts about the late submission must be disclosed truthfully in reports or statements
-
Qualified Firm Selection in QBS
Selection decisions must be based on complete and truthful information about firm qualifications and submission timing
-
Engineer A QBS Review Engineer
He must be objective and truthful in reporting the circumstances of the late submittal to the review team
-
Firm B Competing Firm
Its Statement of Qualifications is a professional report that must be truthful and include all relevant information
-
Submittal Time Stamping
Time stamp information must be accurate and reflect the true date it was current
-
Late Submittal Discovery
All relevant information about the late discovery must be included in reports or statements
-
Engineer A Procurement Rules Application
Engineer A must include all relevant and pertinent information regarding the late submittal when reporting or advising on the matter
-
Board Precedent Reasoning
The Board must be objective and truthful and include all relevant facts when applying precedent to reach its opinion
-
Firm B Submittal Deadline Duty
Firm B must adhere to the deadline honestly without seeking unfair advantage.
-
Engineer A Procurement Rules Adherence Duty
Engineer A must uphold honesty and integrity by following procurement rules impartially despite the late submittal.
-
Late Submittal Delivery
Submitting after deadline implicates honesty and integrity in following stated rules
-
Late Submittal Rejection
Rejecting a late submittal must be handled with honesty and integrity toward all parties
-
Submittal Handoff
Handling handoff of submittals requires honesty and integrity in the process
-
Procurement Method Selection
Selecting a fair procurement method reflects the highest standards of honesty and integrity
-
SOQ Receipt Deadline In Force
Honesty and integrity require adherence to established procurement deadlines
-
Published SOQ Requirements Notice
Integrity demands following the published requirements as stated
-
Engineer A Harmless Error View
Engineer A must apply the highest standards of integrity rather than personal leniency in judging rule violations
-
Procurement Integrity Challenge Exposure
Deviating from deadlines risks violating the integrity standard the code demands
-
Tolerated Non-Adherence Climate Risk
Allowing non-adherence undermines the highest standards of honesty and integrity
-
Procurement Conduct Disrepute Exposure
Improper handling of the late submittal could bring disrepute contrary to integrity standards
-
Qualification Versus Rule Adherence Balance
Balancing qualifications against rule adherence must be guided by honesty and integrity
-
QBS Procedure For Building Project
The QBS procedure itself must be conducted with honesty and integrity
-
Firm B SOQ Receipt Boundary
Honesty and integrity require adhering strictly to the published deadline and delivery location
-
Engineer A Submittal Consideration Bar
Integrity requires Engineer A to refrain from considering or favoring the improperly submitted SOQ
-
Procurement Fairness in QBS Submittal
Honesty and integrity require adherence to the published fair submittal deadline for all firms
-
Procurement Integrity in QBS Submittal
Highest standards of honesty and integrity preclude excusing a rule violation regardless of intent
-
Public Confidence in QBS Process
Maintaining integrity in procurement processes is essential to preserving public trust
-
Engineer A QBS Review Engineer
He must act with honesty and integrity in handling the late-arriving submittal and advising the review team
-
Firm B Competing Firm
As a competing engineering firm it must uphold honesty and integrity in adhering to procurement rules and deadlines
-
Submittal Deadline Passage
Honesty and integrity require respecting the established deadline for submissions
-
Submittal Time Stamping
Integrity requires accurate and unaltered time stamping of submittals
-
Late Submittal Discovery
Highest standards of honesty require proper handling once a late submittal is discovered
-
City X RFQ
Honesty and integrity govern adherence to the deadline and location requirements stated in the RFQ
-
BER Case 10-8
This precedent case directly addresses honesty and integrity in balancing qualification selection with procurement rule compliance
-
Engineer A Procurement Rules Application
Engineer A must apply procurement rules with honesty and integrity when handling Firm B's misdelivered submittal
-
City X Selection Process Structuring
City X must structure the selection process with honesty and integrity to ensure fairness to all firms
-
Board Ethical Balancing
The Board's balancing of qualifications against procedural adherence reflects the highest standards of honesty and integrity
Cross-Case Connections
View ExtractionExplicit 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:
Public procurement systems and their associated rules and regulations are designed to serve the public interest, and engineers should act consistently with those rules; a balance must be struck between selecting the most qualified firm and strict adherence to procurement rules and policies.
Citation Context:
The Board cited this prior case to establish the principle that public procurement systems are designed to advance the public interest and that adherence to established rules and regulations should be respected, even when strict application may seem to create harsh or formalistic results.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions (1 board)
View ExtractionWhat are Engineer A’s ethical responsibilities under the circumstances?
Implicit (4)
Does the fact that the misdirected submittal was delivered to the city manager's office rather than the city clerk's office raise process questions about how City X handled and routed the envelope internally, independent of Firm B's fault?
Should Engineer A's prior positive experience with Firm B's performance on other city projects be treated as a factor that could improperly bias his handling of the late submittal, and what safeguards exist to prevent this?
What obligations, if any, does Engineer A have to inform the other 13 participating firms of how the late submittal was handled, to preserve transparency and trust in the process?
Does Engineer A have a duty to document the circumstances of the late receipt (time stamp, location, discovery) to protect the integrity of the QBS process against future challenge?
Principle tension (3)
How should Qualified Firm Selection in QBS be balanced against Procurement Fairness in QBS Submittal when a highly qualified firm's submittal arrives after the deadline due to an apparent internal misdirection rather than negligence?
Does strict enforcement of Procurement Integrity in QBS Submittal risk undermining Public Confidence in QBS Process if the public perceives the rejection of a well-qualified firm as an overly technical or unfair outcome, or does allowing exceptions undermine that same confidence more severely?
How should Engineer A weigh Procurement Fairness in QBS Submittal toward the other 13 firms that met the deadline against any equitable consideration for Firm B given the ambiguous cause of the late delivery?
Theoretical (3)
From a deontological perspective, did Engineer A fulfill his duty to adhere strictly to published procurement rules by rejecting Firm B's late submittal regardless of the firm's qualifications?
From a consequentialist perspective, did the outcome of excluding a well-qualified firm from consideration justify the strict enforcement of the submittal deadline for the sake of overall procurement integrity?
Did Engineer A act with professional integrity when he treated Firm B's late submittal the same as he would any other firm's late submittal, despite Firm B's strong prior performance record with the city?
Counterfactual (3)
If Firm B had not previously performed well on other engineering design projects for the city, would the Board's conclusion that Engineer A should return the submittal unopened have been any different, or does this confirm that qualifications are irrelevant to the timeliness determination?
If the city's published RFQ had specified only a submission date without a specific time and location, would the Board still have concluded that the 2:05 pm submittal in the city manager's office constituted a late and misdirected submittal warranting rejection?
If there had been evidence that Firm B intentionally delayed or misdirected its submittal to gain an advantage, would the Board's conclusion to simply return the submittal unopened still be an adequate response, or would it require additional ethical action by Engineer A?
Decisions & Arguments (5)
View ExtractionShould Engineer A accept and evaluate Firm B's late submittal, or reject it as untimely regardless of the firm's qualifications and the cause of delay?
Firm B's envelope arrived at the city manager's office rather than the city clerk's office and was time-stamped as received after the published Submittal Deadline had passed; Engineer A had prior favorable experience with Firm B on other city projects.
Engineers must adhere to published public procurement rules and policies uniformly; procurement process integrity requires that deadlines be enforced as a bright-line boundary rather than through discretionary, case-by-case judgments about intent or merit.
Would not apply if the published rules themselves permitted discretionary extensions for demonstrated administrative error, but no such provision is described in the case, so the bright-line rule stands.
Should Engineer A allow his favorable prior experience with Firm B to influence his handling of the late submittal, or must he actively guard against that familiarity?
Engineer A had worked with Firm B on other city projects and held a positive view of its performance; the QBS process involved 14 competing firms subject to the same published deadline.
Engineers must avoid actual or perceived bias in applying procedural rules; equal treatment of all competitors is required to preserve the integrity of a competitive selection process.
Would not apply if the procurement rules explicitly authorized discretionary consideration of a firm's track record in timeliness determinations, but no such authorization exists here.
Must Engineer A contemporaneously document the circumstances of Firm B's late submittal, or is simply returning the envelope unopened sufficient?
The submittal was discovered late by an administrative assistant after being delivered to the city manager's office rather than the city clerk's office, and the deadline had already passed.
Engineers responsible for administering a competitive selection process must maintain records sufficient to demonstrate that procedural decisions were sound and non-arbitrary.
Would not apply if the rejection were never subject to challenge or public scrutiny, but the presence of 13 other competing firms and possible future disputes makes documentation necessary.
Does Engineer A have an obligation to proactively notify the other 13 participating firms about the handling of Firm B's late submittal?
Fourteen firms participated in the QBS process under the same published deadline; only Firm B's submittal arrived late and was returned unopened.
Public confidence in a competitive process depends on evenhanded rule application, which can be demonstrated through accurate record-keeping rather than requiring proactive individualized disclosure to every competitor.
Would not apply if a competing firm formally requested information about how the late submittal was handled, in which case disclosure through the record would be warranted.
Should City X treat the misdirected delivery as raising a legitimate internal process concern requiring administrative review, separate from Engineer A's obligation to reject the late submittal?
Firm B's envelope was delivered to the city manager's office instead of the city clerk's office specified in the RFQ, and the submittal was time-stamped as received only after the deadline had passed.
Submitting firms bear responsibility for ensuring delivery to the location specified in published requirements, while public entities have a separate administrative interest in maintaining reliable internal procedures for logging and time-stamping submittals.
Would not apply if the RFQ's designated delivery location were ambiguous or if City X staff had affirmatively redirected the envelope, but the published requirement clearly specified the city clerk's office.
Event Timeline (10)
Case timeline
- Adherence to Public Procurement Rules and Policies
- began: QBS Procedure For Building Project
- Adherence to Public Procurement Rules and Policies
- began: Published SOQ Requirements Notice
- Adherence to Public Procurement Rules and Policies
- began: SOQ Receipt Deadline In Force
- Adherence to Public Procurement Rules and Policies
- began: Firm B Late Misdirected Submittal
- began: Engineer A Late Receipt Knowledge
- began: Procurement Conduct Disrepute Exposure
- began: Procurement Integrity Challenge Exposure
- Adherence to Public Procurement Rules and Policies
Narrative (3 main characters)
View ExtractionOpening Context
Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.
You are Engineer A, an engineer employed by City X and serving as the point of contact on the city's QBS review team for the design of a new public building. City X conducted a mandatory pre-submittal meeting attended by representatives of 14 engineering firms, after which the city published the submittal deadline, requiring all Statements of Qualifications to be received in the city clerk's office no later than 10:00 am on January 30. This deadline appeared on the city's RFQ webpage and on the printed agenda distributed at the pre-submittal meeting. On the afternoon of January 30, you returned to your office and were stopped by the city manager's administrative assistant, who held a large envelope addressed to you bearing the letterhead of Firm B, a firm that had attended the pre-submittal meeting and had performed well on several prior city projects. The envelope carried a date and time stamp showing it had been received in the city manager's office at 2:05 pm on January 30, more than four hours after the published deadline. You now face a series of decisions about how to handle this late submittal and what obligations follow from it.
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.
Guided by: Procurement Fairness in QBS Submittal, Procurement Integrity in QBS Submittal, Qualified Firm Selection in QBS
Firm B is obligated to submit its Statement of Qualifications by the deadline, but if it fails to do so, Engineer A is bound by a strict bar against considering late submittals. This creates tension between Firm B's interest in having its late submittal reviewed and Engineer A's duty to enforce the consideration cutoff, especially if there is pressure to make an exception for a qualified firm.
Engineer A's duty to adhere to procurement rules requires treating all firms equally under the established process, but the fixed boundary marking when Firm B's SOQ was actually received (after the deadline) constrains what Engineer A can legitimately do with that submission. If City staff or others pressure Engineer A to overlook the late receipt, this creates tension between rule adherence and the hard boundary condition.
Firm B's obligation to meet the submittal deadline and its likely desire for leniency after missing it conflicts with Engineer A's competing obligation to uphold uniform procurement rules for all firms. Granting Firm B special consideration to satisfy fairness to that single firm would undermine Engineer A's broader duty to protect the integrity of the QBS process for all competing firms and the public.
Firm B is obligated to submit its Statement of Qualifications by the deadline, but if it fails to do so, Engineer A is bound by a strict bar against considering late submittals. This creates tension between Firm B's interest in having its late submittal reviewed and Engineer A's duty to enforce the consideration cutoff, especially if there is pressure to make an exception for a qualified firm.
Engineer A's duty to adhere to procurement rules requires treating all firms equally under the established process, but the fixed boundary marking when Firm B's SOQ was actually received (after the deadline) constrains what Engineer A can legitimately do with that submission. If City staff or others pressure Engineer A to overlook the late receipt, this creates tension between rule adherence and the hard boundary condition.
Firm B is obligated to submit its Statement of Qualifications by the deadline, but if it fails to do so, Engineer A is bound by a strict bar against considering late submittals. This creates tension between Firm B's interest in having its late submittal reviewed and Engineer A's duty to enforce the consideration cutoff, especially if there is pressure to make an exception for a qualified firm.
Firm B's obligation to meet the submittal deadline and its likely desire for leniency after missing it conflicts with Engineer A's competing obligation to uphold uniform procurement rules for all firms. Granting Firm B special consideration to satisfy fairness to that single firm would undermine Engineer A's broader duty to protect the integrity of the QBS process for all competing firms and the public.
Other people involved in the case but not central to the opening narrative.
Firm B's obligation to meet the submittal deadline and its likely desire for leniency after missing it conflicts with Engineer A's competing obligation to uphold uniform procurement rules for all firms. Granting Firm B special consideration to satisfy fairness to that single firm would undermine Engineer A's broader duty to protect the integrity of the QBS process for all competing firms and the public.
Engineer A's duty to adhere to procurement rules requires treating all firms equally under the established process, but the fixed boundary marking when Firm B's SOQ was actually received (after the deadline) constrains what Engineer A can legitimately do with that submission. If City staff or others pressure Engineer A to overlook the late receipt, this creates tension between rule adherence and the hard boundary condition.
The Board’s deliberation
How the Board of Ethical Review resolved the case, verbatim from its published conclusions.
Opening States (10)
Summary
- Procedural deadlines in public procurement must be enforced uniformly, even when the excluded firm may be highly qualified, because fairness to all competitors and public trust in the process outweigh individual accommodation.
- Engineers administering selection processes should treat a firm deadline as a hard boundary rather than a negotiable guideline, since any exception invites pressure and undermines the process for everyone else.
- Returning a late submittal unopened is a clear, defensible way to enforce a deadline without appearing to evaluate or judge the substance of the late submission.