Step 4: Review

Review extracted entities and commit to OntServe

Incomplete Plans and Specifications – Engineer, Government, and Contractor Responsibilities
Step 4 of 5
Commit to OntServe
Login to commit entities to OntServe. (332 entities already committed)
Phase 2D: Transfer Resolution transfers obligation/responsibility to another party
Phase 2A: Code Provisions
5 5 committed
code provision reference 5
I.1. individual committed

Hold paramount the safety, health, and welfare of the public.

codeProvision I.1.
provisionText Hold paramount the safety, health, and welfare of the public.
appliesTo 49 items
II.3.a. individual committed

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

codeProvision II.3.a.
provisionText Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which ...
appliesTo 46 items
II.5. individual committed

Engineers shall avoid deceptive acts.

codeProvision II.5.
provisionText Engineers shall avoid deceptive acts.
appliesTo 44 items
III.1.b. individual committed

Engineers shall advise their clients or employers when they believe a project will not be successful.

codeProvision III.1.b.
provisionText Engineers shall advise their clients or employers when they believe a project will not be successful.
appliesTo 46 items
III.2.b. individual committed

Engineers shall not complete, sign, or seal plans and/or specifications that are not in conformity with applicable engineering standards. If the client or employer insists on such unprofessional conduct, they shall notify the proper authorities and withdraw from further service on the project.

codeProvision III.2.b.
provisionText Engineers shall not complete, sign, or seal plans and/or specifications that are not in conformity with applicable engineering standards. If the client or employer insists on such unprofessional condu...
appliesTo 53 items
Phase 2B: Precedent Cases
1 1 committed
precedent case reference 1
BER Case No. 82-5 individual committed

The Board cited this case to compare a situation involving unsatisfactory plans and unjustified expenditure of public funds, and to distinguish the current case by noting that Engineer A's situation involves affirmative responsibility to complete plans rather than a confidentiality conflict.

caseCitation BER Case No. 82-5
caseNumber 82-5
citationContext The Board cited this case to compare a situation involving unsatisfactory plans and unjustified expenditure of public funds, and to distinguish the current case by noting that Engineer A's situation i...
citationType distinguishing
principleEstablished An engineer does not have an ethical obligation to continue efforts to secure a change in employer policy after rejection, nor to report concerns to proper authority when the issue does not involve da...
relevantExcerpts 3 items
internalCaseId 157
resolved True
Phase 2C: Questions & Conclusions
48 48 committed
ethical conclusion 29
Conclusion_1 individual committed

It was not ethical for Engineer A to submit drawings and specifications for review and approval that he knew were incomplete.

conclusionNumber 1
conclusionText It was not ethical for Engineer A to submit drawings and specifications for review and approval that he knew were incomplete.
conclusionType board_explicit
answersQuestions 1 items
extractionReasoning Parsed from imported case text (no LLM)
Conclusion_2 individual committed

It was not ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding.

conclusionNumber 2
conclusionText It was not ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding.
conclusionType board_explicit
answersQuestions 1 items
extractionReasoning Parsed from imported case text (no LLM)
Conclusion_3 individual committed

It was not ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes.

conclusionNumber 3
conclusionText It was not ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes.
conclusionType board_explicit
answersQuestions 1 items
extractionReasoning Parsed from imported case text (no LLM)
Conclusion_101 individual committed

Beyond the Board's finding that Engineer A acted unethically in submitting incomplete drawings, his conduct was further aggravated by the specific vulnerability of his client. The local public agency lacked any in-house technical capacity to detect the deficiencies Engineer A knew existed. This asymmetry of knowledge and capability imposed a heightened affirmative disclosure obligation on Engineer A - one that went beyond the baseline duty owed to a technically sophisticated client. By exploiting, even if passively, the agency's inability to self-protect, Engineer A's omission crossed from mere negligence into a form of professional exploitation of client dependency. The NSPE Code's requirement that engineers act as faithful agents and advisors is most demanding precisely when the client cannot independently verify the adequacy of the professional's work product. Engineer A's silence in this context was not a neutral omission but an active breach of the trust relationship that defines the engineer-client engagement.

conclusionNumber 101
conclusionText Beyond the Board's finding that Engineer A acted unethically in submitting incomplete drawings, his conduct was further aggravated by the specific vulnerability of his client. The local public agency ...
conclusionType analytical_extension
mentionedEntities {"obligations": ["Engineer A Technically Unsupported Client Heightened Disclosure Dam Design", "Engineer A Formal Client Risk Notification Dam Design"], "principles": ["Faithful Agent Notification...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_102 individual committed

The Board's conclusion that Engineer A acted unethically does not fully reckon with the compounding ethical injury his submission inflicted on the competitive bidding process itself. When Engineer A submitted signed and sealed drawings he knew to be incomplete, he did not merely harm his direct client or the federal funding agency - he corrupted the integrity of the public procurement process for every contractor who prepared and submitted a bid. Contractors other than Hi-Lo Construction invested resources pricing a project whose true scope was unknowable from the deficient documents. They could not have submitted accurate or competitive bids, and the award to the lowest bidder was therefore not a genuine market outcome but an artifact of an artificially constrained information environment. This harm to third-party bidders and to the fairness of public procurement is an independent ethical injury that the Board's analysis, focused on the tripartite relationship among Engineer A, Engineer B, and Engineer C, did not explicitly address. The NSPE Code's prohibition on deceptive acts and its requirement of objective and truthful professional representations extend to all foreseeable parties who rely on engineering documents, not merely the immediate client.

conclusionNumber 102
conclusionText The Board's conclusion that Engineer A acted unethically does not fully reckon with the compounding ethical injury his submission inflicted on the competitive bidding process itself. When Engineer A s...
conclusionType analytical_extension
mentionedEntities {"principles": ["Honesty in Professional Representations Violated by Engineer A Sealed Incomplete Documents", "Public Welfare Paramount Invoked by Engineer A Dam Design Failure", "Fraud and...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_103 individual committed

Engineer A's rationalization that federal funds - rather than local funds - would absorb any cost overruns from the incomplete design does not merely fail as a mitigating defense; it constitutes an independent ethical violation distinct from the incompleteness itself. By invoking the federal funding source as a justification for non-disclosure, Engineer A implicitly misrepresented to the federal agency the adequacy of the documents it was being asked to approve and fund. The federal agency's approval decision was predicated on the assumption that signed and sealed drawings represented a professionally complete and conforming design. Engineer A's knowing submission of deficient documents under seal, combined with his internal calculation that federal funds would cover the consequences, amounts to a misrepresentation in his professional dealings with a public funding body. The NSPE Code's prohibition on deceptive acts and its bar on completing or sealing plans not in conformity with applicable standards are not satisfied by the engineer's private belief that downstream funding mechanisms will neutralize the harm. The source of funding is ethically irrelevant to the completeness obligation, and the Board's implicit rejection of this rationalization should be understood as establishing that public funds are not a risk-absorption mechanism that licenses professional shortcuts.

conclusionNumber 103
conclusionText Engineer A's rationalization that federal funds — rather than local funds — would absorb any cost overruns from the incomplete design does not merely fail as a mitigating defense; it constitutes an in...
conclusionType analytical_extension
mentionedEntities {"obligations": ["Engineer A Federal Funds Rationalization Fraud Misrepresentation", "Engineer A Sealed Incomplete Documents Completeness Certification Accuracy"], "principles": ["Funding Source...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_104 individual committed

The Board's conclusion that Engineer B acted unethically in approving incomplete drawings raises a nuance the Board did not fully develop: Engineer B's approval did not merely fail to catch Engineer A's deficiencies - it actively laundered them. A federal agency approval stamp on a set of drawings carries independent epistemic authority in the procurement chain. Contractors, the local public agency, and the public reasonably interpret federal approval as a second-level professional verification of document adequacy. By approving the drawings without substantive review or competence-appropriate scrutiny, Engineer B transformed what was Engineer A's unilateral misrepresentation into an apparently bi-validated professional certification. This amplification of the original ethical violation is a distinct harm attributable to Engineer B. The NSPE Code's responsible charge and professional competence standards require that an engineer's approval reflect genuine engagement with the documents being approved. Where an approving engineer either lacks domain-specific competence to evaluate the submission or fails to exercise that competence, the ethical obligation is to escalate, return the documents with a deficiency notice, or decline approval - not to ratify by default.

conclusionNumber 104
conclusionText The Board's conclusion that Engineer B acted unethically in approving incomplete drawings raises a nuance the Board did not fully develop: Engineer B's approval did not merely fail to catch Engineer A...
conclusionType analytical_extension
mentionedEntities {"capabilities": ["Engineer B Responsible Charge Active Engagement Failure", "Engineer B Domain-Specific Competence Boundary Recognition Failure"], "obligations": ["Engineer B Federal Plan...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_105 individual committed

The Board's finding against Engineer B also implicates a systemic institutional ethics question that the Board's individual-focused analysis did not address. Engineer B's failure may reflect not only personal ethical shortcoming but also a structural deficiency in the federal agency's review process - one in which approval authority was delegated to an engineer without adequate domain competence or without procedural safeguards requiring substantive technical verification before approval. While the NSPE Code speaks to individual engineers' obligations, the Board's conclusion against Engineer B implicitly signals that engineers in institutional approval roles bear a professional duty to advocate internally for review processes that match the technical complexity of submitted projects. An engineer who knows or should know that the agency's review process is inadequate to catch deficiencies of the kind present here has an obligation to flag that systemic gap, not merely to perform a perfunctory review within a broken system. This extends the Board's conclusion from individual culpability to a broader professional responsibility for the integrity of institutional gatekeeping functions.

conclusionNumber 105
conclusionText The Board's finding against Engineer B also implicates a systemic institutional ethics question that the Board's individual-focused analysis did not address. Engineer B's failure may reflect not only ...
conclusionType analytical_extension
mentionedEntities {"obligations": ["Engineer B Federal Plan Approval Substantive Competence Review Dam", "Engineer B Responsible Charge Review Before Federal Approval Dam Project"], "principles": ["Competence...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_106 individual committed

The Board's conclusion that Engineer C acted unethically in submitting a bid on a project he later characterized as unbuildable requires a more granular temporal analysis than the Board provided. The ethical violation is not simply that Engineer C identified deficiencies after winning the contract - it is that the sequence of his conduct suggests the deficiencies were either discoverable or actually discovered during pre-bid review, yet he submitted a bid anyway and raised the unbuildability claim only at the pre-construction conference, after the contract was secured. This timing pattern raises the inference that Engineer C may have strategically withheld his constructability concerns to win the contract at a low bid price, intending to renegotiate scope and price after award - a practice that is both commercially opportunistic and ethically impermissible for a licensed engineer. In his dual role as engineer and contractor, Engineer C possessed professional competence that other bidders may have lacked to identify the design deficiencies. That superior competence, rather than relieving him of disclosure obligations, intensified them: he was better positioned than any other market participant to flag the deficiencies before bid submission, and his failure to do so harmed both the public agency and competing contractors who priced the project without the benefit of his professional insight.

conclusionNumber 106
conclusionText The Board's conclusion that Engineer C acted unethically in submitting a bid on a project he later characterized as unbuildable requires a more granular temporal analysis than the Board provided. The ...
conclusionType analytical_extension
mentionedEntities {"capabilities": ["Engineer C Dual-Role Document Evaluation Dam Project", "Engineer C Pre-Bid Clarification Request Dam Project"], "obligations": ["Engineer C Constructability Deficiency Pre-Bid...
citedProvisions 3 items
answersQuestions 2 items
Conclusion_107 individual committed

The Board's three conclusions, taken together, reveal a cascading ethical failure in which each actor's violation enabled and amplified the next actor's violation - a dynamic the Board did not explicitly theorize but which has important implications for how professional ethics obligations should be understood in multi-party public procurement contexts. Engineer A's submission of incomplete documents created the predicate condition for Engineer B's approval failure; Engineer B's approval created the procurement legitimacy that induced Engineer C and other contractors to invest in bid preparation; and Engineer C's decision to bid rather than disclose completed the cycle by allowing a fatally deficient project to reach contract award. No single actor's ethical compliance would have been sufficient to prevent the harm - Engineer B's proper rejection of the drawings would have stopped the cascade, as would Engineer C's pre-bid disclosure - but each actor's violation was a necessary condition for the harm that ultimately materialized. This interdependence suggests that the NSPE Code's individual-focused obligations should be understood as collectively constituting a system of redundant ethical checkpoints, each of which is designed to catch failures that earlier checkpoints missed. The ethical weight on each downstream actor therefore increases as earlier checkpoints fail, because the downstream actor is the last available safeguard against public harm.

conclusionNumber 107
conclusionText The Board's three conclusions, taken together, reveal a cascading ethical failure in which each actor's violation enabled and amplified the next actor's violation — a dynamic the Board did not explici...
conclusionType analytical_extension
mentionedEntities {"principles": ["Public Welfare Paramount Invoked by Engineer A Dam Design Failure", "Responsible Charge Integrity Violated by Engineer A Seal on Incomplete Documents", "Responsible Charge...
citedProvisions 5 items
answersQuestions 1 items
Conclusion_201 individual committed

Engineer A's submission of signed and sealed incomplete drawings to the federal funding agency constituted a form of misrepresentation that is aggravated, not mitigated, by his assumption that federal funds would absorb cost overruns. The act of sealing documents carries an implicit professional certification of completeness and conformity. By invoking the availability of federal funds as a private rationalization for non-disclosure, Engineer A effectively treated public money as a personal insurance policy against the consequences of his own professional shortfall. This reasoning compounds the ethical violation: it demonstrates not only that Engineer A knew the documents were deficient, but that he made a deliberate, calculated decision to conceal that deficiency from the very agency whose funds he expected to bear the resulting costs. The federal funding agency was thus doubly deceived - first by the implicit certification of completeness in the sealed drawings, and second by Engineer A's silent assumption that the agency's resources would remedy his incomplete work without its knowledge or consent.

conclusionNumber 201
conclusionText Engineer A's submission of signed and sealed incomplete drawings to the federal funding agency constituted a form of misrepresentation that is aggravated, not mitigated, by his assumption that federal...
conclusionType question_response
mentionedEntities {"obligations": ["Engineer A Federal Funds Rationalization Fraud Misrepresentation", "Engineer A Sealed Document Completeness Dam Design"], "principles": ["Fraud and Misrepresentation Prohibition...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_202 individual committed

The local public agency's acknowledged lack of in-house technical capacity to evaluate drawings and specifications imposed a heightened affirmative disclosure obligation on Engineer A that went beyond what would ordinarily be required when dealing with a technically sophisticated client. When a professional engineer knows that his client cannot independently verify the adequacy of the work product, the engineer's duty of honest representation is not merely passive - it is not satisfied by simply refraining from active lies. It becomes an active duty to affirmatively communicate known deficiencies, because the client has no independent means of discovering them. Engineer A's silence in this context was not a neutral omission; it was a functional deception, because the local public agency was wholly dependent on Engineer A's professional judgment and had no realistic ability to detect the incompleteness on its own. The heightened disclosure obligation was therefore not merely a matter of professional courtesy but a structural ethical requirement arising from the asymmetry of technical knowledge between the engineer and his client.

conclusionNumber 202
conclusionText The local public agency's acknowledged lack of in-house technical capacity to evaluate drawings and specifications imposed a heightened affirmative disclosure obligation on Engineer A that went beyond...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Technically Unsupported Client Heightened Disclosure Dam Project", "Local Agency Client Technical Review Incapacity Resource Constraint Dam Project"], "obligations":...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_203 individual committed

A formal written notification to the local public agency disclosing the known incompleteness of the drawings before submission would have been a necessary but not automatically sufficient condition for satisfying Engineer A's ethical obligations. Such written disclosure would have eliminated the deception element of the violation and would have transferred informed decision-making authority back to the client, which is itself an important ethical requirement. However, written notification alone would not have discharged Engineer A's obligation under the code provision prohibiting him from signing or sealing plans not in conformity with applicable engineering standards. The act of sealing incomplete documents carries an independent integrity obligation that cannot be waived by client consent alone. Even if the local public agency, fully informed, had directed Engineer A to proceed with submission, Engineer A would have retained an independent professional duty to decline to seal documents he knew to be incomplete, or at minimum to qualify his seal with an explicit notation of the known deficiencies. Client authorization is not a license to misrepresent the state of professional work to third parties, including the federal funding agency.

conclusionNumber 203
conclusionText A formal written notification to the local public agency disclosing the known incompleteness of the drawings before submission would have been a necessary but not automatically sufficient condition fo...
conclusionType question_response
mentionedEntities {"obligations": ["Engineer A Sealed Incomplete Documents Completeness Certification Accuracy", "Engineer A Formal Client Risk Notification Dam Design"], "principles": ["Responsible Charge...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_204 individual committed

The competitive bidding process itself sustained an independent ethical injury that the Board's conclusions, focused on individual actors, do not fully articulate. When incomplete drawings and specifications are advertised for competitive bids, every contractor other than the one who ultimately discovers and discloses the deficiencies is harmed by being asked to price a project whose true scope is unknowable from the documents provided. Contractors who submitted bids in good faith based on the deficient documents either priced the work incorrectly - potentially winning a contract they cannot perform profitably - or lost the contract to a low bidder whose price may have been artificially low precisely because the scope was undefined. The integrity of public competitive procurement depends on all bidders working from the same complete informational baseline. Engineer A's submission of incomplete documents, and Engineer B's approval of them for bidding, jointly corrupted that baseline and rendered the entire procurement process unreliable as a mechanism for achieving fair pricing of public work. This harm to the procurement process is distinct from, and cumulative with, the harms to the individual parties.

conclusionNumber 204
conclusionText The competitive bidding process itself sustained an independent ethical injury that the Board's conclusions, focused on individual actors, do not fully articulate. When incomplete drawings and specifi...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Public Procurement Fairness Incomplete Bid Documents Dam Project"], "principles": ["Public Welfare Paramount Invoked by Engineer A Dam Design Failure", "Honesty in...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_205 individual committed

The tension between Engineer A's faithful agent obligation to deliver on the contracted schedule and his paramount obligation to protect public welfare is real but ultimately not a genuine conflict that could excuse his conduct. The NSPE Code resolves this tension explicitly by establishing that public welfare is paramount - meaning it is not one consideration to be weighed against schedule compliance but a threshold constraint that overrides contractual performance obligations when the two conflict. Engineer A's schedule pressure was a real professional difficulty, but it did not create an ethical permission to submit incomplete documents; it created an ethical obligation to disclose the conflict to his client and, if necessary, to refuse to seal documents he could not certify as complete. The faithful agent obligation requires an engineer to serve his client's genuine interests, which include receiving honest professional advice about project status - not merely receiving deliverables on time regardless of their adequacy. An engineer who delivers incomplete work on schedule to avoid a difficult conversation with his client has not served the client faithfully; he has served his own convenience at the client's expense.

conclusionNumber 205
conclusionText The tension between Engineer A's faithful agent obligation to deliver on the contracted schedule and his paramount obligation to protect public welfare is real but ultimately not a genuine conflict th...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Schedule Pressure Non-Excuse Sealed Drawings Dam Project", "Engineer A Temporal Constraint Contract Delivery Deadline Dam Project"], "obligations": ["Engineer A...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_206 individual committed

Engineer B's approval of the incomplete drawings created a compounded ethical harm beyond his own individual violation: it generated a false impression of independent professional verification that the documents did not merit. When a second licensed engineer reviews and approves a set of drawings submitted by a first engineer, the approval carries an implicit representation to downstream parties - including the contracting agency, prospective bidders, and the public - that a competent professional has independently assessed the documents and found them adequate. Engineer B's approval, whether the result of inadequate review or insufficient domain competence, effectively laundered Engineer A's deficient work product by attaching to it the imprimatur of federal agency engineering review. This made the deficiency harder to detect and easier to overlook, and it may have discouraged contractors from scrutinizing the documents as carefully as they otherwise might have. The ethical injury from Engineer B's approval was therefore not merely parallel to Engineer A's violation but multiplicative of it.

conclusionNumber 206
conclusionText Engineer B's approval of the incomplete drawings created a compounded ethical harm beyond his own individual violation: it generated a false impression of independent professional verification that th...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer B Federal Plan Approval Substantive Technical Competence Verification Failure", "Engineer B Domain-Specific Competence Boundary Recognition Failure"], "obligations":...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_207 individual committed

From a deontological perspective, Engineer A's conduct cannot be justified by his belief that no harm would ultimately result. Deontological ethics evaluates the moral permissibility of an act by reference to the nature of the act and the duties it implicates, not by reference to the actor's predictions about consequences. The act of signing and sealing drawings is, by professional convention and code, a representation that the documents are complete and conform to applicable standards. Engineer A knew this representation was false when he made it. His belief that federal funds would cover cost overruns is irrelevant to the deontological analysis because it speaks only to his prediction of consequences, not to the character of the act itself. A duty of honest professional representation is categorical - it applies regardless of whether the engineer believes the deception will cause harm. The Board's rejection of the benevolent motive defense is therefore fully consistent with deontological reasoning: good intentions about outcomes cannot transform a dishonest act into an honest one.

conclusionNumber 207
conclusionText From a deontological perspective, Engineer A's conduct cannot be justified by his belief that no harm would ultimately result. Deontological ethics evaluates the moral permissibility of an act by refe...
conclusionType question_response
mentionedEntities {"obligations": ["Engineer A Sealed Incomplete Documents Completeness Certification Accuracy"], "principles": ["Honesty in Professional Representations Violated by Engineer A Sealed Incomplete...
citedProvisions 3 items
answersQuestions 2 items
Conclusion_208 individual committed

From a consequentialist perspective, Engineer A's rationalization was analytically deficient even on its own terms. A consequentialist justification for non-disclosure requires that the engineer have adequately surveyed the full range of foreseeable harms and concluded that the expected benefits outweigh them. Engineer A's reasoning considered only one potential harm - increased project cost - and only one potential remedy - federal fund absorption. He failed to account for the foreseeable harm to procurement fairness caused by asking contractors to bid on unknowable scope; the risk of project delay and disruption when deficiencies were discovered post-award; the waste of public funds on a procurement process that would need to be substantially renegotiated; the erosion of public trust in engineering professionals and federal grant programs; and the possibility that the federal agency might not in fact absorb the costs, leaving the local public agency exposed. A consequentialist analysis that ignores these foreseeable harms is not a good-faith consequentialist analysis - it is a motivated rationalization dressed in consequentialist language.

conclusionNumber 208
conclusionText From a consequentialist perspective, Engineer A's rationalization was analytically deficient even on its own terms. A consequentialist justification for non-disclosure requires that the engineer have ...
conclusionType question_response
mentionedEntities {"obligations": ["Engineer A Funding Source Rationalization Dam Design"], "principles": ["Funding Source Non-Determinative Rationalization by Engineer A", "Benevolent Motive Non-Cure Applied to...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_209 individual committed

From a virtue ethics perspective, Engineer B's approval of the incomplete drawings reflects deficiencies in at least three professional virtues: diligence, intellectual honesty, and professional courage. Diligence required that he conduct a substantive review adequate to detect the incompleteness that Engineer C later identified at a pre-construction conference - a review that, if conducted competently, should have surfaced the same deficiencies. Intellectual honesty required that he recognize and acknowledge the limits of his own domain competence, if those limits prevented him from conducting an adequate review, rather than proceeding as though his approval carried a weight of verification it did not actually possess. Professional courage required that he be willing to return deficient documents to Engineer A with a deficiency notice, even if doing so created friction with the submitting engineer or delayed the federal approval process. The absence of all three virtues from Engineer B's conduct suggests not merely a technical code violation but a deeper failure of professional character that the Board's conclusion, while correct, does not fully illuminate.

conclusionNumber 209
conclusionText From a virtue ethics perspective, Engineer B's approval of the incomplete drawings reflects deficiencies in at least three professional virtues: diligence, intellectual honesty, and professional coura...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer B Responsible Charge Active Engagement Failure", "Engineer B Federal Plan Approval Substantive Technical Competence Verification Failure", "Engineer B Domain-Specific...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_210 individual committed

From a deontological perspective, Engineer C's dual status as both a licensed professional engineer and a contractor created a categorical professional duty to disclose known constructability deficiencies before submitting his bid, rather than after winning the contract. A licensed engineer who reviews documents in connection with a bid and identifies conditions he professionally judges to be unbuildable is not merely a contractor making a business calculation about risk - he is a professional engineer who has formed a professional judgment about the adequacy of engineering documents. That professional judgment carries with it a duty of disclosure that is independent of, and not suspended by, the competitive bidding context. The timing of Engineer C's disclosure - raised only at the pre-construction conference after the contract was awarded - suggests that he used his professional knowledge to evaluate the risk to his own firm while withholding that same professional knowledge from the agency and the other bidders who lacked his engineering expertise. This selective deployment of professional judgment for private competitive advantage, while withholding it from the public agency that needed it, is inconsistent with the duties that accompany a professional engineering license.

conclusionNumber 210
conclusionText From a deontological perspective, Engineer C's dual status as both a licensed professional engineer and a contractor created a categorical professional duty to disclose known constructability deficien...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer C Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure", "Engineer C Pre-Bid Clarification Request Dam Project", "Engineer C Dual-Role Document Evaluation...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_211 individual committed

The tension between Engineer C's constructability disclosure obligation and the discretionary whistleblowing framework recognized in BER Case No. 82-5 is real but resolvable in favor of mandatory disclosure in this case. BER Case No. 82-5 treated disclosure of non-safety deficiencies - specifically, excessive costs and time delays by subcontractors - as a matter of personal conscience rather than mandatory professional duty, in part because the engineer in that case was an employee whose disclosure would have required him to act against his employer's interests. Engineer C's situation is materially different in two respects. First, Engineer C is not an employee being asked to act against his employer; he is an independent contractor-engineer whose disclosure obligation runs to the public agency, not to a superior. Second, and more importantly, Engineer C's knowledge of the unbuildable conditions was not incidental background knowledge - it was knowledge he formed in his professional capacity as a licensed engineer while evaluating documents for a public procurement. The professional engineering license creates obligations that persist regardless of the commercial context in which professional judgment is exercised. The discretionary character of whistleblowing in BER 82-5 does not extend to cases where the engineer's own professional evaluation of documents is the source of the knowledge that needs to be disclosed.

conclusionNumber 211
conclusionText The tension between Engineer C's constructability disclosure obligation and the discretionary whistleblowing framework recognized in BER Case No. 82-5 is real but resolvable in favor of mandatory disc...
conclusionType question_response
mentionedEntities {"obligations": ["Engineer C Constructability Deficiency Pre-Bid Disclosure Dam Project", "BER 82-5 Defense Engineer Whistleblower Personal Conscience Right Non-Mandatory"], "principles":...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_212 individual committed

If Engineer A had refused to submit the drawings by the contractual deadline and instead requested a schedule extension to complete the design properly, this course of action would have been not merely permissible but ethically required under the NSPE Code. The Code's prohibition on signing or sealing plans not in conformity with applicable engineering standards is not qualified by a schedule-compliance exception. An engineer who cannot complete a design to professional standards within a contractual timeframe has an obligation to disclose that fact to his client and seek relief - whether in the form of a schedule extension, a scope reduction, or additional resources - rather than to deliver a deficient product on time. The argument that refusing to meet a deadline would have jeopardized federal funding, while practically significant, does not alter the ethical analysis: the Code does not permit an engineer to compromise professional standards to preserve a client's funding timeline. Had Engineer A taken this course, Engineer B's approval dilemma would not have arisen, and Engineer C would have received either complete documents or no documents at all - either of which would have been ethically preferable to the situation that actually occurred.

conclusionNumber 212
conclusionText If Engineer A had refused to submit the drawings by the contractual deadline and instead requested a schedule extension to complete the design properly, this course of action would have been not merel...
conclusionType question_response
mentionedEntities {"constraints": ["Engineer A Schedule Pressure Non-Excuse Sealed Drawings Dam Project", "Engineer A Temporal Constraint Contract Delivery Deadline Dam Project"], "obligations": ["Engineer A...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_213 individual committed

If Engineer B had recognized the limits of his competence or the incompleteness of the submitted documents and returned the drawings to Engineer A with a formal deficiency notice, the cascade of ethical violations that followed would very likely have been interrupted at that point. The project would not have proceeded to competitive bidding on deficient documents; Engineer C would not have faced the dilemma of bidding on an unbuildable project; and the public agency would have been forced to confront the incompleteness of the design before committing public funds to a procurement. Engineer B's role in the process was therefore not merely one of three parallel violations but a critical control point whose failure allowed Engineer A's initial violation to propagate through the entire procurement chain. This observation underscores the systemic importance of competent independent review in federally funded public projects: the review function is not a formality but a substantive safeguard whose integrity is essential to the integrity of the entire procurement process. Engineer B's failure was not merely an individual ethical lapse but a systemic failure with consequences that extended well beyond his own conduct.

conclusionNumber 213
conclusionText If Engineer B had recognized the limits of his competence or the incompleteness of the submitted documents and returned the drawings to Engineer A with a formal deficiency notice, the cascade of ethic...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer B Competence Limitation Recognition Supervisor Escalation Dam Review", "Engineer B Responsible Charge Active Engagement Failure"], "obligations": ["Engineer B...
citedProvisions 2 items
answersQuestions 1 items
Conclusion_214 individual committed

If Engineer C had formally notified the local public agency of the constructability deficiencies and requested a clarification or addendum before submitting his bid, this action would have discharged his ethical obligations as a licensed engineer and would likely have triggered a re-evaluation of the entire procurement. Such notification would have placed the agency on formal notice that the documents were deficient, potentially requiring suspension of the bidding process, issuance of corrective addenda, or re-advertisement of the project on corrected documents. While this course of action would have disadvantaged Engineer C competitively - by alerting other bidders to deficiencies they might not have independently identified, and by potentially delaying the award - the competitive disadvantage does not constitute an ethical justification for withholding the disclosure. The NSPE Code does not recognize competitive self-interest as a basis for suspending professional disclosure obligations. Moreover, had Engineer C taken this course, he would have performed a public service by surfacing deficiencies that Engineer A concealed and Engineer B failed to detect, potentially saving the public agency and the federal funding authority from the costs of a failed procurement.

conclusionNumber 214
conclusionText If Engineer C had formally notified the local public agency of the constructability deficiencies and requested a clarification or addendum before submitting his bid, this action would have discharged ...
conclusionType question_response
mentionedEntities {"capabilities": ["Engineer C Pre-Bid Clarification Request Dam Project", "Engineer C Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure"], "obligations": ["Engineer C...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_301 individual committed

The tension between the Faithful Agent Notification Obligation - which bound Engineer A to deliver drawings and specifications on the contractually agreed schedule - and the Public Welfare Paramount principle - which required him to withhold or qualify documents whose incompleteness could endanger public safety on a dam project - was resolved decisively in favor of public welfare and honest representation. The Board's reasoning makes clear that schedule pressure is not a recognized mitigating factor under the NSPE Code; it is instead an occasion that triggers, rather than suspends, the engineer's affirmative duty to disclose. Engineer A's obligation to serve his client faithfully did not license him to serve that client with deficient work product, and the faithful agent role itself presupposes honest communication about the state of the deliverable. Where the two principles appeared to conflict, the conflict was illusory: a faithful agent who conceals known deficiencies is not serving his client at all. The case therefore teaches that the Faithful Agent Notification Obligation and the Public Welfare Paramount principle are not genuinely opposed - they converge on the same required action, namely transparent disclosure of incompleteness - and that any apparent tension between them dissolves once the engineer recognizes that concealment is never a permissible form of client service.

conclusionNumber 301
conclusionText The tension between the Faithful Agent Notification Obligation — which bound Engineer A to deliver drawings and specifications on the contractually agreed schedule — and the Public Welfare Paramount p...
conclusionType principle_synthesis
mentionedEntities {"constraints": ["Engineer A Schedule Pressure Non-Excuse Sealed Drawings Dam Project", "Engineer A Incomplete Risk Disclosure Dam Project"], "obligations": ["Engineer A Incomplete Deliverable...
citedProvisions 4 items
answersQuestions 1 items
Conclusion_302 individual committed

The Responsible Charge Integrity principle - which demands that an engineer seal only complete and conforming documents - and the Competence Boundary Recognition and Escalation Obligation imposed on Engineer B interacted in a way that compounded rather than checked each other's failure. Engineer A's seal on incomplete drawings created a facially authoritative document that Engineer B's approval then ratified, producing a layered misrepresentation: the local public agency, the federal funding authority, and ultimately the bidding contractors were all entitled to infer from the combination of Engineer A's seal and Engineer B's approval that two independent competent professionals had verified the documents' adequacy. In reality, neither had done so honestly. This case teaches that the professional sealing and approval system is structurally dependent on each participant exercising genuine independent judgment; when one engineer abdicates that responsibility, a downstream approver who fails to exercise independent scrutiny does not merely commit a separate violation - he amplifies the original violation by lending it additional apparent legitimacy. The ethical injury caused by Engineer B's approval was therefore not simply additive but multiplicative, because it foreclosed the last institutional checkpoint before public procurement. The resolution implied by the Board is that Responsible Charge Integrity and Competence Boundary Recognition are complementary, not competing: each engineer in a review chain must exercise independent judgment precisely because no prior seal can be assumed to have been honestly applied.

conclusionNumber 302
conclusionText The Responsible Charge Integrity principle — which demands that an engineer seal only complete and conforming documents — and the Competence Boundary Recognition and Escalation Obligation imposed on E...
conclusionType principle_synthesis
mentionedEntities {"capabilities": ["Engineer B Responsible Charge Active Engagement Failure", "Engineer B Federal Plan Approval Substantive Technical Competence Verification Failure", "Engineer B Domain-Specific...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_303 individual committed

The Benevolent Motive Non-Cure principle - applied by the Board to reject Engineer A's rationalization that federal funds would absorb any cost overruns - stands in direct tension with a consequentialist reading of the Funding Source Non-Determinative principle, but the Board resolved that tension by adopting a deontological priority: the wrongfulness of submitting sealed incomplete documents is determined by the act itself and the engineer's knowledge at the time, not by the downstream financial outcome the engineer hoped would materialize. Engineer A's genuine belief that no local funds would be harmed did not transform a deceptive act into an honest one, because the Honesty in Professional Representations principle and the Fraud and Misrepresentation Prohibition operate at the moment of submission, not at the moment of financial settlement. This resolution carries a significant teaching for principle prioritization: when an engineer's benevolent motive is used to justify non-disclosure rather than to supplement disclosure, it becomes a rationalization that the Code cannot recognize without effectively licensing engineers to substitute their private cost predictions for transparent professional communication. The case therefore establishes that good-faith assumptions about harm mitigation can never substitute for affirmative disclosure, and that the Benevolent Motive Non-Cure principle functions as a categorical constraint on consequentialist self-exemption from honesty obligations.

conclusionNumber 303
conclusionText The Benevolent Motive Non-Cure principle — applied by the Board to reject Engineer A's rationalization that federal funds would absorb any cost overruns — stands in direct tension with a consequential...
conclusionType principle_synthesis
mentionedEntities {"constraints": ["Engineer A Federal Funding Rationalization Non-Excuse Dam Project", "Engineer A Sealed Drawings Completeness Dam Project"], "obligations": ["Engineer A Funding Source...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_304 individual committed

The Engineer-Contractor Dual Role Constructability Disclosure Obligation imposed on Engineer C - requiring him to flag unbuildable conditions before bidding - and the Whistleblowing Personal Conscience Right recognized in BER Case No. 82-5 - which treats disclosure of non-safety deficiencies as discretionary rather than mandatory - were resolved by the Board in a manner that distinguishes the two on the basis of role, not merely on the basis of harm severity. In BER Case No. 82-5, the engineer was an employee observing misconduct by others and was not himself a participant in the deficient transaction; his disclosure obligation was therefore framed as a matter of personal conscience. Engineer C, by contrast, was an active participant in the procurement: he submitted a bid on documents he had evaluated and found unbuildable, thereby lending his professional credibility to a transaction he privately regarded as defective. The Board's resolution implies that the discretionary whistleblowing framework of BER Case No. 82-5 does not apply when the engineer is not a bystander but a principal whose own bid submission constitutes an implicit representation that the project is executable. The case teaches that the dual role of engineer-contractor triggers a heightened and mandatory disclosure obligation that supersedes the discretionary personal conscience framework, because the contractor's bid is itself a professional representation about constructability - and submitting that bid while privately knowing the project is unbuildable violates the Honesty in Professional Representations principle regardless of whether public safety is immediately at risk.

conclusionNumber 304
conclusionText The Engineer-Contractor Dual Role Constructability Disclosure Obligation imposed on Engineer C — requiring him to flag unbuildable conditions before bidding — and the Whistleblowing Personal Conscienc...
conclusionType principle_synthesis
mentionedEntities {"capabilities": ["Engineer C Unbuildable Bid Deficiency Reflection Dam Project", "Engineer C Pre-Bid Clarification Request Dam Project", "Engineer C Dual-Role Document Evaluation Dam Project",...
citedProvisions 3 items
answersQuestions 1 items
Conclusion_305 individual committed

The Technically Unsupported Client Heightened Disclosure Obligation - which recognized that the local public agency lacked the in-house technical capacity to evaluate Engineer A's drawings and specifications - interacted with the Professional Accountability principle to establish that Engineer A's ethical duties were not merely symmetrical with those owed to a sophisticated client but were affirmatively elevated by the client's vulnerability. This interaction reveals a structural principle of the NSPE Code: the engineer's disclosure and completeness obligations scale with the client's incapacity to self-protect. Where a client can independently verify the engineer's work product, the engineer's concealment of deficiencies is harmful but the client retains some residual capacity for self-correction; where the client is wholly dependent on the engineer's professional judgment, concealment eliminates the last available check on the engineer's conduct. The case therefore teaches that the Technically Unsupported Client Heightened Disclosure Obligation is not a separate or supplementary principle but a contextual intensifier of the baseline honesty and completeness obligations - and that Engineer A's failure to disclose was more serious, not less, precisely because his client had no independent means of discovering the deficiency. This principle interaction also implies that Engineer A's marketing representations, which secured the contract through an impressive brochure and personal interview, created an expectation of professional adequacy that the local agency was structurally unable to verify, making the gap between representation and delivery an aggravated rather than ordinary ethical violation.

conclusionNumber 305
conclusionText The Technically Unsupported Client Heightened Disclosure Obligation — which recognized that the local public agency lacked the in-house technical capacity to evaluate Engineer A's drawings and specifi...
conclusionType principle_synthesis
mentionedEntities {"capabilities": ["Engineer A Technically Unsupported Client Heightened Disclosure Failure", "Engineer A Incomplete Deliverable Self-Disclosure Failure", "Engineer A Signed Sealed Document...
citedProvisions 4 items
answersQuestions 1 items
ethical question 19
Question_1 individual committed

Was it ethical for Engineer A to submit final drawings and specifications for review and approval that he knew were incomplete?

questionNumber 1
questionText Was it ethical for Engineer A to submit final drawings and specifications for review and approval that he knew were incomplete?
questionType board_explicit
extractionReasoning Parsed from imported case text (no LLM)
Question_2 individual committed

Was it ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding?

questionNumber 2
questionText Was it ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding?
questionType board_explicit
extractionReasoning Parsed from imported case text (no LLM)
Question_3 individual committed

Was it ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes?

questionNumber 3
questionText Was it ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes?
questionType board_explicit
extractionReasoning Parsed from imported case text (no LLM)
Question_101 individual committed

Did Engineer A's submission of a signed and sealed set of incomplete drawings constitute fraud or misrepresentation toward the federal funding agency, and does the fact that he anticipated federal funds would absorb cost overruns aggravate rather than mitigate that ethical violation?

questionNumber 101
questionText Did Engineer A's submission of a signed and sealed set of incomplete drawings constitute fraud or misrepresentation toward the federal funding agency, and does the fact that he anticipated federal fun...
questionType implicit
mentionedEntities {"obligations": ["Engineer A Federal Funds Rationalization Fraud Misrepresentation"], "principles": ["Fraud and Misrepresentation Prohibition Invoked Against Engineer A Federal Funds Assertion",...
relatedProvisions 3 items
Question_102 individual committed

Given that the local public agency lacked the in-house technical capacity to evaluate the drawings and specifications, did Engineer A bear a heightened affirmative duty to disclose incompleteness precisely because his client was technically unsophisticated and wholly dependent on his professional judgment?

questionNumber 102
questionText Given that the local public agency lacked the in-house technical capacity to evaluate the drawings and specifications, did Engineer A bear a heightened affirmative duty to disclose incompleteness prec...
questionType implicit
mentionedEntities {"constraints": ["Engineer A Technically Unsupported Client Heightened Disclosure Dam Project", "Local Agency Client Technical Review Incapacity Resource Constraint Dam Project"], "obligations":...
relatedProvisions 2 items
Question_103 individual committed

Was there an independent ethical obligation on Engineer A to formally notify the local public agency in writing that the drawings and specifications were incomplete before submitting them for federal review, and would such written notification have satisfied his professional obligations even if the agency chose to proceed anyway?

questionNumber 103
questionText Was there an independent ethical obligation on Engineer A to formally notify the local public agency in writing that the drawings and specifications were incomplete before submitting them for federal ...
questionType implicit
mentionedEntities {"capabilities": ["Engineer A Formal Written Project Failure Risk Advisory Failure", "Engineer A Incomplete Deliverable Self-Disclosure Failure"], "obligations": ["Engineer A Formal Client Risk...
relatedProvisions 3 items
Question_104 individual committed

To what extent did the competitive bidding process itself suffer an ethical injury independent of the parties' individual violations - specifically, were contractors other than Hi-Lo Construction harmed by being asked to price a project whose true scope was unknowable from the deficient documents?

questionNumber 104
questionText To what extent did the competitive bidding process itself suffer an ethical injury independent of the parties' individual violations — specifically, were contractors other than Hi-Lo Construction harm...
questionType implicit
mentionedEntities {"constraints": ["Engineer A Public Procurement Fairness Incomplete Bid Documents Dam Project"], "obligations": ["Engineer A Public Procurement Fairness Incomplete Bid Documents Dam Project"],...
relatedProvisions 2 items
Question_201 individual committed

Does the Faithful Agent Notification Obligation - which required Engineer A to serve the local public agency's interests by delivering on the contracted schedule - conflict with the Public Welfare Paramount principle, which required him to withhold or qualify incomplete documents that could endanger public safety on a dam project?

questionNumber 201
questionText Does the Faithful Agent Notification Obligation — which required Engineer A to serve the local public agency's interests by delivering on the contracted schedule — conflict with the Public Welfare Par...
questionType principle_tension
mentionedEntities {"constraints": ["Engineer A Schedule Pressure Non-Excuse Sealed Drawings Dam Project", "Engineer A Temporal Constraint Contract Delivery Deadline Dam Project"], "obligations": ["Engineer A...
relatedProvisions 3 items
Question_202 individual committed

Does the Responsible Charge Integrity principle - which demands that an engineer seal only complete and conforming documents - conflict with the Competence Boundary Recognition and Escalation Obligation imposed on Engineer B, in the sense that Engineer B's approval effectively ratified Engineer A's seal and may have created a false impression that a second competent professional had independently verified completeness?

questionNumber 202
questionText Does the Responsible Charge Integrity principle — which demands that an engineer seal only complete and conforming documents — conflict with the Competence Boundary Recognition and Escalation Obligati...
questionType principle_tension
mentionedEntities {"capabilities": ["Engineer B Responsible Charge Active Engagement Failure", "Engineer B Federal Plan Approval Substantive Technical Competence Verification Failure", "Engineer B Domain-Specific...
relatedProvisions 2 items
Question_203 individual committed

Does the Engineer-Contractor Dual Role Constructability Disclosure Obligation imposed on Engineer C - requiring him to flag unbuildable conditions before bidding - conflict with the Whistleblowing Personal Conscience Right recognized in BER Case No. 82-5, which treats disclosure of non-safety deficiencies as discretionary rather than mandatory, and if so, which principle should govern when the deficiency involves public funds but not immediate physical danger?

questionNumber 203
questionText Does the Engineer-Contractor Dual Role Constructability Disclosure Obligation imposed on Engineer C — requiring him to flag unbuildable conditions before bidding — conflict with the Whistleblowing Per...
questionType principle_tension
mentionedEntities {"obligations": ["Engineer C Constructability Deficiency Pre-Bid Disclosure Dam Project", "BER 82-5 Defense Engineer Whistleblower Personal Conscience Right Non-Mandatory"], "principles":...
relatedProvisions 2 items
Question_204 individual committed

Does the Honesty in Professional Representations principle - violated when Engineer A sealed incomplete documents - stand in tension with the Benevolent Motive Non-Cure principle, and does the Board's rejection of Engineer A's benevolent motive defense imply that good-faith assumptions about cost coverage can never substitute for transparent disclosure, even when the engineer genuinely believes no harm will result?

questionNumber 204
questionText Does the Honesty in Professional Representations principle — violated when Engineer A sealed incomplete documents — stand in tension with the Benevolent Motive Non-Cure principle, and does the Board's...
questionType principle_tension
mentionedEntities {"capabilities": ["Engineer A Funding Source Rationalization Non-Excuse Failure", "Engineer A Signed Sealed Document Integrity Significance Recognition Failure"], "obligations": ["Engineer A...
relatedProvisions 3 items
Question_301 individual committed

From a deontological perspective, did Engineer A fulfill his duty of honest professional representation when he signed and sealed drawings he knew to be incomplete, regardless of his belief that federal funds would cover any resulting cost overruns?

questionNumber 301
questionText From a deontological perspective, did Engineer A fulfill his duty of honest professional representation when he signed and sealed drawings he knew to be incomplete, regardless of his belief that feder...
questionType theoretical
mentionedEntities {"capabilities": ["Engineer A Signed Sealed Document Integrity Significance Recognition Failure"], "constraints": ["Engineer A Sealed Drawings Completeness Dam Project", "Engineer A Written Report...
relatedProvisions 3 items
Question_302 individual committed

From a consequentialist perspective, did Engineer A's rationalization that federal funds would absorb any cost overruns adequately account for the full range of foreseeable harms - including procurement unfairness, public fund waste, project delay, and erosion of public trust in engineering - that his submission of incomplete documents would foreseeably cause?

questionNumber 302
questionText From a consequentialist perspective, did Engineer A's rationalization that federal funds would absorb any cost overruns adequately account for the full range of foreseeable harms — including procureme...
questionType theoretical
mentionedEntities {"constraints": ["Engineer A Federal Funding Rationalization Non-Excuse Dam Project", "Engineer A Public Safety Paramount Incomplete Dam Design"], "obligations": ["Engineer A Funding Source...
relatedProvisions 3 items
Question_303 individual committed

From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and intellectual honesty expected of an engineer in responsible charge when he approved drawings he either did not adequately review or lacked the domain-specific competence to evaluate, and did his failure to escalate reflect a deficiency in the virtues of diligence and professional courage?

questionNumber 303
questionText From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and intellectual honesty expected of an engineer in responsible charge when he approved drawings he either did n...
questionType theoretical
mentionedEntities {"capabilities": ["Engineer B Responsible Charge Active Engagement Failure", "Engineer B Federal Plan Approval Substantive Technical Competence Verification Failure", "Engineer B Domain-Specific...
relatedProvisions 2 items
Question_304 individual committed

From a deontological perspective, did Engineer C, in his dual role as both a licensed engineer and a contractor, have a categorical professional duty to disclose known constructability deficiencies to the public agency before submitting a bid, rather than submitting a bid and raising those deficiencies only after winning the contract at the pre-construction conference?

questionNumber 304
questionText From a deontological perspective, did Engineer C, in his dual role as both a licensed engineer and a contractor, have a categorical professional duty to disclose known constructability deficiencies to...
questionType theoretical
mentionedEntities {"capabilities": ["Engineer C Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure", "Engineer C Pre-Bid Clarification Request Dam Project", "Engineer C Dual-Role Document Evaluation...
relatedProvisions 3 items
Question_401 individual committed

If Engineer A had formally notified the local public agency and the federal funding authority in writing of the known incompleteness of the drawings before the submission deadline - citing schedule pressure as the cause - would the ethical violations identified by the Board have been avoided, and would such disclosure have satisfied his obligations under the NSPE Code even if the incomplete documents were still submitted?

questionNumber 401
questionText If Engineer A had formally notified the local public agency and the federal funding authority in writing of the known incompleteness of the drawings before the submission deadline — citing schedule pr...
questionType counterfactual
mentionedEntities {"actions": ["Admit Incompleteness Without Prior Disclosure", "Submit Incomplete Design Documents"], "events": ["Incomplete Documents Enter Review"], "obligations": ["Engineer A Formal Client Risk...
relatedProvisions 3 items
Question_402 individual committed

If Engineer A had refused to submit the drawings by the contractual deadline and instead requested a schedule extension to complete the design properly, how would this have affected the project timeline, the federal funding commitment, and the ethical standing of all three engineers - and does the NSPE Code support contract deadline refusal as a required response to incompleteness pressure?

questionNumber 402
questionText If Engineer A had refused to submit the drawings by the contractual deadline and instead requested a schedule extension to complete the design properly, how would this have affected the project timeli...
questionType counterfactual
mentionedEntities {"actions": ["Submit Incomplete Design Documents"], "constraints": ["Engineer A Temporal Constraint Contract Delivery Deadline Dam Project", "Engineer A Schedule Pressure Non-Excuse Sealed...
relatedProvisions 3 items
Question_403 individual committed

If Engineer B had recognized the limits of his competence or the incompleteness of the submitted documents and escalated the review to a domain-qualified specialist or returned the drawings to Engineer A with a deficiency notice, would the project have proceeded to competitive bidding, and would Engineer C's ethical dilemma have arisen at all?

questionNumber 403
questionText If Engineer B had recognized the limits of his competence or the incompleteness of the submitted documents and escalated the review to a domain-qualified specialist or returned the drawings to Enginee...
questionType counterfactual
mentionedEntities {"actions": ["Approve Incomplete Design Documents"], "capabilities": ["Engineer B Competence Limitation Recognition Supervisor Escalation Dam Review", "Engineer B Responsible Charge Active...
relatedProvisions 2 items
Question_404 individual committed

If Engineer C, upon identifying the constructability deficiencies during his pre-bid review, had formally notified the local public agency and requested a clarification or addendum before submitting his bid, would this have triggered a re-evaluation of the entire procurement - and would such action have discharged his ethical obligations as both an engineer and a contractor, even if it disadvantaged his firm competitively?

questionNumber 404
questionText If Engineer C, upon identifying the constructability deficiencies during his pre-bid review, had formally notified the local public agency and requested a clarification or addendum before submitting h...
questionType counterfactual
mentionedEntities {"actions": ["Submit Low Bid on Inadequate Documents", "Raise Unbuildable Design at Pre-Construction"], "capabilities": ["Engineer C Pre-Bid Clarification Request Dam Project", "Engineer C...
relatedProvisions 3 items
Phase 2E: Rich Analysis
55 55 committed
causal normative link 7
CausalLink_Respond to Dam RFP individual committed

By responding to the RFP and accepting a full-service engineering contract, Engineer A assumes the obligation to deliver complete, buildable design documents, and any marketing representations made during this response cannot later excuse inadequate deliverables.

URI case-85#CausalLink_1
action id case-85#Respond_to_Dam_RFP
action label Respond to Dam RFP
fulfills obligations 2 items
guided by principles 2 items
constrained by 3 items
agent role http://proethica.org/ontology/case/85#Engineer_A_Dam_Design_Engineer
reasoning By responding to the RFP and accepting a full-service engineering contract, Engineer A assumes the obligation to deliver complete, buildable design documents, and any marketing representations made du...
confidence 0.82
CausalLink_Submit Incomplete Design Docum individual committed

Submitting signed-and-sealed but knowingly incomplete design documents without disclosure violates Engineer A's core obligations of completeness, honesty, and heightened duty to a technically unsupported client, while the contractual deadline constraint does not excuse the ethical breach.

URI case-85#CausalLink_2
action id case-85#Submit_Incomplete_Design_Documents
action label Submit Incomplete Design Documents
violates obligations 14 items
guided by principles 5 items
constrained by 10 items
agent role http://proethica.org/ontology/case/85#Engineer_A_Incomplete_Deliverable_Concealing_Design_Engineer
reasoning Submitting signed-and-sealed but knowingly incomplete design documents without disclosure violates Engineer A's core obligations of completeness, honesty, and heightened duty to a technically unsuppor...
confidence 0.97
CausalLink_Rationalize Incompleteness via individual committed

Engineer A's assertion that federal funding will cover cost overruns caused by incomplete documents constitutes a fraudulent misrepresentation that violates the principle that funding source is non-determinative of ethical obligation and that benevolent motive cannot cure a professional ethics breach.

URI case-85#CausalLink_3
action id case-85#Rationalize_Incompleteness_via_Federal_Funds
action label Rationalize Incompleteness via Federal Funds
violates obligations 4 items
guided by principles 7 items
constrained by 2 items
agent role http://proethica.org/ontology/case/85#Engineer_A_Incomplete_Deliverable_Concealing_Design_Engineer
reasoning Engineer A's assertion that federal funding will cover cost overruns caused by incomplete documents constitutes a fraudulent misrepresentation that violates the principle that funding source is non-de...
confidence 0.95
CausalLink_Approve Incomplete Design Docu individual committed

Engineer B's approval of Engineer A's incomplete documents without substantive technical review violates the obligation of responsible charge engagement and the constraint that federal plan approval requires genuine competence verification within the approving engineer's domain expertise.

URI case-85#CausalLink_4
action id case-85#Approve_Incomplete_Design_Documents
action label Approve Incomplete Design Documents
violates obligations 6 items
guided by principles 4 items
constrained by 3 items
agent role http://proethica.org/ontology/case/85#Engineer_B_Competence-Unrecognizing_Plan_Approval_Engineer
reasoning Engineer B's approval of Engineer A's incomplete documents without substantive technical review violates the obligation of responsible charge engagement and the constraint that federal plan approval r...
confidence 0.95
CausalLink_Submit Low Bid on Inadequate D individual committed

Engineer C, acting in a dual engineer-contractor role, violates the pre-bid constructability disclosure obligation by submitting a low bid on documents Engineer C recognized as deficient, rather than raising the deficiencies before bid submission as required by the engineer-contractor dual-role disclosure constraint.

URI case-85#CausalLink_5
action id case-85#Submit_Low_Bid_on_Inadequate_Documents
action label Submit Low Bid on Inadequate Documents
violates obligations 4 items
guided by principles 3 items
constrained by 2 items
agent role http://proethica.org/ontology/case/85#Engineer_C_Unbuildable_Contract_Bidding_Engineer-Contractor
reasoning Engineer C, acting in a dual engineer-contractor role, violates the pre-bid constructability disclosure obligation by submitting a low bid on documents Engineer C recognized as deficient, rather than ...
confidence 0.93
CausalLink_Raise Unbuildable Design at Pr individual committed

Engineer C, acting in the dual role of engineer-contractor, fulfills the constructability disclosure obligation by raising the unbuildable design at the pre-construction conference, though this disclosure comes post-award rather than pre-bid, which partially undermines the public procurement fairness constraint that ideally required earlier disclosure.

URI case-85#CausalLink_6
action id case-85#Raise_Unbuildable_Design_at_Pre-Construction
action label Raise Unbuildable Design at Pre-Construction
fulfills obligations 4 items
guided by principles 4 items
constrained by 3 items
agent role http://proethica.org/ontology/case/85#Engineer_C_Hi-Lo_Construction_Contractor
reasoning Engineer C, acting in the dual role of engineer-contractor, fulfills the constructability disclosure obligation by raising the unbuildable design at the pre-construction conference, though this disclo...
confidence 0.82
CausalLink_Admit Incompleteness Without P individual committed

Engineer A's belated admission of incompleteness without prior disclosure partially satisfies professional accountability obligations in retrospect but fundamentally violates the core obligations of timely client disclosure, sealed document completeness certification, and heightened duty to a technically unsupported client, all of which required proactive disclosure before submission rather than reactive admission after harm had propagated through federal approval and contract award.

URI case-85#CausalLink_7
action id case-85#Admit_Incompleteness_Without_Prior_Disclosure
action label Admit Incompleteness Without Prior Disclosure
fulfills obligations 3 items
violates obligations 9 items
guided by principles 5 items
constrained by 6 items
agent role http://proethica.org/ontology/case/85#Engineer_A_Incomplete_Deliverable_Concealing_Design_Engineer
reasoning Engineer A's belated admission of incompleteness without prior disclosure partially satisfies professional accountability obligations in retrospect but fundamentally violates the core obligations of t...
confidence 0.85
question emergence 19
QuestionEmergence_1 individual committed

This question emerged because Engineer A's submission created a direct collision between the obligation to deliver complete, honest professional work and the rationalization that external pressures and funding structures neutralized the harm of incompleteness. The question persists because the data - a knowingly deficient sealed submission without client disclosure - is unambiguous, yet Engineer A's stated justifications invoke conditions that, if valid, would rebut the standard completeness warrant.

URI case-85#Q1
question uri case-85#Q1
question text Was it ethical for Engineer A to submit final drawings and specifications for review and approval that he knew were incomplete?
data events 4 items
data actions 3 items
involves roles 4 items
competing warrants 3 items
data warrant tension Engineer A's act of submitting signed and sealed drawings he knew to be incomplete simultaneously triggers the warrant that a professional must deliver complete work and the competing claim that deadl...
competing claims One warrant concludes that submitting knowingly incomplete sealed documents is an unambiguous ethical violation regardless of circumstance, while the competing warrant suggests that contractual deadli...
rebuttal conditions Uncertainty arises because if schedule pressure were a recognized professional excuse for incomplete deliverables, or if federal funding mechanisms routinely absorbed such gaps with no harm to the cli...
emergence narrative This question emerged because Engineer A's submission created a direct collision between the obligation to deliver complete, honest professional work and the rationalization that external pressures an...
confidence 0.93
QuestionEmergence_2 individual committed

This question arose because Engineer B's approval action sits at the intersection of two contested warrants: the duty to review competently and the duty to recognize and escalate beyond one's competence boundaries. The ethical question is non-trivial because the data shows approval of deficient documents, but the rebuttal condition - that Engineer B may have lacked the capacity to detect what Engineer A deliberately concealed - creates genuine uncertainty about whether his failure was ethical violation or epistemic limitation.

URI case-85#Q2
question uri case-85#Q2
question text Was it ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding?
data events 3 items
data actions 1 items
involves roles 4 items
competing warrants 3 items
data warrant tension Engineer B's approval of documents he lacked the domain-specific competence to evaluate triggers both the warrant that a reviewing engineer must conduct substantive technical review and the competing ...
competing claims One warrant concludes that Engineer B violated his professional duty by approving documents without substantive technical verification, while a competing warrant suggests that if Engineer B genuinely ...
rebuttal conditions Uncertainty is created by the condition that if Engineer B's role was procedural rather than substantive — i.e., if federal approval was intended only as administrative clearance rather than independe...
emergence narrative This question arose because Engineer B's approval action sits at the intersection of two contested warrants: the duty to review competently and the duty to recognize and escalate beyond one's competen...
confidence 0.91
QuestionEmergence_3 individual committed

This question emerged because Engineer C's engineer-contractor dual role creates a warrant collision that would not exist for a pure contractor: his professional engineering credentials impose disclosure obligations that ordinary bidders do not carry, yet the competitive bidding context creates structural incentives and norms that cut against pre-bid disclosure. The post-award timing of his unbuildability declaration further destabilizes the warrant structure by making it unclear whether his silence during bidding was strategic concealment or genuine post-award discovery.

URI case-85#Q3
question uri case-85#Q3
question text Was it ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes?
data events 3 items
data actions 2 items
involves roles 5 items
competing warrants 3 items
data warrant tension Engineer C's submission of a low bid on documents he later characterized as unbuildable triggers the warrant that an engineer-contractor must disclose known constructability deficiencies before biddin...
competing claims One warrant concludes that Engineer C's dual role as engineer and contractor imposed a heightened obligation to disclose pre-bid constructability concerns rather than exploit them post-award, while a ...
rebuttal conditions Uncertainty arises because if Engineer C identified the unbuildability only after contract award rather than during bid preparation, the pre-bid disclosure warrant would not apply; additionally, if co...
emergence narrative This question emerged because Engineer C's engineer-contractor dual role creates a warrant collision that would not exist for a pure contractor: his professional engineering credentials impose disclos...
confidence 0.89
QuestionEmergence_4 individual committed

This question emerged as an aggravated form of Q1 because the federal funding dimension transforms a straightforward completeness violation into a potential fraud question: Engineer A's internal rationalization that federal funds would absorb overruns is not merely a mitigating excuse but evidence of a deliberate strategy that exploits public resources, which the fraud and misrepresentation warrant treats as aggravating rather than mitigating. The question persists because the rebuttal conditions - good faith, disclosure, or permissive grant structures - are factually contested and could fundamentally alter the ethical characterization.

URI case-85#Q4
question uri case-85#Q4
question text Did Engineer A's submission of a signed and sealed set of incomplete drawings constitute fraud or misrepresentation toward the federal funding agency, and does the fact that he anticipated federal fun...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 3 items
data warrant tension Engineer A's act of sealing incomplete drawings while privately anticipating that federal funds would absorb resulting cost overruns simultaneously triggers the fraud and misrepresentation prohibition...
competing claims One warrant concludes that submitting sealed incomplete drawings to a federal funding agency while internally rationalizing cost overrun absorption constitutes aggravated misrepresentation because it ...
rebuttal conditions Uncertainty is created by the condition that if Engineer A disclosed the incompleteness to any party in the approval chain, or if federal grant mechanisms explicitly contemplated and permitted iterati...
emergence narrative This question emerged as an aggravated form of Q1 because the federal funding dimension transforms a straightforward completeness violation into a potential fraud question: Engineer A's internal ratio...
confidence 0.9
QuestionEmergence_5 individual committed

This question emerged as a structural refinement of Q1 because it isolates the client-vulnerability dimension as an independent ethical variable: the local agency's technical review incapacity is not merely background context but a fact that, under the heightened disclosure warrant, transforms Engineer A's standard completeness obligation into an affirmative, proactive duty to disclose. The question is analytically distinct because it asks whether the identity and capacity of the client modifies the warrant structure itself, rather than simply whether Engineer A violated a fixed standard.

URI case-85#Q5
question uri case-85#Q5
question text Given that the local public agency lacked the in-house technical capacity to evaluate the drawings and specifications, did Engineer A bear a heightened affirmative duty to disclose incompleteness prec...
data events 3 items
data actions 2 items
involves roles 4 items
competing warrants 3 items
data warrant tension The local public agency's documented incapacity to independently evaluate Engineer A's drawings triggers both the standard faithful-agent disclosure warrant and a heightened affirmative disclosure war...
competing claims One warrant concludes that Engineer A's disclosure obligation was heightened — not merely standard — because the client's technical unsophistication created total epistemic dependence on Engineer A's ...
rebuttal conditions Uncertainty arises because if the heightened disclosure warrant is accepted, it must be bounded: if client technical incapacity always escalates engineer obligations, the warrant could impose an unlim...
emergence narrative This question emerged as a structural refinement of Q1 because it isolates the client-vulnerability dimension as an independent ethical variable: the local agency's technical review incapacity is not ...
confidence 0.92
QuestionEmergence_6 individual committed

This question arose because Engineer C occupied two roles simultaneously - licensed engineer and contractor - each governed by a different warrant structure: contractors routinely bid and clarify scope post-award, but engineers bear a categorical pre-bid disclosure duty when they possess professional knowledge of constructability failures. The post-award timing of Engineer C's disclosure at the pre-construction conference made the role-based warrant conflict unavoidable and ethically consequential.

URI case-85#Q6
question uri case-85#Q6
question text From a deontological perspective, did Engineer C, in his dual role as both a licensed engineer and a contractor, have a categorical professional duty to disclose known constructability deficiencies to...
data events 3 items
data actions 2 items
involves roles 5 items
competing warrants 2 items
data warrant tension Engineer C's dual status as a licensed engineer and a contractor means that the same act of submitting a bid on deficient documents simultaneously triggers the contractor's competitive bidding warrant...
competing claims The contractor warrant concludes that raising deficiencies at the pre-construction conference is a normal and acceptable industry practice, while the engineer-professional warrant concludes that Engin...
rebuttal conditions The categorical disclosure duty is uncertain if Engineer C's engineering knowledge of the deficiencies was not sufficiently crystallized before bid submission, or if the deficiencies were only discove...
emergence narrative This question arose because Engineer C occupied two roles simultaneously — licensed engineer and contractor — each governed by a different warrant structure: contractors routinely bid and clarify scop...
confidence 0.87
QuestionEmergence_7 individual committed

This question arose because Engineer A's submission to a technically unsupported client created a gap between the general disclosure norm and the heightened proactive-notification norm: the local agency's incapacity to evaluate the documents meant that ordinary disclosure mechanisms were structurally insufficient, raising the question of whether a formal written warning was an independent ethical obligation rather than merely a best practice. The further sub-question - whether agency acquiescence after written notice would have discharged Engineer A's duty - emerged because the warrant's purpose (protecting a vulnerable client) is not obviously satisfied by notification alone if the agency proceeds anyway.

URI case-85#Q7
question uri case-85#Q7
question text Was there an independent ethical obligation on Engineer A to formally notify the local public agency in writing that the drawings and specifications were incomplete before submitting them for federal ...
data events 4 items
data actions 3 items
involves roles 4 items
competing warrants 2 items
data warrant tension Engineer A submitted signed and sealed drawings he knew to be incomplete to a client he knew lacked technical capacity to detect the deficiency, which simultaneously triggers the general disclosure wa...
competing claims One warrant concludes that any form of disclosure — including post-submission acknowledgment — satisfies the obligation, while the heightened-disclosure warrant concludes that formal written notificat...
rebuttal conditions The independent written-notification obligation is uncertain if the agency already possessed constructive knowledge of the incompleteness through prior communications, or if the federal review process...
emergence narrative This question arose because Engineer A's submission to a technically unsupported client created a gap between the general disclosure norm and the heightened proactive-notification norm: the local agen...
confidence 0.85
QuestionEmergence_8 individual committed

This question arose because the standard ethical analysis of the case focused on Engineer A, Engineer B, and Engineer C as individual wrongdoers, leaving unexamined whether the competitive bidding process - as an institution designed to produce fair pricing and equal opportunity - suffered its own cognizable ethical injury when deficient documents were released to the market. The question became necessary because non-winning bidders expended resources and assumed risks on a project whose true scope was structurally unknowable, a harm that no individual-violation finding directly addresses.

URI case-85#Q8
question uri case-85#Q8
question text To what extent did the competitive bidding process itself suffer an ethical injury independent of the parties' individual violations — specifically, were contractors other than Hi-Lo Construction harm...
data events 3 items
data actions 2 items
involves roles 5 items
competing warrants 2 items
data warrant tension The release of deficient bid documents to the competitive market triggers both the individual-harm warrant (Engineer A wronged the client and winning contractor) and the systemic-harm warrant (the com...
competing claims The individual-harm warrant concludes that ethical injury is fully accounted for by Engineer A's and Engineer B's violations against the client and by Engineer C's post-award conduct, while the system...
rebuttal conditions The systemic-harm claim is uncertain if competitive bidding norms already price in document risk and bidders are understood to bear the cost of evaluating document adequacy, or if the deficiencies wer...
emergence narrative This question arose because the standard ethical analysis of the case focused on Engineer A, Engineer B, and Engineer C as individual wrongdoers, leaving unexamined whether the competitive bidding pro...
confidence 0.82
QuestionEmergence_9 individual committed

This question arose because Engineer A faced a genuine structural conflict between two independently valid professional obligations: the duty to serve the client's schedule and funding interests, and the duty to protect the public from the risks of an incomplete dam design. The conflict was not merely apparent but real, because satisfying the faithful-agent obligation required the very act - timely submission - that the public-welfare obligation prohibited, making it impossible to fully honor both warrants simultaneously.

URI case-85#Q9
question uri case-85#Q9
question text Does the Faithful Agent Notification Obligation — which required Engineer A to serve the local public agency's interests by delivering on the contracted schedule — conflict with the Public Welfare Par...
data events 4 items
data actions 2 items
involves roles 5 items
competing warrants 2 items
data warrant tension Engineer A's contractual deadline created simultaneous pressure from the faithful-agent warrant (deliver on schedule to serve the client's project timeline and funding obligations) and the public-welf...
competing claims The faithful-agent warrant concludes that Engineer A was obligated to meet the delivery schedule and that any deficiencies should have been flagged through normal professional channels without halting...
rebuttal conditions The conflict is uncertain if the incompleteness of the documents did not rise to the level of a public safety threat at the time of submission — i.e., if the deficiencies were design-development gaps ...
emergence narrative This question arose because Engineer A faced a genuine structural conflict between two independently valid professional obligations: the duty to serve the client's schedule and funding interests, and ...
confidence 0.88
QuestionEmergence_10 individual committed

This question arose because Engineer B's approval created an ambiguous signal in the professional record: a second licensed engineer had reviewed and approved documents that were substantively incomplete, and it was unclear whether that approval constituted an independent professional endorsement of completeness or merely a bureaucratic step in the federal funding process. The deeper conflict emerged because the two obligations governing Engineer B - seal integrity and competence-boundary recognition - point in opposite directions: the former demands that approval mean something substantive, while the latter demands that Engineer B acknowledge he lacked the expertise to make that substantive judgment.

URI case-85#Q10
question uri case-85#Q10
question text Does the Responsible Charge Integrity principle — which demands that an engineer seal only complete and conforming documents — conflict with the Competence Boundary Recognition and Escalation Obligati...
data events 3 items
data actions 2 items
involves roles 5 items
competing warrants 2 items
data warrant tension Engineer B's approval of Engineer A's already-sealed incomplete documents triggers both the responsible-charge-integrity warrant (Engineer B's own seal or approval carries an independent completeness ...
competing claims The responsible-charge-integrity warrant concludes that Engineer B's approval effectively ratified Engineer A's seal and created a false impression of independent professional verification of complete...
rebuttal conditions The conflict is uncertain if Engineer B's approval role was institutionally defined as a procedural funding-eligibility check rather than a substantive engineering review, which would rebut the claim ...
emergence narrative This question arose because Engineer B's approval created an ambiguous signal in the professional record: a second licensed engineer had reviewed and approved documents that were substantively incompl...
confidence 0.86
QuestionEmergence_11 individual committed

This question emerged because Engineer A's admitted incompleteness, combined with his failure to notify anyone in writing before submission, left open the counterfactual of whether disclosure alone could have satisfied his obligations under the NSPE Code. The tension between the Sealed Document Completeness Certification Accuracy Obligation and the Proactive Risk Disclosure Obligation creates genuine uncertainty about whether the ethical violation resided in the act of sealing, the act of concealment, or both - making the hypothetical disclosure scenario a live ethical question rather than a settled one.

URI case-85#Q11
question uri case-85#Q11
question text If Engineer A had formally notified the local public agency and the federal funding authority in writing of the known incompleteness of the drawings before the submission deadline — citing schedule pr...
data events 3 items
data actions 3 items
involves roles 4 items
competing warrants 3 items
data warrant tension Engineer A's submission of knowingly incomplete sealed documents under deadline pressure simultaneously triggers the Sealed Document Completeness Certification Accuracy Obligation — which is violated ...
competing claims One warrant concludes that sealing incomplete documents is categorically impermissible regardless of accompanying disclosure, while a competing warrant concludes that proactive written notification to...
rebuttal conditions Uncertainty arises because the NSPE Code's Honesty in Professional Representations principle and the Responsible Charge Integrity obligation may treat the act of sealing as an independent, non-curable...
emergence narrative This question emerged because Engineer A's admitted incompleteness, combined with his failure to notify anyone in writing before submission, left open the counterfactual of whether disclosure alone co...
confidence 0.82
QuestionEmergence_12 individual committed

This question arose because Engineer C occupied a structurally unique dual role that neither the BER 82-5 precedent nor the standard constructability disclosure framework was designed to address in isolation. The collision between the mandatory Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation and the discretionary Whistleblower Personal Conscience Right - in a context involving public funds but no immediate physical danger - created a genuine normative gap that the question attempts to resolve.

URI case-85#Q12
question uri case-85#Q12
question text Does the Engineer-Contractor Dual Role Constructability Disclosure Obligation imposed on Engineer C — requiring him to flag unbuildable conditions before bidding — conflict with the Whistleblowing Per...
data events 3 items
data actions 2 items
involves roles 6 items
competing warrants 3 items
data warrant tension Engineer C's dual status as both engineer and contractor on deficient documents triggers the Engineer-Contractor Dual Role Constructability Disclosure Obligation — which imposes a mandatory pre-bid du...
competing claims The Engineer-Contractor Dual Role Constructability Disclosure Obligation concludes that Engineer C was required to disclose the unbuildable condition before bidding because his engineering expertise c...
rebuttal conditions Uncertainty is created by the rebuttal condition embedded in BER Case No. 82-5 itself: the discretionary whistleblowing right applies when the deficiency does not implicate public safety, but the Curr...
emergence narrative This question arose because Engineer C occupied a structurally unique dual role that neither the BER 82-5 precedent nor the standard constructability disclosure framework was designed to address in is...
confidence 0.85
QuestionEmergence_13 individual committed

This question emerged because the Board's explicit rejection of Engineer A's benevolent motive defense left unresolved the deeper normative question of whether the NSPE Code's honesty obligations are purely conduct-based or also incorporate intent as a relevant variable. The tension between the Honesty in Professional Representations principle and the Benevolent Motive Non-Cure principle forces a determination of whether good-faith assumptions about cost coverage can ever substitute for transparent disclosure - a question the Board answered implicitly but did not fully theorize.

URI case-85#Q13
question uri case-85#Q13
question text Does the Honesty in Professional Representations principle — violated when Engineer A sealed incomplete documents — stand in tension with the Benevolent Motive Non-Cure principle, and does the Board's...
data events 2 items
data actions 3 items
involves roles 4 items
competing warrants 3 items
data warrant tension Engineer A's genuine belief that federal funds would absorb cost overruns — the Federal Funding Cost-Coverage Rationalization State — simultaneously invokes the Honesty in Professional Representations...
competing claims The Honesty in Professional Representations principle concludes that sealing incomplete documents constitutes an objective misrepresentation irrespective of Engineer A's intent, while a competing warr...
rebuttal conditions Uncertainty is generated by the rebuttal condition that the Benevolent Motive Non-Cure principle would not apply if the NSPE Code treats the professional seal as a strict-liability certification of co...
emergence narrative This question emerged because the Board's explicit rejection of Engineer A's benevolent motive defense left unresolved the deeper normative question of whether the NSPE Code's honesty obligations are ...
confidence 0.87
QuestionEmergence_14 individual committed

This question arose because the deontological framing of Engineer A's conduct requires a determination of whether the duty of honest professional representation is violated by the objective fact of incompleteness or by the subjective intent to deceive - a distinction the Board's analysis did not fully resolve. The Schedule Pressure Non-Excuse Constraint and the Funding Source Non-Determinative principle together eliminate Engineer A's available defenses, but they do not settle whether the duty itself is absolute or admits of reasonable-judgment exceptions.

URI case-85#Q14
question uri case-85#Q14
question text From a deontological perspective, did Engineer A fulfill his duty of honest professional representation when he signed and sealed drawings he knew to be incomplete, regardless of his belief that feder...
data events 3 items
data actions 2 items
involves roles 4 items
competing warrants 3 items
data warrant tension Engineer A's act of signing and sealing drawings he knew to be incomplete — the Engineer A Knowingly Incomplete Deliverable Submitted state — triggers the deontological Sealed Document Completeness Ce...
competing claims The deontological warrant concludes that Engineer A violated his duty of honest professional representation categorically — because the act of sealing constitutes a representation of completeness that...
rebuttal conditions Uncertainty arises from the rebuttal condition that deontological duty fulfillment might be assessed relative to the engineer's reasonable professional judgment at the time of sealing rather than the ...
emergence narrative This question arose because the deontological framing of Engineer A's conduct requires a determination of whether the duty of honest professional representation is violated by the objective fact of in...
confidence 0.88
QuestionEmergence_15 individual committed

This question arose because Engineer A's rationalization was framed in consequentialist terms - federal funds will cover any harm - but was evaluated by the Board primarily through deontological principles, leaving open the question of whether the rationalization also fails on its own consequentialist terms. The gap between Engineer A's narrow harm-accounting and the full range of foreseeable harms catalogued by the Public Welfare Paramount, Public Procurement Fairness, and Public Funds Unjustified Expenditure principles created the analytical space for this question to emerge as a distinct consequentialist inquiry.

URI case-85#Q15
question uri case-85#Q15
question text From a consequentialist perspective, did Engineer A's rationalization that federal funds would absorb any cost overruns adequately account for the full range of foreseeable harms — including procureme...
data events 4 items
data actions 3 items
involves roles 6 items
competing warrants 3 items
data warrant tension Engineer A's consequentialist rationalization — that federal funds would absorb cost overruns, making the submission harmless — triggers the Funding Source Non-Determinative of Ethical Obligation prin...
competing claims Engineer A's consequentialist rationalization concludes that federal cost absorption renders the submission net-harmless, while the competing consequentialist warrant — properly accounting for procure...
rebuttal conditions Uncertainty is created by the rebuttal condition that a consequentialist evaluation of Engineer A's rationalization depends on what harms were actually foreseeable to a reasonable engineer at the time...
emergence narrative This question arose because Engineer A's rationalization was framed in consequentialist terms — federal funds will cover any harm — but was evaluated by the Board primarily through deontological princ...
confidence 0.86
QuestionEmergence_16 individual committed

The question emerged because Engineer B's approval action created a factual record that is simultaneously consistent with two distinct ethical failures - inadequate review and unrecognized incompetence - and virtue ethics demands that the character source of the failure be identified, not merely the outcome. Because the data (approval of deficient documents) is undisputed but the internal epistemic state of Engineer B is not, the question of which virtue was deficient - diligence, courage, or competence self-awareness - cannot be resolved without probing the warrant structure underlying responsible charge.

URI case-85#Q16
question uri case-85#Q16
question text From a virtue ethics perspective, did Engineer B demonstrate the professional integrity and intellectual honesty expected of an engineer in responsible charge when he approved drawings he either did n...
data events 3 items
data actions 1 items
involves roles 3 items
competing warrants 3 items
data warrant tension Engineer B's act of approving deficient documents simultaneously triggers the warrant that responsible charge requires substantive engagement and the warrant that competence boundaries must be recogni...
competing claims One warrant concludes Engineer B violated professional integrity by approving documents he did not adequately review, while a competing warrant concludes he violated intellectual honesty by failing to...
rebuttal conditions Uncertainty arises if Engineer B possessed sufficient general engineering competence to conduct a facially adequate review and the deficiencies were latent enough that a reasonably diligent reviewer i...
emergence narrative The question emerged because Engineer B's approval action created a factual record that is simultaneously consistent with two distinct ethical failures — inadequate review and unrecognized incompetenc...
confidence 0.87
QuestionEmergence_17 individual committed

This question arose because the data establishes that Engineer A faced a genuine structural conflict between a contractual deadline and a professional completeness obligation, and the ethical analysis must determine whether the Code's schedule-pressure non-excuse principle rises to the level of mandating contract refusal or merely prohibiting concealment. The federal funding dimension adds a second layer of warrant competition because the funding commitment creates institutional pressure that Engineer A used as rationalization, forcing the question of whether that pressure modifies any of the applicable obligations or is categorically non-determinative.

URI case-85#Q17
question uri case-85#Q17
question text If Engineer A had refused to submit the drawings by the contractual deadline and instead requested a schedule extension to complete the design properly, how would this have affected the project timeli...
data events 3 items
data actions 2 items
involves roles 4 items
competing warrants 4 items
data warrant tension The contractual deadline and federal funding commitment together create a data context in which the warrant demanding complete design delivery and the warrant demanding resistance to schedule pressure...
competing claims One warrant concludes Engineer A was obligated to refuse submission and request an extension to fulfill the complete design delivery duty, while a competing warrant — grounded in faithful agent obliga...
rebuttal conditions Uncertainty arises if the NSPE Code does not affirmatively mandate contract deadline refusal as a required response — as opposed to a permissible one — and if disclosure with client consent could sati...
emergence narrative This question arose because the data establishes that Engineer A faced a genuine structural conflict between a contractual deadline and a professional completeness obligation, and the ethical analysis...
confidence 0.85
QuestionEmergence_18 individual committed

This question arose as a counterfactual causal inquiry because the ethical significance of Engineer B's failure depends on whether his intervention at the review stage was a necessary condition for Engineer C's dilemma - if Engineer B's proper action would have broken the causal chain, his ethical failure is not merely personal but structurally determinative of the entire downstream harm. The competing warrants about substantive review versus competence escalation create uncertainty about which specific obligation, if fulfilled, would have been causally sufficient to prevent the project from proceeding to competitive bidding on deficient documents.

URI case-85#Q18
question uri case-85#Q18
question text If Engineer B had recognized the limits of his competence or the incompleteness of the submitted documents and escalated the review to a domain-qualified specialist or returned the drawings to Enginee...
data events 4 items
data actions 1 items
involves roles 6 items
competing warrants 3 items
data warrant tension Engineer B's approval of incomplete documents triggers both the warrant that substantive competence review was required before approval and the warrant that competence boundary recognition obligated e...
competing claims One warrant concludes that had Engineer B conducted a substantively competent review he would have detected the deficiencies and returned the documents, preventing bidding; a competing warrant conclud...
rebuttal conditions Uncertainty arises if the deficiencies in Engineer A's documents were of a character that a competent dam-design reviewer would have detected through standard plan review procedures, in which case the...
emergence narrative This question arose as a counterfactual causal inquiry because the ethical significance of Engineer B's failure depends on whether his intervention at the review stage was a necessary condition for En...
confidence 0.88
QuestionEmergence_19 individual committed

This question arose because Engineer C occupied a dual role that activated two distinct and partially conflicting warrant structures - the engineering professional's disclosure obligation and the contractor's competitive bidding interest - and the data showing pre-bid deficiency identification made the conflict unavoidable rather than hypothetical. The question of whether formal pre-bid notification would have triggered procurement re-evaluation adds a consequentialist dimension that competes with the deontological discharge-of-obligation framing, forcing analysis of whether the ethical obligation is defined by the act of disclosure or by its systemic effect on the procurement.

URI case-85#Q19
question uri case-85#Q19
question text If Engineer C, upon identifying the constructability deficiencies during his pre-bid review, had formally notified the local public agency and requested a clarification or addendum before submitting h...
data events 3 items
data actions 2 items
involves roles 6 items
competing warrants 4 items
data warrant tension Engineer C's pre-bid identification of constructability deficiencies triggers simultaneously the warrant that his dual engineer-contractor role obligated pre-bid disclosure and the warrant that public...
competing claims One warrant concludes Engineer C was obligated to formally notify the local public agency and request a clarification addendum before bidding, thereby discharging his dual-role disclosure obligation e...
rebuttal conditions Uncertainty arises if the NSPE Code's pre-bid disclosure obligation for engineer-contractors is not clearly established as mandatory rather than aspirational, and if Engineer C's competitive disadvant...
emergence narrative This question arose because Engineer C occupied a dual role that activated two distinct and partially conflicting warrant structures — the engineering professional's disclosure obligation and the cont...
confidence 0.86
resolution pattern 29
ResolutionPattern_1 individual committed

The board concluded that Engineer A's ethical violation was aggravated beyond a baseline omission because the local public agency's complete inability to detect deficiencies imposed a heightened affirmative duty of disclosure; his silence in the face of that dependency was not a neutral omission but a form of professional exploitation of client vulnerability, making his conduct more culpable than it would have been with a technically sophisticated client.

URI case-85#C1
conclusion uri case-85#C1
conclusion text Beyond the Board's finding that Engineer A acted unethically in submitting incomplete drawings, his conduct was further aggravated by the specific vulnerability of his client. The local public agency ...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board resolved any tension between the baseline disclosure duty and a heightened duty by holding that the client's technical incapacity eliminated any discretion Engineer A might otherwise have ha...
resolution narrative The board concluded that Engineer A's ethical violation was aggravated beyond a baseline omission because the local public agency's complete inability to detect deficiencies imposed a heightened affir...
confidence 0.87
ResolutionPattern_2 individual committed

The board concluded that Engineer C acted unethically because his professional engineering license imposed a categorical duty to disclose known constructability deficiencies before submitting his bid, not after winning it; by using his professional judgment to assess risk to his own firm while withholding that same judgment from the public agency and competing bidders, he selectively exploited his licensure for private competitive advantage in a manner fundamentally inconsistent with the obligations that accompany a professional engineering license.

URI case-85#C2
conclusion uri case-85#C2
conclusion text From a deontological perspective, Engineer C's dual status as both a licensed professional engineer and a contractor created a categorical professional duty to disclose known constructability deficien...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board resolved the tension between competitive bidding norms (which might permit strategic information retention) and professional engineering duties by holding that the engineering license create...
resolution narrative The board concluded that Engineer C acted unethically because his professional engineering license imposed a categorical duty to disclose known constructability deficiencies before submitting his bid,...
confidence 0.91
ResolutionPattern_3 individual committed

The board concluded that the apparent conflict between mandatory disclosure and the discretionary whistleblowing framework of BER 82-5 was resolvable in favor of mandatory disclosure because Engineer C's situation differed in two critical respects: he was an independent contractor (not an employee acting against an employer) and his knowledge arose directly from a professional engineering evaluation of procurement documents, making disclosure obligatory rather than a matter of personal conscience.

URI case-85#C3
conclusion uri case-85#C3
conclusion text The tension between Engineer C's constructability disclosure obligation and the discretionary whistleblowing framework recognized in BER Case No. 82-5 is real but resolvable in favor of mandatory disc...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board resolved the conflict between the discretionary whistleblowing right recognized in BER 82-5 and the mandatory constructability disclosure obligation by distinguishing the two cases on their ...
resolution narrative The board concluded that the apparent conflict between mandatory disclosure and the discretionary whistleblowing framework of BER 82-5 was resolvable in favor of mandatory disclosure because Engineer ...
confidence 0.89
ResolutionPattern_4 individual committed

The board concluded that Engineer A's submission of signed and sealed incomplete drawings constituted misrepresentation aggravated - not mitigated - by his federal funds rationalization, because the act of sealing carried an implicit professional certification of completeness, and his private assumption that public money would cover his professional shortfall demonstrated not only knowledge of the deficiency but a calculated decision to conceal it from the very agency whose resources he intended to exploit.

URI case-85#C4
conclusion uri case-85#C4
conclusion text Engineer A's submission of signed and sealed incomplete drawings to the federal funding agency constituted a form of misrepresentation that is aggravated, not mitigated, by his assumption that federal...
answers questions 5 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board rejected any mitigating weight for Engineer A's benevolent motive by holding that the act of sealing is an independent professional representation whose integrity cannot be subordinated to p...
resolution narrative The board concluded that Engineer A's submission of signed and sealed incomplete drawings constituted misrepresentation aggravated — not mitigated — by his federal funds rationalization, because the a...
confidence 0.93
ResolutionPattern_5 individual committed

The board reached the foundational conclusion that Engineer A acted unethically by determining that submitting drawings and specifications for review and approval while knowing they were incomplete is a straightforward violation of the engineer's duty of honest professional representation, with no countervailing consideration - including schedule pressure or anticipated federal cost absorption - sufficient to justify or excuse the conduct.

URI case-85#C5
conclusion uri case-85#C5
conclusion text It was not ethical for Engineer A to submit drawings and specifications for review and approval that he knew were incomplete.
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board did not identify a competing obligation sufficient to justify submission of known incomplete documents — the baseline ethical prohibition on submitting incomplete work for approval was treat...
resolution narrative The board reached the foundational conclusion that Engineer A acted unethically by determining that submitting drawings and specifications for review and approval while knowing they were incomplete is...
confidence 0.97
ResolutionPattern_6 individual committed

The board concluded that Engineer B acted unethically because his approval of incomplete drawings on behalf of the Federal government constituted an implicit professional representation of adequacy that was false; by approving documents he either did not adequately review or lacked the competence to evaluate, he enabled a deficient design to enter competitive bidding in violation of the public welfare paramount principle and the prohibition on deceptive acts.

URI case-85#C6
conclusion uri case-85#C6
conclusion text It was not ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding.
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board treated Engineer B's approval authority as inseparable from a verification obligation, finding that any competing pressure to expedite federal review could not override the duty to withhold ...
resolution narrative The board concluded that Engineer B acted unethically because his approval of incomplete drawings on behalf of the Federal government constituted an implicit professional representation of adequacy th...
confidence 0.87
ResolutionPattern_7 individual committed

The board concluded that Engineer C acted unethically because submitting a bid on a project he knew to be unbuildable without disclosing that fact to the public agency was a deceptive act inconsistent with the objectivity and truthfulness required of a licensed engineer, regardless of whether he was acting in his capacity as a contractor at the time of bidding; the timing of his disclosure - after contract award rather than before bidding - compounded the ethical violation by depriving the agency of the ability to correct the deficiencies before procurement.

URI case-85#C7
conclusion uri case-85#C7
conclusion text It was not ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes.
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board rejected any argument that Engineer C's contractor role relieved him of professional disclosure duties, finding that his dual status as a licensed engineer imposed an affirmative obligation ...
resolution narrative The board concluded that Engineer C acted unethically because submitting a bid on a project he knew to be unbuildable without disclosing that fact to the public agency was a deceptive act inconsistent...
confidence 0.85
ResolutionPattern_8 individual committed

The board concluded from a virtue ethics perspective that Engineer B's approval of incomplete drawings reflected not merely a technical code violation but a deeper failure of professional character, specifically the absence of diligence (failure to review adequately), intellectual honesty (failure to acknowledge competence limits), and professional courage (failure to return deficient documents), and that the Board's prior conclusion, while correct, understated the moral gravity of this tripartite virtue failure.

URI case-85#C8
conclusion uri case-85#C8
conclusion text From a virtue ethics perspective, Engineer B's approval of the incomplete drawings reflects deficiencies in at least three professional virtues: diligence, intellectual honesty, and professional coura...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board, applying virtue ethics, found that no competing obligation — including schedule pressure or deference to the submitting engineer's seal — could justify the simultaneous absence of diligence...
resolution narrative The board concluded from a virtue ethics perspective that Engineer B's approval of incomplete drawings reflected not merely a technical code violation but a deeper failure of professional character, s...
confidence 0.83
ResolutionPattern_9 individual committed

The board concluded that Engineer A's submission of incomplete drawings inflicted an independent ethical injury on the competitive bidding process itself - beyond the harms to his direct client, the federal agency, and Engineer C - because every contractor who priced the project was denied the accurate scope information necessary to submit a genuine bid, making the resulting contract award an artifact of information asymmetry rather than a fair market outcome, a harm the NSPE Code's prohibitions on deceptive acts and untruthful representations are broad enough to reach.

URI case-85#C9
conclusion uri case-85#C9
conclusion text The Board's conclusion that Engineer A acted unethically does not fully reckon with the compounding ethical injury his submission inflicted on the competitive bidding process itself. When Engineer A s...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board found that the ethical injury to the competitive bidding process was independent of and additive to the injuries identified in the tripartite relationship, and that no party's individual eth...
resolution narrative The board concluded that Engineer A's submission of incomplete drawings inflicted an independent ethical injury on the competitive bidding process itself — beyond the harms to his direct client, the f...
confidence 0.81
ResolutionPattern_10 individual committed

The board concluded that Engineer A's rationalization that federal funds would absorb cost overruns was not merely an insufficient mitigating defense but an independent ethical violation, because by invoking the federal funding source as justification for non-disclosure he implicitly misrepresented to the federal agency the adequacy of the documents it was approving and funding, and the NSPE Code's prohibitions on deceptive acts and non-conforming seals are not satisfied by any private belief - however sincere - that downstream funding mechanisms will neutralize the harm caused by professionally deficient submissions.

URI case-85#C10
conclusion uri case-85#C10
conclusion text Engineer A's rationalization that federal funds — rather than local funds — would absorb any cost overruns from the incomplete design does not merely fail as a mitigating defense; it constitutes an in...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board found that Engineer A's benevolent motive defense — that federal funds would cover the consequences — not only failed to mitigate the original incompleteness violation but constituted an ind...
resolution narrative The board concluded that Engineer A's rationalization that federal funds would absorb cost overruns was not merely an insufficient mitigating defense but an independent ethical violation, because by i...
confidence 0.84
ResolutionPattern_11 individual committed

The board concluded Engineer B acted unethically because his approval did not reflect genuine professional engagement with the documents - it instead laundered Engineer A's deficiencies by attaching federal epistemic authority to an inadequately reviewed submission, and the NSPE Code's responsible charge standard required him to escalate, return the documents with a deficiency notice, or decline approval rather than ratify by default.

URI case-85#C11
conclusion uri case-85#C11
conclusion text The Board's conclusion that Engineer B acted unethically in approving incomplete drawings raises a nuance the Board did not fully develop: Engineer B's approval did not merely fail to catch Engineer A...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board resolved any tension between institutional efficiency (approving submissions within a delegated review process) and professional integrity by holding that the obligation to exercise genuine ...
resolution narrative The board concluded Engineer B acted unethically because his approval did not reflect genuine professional engagement with the documents — it instead laundered Engineer A's deficiencies by attaching f...
confidence 0.87
ResolutionPattern_12 individual committed

The board extended its finding against Engineer B beyond personal ethical shortcoming to a broader professional responsibility for institutional gatekeeping integrity, concluding that an engineer who knows the agency's review process is inadequate to catch the type of deficiencies present has an obligation to flag that systemic gap rather than perform a perfunctory review within a broken system.

URI case-85#C12
conclusion uri case-85#C12
conclusion text The Board's finding against Engineer B also implicates a systemic institutional ethics question that the Board's individual-focused analysis did not address. Engineer B's failure may reflect not only ...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board implicitly weighed individual culpability against systemic responsibility and resolved that the NSPE Code's individual-focused obligations do not excuse an engineer from the broader duty to ...
resolution narrative The board extended its finding against Engineer B beyond personal ethical shortcoming to a broader professional responsibility for institutional gatekeeping integrity, concluding that an engineer who ...
confidence 0.82
ResolutionPattern_13 individual committed

The board concluded Engineer C acted unethically because the temporal sequence of his conduct - bidding without disclosure and raising unbuildability only after contract award - suggests strategic withholding of professionally discoverable deficiencies, and his dual role as engineer and contractor made him the market participant best positioned to flag those deficiencies before bid submission, imposing an intensified disclosure obligation he failed to honor.

URI case-85#C13
conclusion uri case-85#C13
conclusion text The Board's conclusion that Engineer C acted unethically in submitting a bid on a project he later characterized as unbuildable requires a more granular temporal analysis than the Board provided. The ...
answers questions 5 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board resolved the tension between competitive bidding self-interest and professional disclosure obligation by holding that Engineer C's superior professional competence, rather than being a priva...
resolution narrative The board concluded Engineer C acted unethically because the temporal sequence of his conduct — bidding without disclosure and raising unbuildability only after contract award — suggests strategic wit...
confidence 0.88
ResolutionPattern_14 individual committed

The board's three conclusions together reveal a cascading ethical failure in which each actor's violation enabled and amplified the next, and the board implicitly theorized that the NSPE Code's individual obligations function as a redundant checkpoint system - meaning Engineer B's proper rejection or Engineer C's pre-bid disclosure would each independently have broken the cascade, and the failure of both compounded the public harm beyond what any single violation would have caused.

URI case-85#C14
conclusion uri case-85#C14
conclusion text The Board's three conclusions, taken together, reveal a cascading ethical failure in which each actor's violation enabled and amplified the next actor's violation — a dynamic the Board did not explici...
answers questions 15 items
determinative principles 3 items
determinative facts 3 items
cited provisions 5 items
weighing process The board resolved the question of individual versus collective responsibility by holding that while each actor bore independent individual obligations, those obligations are structurally interdepende...
resolution narrative The board's three conclusions together reveal a cascading ethical failure in which each actor's violation enabled and amplified the next, and the board implicitly theorized that the NSPE Code's indivi...
confidence 0.85
ResolutionPattern_15 individual committed

The board concluded that Engineer A bore a heightened affirmative disclosure obligation - beyond merely refraining from active lies - because the local public agency's lack of technical capacity made it wholly dependent on his professional judgment, meaning his knowing silence about the incompleteness of the drawings constituted functional deception and violated the structural ethical requirement that engineers actively communicate known deficiencies when clients have no independent means of discovering them.

URI case-85#C15
conclusion uri case-85#C15
conclusion text The local public agency's acknowledged lack of in-house technical capacity to evaluate drawings and specifications imposed a heightened affirmative disclosure obligation on Engineer A that went beyond...
answers questions 9 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board resolved the tension between the engineer's schedule-driven interest in submitting documents and the client's interest in accurate professional representation by holding that the client's te...
resolution narrative The board concluded that Engineer A bore a heightened affirmative disclosure obligation — beyond merely refraining from active lies — because the local public agency's lack of technical capacity made ...
confidence 0.9
ResolutionPattern_16 individual committed

The board concluded that written notification was necessary but not sufficient: it would have cured the deception violation by restoring informed decision-making to the client, but it could not cure the separate violation of sealing incomplete documents, because that duty is categorical and cannot be waived by client direction - Engineer A would have retained an obligation to refuse to seal or to explicitly qualify his seal regardless of what the agency instructed.

URI case-85#C16
conclusion uri case-85#C16
conclusion text A formal written notification to the local public agency disclosing the known incompleteness of the drawings before submission would have been a necessary but not automatically sufficient condition fo...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board disaggregated the deception obligation (resolved by written disclosure) from the sealing integrity obligation (not resolved by client consent), treating them as independent duties with indep...
resolution narrative The board concluded that written notification was necessary but not sufficient: it would have cured the deception violation by restoring informed decision-making to the client, but it could not cure t...
confidence 0.92
ResolutionPattern_17 individual committed

The board concluded that the ethical injury extended beyond the named parties to every contractor who submitted a good-faith bid on deficient documents, because competitive procurement's fairness depends on informational parity among bidders; Engineer A and Engineer B jointly destroyed that parity, rendering the entire procurement unreliable as a price-discovery mechanism and inflicting a harm on the public interest that is separate from any harm to individual contractors or agencies.

URI case-85#C17
conclusion uri case-85#C17
conclusion text The competitive bidding process itself sustained an independent ethical injury that the Board's conclusions, focused on individual actors, do not fully articulate. When incomplete drawings and specifi...
answers questions 1 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board did not weigh competing obligations here but instead identified a systemic harm — to the procurement process itself — that operates independently of and additively to the individual ethical ...
resolution narrative The board concluded that the ethical injury extended beyond the named parties to every contractor who submitted a good-faith bid on deficient documents, because competitive procurement's fairness depe...
confidence 0.89
ResolutionPattern_18 individual committed

The board concluded that Engineer A's schedule pressure, while a genuine professional difficulty, did not create any ethical permission to submit incomplete documents; instead it created an obligation to disclose the conflict honestly to his client, and his failure to do so meant he served his own convenience rather than his client's genuine interests - because a client's genuine interests include receiving accurate professional advice about whether deliverables are adequate, not merely receiving them on time.

URI case-85#C18
conclusion uri case-85#C18
conclusion text The tension between Engineer A's faithful agent obligation to deliver on the contracted schedule and his paramount obligation to protect public welfare is real but ultimately not a genuine conflict th...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board resolved the apparent conflict by denying that it was a genuine conflict at all — public welfare is not a competing consideration to be balanced against schedule compliance but a lexically p...
resolution narrative The board concluded that Engineer A's schedule pressure, while a genuine professional difficulty, did not create any ethical permission to submit incomplete documents; instead it created an obligation...
confidence 0.93
ResolutionPattern_19 individual committed

The board concluded that Engineer B's approval was ethically worse than a mere independent violation because it effectively laundered Engineer A's deficient work product - by attaching the appearance of federal engineering review to documents that had not received competent independent verification, Engineer B made the deficiency less visible to downstream parties and may have suppressed the scrutiny that would otherwise have caught it, compounding rather than merely duplicating the original harm.

URI case-85#C19
conclusion uri case-85#C19
conclusion text Engineer B's approval of the incomplete drawings created a compounded ethical harm beyond his own individual violation: it generated a false impression of independent professional verification that th...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board did not balance competing obligations but instead analyzed the downstream effect of Engineer B's approval, concluding that it was not merely an independent parallel violation but a multiplic...
resolution narrative The board concluded that Engineer B's approval was ethically worse than a mere independent violation because it effectively laundered Engineer A's deficient work product — by attaching the appearance ...
confidence 0.91
ResolutionPattern_20 individual committed

The board concluded that Engineer A's belief that no harm would result was deontologically irrelevant because the moral permissibility of sealing documents is determined by whether the representation the seal makes is true, not by whether the engineer predicts the falsehood will cause harm; since Engineer A knew the representation was false when he made it, his benevolent motive about cost coverage could not transform the dishonest act into an honest one, and the Board's rejection of the benevolent motive defense follows directly from this categorical duty structure.

URI case-85#C20
conclusion uri case-85#C20
conclusion text From a deontological perspective, Engineer A's conduct cannot be justified by his belief that no harm would ultimately result. Deontological ethics evaluates the moral permissibility of an act by refe...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board resolved the tension between benevolent motive and honest representation by applying deontological reasoning that treats the duty of honest professional representation as categorical — the e...
resolution narrative The board concluded that Engineer A's belief that no harm would result was deontologically irrelevant because the moral permissibility of sealing documents is determined by whether the representation ...
confidence 0.95
ResolutionPattern_21 individual committed

The board resolved Q15 by demonstrating that Engineer A's consequentialist justification failed on its own terms: a valid consequentialist analysis must account for all foreseeable harms, and Engineer A's reasoning omitted procurement unfairness, delay risk, public fund waste, erosion of trust, and the contingency that federal funds might not cover overruns - thereby exposing the rationalization as motivated rather than principled.

URI case-85#C21
conclusion uri case-85#C21
conclusion text From a consequentialist perspective, Engineer A's rationalization was analytically deficient even on its own terms. A consequentialist justification for non-disclosure requires that the engineer have ...
answers questions 2 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board found no genuine competing obligation to weigh because Engineer A's consequentialist defense was analytically incomplete — it selectively counted benefits while ignoring the preponderance of...
resolution narrative The board resolved Q15 by demonstrating that Engineer A's consequentialist justification failed on its own terms: a valid consequentialist analysis must account for all foreseeable harms, and Engineer...
confidence 0.91
ResolutionPattern_22 individual committed

The board concluded that refusing to submit by the deadline and requesting a schedule extension was not merely permissible but ethically required, because the Code's prohibition on sealing non-conforming plans admits no schedule exception, and the argument that deadline refusal would jeopardize federal funding, while practically significant, does not alter the ethical analysis - professional standards cannot be compromised to preserve a client's funding timeline.

URI case-85#C22
conclusion uri case-85#C22
conclusion text If Engineer A had refused to submit the drawings by the contractual deadline and instead requested a schedule extension to complete the design properly, this course of action would have been not merel...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board resolved the apparent tension between schedule compliance and professional standards by holding that the Faithful Agent Notification Obligation and the Public Welfare Paramount principle con...
resolution narrative The board concluded that refusing to submit by the deadline and requesting a schedule extension was not merely permissible but ethically required, because the Code's prohibition on sealing non-conform...
confidence 0.93
ResolutionPattern_23 individual committed

The board resolved Q18 and Q2 by characterizing Engineer B's role as a critical systemic control point rather than a parallel individual violation, concluding that a competent independent reviewer who recognized incompleteness or his own competence limits was obligated to return the drawings with a formal deficiency notice, and that his failure to do so allowed Engineer A's initial violation to propagate through the entire procurement chain with consequences extending well beyond his own conduct.

URI case-85#C23
conclusion uri case-85#C23
conclusion text If Engineer B had recognized the limits of his competence or the incompleteness of the submitted documents and returned the drawings to Engineer A with a formal deficiency notice, the cascade of ethic...
answers questions 3 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The board found no legitimate competing obligation that could justify Engineer B's approval of documents he either could not competently evaluate or recognized as incomplete — the review function's sy...
resolution narrative The board resolved Q18 and Q2 by characterizing Engineer B's role as a critical systemic control point rather than a parallel individual violation, concluding that a competent independent reviewer who...
confidence 0.9
ResolutionPattern_24 individual committed

The board concluded that Engineer C's pre-bid formal notification to the public agency was ethically required - not merely permissible - because his dual role as licensed engineer and contractor imposed a categorical constructability disclosure duty that the Code does not suspend for competitive reasons, and because such disclosure would have triggered procurement re-evaluation and performed a public service by surfacing deficiencies that both upstream engineers had failed to correct or flag.

URI case-85#C24
conclusion uri case-85#C24
conclusion text If Engineer C had formally notified the local public agency of the constructability deficiencies and requested a clarification or addendum before submitting his bid, this action would have discharged ...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The board resolved the tension between Engineer C's competitive self-interest and his professional disclosure obligation decisively in favor of disclosure, holding that the Code's treatment of competi...
resolution narrative The board concluded that Engineer C's pre-bid formal notification to the public agency was ethically required — not merely permissible — because his dual role as licensed engineer and contractor impos...
confidence 0.88
ResolutionPattern_25 individual committed

The board concluded that Engineer A's deontological duty of honest professional representation was violated the moment he sealed incomplete drawings regardless of his benevolent motive, because the Faithful Agent role itself presupposes honest communication about the deliverable's state, meaning that concealment was never a permissible form of client service - and that the apparent conflict between faithful agency and public welfare dissolved once the board recognized that both principles demanded the same conduct: transparent written disclosure of incompleteness before or at the time of submission.

URI case-85#C25
conclusion uri case-85#C25
conclusion text The tension between the Faithful Agent Notification Obligation — which bound Engineer A to deliver drawings and specifications on the contractually agreed schedule — and the Public Welfare Paramount p...
answers questions 5 items
determinative principles 3 items
determinative facts 3 items
cited provisions 5 items
weighing process The board resolved the tension between the Faithful Agent Notification Obligation and the Public Welfare Paramount principle by finding it illusory — both principles required the same action (transpar...
resolution narrative The board concluded that Engineer A's deontological duty of honest professional representation was violated the moment he sealed incomplete drawings regardless of his benevolent motive, because the Fa...
confidence 0.94
ResolutionPattern_26 individual committed

The Board concluded that Engineer B's approval was not merely a separate violation but an amplification of Engineer A's original misconduct, because the professional sealing-and-approval system derives its public legitimacy from the assumption that each participant has exercised genuine independent judgment; when Engineer B ratified documents he had not honestly evaluated, he converted a single misrepresentation into a layered one that foreclosed every remaining institutional safeguard before procurement, making the ethical injury multiplicative rather than additive.

URI case-85#C26
conclusion uri case-85#C26
conclusion text The Responsible Charge Integrity principle — which demands that an engineer seal only complete and conforming documents — and the Competence Boundary Recognition and Escalation Obligation imposed on E...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 2 items
weighing process The Board rejected any reading that would treat Engineer B's obligation as diminished because Engineer A had already sealed the documents; instead it held that each engineer in a review chain bears a ...
resolution narrative The Board concluded that Engineer B's approval was not merely a separate violation but an amplification of Engineer A's original misconduct, because the professional sealing-and-approval system derive...
confidence 0.88
ResolutionPattern_27 individual committed

The Board concluded that Engineer A's genuine belief that federal funds would cover cost overruns was ethically irrelevant to the wrongfulness of sealing incomplete documents, because the Honesty in Professional Representations principle and the Fraud and Misrepresentation Prohibition operate at the moment of submission; permitting engineers to substitute private harm-mitigation predictions for affirmative disclosure would effectively license deception whenever the engineer believed the consequences would be benign, a result the Code categorically forecloses.

URI case-85#C27
conclusion uri case-85#C27
conclusion text The Benevolent Motive Non-Cure principle — applied by the Board to reject Engineer A's rationalization that federal funds would absorb any cost overruns — stands in direct tension with a consequential...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The Board resolved the tension between a consequentialist reading — under which Engineer A's benevolent prediction might mitigate culpability — and a deontological reading by holding that honesty obli...
resolution narrative The Board concluded that Engineer A's genuine belief that federal funds would cover cost overruns was ethically irrelevant to the wrongfulness of sealing incomplete documents, because the Honesty in P...
confidence 0.91
ResolutionPattern_28 individual committed

The Board concluded that Engineer C's dual role as licensed engineer and contractor triggered a heightened and mandatory pre-bid disclosure obligation that superseded the discretionary whistleblowing framework recognized in BER Case No. 82-5, because his bid submission was not a neutral act but an implicit professional representation that the project was buildable - submitting that bid while privately knowing otherwise violated the Honesty in Professional Representations principle regardless of whether immediate physical danger was present.

URI case-85#C28
conclusion uri case-85#C28
conclusion text The Engineer-Contractor Dual Role Constructability Disclosure Obligation imposed on Engineer C — requiring him to flag unbuildable conditions before bidding — and the Whistleblowing Personal Conscienc...
answers questions 4 items
determinative principles 3 items
determinative facts 3 items
cited provisions 3 items
weighing process The Board resolved the conflict between the discretionary whistleblowing framework and the mandatory disclosure obligation by distinguishing on the basis of role rather than harm severity: because Eng...
resolution narrative The Board concluded that Engineer C's dual role as licensed engineer and contractor triggered a heightened and mandatory pre-bid disclosure obligation that superseded the discretionary whistleblowing ...
confidence 0.87
ResolutionPattern_29 individual committed

The Board concluded that Engineer A's ethical violation was aggravated rather than ordinary because the local public agency's complete technical dependence on him eliminated every institutional safeguard that might otherwise have caught the deficiency before procurement, and that the Technically Unsupported Client Heightened Disclosure Obligation functions not as a separate principle but as a contextual intensifier of the baseline honesty obligations - meaning Engineer A's duty to disclose was at its maximum precisely because his client was at its most vulnerable.

URI case-85#C29
conclusion uri case-85#C29
conclusion text The Technically Unsupported Client Heightened Disclosure Obligation — which recognized that the local public agency lacked the in-house technical capacity to evaluate Engineer A's drawings and specifi...
answers questions 5 items
determinative principles 3 items
determinative facts 3 items
cited provisions 4 items
weighing process The Board resolved any tension between the engineer's schedule obligations and his disclosure duties by holding that the client's technical vulnerability does not relax but affirmatively intensifies t...
resolution narrative The Board concluded that Engineer A's ethical violation was aggravated rather than ordinary because the local public agency's complete technical dependence on him eliminated every institutional safegu...
confidence 0.85
Phase 3: Decision Points
12 12 committed
canonical decision point 12
Engineer A, having delivered signed and sealed dam design drawings and specifications he knew to be individual committed

Should Engineer A disclose to the local public agency that the signed and sealed drawings are materially incomplete before submitting them for federal review, or proceed with submission without disclosure on the grounds that schedule pressure and expected federal funding make disclosure unnecessary?

URI http://proethica.org/ontology/case-85#DP1
focus id DP1
focus number 1
description Engineer A, having delivered signed and sealed dam design drawings and specifications he knew to be materially incomplete, must decide whether to affirmatively disclose that incompleteness to the loca...
decision question Should Engineer A disclose to the local public agency that the signed and sealed drawings are materially incomplete before submitting them for federal review, or proceed with submission without disclo...
role uri case-85#Engineer_A_Dam_Design_Engineer
role label Engineer A Dam Design Engineer
obligation uri http://proethica.org/ontology/intermediate#IncompleteDeliverableDisclosuretoClientObligation
obligation label Incomplete Deliverable Disclosure to Client Obligation
constraint uri http://proethica.org/ontology/intermediate#TechnicallyUnsupportedClientHeightenedDisclosureObligation
constraint label Technically Unsupported Client Heightened Disclosure Obligation
involved action uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "II.2.b", "III.2.b"], "data_summary": "Engineer A was retained under a full-service engineering contract to deliver complete dam design drawings and...
aligned question uri case-85#Q1
aligned question text Was it ethical for Engineer A to submit final drawings and specifications for review and approval that he knew were incomplete?
addresses questions 6 items
board resolution The board concluded that it was not ethical for Engineer A to submit drawings and specifications he knew to be incomplete. His silence constituted functional deception aggravated by the agency's compl...
options 3 items
intensity score 0.85
qc alignment score 0.88
source unified
source candidate ids 4 items
synthesis method algorithmic+llm
llm refined description Engineer A, having delivered signed and sealed dam design drawings and specifications he knew to be materially incomplete, must decide whether to affirmatively disclose that incompleteness to the loca...
llm refined question Should Engineer A disclose to the local public agency that the signed and sealed drawings are materially incomplete before submitting them for federal review, or proceed with submission without disclo...
Engineer C, owner of Hi-Lo Construction and a licensed professional engineer, reviewed the dam proje individual committed

Should Engineer C disclose the constructability deficiencies and unbuildable elements he identified in the bidding documents to the local public agency before submitting his bid, or submit the low bid without disclosure and raise those concerns only after winning the contract?

URI http://proethica.org/ontology/case-85#DP2
focus id DP2
focus number 2
description Engineer C, owner of Hi-Lo Construction and a licensed professional engineer, reviewed the dam project bidding documents, formed a professional judgment that significant portions of the design were in...
decision question Should Engineer C disclose the constructability deficiencies and unbuildable elements he identified in the bidding documents to the local public agency before submitting his bid, or submit the low bid...
role uri case-85#Engineer_C_Dam_Contractor
role label Engineer C
obligation uri http://proethica.org/ontology/intermediate#Engineer-ContractorConstructabilityDeficiencyPre-BidDisclosureObligation
obligation label Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation
constraint uri http://proethica.org/ontology/intermediate#UnbuildableContractBidReflectionObligation
constraint label Unbuildable Contract Bid Reflection Obligation
involved action uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "II.3.a", "III.2.b"], "data_summary": "The dam project was advertised for competitive bids on drawings and specifications that Engineer A had submitted under seal...
aligned question uri case-85#Q3
aligned question text Was it ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes?
addresses questions 4 items
board resolution The board concluded that it was not ethical for Engineer C to submit a bid on a project he later characterized as unbuildable without disclosing that assessment before bidding. His dual role as licens...
options 3 items
intensity score 0.78
qc alignment score 0.82
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer C, owner of Hi-Lo Construction and a licensed professional engineer, reviewed the dam project bidding documents, formed a professional judgment that significant portions of the design were in...
llm refined question Should Engineer C disclose the constructability deficiencies and unbuildable elements he identified in the bidding documents to the local public agency before submitting his bid, or submit the low bid...
Engineer B, employed by the federal funding agency, was assigned to review, approve, sign, and seal individual committed

Should Engineer B conduct and rely on his own review of Engineer A's dam design documents before approving and sealing them, or recognize the limits of his domain competence or the documents' inadequacy and escalate to a qualified specialist or return the documents with a deficiency notice before approving?

URI http://proethica.org/ontology/case-85#DP3
focus id DP3
focus number 3
description Engineer B, employed by the federal funding agency, was assigned to review, approve, sign, and seal Engineer A's dam design drawings and specifications as a condition of grant funding. He approved the...
decision question Should Engineer B conduct and rely on his own review of Engineer A's dam design documents before approving and sealing them, or recognize the limits of his domain competence or the documents' inadequa...
role uri case-85#Engineer_B_Federal_Reviewer
role label Engineer B
obligation uri http://proethica.org/ontology/intermediate#FederalPlanApprovalEngineerSubstantiveCompetenceReviewObligation
obligation label Federal Plan Approval Engineer Substantive Competence Review Obligation
constraint uri http://proethica.org/ontology/intermediate#CompetenceLimitationRecognitionandSupervisorEscalationObligation
constraint label Competence Limitation Recognition and Supervisor Escalation Obligation
involved action uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "II.2.b", "II.3.a"], "data_summary": "Engineer B was assigned by the federal funding agency to review, approve, sign, and seal Engineer A\u0027s dam design...
aligned question uri case-85#Q2
aligned question text Was it ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding?
addresses questions 4 items
board resolution The board concluded that it was not ethical for Engineer B to approve a set of incomplete drawings on behalf of the federal government for competitive bidding. His approval constituted an implicit pro...
options 3 items
intensity score 0.75
qc alignment score 0.8
source unified
synthesis method algorithmic+llm
llm refined description Engineer B, employed by the federal funding agency, was assigned to review, approve, sign, and seal Engineer A's dam design drawings and specifications as a condition of grant funding. He approved the...
llm refined question Should Engineer B conduct and rely on his own review of Engineer A's dam design documents before approving and sealing them, or recognize the limits of his domain competence or the documents' inadequa...
Engineer A: Disclosure of Known Incompleteness Before Submitting Sealed Drawings for Federal Review individual committed

Should Engineer A formally disclose the known incompleteness of the drawings to the local public agency and federal authority before submitting them under seal, or proceed with submission on schedule and rely on federal funds to absorb any resulting cost overruns?

URI http://proethica.org/ontology/case-85#DP4
focus id DP4
focus number 4
description Engineer A: Disclosure of Known Incompleteness Before Submitting Sealed Drawings for Federal Review
decision question Should Engineer A formally disclose the known incompleteness of the drawings to the local public agency and federal authority before submitting them under seal, or proceed with submission on schedule ...
role uri http://proethica.org/ontology/case/85#Engineer
role label Engineer A
obligation uri http://proethica.org/ontology/case/85#Engineer_A_Incomplete_Deliverable_Disclosure_Dam_Design
obligation label Engineer A Incomplete Deliverable Disclosure Dam Design
constraint uri http://proethica.org/ontology/intermediate#SchedulePressureNon-ExcuseforIncompleteDeliverableDisclosure
constraint label Schedule Pressure Non-Excuse for Incomplete Deliverable Disclosure
involved action uris 5 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "II.3.a", "III.2.b"], "data_summary": "Engineer A holds a full-service contract for dam design with a local public agency that lacks any in-house technical...
aligned question uri case-85#Q1
aligned question text Was it ethical for Engineer A to submit final drawings and specifications for review and approval that he knew were incomplete?
addresses questions 8 items
board resolution The board concluded that Engineer A acted unethically on multiple compounding grounds: submitting incomplete drawings under seal was itself a misrepresentation; the federal funds rationalization aggra...
options 3 items
intensity score 0.85
qc alignment score 0.88
source unified
source candidate ids 4 items
synthesis method algorithmic+llm
llm refined description Engineer A: Disclosure of Known Incompleteness Before Submitting Sealed Drawings for Federal Review
llm refined question Should Engineer A formally disclose the known incompleteness of the drawings to the local public agency and federal authority before submitting them under seal, or proceed with submission on schedule ...
Engineer B: Substantive Review vs. Procedural Approval of Incomplete Federal Drawings individual committed

Should Engineer B conduct - or escalate for - a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government, or treat his role as a procedural funding-eligibility clearance and approve the documents as submitted?

URI http://proethica.org/ontology/case-85#DP5
focus id DP5
focus number 5
description Engineer B: Substantive Review vs. Procedural Approval of Incomplete Federal Drawings
decision question Should Engineer B conduct — or escalate for — a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government, or treat his role as a pro...
role uri http://proethica.org/ontology/case/85#Engineer
role label Engineer B
obligation uri http://proethica.org/ontology/case/85#Engineer_B_Federal_Plan_Approval_Substantive_Review_Dam_Design
obligation label Engineer B Federal Plan Approval Substantive Review Dam Design
constraint uri http://proethica.org/ontology/intermediate#CompetenceBoundaryRecognitionandEscalationObligation
constraint label Competence Boundary Recognition and Escalation Obligation
involved action uris 4 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "III.2.a", "III.2.c"], "data_summary": "Engineer B, acting on behalf of the federal government, receives signed and sealed drawings from Engineer A for a dam...
aligned question uri case-85#Q2
aligned question text Was it ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding?
addresses questions 4 items
board resolution The board concluded that Engineer B acted unethically because his approval of incomplete drawings constituted an implicit professional representation of adequacy that the documents did not merit. His ...
options 3 items
intensity score 0.78
qc alignment score 0.82
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer B: Substantive Review vs. Procedural Approval of Incomplete Federal Drawings
llm refined question Should Engineer B conduct — or escalate for — a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government, or treat his role as a pro...
Engineer C: Pre-Bid Disclosure of Constructability Deficiencies vs. Competitive Bid Submission individual committed

Should Engineer C formally disclose the constructability deficiencies he identified in the drawings to the local public agency before submitting his bid, or submit a competitive bid and raise the unbuildability concerns only after winning the contract?

URI http://proethica.org/ontology/case-85#DP6
focus id DP6
focus number 6
description Engineer C: Pre-Bid Disclosure of Constructability Deficiencies vs. Competitive Bid Submission
decision question Should Engineer C formally disclose the constructability deficiencies he identified in the drawings to the local public agency before submitting his bid, or submit a competitive bid and raise the unbu...
role uri http://proethica.org/ontology/case/85#Engineer
role label Engineer C
obligation uri http://proethica.org/ontology/case/85#Engineer_C_Constructability_Deficiency_Pre-Bid_Disclosure_Dam_Project
obligation label Engineer C Constructability Deficiency Pre-Bid Disclosure Dam Project
constraint uri http://proethica.org/ontology/intermediate#Engineer-ContractorDualRoleConstructabilityDisclosureObligation
constraint label Engineer-Contractor Dual Role Constructability Disclosure Obligation
involved action uris 5 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "II.3.a", "III.2.b"], "data_summary": "Engineer C, a licensed professional engineer who also owns Hi-Lo Construction, reviews the advertised bid documents for a...
aligned question uri case-85#Q3
aligned question text Was it ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes?
addresses questions 4 items
board resolution The board concluded that Engineer C acted unethically because his dual role as licensed engineer and contractor imposed a categorical mandatory pre-bid disclosure obligation that superseded the discre...
options 3 items
intensity score 0.8
qc alignment score 0.83
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer C: Pre-Bid Disclosure of Constructability Deficiencies vs. Competitive Bid Submission
llm refined question Should Engineer C formally disclose the constructability deficiencies he identified in the drawings to the local public agency before submitting his bid, or submit a competitive bid and raise the unbu...
Engineer A Dam Design Engineer: Disclosure and Sealing Obligation When Facing Schedule Pressure on I individual committed

Should Engineer A disclose the known incompleteness of the drawings to the client and federal agency before submission, or proceed to sign, seal, and submit the incomplete documents on schedule while relying on federal funds to absorb any resulting cost overruns?

URI http://proethica.org/ontology/case-85#DP7
focus id DP7
focus number 7
description Engineer A Dam Design Engineer: Disclosure and Sealing Obligation When Facing Schedule Pressure on Incomplete Dam Design Documents
decision question Should Engineer A disclose the known incompleteness of the drawings to the client and federal agency before submission, or proceed to sign, seal, and submit the incomplete documents on schedule while ...
role uri case-85#Engineer_A_Dam_Design_Engineer
role label Engineer A Dam Design Engineer
obligation uri http://proethica.org/ontology/intermediate#Full-ServiceContractCompleteDesignDeliveryObligation
obligation label Full-Service Contract Complete Design Delivery Obligation with Incomplete Deliverable Disclosure
constraint uri http://proethica.org/ontology/intermediate#SchedulePressureNon-ExcuseforIncompleteDeliverableDisclosure
constraint label Schedule Pressure Non-Excuse for Incomplete Deliverable Disclosure
involved action uris 5 items
provision uris 4 items
provision labels 4 items
toulmin {"backing_provisions": ["II.2.a", "II.2.b", "III.2.b", "III.3.a"], "data_summary": "Engineer A holds a full-service contract with a local public agency that lacks in-house technical capacity to...
aligned question uri case-85#Q1
aligned question text Was it ethical for Engineer A to submit final drawings and specifications for review and approval that he knew were incomplete?
addresses questions 10 items
board resolution The board concluded that Engineer A acted unethically on multiple compounding grounds: submitting incomplete drawings under seal constituted an implicit misrepresentation of completeness; the federal ...
options 3 items
intensity score 0.85
qc alignment score 0.88
source unified
source candidate ids 3 items
synthesis method algorithmic+llm
llm refined description Engineer A Dam Design Engineer: Disclosure and Sealing Obligation When Facing Schedule Pressure on Incomplete Dam Design Documents
llm refined question Should Engineer A disclose the known incompleteness of the drawings to the client and federal agency before submission, or proceed to sign, seal, and submit the incomplete documents on schedule while ...
Engineer C Engineer-Contractor Dual Role: Pre-Bid Constructability Disclosure Obligation When Biddin individual committed

Should Engineer C formally disclose the constructability deficiencies to the public agency before submitting his bid, or submit a competitive low bid on the deficient documents and raise the unbuildability claim only after winning the contract?

URI http://proethica.org/ontology/case-85#DP8
focus id DP8
focus number 8
description Engineer C Engineer-Contractor Dual Role: Pre-Bid Constructability Disclosure Obligation When Bidding on Documents Identified as Unbuildable
decision question Should Engineer C formally disclose the constructability deficiencies to the public agency before submitting his bid, or submit a competitive low bid on the deficient documents and raise the unbuildab...
role uri case-85#Engineer
role label Engineer
obligation uri http://proethica.org/ontology/case/85#Engineer_C_Constructability_Deficiency_Pre-Bid_Disclosure_Dam_Project
obligation label Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation
constraint uri http://proethica.org/ontology/intermediate#UnbuildableContractBidDeficiencyReflectionObligation
constraint label Unbuildable Contract Bid Deficiency Reflection Obligation
involved action uris 5 items
provision uris 4 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "II.3.a", "III.2.b"], "data_summary": "Engineer C, a licensed professional engineer who owns Hi-Lo Construction, reviews the advertised bid documents for a dam...
aligned question uri case-85#Q3
aligned question text Was it ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes?
addresses questions 5 items
board resolution The board concluded that Engineer C acted unethically because his professional engineering license imposed a categorical duty to disclose known constructability deficiencies before submitting his bid....
options 3 items
intensity score 0.78
qc alignment score 0.82
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer C Engineer-Contractor Dual Role: Pre-Bid Constructability Disclosure Obligation When Bidding on Documents Identified as Unbuildable
llm refined question Should Engineer C formally disclose the constructability deficiencies to the public agency before submitting his bid, or submit a competitive low bid on the deficient documents and raise the unbuildab...
Engineer B Federal Plan Approval Engineer: Substantive Review Obligation Versus Procedural Approval individual committed

Should Engineer B conduct a substantive independent technical review of the submitted drawings - escalating to a domain specialist or returning deficient documents to Engineer A if competence limits are reached - or approve the documents as submitted based on the procedural funding-eligibility scope of his federal review role?

URI http://proethica.org/ontology/case-85#DP9
focus id DP9
focus number 9
description Engineer B Federal Plan Approval Engineer: Substantive Review Obligation Versus Procedural Approval When Evaluating Incomplete Dam Design Documents for Federal Funding Clearance
decision question Should Engineer B conduct a substantive independent technical review of the submitted drawings — escalating to a domain specialist or returning deficient documents to Engineer A if competence limits a...
role uri case-85#Engineer
role label Engineer
obligation uri http://proethica.org/ontology/intermediate#FederalPlanApprovalEngineerSubstantiveCompetenceReviewObligation
obligation label Federal Plan Approval Engineer Substantive Competence Review Obligation
constraint uri http://proethica.org/ontology/intermediate#CompetenceBoundaryRecognitionandEscalationObligation
constraint label Competence Boundary Recognition and Escalation Obligation
involved action uris 4 items
provision uris 4 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "II.2.b", "III.2.a"], "data_summary": "Engineer B, acting on behalf of the federal government, receives signed and sealed drawings from Engineer A for review and...
aligned question uri case-85#Q2
aligned question text Was it ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding?
addresses questions 4 items
board resolution The board concluded that Engineer B acted unethically because his approval of incomplete drawings on behalf of the federal government constituted an implicit professional representation of adequacy th...
options 3 items
intensity score 0.75
qc alignment score 0.8
source unified
source candidate ids 3 items
synthesis method algorithmic+llm
llm refined description Engineer B Federal Plan Approval Engineer: Substantive Review Obligation Versus Procedural Approval When Evaluating Incomplete Dam Design Documents for Federal Funding Clearance
llm refined question Should Engineer B conduct a substantive independent technical review of the submitted drawings — escalating to a domain specialist or returning deficient documents to Engineer A if competence limits a...
Engineer A: Heightened Disclosure Obligation to Technically Unsupported Client on Incomplete Dam Des individual committed

Should Engineer A disclose the known incompleteness of the drawings to the local public agency before submitting them for federal review, or proceed with submission under the assumption that federal funds will absorb any resulting cost overruns?

URI http://proethica.org/ontology/case-85#DP10
focus id DP10
focus number 10
description Engineer A: Heightened Disclosure Obligation to Technically Unsupported Client on Incomplete Dam Design Documents
decision question Should Engineer A disclose the known incompleteness of the drawings to the local public agency before submitting them for federal review, or proceed with submission under the assumption that federal f...
role uri http://proethica.org/ontology/case/85#Engineer_A
role label Engineer A
obligation uri http://proethica.org/ontology/case/85#Engineer_A_Technically_Unsupported_Client_Heightened_Disclosure_Dam_Project
obligation label Engineer A Technically Unsupported Client Heightened Disclosure Dam Project
involved action uris 3 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "II.2.b", "III.2.b"], "data_summary": "Engineer A holds a full-service contract with a local public agency that lacks any in-house technical capacity to evaluate...
aligned question uri case-85#Q1
aligned question text Was it ethical for Engineer A to submit final drawings and specifications for review and approval that he knew were incomplete?
addresses questions 7 items
board resolution The board concluded that Engineer A acted unethically. His submission of signed and sealed incomplete drawings without prior disclosure to the technically dependent local public agency violated the he...
options 3 items
intensity score 0.85
qc alignment score 0.88
source unified
source candidate ids 1 items
synthesis method algorithmic+llm
llm refined description Engineer A: Heightened Disclosure Obligation to Technically Unsupported Client on Incomplete Dam Design Documents
llm refined question Should Engineer A disclose the known incompleteness of the drawings to the local public agency before submitting them for federal review, or proceed with submission under the assumption that federal f...
Engineer C: Mandatory Pre-Bid Constructability Disclosure vs. Discretionary Whistleblowing Right Whe individual committed

Should Engineer C disclose the constructability deficiencies to the local public agency before submitting his bid, or submit the bid and raise the unbuildability concerns only after winning the contract at the pre-construction conference?

URI http://proethica.org/ontology/case-85#DP11
focus id DP11
focus number 11
description Engineer C: Mandatory Pre-Bid Constructability Disclosure vs. Discretionary Whistleblowing Right When Dual Role Engineer-Contractor Identifies Unbuildable Conditions Involving Public Funds
decision question Should Engineer C disclose the constructability deficiencies to the local public agency before submitting his bid, or submit the bid and raise the unbuildability concerns only after winning the contra...
role uri http://proethica.org/ontology/case/85#Engineer_C
role label Engineer C
obligation uri http://proethica.org/ontology/case/85#Current_Case_Ethics_Code_Non-Narrow_Public-Funds_Scope_Recognition
obligation label Current Case Ethics Code Non-Narrow Public-Funds Scope Recognition
constraint uri http://proethica.org/ontology/intermediate#WhistleblowerNon-Public-SafetyPersonalConscienceRightAcknowledgmentObligation
constraint label Whistleblower Non-Public-Safety Personal Conscience Right Acknowledgment Obligation
involved action uris 4 items
provision uris 4 items
provision labels 4 items
toulmin {"backing_provisions": ["II.2.a", "II.3.a", "III.2.b", "III.4.a"], "data_summary": "Engineer C, a licensed professional engineer who also owns Hi-Lo Construction, reviews the advertised bid...
aligned question uri case-85#Q3
aligned question text Was it ethical for Engineer C, owner of the Hi-Lo Construction firm, to submit a bid on a construction contract that he later characterized as “unbuildable” without major changes?
addresses questions 5 items
board resolution The board concluded that Engineer C acted unethically. His dual status as licensed engineer and contractor imposed a categorical professional duty to disclose known constructability deficiencies befor...
options 3 items
intensity score 0.8
qc alignment score 0.85
source unified
source candidate ids 3 items
synthesis method algorithmic+llm
llm refined description Engineer C: Mandatory Pre-Bid Constructability Disclosure vs. Discretionary Whistleblowing Right When Dual Role Engineer-Contractor Identifies Unbuildable Conditions Involving Public Funds
llm refined question Should Engineer C disclose the constructability deficiencies to the local public agency before submitting his bid, or submit the bid and raise the unbuildability concerns only after winning the contra...
Engineer B: Substantive Competence Review vs. Procedural Approval of Incomplete Federal Dam Design D individual committed

Should Engineer B conduct a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government - escalating or returning deficient documents if his domain competence is insufficient - or approve the drawings as a procedural funding-eligibility determination without independent verification of engineering completeness?

URI http://proethica.org/ontology/case-85#DP12
focus id DP12
focus number 12
description Engineer B: Substantive Competence Review vs. Procedural Approval of Incomplete Federal Dam Design Documents
decision question Should Engineer B conduct a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government — escalating or returning deficient documents i...
role uri http://proethica.org/ontology/case/85#Engineer_B
role label Engineer B
obligation uri http://proethica.org/ontology/case/85#Engineer_B_Federal_Plan_Approval_Substantive_Review_Dam_Design
obligation label Engineer B Federal Plan Approval Substantive Review Dam Design
involved action uris 4 items
provision uris 3 items
provision labels 3 items
toulmin {"backing_provisions": ["II.2.a", "II.2.b", "III.2.a"], "data_summary": "Engineer B, acting on behalf of the federal government, receives signed and sealed dam design drawings and specifications...
aligned question uri case-85#Q2
aligned question text Was it ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding?
addresses questions 4 items
board resolution The board concluded that Engineer B acted unethically because his approval of incomplete drawings on behalf of the federal government constituted an implicit professional representation of adequacy th...
options 3 items
intensity score 0.78
qc alignment score 0.82
source unified
source candidate ids 2 items
synthesis method algorithmic+llm
llm refined description Engineer B: Substantive Competence Review vs. Procedural Approval of Incomplete Federal Dam Design Documents
llm refined question Should Engineer B conduct a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government — escalating or returning deficient documents i...
Phase 4: Narrative Elements
64
Characters 9
Engineer C Unbuildable Contract Bidding Engineer-Contractor stakeholder The low-bid contractor who, upon closer pre-construction rev...

Guided by: Public Welfare Paramount Invoked by Engineer A Dam Design Failure, Schedule Pressure Non-Excuse Invoked Against Engineer A, Engineer Pressure Resistance Obligation Violated by Engineer A

Engineer A Dam Design Engineer protagonist A design engineer who delivered knowingly incomplete dam dra...
Engineer B Federal Grant Agency Approval Engineer stakeholder A federal agency staff engineer who reviewed, stamped, and s...
Engineer C Hi-Lo Construction Contractor stakeholder Owner of Hi-Lo Construction (low-bid awardee) who at the pre...
Local Public Agency Dam Project Client stakeholder Small local public agency that issued the RFP, awarded the d...
Federal Funding Agency Infrastructure Grant Authority authority Federal agency providing partial grant funding for the dam p...
Engineer A Incomplete Deliverable Concealing Design Engineer protagonist Prepared, signed, and sealed incomplete design drawings and ...
Engineer B Competence-Unrecognizing Plan Approval Engineer stakeholder Approved Engineer A's incomplete design plans despite lackin...
BER Case 82-5 Defense Industry Whistleblower Engineer stakeholder Referenced precedent: an engineer employed by a large defens...
Timeline Events 30 -- synthesized from Step 3 temporal dynamics
case_begins state Initial Situation synthesized

The case originates in a procurement environment where the local agency lacks the technical expertise to independently evaluate engineering submissions, and critical design deficiencies go undetected until after the contract has already been awarded. This foundational context sets the stage for a series of professional and ethical failures that compound over time.

Respond to Dam RFP action Action Step 3

An engineering firm responds to a Request for Proposals issued by a local agency for the design of a dam project, entering a competitive procurement process with significant public safety implications. This decision initiates the firm's professional obligations to deliver complete, accurate, and buildable design documents.

Submit Incomplete Design Documents action Action Step 3

The engineering firm submits design documents that are materially incomplete, lacking the detail necessary for contractors to accurately price and construct the project. Rather than disclosing these gaps transparently, the firm allows the incomplete submission to move forward through the review process.

Rationalize Incompleteness via Federal Funds action Action Step 3

When confronted with or internally acknowledging the incomplete nature of the design documents, the firm justifies the deficiency by pointing to the involvement of federal funding, implying that additional design development would occur later in the process. This rationalization obscures the firm's professional responsibility to provide sufficient documentation regardless of funding source.

Approve Incomplete Design Documents action Action Step 3

The local agency, lacking the technical capacity to identify the deficiencies, approves the incomplete design documents and advances the project to the bidding phase. This approval represents a critical missed checkpoint that allows a fundamentally flawed set of documents to form the basis of a public construction contract.

Submit Low Bid on Inadequate Documents action Action Step 3

A contractor submits a low bid based on the incomplete and inadequate design documents, unable to fully anticipate the true scope and cost of construction due to the missing information. This low bid creates a contractual baseline that is misaligned with the actual complexity of the work, setting the stage for future disputes and cost overruns.

Raise Unbuildable Design at Pre-Construction action Action Step 3

At the pre-construction meeting, the contractor raises serious concerns that the design as documented cannot be built as specified, bringing the fundamental inadequacy of the plans into formal view for the first time. This disclosure, occurring after contract award, signals that the project is already in a compromised position before any physical work has begun.

Admit Incompleteness Without Prior Disclosure action Action Step 3

The engineering firm acknowledges that the design documents were intentionally or knowingly incomplete, but does so only after the contract has been awarded and construction is imminent rather than disclosing this proactively during the design or bidding phases. This belated admission highlights a serious breach of the engineer's duty of candor to the client, the public, and other project stakeholders.

Contract Award to Engineer A automatic Event Step 3

Contract Award to Engineer A

Federal Funding Commitment Established automatic Event Step 3

Federal Funding Commitment Established

Time Pressure Condition Emerges automatic Event Step 3

Time Pressure Condition Emerges

Incomplete Documents Enter Review automatic Event Step 3

Incomplete Documents Enter Review

Deficient Documents Approved automatic Event Step 3

Deficient Documents Approved

Project Advertised for Bids automatic Event Step 3

Project Advertised for Bids

Hi-Lo Wins Construction Contract automatic Event Step 3

Hi-Lo Wins Construction Contract

conflict_emerges_conflict_1 automatic Conflict Emerges synthesized

Tension between Incomplete Deliverable Disclosure to Client Obligation and Technically Unsupported Client Heightened Disclosure Obligation

conflict_emerges_conflict_2 automatic Conflict Emerges synthesized

Tension between Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation and Unbuildable Contract Bid Reflection Obligation

DP1 decision Decision: DP1 synthesized

Should Engineer A disclose to the local public agency that the signed and sealed drawings are materially incomplete before submitting them for federal review, or proceed with submission without disclosure on the grounds that schedule pressure and expected federal funding make disclosure unnecessary?

DP2 decision Decision: DP2 synthesized

Should Engineer C disclose the constructability deficiencies and unbuildable elements he identified in the bidding documents to the local public agency before submitting his bid, or submit the low bid without disclosure and raise those concerns only after winning the contract?

DP3 decision Decision: DP3 synthesized

Should Engineer B conduct and rely on his own review of Engineer A's dam design documents before approving and sealing them, or recognize the limits of his domain competence or the documents' inadequacy and escalate to a qualified specialist or return the documents with a deficiency notice before approving?

DP4 decision Decision: DP4 synthesized

Should Engineer A formally disclose the known incompleteness of the drawings to the local public agency and federal authority before submitting them under seal, or proceed with submission on schedule and rely on federal funds to absorb any resulting cost overruns?

DP5 decision Decision: DP5 synthesized

Should Engineer B conduct — or escalate for — a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government, or treat his role as a procedural funding-eligibility clearance and approve the documents as submitted?

DP6 decision Decision: DP6 synthesized

Should Engineer C formally disclose the constructability deficiencies he identified in the drawings to the local public agency before submitting his bid, or submit a competitive bid and raise the unbuildability concerns only after winning the contract?

DP7 decision Decision: DP7 synthesized

Should Engineer A disclose the known incompleteness of the drawings to the client and federal agency before submission, or proceed to sign, seal, and submit the incomplete documents on schedule while relying on federal funds to absorb any resulting cost overruns?

DP8 decision Decision: DP8 synthesized

Should Engineer C formally disclose the constructability deficiencies to the public agency before submitting his bid, or submit a competitive low bid on the deficient documents and raise the unbuildability claim only after winning the contract?

DP9 decision Decision: DP9 synthesized

Should Engineer B conduct a substantive independent technical review of the submitted drawings — escalating to a domain specialist or returning deficient documents to Engineer A if competence limits are reached — or approve the documents as submitted based on the procedural funding-eligibility scope of his federal review role?

DP10 decision Decision: DP10 synthesized

Should Engineer A disclose the known incompleteness of the drawings to the local public agency before submitting them for federal review, or proceed with submission under the assumption that federal funds will absorb any resulting cost overruns?

DP11 decision Decision: DP11 synthesized

Should Engineer C disclose the constructability deficiencies to the local public agency before submitting his bid, or submit the bid and raise the unbuildability concerns only after winning the contract at the pre-construction conference?

DP12 decision Decision: DP12 synthesized

Should Engineer B conduct a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government — escalating or returning deficient documents if his domain competence is insufficient — or approve the drawings as a procedural funding-eligibility determination without independent verification of engineering completeness?

board_resolution outcome Resolution synthesized

Beyond the Board's finding that Engineer A acted unethically in submitting incomplete drawings, his conduct was further aggravated by the specific vulnerability of his client. The local public agency

Ethical Tensions 13
Tension between Incomplete Deliverable Disclosure to Client Obligation and Technically Unsupported Client Heightened Disclosure Obligation obligation vs constraint
Incomplete Deliverable Disclosure to Client Obligation Technically Unsupported Client Heightened Disclosure Obligation
Tension between Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation and Unbuildable Contract Bid Reflection Obligation obligation vs constraint
Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation Unbuildable Contract Bid Reflection Obligation
Tension between Federal Plan Approval Engineer Substantive Competence Review Obligation and Competence Limitation Recognition and Supervisor Escalation Obligation obligation vs constraint
Federal Plan Approval Engineer Substantive Competence Review Obligation Competence Limitation Recognition and Supervisor Escalation Obligation
Tension between Engineer A Incomplete Deliverable Disclosure Dam Design and Schedule Pressure Non-Excuse for Incomplete Deliverable Disclosure obligation vs constraint
Engineer A Incomplete Deliverable Disclosure Dam Design Schedule Pressure Non-Excuse for Incomplete Deliverable Disclosure
Tension between Engineer B Federal Plan Approval Substantive Review Dam Design and Competence Boundary Recognition and Escalation Obligation obligation vs constraint
Engineer B Federal Plan Approval Substantive Review Dam Design Competence Boundary Recognition and Escalation Obligation
Tension between Engineer C Constructability Deficiency Pre-Bid Disclosure Dam Project and Engineer-Contractor Dual Role Constructability Disclosure Obligation obligation vs constraint
Engineer C Constructability Deficiency Pre-Bid Disclosure Dam Project Engineer-Contractor Dual Role Constructability Disclosure Obligation
Tension between Full-Service Contract Complete Design Delivery Obligation with Incomplete Deliverable Disclosure and Schedule Pressure Non-Excuse for Incomplete Deliverable Disclosure obligation vs constraint
Full-Service Contract Complete Design Delivery Obligation with Incomplete Deliverable Disclosure Schedule Pressure Non-Excuse for Incomplete Deliverable Disclosure
Tension between Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation and Unbuildable Contract Bid Deficiency Reflection Obligation obligation vs constraint
Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation Unbuildable Contract Bid Deficiency Reflection Obligation
Tension between Federal Plan Approval Engineer Substantive Competence Review Obligation and Competence Boundary Recognition and Escalation Obligation obligation vs constraint
Federal Plan Approval Engineer Substantive Competence Review Obligation Competence Boundary Recognition and Escalation Obligation
Tension between Current Case Ethics Code Non-Narrow Public-Funds Scope Recognition and Whistleblower Non-Public-Safety Personal Conscience Right Acknowledgment Obligation obligation vs constraint
Current Case Ethics Code Non-Narrow Public-Funds Scope Recognition Whistleblower Non-Public-Safety Personal Conscience Right Acknowledgment Obligation
Engineer A bears a professional and legal duty to certify sealed drawings as complete and accurate — a certification that carries public safety weight for a dam project. The schedule pressure constraint makes explicit that timeline urgency cannot justify sealing incomplete documents. This creates a genuine dilemma: the engineer faces real-world project pressure to deliver sealed drawings on time, yet sealing incomplete drawings constitutes a false professional certification. Yielding to schedule pressure directly violates the integrity of the seal, while refusing to seal delays the project and may trigger contractual or funding consequences. The tension is not merely procedural — a falsely sealed dam design exposes downstream populations to structural failure risk. obligation vs constraint
Sealed Document Completeness Certification Accuracy Obligation Engineer A Schedule Pressure Non-Excuse Sealed Drawings Dam Project
Because the Local Public Agency client lacks technical sophistication to independently evaluate the completeness or adequacy of dam design deliverables, Engineer A bears a heightened affirmative duty to proactively disclose deficiencies in plain terms. However, Engineer A appears to rationalize withholding or minimizing this disclosure on the grounds that anticipated federal funding will eventually cover remediation costs or that the federal review process will catch errors. The constraint explicitly forecloses this rationalization. The tension is genuine: the engineer must choose between the discomfort and project-jeopardizing consequences of full disclosure to a technically unsupported client versus relying on downstream federal oversight as a substitute — a substitution that the constraint categorically prohibits. The client's vulnerability amplifies the moral weight of non-disclosure. obligation vs constraint
Technically Unsupported Client Heightened Disclosure Obligation Engineer A Federal Funding Rationalization Non-Excuse Dam Project
Engineer B, acting as the federal grant agency approval engineer, is obligated to conduct a substantive, technically rigorous review of the dam design before granting federal approval — not a perfunctory administrative check. Simultaneously, the competence boundary constraint requires Engineer B to recognize when the complexity of the design (e.g., dam hydraulics, geotechnical considerations) exceeds their own expertise and to escalate accordingly rather than approve beyond their competence. These pull in opposite directions: fulfilling the substantive review obligation demands deep technical engagement, but if Engineer B lacks the requisite expertise, performing that review without escalation violates the competence boundary constraint. Approving an incomplete or flawed dam design under federal authority lends it a false legitimacy that may suppress further scrutiny. obligation vs constraint
Federal Plan Approval Engineer Substantive Competence Review Obligation Engineer B Federal Plan Approval Competence Boundary Dam Project
Decision Moments 12
Should Engineer A disclose to the local public agency that the signed and sealed drawings are materially incomplete before submitting them for federal review, or proceed with submission without disclosure on the grounds that schedule pressure and expected federal funding make disclosure unnecessary? Engineer A Dam Design Engineer
Competing obligations: Incomplete Deliverable Disclosure to Client Obligation, Technically Unsupported Client Heightened Disclosure Obligation
  • Disclose Incompleteness Before Submission board choice
  • Submit Under Seal Relying on Federal Funds
  • Submit With Qualified Seal Notation
Should Engineer C disclose the constructability deficiencies and unbuildable elements he identified in the bidding documents to the local public agency before submitting his bid, or submit the low bid without disclosure and raise those concerns only after winning the contract? Engineer C
Competing obligations: Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation, Unbuildable Contract Bid Reflection Obligation
  • Disclose Deficiencies Before Submitting Bid board choice
  • Submit Low Bid and Raise Issues Post-Award
  • Bid With Contingency Items for Deficiencies
Should Engineer B conduct and rely on his own review of Engineer A's dam design documents before approving and sealing them, or recognize the limits of his domain competence or the documents' inadequacy and escalate to a qualified specialist or return the documents with a deficiency notice before approving? Engineer B
Competing obligations: Federal Plan Approval Engineer Substantive Competence Review Obligation, Competence Limitation Recognition and Supervisor Escalation Obligation
  • Escalate or Return Documents With Deficiency Notice board choice
  • Approve Based on General Engineering Review
  • Approve With Conditional Deficiency Notation
Should Engineer A formally disclose the known incompleteness of the drawings to the local public agency and federal authority before submitting them under seal, or proceed with submission on schedule and rely on federal funds to absorb any resulting cost overruns? Engineer A
Competing obligations: Engineer A Incomplete Deliverable Disclosure Dam Design, Schedule Pressure Non-Excuse for Incomplete Deliverable Disclosure
  • Disclose Incompleteness and Withhold Seal board choice
  • Disclose in Writing but Proceed Under Seal
  • Submit on Schedule Relying on Federal Cost Absorption
Should Engineer B conduct — or escalate for — a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government, or treat his role as a procedural funding-eligibility clearance and approve the documents as submitted? Engineer B
Competing obligations: Engineer B Federal Plan Approval Substantive Review Dam Design, Competence Boundary Recognition and Escalation Obligation
  • Conduct Substantive Review or Escalate to Specialist board choice
  • Apply Standard Agency Plan-Review Protocols
  • Approve with Conditional Deficiency Notice
Should Engineer C formally disclose the constructability deficiencies he identified in the drawings to the local public agency before submitting his bid, or submit a competitive bid and raise the unbuildability concerns only after winning the contract? Engineer C
Competing obligations: Engineer C Constructability Deficiency Pre-Bid Disclosure Dam Project, Engineer-Contractor Dual Role Constructability Disclosure Obligation
  • Disclose Deficiencies Before Submitting Bid board choice
  • Submit Bid and Raise Concerns Post-Award
  • Decline to Bid on Unbuildable Documents
Should Engineer A disclose the known incompleteness of the drawings to the client and federal agency before submission, or proceed to sign, seal, and submit the incomplete documents on schedule while relying on federal funds to absorb any resulting cost overruns? Engineer A Dam Design Engineer
Competing obligations: Full-Service Contract Complete Design Delivery Obligation with Incomplete Deliverable Disclosure, Schedule Pressure Non-Excuse for Incomplete Deliverable Disclosure
  • Disclose Incompleteness and Withhold Seal board choice
  • Disclose in Writing Then Submit Under Seal
  • Submit Under Seal Relying on Federal Cost Absorption
Should Engineer C formally disclose the constructability deficiencies to the public agency before submitting his bid, or submit a competitive low bid on the deficient documents and raise the unbuildability claim only after winning the contract? Engineer
Competing obligations: Engineer-Contractor Constructability Deficiency Pre-Bid Disclosure Obligation, Unbuildable Contract Bid Deficiency Reflection Obligation
  • Disclose Deficiencies Before Submitting Bid board choice
  • Submit Bid With Qualifying Notation
  • Bid Without Disclosure and Raise Post-Award
Should Engineer B conduct a substantive independent technical review of the submitted drawings — escalating to a domain specialist or returning deficient documents to Engineer A if competence limits are reached — or approve the documents as submitted based on the procedural funding-eligibility scope of his federal review role? Engineer
Competing obligations: Federal Plan Approval Engineer Substantive Competence Review Obligation, Competence Boundary Recognition and Escalation Obligation
  • Conduct Substantive Review or Escalate to Specialist board choice
  • Apply Standard Procedural Funding Review
  • Approve With Conditional Deficiency Notice
Should Engineer A disclose the known incompleteness of the drawings to the local public agency before submitting them for federal review, or proceed with submission under the assumption that federal funds will absorb any resulting cost overruns? Engineer A
Competing obligations: Engineer A Technically Unsupported Client Heightened Disclosure Dam Project
  • Disclose Incompleteness in Writing Before Submission board choice
  • Submit Under Federal Funds Absorption Assumption
  • Submit With Qualified Seal Notation
Should Engineer C disclose the constructability deficiencies to the local public agency before submitting his bid, or submit the bid and raise the unbuildability concerns only after winning the contract at the pre-construction conference? Engineer C
Competing obligations: Current Case Ethics Code Non-Narrow Public-Funds Scope Recognition, Whistleblower Non-Public-Safety Personal Conscience Right Acknowledgment Obligation
  • Formally Notify Agency Before Submitting Bid board choice
  • Submit Bid and Disclose Post-Award
  • Decline to Bid and Notify Agency
Should Engineer B conduct a substantive independent technical review of the submitted drawings before approving them on behalf of the federal government — escalating or returning deficient documents if his domain competence is insufficient — or approve the drawings as a procedural funding-eligibility determination without independent verification of engineering completeness? Engineer B
Competing obligations: Engineer B Federal Plan Approval Substantive Review Dam Design
  • Conduct Substantive Review or Escalate to Specialist board choice
  • Approve as Procedural Funding Eligibility Check
  • Apply Standard Plan Review Without Domain Escalation