22 entities 3 actions 5 events 4 causal chains 9 temporal relations
Timeline Overview
Action Event 8 sequenced markers
City Establishes Submission Rules Prior to January 30, at the mandatory pre-submittal meeting
Firm B Submits SOQ Late January 30 at 2:05 pm
Engineer A Decides on Late Submittal Afternoon of January 30, upon returning to his office
Pre-Submittal Meeting Held Prior to January 30 (exact date unspecified, before SOQ deadline)
Deadline Passes Unmet January 30, 10:00 am
Submittal Arrives Wrong Office January 30, 2:05 pm
Engineer A Discovers Submittal January 30, afternoon (after 2:05 pm, exact time unspecified)
QBS Evaluation Period Affected January 30, afternoon onward (following Engineer A's discovery)
OWL-Time Temporal Structure 9 relations time: = w3.org/2006/time
mandatory pre-submittal meeting time:before publication of SOQ deadline (date, time, location)
mandatory pre-submittal meeting time:before SOQ submission deadline (10:00 AM, January 30)
SOQ submission deadline (10:00 AM, January 30) time:before Firm B submittal receipt (2:05 PM, January 30)
Firm B submittal receipt (2:05 PM, January 30) time:before Engineer A's return to office (afternoon, January 30)
hard copy agenda distribution at pre-submittal meeting time:intervalEquals mandatory pre-submittal meeting
Engineer B's FOIA request (BER Case 10-8) time:before interview process (BER Case 10-8)
Engineer B's FOIA request (BER Case 10-8) time:before Engineer B's RFQ submission (BER Case 10-8)
state providing FOIA information to Engineer B (BER Case 10-8) time:before Engineer B's RFQ submission (BER Case 10-8)
Firm B's past engineering design projects for the city time:before current QBS process for new public building
Extracted Actions (3)
Volitional professional decisions with intentions and ethical context

Description: City X formally established and communicated the SOQ deadline of 10:00 am on January 30 and the designated submission location (city clerk's office) to all 14 interested firms via the pre-submittal meeting, hard copy agenda, and RFQ webpage. This decision set the binding procedural framework for the entire QBS process.

Temporal Marker: Prior to January 30, at the mandatory pre-submittal meeting

Mental State: deliberate

Intended Outcome: Establish clear, uniform, and enforceable submission rules to ensure a fair and transparent QBS procurement process for all participating firms

Fulfills Obligations:
  • Public transparency — rules were published in multiple venues
  • Equal treatment — all firms received identical information
  • Protection of the public interest through a structured QBS process
  • Compliance with public procurement laws and regulations
Guided By Principles:
  • Fairness and impartiality in public procurement
  • Transparency and openness
  • Protection of the public interest
  • NSPE Code: Engineers shall act in such a manner as to uphold and enhance the honor, integrity, and dignity of the engineering profession
Required Capabilities:
Knowledge of public procurement law and QBS procedures Ability to draft and communicate clear procedural requirements Administrative coordination across city offices
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: City X sought to ensure a fair, transparent, and legally defensible QBS procurement process by establishing unambiguous rules that would apply equally to all 14 competing firms, protecting the integrity of public contracting and minimizing grounds for future protest or litigation.

Ethical Tension: Flexibility and administrative convenience vs. equal treatment and procedural fairness — the city had to balance the practical desire to attract strong submittals against the obligation to create rules that bind all parties uniformly, including the city itself.

Learning Significance: Illustrates that clearly communicated procurement rules are not merely administrative formalities but constitute binding ethical commitments to all participants; the act of publishing rules creates a duty to enforce them consistently, regardless of downstream inconvenience.

Stakes: The legitimacy of the entire QBS process is at risk; if rules are ambiguous or inconsistently communicated, the city loses its moral and legal authority to enforce them later. Taxpayer trust, vendor fairness, and public project quality all depend on this foundational step.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Publish a deadline without a designated submission location, leaving delivery logistics ambiguous
  • Allow submittals to be accepted at multiple city offices without specifying a single authoritative location
  • Set a deadline but include language permitting the city to accept late submittals at its discretion

Narrative Role: inciting_incident

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/99#Action_City_Establishes_Submission_Rules",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Publish a deadline without a designated submission location, leaving delivery logistics ambiguous",
    "Allow submittals to be accepted at multiple city offices without specifying a single authoritative location",
    "Set a deadline but include language permitting the city to accept late submittals at its discretion"
  ],
  "proeth-scenario:characterMotivation": "City X sought to ensure a fair, transparent, and legally defensible QBS procurement process by establishing unambiguous rules that would apply equally to all 14 competing firms, protecting the integrity of public contracting and minimizing grounds for future protest or litigation.",
  "proeth-scenario:consequencesIfAlternative": [
    "Ambiguity about submission location would directly enable the situation that arose with Firm B, undermining the city\u0027s ability to reject the late submittal on procedural grounds and inviting protests from other firms",
    "Accepting submittals at multiple offices would create chain-of-custody and timestamp verification problems, making it impossible to fairly adjudicate disputes about timeliness and giving no firm a clear target for compliance",
    "Discretionary acceptance language would shift the ethical burden entirely onto Engineer A later, transforming a clear procedural question into a subjective judgment call and opening the door to favoritism, bias claims, and legal challenges from competing firms"
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that clearly communicated procurement rules are not merely administrative formalities but constitute binding ethical commitments to all participants; the act of publishing rules creates a duty to enforce them consistently, regardless of downstream inconvenience.",
  "proeth-scenario:ethicalTension": "Flexibility and administrative convenience vs. equal treatment and procedural fairness \u2014 the city had to balance the practical desire to attract strong submittals against the obligation to create rules that bind all parties uniformly, including the city itself.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "The legitimacy of the entire QBS process is at risk; if rules are ambiguous or inconsistently communicated, the city loses its moral and legal authority to enforce them later. Taxpayer trust, vendor fairness, and public project quality all depend on this foundational step.",
  "proeth:description": "City X formally established and communicated the SOQ deadline of 10:00 am on January 30 and the designated submission location (city clerk\u0027s office) to all 14 interested firms via the pre-submittal meeting, hard copy agenda, and RFQ webpage. This decision set the binding procedural framework for the entire QBS process.",
  "proeth:foreseenUnintendedEffects": [
    "Firms that misread or ignore the rules will be disqualified, potentially excluding otherwise qualified candidates",
    "Strict rules may deter some firms from participating if they perceive the process as inflexible"
  ],
  "proeth:fulfillsObligation": [
    "Public transparency \u2014 rules were published in multiple venues",
    "Equal treatment \u2014 all firms received identical information",
    "Protection of the public interest through a structured QBS process",
    "Compliance with public procurement laws and regulations"
  ],
  "proeth:guidedByPrinciple": [
    "Fairness and impartiality in public procurement",
    "Transparency and openness",
    "Protection of the public interest",
    "NSPE Code: Engineers shall act in such a manner as to uphold and enhance the honor, integrity, and dignity of the engineering profession"
  ],
  "proeth:hasAgent": "City X QBS Review Team (including Engineer A as point of contact)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Inclusivity of qualified firms vs. process integrity and equal enforcement",
    "proeth:resolutionReasoning": "The city prioritized process integrity and legal defensibility by establishing unambiguous, publicly communicated rules, accepting that non-compliant submittals would be excluded regardless of firm quality"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Establish clear, uniform, and enforceable submission rules to ensure a fair and transparent QBS procurement process for all participating firms",
  "proeth:requiresCapability": [
    "Knowledge of public procurement law and QBS procedures",
    "Ability to draft and communicate clear procedural requirements",
    "Administrative coordination across city offices"
  ],
  "proeth:temporalMarker": "Prior to January 30, at the mandatory pre-submittal meeting",
  "proeth:withinCompetence": true,
  "rdfs:label": "City Establishes Submission Rules"
}

Description: Firm B chose to deliver its SOQ submittal to the city manager's office rather than the city clerk's office, and did so at 2:05 pm — more than four hours after the published 10:00 am deadline. This was a volitional decision by Firm B about when and where to deliver its submission despite having received clear instructions at the mandatory pre-submittal meeting.

Temporal Marker: January 30 at 2:05 pm

Mental State: deliberate as to the act of submitting; apparently negligent or mistaken as to compliance with the stated rules

Intended Outcome: Participate in the City X QBS process by submitting its Statement of Qualifications

Fulfills Obligations:
  • Attempted to participate in a public procurement process
Guided By Principles:
  • Adherence to public procurement rules
  • Professional diligence in meeting submission requirements
  • Fairness to competing firms who complied with the rules
Required Capabilities:
Knowledge of public procurement submission requirements Organizational and logistical planning to meet deadlines Familiarity with city office locations and procedures
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Firm B, likely motivated by strong interest in winning the contract and confidence in its qualifications, failed to comply with submission requirements — whether through internal miscommunication, logistical error, misreading of instructions, or underestimation of deadline strictness. The firm may have assumed that its reputation or the apparently minor nature of the error would lead to leniency.

Ethical Tension: Firm B's genuine interest in competing for public work and its presumably innocent administrative error stand in tension with its professional obligation to follow clearly stated procurement rules — rules it had explicitly received at a mandatory meeting. Competence and good faith do not excuse non-compliance in a regulated procurement environment.

Learning Significance: Demonstrates that even well-intentioned or high-performing firms bear full responsibility for procedural compliance in public procurement; attendance at a mandatory pre-submittal meeting creates an affirmative duty to follow the rules communicated there, and ignorance or carelessness is not a valid defense.

Stakes: Firm B risks disqualification from a significant public contract opportunity. More broadly, if Firm B's non-compliant submittal is accepted, the 13 other firms that complied on time are disadvantaged, the fairness of the process is compromised, and a precedent is set that deadlines are negotiable.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Deliver the SOQ to the correct location (city clerk's office) before the 10:00 am deadline on January 30
  • Recognize before the deadline that delivery would be late and contact Engineer A to request guidance or a brief extension
  • Deliver to the city manager's office but do so before 10:00 am, then notify Engineer A of the misdirected delivery so it could be redirected in time

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/99#Action_Firm_B_Submits_SOQ_Late",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Deliver the SOQ to the correct location (city clerk\u0027s office) before the 10:00 am deadline on January 30",
    "Recognize before the deadline that delivery would be late and contact Engineer A to request guidance or a brief extension",
    "Deliver to the city manager\u0027s office but do so before 10:00 am, then notify Engineer A of the misdirected delivery so it could be redirected in time"
  ],
  "proeth-scenario:characterMotivation": "Firm B, likely motivated by strong interest in winning the contract and confidence in its qualifications, failed to comply with submission requirements \u2014 whether through internal miscommunication, logistical error, misreading of instructions, or underestimation of deadline strictness. The firm may have assumed that its reputation or the apparently minor nature of the error would lead to leniency.",
  "proeth-scenario:consequencesIfAlternative": [
    "Full compliance would have placed Firm B in the pool of qualified submittals, allowing its strong past performance to be evaluated on the merits \u2014 the outcome Firm B presumably wanted all along",
    "Proactively communicating the delivery problem before the deadline would have demonstrated professional responsibility and potentially allowed the city to clarify options, though the city would still have been bound by its published rules and likely could not grant an individual extension without compromising fairness to other firms",
    "Early misdirected delivery with prompt notification might have created a narrow window for administrative correction before the deadline, though this would still raise questions about equal treatment and whether the city\u0027s rules permitted such redirection"
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that even well-intentioned or high-performing firms bear full responsibility for procedural compliance in public procurement; attendance at a mandatory pre-submittal meeting creates an affirmative duty to follow the rules communicated there, and ignorance or carelessness is not a valid defense.",
  "proeth-scenario:ethicalTension": "Firm B\u0027s genuine interest in competing for public work and its presumably innocent administrative error stand in tension with its professional obligation to follow clearly stated procurement rules \u2014 rules it had explicitly received at a mandatory meeting. Competence and good faith do not excuse non-compliance in a regulated procurement environment.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Firm B risks disqualification from a significant public contract opportunity. More broadly, if Firm B\u0027s non-compliant submittal is accepted, the 13 other firms that complied on time are disadvantaged, the fairness of the process is compromised, and a precedent is set that deadlines are negotiable.",
  "proeth:description": "Firm B chose to deliver its SOQ submittal to the city manager\u0027s office rather than the city clerk\u0027s office, and did so at 2:05 pm \u2014 more than four hours after the published 10:00 am deadline. This was a volitional decision by Firm B about when and where to deliver its submission despite having received clear instructions at the mandatory pre-submittal meeting.",
  "proeth:foreseenUnintendedEffects": [
    "Risk of disqualification for late delivery or incorrect submission location \u2014 apparently not foreseen or misjudged by Firm B",
    "Potential damage to Firm B\u0027s professional reputation with the city"
  ],
  "proeth:fulfillsObligation": [
    "Attempted to participate in a public procurement process"
  ],
  "proeth:guidedByPrinciple": [
    "Adherence to public procurement rules",
    "Professional diligence in meeting submission requirements",
    "Fairness to competing firms who complied with the rules"
  ],
  "proeth:hasAgent": "Firm B (unnamed representative, engineering firm)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Business interest in participating vs. strict procedural compliance",
    "proeth:resolutionReasoning": "Firm B prioritized (or failed to properly execute) submission participation over strict procedural compliance, resulting in a late and misdirected submittal \u2014 the Board found no nefarious intent but noted the non-compliance nonetheless creates process integrity risks"
  },
  "proeth:hasMentalState": "deliberate as to the act of submitting; apparently negligent or mistaken as to compliance with the stated rules",
  "proeth:intendedOutcome": "Participate in the City X QBS process by submitting its Statement of Qualifications",
  "proeth:requiresCapability": [
    "Knowledge of public procurement submission requirements",
    "Organizational and logistical planning to meet deadlines",
    "Familiarity with city office locations and procedures"
  ],
  "proeth:temporalMarker": "January 30 at 2:05 pm",
  "proeth:violatesObligation": [
    "Compliance with published procurement rules (deadline and location)",
    "Professional responsibility to follow established procedures in public procurement",
    "NSPE Code: Engineers shall not attempt to obtain employment by unethical means \u2014 while not nefarious, non-compliance with rules creates an unfair advantage if accepted"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Firm B Submits SOQ Late"
}

Description: Upon being intercepted with Firm B's late and misdirected envelope on the afternoon of January 30, Engineer A faced the central ethical decision of whether to accept or reject Firm B's SOQ submittal for consideration in the QBS process. The NSPE Board concluded that Engineer A must reject the submittal and strictly adhere to the published procurement rules, despite Firm B's strong past performance and the apparently innocent nature of the error.

Temporal Marker: Afternoon of January 30, upon returning to his office

Mental State: deliberate — a conscious choice point requiring professional and ethical judgment

Intended Outcome: Uphold the integrity of the public QBS procurement process by strictly enforcing submission rules, thereby protecting the process from legal challenge and maintaining public trust

Fulfills Obligations:
  • Public duty to maintain integrity of the procurement process
  • Equal treatment of all firms — enforcing the same rules regardless of prior relationship or past performance
  • Compliance with public procurement laws and city policies
  • NSPE Code: Engineers shall act in such a manner as to uphold and enhance the honor, integrity, and dignity of the engineering profession
  • NSPE Code: Engineers shall be objective and truthful in professional reports and public statements
  • Protection of the public interest in receiving fair and transparent procurement
Guided By Principles:
  • Process integrity over merit-based accommodation
  • Equal and impartial enforcement of procurement rules
  • Public trust in government procurement processes
  • Avoidance of the appearance of impropriety
  • NSPE Code: Engineers shall hold paramount the safety, health, and welfare of the public
  • Zero-tolerance posture on rule violations to prevent climate of non-adherence
Required Capabilities:
Knowledge of public procurement law and QBS procedures Ability to apply ethical reasoning to competing professional obligations Impartial judgment free from personal relationships or past performance bias Understanding of legal risks associated with procurement rule violations Familiarity with NSPE Code of Ethics and BER precedent cases
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A, as the city's QBS point of contact and a licensed professional engineer, was motivated by a desire to do right by the city, the procurement process, and potentially by Firm B — whose past performance he may have been aware of. However, his professional and ethical obligations under NSPE guidance required him to subordinate personal sympathy or administrative convenience to the integrity of the public procurement process.

Ethical Tension: Compassion and pragmatism (Firm B's error appears innocent, its qualifications may be strong, and rejection means losing a potentially excellent firm) vs. strict procedural fairness and equal treatment (13 other firms complied with the same rules; accepting the late submittal rewards non-compliance and undermines the rule of law in public contracting). Engineer A also faces tension between his personal discretion as an individual and his role as a steward of a public process that belongs to all stakeholders.

Learning Significance: This is the core ethical teaching moment of the case: public procurement rules exist precisely to remove individual discretion from the selection process, and an engineer acting in a public-trust role must enforce those rules even when doing so feels harsh. The NSPE conclusion reinforces that fairness to the many compliant firms outweighs sympathy for the one non-compliant firm, and that consistent enforcement protects the engineer, the city, and the profession.

Stakes: Engineer A's professional reputation and potential liability are at risk if he makes the wrong call. The city faces legal exposure to protests from the 13 compliant firms if it accepts the late submittal. The integrity of the QBS process — and by extension public trust in government procurement — hangs on this single decision. If Engineer A accepts, he may also be setting a precedent that invites future non-compliance.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Accept Firm B's submittal on the grounds that the error was innocent, the firm is highly qualified, and the city's interests are best served by considering the strongest possible pool of candidates
  • Escalate the decision to city management or legal counsel rather than deciding unilaterally, deferring the ethical burden to a higher authority
  • Accept the submittal conditionally, flagging it for the evaluation committee to decide whether to consider it, while notifying all other firms of the situation to allow them to protest if desired

Narrative Role: climax

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/99#Action_Engineer_A_Decides_on_Late_Submittal",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Accept Firm B\u0027s submittal on the grounds that the error was innocent, the firm is highly qualified, and the city\u0027s interests are best served by considering the strongest possible pool of candidates",
    "Escalate the decision to city management or legal counsel rather than deciding unilaterally, deferring the ethical burden to a higher authority",
    "Accept the submittal conditionally, flagging it for the evaluation committee to decide whether to consider it, while notifying all other firms of the situation to allow them to protest if desired"
  ],
  "proeth-scenario:characterMotivation": "Engineer A, as the city\u0027s QBS point of contact and a licensed professional engineer, was motivated by a desire to do right by the city, the procurement process, and potentially by Firm B \u2014 whose past performance he may have been aware of. However, his professional and ethical obligations under NSPE guidance required him to subordinate personal sympathy or administrative convenience to the integrity of the public procurement process.",
  "proeth-scenario:consequencesIfAlternative": [
    "Accepting the submittal would expose the city to formal protests from any of the 13 compliant firms, potentially invalidating the entire procurement process, triggering legal costs, and delaying the public project; it would also signal to the market that deadlines in City X procurements are not strictly enforced, degrading future process integrity",
    "Escalating to management or legal counsel is procedurally defensible and may be appropriate given the stakes, but does not eliminate the ethical obligation \u2014 it merely distributes it; the NSPE analysis suggests the correct answer is clear enough that Engineer A should be prepared to make and defend the rejection decision, and escalation should not be used as a mechanism to avoid an uncomfortable but correct choice",
    "Conditional acceptance with notification is the most dangerous alternative because it creates the appearance of fairness while actually compounding the procedural violation \u2014 it introduces a new, unpublished review mechanism mid-process, potentially exposes confidential procurement information, and still results in one firm receiving treatment unavailable to others, maximizing legal and ethical risk for the city"
  ],
  "proeth-scenario:decisionSignificance": "This is the core ethical teaching moment of the case: public procurement rules exist precisely to remove individual discretion from the selection process, and an engineer acting in a public-trust role must enforce those rules even when doing so feels harsh. The NSPE conclusion reinforces that fairness to the many compliant firms outweighs sympathy for the one non-compliant firm, and that consistent enforcement protects the engineer, the city, and the profession.",
  "proeth-scenario:ethicalTension": "Compassion and pragmatism (Firm B\u0027s error appears innocent, its qualifications may be strong, and rejection means losing a potentially excellent firm) vs. strict procedural fairness and equal treatment (13 other firms complied with the same rules; accepting the late submittal rewards non-compliance and undermines the rule of law in public contracting). Engineer A also faces tension between his personal discretion as an individual and his role as a steward of a public process that belongs to all stakeholders.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Engineer A\u0027s professional reputation and potential liability are at risk if he makes the wrong call. The city faces legal exposure to protests from the 13 compliant firms if it accepts the late submittal. The integrity of the QBS process \u2014 and by extension public trust in government procurement \u2014 hangs on this single decision. If Engineer A accepts, he may also be setting a precedent that invites future non-compliance.",
  "proeth:description": "Upon being intercepted with Firm B\u0027s late and misdirected envelope on the afternoon of January 30, Engineer A faced the central ethical decision of whether to accept or reject Firm B\u0027s SOQ submittal for consideration in the QBS process. The NSPE Board concluded that Engineer A must reject the submittal and strictly adhere to the published procurement rules, despite Firm B\u0027s strong past performance and the apparently innocent nature of the error.",
  "proeth:foreseenUnintendedEffects": [
    "Firm B, a previously high-performing firm, is excluded from consideration for this project",
    "The city may lose access to a qualified and experienced engineering firm for this project",
    "Firm B may suffer reputational or business harm from disqualification"
  ],
  "proeth:fulfillsObligation": [
    "Public duty to maintain integrity of the procurement process",
    "Equal treatment of all firms \u2014 enforcing the same rules regardless of prior relationship or past performance",
    "Compliance with public procurement laws and city policies",
    "NSPE Code: Engineers shall act in such a manner as to uphold and enhance the honor, integrity, and dignity of the engineering profession",
    "NSPE Code: Engineers shall be objective and truthful in professional reports and public statements",
    "Protection of the public interest in receiving fair and transparent procurement"
  ],
  "proeth:guidedByPrinciple": [
    "Process integrity over merit-based accommodation",
    "Equal and impartial enforcement of procurement rules",
    "Public trust in government procurement processes",
    "Avoidance of the appearance of impropriety",
    "NSPE Code: Engineers shall hold paramount the safety, health, and welfare of the public",
    "Zero-tolerance posture on rule violations to prevent climate of non-adherence"
  ],
  "proeth:hasAgent": "Engineer A (public agency engineer and QBS point of contact, City X)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Merit-based outcome and firm accommodation vs. strict process integrity and equal enforcement",
    "proeth:resolutionReasoning": "The NSPE Board concluded that Engineer A must reject the submittal because allowing exceptions \u2014 even for innocent errors by high-performing firms \u2014 would undermine the integrity of the procurement process, expose the city to legal challenge, create a climate of non-adherence, and reflect poorly on the city and the engineering profession; process integrity was deemed paramount over merit-based accommodation"
  },
  "proeth:hasMentalState": "deliberate \u2014 a conscious choice point requiring professional and ethical judgment",
  "proeth:intendedOutcome": "Uphold the integrity of the public QBS procurement process by strictly enforcing submission rules, thereby protecting the process from legal challenge and maintaining public trust",
  "proeth:requiresCapability": [
    "Knowledge of public procurement law and QBS procedures",
    "Ability to apply ethical reasoning to competing professional obligations",
    "Impartial judgment free from personal relationships or past performance bias",
    "Understanding of legal risks associated with procurement rule violations",
    "Familiarity with NSPE Code of Ethics and BER precedent cases"
  ],
  "proeth:temporalMarker": "Afternoon of January 30, upon returning to his office",
  "proeth:violatesObligation": [
    "If submittal were accepted: equal treatment of all competing firms who complied with the rules",
    "If submittal were accepted: compliance with published procurement rules and applicable law",
    "If submittal were accepted: avoidance of the appearance of favoritism or impropriety"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Engineer A Decides on Late Submittal"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changes

Description: Firm B's SOQ submittal arrived at the city manager's office — not the specified city clerk's office — at 2:05 pm on January 30, more than four hours after the published deadline and at an incorrect location.

Temporal Marker: January 30, 2:05 pm

Activates Constraints:
  • Wrong_Office_Submission_Constraint
  • Deadline_Enforcement_Constraint
  • Procurement_Integrity_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: City manager's office staff may be uncertain or confused about what to do with a misdirected procurement submittal; Firm B's representatives may be hoping the submittal will be accepted despite its deficiencies; no emotional impact yet on Engineer A who has not discovered it

Stakeholder Consequences:
  • firm_b: Has compounded its deadline failure with a location failure, weakening any argument for leniency; faces near-certain disqualification
  • city_manager_office_staff: Placed in an awkward position of holding a document that should not have been delivered to them; may feel uncertain about proper handling
  • engineer_a: Will soon face the core ethical dilemma of the case upon discovering this submittal
  • compliant_firms: Their fair treatment depends entirely on this submittal being rejected; acceptance would retroactively penalize their compliance
  • public: Public trust in procurement integrity is implicated by how this non-compliant submittal is handled

Learning Moment: A dual violation — wrong time AND wrong place — is significant because it eliminates ambiguity. Unlike a submittal that is late but correctly addressed, or on-time but misdirected, this case presents compounded non-compliance that makes the ethical analysis clearer. Students should recognize how the compounding of rule violations affects the strength of enforcement obligations.

Ethical Implications: Exposes the tension between compassion (Firm B may have made an honest administrative error) and fairness to compliant competitors. Also raises questions about institutional responsibility: does the city bear any obligation to redirect misdirected submittals, or does that create an unfair advantage? Highlights how administrative errors have real competitive consequences in public procurement.

Discussion Prompts:
  • Does the fact that Firm B committed two simultaneous violations (late AND wrong office) change the ethical calculus compared to a single violation? Why or why not?
  • What obligation, if any, do city manager's office staff have upon receiving this misdirected submittal? Should they have immediately returned it to Firm B or notified Engineer A?
  • If Firm B's submittal had arrived at the correct office (city clerk) but still four hours late, would Engineer A's ethical obligation be different? What about if it arrived on time at the wrong office?
Crisis / Turning Point Tension: high Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/99#Event_Submittal_Arrives_Wrong_Office",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "Does the fact that Firm B committed two simultaneous violations (late AND wrong office) change the ethical calculus compared to a single violation? Why or why not?",
    "What obligation, if any, do city manager\u0027s office staff have upon receiving this misdirected submittal? Should they have immediately returned it to Firm B or notified Engineer A?",
    "If Firm B\u0027s submittal had arrived at the correct office (city clerk) but still four hours late, would Engineer A\u0027s ethical obligation be different? What about if it arrived on time at the wrong office?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "City manager\u0027s office staff may be uncertain or confused about what to do with a misdirected procurement submittal; Firm B\u0027s representatives may be hoping the submittal will be accepted despite its deficiencies; no emotional impact yet on Engineer A who has not discovered it",
  "proeth-scenario:ethicalImplications": "Exposes the tension between compassion (Firm B may have made an honest administrative error) and fairness to compliant competitors. Also raises questions about institutional responsibility: does the city bear any obligation to redirect misdirected submittals, or does that create an unfair advantage? Highlights how administrative errors have real competitive consequences in public procurement.",
  "proeth-scenario:learningMoment": "A dual violation \u2014 wrong time AND wrong place \u2014 is significant because it eliminates ambiguity. Unlike a submittal that is late but correctly addressed, or on-time but misdirected, this case presents compounded non-compliance that makes the ethical analysis clearer. Students should recognize how the compounding of rule violations affects the strength of enforcement obligations.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "city_manager_office_staff": "Placed in an awkward position of holding a document that should not have been delivered to them; may feel uncertain about proper handling",
    "compliant_firms": "Their fair treatment depends entirely on this submittal being rejected; acceptance would retroactively penalize their compliance",
    "engineer_a": "Will soon face the core ethical dilemma of the case upon discovering this submittal",
    "firm_b": "Has compounded its deadline failure with a location failure, weakening any argument for leniency; faces near-certain disqualification",
    "public": "Public trust in procurement integrity is implicated by how this non-compliant submittal is handled"
  },
  "proeth:activatesConstraint": [
    "Wrong_Office_Submission_Constraint",
    "Deadline_Enforcement_Constraint",
    "Procurement_Integrity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/99#Action_Firm_B_Submits_SOQ_Late",
  "proeth:causesStateChange": "A physical non-compliant document now exists within City X\u0027s administrative system; the procurement process has been complicated by a dual violation (late delivery AND wrong office); the submittal\u0027s presence creates pressure on city staff to make a decision about its disposition",
  "proeth:createsObligation": [
    "City_Staff_Must_Flag_Non-Compliant_Submittal",
    "Engineer_A_Must_Be_Notified_Upon_Discovery",
    "Submittal_Must_Not_Be_Processed_As_Compliant"
  ],
  "proeth:description": "Firm B\u0027s SOQ submittal arrived at the city manager\u0027s office \u2014 not the specified city clerk\u0027s office \u2014 at 2:05 pm on January 30, more than four hours after the published deadline and at an incorrect location.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "January 30, 2:05 pm",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Submittal Arrives Wrong Office"
}

Description: Upon returning to his office that afternoon, Engineer A discovered Firm B's late and misdirected SOQ submittal, becoming aware of both violations simultaneously and triggering his obligation to make a disposition decision.

Temporal Marker: January 30, afternoon (after 2:05 pm, exact time unspecified)

Activates Constraints:
  • Engineer_A_Decision_Authority_Constraint
  • Procurement_Integrity_Constraint
  • Equal_Treatment_Of_Firms_Constraint
  • Professional_Ethics_Constraint
  • Public_Employee_Duty_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A likely experiences surprise, discomfort, and ethical tension upon discovering the submittal; he may feel sympathy for Firm B while also recognizing the clear rule violation; the discovery creates an immediate sense of professional responsibility and perhaps anxiety about making the right call; there may also be institutional pressure to be accommodating

Stakeholder Consequences:
  • engineer_a: Now personally responsible for a high-stakes procurement decision; his professional integrity and adherence to engineering ethics codes are directly implicated; faces potential criticism regardless of decision
  • firm_b: Their fate in this procurement now rests entirely with Engineer A's decision; they may be unaware that their submittal has been discovered
  • compliant_firms: Their fair treatment is now dependent on Engineer A's decision; they are unaware but have a stake in the outcome
  • city_x: The integrity of its public procurement process depends on Engineer A making the ethically and legally correct decision
  • public: Taxpayer interests in fair, competitive public procurement are at stake

Learning Moment: Discovery of a problem does not create the ethical obligation — the obligation existed the moment the deadline passed. However, discovery activates the decision-maker's personal professional responsibility. Students should understand that Engineer A's ethical duty is not to decide whether to accept or reject based on sympathy or convenience, but to apply the rules that were established to protect all parties equally. The moment of discovery is the moment of ethical reckoning.

Ethical Implications: This event is the ethical fulcrum of the entire case. It reveals the tension between human compassion (an honest mistake deserves a second chance) and systemic fairness (rules must apply equally to protect all competitors). It also implicates Engineer A's dual role as a public servant (obligated to protect procurement integrity) and a professional engineer (bound by NSPE Code of Ethics to act with fairness and in the public interest). The discovery moment tests whether professional ethics are principles or merely preferences.

Discussion Prompts:
  • At the moment Engineer A discovers the submittal, what emotions and pressures might influence his thinking, and how should a professional engineer manage those influences?
  • Does Engineer A have any obligation to investigate why Firm B was late or misdirected before making his decision, or is the fact of non-compliance sufficient to determine the outcome?
  • If Engineer A were personally acquainted with principals at Firm B, how would that relationship affect his ethical obligations, and what should he do to manage that conflict?
Crisis / Turning Point Tension: high Pacing: crisis
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/99#Event_Engineer_A_Discovers_Submittal",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "At the moment Engineer A discovers the submittal, what emotions and pressures might influence his thinking, and how should a professional engineer manage those influences?",
    "Does Engineer A have any obligation to investigate why Firm B was late or misdirected before making his decision, or is the fact of non-compliance sufficient to determine the outcome?",
    "If Engineer A were personally acquainted with principals at Firm B, how would that relationship affect his ethical obligations, and what should he do to manage that conflict?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences surprise, discomfort, and ethical tension upon discovering the submittal; he may feel sympathy for Firm B while also recognizing the clear rule violation; the discovery creates an immediate sense of professional responsibility and perhaps anxiety about making the right call; there may also be institutional pressure to be accommodating",
  "proeth-scenario:ethicalImplications": "This event is the ethical fulcrum of the entire case. It reveals the tension between human compassion (an honest mistake deserves a second chance) and systemic fairness (rules must apply equally to protect all competitors). It also implicates Engineer A\u0027s dual role as a public servant (obligated to protect procurement integrity) and a professional engineer (bound by NSPE Code of Ethics to act with fairness and in the public interest). The discovery moment tests whether professional ethics are principles or merely preferences.",
  "proeth-scenario:learningMoment": "Discovery of a problem does not create the ethical obligation \u2014 the obligation existed the moment the deadline passed. However, discovery activates the decision-maker\u0027s personal professional responsibility. Students should understand that Engineer A\u0027s ethical duty is not to decide whether to accept or reject based on sympathy or convenience, but to apply the rules that were established to protect all parties equally. The moment of discovery is the moment of ethical reckoning.",
  "proeth-scenario:narrativePacing": "crisis",
  "proeth-scenario:stakeholderConsequences": {
    "city_x": "The integrity of its public procurement process depends on Engineer A making the ethically and legally correct decision",
    "compliant_firms": "Their fair treatment is now dependent on Engineer A\u0027s decision; they are unaware but have a stake in the outcome",
    "engineer_a": "Now personally responsible for a high-stakes procurement decision; his professional integrity and adherence to engineering ethics codes are directly implicated; faces potential criticism regardless of decision",
    "firm_b": "Their fate in this procurement now rests entirely with Engineer A\u0027s decision; they may be unaware that their submittal has been discovered",
    "public": "Taxpayer interests in fair, competitive public procurement are at stake"
  },
  "proeth:activatesConstraint": [
    "Engineer_A_Decision_Authority_Constraint",
    "Procurement_Integrity_Constraint",
    "Equal_Treatment_Of_Firms_Constraint",
    "Professional_Ethics_Constraint",
    "Public_Employee_Duty_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/99#Action_Firm_B_Submits_SOQ_Late",
  "proeth:causesStateChange": "Engineer A transitions from unaware to fully informed of the procurement violation; the ethical decision point is now active; Engineer A bears personal professional responsibility for the disposition of the non-compliant submittal",
  "proeth:createsObligation": [
    "Engineer_A_Must_Evaluate_Compliance_Status",
    "Engineer_A_Must_Apply_Procurement_Rules_Uniformly",
    "Engineer_A_Must_Not_Accept_Non-Compliant_Submittal",
    "Engineer_A_Must_Notify_Firm_B_Of_Rejection",
    "Engineer_A_Must_Document_Disposition_Decision"
  ],
  "proeth:description": "Upon returning to his office that afternoon, Engineer A discovered Firm B\u0027s late and misdirected SOQ submittal, becoming aware of both violations simultaneously and triggering his obligation to make a disposition decision.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "January 30, afternoon (after 2:05 pm, exact time unspecified)",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Engineer A Discovers Submittal"
}

Description: The existence of Firm B's non-compliant submittal in the procurement system created a state of uncertainty in the QBS evaluation process, as the disposition of the submittal had to be resolved before fair evaluation of compliant firms could proceed.

Temporal Marker: January 30, afternoon onward (following Engineer A's discovery)

Activates Constraints:
  • Procurement_Process_Integrity_Constraint
  • Equal_Treatment_Of_Firms_Constraint
  • Timely_Procurement_Resolution_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A may feel time pressure and institutional stress; compliant firms are unaware but would feel aggrieved if they knew; city administration may feel reputational risk from the procurement complication

Stakeholder Consequences:
  • engineer_a: Bears responsibility for resolving the situation promptly and correctly to allow the procurement to proceed
  • compliant_firms: Experience potential delay in evaluation process through no fault of their own
  • firm_b: Awaits notification of disposition; outcome will determine whether they continue in the process
  • city_x: Procurement timeline potentially affected; institutional reputation for fair procurement at risk
  • public: Delay in procurement process for public building affects timely delivery of public infrastructure

Learning Moment: Procurement violations do not only affect the violating firm — they create ripple effects that impact the entire process, all compliant competitors, and the public project timeline. Students should understand that the consequences of non-compliance extend well beyond the individual firm that violated the rules.

Ethical Implications: Illustrates how one firm's non-compliance creates externalities that affect innocent parties (compliant firms, the public). Raises questions about institutional design: should procurement systems have automatic rejection mechanisms at the point of receipt to prevent this situation from arising? Also highlights Engineer A's duty not just to make the right decision, but to make it promptly and transparently to protect the broader process.

Discussion Prompts:
  • What systemic safeguards could City X implement to prevent non-compliant submittals from entering the procurement system in the first place (e.g., at the point of receipt)?
  • How does the existence of this unresolved submittal affect the fairness of the evaluation process for compliant firms, even if Engineer A ultimately rejects it?
  • What documentation should Engineer A create to protect City X's procurement integrity regardless of which decision he makes?
Tension: medium Pacing: aftermath
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/99#Event_QBS_Evaluation_Period_Affected",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What systemic safeguards could City X implement to prevent non-compliant submittals from entering the procurement system in the first place (e.g., at the point of receipt)?",
    "How does the existence of this unresolved submittal affect the fairness of the evaluation process for compliant firms, even if Engineer A ultimately rejects it?",
    "What documentation should Engineer A create to protect City X\u0027s procurement integrity regardless of which decision he makes?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A may feel time pressure and institutional stress; compliant firms are unaware but would feel aggrieved if they knew; city administration may feel reputational risk from the procurement complication",
  "proeth-scenario:ethicalImplications": "Illustrates how one firm\u0027s non-compliance creates externalities that affect innocent parties (compliant firms, the public). Raises questions about institutional design: should procurement systems have automatic rejection mechanisms at the point of receipt to prevent this situation from arising? Also highlights Engineer A\u0027s duty not just to make the right decision, but to make it promptly and transparently to protect the broader process.",
  "proeth-scenario:learningMoment": "Procurement violations do not only affect the violating firm \u2014 they create ripple effects that impact the entire process, all compliant competitors, and the public project timeline. Students should understand that the consequences of non-compliance extend well beyond the individual firm that violated the rules.",
  "proeth-scenario:narrativePacing": "aftermath",
  "proeth-scenario:stakeholderConsequences": {
    "city_x": "Procurement timeline potentially affected; institutional reputation for fair procurement at risk",
    "compliant_firms": "Experience potential delay in evaluation process through no fault of their own",
    "engineer_a": "Bears responsibility for resolving the situation promptly and correctly to allow the procurement to proceed",
    "firm_b": "Awaits notification of disposition; outcome will determine whether they continue in the process",
    "public": "Delay in procurement process for public building affects timely delivery of public infrastructure"
  },
  "proeth:activatesConstraint": [
    "Procurement_Process_Integrity_Constraint",
    "Equal_Treatment_Of_Firms_Constraint",
    "Timely_Procurement_Resolution_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/99#Action_Firm_B_Submits_SOQ_Late",
  "proeth:causesStateChange": "The QBS evaluation process is in a suspended or compromised state until Engineer A resolves the disposition of Firm B\u0027s submittal; the integrity of the entire evaluation depends on this resolution",
  "proeth:createsObligation": [
    "Engineer_A_Must_Resolve_Submittal_Disposition_Before_Evaluation",
    "City_Must_Document_Disposition_Decision",
    "City_Must_Notify_Firm_B_Of_Outcome"
  ],
  "proeth:description": "The existence of Firm B\u0027s non-compliant submittal in the procurement system created a state of uncertainty in the QBS evaluation process, as the disposition of the submittal had to be resolved before fair evaluation of compliant firms could proceed.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "January 30, afternoon onward (following Engineer A\u0027s discovery)",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "QBS Evaluation Period Affected"
}

Description: A mandatory pre-submittal meeting was conducted by City X, attended by 14 firms including Firm B, during which submission rules, deadlines, and office location requirements were formally distributed to all participants.

Temporal Marker: Prior to January 30 (exact date unspecified, before SOQ deadline)

Activates Constraints:
  • Procurement_Rules_Binding_Constraint
  • Equal_Treatment_Of_Firms_Constraint
  • Public_Notice_Requirement_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Routine and procedural for all parties; no immediate emotional charge, but this moment carries latent legal and ethical weight that will matter later when Firm B's late submittal is discovered

Stakeholder Consequences:
  • firm_b: Now formally bound by all stated rules; cannot later claim ignorance of deadline or correct office location
  • other_13_firms: Placed on equal footing with Firm B regarding rule knowledge; sets fairness baseline
  • city_x: Fulfilled its public notice obligation; created evidentiary record of rule dissemination
  • engineer_a: As point of contact, becomes responsible for enforcing the rules communicated at this meeting
  • public: Protected by transparent, equally-applied procurement process

Learning Moment: Mandatory pre-submittal meetings serve a critical legal and ethical function: they create binding constructive notice that underpins fair and enforceable procurement. Attendance transforms procedural rules into enforceable obligations. Students should understand that procurement fairness begins with equal access to information.

Ethical Implications: Establishes the foundational fairness principle: all competing firms receive identical information simultaneously, which creates the ethical basis for strict rule enforcement later. Reveals how procedural justice (equal treatment) is built into procurement design and why deviations undermine the entire competitive process.

Discussion Prompts:
  • Why does mandatory attendance at a pre-submittal meeting matter legally and ethically compared to simply posting rules online?
  • If a firm sends a junior employee to a mandatory meeting who fails to relay the deadline correctly internally, does that change the firm's ethical or legal obligation to comply?
  • How does the equal distribution of rules at this meeting affect Engineer A's later obligation to treat Firm B's late submittal?
Tension: low Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/99#Event_Pre-Submittal_Meeting_Held",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Why does mandatory attendance at a pre-submittal meeting matter legally and ethically compared to simply posting rules online?",
    "If a firm sends a junior employee to a mandatory meeting who fails to relay the deadline correctly internally, does that change the firm\u0027s ethical or legal obligation to comply?",
    "How does the equal distribution of rules at this meeting affect Engineer A\u0027s later obligation to treat Firm B\u0027s late submittal?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Routine and procedural for all parties; no immediate emotional charge, but this moment carries latent legal and ethical weight that will matter later when Firm B\u0027s late submittal is discovered",
  "proeth-scenario:ethicalImplications": "Establishes the foundational fairness principle: all competing firms receive identical information simultaneously, which creates the ethical basis for strict rule enforcement later. Reveals how procedural justice (equal treatment) is built into procurement design and why deviations undermine the entire competitive process.",
  "proeth-scenario:learningMoment": "Mandatory pre-submittal meetings serve a critical legal and ethical function: they create binding constructive notice that underpins fair and enforceable procurement. Attendance transforms procedural rules into enforceable obligations. Students should understand that procurement fairness begins with equal access to information.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "city_x": "Fulfilled its public notice obligation; created evidentiary record of rule dissemination",
    "engineer_a": "As point of contact, becomes responsible for enforcing the rules communicated at this meeting",
    "firm_b": "Now formally bound by all stated rules; cannot later claim ignorance of deadline or correct office location",
    "other_13_firms": "Placed on equal footing with Firm B regarding rule knowledge; sets fairness baseline",
    "public": "Protected by transparent, equally-applied procurement process"
  },
  "proeth:activatesConstraint": [
    "Procurement_Rules_Binding_Constraint",
    "Equal_Treatment_Of_Firms_Constraint",
    "Public_Notice_Requirement_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/99#Action_City_Establishes_Submission_Rules",
  "proeth:causesStateChange": "All 14 attending firms are formally on notice of submission requirements; ignorance of rules is no longer a valid defense for any attendee firm including Firm B",
  "proeth:createsObligation": [
    "All_Firms_Must_Comply_With_Stated_Rules",
    "City_Must_Enforce_Rules_Uniformly",
    "Firms_Accountable_For_Deadline_Knowledge"
  ],
  "proeth:description": "A mandatory pre-submittal meeting was conducted by City X, attended by 14 firms including Firm B, during which submission rules, deadlines, and office location requirements were formally distributed to all participants.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Prior to January 30 (exact date unspecified, before SOQ deadline)",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Pre-Submittal Meeting Held"
}

Description: The published 10:00 am January 30 deadline for SOQ submittals to the city clerk's office passed without Firm B having delivered its submittal to the correct location, triggering automatic disqualification conditions under procurement rules.

Temporal Marker: January 30, 10:00 am

Activates Constraints:
  • Deadline_Enforcement_Constraint
  • Equal_Treatment_Of_Firms_Constraint
  • Procurement_Integrity_Constraint
  • No_Post_Deadline_Acceptance_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Unknown to Engineer A and City X at this moment (they have not yet discovered the late submittal); Firm B's representatives may be aware of their failure and experiencing anxiety; compliant firms are unaware but their interests are now legally protected

Stakeholder Consequences:
  • firm_b: Has objectively failed to meet a binding procurement condition; faces potential disqualification regardless of submittal quality
  • compliant_firms: Their timely compliance is now a competitive advantage protected by procurement rules; accepting Firm B's late submittal would harm them
  • city_x: Now has a legal and ethical obligation to enforce the deadline uniformly to protect procurement integrity
  • engineer_a: Will later face the decision of whether to honor this automatic trigger or override it — the central ethical dilemma of the case
  • public: The integrity of the public procurement process is at stake; taxpayer interests depend on fair competition

Learning Moment: Deadlines in public procurement are not merely administrative courtesies — they are legally and ethically binding conditions that trigger automatic eligibility consequences the moment they pass. Students should understand that the ethical weight of a deadline is established before any human decision-maker becomes aware of non-compliance.

Ethical Implications: Reveals the tension between rule-based ethics (deontological: rules must be followed regardless of outcome) and consequentialist reasoning (what if accepting the late submittal produces a better building?). Also highlights how procedural fairness protects parties (compliant firms) who are not even present in the immediate decision context.

Discussion Prompts:
  • If no one at City X is aware that Firm B missed the deadline at 10:00 am, does the ethical obligation to enforce the deadline still exist at that moment? Why or why not?
  • Should procurement deadlines ever be treated as flexible if the late submittal is of exceptionally high quality? What values conflict in that scenario?
  • How does the automatic nature of this trigger — requiring no human decision — affect Engineer A's later ethical obligations when he discovers the late submittal?
Tension: medium Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "proeth-scenario": "http://proethica.org/ontology/scenario#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "time": "http://www.w3.org/2006/time#"
  },
  "@id": "http://proethica.org/cases/99#Event_Deadline_Passes_Unmet",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "If no one at City X is aware that Firm B missed the deadline at 10:00 am, does the ethical obligation to enforce the deadline still exist at that moment? Why or why not?",
    "Should procurement deadlines ever be treated as flexible if the late submittal is of exceptionally high quality? What values conflict in that scenario?",
    "How does the automatic nature of this trigger \u2014 requiring no human decision \u2014 affect Engineer A\u0027s later ethical obligations when he discovers the late submittal?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Unknown to Engineer A and City X at this moment (they have not yet discovered the late submittal); Firm B\u0027s representatives may be aware of their failure and experiencing anxiety; compliant firms are unaware but their interests are now legally protected",
  "proeth-scenario:ethicalImplications": "Reveals the tension between rule-based ethics (deontological: rules must be followed regardless of outcome) and consequentialist reasoning (what if accepting the late submittal produces a better building?). Also highlights how procedural fairness protects parties (compliant firms) who are not even present in the immediate decision context.",
  "proeth-scenario:learningMoment": "Deadlines in public procurement are not merely administrative courtesies \u2014 they are legally and ethically binding conditions that trigger automatic eligibility consequences the moment they pass. Students should understand that the ethical weight of a deadline is established before any human decision-maker becomes aware of non-compliance.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "city_x": "Now has a legal and ethical obligation to enforce the deadline uniformly to protect procurement integrity",
    "compliant_firms": "Their timely compliance is now a competitive advantage protected by procurement rules; accepting Firm B\u0027s late submittal would harm them",
    "engineer_a": "Will later face the decision of whether to honor this automatic trigger or override it \u2014 the central ethical dilemma of the case",
    "firm_b": "Has objectively failed to meet a binding procurement condition; faces potential disqualification regardless of submittal quality",
    "public": "The integrity of the public procurement process is at stake; taxpayer interests depend on fair competition"
  },
  "proeth:activatesConstraint": [
    "Deadline_Enforcement_Constraint",
    "Equal_Treatment_Of_Firms_Constraint",
    "Procurement_Integrity_Constraint",
    "No_Post_Deadline_Acceptance_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/99#Action_City_Establishes_Submission_Rules",
  "proeth:causesStateChange": "Firm B transitions from \u0027eligible competitor\u0027 to \u0027non-compliant submitter\u0027 at the moment the deadline passes; the legal and ethical window for valid submission closes; all other compliant firms\u0027 competitive positions are now protected",
  "proeth:createsObligation": [
    "City_Must_Not_Accept_Late_Submittals",
    "Engineer_A_Must_Enforce_Deadline_Uniformly",
    "Compliant_Firms_Entitled_To_Fair_Evaluation"
  ],
  "proeth:description": "The published 10:00 am January 30 deadline for SOQ submittals to the city clerk\u0027s office passed without Firm B having delivered its submittal to the correct location, triggering automatic disqualification conditions under procurement rules.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "automatic_trigger",
  "proeth:temporalMarker": "January 30, 10:00 am",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Deadline Passes Unmet"
}
Causal Chains (4)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: City X formally established and communicated the SOQ deadline of 10:00 am on January 30 and the designated submission location (city clerk's office), creating the compliance standard against which Firm B's submittal was measured

Necessary Factors (NESS):
  • Formal establishment of a specific deadline (10:00 am, January 30)
  • Designation of a specific submission location (city clerk's office)
  • Communication of these rules to all participating firms at pre-submittal meeting
  • Firm B's failure to comply with either requirement
Sufficient Factors:
  • Combination of clearly published rules + Firm B's non-compliant delivery behavior = deadline passing without a valid compliant submittal from Firm B
Counterfactual Test: Without the formally established rules, no 'deadline' could have passed unmet; alternatively, had Firm B complied, the deadline would have passed with a valid submittal on record
Responsibility Attribution:

Agent: City X (municipal authority)
Type: indirect
Within Agent Control: Yes

Causal Sequence:
  1. City Establishes Submission Rules
    City X formally sets 10:00 am January 30 deadline and city clerk's office as the required submission location
  2. Pre-Submittal Meeting Held
    Rules are communicated to all 14 firms including Firm B at mandatory pre-submittal meeting, establishing constructive knowledge
  3. Firm B Submits SOQ Late
    Firm B delivers its SOQ to the wrong office (city manager's) after the 10:00 am deadline, violating both requirements
  4. Deadline Passes Unmet
    The 10:00 am deadline passes without a compliant submittal from Firm B at the city clerk's office
  5. QBS Evaluation Period Affected
    Non-compliant submittal creates uncertainty and ethical dilemma in the procurement process
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/99#CausalChain_f861f5b9",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "City X formally established and communicated the SOQ deadline of 10:00 am on January 30 and the designated submission location (city clerk\u0027s office), creating the compliance standard against which Firm B\u0027s submittal was measured",
  "proeth:causalSequence": [
    {
      "proeth:description": "City X formally sets 10:00 am January 30 deadline and city clerk\u0027s office as the required submission location",
      "proeth:element": "City Establishes Submission Rules",
      "proeth:step": 1
    },
    {
      "proeth:description": "Rules are communicated to all 14 firms including Firm B at mandatory pre-submittal meeting, establishing constructive knowledge",
      "proeth:element": "Pre-Submittal Meeting Held",
      "proeth:step": 2
    },
    {
      "proeth:description": "Firm B delivers its SOQ to the wrong office (city manager\u0027s) after the 10:00 am deadline, violating both requirements",
      "proeth:element": "Firm B Submits SOQ Late",
      "proeth:step": 3
    },
    {
      "proeth:description": "The 10:00 am deadline passes without a compliant submittal from Firm B at the city clerk\u0027s office",
      "proeth:element": "Deadline Passes Unmet",
      "proeth:step": 4
    },
    {
      "proeth:description": "Non-compliant submittal creates uncertainty and ethical dilemma in the procurement process",
      "proeth:element": "QBS Evaluation Period Affected",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "City Establishes Submission Rules",
  "proeth:counterfactual": "Without the formally established rules, no \u0027deadline\u0027 could have passed unmet; alternatively, had Firm B complied, the deadline would have passed with a valid submittal on record",
  "proeth:effect": "Deadline Passes Unmet",
  "proeth:necessaryFactors": [
    "Formal establishment of a specific deadline (10:00 am, January 30)",
    "Designation of a specific submission location (city clerk\u0027s office)",
    "Communication of these rules to all participating firms at pre-submittal meeting",
    "Firm B\u0027s failure to comply with either requirement"
  ],
  "proeth:responsibilityType": "indirect",
  "proeth:responsibleAgent": "City X (municipal authority)",
  "proeth:sufficientFactors": [
    "Combination of clearly published rules + Firm B\u0027s non-compliant delivery behavior = deadline passing without a valid compliant submittal from Firm B"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Firm B chose to deliver its SOQ submittal to the city manager's office rather than the city clerk's office, and did so after the published 10:00 am deadline, resulting in a doubly non-compliant submittal arriving at the wrong location

Necessary Factors (NESS):
  • Firm B's volitional decision to use the city manager's office as the delivery point
  • Firm B's failure to submit before the 10:00 am deadline
  • The existence of a clearly designated alternative location (city clerk's office)
  • Firm B's attendance at the pre-submittal meeting where rules were communicated
Sufficient Factors:
  • Firm B's deliberate or negligent choice of wrong delivery location + late timing = doubly non-compliant submittal that triggers the ethical dilemma for Engineer A
Counterfactual Test: Had Firm B delivered to the city clerk's office before 10:00 am, no non-compliance would have occurred and no ethical dilemma would have arisen for Engineer A
Responsibility Attribution:

Agent: Firm B
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Pre-Submittal Meeting Held
    Firm B attends mandatory meeting and receives explicit notice of submission rules including location and deadline
  2. Firm B Submits SOQ Late
    Firm B prepares and dispatches its SOQ but fails to deliver it on time or to the correct location
  3. Submittal Arrives Wrong Office
    SOQ physically arrives at city manager's office — not city clerk's office — after the 10:00 am deadline
  4. Engineer A Discovers Submittal
    Engineer A, returning to his office that afternoon, discovers the misdirected and late envelope
  5. QBS Evaluation Period Affected
    Engineer A faces an ethical decision about whether and how to handle the non-compliant submittal
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/99#CausalChain_724ceb66",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Firm B chose to deliver its SOQ submittal to the city manager\u0027s office rather than the city clerk\u0027s office, and did so after the published 10:00 am deadline, resulting in a doubly non-compliant submittal arriving at the wrong location",
  "proeth:causalSequence": [
    {
      "proeth:description": "Firm B attends mandatory meeting and receives explicit notice of submission rules including location and deadline",
      "proeth:element": "Pre-Submittal Meeting Held",
      "proeth:step": 1
    },
    {
      "proeth:description": "Firm B prepares and dispatches its SOQ but fails to deliver it on time or to the correct location",
      "proeth:element": "Firm B Submits SOQ Late",
      "proeth:step": 2
    },
    {
      "proeth:description": "SOQ physically arrives at city manager\u0027s office \u2014 not city clerk\u0027s office \u2014 after the 10:00 am deadline",
      "proeth:element": "Submittal Arrives Wrong Office",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A, returning to his office that afternoon, discovers the misdirected and late envelope",
      "proeth:element": "Engineer A Discovers Submittal",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A faces an ethical decision about whether and how to handle the non-compliant submittal",
      "proeth:element": "QBS Evaluation Period Affected",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Firm B Submits SOQ Late",
  "proeth:counterfactual": "Had Firm B delivered to the city clerk\u0027s office before 10:00 am, no non-compliance would have occurred and no ethical dilemma would have arisen for Engineer A",
  "proeth:effect": "Submittal Arrives Wrong Office",
  "proeth:necessaryFactors": [
    "Firm B\u0027s volitional decision to use the city manager\u0027s office as the delivery point",
    "Firm B\u0027s failure to submit before the 10:00 am deadline",
    "The existence of a clearly designated alternative location (city clerk\u0027s office)",
    "Firm B\u0027s attendance at the pre-submittal meeting where rules were communicated"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Firm B",
  "proeth:sufficientFactors": [
    "Firm B\u0027s deliberate or negligent choice of wrong delivery location + late timing = doubly non-compliant submittal that triggers the ethical dilemma for Engineer A"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Upon returning to his office that afternoon, Engineer A discovered Firm B's late and misdirected SOQ submittal, placing him at the center of an ethical decision whose outcome — whatever it was — would affect the integrity and fairness of the QBS evaluation period

Necessary Factors (NESS):
  • Engineer A's physical discovery of the non-compliant envelope
  • Engineer A's role and authority within the city procurement process
  • The pre-existing non-compliant state of Firm B's submittal
  • The ongoing QBS evaluation process that could be influenced by Engineer A's decision
Sufficient Factors:
  • Discovery of non-compliant submittal by the responsible engineer + Engineer A's decision-making authority = sufficient to create a state of uncertainty and potential procedural compromise in the QBS process regardless of which action Engineer A chose
Counterfactual Test: Had Engineer A not discovered the submittal, or had the submittal never arrived, the QBS process would have proceeded without this complication; had Engineer A immediately and transparently reported the discovery to city officials without taking unilateral action, the impact on the evaluation period could have been minimized
Responsibility Attribution:

Agent: Engineer A (shared with Firm B as originating cause)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Submittal Arrives Wrong Office
    Firm B's non-compliant SOQ arrives at city manager's office after the deadline
  2. Engineer A Discovers Submittal
    Engineer A returns to his office and discovers the misdirected, late envelope from Firm B
  3. Engineer A Decides on Late Submittal
    Engineer A faces a volitional decision: accept, reject, escalate, or otherwise handle the non-compliant submittal
  4. Deadline Passes Unmet (confirmed)
    Engineer A's awareness confirms the deadline has passed without compliant submission, crystallizing the ethical dilemma
  5. QBS Evaluation Period Affected
    Engineer A's chosen course of action — whatever it is — introduces uncertainty, potential unfairness, or procedural irregularity into the QBS evaluation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/99#CausalChain_79d0598d",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Upon returning to his office that afternoon, Engineer A discovered Firm B\u0027s late and misdirected SOQ submittal, placing him at the center of an ethical decision whose outcome \u2014 whatever it was \u2014 would affect the integrity and fairness of the QBS evaluation period",
  "proeth:causalSequence": [
    {
      "proeth:description": "Firm B\u0027s non-compliant SOQ arrives at city manager\u0027s office after the deadline",
      "proeth:element": "Submittal Arrives Wrong Office",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A returns to his office and discovers the misdirected, late envelope from Firm B",
      "proeth:element": "Engineer A Discovers Submittal",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A faces a volitional decision: accept, reject, escalate, or otherwise handle the non-compliant submittal",
      "proeth:element": "Engineer A Decides on Late Submittal",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A\u0027s awareness confirms the deadline has passed without compliant submission, crystallizing the ethical dilemma",
      "proeth:element": "Deadline Passes Unmet (confirmed)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A\u0027s chosen course of action \u2014 whatever it is \u2014 introduces uncertainty, potential unfairness, or procedural irregularity into the QBS evaluation",
      "proeth:element": "QBS Evaluation Period Affected",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Engineer A Discovers Submittal",
  "proeth:counterfactual": "Had Engineer A not discovered the submittal, or had the submittal never arrived, the QBS process would have proceeded without this complication; had Engineer A immediately and transparently reported the discovery to city officials without taking unilateral action, the impact on the evaluation period could have been minimized",
  "proeth:effect": "QBS Evaluation Period Affected",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s physical discovery of the non-compliant envelope",
    "Engineer A\u0027s role and authority within the city procurement process",
    "The pre-existing non-compliant state of Firm B\u0027s submittal",
    "The ongoing QBS evaluation process that could be influenced by Engineer A\u0027s decision"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (shared with Firm B as originating cause)",
  "proeth:sufficientFactors": [
    "Discovery of non-compliant submittal by the responsible engineer + Engineer A\u0027s decision-making authority = sufficient to create a state of uncertainty and potential procedural compromise in the QBS process regardless of which action Engineer A chose"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: A mandatory pre-submittal meeting was conducted by City X, attended by 14 firms including Firm B, during which submission rules were communicated — establishing the knowledge baseline that makes Firm B's subsequent non-compliance a volitional act rather than an innocent mistake, and ultimately leading to Engineer A's discovery of the misdirected envelope

Necessary Factors (NESS):
  • Mandatory attendance requirement ensuring all firms received the same information
  • Explicit communication of both deadline and submission location at the meeting
  • Firm B's actual attendance at the meeting
  • Firm B's subsequent failure to act on the communicated requirements
Sufficient Factors:
  • Mandatory meeting + explicit rule communication + Firm B attendance + Firm B non-compliance = chain of events leading to Engineer A's discovery and ethical dilemma
Counterfactual Test: Had the pre-submittal meeting not been held or had Firm B not attended, Firm B's non-compliance might be attributed to lack of notice rather than negligence or disregard, fundamentally changing the ethical and legal character of the situation Engineer A faces
Responsibility Attribution:

Agent: City X (for establishing meeting) and Firm B (for attending but not complying)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. City Establishes Submission Rules
    City X creates formal procurement rules including deadline and submission location
  2. Pre-Submittal Meeting Held
    Mandatory meeting attended by Firm B communicates all submission requirements, establishing constructive knowledge
  3. Firm B Submits SOQ Late
    Despite having full knowledge of requirements, Firm B submits late and to the wrong location
  4. Submittal Arrives Wrong Office
    Non-compliant envelope arrives at city manager's office rather than city clerk's office
  5. Engineer A Discovers Submittal
    Engineer A discovers the envelope, triggering the ethical decision point
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/99#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#"
  },
  "@id": "http://proethica.org/cases/99#CausalChain_cf9eb761",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "A mandatory pre-submittal meeting was conducted by City X, attended by 14 firms including Firm B, during which submission rules were communicated \u2014 establishing the knowledge baseline that makes Firm B\u0027s subsequent non-compliance a volitional act rather than an innocent mistake, and ultimately leading to Engineer A\u0027s discovery of the misdirected envelope",
  "proeth:causalSequence": [
    {
      "proeth:description": "City X creates formal procurement rules including deadline and submission location",
      "proeth:element": "City Establishes Submission Rules",
      "proeth:step": 1
    },
    {
      "proeth:description": "Mandatory meeting attended by Firm B communicates all submission requirements, establishing constructive knowledge",
      "proeth:element": "Pre-Submittal Meeting Held",
      "proeth:step": 2
    },
    {
      "proeth:description": "Despite having full knowledge of requirements, Firm B submits late and to the wrong location",
      "proeth:element": "Firm B Submits SOQ Late",
      "proeth:step": 3
    },
    {
      "proeth:description": "Non-compliant envelope arrives at city manager\u0027s office rather than city clerk\u0027s office",
      "proeth:element": "Submittal Arrives Wrong Office",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A discovers the envelope, triggering the ethical decision point",
      "proeth:element": "Engineer A Discovers Submittal",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Pre-Submittal Meeting Held",
  "proeth:counterfactual": "Had the pre-submittal meeting not been held or had Firm B not attended, Firm B\u0027s non-compliance might be attributed to lack of notice rather than negligence or disregard, fundamentally changing the ethical and legal character of the situation Engineer A faces",
  "proeth:effect": "Engineer A Discovers Submittal",
  "proeth:necessaryFactors": [
    "Mandatory attendance requirement ensuring all firms received the same information",
    "Explicit communication of both deadline and submission location at the meeting",
    "Firm B\u0027s actual attendance at the meeting",
    "Firm B\u0027s subsequent failure to act on the communicated requirements"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "City X (for establishing meeting) and Firm B (for attending but not complying)",
  "proeth:sufficientFactors": [
    "Mandatory meeting + explicit rule communication + Firm B attendance + Firm B non-compliance = chain of events leading to Engineer A\u0027s discovery and ethical dilemma"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (9)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
mandatory pre-submittal meeting before
Entity1 is before Entity2
publication of SOQ deadline (date, time, location) time:before
http://www.w3.org/2006/time#before
The city conducted a mandatory pre-submittal meeting and received initial interest from 14 different... [more]
mandatory pre-submittal meeting before
Entity1 is before Entity2
SOQ submission deadline (10:00 AM, January 30) time:before
http://www.w3.org/2006/time#before
The city conducted a mandatory pre-submittal meeting... indicating all submittals must be received b... [more]
SOQ submission deadline (10:00 AM, January 30) before
Entity1 is before Entity2
Firm B submittal receipt (2:05 PM, January 30) time:before
http://www.w3.org/2006/time#before
all submittals must be received... no later than 10:00 am on January 30... the submittal was receive... [more]
Firm B submittal receipt (2:05 PM, January 30) before
Entity1 is before Entity2
Engineer A's return to office (afternoon, January 30) time:before
http://www.w3.org/2006/time#before
Engineer A returned to his office in the afternoon on January 30 and was intercepted by the city man... [more]
hard copy agenda distribution at pre-submittal meeting equals
Entity1 and Entity2 have the same start and end times
mandatory pre-submittal meeting time:intervalEquals
http://www.w3.org/2006/time#intervalEquals
The date, time, and location were also listed in the city's RFQ webpage and appeared on the hard cop... [more]
Engineer B's FOIA request (BER Case 10-8) before
Entity1 is before Entity2
interview process (BER Case 10-8) time:before
http://www.w3.org/2006/time#before
Prior to the interview process, Engineer B... submitted a state Freedom of Information Act (FOIA) re... [more]
Engineer B's FOIA request (BER Case 10-8) before
Entity1 is before Entity2
Engineer B's RFQ submission (BER Case 10-8) time:before
http://www.w3.org/2006/time#before
Engineer B should have made the FOIA request subsequent to and not before Engineer B's firm submitte... [more]
state providing FOIA information to Engineer B (BER Case 10-8) before
Entity1 is before Entity2
Engineer B's RFQ submission (BER Case 10-8) time:before
http://www.w3.org/2006/time#before
The state then provided the information to Engineer B. Thereafter, Engineer B submitted his firm's e... [more]
Firm B's past engineering design projects for the city before
Entity1 is before Entity2
current QBS process for new public building time:before
http://www.w3.org/2006/time#before
Firm B had also performed well on several other engineering design projects for the city
About Allen Relations & OWL-Time

Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.

Each relation includes both a ProEthica custom property and a time:* OWL-Time property for maximum compatibility.