Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Pipeline Steps
Overview
1 Contextual Framework
2 Normative Requirements
3 Temporal Dynamics Reconcile
4 Whole-Case Synthesis
Extraction Review Full View
Provenance
Incomplete Plans and Specifications – Engineer, Government, and Contractor Responsibilities
Step 4 of 5
Entity Review

264

Entities

5

Provisions

1

Precedents

19

Questions

21

Conclusions

Phase Lag

Transformation
Phase Lag Delayed consequences reveal obligations not initially apparent
Engineer A sealed and submitted documents he knew were incomplete, but the deficiency lay dormant through federal approval, bid advertisement, and contract award before being 'subsequently revealed' at the pre-construction conference. The Board's analysis hinges on this temporal gap: had disclosure occurred at the moment of submission, the downstream cascade (wasted bids, contract on a false premise, redesign delays) would have been avoided. The latent, undisclosed defect propagated through multiple project phases before its consequences became apparent, generating retrospective ethical findings against each actor.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (5)
View Extraction
I.1. Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 34)
Obligation
Engineer A Safety Obligation Dam Design
This provision directly mandates holding public safety paramount, which is the core of Engineer A's obligation to ensure complete dam drawings.
Action
Incomplete Work Submission
Submitting incomplete work endangers public safety and welfare by allowing deficient plans to proceed.
State
Engineer A Incomplete Drawings Submitted
Submitting incomplete drawings for a dam project directly endangers public safety.
Obligation (4)
  • Engineer A Safety Obligation Dam Design
    This provision directly mandates holding public safety paramount, which is the core of Engineer A's obligation to ensure complete dam drawings.
  • Engineer A Complete Design Delivery
    Providing complete and buildable design documents is necessary to protect public safety as required by this provision.
  • Engineer A Competence Dam Drawings
    Producing technically adequate and buildable drawings is directly tied to protecting public safety and welfare.
  • Engineer B Approving Engineer Verification
    Thorough independent review of dam drawings is necessary to uphold public safety as required by this provision.
Action (2)
  • Incomplete Work Submission
    Submitting incomplete work endangers public safety and welfare by allowing deficient plans to proceed.
  • Incomplete Documents Approval
    Approving incomplete documents risks public safety by allowing unsafe or deficient construction to proceed.
State (6)
  • Engineer A Incomplete Drawings Submitted
    Submitting incomplete drawings for a dam project directly endangers public safety.
  • Engineer A Deficient Work Product
    A deficient work product for a dam creates direct risk to public health and safety.
  • Engineer A Public Safety Risk
    This entity explicitly describes the public safety risk arising from proceeding on incomplete design documents.
  • Engineer A Incomplete Deliverable
    Submitting an incomplete deliverable for dam construction places the public at risk of harm.
  • Engineer B Unreviewed Incomplete Approval
    Approving materially incomplete plans without review contributes to public safety risk on a dam project.
  • Engineer C Unbuildable Contract Bid
    Bidding on a project with known document deficiencies risks proceeding toward unsafe construction.
Constraint (5)
  • Engineer A Safety Dam Design
    I.1 requires holding public safety paramount, directly creating the obligation to ensure dam drawings were complete and safe before submission.
  • Engineer A Responsible Charge Seal Dam
    Sealing materially incomplete and unbuildable dam drawings endangers public safety, which I.1 prohibits.
  • Engineer A Complete Design Constraint
    I.1 underpins the requirement to provide complete design documents to protect public safety during construction.
  • Engineer B Approving Review Verification
    I.1 requires Engineer B to conduct a thorough review to protect public safety by catching dangerous deficiencies.
  • Engineer A Non-Safety Disclosure Limit
    I.1 is the provision being assessed when determining whether the incomplete plans rose to the level of a public safety danger requiring disclosure.
Principle (4)
  • Engineer A Public Welfare Deficient Dam Design
    Submitting incomplete and unbuildable dam drawings directly endangered the public who would rely on the dam, violating the paramount duty to protect public safety.
  • Engineer A Professional Competence Dam Drawings
    Producing materially incomplete and unbuildable dam drawings failed to protect the safety and welfare of the public depending on the structure.
  • Engineer B Federal Review Approval Competence
    Approving deficient drawings without identifying their inadequacy allowed a public safety risk to proceed unchecked.
  • Engineer B Competence Recognition Approval
    Failing to identify or act on the inadequacy of the submitted drawings permitted a potentially dangerous dam design to advance, undermining public welfare.
Role (3)
  • Engineer A Dam Design Engineer
    Engineer A produced incomplete plans for a dam project, directly threatening public safety by failing to hold it paramount.
  • Engineer B Federal Approving Engineer
    Engineer B approved deficient design documents, failing to protect public safety as required by this provision.
  • Engineer C Engineer Contractor
    Engineer C as a licensed engineer had an obligation to hold public safety paramount when proceeding with a project known to have incomplete design details.
Event (3)
  • Unbuildability Declaration
    Public safety is directly implicated when a project is declared unbuildable, requiring paramount concern for welfare.
  • Document Incompleteness Occurrence
    Incomplete documents risk public safety by enabling construction based on deficient plans.
  • Bid Advertisement
    Advertising incomplete plans for bid endangers public welfare by initiating a flawed construction process.
Capability (7)
  • Engineer A Complete Design Delivery
    Delivering complete and buildable plans is necessary to protect public safety on a dam project.
  • Engineer A Responsible Charge Verification
    Verifying documents before sealing is required to ensure public safety is not compromised by incomplete designs.
  • Engineer B Responsible Charge Verification
    Engineer B's review obligation exists to catch unsafe or unbuildable designs before construction proceeds.
  • Engineer A Buildability Assessment
    Recognizing that drawings are incomplete and unbuildable directly relates to preventing harm to the public.
  • Engineer B Buildability Assessment
    Identifying unbuildable or incomplete dam specifications is necessary to uphold public safety.
  • Engineer C Buildability Assessment
    Engineer C's identification of lacking design detail reflects the obligation to protect public welfare on a dam project.
  • Engineer A Deadline Pressure Resistance
    Submitting incomplete drawings under deadline pressure endangers public safety by allowing construction to proceed on deficient plans.
II.3.a. 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.
How this applies in the case (showing 3 of 30)
Obligation
Engineer A Deliverable Completeness Disclosure
This provision requires truthful and complete disclosure in professional statements, directly matching the obligation to disclose document deficiencies to all parties.
Action
Non-Disclosure of Incompleteness
Failing to disclose incompleteness violates the requirement to be truthful and include all relevant information in professional reports and statements.
State
Engineer A Undisclosed Deadline Pressure
Failing to disclose that deadline pressure caused incompleteness is a failure to include all relevant information in professional submissions.
Obligation (3)
  • Engineer A Deliverable Completeness Disclosure
    This provision requires truthful and complete disclosure in professional statements, directly matching the obligation to disclose document deficiencies to all parties.
  • Engineer A Public Funds Misrepresentation
    This provision prohibits misrepresenting incomplete documents as acceptable, which is exactly what Engineer A was obligated to avoid.
  • Engineer A Cost Allocation Neutrality
    This provision requires objectivity in professional reports and statements, aligning with the obligation to make decisions without bias toward funding assumptions.
Action (2)
  • Non-Disclosure of Incompleteness
    Failing to disclose incompleteness violates the requirement to be truthful and include all relevant information in professional reports and statements.
  • Reactive Incompleteness Acknowledgment
    Acknowledging incompleteness only when prompted rather than proactively fails the standard of objective and truthful disclosure of all pertinent information.
State (5)
  • Engineer A Undisclosed Deadline Pressure
    Failing to disclose that deadline pressure caused incompleteness is a failure to include all relevant information in professional submissions.
  • Engineer A Federal Funding Assumption
    Not disclosing the assumption that federal funds would cover overruns omits pertinent information from professional reports.
  • Engineer A Deadline Pressure Undisclosed
    Withholding the reason for incompleteness from the client violates the duty to be truthful and include all relevant information.
  • Engineer A Federal Funds Assumption
    Relying on undisclosed federal funding assumptions without informing the client omits pertinent information from professional communications.
  • Engineer B Unreviewed Incomplete Approval
    Approving plans without adequate review and without disclosing that fact lacks the objectivity and truthfulness required in professional statements.
Constraint (5)
  • Engineer A Incomplete Deliverable Disclosure
    II.3.a requires truthful and complete professional submissions, prohibiting submission of incomplete drawings without disclosure.
  • Engineer A Incomplete Submission Disclosure
    II.3.a directly requires including all relevant information in professional reports, creating the obligation to disclose that drawings were incomplete.
  • Engineer A Federal Funds Misrepresentation
    II.3.a prohibits misrepresenting incomplete drawings as complete to the agency and federal authority, requiring truthful statements.
  • Engineer A Federal Funds Rationalization
    II.3.a requires objective and truthful reporting, prohibiting undisclosed assumptions from being used to justify incomplete submissions.
  • Engineer A Cost Assumption Rationalization
    II.3.a requires that all relevant information be disclosed, prohibiting rationalization based on undisclosed cost assumptions.
Principle (6)
  • Engineer A Deliverable Completeness Concealment
    Submitting sealed documents while knowing they were incomplete violated the duty to be truthful and include all relevant information in professional submissions.
  • Engineer A Honesty Concealment of Deficiency
    Concealing known incompleteness from the client, federal engineer, and contractor directly violated the requirement for objectivity and full disclosure in professional reports.
  • Engineer A Transparency Deficient Submission
    Failing to disclose the deficiencies of the submitted drawings contradicts the obligation to include all pertinent information in professional documents.
  • Engineer A Deliverable Completeness Disclosure
    Asserting time pressure as justification without fully disclosing the extent of incompleteness fell short of the truthfulness required in professional statements.
  • Engineer A Public Funds Misrepresentation
    Misrepresenting that federal funds would remedy the deficiency constituted a failure to be truthful and objective in professional communications.
  • Engineer C Bid Transparency Obligation
    Submitting a bid without including items to address known deficiencies raised concerns about full transparency in professional reporting and communication.
Role (2)
  • Engineer A Dam Design Engineer
    Engineer A concealed the incompleteness of the drawings and specifications, violating the duty to be truthful and include all relevant information in professional documents.
  • Engineer B Federal Approving Engineer
    Engineer B approved and represented the documents as adequate without disclosing their deficiencies, failing the duty of objectivity and truthfulness.
Event (3)
  • Incompleteness Acknowledgment Event
    Acknowledging incompleteness requires truthful and objective reporting of all relevant deficiencies.
  • Pre-Construction Conference
    Engineers must provide truthful and complete information about plan deficiencies during pre-construction discussions.
  • Federal Review Completion
    Reports or statements made during federal review must include all pertinent information about document status.
Capability (4)
  • Engineer A Incomplete Deliverable Disclosure
    Disclosing the material incompleteness of drawings and specifications is required to be truthful and include all relevant information in professional submissions.
  • Engineer A Public Funds Misrepresentation Avoidance
    Asserting incomplete work is acceptable because federal funds will cover it is a failure to be objective and truthful in professional statements.
  • Engineer A Responsible Charge Verification
    Sealing and submitting documents without verifying their completeness undermines the truthfulness and accuracy required in professional reports.
  • Engineer B Approving Engineer Verification
    Engineer B's independent review must be thorough enough to support truthful and accurate professional statements about the submitted documents.
II.5. Engineers shall avoid deceptive acts.
How this applies in the case (showing 3 of 31)
Obligation
Engineer A Public Funds Misrepresentation
Representing incomplete documents as acceptable to the client and federal agency constitutes a deceptive act that this provision prohibits.
Action
Non-Disclosure of Incompleteness
Concealing the incomplete nature of plans and specifications constitutes a deceptive act.
State
Engineer A Undisclosed Deadline Pressure
Concealing that deadline pressure caused the incomplete submission constitutes a deceptive act toward the client.
Obligation (3)
  • Engineer A Public Funds Misrepresentation
    Representing incomplete documents as acceptable to the client and federal agency constitutes a deceptive act that this provision prohibits.
  • Engineer A Deliverable Completeness Disclosure
    Failing to disclose known deficiencies in design documents to relevant parties would constitute a deceptive act under this provision.
  • Engineer A Cost Allocation Neutrality
    Allowing funding assumptions to bias the completeness of submitted documents would constitute a deceptive act toward the client and agency.
Action (2)
  • Non-Disclosure of Incompleteness
    Concealing the incomplete nature of plans and specifications constitutes a deceptive act.
  • Incomplete Documents Approval
    Approving documents known to be incomplete without disclosure is a deceptive act toward clients and the public.
State (5)
  • Engineer A Undisclosed Deadline Pressure
    Concealing that deadline pressure caused the incomplete submission constitutes a deceptive act toward the client.
  • Engineer A Federal Funding Assumption
    Hiding the assumption that federal funds would cover overruns is a deceptive act that misrepresents the project situation.
  • Engineer A Deadline Pressure Undisclosed
    Failing to disclose time pressure as the cause of incompleteness deceives the client about the nature of the deliverable.
  • Engineer A Federal Funds Assumption
    Undisclosed reliance on anticipated federal funding to justify incomplete work is a deceptive act.
  • Engineer B Unreviewed Incomplete Approval
    Approving plans without actual review while implying they have been reviewed constitutes a deceptive act.
Constraint (5)
  • Engineer A Non-Deception Submission
    II.5 directly prohibits deceptive acts, which is the basis for constraining Engineer A from misrepresenting incomplete drawings.
  • Engineer A Federal Funds Misrepresentation
    II.5 prohibits deceptive acts, directly applying to Engineer A misrepresenting incomplete documents to the agency and federal authority.
  • Engineer A Incomplete Deliverable Disclosure
    II.5 prohibits deception, requiring disclosure of known incompleteness rather than submitting drawings without warning.
  • Engineer A Federal Funds Rationalization
    II.5 prohibits deceptive acts, which includes using an undisclosed assumption to justify submitting incomplete work.
  • Engineer A Cost Assumption Rationalization
    II.5 prohibits deceptive acts, directly applying to rationalizing incomplete submissions through undisclosed cost assumptions.
Principle (7)
  • Engineer A Deliverable Completeness Concealment
    Knowingly submitting incomplete drawings under seal without disclosure constitutes a deceptive act toward the client and reviewing parties.
  • Engineer A Honesty Concealment of Deficiency
    Actively concealing known deficiencies from multiple parties is a direct deceptive act prohibited by this provision.
  • Engineer A Professional Integrity Deceptive Acts
    Attributing incompleteness to time pressures while knowing the documents were unbuildable is explicitly deceptive conduct.
  • Engineer A Cost Allocation Rationalization
    Using the availability of federal funds as a rationalization for submitting deficient work is a form of deception toward the client and public.
  • Engineer A Cost Allocation Bias
    Treating federal funds as a remedy for self-created deficiencies without disclosure represents deceptive conduct in professional practice.
  • Engineer A Public Funds Misrepresentation
    Misrepresenting the acceptability of incomplete work by invoking anticipated federal funds is a deceptive act.
  • Engineer A Transparency Deficient Submission
    Submitting deficient documents without disclosing their inadequacy is inherently deceptive to all relying parties.
Role (2)
  • Engineer A Dam Design Engineer
    Engineer A actively concealed the incompleteness of the plans and specifications, constituting a deceptive act.
  • Engineer B Federal Approving Engineer
    Engineer B approved deficient documents without disclosure, enabling a deceptive representation that the designs met required standards.
Event (3)
  • Bid Advertisement
    Advertising incomplete plans without disclosure constitutes a deceptive act toward bidding contractors.
  • Document Incompleteness Occurrence
    Allowing incomplete documents to proceed without disclosure is a deceptive act.
  • Federal Review Completion
    Presenting documents as complete during federal review when they are not would be a deceptive act.
Capability (4)
  • Engineer A Incomplete Deliverable Disclosure
    Failing to disclose known incompleteness of submitted documents constitutes a deceptive act toward the client and reviewing authorities.
  • Engineer A Public Funds Misrepresentation Avoidance
    Representing incomplete work as acceptable by relying on anticipated federal funding is a deceptive act.
  • Engineer A Cost Assumption Neutrality
    Allowing assumptions about federal cost coverage to justify submitting incomplete deliverables involves a form of deception about the adequacy of the work.
  • Engineer A Responsible Charge Verification
    Sealing documents without proper verification creates a false impression of completeness and conformity, constituting a deceptive act.
III.1.b. Engineers shall advise their clients or employers when they believe a project will not be successful.
How this applies in the case (showing 3 of 30)
Obligation
Engineer A Deadline Pressure Resistance
This provision requires engineers to advise clients when project conditions such as unrealistic deadlines will prevent successful completion.
Action
Incomplete Work Submission
Engineers should advise clients when incomplete work submissions indicate the project will not be successful.
State
Engineer A Incomplete Drawings Submitted
Engineer A had a duty to advise the client that the project could not succeed with incomplete drawings before submitting them.
Obligation (4)
  • Engineer A Deadline Pressure Resistance
    This provision requires engineers to advise clients when project conditions such as unrealistic deadlines will prevent successful completion.
  • Engineer A Deliverable Completeness Disclosure
    This provision requires Engineer A to inform the client that incomplete documents would prevent the project from being successfully built.
  • Engineer B Competence Limit Escalation
    This provision requires Engineer B to advise a supervisor when unable to competently review the submitted documents, signaling project risk.
  • Engineer C Bid Adequacy Reflection
    This provision supports Engineer C's obligation to communicate identified deficiencies that would prevent the project from being successfully executed.
Action (2)
  • Incomplete Work Submission
    Engineers should advise clients when incomplete work submissions indicate the project will not be successful.
  • Non-Disclosure of Incompleteness
    Failing to advise the client of incompleteness violates the duty to warn when a project is unlikely to succeed.
State (6)
  • Engineer A Incomplete Drawings Submitted
    Engineer A had a duty to advise the client that the project could not succeed with incomplete drawings before submitting them.
  • Engineer A Undisclosed Deadline Pressure
    Engineer A should have advised the client that deadline pressure was causing a deliverable that would not support successful project completion.
  • Engineer A Federal Funding Assumption
    Engineer A should have advised the client of the funding assumption rather than proceeding silently with an incomplete design.
  • Engineer A Incomplete Deliverable
    Engineer A was obligated to advise the client that the incomplete deliverable would prevent the project from being successfully built.
  • Local Agency Technical Review Capacity
    Knowing the agency lacked review capacity, Engineer A had greater obligation to advise them that the submission was not ready for construction.
  • Engineer B Unreviewed Incomplete Approval
    Engineer B should have advised the relevant parties that the incomplete plans would not lead to a successful project rather than approving them.
Constraint (5)
  • Engineer A Deadline Pressure Disclosure
    III.1.b requires advising clients when a project will not be successful, directly creating the obligation to communicate that the deadline was incompatible with complete deliverables.
  • Engineer A Deadline Pressure Submission
    III.1.b requires informing the client that the delivery date was incompatible with producing complete and buildable drawings.
  • Engineer A Incomplete Deliverable Disclosure
    III.1.b requires advising the client of project problems, which includes disclosing that the drawings were materially incomplete.
  • Engineer B Competence Escalation
    III.1.b supports the obligation for Engineer B to advise a supervisor when unable to perform a competent review, as the project review would not be successful.
  • Defense Engineer Whistleblower Conscience
    III.1.b is relevant to the extent of the obligation to advise employers of project problems, informing the limit of the whistleblower duty after reports are rejected.
Principle (4)
  • Engineer A Faithful Agent Duty Limits
    Engineer A owed a duty to advise the client of the project's deficiencies rather than concealing them under a misapplied notion of loyalty.
  • Engineer A Deliverable Completeness Disclosure
    Engineer A should have advised the client that the project could not succeed as submitted rather than proceeding with incomplete documents.
  • Engineer A Public Welfare Deficient Dam Design
    Engineer A was obligated to inform the client that the incomplete design created risks that would prevent the project from being successfully completed.
  • Engineer B Competence Recognition Approval
    Engineer B, upon reviewing the documents, had a duty to advise the funding agency that the project as submitted was unlikely to succeed.
Role (2)
  • Engineer A Dam Design Engineer
    Engineer A was obligated to advise the client that the incomplete plans and specifications would likely cause the project to be unsuccessful.
  • Engineer C Engineer Contractor
    Engineer C as a licensed engineer was obligated to formally advise the client or employer that the project could not succeed given the lack of design detail identified at the pre-construction conference.
Event (3)
  • Unbuildability Declaration
    Engineers must advise clients when a project is declared unbuildable, signaling it will not be successful.
  • Incompleteness Acknowledgment Event
    Engineers are obligated to advise clients of plan incompleteness that would prevent project success.
  • Design Contract Award
    Upon contract award, engineers should advise clients of any foreseeable issues that would prevent project success.
Capability (4)
  • Engineer A Deadline Pressure Resistance
    Engineer A was required to communicate to the client that the schedule was incompatible with producing complete documents rather than submitting deficient work.
  • Engineer A Incomplete Deliverable Disclosure
    Advising the client of material incompleteness is directly required by the obligation to inform clients when a project will not be successful.
  • Engineer B Competence Limit Recognition
    If the review fell outside Engineer B's competence, advising the client of that limitation is required before the project proceeds unsuccessfully.
  • Engineer C Contractor Deficiency Notification
    Engineer C's notification at the pre-construction conference about design deficiencies reflects the obligation to advise relevant parties when a project cannot succeed as designed.
III.2.b. 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.
How this applies in the case (showing 3 of 34)
Obligation
Engineer A Responsible Charge Seal
This provision directly prohibits signing or sealing plans not conforming to engineering standards, matching Engineer A's obligation to seal only complete documents.
Action
Incomplete Work Submission
Submitting incomplete plans and specifications violates the prohibition against completing or sealing documents not in conformity with engineering standards.
State
Engineer A Incomplete Drawings Submitted
Engineer A signed and sealed drawings that did not conform to applicable engineering standards by being incomplete.
Obligation (4)
  • Engineer A Responsible Charge Seal
    This provision directly prohibits signing or sealing plans not conforming to engineering standards, matching Engineer A's obligation to seal only complete documents.
  • Engineer A Competence Dam Drawings
    This provision requires that sealed plans meet applicable engineering standards, directly relating to the obligation to produce technically adequate drawings.
  • Engineer A Complete Design Delivery
    This provision mandates that completed and sealed plans conform to engineering standards, aligning with the obligation to deliver complete buildable documents.
  • Engineer C Contractor Deficiency Notification
    This provision supports Engineer C's obligation to formally report design deficiencies rather than proceed with nonconforming documents.
Action (3)
  • Incomplete Work Submission
    Submitting incomplete plans and specifications violates the prohibition against completing or sealing documents not in conformity with engineering standards.
  • Incomplete Documents Approval
    Approving incomplete documents directly violates the prohibition against signing or sealing plans not conforming to applicable engineering standards.
  • RFP Response Submission
    Responding to an RFP with plans known to be incomplete risks committing to seal nonconforming documents in violation of this provision.
State (5)
  • Engineer A Incomplete Drawings Submitted
    Engineer A signed and sealed drawings that did not conform to applicable engineering standards by being incomplete.
  • Engineer A Deficient Work Product
    Signing and sealing a deficient work product directly violates the prohibition on completing plans not in conformity with engineering standards.
  • Engineer A Incomplete Deliverable
    Completing and sealing an incomplete deliverable violates the duty not to sign plans that do not meet engineering standards.
  • Current Case No Safety Nexus
    Even absent a direct safety nexus, signing incomplete plans still violates the standard against sealing nonconforming documents.
  • Engineer B Unreviewed Incomplete Approval
    Engineer B approved plans that were materially incomplete and thus not in conformity with applicable engineering standards.
Constraint (6)
  • Engineer A Responsible Charge Seal Dam
    III.2.b directly prohibits completing, signing, or sealing plans not in conformity with engineering standards, which is the basis for this constraint.
  • Engineer A Complete Design Constraint
    III.2.b prohibits sealing incomplete plans, directly creating the requirement to provide complete design drawings before submission.
  • Engineer A Competence Dam Drawings
    III.2.b prohibits sealing plans not meeting engineering standards, applying when Engineer A lacked capacity to complete drawings to professional standards.
  • Engineer B Competence Review Limit
    III.2.b prohibits approving plans not in conformity with engineering standards, constraining Engineer B from approving documents without adequate competence.
  • Engineer B Competence Escalation
    III.2.b requires notifying proper authorities and withdrawing if unable to ensure conformity with standards, supporting Engineer B escalating to a supervisor.
  • Engineer A Incomplete Submission Disclosure
    III.2.b requires notifying proper authorities when plans do not conform to standards, creating the disclosure obligation to the agency, federal engineer, and contractors.
Principle (5)
  • Engineer A Deliverable Completeness Concealment
    Engineer A signed and sealed plans that were not in conformity with engineering standards, directly violating this provision.
  • Engineer A Professional Competence Dam Drawings
    Producing and sealing materially incomplete and unbuildable drawings violated the prohibition on completing plans not conforming to engineering standards.
  • Engineer A Professional Integrity Deceptive Acts
    Sealing and submitting non-conforming drawings while attributing deficiencies to external factors violated the duty to refuse to seal substandard plans.
  • Engineer B Federal Review Approval Competence
    Approving sealed drawings that were materially deficient without taking corrective action was inconsistent with the standard of not endorsing non-conforming plans.
  • Engineer B Competence Recognition Approval
    Engineer B approved documents that did not meet engineering standards, failing to notify proper authorities or withdraw as required by this provision.
Role (2)
  • Engineer A Dam Design Engineer
    Engineer A signed and sealed plans and specifications that were incomplete and not in conformity with applicable engineering standards.
  • Engineer B Federal Approving Engineer
    Engineer B signed off on drawings and specifications that did not conform to applicable engineering standards, violating the duty to refuse approval of non-conforming documents.
Event (3)
  • Document Incompleteness Occurrence
    Engineers must not sign or seal incomplete plans that do not conform to applicable engineering standards.
  • Bid Advertisement
    Sealing and releasing incomplete plans for bid advertisement violates the requirement to withhold non-conforming documents.
  • Contract Award to Contractor
    Incomplete plans used as the basis for a contract award reflect a failure to withhold non-conforming specifications.
Capability (6)
  • Engineer A Responsible Charge Verification
    Engineer A was required to verify conformity with engineering standards before sealing and submitting the drawings and specifications.
  • Engineer A Complete Design Delivery
    Producing drawings that are complete and conformant with engineering standards is the direct obligation addressed by this provision.
  • Engineer A Norm Awareness Dam Design
    Recognizing professional standards of completeness and responsible charge is prerequisite to complying with the obligation not to seal nonconforming plans.
  • Engineer B Responsible Charge Verification
    Engineer B was required to identify nonconformity with engineering standards in the submitted documents before approving them.
  • Engineer B Approving Engineer Verification
    Engineer B's independent technical review is required to ensure that approved documents conform to applicable engineering standards.
  • Engineer C Bid Document Adequacy
    Engineer C's evaluation of bidding documents for completeness reflects the standard that plans and specifications must conform to engineering requirements before use.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

When an engineer documents unsatisfactory plans or unjustified expenditure of public funds not involving public health or safety, the engineer has no ethical obligation to continue efforts for change after employer rejection, but has an ethical right to do so as a matter of personal conscience, even to the point of public disclosure.

Citation Context:

The Board cited this case to compare the ethical obligations of engineers regarding disclosure of unsatisfactory plans and unjustified expenditure of public funds, noting that the Code does not require disclosure in cases not involving public health and safety but that engineers have an ethical right to pursue the matter further.

Relevant Excerpts
discussion: "In BER Case No. 82-5 , where an engineer employed by a large defense industry firm documented and reported to his employer excessive costs and time delays by sub-contractors, the Board ruled that the engineer did not have an ethical obligation to continue his efforts to secure a change in the policy after his employer rejected his reports or to report his concerns to proper authority, but has an ethical right to do so as a matter of personal conscience."
discussion: "As in Case No. 82-5 , the issue does not allege a danger to public health or safety, but is premised upon a claim of unsatisfactory plans and the unjustified expenditure of public funds."
discussion: "Unlike Case No. 82-5 , this case does not involve a conflict with the ethical requirement of confidentiality, but concerns the affirmative responsibility of engineers to complete plans in conformity with applicable engineering standards and avoid deceptive acts."
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 58% Facts Similarity 52% Discussion Similarity 63% Provision Overlap 46% Outcome Alignment 100% Tag Overlap 55%
Shared provisions: I.1, I.5, II.1.b, II.2.a, II.2.b, III.1.a Same outcome True View Synthesis
Component Similarity 59% Facts Similarity 64% Discussion Similarity 45% Provision Overlap 27% Outcome Alignment 100% Tag Overlap 56%
Shared provisions: II.1.b, III.1.a, III.3.a Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 42% Discussion Similarity 53% Provision Overlap 29% Outcome Alignment 100% Tag Overlap 60%
Shared provisions: I.5, II.1.b, III.1.a, III.3.a Same outcome True View Synthesis
Component Similarity 53% Facts Similarity 50% Discussion Similarity 68% Provision Overlap 23% Outcome Alignment 100% Tag Overlap 67%
Shared provisions: I.1, II.1.b, III.1.a Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 51% Discussion Similarity 51% Provision Overlap 20% Outcome Alignment 100% Tag Overlap 44%
Shared provisions: II.2.a, II.2.b Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 65% Discussion Similarity 60% Provision Overlap 21% Outcome Alignment 100% Tag Overlap 36%
Shared provisions: I.1, II.2.b, III.1.a Same outcome True View Synthesis
Component Similarity 54% Facts Similarity 43% Discussion Similarity 75% Provision Overlap 30% Outcome Alignment 100% Tag Overlap 30%
Shared provisions: I.1, III.1.a, III.3.a Same outcome True View Synthesis
Component Similarity 59% Facts Similarity 63% Discussion Similarity 59% Provision Overlap 20% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: II.2.a, II.2.b Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 49% Discussion Similarity 53% Provision Overlap 25% Outcome Alignment 100% Tag Overlap 36%
Shared provisions: I.1, I.5, II.2.a, III.1.a Same outcome True View Synthesis
Component Similarity 46% Facts Similarity 47% Discussion Similarity 64% Provision Overlap 31% Outcome Alignment 100% Tag Overlap 56%
Shared provisions: I.1, II.2.a, II.2.b, III.2.b Same outcome True View Synthesis
Questions & Conclusions (3 board)
View Extraction
Board Board question 1

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

Board conclusion It was not ethical for Engineer A to submit drawings and specifications for review and approval that he knew were incomplete.
Implicit (4)

Did Engineer A's assumption that federal funds would absorb cost overruns from his incomplete design constitute a misuse or misrepresentation of public funds, and does that assumption itself represent a separate ethical violation independent of the incompleteness of the drawings?

AnalyticalBeyond the Board's finding that Engineer A acted unethically in submitting incomplete drawings, Engineer A committed a compounded ethical violation by affixing his professional seal to documents he knew were deficient. The act of signing and sealing drawings carries an affirmative professional representation that the work product meets the standard of care and is fit for its intended purpose. By sealing incomplete drawings, Engineer A did not merely fail to disclose a deficiency — he actively misrepresented the completeness and adequacy of the documents to every downstream party who relied on that seal, including Engineer B, the local public agency, and ultimately the bidding contractors. This transforms what might otherwise be characterized as an omission into an affirmative deceptive act, implicating not only the duty of honest disclosure but also the prohibition against deceptive acts and the obligation to avoid sealing plans not in conformity with accepted engineering standards.
AnalyticalEngineer A's rationalization that federal funds — rather than local funds — would absorb cost overruns from his incomplete design represents a separate and independent ethical violation beyond the incompleteness of the drawings themselves. This reasoning reflects a fundamental misuse of public funds: Engineer A effectively treated federal grant money as a contingency reserve to underwrite his own professional shortfall, without the knowledge or consent of either the federal agency or the local public agency. This assumption also introduced a cost allocation bias that distorted his professional judgment, allowing him to rationalize proceeding with a deficient deliverable that he might otherwise have refused to submit. On a dam project — a structure whose failure poses direct risks to public safety — this rationalization is especially troubling, as it subordinated the paramount obligation to protect public welfare to a financial convenience that was not his to invoke.
AnalyticalIn response to Q101: Engineer A's assumption that federal funds would absorb cost overruns from his incomplete design constitutes a separate and independent ethical violation beyond the mere incompleteness of the drawings. By privately reasoning that the financial consequences of his deficient work would fall on federal rather than local coffers, Engineer A engaged in a form of cost allocation rationalization that misrepresented the true risk profile of the project to all stakeholders. This assumption was never disclosed to the local public agency, Engineer B, or any other party, meaning that the parties who bore fiduciary responsibility for public funds were denied the information necessary to make an informed decision about whether to proceed. The rationalization also reflects a troubling indifference to the public interest: federal funds are no less public funds, and the deliberate structuring of one's professional conduct around the expectation that a particular funding source will silently absorb the costs of one's own professional shortfall is itself a form of misrepresentation. Under Code Section II.3.a, engineers must be objective and truthful in professional reports and statements, and Engineer A's silence about both the incompleteness and his funding assumption violated that standard. Under Code Section II.5, engineers shall avoid deceptive acts, and the deliberate non-disclosure of a known deficiency paired with a private financial rationalization satisfies the definition of a deceptive act even in the absence of an affirmative false statement.

Given that the local public agency lacked the in-house technical capacity to review the drawings and specifications, did Engineer A bear a heightened duty of disclosure precisely because his client was unable to independently detect the deficiencies he knew existed?

AnalyticalIn response to Q102: Engineer A bore a heightened and affirmative duty of disclosure precisely because his client, the local public agency, lacked the in-house technical capacity to independently detect the deficiencies he knew existed. The asymmetry of technical knowledge between a licensed professional engineer and a non-technical client is not a passive background condition that reduces the engineer's obligations; it is an aggravating factor that intensifies them. When a client is structurally incapable of identifying a deficiency that the engineer knows exists, the engineer's silence is not merely non-disclosure — it is the functional equivalent of concealment. Code Section III.1.b requires engineers to advise their clients when they believe a project will not be successful, and the submission of drawings and specifications that Engineer A himself acknowledged were incomplete and that Engineer C later characterized as unbuildable clearly falls within the scope of a project that will not be successful in its submitted form. The local public agency's reliance on Engineer A was total and unchecked, which means Engineer A's failure to disclose was not a minor procedural omission but a fundamental breach of the fiduciary-like relationship that professional engineers owe to clients who cannot protect themselves through independent technical review.
AnalyticalThe Board's conclusion regarding Engineer A's ethical failure does not fully address the heightened duty of disclosure that arose specifically because the local public agency lacked in-house technical capacity to review the drawings and specifications. When an engineer's client is demonstrably unable to independently detect deficiencies in the work product, the engineer's obligation of candor is not merely equivalent to the baseline standard — it is materially elevated. Engineer A was aware of this incapacity, and his silence in the face of it effectively denied the local public agency any meaningful opportunity to protect its own interests, to seek independent review, or to require corrections before the project advanced to federal approval and competitive bidding. This asymmetry of technical knowledge, combined with Engineer A's deliberate non-disclosure, constitutes a breach of the faithful agent duty that goes beyond the simple submission of incomplete work.

At what point during the design process did Engineer B's review obligation begin, and should Engineer B have escalated concerns about the adequacy of the submission to higher federal authority rather than simply approving or rejecting the documents unilaterally?

AnalyticalThe Board's conclusion that Engineer B acted unethically in approving incomplete drawings does not fully examine the institutional dimension of that failure. Engineer B's approval did not merely constitute a personal lapse in professional judgment — it lent the formal imprimatur of federal authority to a materially deficient document set, thereby triggering the entire downstream sequence of competitive bidding, contract award, and pre-construction conflict. When a federal approving engineer lacks the technical competence to independently assess the adequacy of a submission, the ethical obligation is not to defer to the submitting engineer's seal but rather to escalate the review to a technically qualified authority or to condition approval on supplemental verification. Engineer B's failure to recognize the limits of his own competence, or to act on those limits by seeking escalation, compounded Engineer A's original violation by converting a deficient private submission into an officially sanctioned federal procurement.
AnalyticalEngineer B's ethical failure also raises a systemic question the Board did not address: the approval process itself appears to have been structurally inadequate for a dam project involving public safety. A federal review mechanism that permits a single engineer to approve complex dam design documents without independent verification protocols, peer review requirements, or competence thresholds specific to dam engineering creates conditions in which individual ethical failures become institutionally probable. While Engineer B bears personal ethical responsibility for the approval, the absence of systemic safeguards suggests that the federal agency's oversight framework itself may have been deficient. Engineers in institutional roles bear a professional obligation to advocate for review processes commensurate with the safety stakes of the projects they oversee, and Engineer B's acquiescence to an inadequate process — whether by silence or by action — represents a failure of professional responsibility that extends beyond the single approval decision.
AnalyticalIn response to Q103: Engineer B's review obligation did not begin only at the moment of formal submission; it encompassed a duty to assess whether the submission was substantively complete before lending federal approval to it. The act of approval by a federal engineering authority is not a ministerial stamp but a professional judgment that the documents meet the standard required for competitive bidding on a public project. Engineer B's approval of materially incomplete drawings effectively transferred federal legitimacy to a deficient document set, thereby enabling the project to proceed through bidding and contract award in a state that Engineer A himself later acknowledged was problematic. Code Section III.2.b prohibits engineers from completing, signing, or sealing plans and specifications not in conformity with applicable engineering standards, and while that provision is most directly applicable to Engineer A, it also informs the standard of care applicable to Engineer B as a reviewing authority. If Engineer B lacked the technical competence to identify the material incompleteness of the submission, Code Section I.1 required him to escalate the matter to higher federal authority or to seek supplemental technical review rather than approving documents whose adequacy he could not independently verify. Deference to Engineer A's professional seal does not relieve Engineer B of independent verification responsibility; it compounds the ethical failure by adding a second layer of professional endorsement to a document set that was known by its author to be deficient.

Was Engineer C's ethical obligation limited to notifying the contracting parties of the unbuildability deficiencies at the pre-construction conference, or did it extend to refusing to proceed with the contract until the drawings and specifications were corrected to a buildable standard?

AnalyticalIn response to Q104: Engineer C's ethical obligation was not limited to notifying the contracting parties of the unbuildability deficiencies at the pre-construction conference. That notification, while better than silence, came after contract award and after Engineer C had already submitted a bid on documents he assessed as containing unbuildable elements. The more demanding ethical standard — and the one more consistent with Code Section II.5's prohibition on deceptive acts and Code Section III.1.b's duty to advise clients of project failure risks — would have required Engineer C to notify the local public agency and Engineer A of the apparent deficiencies before submitting his bid, or at minimum to condition his bid on resolution of those deficiencies. By submitting a low bid on a project whose documents he privately assessed as materially defective, Engineer C entered a binding contractual relationship under conditions he believed to be unbuildable, which is itself a form of deception toward the contracting parties who relied on the competitive bidding process to produce a reliable, executable contract. Furthermore, once Engineer C identified the unbuildability issues, his obligation as a licensed engineer extended beyond mere notification to refusing to proceed with construction until the drawings and specifications were corrected to a buildable standard, because proceeding on deficient dam design documents implicates the paramount obligation to protect public safety under Code Section I.1.
Board Board question 2

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

Board conclusion It was not ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding.
Principle tension (4)

Does Engineer A's duty as a faithful agent to meet the client's specified delivery deadline conflict with his overriding obligation to submit only complete, accurate, and professionally sealed drawings, and if so, which obligation must yield and under what circumstances?

AnalyticalThe tension between Engineer A's duty as a faithful agent to meet the client's delivery deadline and his overriding obligation to submit only complete, accurate, and professionally sealed drawings was never genuinely resolved — it was simply evaded. Engineer A treated the deadline as an absolute constraint and the completeness obligation as a negotiable one, when the ethical hierarchy demands the opposite. The NSPE code's requirement that engineers hold paramount the safety, health, and welfare of the public, combined with the prohibition on completing, signing, or sealing plans not in conformity with accepted engineering standards, establishes that professional completeness is not subordinate to schedule compliance. A faithful agent duty cannot be fulfilled by delivering a deficient product on time; it is fulfilled only when the deliverable itself meets professional standards. Where those two obligations genuinely conflict, the engineer's recourse is disclosure and renegotiation of the deadline — not silent submission of incomplete work. This case teaches that schedule pressure, however real, does not constitute a recognized exception to the completeness and honesty obligations that attach to a professional seal.
AnalyticalIn response to Q201 and Q301: From a deontological perspective, Engineer A's deadline pressure does not constitute a morally sufficient justification for submitting incomplete drawings and specifications, and his duty of honest disclosure was not discharged by silence. The deontological framework evaluates the moral permissibility of an action based on whether it conforms to a universalizable duty, not on whether the actor believed the consequences would be manageable. Engineer A's duty as a faithful agent to meet a client's delivery deadline is a real but subordinate obligation; it cannot override his overriding duty under Code Section III.2.b not to sign or seal plans that are not in conformity with applicable engineering standards, nor his duty under Code Section II.3.a to be truthful in professional statements. When two duties conflict, the engineer's obligation is to disclose the conflict to the client — not to resolve it unilaterally by delivering a deficient product without disclosure. A universalizable rule permitting engineers to submit incomplete sealed drawings whenever deadline pressure exists would systematically undermine the reliability of professional seals and the integrity of public procurement processes. Engineer A's failure to disclose the incompleteness to the local public agency, Engineer B, or any other stakeholder was therefore not merely a procedural lapse but a categorical violation of his duty of honest disclosure.

Does Engineer A's principle of professional competence in dam design conflict with his principle of honesty and non-concealment of deficiency, given that his technical confidence in his own eventual ability to resolve the missing details may have led him to rationalize withholding disclosure of the incompleteness from the client and approving authority?

AnalyticalEngineer A's cost allocation rationalization — his private assumption that federal funds rather than local funds would absorb cost overruns — did not merely reflect poor financial judgment; it functioned as a principle-substitution mechanism that allowed him to suppress the honesty and public welfare principles that should have governed his conduct. By convincing himself that the financial consequences would fall on a deep-pocketed federal source rather than the local public agency, Engineer A effectively neutralized his own sense of obligation to disclose the deficiencies. This represents a compounded ethical failure: the rationalization itself violated the principle of cost allocation neutrality and the prohibition on deceptive acts, because it permitted Engineer A to proceed as though the incompleteness were inconsequential when he knew it was not. The case teaches that a professional's ethical obligations are not contingent on who bears the financial cost of a failure; the duty of honest disclosure and the duty to submit only complete work apply regardless of funding source. Allowing anticipated federal indemnification to substitute for professional completeness inverts the public welfare principle, since federal funds are themselves public funds, and their misuse harms the public interest no less than misuse of local funds.
AnalyticalThe interaction among Engineer A's professional competence principle, Engineer B's competence-limit recognition principle, and Engineer C's bid adequacy and deficiency notification principles reveals a systemic failure in which each actor's ethical shortfall was partially enabled by the others' failures, yet none is thereby relieved of independent responsibility. Engineer A's confidence in his own eventual ability to resolve the missing design details — a form of competence rationalization — led him to treat the incompleteness as a technical inconvenience rather than a professional and public safety violation. Engineer B's deference to Engineer A's professional seal, rather than exercising independent verification or escalating concerns about the submission's adequacy, lent federal legitimacy to a deficient document set and foreclosed the last institutional checkpoint before competitive bidding. Engineer C's decision to submit a low bid on documents he assessed as containing unbuildable elements, and to raise those concerns only after contract award at the pre-construction conference, allowed the procurement process to run to completion on a materially defective foundation. The case teaches that professional ethical obligations are not discharged by reliance on another engineer's seal or institutional role: each engineer in a multi-party project bears an independent, non-delegable duty to act on what he knows. The principle of honest disclosure and the principle of public welfare are not satisfied by collective silence followed by reactive acknowledgment; they require affirmative, timely action at the moment the deficiency is known, regardless of the actor's position in the project hierarchy.

Does Engineer A's cost allocation rationalization — his assumption that federal funds rather than local funds would cover overruns — conflict with the principle of public welfare and safety, insofar as that rationalization functioned as a justification for proceeding with a design that posed a public safety risk on a dam project?

Does Engineer B's obligation to recognize the limits of his own competence in reviewing the incomplete submission conflict with his institutional role as the federal approving authority, and does deference to Engineer A's professional seal relieve Engineer B of independent verification responsibility or instead compound the ethical failure by lending federal legitimacy to a deficient document set?

Board Board question 3

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?

Board conclusion 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.
Theoretical (4)

From a deontological perspective, did Engineer A fulfill his duty of honest disclosure when he knowingly submitted incomplete drawings and specifications without informing the local public agency, Engineer B, or any other stakeholder of their deficiency, regardless of whether he believed federal funds would cover resulting cost overruns?

From a virtue ethics standpoint, did Engineer A demonstrate professional integrity when he rationalized submitting deficient work by assuming federal funds would absorb any cost overruns, thereby prioritizing schedule compliance and financial convenience over the honest exercise of his professional judgment?

From a consequentialist perspective, did the aggregate harm produced by Engineer B's approval of materially incomplete drawings — including wasted public funds, project delays, potential construction defects, and erosion of public trust in federal engineering oversight — outweigh any benefit gained by expediting the project timeline?

AnalyticalIn response to Q303 and Q403: From a consequentialist perspective, Engineer B's approval of materially incomplete drawings produced a cascade of harms that substantially outweighed any benefit gained by expediting the project timeline. The approval enabled the project to proceed through competitive bidding and contract award in a state that Engineer A himself acknowledged was deficient, meaning that every subsequent step in the procurement process — bid preparation by contractors, contract award, and pre-construction planning — was conducted on a false premise of document adequacy. The concrete harms include: wasted public funds expended by bidders preparing bids on unbuildable documents; the risk of construction defects on a dam project with direct public safety implications under Code Section I.1; project delays and cost overruns attributable to the need for redesign after contract award; and erosion of public trust in federal engineering oversight as an effective safeguard against deficient design. Systemically, Engineer B's approval also signals to other design engineers that incomplete submissions can pass federal review, which creates a perverse incentive structure that degrades the quality of future submissions. The counterfactual in which Engineer B either rejected the submission or escalated to higher federal authority would have imposed a short-term delay but would have prevented all of these downstream harms, making it the clearly superior outcome under a consequentialist analysis.

From a deontological perspective, did Engineer C violate his duty of candor to the contracting parties by submitting a low bid on a project whose documents he assessed as containing unbuildable elements, thereby entering a binding contractual relationship under conditions he privately believed to be materially defective?

Cross-cutting analytical questions (4)

These questions consider the case as a whole rather than a specific board question above.

Counterfactual (4)

Would the public safety risk and financial harm to the project have been avoided if Engineer A had disclosed the incompleteness of the drawings and specifications to the local public agency and Engineer B at the time of submission, rather than waiting until the deficiencies were raised by Engineer C at the pre-construction conference?

AnalyticalIn response to Q401 and Q402: The public safety risk and financial harm to the project would very likely have been substantially reduced, if not avoided, had Engineer A disclosed the incompleteness of the drawings and specifications at the time of submission rather than waiting for Engineer C to raise the issue at the pre-construction conference. Early disclosure would have triggered one of two corrective pathways: either the local public agency and Engineer B would have required Engineer A to complete the drawings before approval, preventing the project from proceeding to competitive bidding on deficient documents, or the parties would have made an informed collective decision about how to proceed — a decision that would at minimum have been made with full knowledge of the risks. The alternative counterfactual — Engineer A refusing to submit by the deadline rather than delivering an incomplete product — would have been governed by his contractual obligations to the local public agency and his professional obligations under Code Section III.2.b. While a refusal to deliver might have exposed Engineer A to contractual liability for delay, that consequence does not override his professional obligation not to seal and submit non-conforming plans. The professional and ethical framework clearly contemplates that an engineer's duty to submit only complete and conforming documents takes precedence over schedule compliance, and that the appropriate response to irreconcilable deadline pressure is disclosure and renegotiation, not silent delivery of a deficient product.

If Engineer A had refused to submit the drawings and specifications by the specified deadline rather than delivering an incomplete product, what professional and contractual obligations would have governed that refusal, and would such a refusal have better served the public welfare than the path he chose?

If Engineer B had possessed or sought the technical expertise necessary to identify the material incompleteness of Engineer A's drawings before approving them, would the project have proceeded to competitive bidding, and what systemic changes to federal review protocols might have prevented the approval of deficient documents?

Had Engineer C notified the local public agency and Engineer A of the apparent unbuildability of portions of the project before submitting his bid rather than after contract award, would the competitive bidding process have been suspended for redesign, and would that course of action have better aligned with Engineer C's professional obligations as both a contractor and an engineer?

AnalyticalIn response to Q404 and Q304: From a deontological perspective, Engineer C violated his duty of candor to the contracting parties by submitting a low bid on a project whose documents he assessed as containing unbuildable elements, and the timing of his disclosure — after contract award rather than before bid submission — is ethically significant rather than merely procedurally inconvenient. By waiting until the pre-construction conference to raise deficiencies he had identified during bid preparation, Engineer C allowed the competitive bidding process to run to completion on a false premise, depriving the local public agency of the opportunity to suspend bidding for redesign. Had Engineer C notified the local public agency and Engineer A of the apparent unbuildability before submitting his bid, the contracting parties would have had the information necessary to make a meaningful decision about whether to proceed, suspend, or redesign — and the competitive bidding process would have served its intended function of producing reliable, executable contracts. Engineer C's post-award disclosure, while better than permanent silence, did not cure the ethical deficiency of having entered a binding contractual relationship under conditions he privately believed to be materially defective. Code Section II.5's prohibition on deceptive acts applies to Engineer C in his capacity as a licensed engineer, and submitting a bid while privately assessing the project as unbuildable without major changes satisfies the functional definition of a deceptive act toward the contracting parties who relied on the integrity of the bidding process.
Decisions & Arguments (5)
View Extraction

Should Engineer A disclose the incompleteness of the dam design documents to the client and approving authority at the time of submission, or submit the documents without flagging the deficiency?

Options considered:
O1 Formally notify the client and approving authority in writing that the submitted documents are incomplete, identify the missing elements, and specify conditions under which completion would occur. Board's choice
O2 Submit the documents on schedule on the assumption that all parties understand the staged nature of the design due to the pending federal funding, without a formal written disclosure of incompleteness.
O3 Refuse to submit the documents until they meet minimum completeness standards, even if this means missing the deadline and potentially jeopardizing the funding timeline.
Argument structure:
Warrants

Engineers are obligated to be honest and forthright with clients and to disclose information that could affect the safety or adequacy of a project. Submitting incomplete documents without disclosure misrepresents the state of the work and may expose the public to safety risks. Competing pressure arises from contractual deadlines and the expectation that funding would later allow completion of the design.

Rebuttals

Engineer A may have believed the incompleteness was understood by all parties given the funding situation, or that submission of partial documents was an accepted industry practice under the circumstances. The expectation of future federal funding could be seen as a reasonable basis for staged delivery.

Grounds

Engineer A submitted dam design drawings and specifications that were materially incomplete. The incompleteness was attributed to time pressures and an expectation of future federal funding. No disclosure of the deficiency was made to the client or the approving authority at the time of submission. Multiple obligations including complete design delivery and responsible charge seal were unmet, and Engineer A's proficiency in incomplete deliverable disclosure was rated only basic.

Engineer A Deliverable Completeness Disclosure

Should Engineer A seal the incomplete dam design documents, or decline to seal until the documents meet the standard required for responsible charge?

Options considered:
O1 Withhold the professional seal until the design documents are sufficiently complete to support a responsible charge determination, communicating this position clearly to the client. Board's choice
O2 Affix the seal accompanied by a written statement explicitly limiting its scope to the completed portions of the design and identifying elements not yet finalized.
O3 Seal and submit the documents to preserve the project timeline, relying on the approving authority's review process to identify any deficiencies before construction approval is granted.
Argument structure:
Warrants

A professional seal represents that the engineer has exercised responsible charge over the work and that the documents are complete and technically adequate. Sealing incomplete documents misrepresents the state of the design and may mislead the approving authority into treating the submission as a finished product. The public safety obligation for dam design was also unmet.

Rebuttals

Engineer A may have interpreted the seal as applying only to the portions of the design that were complete, or may have believed that the approving authority understood the documents were preliminary. Some jurisdictions permit phased submissions with seals on partial documents when the limitations are understood.

Grounds

Engineer A affixed a professional seal to dam design documents that were materially incomplete. The obligation for responsible charge seal was unmet, and Engineer A's proficiency in responsible charge verification was rated only basic. Sealing incomplete documents may imply to reviewers and the public that the design is complete and adequate.

Engineer A Responsible Charge Seal

Should Engineer B escalate the review to a qualified engineer upon recognizing competence limitations, or proceed with approving the dam design documents as submitted?

Options considered:
O1 Inform a supervisor of the competence limitation and request that a qualified engineer be assigned to review the dam design documents before any approval is granted. Board's choice
O2 Approve the documents while formally documenting identified deficiencies and incompleteness in writing, placing the record in the project file and notifying the submitting engineer.
O3 Treat Engineer A's professional seal as sufficient evidence of responsible charge and approve the documents on the basis that the submitting engineer bears professional responsibility for completeness.
Argument structure:
Warrants

Engineers must perform services only in areas of their competence and must not approve work they cannot adequately evaluate. When a reviewer recognizes an inability to perform a competent review, the obligation is to inform a supervisor so that a qualified engineer can be assigned. Approving incomplete documents without escalation may create a false impression of adequacy and expose the public to safety risks.

Rebuttals

Engineer B may have believed the documents were adequate for the stage of the project, or may have relied on Engineer A's professional judgment and seal as sufficient basis for approval. Institutional pressures and the expectation that deficiencies would be caught later in the process could also have influenced the decision.

Grounds

Engineer B approved dam design documents that were materially incomplete. The obligation for competence limit escalation was unmet and the obligation for approving engineer verification was also unmet. Engineer B's proficiency in competence limit recognition was rated intermediate, while proficiency in buildability assessment and responsible charge verification were rated advanced, suggesting Engineer B had the capacity to identify the deficiencies.

Engineer B Competence Limit Escalation

Should Engineer A pursue external disclosure of the design deficiencies and public funds concerns after internal reporting was rejected, or treat the matter as resolved once internal channels were exhausted?

Options considered:
O1 After internal reporting is rejected, escalate disclosure of the design deficiencies and public safety concerns to the relevant state or federal regulatory authority responsible for dam safety. Board's choice
O2 Treat the matter as resolved once internal channels are exhausted, on the basis that the employer's rejection of the reports and the existence of an independent approving authority are sufficient safeguards.
O3 Consult legal counsel to determine the scope of professional and legal obligations before deciding whether to pursue external disclosure, balancing whistleblower protections against contractual and employment constraints.
Argument structure:
Warrants

Engineers have a paramount obligation to protect public safety. Where a design deficiency poses a direct safety risk, the obligation to disclose extends beyond internal channels to external authorities if internal reporting is rejected. The public safety dimension of a dam design elevates the duty beyond the whistleblower conscience standard applicable to financial waste alone.

Rebuttals

Engineer A may have reasonably concluded that the approving authority's review process would catch the deficiencies, or that the employer's rejection of internal reports indicated a legitimate business judgment about the adequacy of the design. The distinction between a right and a duty to continue disclosure after employer rejection creates genuine uncertainty about the scope of the obligation.

Grounds

Engineer A's obligations regarding public funds misrepresentation and safety were unmet. The dam design involved direct public safety risks, not merely financial waste. The defense industry whistleblower principle distinguishes between cases involving unjustified public expenditure, where continued pursuit is a right but not a duty, and cases involving direct public safety threats, where the duty to disclose is stronger.

Whistleblower Conscience Obligation

Should Engineer A treat time pressure and anticipated funding as sufficient justification for submitting incomplete documents without disclosure, or are those circumstances insufficient to override the disclosure obligation?

Options considered:
O1 Treat the disclosure obligation as unconditional and formally notify all relevant parties of the incompleteness regardless of time pressures or funding status. Board's choice
O2 Treat the submission as a recognized phased deliverable under the project's funding structure, documenting the staged nature of the design in the project record and relying on the approving authority's familiarity with the funding context.
O3 Refuse to submit incomplete documents and instead negotiate with the client for an extended deadline that allows for a complete submission, even at the risk of delaying the funding application.
Argument structure:
Warrants

Professional obligations to clients and the public are not suspended by schedule pressures or funding contingencies. The engineer's duty to disclose material deficiencies in submitted work exists independently of the reasons for those deficiencies. Allowing time pressure to justify non-disclosure would undermine the reliability of professional submissions generally.

Rebuttals

In practice, phased design delivery under funding contingencies is common in public works projects, and all parties may implicitly understand that documents submitted at an early stage are not final. If the client and approving authority were aware of the funding situation, the argument that non-disclosure was misleading is weakened.

Grounds

Engineer A cited time pressures and an expectation of future federal funding as reasons for submitting incomplete documents without disclosure. The obligation for deadline pressure resistance was unmet and proficiency in that area was rated basic. The obligation for complete design delivery was also unmet despite advanced proficiency in that area, suggesting the failure was a choice rather than a capability gap.

Deliverable Completeness Disclosure Obligation
Event Timeline (15)
15 sequenced 6 actions 9 events
Case timeline
The dam project was partially funded by a federal grant, which brought federal oversight requirements and Engineer B's review role into the project.
Engineer A's firm decided to respond to the local public agency's RFP for dam design, submitting an impressive brochure and completing a personal interview, thereby implicitly committing to deliver a complete and competent design within the project's stated time parameters.
Fulfills (1)
  • Obligation to perform services within area of competence by representing the firm as capable
Engineer A's firm was awarded the design contract by the local public agency following submission of an impressive brochure and completion of a personal interview.
Engineer A's drawings and specifications were produced in a knowingly incomplete state, creating a condition of deficient project documentation that would affect all downstream project phases.
Engineer A decided to submit drawings and specifications that he knew to be incomplete by the specified deadline, citing time pressure as justification, rather than requesting an extension or otherwise seeking relief from the schedule constraint.
Violates (3)
  • Obligation to provide complete design drawings and specifications
  • Obligation to avoid deceptive acts
  • Obligation to perform services within area of competence
Engineer A decided not to inform the local public agency, the federal funding agency, or any other stakeholder that the submitted drawings and specifications were incomplete, privately rationalizing that federal funds would cover any resulting cost overruns.
Violates (4)
  • Obligation to avoid deceptive acts
  • Obligation to provide complete design drawings and specifications
  • Obligation of honest disclosure to client and funding agency
  • Public fund stewardship
Engineer B, acting on behalf of the federal funding agency's engineering staff, decided to approve Engineer A's incomplete drawings and specifications without flagging identified or identifiable deficiencies or escalating the review to a more competent reviewer.
Violates (3)
  • Obligation to perform services within area of competence
  • Obligation to recognize limits of competency and escalate appropriately
  • Public fund stewardship
Engineer B, acting as the federal funding agency's engineering staff reviewer, completed a review of the incomplete documents and approved them without identifying or flagging the deficiencies.
The dam project was advertised for bids to the public following federal approval of the incomplete documents, initiating the contractor selection process.
Engineer C, as owner of Hi-Lo Construction, decided to submit the low bid on the dam project based on documents that, upon review, should have revealed incompleteness and unbuildable elements, without seeking clarification from the owner or Engineer A and without adjusting the bid to reflect the additional work required.
Violates (2)
  • Obligation to perform services within area of competence
  • Obligation to make an informed professional judgment before committing to contract performance
Hi-Lo Construction, owned by Engineer C, was identified as the winning low bidder and awarded the construction contract for the dam project.
A pre-construction conference was convened bringing together Engineer A, Engineer C, and the agency, at which the deficiencies in the project documents were first openly discussed.
At the pre-construction conference, Engineer C declared that portions of the dam project were unbuildable, surfacing the practical construction consequences of the document deficiencies.
At the pre-construction conference, Engineer A acknowledged the incompleteness of the drawings and specifications only after Engineer C raised the issue and declared portions of the project unbuildable, rather than proactively disclosing the deficiencies to any stakeholder at any earlier point.
Violates (3)
  • Obligation to avoid deceptive acts
  • Obligation of honest disclosure to client and funding agency
  • Obligation to provide complete design drawings and specifications
Engineer A acknowledged at the pre-construction conference that the submitted drawings and specifications were incomplete, confirming what had previously been concealed from the agency and contractor.
Narrative (2 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are Engineer A, a licensed engineer whose firm was awarded a contract by a small local public agency to design a new dam to be funded in part by a federal grant. Your firm prepared and sealed the drawings and specifications, which were then submitted to Engineer B at the federal funding agency for approval and subsequently used to advertise the project for bids. Hi-Lo Construction, the low bidder, has now raised concerns at the pre-construction conference that significant design detail is missing and that portions of the project cannot be built as documented. The local public agency lacks the technical staff to independently evaluate the drawings and specifications, and you are aware that the documents were submitted before the design work was complete. The decisions you face involve your obligations to your client, the approving authority, and the public as the project moves toward construction.

Main characters (2)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Engineer A Roles in this case: hover for definitions Dam Design Engineer
Engineer B Roles in this case: Federal Approving Engineer

Other people involved in the case but not central to the opening narrative.

Opening States (10)
Incomplete Deliverable Submitted State Undisclosed Deadline Pressure State Client Funding Assumption State Engineer A Incomplete Drawings Submitted Engineer A Undisclosed Deadline Pressure Engineer A Federal Funding Assumption Local Agency Technical Review Capacity Engineer A Deficient Work Product Engineer A Public Safety Risk No Public Safety Nexus State
Summary
  • Engineers must not submit incomplete drawings or specifications for official review, even when facing schedule pressure or client demands.
  • The integrity of the approval process depends on engineers certifying only work that is genuinely ready for evaluation, not work that will be revised later.
  • Knowingly misrepresenting the completeness of submitted documents is a form of deception toward the reviewing authority, regardless of intent to correct the deficiencies afterward.

© Licensed under the GNU GPL v3 | Report Issue