32 entities 7 actions 7 events 5 causal chains 12 temporal relations
Timeline Overview
Action Event 14 sequenced markers
Submit Incomplete Design Documents Design phase, at or before the contractually specified delivery deadline
Respond to Dam RFP Early project phase, prior to contract award
Rationalize Incompleteness via Federal Funds Design phase, concurrent with decision to submit incomplete documents
Approve Incomplete Design Documents Pre-bid phase, following Engineer A's submission of drawings and specifications
Submit Low Bid on Inadequate Documents Bidding phase, following public advertisement of the project
Admit Incompleteness Without Prior Disclosure Pre-construction conference, after contract award to Hi-Lo Construction
Contract Award to Engineer A Early phase — after RFP response and interview evaluation
Federal Funding Commitment Established Pre-contract or concurrent with RFP issuance
Time Pressure Condition Emerges During design production phase, prior to document submission
Incomplete Documents Enter Review After Engineer A's submission; beginning of federal review phase
Deficient Documents Approved End of federal review phase; prior to bid advertisement
Project Advertised for Bids After federal approval; prior to bid submission deadline
Hi-Lo Wins Construction Contract After bid submission deadline; prior to pre-construction conference
OWL-Time Temporal Structure 12 relations time: = w3.org/2006/time
Engineer A's knowledge of incompleteness time:intervalEquals submission of incomplete drawings and specifications
Engineer A responds to RFP time:before award of contract for design, drawings, and specifications
award of contract for design time:before production of drawings and specifications
production of incomplete drawings and specifications time:before Engineer B's approval
Engineer B's approval time:before project advertised for bids
project advertised for bids time:before contract awarded to Hi-Lo Construction
contract awarded to Hi-Lo Construction time:before pre-construction conference
Engineer C's review of bidding documents time:before Engineer C submitting low bid
Engineer C submitting low bid time:before Engineer C identifying design deficiencies at pre-construction conference
time pressure deadline time:before submission of incomplete drawings and specifications
BER Case No. 82-5 time:before current Board discussion of Engineer A, B, and C case
Engineer A's non-disclosure of incompleteness time:intervalStarts submission through approval through bid award sequence
Extracted Actions (7)
Volitional professional decisions with intentions and ethical context

Description: Engineer A chose to respond to the local public agency's RFP for dam design, presenting an impressive brochure and participating in a personal interview to secure the contract. This was a deliberate competitive pursuit of a publicly funded engineering project.

Temporal Marker: Early project phase, prior to contract award

Mental State: deliberate

Intended Outcome: Win the design contract for the dam project and secure revenue for the firm

Fulfills Obligations:
  • Competitive participation in public procurement process
Guided By Principles:
  • Professional competence
  • Public service
  • Honest representation of firm capabilities
Required Capabilities:
Dam design expertise Project management Preparation of complete drawings and specifications
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A was motivated by business development imperatives, competitive ambition, and the professional prestige of winning a publicly funded dam project. The decision to pursue the contract likely reflected confidence in the firm's capabilities, financial incentives, and the reputational value of a federal-grant-backed infrastructure award.

Ethical Tension: Honest representation of firm capacity vs. competitive pressure to win work. Engineer A must balance the duty to only undertake work within one's competence and available resources (NSPE Code Section II.2) against the business reality that firms must compete aggressively for contracts. There is also a latent tension between marketing enthusiasm and factual accuracy in the brochure and interview.

Learning Significance: Teaches that the ethical obligations of an engineer begin at the proposal stage, not at project execution. Winning a contract the firm cannot properly fulfill plants the seed of every downstream ethical failure. Students learn that accepting a commission carries implicit representations of capacity, timeline feasibility, and professional readiness.

Stakes: Public safety on a dam project, integrity of the federal grant process, the agency's trust in the procurement system, and the long-term reputational standing of Engineer A's firm. A dam is a life-safety structure; any downstream design failure could result in catastrophic harm.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Decline to respond to the RFP after honestly assessing that current workload or staffing cannot support adequate dam design within the required timeline.
  • Respond to the RFP with a transparent disclosure of current capacity constraints and propose a realistic schedule that accommodates complete design work.
  • Pursue the contract as a joint venture or sub-consultant arrangement with a firm that has demonstrated dam design capacity, ensuring adequate resources are committed.

Narrative Role: inciting_incident

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Action_Respond_to_Dam_RFP",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Decline to respond to the RFP after honestly assessing that current workload or staffing cannot support adequate dam design within the required timeline.",
    "Respond to the RFP with a transparent disclosure of current capacity constraints and propose a realistic schedule that accommodates complete design work.",
    "Pursue the contract as a joint venture or sub-consultant arrangement with a firm that has demonstrated dam design capacity, ensuring adequate resources are committed."
  ],
  "proeth-scenario:characterMotivation": "Engineer A was motivated by business development imperatives, competitive ambition, and the professional prestige of winning a publicly funded dam project. The decision to pursue the contract likely reflected confidence in the firm\u0027s capabilities, financial incentives, and the reputational value of a federal-grant-backed infrastructure award.",
  "proeth-scenario:consequencesIfAlternative": [
    "Declining would forfeit the contract and associated revenue, but would preserve public safety, the agency\u0027s ability to select a qualified firm, and Engineer A\u0027s long-term professional integrity. No downstream ethical violations would occur.",
    "Disclosing constraints in the proposal might reduce competitiveness but would allow the agency to make an informed selection decision. If selected, a realistic schedule would reduce the probability of incomplete documents and all subsequent harms.",
    "A joint venture approach would distribute workload appropriately, likely produce complete and buildable design documents, and model the collaborative professionalism the NSPE Code envisions for complex public infrastructure."
  ],
  "proeth-scenario:decisionSignificance": "Teaches that the ethical obligations of an engineer begin at the proposal stage, not at project execution. Winning a contract the firm cannot properly fulfill plants the seed of every downstream ethical failure. Students learn that accepting a commission carries implicit representations of capacity, timeline feasibility, and professional readiness.",
  "proeth-scenario:ethicalTension": "Honest representation of firm capacity vs. competitive pressure to win work. Engineer A must balance the duty to only undertake work within one\u0027s competence and available resources (NSPE Code Section II.2) against the business reality that firms must compete aggressively for contracts. There is also a latent tension between marketing enthusiasm and factual accuracy in the brochure and interview.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "inciting_incident",
  "proeth-scenario:stakes": "Public safety on a dam project, integrity of the federal grant process, the agency\u0027s trust in the procurement system, and the long-term reputational standing of Engineer A\u0027s firm. A dam is a life-safety structure; any downstream design failure could result in catastrophic harm.",
  "proeth:description": "Engineer A chose to respond to the local public agency\u0027s RFP for dam design, presenting an impressive brochure and participating in a personal interview to secure the contract. This was a deliberate competitive pursuit of a publicly funded engineering project.",
  "proeth:foreseenUnintendedEffects": [
    "Commitment to full design deliverables including complete drawings and specifications"
  ],
  "proeth:fulfillsObligation": [
    "Competitive participation in public procurement process"
  ],
  "proeth:guidedByPrinciple": [
    "Professional competence",
    "Public service",
    "Honest representation of firm capabilities"
  ],
  "proeth:hasAgent": "Engineer A (Private Design Engineer / Firm Principal)",
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Win the design contract for the dam project and secure revenue for the firm",
  "proeth:requiresCapability": [
    "Dam design expertise",
    "Project management",
    "Preparation of complete drawings and specifications"
  ],
  "proeth:temporalMarker": "Early project phase, prior to contract award",
  "proeth:withinCompetence": true,
  "rdfs:label": "Respond to Dam RFP"
}

Description: Engineer A knowingly submitted incomplete drawings and specifications by the specified deadline without disclosing their incompleteness to the client, the federal funding agency, or any other party. Engineer A made a deliberate choice to deliver deficient work product rather than request a deadline extension or communicate the shortfall.

Temporal Marker: Design phase, at or before the contractually specified delivery deadline

Mental State: deliberate

Intended Outcome: Meet the contractual delivery deadline and avoid conflict or delay with the client and federal agency

Guided By Principles:
  • Completeness of engineering work product
  • Honesty and transparency
  • Public welfare
  • Professional integrity
Required Capabilities:
Complete dam design Hydraulic and structural engineering Preparation of buildable construction documents Project scheduling and scope management
Within Competence: No
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A was driven by deadline compliance, fear of contract penalties or client dissatisfaction for late delivery, and possibly a belief that partial documents were 'good enough' to move the project forward. There may also have been financial motivation to invoice for completed deliverables and avoid the cost of additional design time.

Ethical Tension: Obligation to produce complete, accurate, and safe engineering documents (NSPE Code Section II.2, III.2) vs. contractual deadline pressure and the desire to avoid difficult conversations with the client about schedule slippage. The tension pits short-term convenience and client-pleasing against the foundational professional duty to protect public safety and deliver competent work.

Learning Significance: This is the central ethical violation of the case and the most teachable moment about professional integrity under pressure. Students learn that knowingly submitting deficient work without disclosure is not a gray area — it is a clear breach of professional duty regardless of the reasons behind it. The action also illustrates that silence in the face of a known deficiency is itself a form of deception.

Stakes: Public safety on a life-safety structure, the validity of the entire competitive bidding process, the federal agency's stewardship of grant funds, the ability of contractors to bid accurately, and Engineer A's license and professional standing. Incomplete dam specifications can lead to structural failure, cost overruns, litigation, and loss of public trust.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Request a formal deadline extension from the client, transparently explaining the current state of the documents and the additional time needed to complete them properly.
  • Submit the documents on time but include a formal written disclosure identifying which sections are incomplete, what work remains, and a proposed schedule for delivering the remaining design.
  • Withdraw from the contract if the firm genuinely cannot complete the work to a competent standard, allowing the agency to engage a firm with available capacity.

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Action_Submit_Incomplete_Design_Documents",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Request a formal deadline extension from the client, transparently explaining the current state of the documents and the additional time needed to complete them properly.",
    "Submit the documents on time but include a formal written disclosure identifying which sections are incomplete, what work remains, and a proposed schedule for delivering the remaining design.",
    "Withdraw from the contract if the firm genuinely cannot complete the work to a competent standard, allowing the agency to engage a firm with available capacity."
  ],
  "proeth-scenario:characterMotivation": "Engineer A was driven by deadline compliance, fear of contract penalties or client dissatisfaction for late delivery, and possibly a belief that partial documents were \u0027good enough\u0027 to move the project forward. There may also have been financial motivation to invoice for completed deliverables and avoid the cost of additional design time.",
  "proeth-scenario:consequencesIfAlternative": [
    "Requesting an extension might delay the project schedule and create client frustration, but it preserves the integrity of the design process. The agency retains the ability to make an informed decision about whether to grant the extension or re-scope the engagement.",
    "Submitting with written disclosure of incompleteness is ethically superior because it is honest and allows all parties \u2014 client, federal agency, and eventual bidders \u2014 to make informed decisions. The project might be paused or re-scoped, but public safety and procurement integrity are protected.",
    "Withdrawal is professionally painful and financially costly but is the ethical choice if competent completion is impossible. It prevents a cascade of downstream harms and preserves the public\u0027s right to receive competent engineering services."
  ],
  "proeth-scenario:decisionSignificance": "This is the central ethical violation of the case and the most teachable moment about professional integrity under pressure. Students learn that knowingly submitting deficient work without disclosure is not a gray area \u2014 it is a clear breach of professional duty regardless of the reasons behind it. The action also illustrates that silence in the face of a known deficiency is itself a form of deception.",
  "proeth-scenario:ethicalTension": "Obligation to produce complete, accurate, and safe engineering documents (NSPE Code Section II.2, III.2) vs. contractual deadline pressure and the desire to avoid difficult conversations with the client about schedule slippage. The tension pits short-term convenience and client-pleasing against the foundational professional duty to protect public safety and deliver competent work.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Public safety on a life-safety structure, the validity of the entire competitive bidding process, the federal agency\u0027s stewardship of grant funds, the ability of contractors to bid accurately, and Engineer A\u0027s license and professional standing. Incomplete dam specifications can lead to structural failure, cost overruns, litigation, and loss of public trust.",
  "proeth:description": "Engineer A knowingly submitted incomplete drawings and specifications by the specified deadline without disclosing their incompleteness to the client, the federal funding agency, or any other party. Engineer A made a deliberate choice to deliver deficient work product rather than request a deadline extension or communicate the shortfall.",
  "proeth:foreseenUnintendedEffects": [
    "Incomplete documents would be submitted for federal approval and public bidding",
    "Contractor would encounter unbuildable conditions",
    "Cost overruns would likely result"
  ],
  "proeth:guidedByPrinciple": [
    "Completeness of engineering work product",
    "Honesty and transparency",
    "Public welfare",
    "Professional integrity"
  ],
  "proeth:hasAgent": "Engineer A (Private Design Engineer / Firm Principal)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Time pressure vs. design completeness and honest disclosure",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict by prioritizing schedule compliance over completeness and transparency, without seeking a legitimate remedy such as requesting a deadline extension or notifying stakeholders of the deficiency \u2014 an ethically impermissible resolution"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Meet the contractual delivery deadline and avoid conflict or delay with the client and federal agency",
  "proeth:requiresCapability": [
    "Complete dam design",
    "Hydraulic and structural engineering",
    "Preparation of buildable construction documents",
    "Project scheduling and scope management"
  ],
  "proeth:temporalMarker": "Design phase, at or before the contractually specified delivery deadline",
  "proeth:violatesObligation": [
    "NSPE Code obligation to perform services in conformity with applicable engineering standards",
    "NSPE Code prohibition on deceptive acts",
    "Obligation of honest and transparent communication with client",
    "Obligation to protect the public interest and steward public funds responsibly",
    "Obligation to deliver complete design documents as contracted"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Submit Incomplete Design Documents"
}

Description: Engineer A internally justified submitting incomplete documents by assuming that federal funds would be available to cover any cost overruns resulting from the missing design detail. This rationalization was made without any disclosed basis or authorization, and was used as a substitute for proper disclosure and remediation.

Temporal Marker: Design phase, concurrent with decision to submit incomplete documents

Mental State: deliberate rationalization

Intended Outcome: Justify proceeding with incomplete submission by framing federal funding as a financial backstop for resulting cost overruns

Guided By Principles:
  • Honesty
  • Integrity
  • Public welfare
  • Responsible use of public funds
Required Capabilities:
Honest project communication Understanding of federal grant fund use restrictions Professional judgment about disclosure obligations
Within Competence: No
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer A sought psychological relief from the cognitive dissonance of knowingly submitting deficient work. By constructing a rationalization — that federal funds would absorb cost overruns — Engineer A could reframe the ethical violation as a manageable financial inconvenience rather than a safety and integrity failure. This self-justification also deflected personal accountability onto an external funding mechanism.

Ethical Tension: Personal accountability and honest professional judgment vs. motivated reasoning and wishful thinking. The tension here is between what Engineer A knew to be true (the documents were incomplete and this was wrong) and what Engineer A wanted to believe (that the consequences would be absorbed by someone else's money). There is also a secondary tension involving the misuse of public federal funds as a private risk-management buffer.

Learning Significance: Illustrates the psychology of ethical self-deception and the danger of rationalization in professional practice. Students learn that a rationalization is not a justification — the absence of disclosed authorization for using federal funds as a contingency makes this assumption both professionally irresponsible and potentially improper. This action teaches that engineers must distinguish between genuine ethical reasoning and motivated reasoning designed to avoid discomfort.

Stakes: Integrity of federal grant fund management, the agency's fiduciary obligations to taxpayers, the accuracy of project cost estimates, and the professional credibility of Engineer A. If federal funds are improperly used to cover overruns caused by negligent design, taxpayers bear the cost of Engineer A's ethical failure.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Formally consult with the client and the federal funding agency to determine whether contingency funds exist and under what conditions they may be used, before treating them as a backstop.
  • Acknowledge internally that no authorized contingency exists and treat the incompleteness as the serious professional problem it is, triggering disclosure and remediation.
  • Engage the client in a transparent conversation about the design gap, the likely cost implications, and options for addressing them — including schedule adjustment, scope reduction, or phased design delivery.

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Action_Rationalize_Incompleteness_via_Federal_Funds",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Formally consult with the client and the federal funding agency to determine whether contingency funds exist and under what conditions they may be used, before treating them as a backstop.",
    "Acknowledge internally that no authorized contingency exists and treat the incompleteness as the serious professional problem it is, triggering disclosure and remediation.",
    "Engage the client in a transparent conversation about the design gap, the likely cost implications, and options for addressing them \u2014 including schedule adjustment, scope reduction, or phased design delivery."
  ],
  "proeth-scenario:characterMotivation": "Engineer A sought psychological relief from the cognitive dissonance of knowingly submitting deficient work. By constructing a rationalization \u2014 that federal funds would absorb cost overruns \u2014 Engineer A could reframe the ethical violation as a manageable financial inconvenience rather than a safety and integrity failure. This self-justification also deflected personal accountability onto an external funding mechanism.",
  "proeth-scenario:consequencesIfAlternative": [
    "Formal consultation would likely reveal that federal funds cannot be unilaterally earmarked for design-negligence overruns, forcing Engineer A to confront the problem directly. This would be uncomfortable but would initiate an honest resolution process.",
    "Honest internal acknowledgment would compel disclosure and remediation, preventing all downstream harms. It requires moral courage but is the only path consistent with professional ethics.",
    "A transparent client conversation would be professionally difficult but would model the kind of candid, trust-based relationship that the NSPE Code envisions between engineers and their clients. It would also give the agency the information needed to make sound project decisions."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the psychology of ethical self-deception and the danger of rationalization in professional practice. Students learn that a rationalization is not a justification \u2014 the absence of disclosed authorization for using federal funds as a contingency makes this assumption both professionally irresponsible and potentially improper. This action teaches that engineers must distinguish between genuine ethical reasoning and motivated reasoning designed to avoid discomfort.",
  "proeth-scenario:ethicalTension": "Personal accountability and honest professional judgment vs. motivated reasoning and wishful thinking. The tension here is between what Engineer A knew to be true (the documents were incomplete and this was wrong) and what Engineer A wanted to believe (that the consequences would be absorbed by someone else\u0027s money). There is also a secondary tension involving the misuse of public federal funds as a private risk-management buffer.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "Integrity of federal grant fund management, the agency\u0027s fiduciary obligations to taxpayers, the accuracy of project cost estimates, and the professional credibility of Engineer A. If federal funds are improperly used to cover overruns caused by negligent design, taxpayers bear the cost of Engineer A\u0027s ethical failure.",
  "proeth:description": "Engineer A internally justified submitting incomplete documents by assuming that federal funds would be available to cover any cost overruns resulting from the missing design detail. This rationalization was made without any disclosed basis or authorization, and was used as a substitute for proper disclosure and remediation.",
  "proeth:foreseenUnintendedEffects": [
    "Potential misuse or misrepresentation of federal grant funds",
    "Cost overruns borne by public rather than addressed through proper design"
  ],
  "proeth:guidedByPrinciple": [
    "Honesty",
    "Integrity",
    "Public welfare",
    "Responsible use of public funds"
  ],
  "proeth:hasAgent": "Engineer A (Private Design Engineer / Firm Principal)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Cost source assumption vs. transparency and honest communication",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict by substituting an unauthorized and undisclosed financial assumption for proper professional action, prioritizing personal convenience and project continuity over ethical transparency"
  },
  "proeth:hasMentalState": "deliberate rationalization",
  "proeth:intendedOutcome": "Justify proceeding with incomplete submission by framing federal funding as a financial backstop for resulting cost overruns",
  "proeth:requiresCapability": [
    "Honest project communication",
    "Understanding of federal grant fund use restrictions",
    "Professional judgment about disclosure obligations"
  ],
  "proeth:temporalMarker": "Design phase, concurrent with decision to submit incomplete documents",
  "proeth:violatesObligation": [
    "NSPE Code prohibition on fraud and misrepresentation",
    "Obligation to steward public funds responsibly",
    "Obligation of honest communication with client and funding agency",
    "Obligation to avoid deceptive acts that harm the public interest"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Rationalize Incompleteness via Federal Funds"
}

Description: Engineer B, acting on behalf of the federal funding agency, reviewed and approved Engineer A's incomplete drawings and specifications without flagging deficiencies, requesting corrections, or escalating the review to a more qualified colleague. This approval enabled the project to proceed to public bidding on the basis of deficient documents.

Temporal Marker: Pre-bid phase, following Engineer A's submission of drawings and specifications

Mental State: deliberate action under uncertain competency

Intended Outcome: Advance the project through federal approval and enable public bidding to proceed

Guided By Principles:
  • Competence
  • Public welfare
  • Professional responsibility
  • Honest self-assessment
Required Capabilities:
Dam design review expertise Structural and hydraulic engineering judgment Ability to identify incomplete or inadequate construction documents
Within Competence: No
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer B was likely motivated by institutional efficiency pressures, deference to the submitting engineer's professional credentials, workload constraints, or a culture of rubber-stamp review within the federal agency. Engineer B may have lacked specialized dam design expertise, felt unempowered to challenge a licensed PE's submission, or simply failed to apply the diligence the review role required.

Ethical Tension: Duty to perform a competent, independent technical review in the public interest (NSPE Code Section II.2, III.2) vs. institutional pressure to process approvals efficiently, deference to the submitting engineer's authority, and the practical difficulty of identifying deficiencies in a complex submission. There is also a tension between bureaucratic role compliance ('my job is to process this') and professional responsibility ('my obligation is to protect public safety').

Learning Significance: Demonstrates that ethical responsibility does not disappear because one is acting in a review or oversight capacity rather than as the primary designer. Students learn that approving deficient work is itself an ethical act with consequences, and that the review engineer cannot hide behind the submitting engineer's primary responsibility. This action also illustrates how institutional cultures can normalize inadequate oversight.

Stakes: The federal agency's legal and fiduciary obligations, the integrity of the grant funding process, public safety, and the validity of the competitive bidding process. Engineer B's approval is the institutional gate that transforms a deficient private submission into an official public bidding document — significantly amplifying the harm.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Return the documents to Engineer A with a formal deficiency notice identifying the incomplete sections and requiring resubmission of complete documents before approval.
  • Escalate the review to a senior engineer or external technical reviewer with dam design expertise before making an approval determination.
  • Conditionally approve the documents with a written record of identified deficiencies, requiring Engineer A to resolve them before construction documents are issued to bidders.

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Action_Approve_Incomplete_Design_Documents",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Return the documents to Engineer A with a formal deficiency notice identifying the incomplete sections and requiring resubmission of complete documents before approval.",
    "Escalate the review to a senior engineer or external technical reviewer with dam design expertise before making an approval determination.",
    "Conditionally approve the documents with a written record of identified deficiencies, requiring Engineer A to resolve them before construction documents are issued to bidders."
  ],
  "proeth-scenario:characterMotivation": "Engineer B was likely motivated by institutional efficiency pressures, deference to the submitting engineer\u0027s professional credentials, workload constraints, or a culture of rubber-stamp review within the federal agency. Engineer B may have lacked specialized dam design expertise, felt unempowered to challenge a licensed PE\u0027s submission, or simply failed to apply the diligence the review role required.",
  "proeth-scenario:consequencesIfAlternative": [
    "Returning documents with a deficiency notice would delay the project but would force Engineer A to complete the design properly. It would protect the federal agency from complicity in approving inadequate work and preserve the integrity of the bidding process.",
    "Escalating to a qualified reviewer would introduce the technical expertise needed to identify deficiencies that Engineer B may have missed, providing a proper institutional check. This is especially appropriate for a life-safety structure like a dam.",
    "Conditional approval with documented deficiencies would create a formal record of known problems and assign responsibility for resolution. While not as protective as full rejection, it would prevent silent propagation of the deficiencies into the bidding process."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that ethical responsibility does not disappear because one is acting in a review or oversight capacity rather than as the primary designer. Students learn that approving deficient work is itself an ethical act with consequences, and that the review engineer cannot hide behind the submitting engineer\u0027s primary responsibility. This action also illustrates how institutional cultures can normalize inadequate oversight.",
  "proeth-scenario:ethicalTension": "Duty to perform a competent, independent technical review in the public interest (NSPE Code Section II.2, III.2) vs. institutional pressure to process approvals efficiently, deference to the submitting engineer\u0027s authority, and the practical difficulty of identifying deficiencies in a complex submission. There is also a tension between bureaucratic role compliance (\u0027my job is to process this\u0027) and professional responsibility (\u0027my obligation is to protect public safety\u0027).",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The federal agency\u0027s legal and fiduciary obligations, the integrity of the grant funding process, public safety, and the validity of the competitive bidding process. Engineer B\u0027s approval is the institutional gate that transforms a deficient private submission into an official public bidding document \u2014 significantly amplifying the harm.",
  "proeth:description": "Engineer B, acting on behalf of the federal funding agency, reviewed and approved Engineer A\u0027s incomplete drawings and specifications without flagging deficiencies, requesting corrections, or escalating the review to a more qualified colleague. This approval enabled the project to proceed to public bidding on the basis of deficient documents.",
  "proeth:foreseenUnintendedEffects": [
    "Incomplete documents would enter public bidding process",
    "Contractors would bid on inadequate documentation"
  ],
  "proeth:guidedByPrinciple": [
    "Competence",
    "Public welfare",
    "Professional responsibility",
    "Honest self-assessment"
  ],
  "proeth:hasAgent": "Engineer B (Federal Agency Engineering Staff Reviewer)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Competency limits vs. duty to ensure adequate review",
    "proeth:resolutionReasoning": "Engineer B failed to recognize or act on competency limitations, approving documents without adequate review or escalation \u2014 a violation of the NSPE Code\u0027s requirement to recognize limits of competence and take corrective action"
  },
  "proeth:hasMentalState": "deliberate action under uncertain competency",
  "proeth:intendedOutcome": "Advance the project through federal approval and enable public bidding to proceed",
  "proeth:requiresCapability": [
    "Dam design review expertise",
    "Structural and hydraulic engineering judgment",
    "Ability to identify incomplete or inadequate construction documents"
  ],
  "proeth:temporalMarker": "Pre-bid phase, following Engineer A\u0027s submission of drawings and specifications",
  "proeth:violatesObligation": [
    "NSPE Code obligation to perform services only within areas of competence",
    "NSPE Code obligation to recognize limits of competence and take appropriate action",
    "Obligation to protect public interest by ensuring federal funds support adequately designed projects",
    "Duty to escalate review to a qualified engineer when personal competency is insufficient"
  ],
  "proeth:withinCompetence": false,
  "rdfs:label": "Approve Incomplete Design Documents"
}

Description: Engineer C, as owner of Hi-Lo Construction, submitted the low bid on the project despite possessing the engineering background to recognize that the bidding documents were incomplete or inadequate. Engineer C did not request clarification from the owner or Engineer A, nor did the bid reflect additional costs for completing the work implied by the document deficiencies.

Temporal Marker: Bidding phase, following public advertisement of the project

Mental State: deliberate

Intended Outcome: Win the construction contract by submitting the lowest bid

Guided By Principles:
  • Honest bidding
  • Competent evaluation of contract documents
  • Fair dealing with project owner
  • Professional responsibility
Required Capabilities:
Engineering evaluation of construction documents Cost estimation accounting for document deficiencies Bid preparation and clarification request processes
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Engineer C, as a contractor-owner, was motivated by the competitive imperative to win the bid and secure revenue for Hi-Lo Construction. Submitting the low bid without flagging document deficiencies may reflect a calculated business strategy: win the contract, then leverage the deficiencies during construction to negotiate change orders and additional compensation. Alternatively, Engineer C may have underestimated the severity of the deficiencies at bid time.

Ethical Tension: Professional duty to use engineering knowledge to identify and communicate known deficiencies in bidding documents (NSPE Code Section III.2) vs. competitive business interest in winning the contract at the lowest possible bid price. There is also tension between the contractor role (bid to win) and the engineering license obligations (flag safety and design concerns), which Engineer C simultaneously holds.

Learning Significance: Illustrates the unique ethical complexity faced by engineer-contractors, who carry professional engineering obligations that transcend the purely commercial contractor role. Students learn that possessing an engineering license creates duties that cannot be set aside when wearing a contractor's hat. The action also raises questions about bid manipulation and the ethics of strategically withholding known concerns to gain post-award leverage.

Stakes: The integrity of the competitive bidding process, the accuracy of the project budget, the ability of the owner to make informed award decisions, and the safety of construction workers and the public. If Engineer C wins the contract on a low bid that does not account for the cost of completing the design, the project is set up for disputes, delays, and potential safety failures.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Submit a Request for Information (RFI) or formal clarification request to Engineer A and the owner before bid submission, identifying the specific document deficiencies and requesting resolution or clarification.
  • Submit a bid that explicitly includes a contingency or allowance for the costs of completing or resolving the identified design deficiencies, with a written explanation to the owner.
  • Decline to bid on the project, citing the inadequacy of the bidding documents as a basis for withdrawal, and formally notify the owner of the deficiencies in writing.

Narrative Role: rising_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Action_Submit_Low_Bid_on_Inadequate_Documents",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Submit a Request for Information (RFI) or formal clarification request to Engineer A and the owner before bid submission, identifying the specific document deficiencies and requesting resolution or clarification.",
    "Submit a bid that explicitly includes a contingency or allowance for the costs of completing or resolving the identified design deficiencies, with a written explanation to the owner.",
    "Decline to bid on the project, citing the inadequacy of the bidding documents as a basis for withdrawal, and formally notify the owner of the deficiencies in writing."
  ],
  "proeth-scenario:characterMotivation": "Engineer C, as a contractor-owner, was motivated by the competitive imperative to win the bid and secure revenue for Hi-Lo Construction. Submitting the low bid without flagging document deficiencies may reflect a calculated business strategy: win the contract, then leverage the deficiencies during construction to negotiate change orders and additional compensation. Alternatively, Engineer C may have underestimated the severity of the deficiencies at bid time.",
  "proeth-scenario:consequencesIfAlternative": [
    "Submitting an RFI would force the deficiencies into the public record before bid submission, potentially triggering addenda, document correction, or bid postponement. This protects all bidders, the owner, and the public, and models the professional conduct the NSPE Code requires.",
    "A bid with explicit contingency and written explanation would be transparent about the cost implications of the deficiencies, giving the owner honest information for the award decision. It would likely not be the low bid, but it would be an ethical one.",
    "Declining to bid and formally notifying the owner would be the most protective action for the public and the procurement process. It would create an official record of the deficiencies and compel the owner and Engineer A to address them before proceeding."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates the unique ethical complexity faced by engineer-contractors, who carry professional engineering obligations that transcend the purely commercial contractor role. Students learn that possessing an engineering license creates duties that cannot be set aside when wearing a contractor\u0027s hat. The action also raises questions about bid manipulation and the ethics of strategically withholding known concerns to gain post-award leverage.",
  "proeth-scenario:ethicalTension": "Professional duty to use engineering knowledge to identify and communicate known deficiencies in bidding documents (NSPE Code Section III.2) vs. competitive business interest in winning the contract at the lowest possible bid price. There is also tension between the contractor role (bid to win) and the engineering license obligations (flag safety and design concerns), which Engineer C simultaneously holds.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "rising_action",
  "proeth-scenario:stakes": "The integrity of the competitive bidding process, the accuracy of the project budget, the ability of the owner to make informed award decisions, and the safety of construction workers and the public. If Engineer C wins the contract on a low bid that does not account for the cost of completing the design, the project is set up for disputes, delays, and potential safety failures.",
  "proeth:description": "Engineer C, as owner of Hi-Lo Construction, submitted the low bid on the project despite possessing the engineering background to recognize that the bidding documents were incomplete or inadequate. Engineer C did not request clarification from the owner or Engineer A, nor did the bid reflect additional costs for completing the work implied by the document deficiencies.",
  "proeth:foreseenUnintendedEffects": [
    "Winning a contract on documents that may be insufficient to build the project",
    "Exposure to cost overruns and construction difficulties not reflected in the bid price"
  ],
  "proeth:guidedByPrinciple": [
    "Honest bidding",
    "Competent evaluation of contract documents",
    "Fair dealing with project owner",
    "Professional responsibility"
  ],
  "proeth:hasAgent": "Engineer C (Owner, Hi-Lo Construction)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Low bid competitive advantage vs. ethical and accurate bid preparation",
    "proeth:resolutionReasoning": "Engineer C resolved the conflict by submitting a low bid without adjustment or clarification, presumably accepting the risk of inadequate documents in exchange for the competitive advantage of the lowest price \u2014 a resolution the Discussion characterizes as leaving Engineer C with no one to fault but himself"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Win the construction contract by submitting the lowest bid",
  "proeth:requiresCapability": [
    "Engineering evaluation of construction documents",
    "Cost estimation accounting for document deficiencies",
    "Bid preparation and clarification request processes"
  ],
  "proeth:temporalMarker": "Bidding phase, following public advertisement of the project",
  "proeth:violatesObligation": [
    "Obligation to accurately reflect the true cost of completing the work in the bid, including costs arising from document deficiencies",
    "Obligation to request clarification when bidding documents are incomplete or ambiguous",
    "NSPE Code obligation to perform services within areas of competence, including competent bid preparation",
    "Obligation to protect the owner from uninformed contract award based on deficient documents"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Submit Low Bid on Inadequate Documents"
}

Description: At the pre-construction conference, Engineer C formally identified major design deficiencies in the drawings and specifications and declared certain parts of the project unbuildable without major changes. This action brought the ethical crisis into public view among the project parties and triggered Engineer A's admission of incompleteness.

Temporal Marker: Pre-construction conference, after contract award to Hi-Lo Construction

Mental State: deliberate

Intended Outcome: Formally notify the project parties of the design deficiencies and protect Hi-Lo Construction's interests before construction commenced on an unbuildable project

Fulfills Obligations:
  • Obligation to communicate known project deficiencies to the owner and design engineer before construction begins
  • Obligation to protect the public interest by flagging conditions that could result in a failed or dangerous structure
Guided By Principles:
  • Honest communication
  • Public safety
  • Professional responsibility
  • Protection of owner interests
Required Capabilities:
Engineering evaluation of construction documents Construction sequencing and buildability assessment Professional communication of technical deficiencies
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: By the pre-construction conference, Engineer C had contractual and financial skin in the game and could no longer defer the deficiency issue. Raising the unbuildable conditions was likely motivated by a combination of legitimate professional concern, self-protection from liability for executing an unsafe or unworkable design, and the practical need to establish a formal record of the design failures before construction began and cost disputes arose.

Ethical Tension: Professional duty to identify and disclose safety-threatening design deficiencies (NSPE Code Section III.2) — which Engineer C should have exercised at bid time — vs. the strategic timing of that disclosure to maximize contractual leverage after contract award. There is a tension between doing the right thing (disclosure) and doing it at the right time (before bidding). Late disclosure, while better than no disclosure, raises questions about Engineer C's earlier silence.

Learning Significance: Demonstrates that disclosure of known deficiencies, while ethically required, is most valuable before harm propagates through the project lifecycle. Students learn that 'better late than never' is not an ethical standard — the timing of disclosure matters. However, this action also illustrates that even belated professional candor can prevent construction-phase catastrophes and is always preferable to continued silence.

Stakes: Worker safety during construction, structural integrity of the dam, project cost and schedule, the owner's ability to make informed decisions about proceeding, and the legal liability exposure of all parties. Declaring parts of the project unbuildable is a high-stakes professional act that cannot be walked back.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Raise the deficiencies privately with Engineer A and the owner in a pre-conference meeting before the formal pre-construction conference, allowing for a collaborative resolution process.
  • Submit a formal written notice of design deficiencies to the owner and Engineer A immediately upon contract award, before the pre-construction conference, creating an early and documented record.
  • Proceed with construction on the buildable portions while formally documenting the unbuildable sections as pending design resolution, managing risk incrementally rather than through a single dramatic declaration.

Narrative Role: climax

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Action_Raise_Unbuildable_Design_at_Pre-Construction",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Raise the deficiencies privately with Engineer A and the owner in a pre-conference meeting before the formal pre-construction conference, allowing for a collaborative resolution process.",
    "Submit a formal written notice of design deficiencies to the owner and Engineer A immediately upon contract award, before the pre-construction conference, creating an early and documented record.",
    "Proceed with construction on the buildable portions while formally documenting the unbuildable sections as pending design resolution, managing risk incrementally rather than through a single dramatic declaration."
  ],
  "proeth-scenario:characterMotivation": "By the pre-construction conference, Engineer C had contractual and financial skin in the game and could no longer defer the deficiency issue. Raising the unbuildable conditions was likely motivated by a combination of legitimate professional concern, self-protection from liability for executing an unsafe or unworkable design, and the practical need to establish a formal record of the design failures before construction began and cost disputes arose.",
  "proeth-scenario:consequencesIfAlternative": [
    "Private pre-conference discussion would allow Engineer A and the owner to begin remediation before the formal meeting, potentially avoiding the adversarial dynamic of a public declaration. However, it risks the concerns being minimized or suppressed without a formal record.",
    "Written notice immediately after award would create a clear, timestamped record of Engineer C\u0027s concerns, protect Hi-Lo Construction from liability, and give the owner maximum time to address the deficiencies before mobilization costs are incurred.",
    "Incremental construction with documented pending items might keep the project moving but risks compounding costs and safety issues if the unbuildable sections are foundational to the overall design. It also diffuses the urgency needed to force resolution."
  ],
  "proeth-scenario:decisionSignificance": "Demonstrates that disclosure of known deficiencies, while ethically required, is most valuable before harm propagates through the project lifecycle. Students learn that \u0027better late than never\u0027 is not an ethical standard \u2014 the timing of disclosure matters. However, this action also illustrates that even belated professional candor can prevent construction-phase catastrophes and is always preferable to continued silence.",
  "proeth-scenario:ethicalTension": "Professional duty to identify and disclose safety-threatening design deficiencies (NSPE Code Section III.2) \u2014 which Engineer C should have exercised at bid time \u2014 vs. the strategic timing of that disclosure to maximize contractual leverage after contract award. There is a tension between doing the right thing (disclosure) and doing it at the right time (before bidding). Late disclosure, while better than no disclosure, raises questions about Engineer C\u0027s earlier silence.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "climax",
  "proeth-scenario:stakes": "Worker safety during construction, structural integrity of the dam, project cost and schedule, the owner\u0027s ability to make informed decisions about proceeding, and the legal liability exposure of all parties. Declaring parts of the project unbuildable is a high-stakes professional act that cannot be walked back.",
  "proeth:description": "At the pre-construction conference, Engineer C formally identified major design deficiencies in the drawings and specifications and declared certain parts of the project unbuildable without major changes. This action brought the ethical crisis into public view among the project parties and triggered Engineer A\u0027s admission of incompleteness.",
  "proeth:foreseenUnintendedEffects": [
    "Exposure of Engineer A\u0027s incomplete work product",
    "Potential project delay, redesign, or contract dispute"
  ],
  "proeth:fulfillsObligation": [
    "Obligation to communicate known project deficiencies to the owner and design engineer before construction begins",
    "Obligation to protect the public interest by flagging conditions that could result in a failed or dangerous structure"
  ],
  "proeth:guidedByPrinciple": [
    "Honest communication",
    "Public safety",
    "Professional responsibility",
    "Protection of owner interests"
  ],
  "proeth:hasAgent": "Engineer C (Owner, Hi-Lo Construction)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Timely disclosure of deficiencies vs. protecting competitive bid position",
    "proeth:resolutionReasoning": "Engineer C chose to raise deficiencies after contract award rather than during bidding, which served Hi-Lo\u0027s competitive interests but delayed the disclosure that could have triggered redesign before bidding \u2014 a partially fulfilling but temporally late resolution"
  },
  "proeth:hasMentalState": "deliberate",
  "proeth:intendedOutcome": "Formally notify the project parties of the design deficiencies and protect Hi-Lo Construction\u0027s interests before construction commenced on an unbuildable project",
  "proeth:requiresCapability": [
    "Engineering evaluation of construction documents",
    "Construction sequencing and buildability assessment",
    "Professional communication of technical deficiencies"
  ],
  "proeth:temporalMarker": "Pre-construction conference, after contract award to Hi-Lo Construction",
  "proeth:violatesObligation": [
    "Obligation to have raised deficiencies earlier, during the bid phase, rather than after contract award"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Raise Unbuildable Design at Pre-Construction"
}

Description: At the pre-construction conference, Engineer A acknowledged that the drawings and specifications were incomplete and agreed with Hi-Lo Construction's characterization of unbuildable conditions, while deflecting responsibility onto time pressures and the assumption of federal funding coverage. This was the first disclosure of incompleteness to any project party.

Temporal Marker: Pre-construction conference, after contract award to Hi-Lo Construction

Mental State: reactive and self-protective

Intended Outcome: Acknowledge the deficiencies while minimizing personal professional and legal liability by attributing incompleteness to external pressures and financial assumptions

Fulfills Obligations:
  • Partial acknowledgment of design deficiencies to project parties
Guided By Principles:
  • Honesty
  • Transparency
  • Timely professional communication
  • Accountability
Required Capabilities:
Honest professional communication Accountability for work product Understanding of disclosure obligations under NSPE Code
Within Competence: Yes
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Character Motivation: Faced with a public, on-record declaration of unbuildable conditions by the contractor, Engineer A could no longer maintain the fiction of adequate documents. The admission was compelled by circumstances rather than chosen from integrity. Engineer A's simultaneous deflection onto time pressures and federal funding assumptions reflects a continued effort to minimize personal accountability even while conceding the factual reality of the deficiencies.

Ethical Tension: The obligation to be honest and take full professional responsibility for one's work product (NSPE Code Section II.3, III.2) vs. the human impulse toward self-protection, blame diffusion, and reputational damage control. There is also a tension between the partial honesty of admitting the incompleteness and the continued dishonesty of the deflection narrative, which misrepresents the ethical nature of the original decision.

Learning Significance: Illustrates that compelled disclosure under pressure is not equivalent to the proactive honesty the NSPE Code requires. Students learn to distinguish between reactive admission (ethically insufficient) and proactive disclosure (ethically required). The deflection component also teaches about the ethics of accountability: admitting a fact while denying responsibility for it is a form of continued ethical evasion. This moment models what not to do when confronted with professional failure.

Stakes: Engineer A's professional license, the resolution of the project's design deficiencies, the legal and financial exposure of all parties, the owner's ability to recover the project, and the broader public trust in the engineering profession. How Engineer A responds at this moment shapes the path to resolution and the magnitude of harm to the owner and public.

Decision Point: Yes - Story can branch here

Alternative Actions:
  • Provide a full, unqualified admission of responsibility — acknowledging that the documents were knowingly submitted incomplete, that no authorization existed for the federal funds rationalization, and committing to a specific remediation plan at no additional cost to the owner.
  • Proactively disclose the incompleteness to the owner and federal agency before the pre-construction conference, as soon as it became clear that the documents were deficient — avoiding the need for a reactive admission entirely.
  • At the pre-construction conference, immediately propose a concrete remediation plan — including a timeline for producing complete design documents, an offer to bear the cost of any resulting delays, and a commitment to work transparently with all parties — rather than leading with deflection.

Narrative Role: falling_action

RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Action_Admit_Incompleteness_Without_Prior_Disclosure",
  "@type": "proeth:Action",
  "proeth-scenario:alternativeActions": [
    "Provide a full, unqualified admission of responsibility \u2014 acknowledging that the documents were knowingly submitted incomplete, that no authorization existed for the federal funds rationalization, and committing to a specific remediation plan at no additional cost to the owner.",
    "Proactively disclose the incompleteness to the owner and federal agency before the pre-construction conference, as soon as it became clear that the documents were deficient \u2014 avoiding the need for a reactive admission entirely.",
    "At the pre-construction conference, immediately propose a concrete remediation plan \u2014 including a timeline for producing complete design documents, an offer to bear the cost of any resulting delays, and a commitment to work transparently with all parties \u2014 rather than leading with deflection."
  ],
  "proeth-scenario:characterMotivation": "Faced with a public, on-record declaration of unbuildable conditions by the contractor, Engineer A could no longer maintain the fiction of adequate documents. The admission was compelled by circumstances rather than chosen from integrity. Engineer A\u0027s simultaneous deflection onto time pressures and federal funding assumptions reflects a continued effort to minimize personal accountability even while conceding the factual reality of the deficiencies.",
  "proeth-scenario:consequencesIfAlternative": [
    "A full, unqualified admission with a remediation commitment would be the most professionally and ethically appropriate response. It would not eliminate Engineer A\u0027s liability but would demonstrate the integrity the NSPE Code requires and give the project the best chance of a constructive resolution. It would also model the professional accountability that distinguishes ethical engineers from those who merely comply when cornered.",
    "Proactive disclosure before the conference would have been the ideal intervention point \u2014 it would have prevented the adversarial dynamic of the pre-construction confrontation, preserved the owner\u0027s ability to make informed decisions, and demonstrated that Engineer A\u0027s professional obligations outweighed self-interest.",
    "Leading with a remediation plan rather than deflection would signal professional responsibility and a commitment to making the owner whole. It would shift the conversation from blame to resolution, reduce the likelihood of litigation, and partially rehabilitate Engineer A\u0027s professional standing."
  ],
  "proeth-scenario:decisionSignificance": "Illustrates that compelled disclosure under pressure is not equivalent to the proactive honesty the NSPE Code requires. Students learn to distinguish between reactive admission (ethically insufficient) and proactive disclosure (ethically required). The deflection component also teaches about the ethics of accountability: admitting a fact while denying responsibility for it is a form of continued ethical evasion. This moment models what not to do when confronted with professional failure.",
  "proeth-scenario:ethicalTension": "The obligation to be honest and take full professional responsibility for one\u0027s work product (NSPE Code Section II.3, III.2) vs. the human impulse toward self-protection, blame diffusion, and reputational damage control. There is also a tension between the partial honesty of admitting the incompleteness and the continued dishonesty of the deflection narrative, which misrepresents the ethical nature of the original decision.",
  "proeth-scenario:isDecisionPoint": true,
  "proeth-scenario:narrativeRole": "falling_action",
  "proeth-scenario:stakes": "Engineer A\u0027s professional license, the resolution of the project\u0027s design deficiencies, the legal and financial exposure of all parties, the owner\u0027s ability to recover the project, and the broader public trust in the engineering profession. How Engineer A responds at this moment shapes the path to resolution and the magnitude of harm to the owner and public.",
  "proeth:description": "At the pre-construction conference, Engineer A acknowledged that the drawings and specifications were incomplete and agreed with Hi-Lo Construction\u0027s characterization of unbuildable conditions, while deflecting responsibility onto time pressures and the assumption of federal funding coverage. This was the first disclosure of incompleteness to any project party.",
  "proeth:foreseenUnintendedEffects": [
    "Exposure of prior failure to disclose",
    "Potential professional disciplinary action",
    "Project delay and cost disputes"
  ],
  "proeth:fulfillsObligation": [
    "Partial acknowledgment of design deficiencies to project parties"
  ],
  "proeth:guidedByPrinciple": [
    "Honesty",
    "Transparency",
    "Timely professional communication",
    "Accountability"
  ],
  "proeth:hasAgent": "Engineer A (Private Design Engineer / Firm Principal)",
  "proeth:hasCompetingPriorities": {
    "@type": "proeth:CompetingPriorities",
    "proeth:priorityConflict": "Honest and timely disclosure vs. self-protection and reputation management",
    "proeth:resolutionReasoning": "Engineer A resolved the conflict by disclosing only when concealment became impossible, and framed the admission with blame-shifting justifications rather than taking full professional accountability \u2014 an ethically insufficient resolution that compounded the original violation"
  },
  "proeth:hasMentalState": "reactive and self-protective",
  "proeth:intendedOutcome": "Acknowledge the deficiencies while minimizing personal professional and legal liability by attributing incompleteness to external pressures and financial assumptions",
  "proeth:requiresCapability": [
    "Honest professional communication",
    "Accountability for work product",
    "Understanding of disclosure obligations under NSPE Code"
  ],
  "proeth:temporalMarker": "Pre-construction conference, after contract award to Hi-Lo Construction",
  "proeth:violatesObligation": [
    "Obligation to have disclosed incompleteness at the time of submission, not after contract award",
    "NSPE Code prohibition on deceptive acts \u2014 prior non-disclosure constituted ongoing deception",
    "Obligation of honest and timely communication with client and funding agency",
    "Obligation to avoid misrepresentation \u2014 the federal fund rationalization borders on fraud per the Discussion"
  ],
  "proeth:withinCompetence": true,
  "rdfs:label": "Admit Incompleteness Without Prior Disclosure"
}
Extracted Events (7)
Occurrences that trigger ethical considerations and state changes

Description: Engineer A's firm is awarded the dam design contract by the local public agency following evaluation of the submitted brochure and interview performance. This outcome formalizes Engineer A's professional and legal obligations to deliver complete, competent engineering work.

Temporal Marker: Early phase — after RFP response and interview evaluation

Activates Constraints:
  • Competence_Obligation_Constraint
  • Faithful_Service_to_Client_Constraint
  • Public_Safety_Paramount_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A experiences professional pride and optimism upon winning; agency feels confident in selection; public and downstream stakeholders are unaware but implicitly trusting the process to protect them

Stakeholder Consequences:
  • engineer_a: Gains revenue and reputational opportunity but also assumes full legal and ethical design responsibility
  • local_public_agency: Believes it has secured a qualified engineer; unknowingly relies on potentially misleading credentials presentation
  • public: Indirectly affected — their safety now depends on Engineer A's competence and integrity
  • federal_agency: Federal funds are now committed contingent on proper execution of the project

Learning Moment: Contract award is not merely a business transaction — it is the moment professional ethical obligations formally attach. Students should understand that winning a contract through impressive presentation creates binding duties of competence and honesty.

Ethical Implications: Reveals tension between competitive self-promotion and honest representation of capabilities; establishes the moment where professional duty to public safety supersedes commercial interest; raises questions about informed consent in client-engineer relationships

Discussion Prompts:
  • Does an impressive brochure and interview create an implicit representation of competence? What are the ethical consequences if that impression is misleading?
  • At the moment of contract award, what specific obligations does Engineer A now hold toward the agency, the public, and the federal government?
  • Should engineers decline contracts they cannot fully execute competently, even when the financial incentive is significant?
Tension: low Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Event_Contract_Award_to_Engineer_A",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "Does an impressive brochure and interview create an implicit representation of competence? What are the ethical consequences if that impression is misleading?",
    "At the moment of contract award, what specific obligations does Engineer A now hold toward the agency, the public, and the federal government?",
    "Should engineers decline contracts they cannot fully execute competently, even when the financial incentive is significant?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Engineer A experiences professional pride and optimism upon winning; agency feels confident in selection; public and downstream stakeholders are unaware but implicitly trusting the process to protect them",
  "proeth-scenario:ethicalImplications": "Reveals tension between competitive self-promotion and honest representation of capabilities; establishes the moment where professional duty to public safety supersedes commercial interest; raises questions about informed consent in client-engineer relationships",
  "proeth-scenario:learningMoment": "Contract award is not merely a business transaction \u2014 it is the moment professional ethical obligations formally attach. Students should understand that winning a contract through impressive presentation creates binding duties of competence and honesty.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Gains revenue and reputational opportunity but also assumes full legal and ethical design responsibility",
    "federal_agency": "Federal funds are now committed contingent on proper execution of the project",
    "local_public_agency": "Believes it has secured a qualified engineer; unknowingly relies on potentially misleading credentials presentation",
    "public": "Indirectly affected \u2014 their safety now depends on Engineer A\u0027s competence and integrity"
  },
  "proeth:activatesConstraint": [
    "Competence_Obligation_Constraint",
    "Faithful_Service_to_Client_Constraint",
    "Public_Safety_Paramount_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/85#Action_Respond_to_Dam_RFP",
  "proeth:causesStateChange": "Engineer A transitions from bidder to contracted professional; fiduciary and ethical duties to client and public formally commence",
  "proeth:createsObligation": [
    "Deliver_Complete_Design_Documents",
    "Disclose_Limitations_If_Discovered",
    "Maintain_Professional_Competence_Throughout_Project",
    "Protect_Public_Safety_in_Dam_Design"
  ],
  "proeth:description": "Engineer A\u0027s firm is awarded the dam design contract by the local public agency following evaluation of the submitted brochure and interview performance. This outcome formalizes Engineer A\u0027s professional and legal obligations to deliver complete, competent engineering work.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "Early phase \u2014 after RFP response and interview evaluation",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Contract Award to Engineer A"
}

Description: Federal grant funds are allocated as part of the dam project's financing structure, introducing a federal oversight dimension and creating the expectation — later exploited by Engineer A — that cost overruns might be absorbed by federal funds. This is an exogenous structural condition shaping subsequent actor behavior.

Temporal Marker: Pre-contract or concurrent with RFP issuance

Activates Constraints:
  • Federal_Oversight_Compliance_Constraint
  • Document_Review_Requirement_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Neutral at this stage for most actors; Engineer A may later view federal funding as a financial safety net, creating a morally hazardous sense of reduced personal accountability

Stakeholder Consequences:
  • engineer_a: Federal funding becomes a rationalization prop for submitting incomplete documents
  • engineer_b: Acquires formal review responsibility and the power to stop inadequate documents from advancing
  • local_public_agency: Gains project funding but also becomes subject to federal compliance requirements
  • taxpayers: Federal tax dollars are now at risk of misuse due to inadequate design oversight

Learning Moment: Funding structures are not ethically neutral — they create oversight obligations and can inadvertently generate moral hazards. Students should recognize how institutional arrangements shape individual ethical behavior.

Ethical Implications: Exposes how funding structures can create moral hazards; highlights the public trust dimension of federal funds; raises questions about institutional design and professional accountability

Discussion Prompts:
  • How does the presence of federal funding change the ethical obligations of each engineer in this case?
  • Is it ever ethically permissible to assume that institutional funding mechanisms will compensate for professional shortfalls?
  • What systemic safeguards should federal grant programs require to prevent the moral hazard Engineer A exploited?
Tension: low Pacing: slow_burn
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Event_Federal_Funding_Commitment_Established",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "How does the presence of federal funding change the ethical obligations of each engineer in this case?",
    "Is it ever ethically permissible to assume that institutional funding mechanisms will compensate for professional shortfalls?",
    "What systemic safeguards should federal grant programs require to prevent the moral hazard Engineer A exploited?"
  ],
  "proeth-scenario:dramaticTension": "low",
  "proeth-scenario:emotionalImpact": "Neutral at this stage for most actors; Engineer A may later view federal funding as a financial safety net, creating a morally hazardous sense of reduced personal accountability",
  "proeth-scenario:ethicalImplications": "Exposes how funding structures can create moral hazards; highlights the public trust dimension of federal funds; raises questions about institutional design and professional accountability",
  "proeth-scenario:learningMoment": "Funding structures are not ethically neutral \u2014 they create oversight obligations and can inadvertently generate moral hazards. Students should recognize how institutional arrangements shape individual ethical behavior.",
  "proeth-scenario:narrativePacing": "slow_burn",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Federal funding becomes a rationalization prop for submitting incomplete documents",
    "engineer_b": "Acquires formal review responsibility and the power to stop inadequate documents from advancing",
    "local_public_agency": "Gains project funding but also becomes subject to federal compliance requirements",
    "taxpayers": "Federal tax dollars are now at risk of misuse due to inadequate design oversight"
  },
  "proeth:activatesConstraint": [
    "Federal_Oversight_Compliance_Constraint",
    "Document_Review_Requirement_Constraint"
  ],
  "proeth:causesStateChange": "Project gains federal oversight layer; Engineer B\u0027s review role becomes mandatory; federal standards for completeness apply to design documents",
  "proeth:createsObligation": [
    "Engineer_B_Must_Conduct_Thorough_Document_Review",
    "Engineer_A_Must_Meet_Federal_Standards",
    "Agency_Must_Ensure_Proper_Use_of_Federal_Funds"
  ],
  "proeth:description": "Federal grant funds are allocated as part of the dam project\u0027s financing structure, introducing a federal oversight dimension and creating the expectation \u2014 later exploited by Engineer A \u2014 that cost overruns might be absorbed by federal funds. This is an exogenous structural condition shaping subsequent actor behavior.",
  "proeth:emergencyStatus": "routine",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "Pre-contract or concurrent with RFP issuance",
  "proeth:urgencyLevel": "low",
  "rdfs:label": "Federal Funding Commitment Established"
}

Description: Significant time pressure develops during Engineer A's design phase, creating conditions under which completeness of drawings and specifications is compromised. This environmental constraint becomes the primary rationalization Engineer A later invokes for submitting incomplete documents.

Temporal Marker: During design production phase, prior to document submission

Activates Constraints:
  • Disclosure_Obligation_If_Unable_to_Perform_Constraint
  • Competence_Maintenance_Constraint
  • Client_Communication_Obligation_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer A likely experiences stress, anxiety, and rationalization; may feel trapped between professional reputation and schedule compliance; client agency is unaware of the pressure and its implications

Stakeholder Consequences:
  • engineer_a: Faces a critical ethical decision point; chooses expediency over integrity
  • local_public_agency: Unaware that schedule pressure is degrading design quality
  • engineer_b: Will subsequently receive documents whose incompleteness is partly attributable to this condition
  • public: Safety risk begins to materialize as design quality degrades under pressure

Learning Moment: Time pressure is a common real-world constraint but never justifies knowingly submitting incomplete work. Students should learn that professional obligations require disclosure and renegotiation, not silent compromise of quality.

Ethical Implications: Illustrates the classic tension between commercial/schedule pressures and professional duty; reveals how systemic workplace pressures can normalize ethical compromise; raises questions about organizational culture and individual responsibility

Discussion Prompts:
  • When a professional faces time pressure that threatens work quality, what are their ethical options beyond simply submitting incomplete work?
  • Does time pressure ever mitigate moral responsibility for submitting incomplete engineering documents? Why or why not?
  • How should engineering firms structure project management to prevent time pressure from becoming a driver of ethical violations?
Tension: medium Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Event_Time_Pressure_Condition_Emerges",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "When a professional faces time pressure that threatens work quality, what are their ethical options beyond simply submitting incomplete work?",
    "Does time pressure ever mitigate moral responsibility for submitting incomplete engineering documents? Why or why not?",
    "How should engineering firms structure project management to prevent time pressure from becoming a driver of ethical violations?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer A likely experiences stress, anxiety, and rationalization; may feel trapped between professional reputation and schedule compliance; client agency is unaware of the pressure and its implications",
  "proeth-scenario:ethicalImplications": "Illustrates the classic tension between commercial/schedule pressures and professional duty; reveals how systemic workplace pressures can normalize ethical compromise; raises questions about organizational culture and individual responsibility",
  "proeth-scenario:learningMoment": "Time pressure is a common real-world constraint but never justifies knowingly submitting incomplete work. Students should learn that professional obligations require disclosure and renegotiation, not silent compromise of quality.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Faces a critical ethical decision point; chooses expediency over integrity",
    "engineer_b": "Will subsequently receive documents whose incompleteness is partly attributable to this condition",
    "local_public_agency": "Unaware that schedule pressure is degrading design quality",
    "public": "Safety risk begins to materialize as design quality degrades under pressure"
  },
  "proeth:activatesConstraint": [
    "Disclosure_Obligation_If_Unable_to_Perform_Constraint",
    "Competence_Maintenance_Constraint",
    "Client_Communication_Obligation_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/85#Action_Respond_to_Dam_RFP",
  "proeth:causesStateChange": "Design production environment becomes constrained; decision point arises for Engineer A between honest disclosure and concealed submission",
  "proeth:createsObligation": [
    "Notify_Client_of_Schedule_Risk",
    "Request_Timeline_Extension_If_Needed",
    "Disclose_Incompleteness_Before_Submission",
    "Decline_or_Renegotiate_If_Quality_Cannot_Be_Maintained"
  ],
  "proeth:description": "Significant time pressure develops during Engineer A\u0027s design phase, creating conditions under which completeness of drawings and specifications is compromised. This environmental constraint becomes the primary rationalization Engineer A later invokes for submitting incomplete documents.",
  "proeth:emergencyStatus": "medium",
  "proeth:eventType": "exogenous",
  "proeth:temporalMarker": "During design production phase, prior to document submission",
  "proeth:urgencyLevel": "medium",
  "rdfs:label": "Time Pressure Condition Emerges"
}

Description: Engineer A's knowingly incomplete drawings and specifications are formally received by the federal agency, entering Engineer B's review queue. This event transfers the immediate gatekeeping responsibility to Engineer B and marks the point at which the design deficiency becomes an institutional rather than solely individual problem.

Temporal Marker: After Engineer A's submission; beginning of federal review phase

Activates Constraints:
  • Thorough_Technical_Review_Constraint
  • Public_Safety_Gatekeeping_Constraint
  • Engineer_B_Independent_Judgment_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer B may feel routine professional responsibility at receipt; Engineer A may feel relief at having passed the immediate deadline; the agency remains unaware of the quality problem embedded in the submission

Stakeholder Consequences:
  • engineer_b: Now bears critical responsibility to catch what Engineer A concealed; failure to do so will make Engineer B complicit
  • engineer_a: Momentarily relieved of immediate pressure but ethical violation is now compounded by concealment
  • federal_agency: Institutional credibility is now at risk if review fails
  • public: Safety protection now depends entirely on Engineer B's thoroughness

Learning Moment: Independent review is a critical systemic safeguard — but it only works if the reviewer exercises genuine independent judgment. Students should understand that review roles carry their own ethical obligations, not merely procedural ones.

Ethical Implications: Highlights the ethics of institutional gatekeeping; reveals how systemic review processes can fail when treated as procedural formalities rather than substantive safety checks; raises questions about diffusion of responsibility in multi-party oversight systems

Discussion Prompts:
  • What specific actions should Engineer B take upon receiving design documents for a dam project, and how thorough must that review be?
  • Does Engineer B's role as a federal reviewer create a higher standard of care than a typical peer reviewer? Why?
  • If Engineer B lacks the time or expertise to conduct a thorough review, what are their ethical obligations?
Crisis / Turning Point Tension: high Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Event_Incomplete_Documents_Enter_Review",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What specific actions should Engineer B take upon receiving design documents for a dam project, and how thorough must that review be?",
    "Does Engineer B\u0027s role as a federal reviewer create a higher standard of care than a typical peer reviewer? Why?",
    "If Engineer B lacks the time or expertise to conduct a thorough review, what are their ethical obligations?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer B may feel routine professional responsibility at receipt; Engineer A may feel relief at having passed the immediate deadline; the agency remains unaware of the quality problem embedded in the submission",
  "proeth-scenario:ethicalImplications": "Highlights the ethics of institutional gatekeeping; reveals how systemic review processes can fail when treated as procedural formalities rather than substantive safety checks; raises questions about diffusion of responsibility in multi-party oversight systems",
  "proeth-scenario:learningMoment": "Independent review is a critical systemic safeguard \u2014 but it only works if the reviewer exercises genuine independent judgment. Students should understand that review roles carry their own ethical obligations, not merely procedural ones.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_a": "Momentarily relieved of immediate pressure but ethical violation is now compounded by concealment",
    "engineer_b": "Now bears critical responsibility to catch what Engineer A concealed; failure to do so will make Engineer B complicit",
    "federal_agency": "Institutional credibility is now at risk if review fails",
    "public": "Safety protection now depends entirely on Engineer B\u0027s thoroughness"
  },
  "proeth:activatesConstraint": [
    "Thorough_Technical_Review_Constraint",
    "Public_Safety_Gatekeeping_Constraint",
    "Engineer_B_Independent_Judgment_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/85#Action_Submit_Incomplete_Design_Documents",
  "proeth:causesStateChange": "Design deficiency propagates from Engineer A\u0027s firm into the federal review system; Engineer B now holds the critical gatekeeping role that could halt or allow project advancement",
  "proeth:createsObligation": [
    "Engineer_B_Must_Review_Thoroughly_and_Independently",
    "Engineer_B_Must_Identify_Deficiencies",
    "Engineer_B_Must_Reject_or_Return_Incomplete_Documents",
    "Engineer_B_Must_Not_Rubber_Stamp_Submissions"
  ],
  "proeth:description": "Engineer A\u0027s knowingly incomplete drawings and specifications are formally received by the federal agency, entering Engineer B\u0027s review queue. This event transfers the immediate gatekeeping responsibility to Engineer B and marks the point at which the design deficiency becomes an institutional rather than solely individual problem.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After Engineer A\u0027s submission; beginning of federal review phase",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Incomplete Documents Enter Review"
}

Description: Engineer B approves Engineer A's incomplete design documents, allowing the project to advance to the bidding phase despite unresolved design deficiencies. This outcome represents a critical failure of the federal oversight mechanism and compounds the original ethical violation.

Temporal Marker: End of federal review phase; prior to bid advertisement

Activates Constraints:
  • Public_Safety_Paramount_Constraint
  • Downstream_Harm_Prevention_Constraint
  • Contractor_Reliance_Protection_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer B may feel routine satisfaction at completing a review; Engineer A may feel emboldened that concealment succeeded; future contractors and the public remain unaware that a critical safety check has failed

Stakeholder Consequences:
  • engineer_b: Professional integrity compromised; becomes complicit in the downstream consequences of inadequate review
  • engineer_a: Concealment appears to have succeeded, potentially reinforcing unethical behavior
  • local_public_agency: Proceeds in good faith on approved documents, unaware of embedded risk
  • contractors: Will soon be asked to bid on documents that cannot support accurate cost estimation
  • public: Safety risk is now locked into the project's institutional trajectory

Learning Moment: Approval by a reviewing authority does not absolve the original designer of responsibility, nor does it substitute for genuine independent review. Students should understand that rubber-stamping is an ethical violation in its own right.

Ethical Implications: Reveals the ethics of institutional complicity; demonstrates how review failures amplify original violations; raises questions about the diffusion of responsibility across multi-party approval chains and the moral weight of institutional endorsement

Discussion Prompts:
  • What specific technical checks should Engineer B have performed that would have revealed the incompleteness?
  • Does Engineer B's approval of the documents make Engineer B morally responsible for subsequent harms, even if Engineer A was the primary wrongdoer?
  • How should federal agencies structure engineering review processes to prevent superficial approvals?
Crisis / Turning Point Tension: high Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Event_Deficient_Documents_Approved",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": true,
  "proeth-scenario:discussionPrompts": [
    "What specific technical checks should Engineer B have performed that would have revealed the incompleteness?",
    "Does Engineer B\u0027s approval of the documents make Engineer B morally responsible for subsequent harms, even if Engineer A was the primary wrongdoer?",
    "How should federal agencies structure engineering review processes to prevent superficial approvals?"
  ],
  "proeth-scenario:dramaticTension": "high",
  "proeth-scenario:emotionalImpact": "Engineer B may feel routine satisfaction at completing a review; Engineer A may feel emboldened that concealment succeeded; future contractors and the public remain unaware that a critical safety check has failed",
  "proeth-scenario:ethicalImplications": "Reveals the ethics of institutional complicity; demonstrates how review failures amplify original violations; raises questions about the diffusion of responsibility across multi-party approval chains and the moral weight of institutional endorsement",
  "proeth-scenario:learningMoment": "Approval by a reviewing authority does not absolve the original designer of responsibility, nor does it substitute for genuine independent review. Students should understand that rubber-stamping is an ethical violation in its own right.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "contractors": "Will soon be asked to bid on documents that cannot support accurate cost estimation",
    "engineer_a": "Concealment appears to have succeeded, potentially reinforcing unethical behavior",
    "engineer_b": "Professional integrity compromised; becomes complicit in the downstream consequences of inadequate review",
    "local_public_agency": "Proceeds in good faith on approved documents, unaware of embedded risk",
    "public": "Safety risk is now locked into the project\u0027s institutional trajectory"
  },
  "proeth:activatesConstraint": [
    "Public_Safety_Paramount_Constraint",
    "Downstream_Harm_Prevention_Constraint",
    "Contractor_Reliance_Protection_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/85#Action_Approve_Incomplete_Design_Documents",
  "proeth:causesStateChange": "Design deficiency is institutionally legitimized; project advances to bidding on false foundation; downstream actors (contractors, public) now bear risk created by dual professional failures",
  "proeth:createsObligation": [
    "Agency_Must_Ensure_Bid_Documents_Are_Complete",
    "Future_Obligation_to_Correct_Deficiencies_Before_Construction",
    "Engineer_B_Retrospective_Obligation_to_Acknowledge_Review_Failure"
  ],
  "proeth:description": "Engineer B approves Engineer A\u0027s incomplete design documents, allowing the project to advance to the bidding phase despite unresolved design deficiencies. This outcome represents a critical failure of the federal oversight mechanism and compounds the original ethical violation.",
  "proeth:emergencyStatus": "critical",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "End of federal review phase; prior to bid advertisement",
  "proeth:urgencyLevel": "critical",
  "rdfs:label": "Deficient Documents Approved"
}

Description: The dam project is publicly advertised for contractor bids using the approved but incomplete design documents, formally inviting contractors to submit binding price commitments based on deficient information. This event propagates the design deficiency into the competitive bidding market.

Temporal Marker: After federal approval; prior to bid submission deadline

Activates Constraints:
  • Bid_Document_Accuracy_Constraint
  • Contractor_Reliance_Protection_Constraint
  • Public_Procurement_Integrity_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Agency feels procedural progress; contractors view advertisement as a normal business opportunity; the public remains unaware; Engineer A may feel increasing anxiety as the deficiency moves closer to exposure

Stakeholder Consequences:
  • contractors: Now exposed to financial risk of bidding on incomplete documents without knowing it
  • engineer_c_hi_lo: Will soon commit significant estimating resources to a flawed bid process
  • local_public_agency: Committed to a procurement process built on a deficient foundation
  • public: Project momentum now makes correction increasingly costly and difficult

Learning Moment: Public bid advertisement is a point of no easy return — once contractors invest in bidding, the cost of correction escalates. Students should understand that design integrity must be ensured before procurement begins, not after.

Ethical Implications: Illustrates how professional failures cascade through institutional processes; reveals the ethics of public procurement reliance; raises questions about when correction obligations become disclosure obligations

Discussion Prompts:
  • At what point in the procurement process does it become too late for Engineer A to correct the ethical violation without causing serious harm?
  • What obligations does the agency have to verify document completeness before advertising for bids?
  • How does the public bidding process create reliance interests that amplify the harm from incomplete design documents?
Tension: medium Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Event_Project_Advertised_for_Bids",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "At what point in the procurement process does it become too late for Engineer A to correct the ethical violation without causing serious harm?",
    "What obligations does the agency have to verify document completeness before advertising for bids?",
    "How does the public bidding process create reliance interests that amplify the harm from incomplete design documents?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Agency feels procedural progress; contractors view advertisement as a normal business opportunity; the public remains unaware; Engineer A may feel increasing anxiety as the deficiency moves closer to exposure",
  "proeth-scenario:ethicalImplications": "Illustrates how professional failures cascade through institutional processes; reveals the ethics of public procurement reliance; raises questions about when correction obligations become disclosure obligations",
  "proeth-scenario:learningMoment": "Public bid advertisement is a point of no easy return \u2014 once contractors invest in bidding, the cost of correction escalates. Students should understand that design integrity must be ensured before procurement begins, not after.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "contractors": "Now exposed to financial risk of bidding on incomplete documents without knowing it",
    "engineer_c_hi_lo": "Will soon commit significant estimating resources to a flawed bid process",
    "local_public_agency": "Committed to a procurement process built on a deficient foundation",
    "public": "Project momentum now makes correction increasingly costly and difficult"
  },
  "proeth:activatesConstraint": [
    "Bid_Document_Accuracy_Constraint",
    "Contractor_Reliance_Protection_Constraint",
    "Public_Procurement_Integrity_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/85#Action_Approve_Incomplete_Design_Documents",
  "proeth:causesStateChange": "Incomplete documents become the public basis for contractor pricing; market actors are now exposed to financial risk from hidden design deficiencies; the deficiency\u0027s impact radius expands from design team to competitive market",
  "proeth:createsObligation": [
    "Agency_Must_Provide_Accurate_Bid_Documents",
    "Engineer_A_Ongoing_Obligation_to_Disclose_Known_Deficiencies",
    "Contractors_Entitled_to_Rely_on_Advertised_Documents"
  ],
  "proeth:description": "The dam project is publicly advertised for contractor bids using the approved but incomplete design documents, formally inviting contractors to submit binding price commitments based on deficient information. This event propagates the design deficiency into the competitive bidding market.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After federal approval; prior to bid submission deadline",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Project Advertised for Bids"
}

Description: Engineer C's firm, Hi-Lo Construction, submits the lowest bid and is awarded the construction contract, formally committing to build a project based on documents that are materially incomplete. This outcome locks Engineer C into a contractual relationship built on a deficient foundation.

Temporal Marker: After bid submission deadline; prior to pre-construction conference

Activates Constraints:
  • Contractor_Reliance_Protection_Constraint
  • Engineer_C_Professional_Obligation_Constraint
  • Public_Safety_in_Construction_Constraint
Scenario Metadata
Pedagogical context for interactive teaching scenarios

Emotional Impact: Engineer C initially feels competitive satisfaction at winning; agency feels procurement progress; Engineer A may feel growing dread as construction scrutiny approaches; the public remains unaware

Stakeholder Consequences:
  • engineer_c: Financially and legally committed to a project with hidden design flaws; will soon discover the extent of the problem
  • hi_lo_construction: Business resources committed; potential for significant financial loss if design requires major revision
  • local_public_agency: Procurement appears successful on the surface; unaware of impending crisis
  • public: Now one step closer to a construction project that may not be safely buildable as designed

Learning Moment: Contract award to a low bidder on deficient documents creates a chain of harm that extends from the designer's original failure through to the contractor's financial exposure. Students should understand that procurement integrity depends on design integrity.

Ethical Implications: Reveals how design failures create downstream financial and safety risks for contractors; raises questions about contractor due diligence obligations; illustrates the cascading harm structure of professional ethical violations

Discussion Prompts:
  • What due diligence should Engineer C have performed on the design documents before submitting a bid?
  • Does winning a contract on deficient documents give Engineer C any ethical or legal recourse against Engineer A?
  • How does the competitive bidding structure create pressure on contractors that may inadvertently expose design deficiencies?
Tension: medium Pacing: escalation
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#Event_Hi-Lo_Wins_Construction_Contract",
  "@type": "proeth:Event",
  "proeth-scenario:crisisIdentification": false,
  "proeth-scenario:discussionPrompts": [
    "What due diligence should Engineer C have performed on the design documents before submitting a bid?",
    "Does winning a contract on deficient documents give Engineer C any ethical or legal recourse against Engineer A?",
    "How does the competitive bidding structure create pressure on contractors that may inadvertently expose design deficiencies?"
  ],
  "proeth-scenario:dramaticTension": "medium",
  "proeth-scenario:emotionalImpact": "Engineer C initially feels competitive satisfaction at winning; agency feels procurement progress; Engineer A may feel growing dread as construction scrutiny approaches; the public remains unaware",
  "proeth-scenario:ethicalImplications": "Reveals how design failures create downstream financial and safety risks for contractors; raises questions about contractor due diligence obligations; illustrates the cascading harm structure of professional ethical violations",
  "proeth-scenario:learningMoment": "Contract award to a low bidder on deficient documents creates a chain of harm that extends from the designer\u0027s original failure through to the contractor\u0027s financial exposure. Students should understand that procurement integrity depends on design integrity.",
  "proeth-scenario:narrativePacing": "escalation",
  "proeth-scenario:stakeholderConsequences": {
    "engineer_c": "Financially and legally committed to a project with hidden design flaws; will soon discover the extent of the problem",
    "hi_lo_construction": "Business resources committed; potential for significant financial loss if design requires major revision",
    "local_public_agency": "Procurement appears successful on the surface; unaware of impending crisis",
    "public": "Now one step closer to a construction project that may not be safely buildable as designed"
  },
  "proeth:activatesConstraint": [
    "Contractor_Reliance_Protection_Constraint",
    "Engineer_C_Professional_Obligation_Constraint",
    "Public_Safety_in_Construction_Constraint"
  ],
  "proeth:causedByAction": "http://proethica.org/cases/85#Action_Submit_Low_Bid_on_Inadequate_Documents",
  "proeth:causesStateChange": "Engineer C assumes contractual and professional responsibility for construction; deficiency exposure risk intensifies as construction planning begins in earnest",
  "proeth:createsObligation": [
    "Engineer_C_Must_Review_Documents_Thoroughly_Before_Construction",
    "Engineer_C_Must_Raise_Design_Deficiencies_If_Found",
    "Engineer_C_Must_Not_Build_Unbuildable_Design_Without_Resolution"
  ],
  "proeth:description": "Engineer C\u0027s firm, Hi-Lo Construction, submits the lowest bid and is awarded the construction contract, formally committing to build a project based on documents that are materially incomplete. This outcome locks Engineer C into a contractual relationship built on a deficient foundation.",
  "proeth:emergencyStatus": "high",
  "proeth:eventType": "outcome",
  "proeth:temporalMarker": "After bid submission deadline; prior to pre-construction conference",
  "proeth:urgencyLevel": "high",
  "rdfs:label": "Hi-Lo Wins Construction Contract"
}
Causal Chains (5)
NESS test analysis: Necessary Element of Sufficient Set

Causal Language: Engineer A knowingly submitted incomplete drawings and specifications by the specified deadline, which were formally received by the federal agency for review

Necessary Factors (NESS):
  • Engineer A's deliberate decision to submit despite known incompleteness
  • Existence of a submission deadline creating time pressure
  • Federal review process requiring document receipt before approval
Sufficient Factors:
  • Knowing submission of incomplete documents + active deadline + federal review gateway = documents entering review in deficient state
Counterfactual Test: Had Engineer A declined to submit until documents were complete, or requested a deadline extension, incomplete documents would not have entered the federal review pipeline
Responsibility Attribution:

Agent: Engineer A
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Time Pressure Condition Emerges (Event 3)
    Significant time pressure develops during Engineer A's design phase, creating conditions conducive to cutting corners
  2. Rationalize Incompleteness via Federal Funds (Action 3)
    Engineer A internally justifies proceeding by assuming federal oversight will compensate for deficiencies
  3. Submit Incomplete Design Documents (Action 2)
    Engineer A knowingly submits deficient drawings and specifications by the deadline
  4. Incomplete Documents Enter Review (Event 4)
    Deficient documents are formally received by the federal agency, entering the official review process
  5. Deficient Documents Approved (Event 5)
    Federal review passes incomplete documents forward, validating their use in the procurement process
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#CausalChain_4ae6574e",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A knowingly submitted incomplete drawings and specifications by the specified deadline, which were formally received by the federal agency for review",
  "proeth:causalSequence": [
    {
      "proeth:description": "Significant time pressure develops during Engineer A\u0027s design phase, creating conditions conducive to cutting corners",
      "proeth:element": "Time Pressure Condition Emerges (Event 3)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A internally justifies proceeding by assuming federal oversight will compensate for deficiencies",
      "proeth:element": "Rationalize Incompleteness via Federal Funds (Action 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer A knowingly submits deficient drawings and specifications by the deadline",
      "proeth:element": "Submit Incomplete Design Documents (Action 2)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Deficient documents are formally received by the federal agency, entering the official review process",
      "proeth:element": "Incomplete Documents Enter Review (Event 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Federal review passes incomplete documents forward, validating their use in the procurement process",
      "proeth:element": "Deficient Documents Approved (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Submit Incomplete Design Documents (Action 2)",
  "proeth:counterfactual": "Had Engineer A declined to submit until documents were complete, or requested a deadline extension, incomplete documents would not have entered the federal review pipeline",
  "proeth:effect": "Incomplete Documents Enter Review (Event 4)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s deliberate decision to submit despite known incompleteness",
    "Existence of a submission deadline creating time pressure",
    "Federal review process requiring document receipt before approval"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer A",
  "proeth:sufficientFactors": [
    "Knowing submission of incomplete documents + active deadline + federal review gateway = documents entering review in deficient state"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer A internally justified submitting incomplete documents by assuming that federal funds would trigger a more rigorous review process, creating a false expectation that Engineer B's approval would serve as a corrective gate

Necessary Factors (NESS):
  • Engineer A's flawed assumption that federal review would catch and remediate deficiencies
  • Engineer B's failure to reject or flag incomplete documents during review
  • Absence of a mandatory completeness standard enforced at the federal review stage
Sufficient Factors:
  • Flawed rationalization by Engineer A + inadequate federal review rigor by Engineer B = deficient documents advancing through approval without correction
Counterfactual Test: Had Engineer A not rationalized the incompleteness, complete documents would have been submitted; alternatively, had Engineer B applied rigorous review standards, incomplete documents would have been rejected regardless of Engineer A's rationalization
Responsibility Attribution:

Agent: Engineer A (primary); Engineer B (secondary)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Federal Funding Commitment Established (Event 2)
    Federal grant funds are allocated, introducing a federal review layer that Engineer A later misinterprets as a corrective mechanism
  2. Rationalize Incompleteness via Federal Funds (Action 3)
    Engineer A uses the existence of federal oversight as internal justification for submitting incomplete work
  3. Incomplete Documents Enter Review (Event 4)
    Deficient documents are formally submitted and received by Engineer B's federal agency
  4. Approve Incomplete Design Documents (Action 4)
    Engineer B reviews and approves documents without identifying or rejecting the known incompleteness
  5. Deficient Documents Approved (Event 5)
    Official federal approval is granted, lending false legitimacy to incomplete design documents and enabling project advancement
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#CausalChain_9d5d0240",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer A internally justified submitting incomplete documents by assuming that federal funds would trigger a more rigorous review process, creating a false expectation that Engineer B\u0027s approval would serve as a corrective gate",
  "proeth:causalSequence": [
    {
      "proeth:description": "Federal grant funds are allocated, introducing a federal review layer that Engineer A later misinterprets as a corrective mechanism",
      "proeth:element": "Federal Funding Commitment Established (Event 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer A uses the existence of federal oversight as internal justification for submitting incomplete work",
      "proeth:element": "Rationalize Incompleteness via Federal Funds (Action 3)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Deficient documents are formally submitted and received by Engineer B\u0027s federal agency",
      "proeth:element": "Incomplete Documents Enter Review (Event 4)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer B reviews and approves documents without identifying or rejecting the known incompleteness",
      "proeth:element": "Approve Incomplete Design Documents (Action 4)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Official federal approval is granted, lending false legitimacy to incomplete design documents and enabling project advancement",
      "proeth:element": "Deficient Documents Approved (Event 5)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Rationalize Incompleteness via Federal Funds (Action 3)",
  "proeth:counterfactual": "Had Engineer A not rationalized the incompleteness, complete documents would have been submitted; alternatively, had Engineer B applied rigorous review standards, incomplete documents would have been rejected regardless of Engineer A\u0027s rationalization",
  "proeth:effect": "Deficient Documents Approved (Event 5)",
  "proeth:necessaryFactors": [
    "Engineer A\u0027s flawed assumption that federal review would catch and remediate deficiencies",
    "Engineer B\u0027s failure to reject or flag incomplete documents during review",
    "Absence of a mandatory completeness standard enforced at the federal review stage"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (primary); Engineer B (secondary)",
  "proeth:sufficientFactors": [
    "Flawed rationalization by Engineer A + inadequate federal review rigor by Engineer B = deficient documents advancing through approval without correction"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer B, acting on behalf of the federal funding agency, reviewed and approved Engineer A's incomplete design documents, allowing the project to advance to the bidding stage using deficient construction documents

Necessary Factors (NESS):
  • Engineer B's affirmative approval decision
  • Federal approval being a prerequisite gate for project advertisement
  • Absence of a rejection or conditional approval requiring remediation
Sufficient Factors:
  • Federal approval granted on incomplete documents + no corrective condition attached = project legally and procedurally cleared for public bid advertisement
Counterfactual Test: Without Engineer B's approval, the project could not have been advertised for bids; rejection would have forced remediation of design deficiencies before contractor solicitation
Responsibility Attribution:

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

Causal Sequence:
  1. Incomplete Documents Enter Review (Event 4)
    Deficient design documents are formally submitted to the federal agency for Engineer B's review
  2. Approve Incomplete Design Documents (Action 4)
    Engineer B approves documents without identifying or requiring correction of known deficiencies
  3. Deficient Documents Approved (Event 5)
    Official approval is recorded, clearing the project for the next phase
  4. Project Advertised for Bids (Event 6)
    The dam project is publicly advertised using approved but incomplete design documents as the basis for contractor bids
  5. Hi-Lo Wins Construction Contract (Event 7)
    Engineer C submits the lowest bid on inadequate documents and is awarded the construction contract, inheriting the design deficiencies
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#CausalChain_9d31dbf8",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer B, acting on behalf of the federal funding agency, reviewed and approved Engineer A\u0027s incomplete design documents, allowing the project to advance to the bidding stage using deficient construction documents",
  "proeth:causalSequence": [
    {
      "proeth:description": "Deficient design documents are formally submitted to the federal agency for Engineer B\u0027s review",
      "proeth:element": "Incomplete Documents Enter Review (Event 4)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer B approves documents without identifying or requiring correction of known deficiencies",
      "proeth:element": "Approve Incomplete Design Documents (Action 4)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Official approval is recorded, clearing the project for the next phase",
      "proeth:element": "Deficient Documents Approved (Event 5)",
      "proeth:step": 3
    },
    {
      "proeth:description": "The dam project is publicly advertised using approved but incomplete design documents as the basis for contractor bids",
      "proeth:element": "Project Advertised for Bids (Event 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer C submits the lowest bid on inadequate documents and is awarded the construction contract, inheriting the design deficiencies",
      "proeth:element": "Hi-Lo Wins Construction Contract (Event 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Approve Incomplete Design Documents (Action 4)",
  "proeth:counterfactual": "Without Engineer B\u0027s approval, the project could not have been advertised for bids; rejection would have forced remediation of design deficiencies before contractor solicitation",
  "proeth:effect": "Project Advertised for Bids (Event 6)",
  "proeth:necessaryFactors": [
    "Engineer B\u0027s affirmative approval decision",
    "Federal approval being a prerequisite gate for project advertisement",
    "Absence of a rejection or conditional approval requiring remediation"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer B",
  "proeth:sufficientFactors": [
    "Federal approval granted on incomplete documents + no corrective condition attached = project legally and procedurally cleared for public bid advertisement"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: Engineer C, as owner of Hi-Lo Construction, submitted the low bid on the project despite possessing knowledge of the design documents' inadequacy, resulting in Hi-Lo being awarded the construction contract

Necessary Factors (NESS):
  • Engineer C's decision to submit a bid despite recognizing document inadequacy
  • Hi-Lo's bid being the lowest among all submitted bids
  • Award criteria favoring lowest bid under public procurement rules
Sufficient Factors:
  • Submission of lowest bid on publicly advertised project + standard low-bid award criteria = contract award to Hi-Lo regardless of document quality concerns
Counterfactual Test: Had Engineer C declined to bid or formally notified the agency of design deficiencies before bidding, either no award would have been made or the agency would have been compelled to address deficiencies prior to award
Responsibility Attribution:

Agent: Engineer C
Type: direct
Within Agent Control: Yes

Causal Sequence:
  1. Project Advertised for Bids (Event 6)
    Dam project is publicly advertised using approved but incomplete design documents
  2. Submit Low Bid on Inadequate Documents (Action 5)
    Engineer C submits the lowest bid despite recognizing the design documents are inadequate for construction
  3. Hi-Lo Wins Construction Contract (Event 7)
    Hi-Lo Construction is awarded the contract as low bidder, inheriting responsibility to build from deficient documents
  4. Raise Unbuildable Design at Pre-Construction (Action 6)
    Engineer C formally identifies major design deficiencies at the pre-construction conference, after contract award
  5. Admit Incompleteness Without Prior Disclosure (Action 7)
    Engineer A acknowledges at the pre-construction conference that drawings were incomplete, confirming what Engineer C identified
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#CausalChain_0ed07271",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "Engineer C, as owner of Hi-Lo Construction, submitted the low bid on the project despite possessing knowledge of the design documents\u0027 inadequacy, resulting in Hi-Lo being awarded the construction contract",
  "proeth:causalSequence": [
    {
      "proeth:description": "Dam project is publicly advertised using approved but incomplete design documents",
      "proeth:element": "Project Advertised for Bids (Event 6)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer C submits the lowest bid despite recognizing the design documents are inadequate for construction",
      "proeth:element": "Submit Low Bid on Inadequate Documents (Action 5)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Hi-Lo Construction is awarded the contract as low bidder, inheriting responsibility to build from deficient documents",
      "proeth:element": "Hi-Lo Wins Construction Contract (Event 7)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer C formally identifies major design deficiencies at the pre-construction conference, after contract award",
      "proeth:element": "Raise Unbuildable Design at Pre-Construction (Action 6)",
      "proeth:step": 4
    },
    {
      "proeth:description": "Engineer A acknowledges at the pre-construction conference that drawings were incomplete, confirming what Engineer C identified",
      "proeth:element": "Admit Incompleteness Without Prior Disclosure (Action 7)",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Submit Low Bid on Inadequate Documents (Action 5)",
  "proeth:counterfactual": "Had Engineer C declined to bid or formally notified the agency of design deficiencies before bidding, either no award would have been made or the agency would have been compelled to address deficiencies prior to award",
  "proeth:effect": "Hi-Lo Wins Construction Contract (Event 7)",
  "proeth:necessaryFactors": [
    "Engineer C\u0027s decision to submit a bid despite recognizing document inadequacy",
    "Hi-Lo\u0027s bid being the lowest among all submitted bids",
    "Award criteria favoring lowest bid under public procurement rules"
  ],
  "proeth:responsibilityType": "direct",
  "proeth:responsibleAgent": "Engineer C",
  "proeth:sufficientFactors": [
    "Submission of lowest bid on publicly advertised project + standard low-bid award criteria = contract award to Hi-Lo regardless of document quality concerns"
  ],
  "proeth:withinAgentControl": true
}

Causal Language: At the pre-construction conference, Engineer C formally identified major design deficiencies, which precipitated Engineer A's acknowledgment that the drawings and specifications were incomplete — a disclosure Engineer A had not made prior to contract award

Necessary Factors (NESS):
  • Engineer C's formal identification of deficiencies creating an undeniable public record
  • Pre-construction conference as a structured forum requiring Engineer A to respond
  • Engineer A's prior knowledge of incompleteness making denial professionally untenable
Sufficient Factors:
  • Public formal challenge by Engineer C + structured pre-construction forum + Engineer A's prior knowledge = forced acknowledgment of incompleteness that had been concealed through submission and approval phases
Counterfactual Test: Without Engineer C's formal challenge at the pre-construction conference, Engineer A's acknowledgment may have been further delayed or never made, allowing construction to proceed on deficient documents with greater risk of structural failure
Responsibility Attribution:

Agent: Engineer A (for delayed disclosure); Engineer C (for triggering disclosure)
Type: shared
Within Agent Control: Yes

Causal Sequence:
  1. Submit Incomplete Design Documents (Action 2)
    Engineer A knowingly submits deficient documents, initiating a chain of concealment
  2. Hi-Lo Wins Construction Contract (Event 7)
    Engineer C's firm is awarded the contract, creating the pre-construction conference obligation
  3. Raise Unbuildable Design at Pre-Construction (Action 6)
    Engineer C formally and publicly identifies major design deficiencies at the pre-construction conference
  4. Admit Incompleteness Without Prior Disclosure (Action 7)
    Engineer A acknowledges incompleteness for the first time in a formal setting, after contract award and project advancement
  5. Project Crisis Point
    All parties now face the consequences of proceeding through design, review, bidding, and award on knowingly incomplete documents, requiring costly remediation, potential contract disputes, and reputational and legal consequences
RDF JSON-LD
{
  "@context": {
    "proeth": "http://proethica.org/ontology/intermediate#",
    "proeth-case": "http://proethica.org/cases/85#",
    "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/85#CausalChain_58861a41",
  "@type": "proeth:CausalChain",
  "proeth:causalLanguage": "At the pre-construction conference, Engineer C formally identified major design deficiencies, which precipitated Engineer A\u0027s acknowledgment that the drawings and specifications were incomplete \u2014 a disclosure Engineer A had not made prior to contract award",
  "proeth:causalSequence": [
    {
      "proeth:description": "Engineer A knowingly submits deficient documents, initiating a chain of concealment",
      "proeth:element": "Submit Incomplete Design Documents (Action 2)",
      "proeth:step": 1
    },
    {
      "proeth:description": "Engineer C\u0027s firm is awarded the contract, creating the pre-construction conference obligation",
      "proeth:element": "Hi-Lo Wins Construction Contract (Event 7)",
      "proeth:step": 2
    },
    {
      "proeth:description": "Engineer C formally and publicly identifies major design deficiencies at the pre-construction conference",
      "proeth:element": "Raise Unbuildable Design at Pre-Construction (Action 6)",
      "proeth:step": 3
    },
    {
      "proeth:description": "Engineer A acknowledges incompleteness for the first time in a formal setting, after contract award and project advancement",
      "proeth:element": "Admit Incompleteness Without Prior Disclosure (Action 7)",
      "proeth:step": 4
    },
    {
      "proeth:description": "All parties now face the consequences of proceeding through design, review, bidding, and award on knowingly incomplete documents, requiring costly remediation, potential contract disputes, and reputational and legal consequences",
      "proeth:element": "Project Crisis Point",
      "proeth:step": 5
    }
  ],
  "proeth:cause": "Raise Unbuildable Design at Pre-Construction (Action 6)",
  "proeth:counterfactual": "Without Engineer C\u0027s formal challenge at the pre-construction conference, Engineer A\u0027s acknowledgment may have been further delayed or never made, allowing construction to proceed on deficient documents with greater risk of structural failure",
  "proeth:effect": "Admit Incompleteness Without Prior Disclosure (Action 7)",
  "proeth:necessaryFactors": [
    "Engineer C\u0027s formal identification of deficiencies creating an undeniable public record",
    "Pre-construction conference as a structured forum requiring Engineer A to respond",
    "Engineer A\u0027s prior knowledge of incompleteness making denial professionally untenable"
  ],
  "proeth:responsibilityType": "shared",
  "proeth:responsibleAgent": "Engineer A (for delayed disclosure); Engineer C (for triggering disclosure)",
  "proeth:sufficientFactors": [
    "Public formal challenge by Engineer C + structured pre-construction forum + Engineer A\u0027s prior knowledge = forced acknowledgment of incompleteness that had been concealed through submission and approval phases"
  ],
  "proeth:withinAgentControl": true
}
Allen Temporal Relations (12)
Interval algebra relationships with OWL-Time standard properties
From Entity Allen Relation To Entity OWL-Time Property Evidence
Engineer A's knowledge of incompleteness equals
Entity1 and Entity2 have the same start and end times
submission of incomplete drawings and specifications time:intervalEquals
http://www.w3.org/2006/time#intervalEquals
Engineer A generally agrees with Hi-Lo's characterization, but in his defense responds that he felt ... [more]
Engineer A responds to RFP before
Entity1 is before Entity2
award of contract for design, drawings, and specifications time:before
http://www.w3.org/2006/time#before
Engineer A responds to an RFP from a small local public agency... Engineer A's firm's impressive bro... [more]
award of contract for design before
Entity1 is before Entity2
production of drawings and specifications time:before
http://www.w3.org/2006/time#before
Engineer A's firm's impressive brochure and personal interview results in the award of a contract fo... [more]
production of incomplete drawings and specifications before
Entity1 is before Entity2
Engineer B's approval time:before
http://www.w3.org/2006/time#before
The signed and sealed drawings and specifications are ultimately approved by Engineer B of the engin... [more]
Engineer B's approval before
Entity1 is before Entity2
project advertised for bids time:before
http://www.w3.org/2006/time#before
the project is thereafter duly advertised for bids and a contract is awarded to the low bidder, Hi-L... [more]
project advertised for bids before
Entity1 is before Entity2
contract awarded to Hi-Lo Construction time:before
http://www.w3.org/2006/time#before
the project is thereafter duly advertised for bids and a contract is awarded to the low bidder, Hi-L... [more]
contract awarded to Hi-Lo Construction before
Entity1 is before Entity2
pre-construction conference time:before
http://www.w3.org/2006/time#before
a contract is awarded to the low bidder, Hi-Lo Construction... At the pre-construction conference, i... [more]
Engineer C's review of bidding documents before
Entity1 is before Entity2
Engineer C submitting low bid time:before
http://www.w3.org/2006/time#before
Presumably, Engineer C had an opportunity to review the bidding documents which included appropriate... [more]
Engineer C submitting low bid before
Entity1 is before Entity2
Engineer C identifying design deficiencies at pre-construction conference time:before
http://www.w3.org/2006/time#before
a contract is awarded to the low bidder, Hi-Lo Construction. At the pre-construction conference, it ... [more]
time pressure deadline before
Entity1 is before Entity2
submission of incomplete drawings and specifications time:before
http://www.w3.org/2006/time#before
he felt pressured to deliver the drawings and specifications on a specified date, but did not inform... [more]
BER Case No. 82-5 before
Entity1 is before Entity2
current Board discussion of Engineer A, B, and C case time:before
http://www.w3.org/2006/time#before
The Board has considered cases involving similar situations in the past. In BER Case No. 82-5...
Engineer A's non-disclosure of incompleteness starts
Entity1 and Entity2 start at the same time, Entity1 ends first
submission through approval through bid award sequence time:intervalStarts
http://www.w3.org/2006/time#intervalStarts
did not inform anyone as to their incompleteness... The signed and sealed drawings and specification... [more]
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.