Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Incomplete Plans and Specifications – Engineer, Government, and Contractor Responsibilities
Step 4 of 5

219

Entities

5

Provisions

1

Precedents

19

Questions

20

Conclusions

Phase Lag

Transformation
Phase Lag Delayed consequences reveal obligations not initially apparent
Engineer A's concealed incompleteness and Engineer B's approval created a set of 'parallel' obligations that ran silently alongside the actual technical reality of the drawings; the ethical and practical consequences (unbuildability) were not revealed until the pre-construction conference, well after the RFP, design approval, and bid award had already occurred. This produces a phase lag between the point of ethical breach (nondisclosure at submission) and the point of consequence discovery (Engineer C's objection at pre-construction), with the Board's conclusions (C4, C7, C9) explicitly grappling with this delayed revelation and its retroactive implications for responsibility.
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

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

I.1 board + analysis Hold paramount the safety, health, and welfare of the public.
How this applies in the case (showing 3 of 22)
Obligation
Engineer A Complete Design Delivery Duty
Delivering complete dam design drawings protects public safety and welfare.
Action
Incomplete Design Delivery
Delivering incomplete designs endangers public safety and welfare
State
Unbuildable Dam Project Parts
Public safety is at risk if dam parts cannot be built as designed
Obligation (3)
  • Engineer A Complete Design Delivery Duty
    Delivering complete dam design drawings protects public safety and welfare.
  • Engineer B Competence Duty
    Reviewing within competence safeguards public safety on the dam project.
  • Engineer C Informed Bid Duty
    An informed bid accounting for incomplete documents helps ensure safe construction.
Action (2)
  • Incomplete Design Delivery
    Delivering incomplete designs endangers public safety and welfare
  • Nondisclosure of Incompleteness
    Failing to disclose deficiencies threatens public safety and welfare
State (3)
  • Unbuildable Dam Project Parts
    Public safety is at risk if dam parts cannot be built as designed
  • Incomplete Dam Design Documents
    Incomplete plans threaten public welfare if construction proceeds
  • Concealed Incompleteness Of Deliverables
    Hiding incompleteness endangers public safety and welfare
Constraint (3)
  • Engineer A Incompleteness Concealment Prohibition
    Withholding incompleteness information endangers public safety and welfare
  • Engineer A Incomplete Seal Prohibition
    Sealing incomplete designs risks public safety
  • Engineer B Competence Review Boundary
    Reviewing beyond competence risks public safety
Principle (2)
  • Design Completeness on Dam Project
    Complete design detail is necessary to protect public safety in a dam project
  • Competence in Federal Agency Review
    Proper review of dam plans is required to safeguard public welfare
Role (3)
  • Engineer A Design Engineer
    Delivering incomplete drawings under schedule pressure risks public safety in dam construction
  • Engineer B Federal Reviewing Engineer
    Approving incomplete signed and sealed drawings for a dam risks public safety
  • Engineer C Bidding Engineer
    As a professional engineer reviewing bid documents, has a duty to protect public safety by flagging deficiencies
Event (2)
  • Design Deficiency Revealed
    Public safety is compromised when design deficiencies are revealed during construction
  • Pre-Construction Conference
    Public welfare must be considered when issues are discussed before construction begins
Resource (1)
  • Dam Design Drawings and Specifications
    The dam design must hold public safety paramount given the risks of dam failure
Capability (3)
  • Engineer A Dam Design
    Public safety depends on complete and adequate dam design being delivered
  • Engineer C Constructability Assessment
    Identifying incomplete specifications at pre-construction protects public safety in dam construction
  • Engineer B Design Review
    Reviewing the signed and sealed drawings for a dam relates to safeguarding public welfare
II.3.a board + analysis 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 19)
Obligation
Engineer A Incompleteness Disclosure Duty
Disclosing incomplete plans requires objective and truthful reporting to clients and agencies.
Action
Nondisclosure of Incompleteness
Omitting relevant information about deficiencies violates truthful reporting duty
State
Concealed Incompleteness Of Deliverables
Failing to disclose incompleteness violates truthful and complete reporting
Obligation (1)
  • Engineer A Incompleteness Disclosure Duty
    Disclosing incomplete plans requires objective and truthful reporting to clients and agencies.
Action (2)
  • Nondisclosure of Incompleteness
    Omitting relevant information about deficiencies violates truthful reporting duty
  • Admission With Justification
    Admitting fault but with justification relates to truthful and complete disclosure obligations
State (4)
  • Concealed Incompleteness Of Deliverables
    Failing to disclose incompleteness violates truthful and complete reporting
  • Public Fund Expenditure Claim
    Claims about fund use must be truthful and include all relevant information
  • Federal Funding Coverage Assumption
    Assumptions about funding must be verified and truthfully stated
  • Engineer A Incompleteness Awareness
    Knowing about incompleteness requires truthful disclosure in reports
Constraint (2)
  • Engineer A Incompleteness Concealment Prohibition
    Withholding relevant information violates objectivity and truthfulness requirements
  • Engineer A Federal Funds Misrepresentation
    Misrepresenting funding status omits relevant and pertinent information
Principle (2)
  • Honesty in Federal Funds Assertion
    Justifying incomplete work with unfounded funding claims violates truthful reporting
  • Transparency in Incomplete Dam Design
    Failing to disclose missing design details violates the duty to include all relevant information
Role (2)
  • Engineer A Design Engineer
    Delivered drawings and specifications lacking relevant and pertinent information
  • Engineer B Federal Reviewing Engineer
    Approved incomplete drawings and specifications as if they were complete and current
Event (2)
  • Pre-Construction Conference
    Engineers must be truthful and disclose all relevant information during this conference
  • Design Deficiency Revealed
    Full disclosure of deficiencies is required once they are identified
Resource (2)
  • Engineer A Firm Brochure
    The brochure must be objective and truthful about the firm's qualifications
  • Dam Design Drawings and Specifications
    The drawings and specifications must include all relevant and pertinent information
Capability (2)
  • Engineer A Incompleteness Disclosure
    Truthful and complete reporting requires disclosing known incompleteness of drawings
  • Engineer C Bid Document Evaluation
    Evaluating bid documents requires objective and complete assessment of relevant information
II.5 board + analysis Engineers shall avoid deceptive acts.
How this applies in the case (showing 3 of 15)
Obligation
Engineer A Incompleteness Disclosure Duty
Failing to disclose incomplete plans would be a deceptive act.
Action
Nondisclosure of Incompleteness
Concealing known deficiencies constitutes a deceptive act
State
Concealed Incompleteness Of Deliverables
Concealing incomplete work is a deceptive act
Obligation (1)
  • Engineer A Incompleteness Disclosure Duty
    Failing to disclose incomplete plans would be a deceptive act.
Action (2)
  • Nondisclosure of Incompleteness
    Concealing known deficiencies constitutes a deceptive act
  • Incomplete Design Delivery
    Delivering incomplete plans without disclosure is a deceptive act
State (2)
  • Concealed Incompleteness Of Deliverables
    Concealing incomplete work is a deceptive act
  • Engineer A Incompleteness Awareness
    Knowingly hiding awareness of incompleteness constitutes deception
Constraint (2)
  • Engineer A Incompleteness Concealment Prohibition
    Concealing incompleteness is a deceptive act
  • Engineer A Federal Funds Misrepresentation
    Using a false excuse for incompleteness is deceptive
Principle (2)
  • Honesty in Federal Funds Assertion
    Bordering on fraud through misleading funding justification is a deceptive act
  • Transparency in Incomplete Dam Design
    Not disclosing incomplete drawings is a form of deception
Role (2)
  • Engineer A Design Engineer
    Signing and sealing incomplete plans as complete constitutes a deceptive act
  • Engineer B Federal Reviewing Engineer
    Approving known incomplete plans without disclosure is a deceptive act
Event (2)
  • Bid Advertisement
    Advertising bids based on incomplete plans without disclosure is a deceptive act
  • Design Deficiency Revealed
    Failing to disclose known deficiencies constitutes deceptive conduct
Resource (1)
  • Engineer A Firm Brochure
    The brochure must avoid deceptive claims about qualifications
Capability (1)
  • Engineer A Incompleteness Disclosure
    Delivering known incomplete plans without disclosure constitutes a deceptive act
III.1.b board + analysis 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 16)
Obligation
Engineer A Incompleteness Disclosure Duty
Engineer A must advise the client if the incomplete project risks failure.
Action
Deficiency Disclosure
Engineers must advise clients when a project has deficiencies threatening its success
State
Unbuildable Dam Project Parts
Engineer must advise client that unbuildable parts will cause project failure
Obligation (1)
  • Engineer A Incompleteness Disclosure Duty
    Engineer A must advise the client if the incomplete project risks failure.
Action (2)
  • Deficiency Disclosure
    Engineers must advise clients when a project has deficiencies threatening its success
  • Nondisclosure of Incompleteness
    Failing to advise client of deficiencies violates duty to disclose project risks
State (3)
  • Unbuildable Dam Project Parts
    Engineer must advise client that unbuildable parts will cause project failure
  • Incomplete Dam Design Documents
    Engineer must warn client the project cannot succeed with incomplete documents
  • Engineer A Incompleteness Awareness
    Awareness of incompleteness obligates advising the client of failure risk
Constraint (1)
  • Engineer A Incompleteness Concealment Prohibition
    Engineer must advise client if project will not succeed due to incompleteness
Principle (2)
  • Schedule Pressure on Dam Design Delivery
    Engineer A should have advised the client that meeting the deadline would compromise project success
  • Design Completeness on Dam Project
    Engineer A had a duty to advise that the design was incomplete and thus unsuccessful as delivered
Role (2)
  • Engineer A Design Engineer
    Should have advised the client that the incomplete design would not result in a successful project
  • Engineer C Bidding Engineer
    Had professional duty to advise the client of unbuildable design elements before proceeding
Event (2)
  • Design Deficiency Revealed
    Engineer must advise client that the project may not succeed due to deficiencies
  • Pre-Construction Conference
    Engineer should advise client of potential project failure at this stage
Resource (1)
  • Public Agency RFP for Dam
    The engineer must advise the agency issuing the RFP if the dam project will not be successful
Capability (2)
  • Engineer A Incompleteness Disclosure
    Engineer A had the duty to advise the client agency that the incomplete project would not succeed
  • Engineer C Constructability Assessment
    Engineer C's identification of incompleteness relates to advising the client of project viability concerns
III.2.b board + analysis 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 24)
Obligation
Engineer A Complete Design Delivery Duty
Signing and sealing incomplete plans violates the requirement to conform to engineering standards.
Action
Incomplete Design Delivery
Signing or delivering plans not conforming to standards violates this provision
State
Incomplete Dam Design Documents
Engineer should not sign incomplete plans not meeting standards
Obligation (2)
  • Engineer A Complete Design Delivery Duty
    Signing and sealing incomplete plans violates the requirement to conform to engineering standards.
  • Engineer B Competence Referral Duty
    Engineer B should not approve or complete review of non-conforming plans outside his competence without referral.
Action (2)
  • Incomplete Design Delivery
    Signing or delivering plans not conforming to standards violates this provision
  • Plan Approval
    Approving nonconforming plans violates the duty to ensure conformity with standards
State (4)
  • Incomplete Dam Design Documents
    Engineer should not sign incomplete plans not meeting standards
  • Complete Design Delivery Requirement
    This provision mandates delivering only conforming complete plans
  • Engineer A Delivery Deadline Pressure
    Deadline pressure should not justify signing nonconforming plans
  • Engineer A Incompleteness Awareness
    Awareness of nonconformity requires withdrawal rather than signing
Constraint (2)
  • Engineer A Incomplete Seal Prohibition
    Directly addresses prohibition on signing and sealing nonconforming incomplete plans
  • Engineer B Competence Review Boundary
    Reviewing and approving nonconforming incomplete work without competence violates this standard
Principle (3)
  • Transparency in Incomplete Dam Design
    Signing and sealing incomplete plans violates the requirement to conform to engineering standards
  • Design Completeness on Dam Project
    Delivering an incomplete full design without proper delegation violates the standard for sealing complete plans
  • Competence in Federal Agency Review
    Approving incomplete plans without proper review breaches the standard for conformity checks
Role (2)
  • Engineer A Design Engineer
    Signed and sealed plans and specifications that did not conform to applicable engineering standards
  • Engineer B Federal Reviewing Engineer
    Approved signed and sealed plans that were not in conformity with applicable engineering standards
Event (3)
  • Design Contract Award
    Engineer must ensure plans conform to standards when accepting the design contract
  • Bid Advertisement
    Plans advertised for bid must conform to applicable engineering standards
  • Design Deficiency Revealed
    Engineer must notify authorities and withdraw if deficient plans are not corrected
Resource (2)
  • Dam Design Drawings and Specifications
    Engineers shall not sign or seal plans that fail to conform to applicable engineering standards
  • BER Case No. 82-5
    This precedent case addresses the duty to notify authorities regarding unsatisfactory plans
Capability (4)
  • Engineer A Dam Design
    Signing and sealing incomplete plans not conforming to standards violates this provision
  • Engineer A Incompleteness Disclosure
    Engineer A should have withdrawn or notified authorities upon knowingly delivering nonconforming plans
  • Engineer B Design Review
    Reviewing and approving signed drawings that do not conform to standards implicates this provision
  • Engineer B Competence Self-Assessment
    Failure to recognize incompetency in reviewing nonconforming plans relates to this provision
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:

An engineer has no Code-mandated duty to continue efforts to change an employer's policy or report concerns to authorities when there is no danger to public health or safety, but has an ethical right to do so as a matter of personal conscience; this principle is distinguished here because the present case involves an affirmative duty to complete plans in conformity with engineering standards, not a confidentiality conflict.

Citation Context:

The Board discussed this prior case, which involved an engineer reporting excessive costs and time delays to his employer, to compare the public health/safety analysis and then to distinguish it from the present case's focus on the affirmative duty to complete plans properly.

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..."
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 57% Facts Similarity 44% Discussion Similarity 72% Outcome Alignment 100% Tag Overlap 38% Principle Overlap 72%
Same outcome unethical View Synthesis
Component Similarity 56% Facts Similarity 54% Discussion Similarity 51% Outcome Alignment 100% Tag Overlap 40% Principle Overlap 69%
Same outcome unethical View Synthesis
Component Similarity 62% Facts Similarity 63% Discussion Similarity 59% Outcome Alignment 100% Tag Overlap 11% Principle Overlap 70%
Same outcome unethical View Synthesis
Component Similarity 59% Facts Similarity 59% Discussion Similarity 58% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 60%
Same outcome unethical View Synthesis
Component Similarity 63% Facts Similarity 65% Discussion Similarity 60% Outcome Alignment 100% Tag Overlap 8% Principle Overlap 57%
Same outcome unethical View Synthesis
Component Similarity 62% Facts Similarity 56% Discussion Similarity 64% Outcome Alignment 100% Tag Overlap 8% Principle Overlap 58%
Same outcome unethical View Synthesis
Component Similarity 60% Facts Similarity 49% Discussion Similarity 53% Outcome Alignment 100% Tag Overlap 18% Principle Overlap 56%
Same outcome unethical View Synthesis
Component Similarity 55% Facts Similarity 43% Discussion Similarity 75% Outcome Alignment 100% Tag Overlap 38% Principle Overlap 56%
Same outcome unethical View Synthesis
Component Similarity 52% Facts Similarity 48% Discussion Similarity 49% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 70%
Same outcome unethical View Synthesis
Component Similarity 53% Facts Similarity 34% Discussion Similarity 72% Outcome Alignment 100% Tag Overlap 43% Principle Overlap 55%
Same outcome unethical 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.
Resolved by: The board held that schedule pressure could not override the obligation of design completeness, treating the deadline as an insufficient justification for sealing unfinished work. (confidence 0.85)
III.1.b. III.2.b. 3 principles 3 facts Conditions Narrative
Implicit (2)

Did the Local Public Agency's lack of in-house technical resources effectively eliminate any independent check on the incomplete drawings before they reached Engineer B for approval?

AnalyticalEngineer B's approval of incomplete drawings is compounded by the structural fact that the Local Public Agency lacked any in-house technical capacity to independently review the design. This means Engineer B's review was not one layer among several safeguards but effectively the sole technical checkpoint standing between Engineer A's incomplete work and public bidding. The absence of a backstop heightens, rather than diminishes, Engineer B's duty to ensure his review was rigorous and within the bounds of his own competence; if he lacked the specialized expertise to detect the missing design detail, he had an obligation to seek qualified assistance or decline to approve, rather than allow the sole review point to be a rubber stamp.
Resolved by: The board weighed the practical reality that Engineer B was the only safeguard against the temptation to treat that isolation as an excuse, and resolved that isolation increases rather than decreases his duty of rigorous, competence-bounded review. (confidence 0.78)
I.1. III.2.b. 2 principles 3 facts Conditions Narrative
AnalyticalBecause the Local Public Agency lacked in-house technical resources (Q101), Engineer B's review effectively functioned as the sole technical safeguard against incomplete design documents reaching the competitive bidding stage. This structural gap did not excuse Engineer B's approval, but it does mean that his failure to detect or object to the incompleteness had outsized consequences, since no other independent check existed in the review chain before the drawings were advertised for bids.
Resolved by: The board balances the structural absence of a backstop against the excusing effect it might otherwise have, concluding that the gap amplifies the consequences of Engineer B's failure rather than excusing it. (confidence 0.78)
I.1. III.2.b. 2 principles 3 facts Conditions Narrative

Does Engineer A's reliance on the assumption that federal funds would cover cost overruns, as a justification for withholding disclosure of incompleteness, constitute a separate ethical violation beyond simply submitting incomplete drawings?

AnalyticalEngineer A's stated confidence that federal funds would cover any cost overruns does not mitigate his ethical exposure; if anything, it aggravates it. This assumption reveals that Engineer A treated the deficiency as a financial risk to be absorbed after the fact rather than a professional and safety risk requiring disclosure before bidding. By privately resolving the funding question in his own mind, he substituted his personal judgment about the acceptability of the risk for the informed consent of the client and the public agency, who never had the opportunity to weigh in. This is problematic independent of whether federal funds actually materialized, because the ethical failure lies in the unilateral, undisclosed risk-shifting itself, not in whether the gamble paid off.
AnalyticalEngineer A's assumption that federal funds would cover cost overruns cannot substitute for disclosure and constitutes an independent honesty problem beyond mere incompleteness (Q103). By silently relying on an unstated financial contingency to justify withholding known deficiencies from the client and reviewing engineer, Engineer A effectively made an implicit, undisclosed representation about project cost and scope that was never verified or agreed to by the parties responsible for approving and funding the work.
Resolved by: The board weighs Engineer A's reliance on an unstated financial contingency against his duty of honest disclosure, concluding that the former cannot substitute for or excuse a failure of the latter and instead constitutes a distinct violation. (confidence 0.80)
II.3.a. II.5. 2 principles 3 facts Conditions Narrative
Also discussed in: C101
Principle tension (3)

How should Schedule Pressure on Dam Design Delivery be balanced against the principle of Design Completeness on Dam Project when a deadline forces submission of unfinished work?

AnalyticalSchedule pressure on Engineer A to deliver drawings by a specified date does not ethically outweigh the principle of design completeness (Q201). The Code's requirement that engineers not seal or submit non-conforming plans is not conditioned on scheduling convenience; when deadline pressure and completeness conflict, the engineer's obligation is to disclose the resulting incompleteness or negotiate an extension, not to submit deficient work silently.
Resolved by: The board subordinated schedule pressure to the completeness obligation, holding that deadline convenience cannot excuse submission of nonconforming plans and that the proper response to a time conflict is disclosure or a negotiated extension rather than silent submission. (confidence 0.80)
III.2.b. 2 principles 3 facts Conditions Narrative
AnalyticalThe case demonstrates that Schedule Pressure on Dam Design Delivery cannot ethically override Design Completeness on Dam Project: Engineer A's justification that he felt pressured to meet a delivery date did not excuse submitting known-incomplete drawings, nor did it excuse his failure to disclose the incompleteness. The Board's finding of a violation shows that practical/business pressures are subordinate to the Code's substantive completeness and disclosure obligations -- schedule pressure may explain non-compliance but does not justify or mitigate it.
Resolved by: The board subordinated the practical pressure of the deadline to the substantive obligations of completeness and disclosure, treating schedule pressure as an explanatory factor but not a legitimate offset against those duties. (confidence 0.80)
III.2.b. III.1.b. II.5. 3 principles 3 facts Conditions Narrative

How should Honesty in Federal Funds Assertion be balanced against Transparency in Incomplete Dam Design when Engineer A justified non-disclosure by assuming federal funding would absorb any resulting cost overruns?

AnalyticalEngineer A's reliance on Honesty in Federal Funds Assertion (his confidence that federal funds would cover cost overruns) reflects a conflation of two distinct ethical duties: an obligation to ensure adequate funding exists, and an entirely separate obligation of Transparency in Incomplete Dam Design to disclose known deficiencies regardless of funding availability. The Board's conclusion indicates that a favorable financial outcome or expectation cannot substitute for honesty about the state of one's work -- these principles are not fungible, and satisfying one does not discharge the other.
Resolved by: The board separated the duty to ensure adequate funding from the distinct duty to disclose known deficiencies, concluding that confidence in one could not substitute for compliance with the other. (confidence 0.77)
II.5. III.2.b. II.3.a. 2 principles 3 facts Conditions Narrative

Does Transparency in Incomplete Dam Design conflict with Schedule Pressure on Dam Design Delivery, given that disclosing known deficiencies might have delayed the project beyond the imposed deadline?

AnalyticalTransparency about known deficiencies and schedule pressure are not mutually exclusive; Engineer A could have disclosed the incompleteness to the Local Public Agency or Engineer B while still meeting the delivery date, thereby allowing the reviewing parties to make an informed decision about whether to delay the bidding process (Q204). The Board's finding of a violation rests specifically on the failure to disclose, not on the existence of schedule pressure itself, indicating that transparency was the ethically required response to that pressure rather than silence.
Resolved by: The board treated transparency and schedule pressure as compatible rather than truly conflicting, weighing the feasibility of timely disclosure to the agency or Engineer B against silent submission, and located the violation in the concealment rather than in the pressure itself. (confidence 0.75)
II.3.a. II.5. 2 principles 3 facts Conditions Narrative
Also discussed in: C301
Theoretical (2)

From a deontological perspective, did Engineer A fulfill his duty to advise his client that the dam project, as designed, would not be successful due to incomplete drawings and specifications?

AnalyticalFrom a deontological standpoint grounded in Code provision III.1.b, Engineer A had a duty to advise the client that the project as designed and delivered would not be successful due to incomplete drawings and specifications, independent of any expected outcome (Q301). This duty is not conditional on whether sufficient funds would later materialize to cover the gaps; it attaches at the moment the engineer becomes aware that the deliverable does not meet professional completeness standards, and Engineer A's own admission that he knew of the incompleteness confirms the duty was triggered and breached.
Resolved by: The board applied a deontological framework that prioritized the duty-based obligation to advise the client over any outcome-based consideration such as eventual funding sufficiency, treating the duty as triggered by awareness alone. (confidence 0.80)
III.1.b. 2 principles 3 facts Conditions Narrative

Did the outcome of the case -- namely, Engineer A's confidence that federal funds would cover the increased costs -- justify his decision to submit knowingly incomplete drawings and specifications?

AnalyticalThe eventual availability of federal funds to absorb cost overruns does not retroactively justify Engineer A's decision to submit known-incomplete drawings, because the ethical violation lies in the act of nondisclosure and delivery of substandard work product, not in the financial outcome (Q302). A favorable resource outcome is irrelevant to whether the professional obligation to deliver complete, conforming plans was met at the time of submission; ends-based justification of this kind is inconsistent with the Code's rule-based prohibitions on signing and sealing nonconforming documents.
Resolved by: The board rejected an ends-justify-means weighing, holding that a favorable financial outcome could not offset the rule-based violation of submitting nonconforming, incomplete sealed documents. (confidence 0.80)
III.2.b. 2 principles 3 facts Conditions Narrative
Also discussed in: C102 C303
Counterfactual (2)

If Engineer A had disclosed the incompleteness of the drawings and specifications to the local public agency or Engineer B before submission, rather than concealing it, would the Board still have found his conduct unethical?

AnalyticalHad Engineer A disclosed the incompleteness of the drawings to the Local Public Agency or Engineer B prior to submission, the Board would likely have reached a materially different, and probably favorable, conclusion regarding his conduct (Q401). The violation identified by the Board centers specifically on concealment combined with delivering nonconforming plans; timely disclosure would have shifted responsibility for the decision to proceed (or delay) onto the client and reviewing engineer, converting a unilateral ethical breach into a transparent, jointly-managed risk decision.
Resolved by: The board treated concealment paired with nonconforming delivery as the operative wrong, so it weighed disclosure not as curing the incompleteness itself but as transferring the risk-acceptance decision to the client and reviewer, which it judged would have materially changed the ethical character of the act. (confidence 0.78)
II.5. III.2.b. III.1.b. 2 principles 3 facts Conditions Narrative

If sufficient federal funds had not, in fact, been available to cover the increased costs arising from the incomplete design, would the Board's conclusion about the ethicality of Engineer A's submission be altered or intensified?

AnalyticalIf sufficient federal funds had not actually been available to cover the increased costs stemming from the incomplete design, the Board's condemnation of Engineer A's conduct would likely have been intensified rather than altered in kind (Q404). The ethical breach already exists independent of funding outcomes, but a funding shortfall would have compounded the harm to the public agency and project, illustrating that Engineer A's private assumption about federal funds was an unjustified gamble with public resources rather than a legitimate risk-mitigation strategy.
Resolved by: The board weighed the funding assumption as a private risk gamble against the public duty of completeness, concluding that a failed gamble would deepen rather than offset the existing breach because the wrongness of concealment did not depend on the funding outcome. (confidence 0.75)
II.5. III.2.b. 2 principles 3 facts Conditions Narrative
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.
Resolved by: The board weighed Engineer B's role as the only competent technical check against the agency's resource shortage and found that this gap increased, rather than excused, his duty to catch the deficiency before approval. (confidence 0.80)
III.2.b. 2 principles 3 facts Conditions Narrative
Implicit (1)

What duty did Engineer B have to assess his own competence to detect the incompleteness of the drawings before approving them for federal-funded competitive bidding?

AnalyticalEngineer B carried an affirmative duty to assess his own competence to detect incompleteness in specialized dam design documents before approving them for federal-funded competitive bidding (Q104). Given the agency's lack of independent technical capacity, Engineer B's approval role required either genuine subject-matter competence to identify missing design detail or a referral to someone with that expertise; approving complex, signed and sealed documents without this self-assessment undermines the code's competence-boundary requirements.
Resolved by: The board weighed Engineer B's duty to stay within his competence against the practical reality that he was the only technical check available to a client with no in-house expertise, and resolved this by requiring either genuine competence or referral rather than allowing the gap to excuse unchecked approval. (confidence 0.75)
2 principles 3 facts Conditions Narrative
Also discussed in: C103
Principle tension (1)

Does Competence in Federal Agency Review conflict with the requirement of Design Completeness on Dam Project when the reviewing engineer may lack the specialized expertise needed to detect missing design detail?

AnalyticalCompetence in Federal Agency Review and Design Completeness on Dam Project were placed in unresolved tension by the Local Public Agency's lack of in-house technical resources: because no independent check existed before Engineer B's review, his approval became the sole safeguard for completeness, yet the Board's concern about his possible competence gap suggests his review may not have been an adequate substitute. This shows that when an agency's institutional structure removes redundant checks, the remaining reviewer's competence obligation becomes ethically decisive rather than a secondary formality -- if that reviewer cannot detect deficiencies within his expertise, the whole system's safeguard against incomplete designs fails, regardless of formal approval having occurred.
Resolved by: The board weighed the agency's absent in-house check against Engineer B's competence obligation and found that with no redundant safeguard, Engineer B's competence became the decisive rather than secondary determinant of whether the incomplete design would be caught. (confidence 0.72)
III.2.b. 2 principles 3 facts Conditions Narrative
Theoretical (1)

Did Engineer B act with professional integrity in approving drawings and specifications that may have exceeded his area of competence to review, given the agency's lack of in-house technical resources?

Also discussed in: C302
Counterfactual (1)

If the local public agency had possessed in-house technical resources to independently review the drawings and specifications, would the Board still have concluded that Engineer B's approval on behalf of the federal government was unethical?

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.
Resolved by: The board weighed Engineer C's demonstrated competence to detect the deficiencies against his choice to submit a low bid without qualification, concluding his competence obligated earlier disclosure rather than after-the-fact objection. (confidence 0.80)
I.1. II.3.a. 2 principles 3 facts Conditions Narrative
Implicit (1)

Should Engineer C have raised concerns about the adequacy of the drawings and specifications during the bidding phase, rather than waiting until the pre-construction conference after the contract had already been awarded?

AnalyticalThe Board's conclusion regarding Engineer C focuses on the act of submitting a bid on documents he later called unbuildable, but an important nuance is the timing of his objection. Because Engineer C possessed the competence to evaluate the bid documents, his silence during the bidding phase and subsequent objection only after contract award suggests either that the deficiencies were not fully apparent until deeper engagement with the drawings occurred during pre-construction planning, or that Engineer C recognized the problems earlier but chose to bid low and raise issues afterward, potentially anticipating change orders or renegotiated terms. The Board's finding would be strengthened by distinguishing between these two scenarios, since they carry different ethical weight: the former suggests a competence limitation, while the latter suggests strategic non-disclosure analogous to Engineer A's own concealment.
Resolved by: The board implicitly weighs a competence-limitation explanation (deficiencies not apparent until deeper engagement) against a strategic non-disclosure explanation (bid low, raise issues later), treating the two as carrying different ethical weight without fully resolving which applied. (confidence 0.72)
II.3.a. II.5. 2 principles 3 facts Conditions Narrative
AnalyticalEngineer C's obligation to flag design inadequacies arguably arose at the bid-preparation stage, not merely at the pre-construction conference (Q102). An engineer competent to evaluate bid documents (Engineer C Bid Evaluation Competence) has an obligation to raise material concerns about buildability before submitting a bid rather than after being awarded the contract, since post-award objections shift risk and cost uncertainty onto the public project after competitive bidding integrity has already been relied upon by the agency and other bidders.
Resolved by: The board weighs Engineer C's individual interest in winning the bid against the systemic cost to bidding integrity and public risk allocation, favoring an obligation to disclose material buildability concerns before submission over waiting until after award. (confidence 0.75)
II.3.a. II.5. III.1.b. 2 principles 3 facts Conditions Narrative
Theoretical (1)

Did Engineer C act with professional integrity by submitting a low bid on documents he was competent to evaluate, only to later characterize the same design as 'unbuildable' at the pre-construction conference?

Also discussed in: C104
Counterfactual (1)

If Engineer C had identified the 'unbuildable' design deficiencies during bid preparation rather than only at the pre-construction conference after the contract was awarded, would the Board still have found his bid submission unethical?

Decisions & Arguments (4)
View Extraction

Should Engineer A disclose the known incompleteness of the drawings and specifications to the Local Public Agency and federal reviewer before submission, or submit the signed and sealed documents without disclosure to meet the delivery deadline?

Options considered:
O1 Inform the Local Public Agency and the federal reviewing agency that the signed and sealed drawings are missing significant design detail, allowing them to decide whether to delay bidding or accept the risk. Board's choice
O2 Sign, seal, and deliver the incomplete drawings and specifications on schedule without informing the client or reviewing agency of the missing design detail.
O3 Negotiate a delivery extension with the Local Public Agency in order to finish the missing design detail before signing, sealing, and submitting the documents.
Argument structure (Toulmin):
Grounds

Engineer A signed and sealed the drawings and specifications knowing much of the design detail was missing, and delivered them for bidding without informing the local public agency or the federal reviewing agency of this fact.

Warrant

Engineers must deliver complete conforming plans under contract (Engineer A Complete Design Delivery Duty); where completeness cannot be achieved by deadline, engineers must disclose known deficiencies to the client and reviewers rather than conceal them (Engineer A Incompleteness Disclosure Duty); the disclosure duty prevails over schedule convenience.

Rebuttal

Would not apply if Engineer A had in fact clearly communicated the incompleteness to the agency and reviewers despite the deadline pressure, converting the matter into a jointly managed risk decision rather than concealment.

Engineer A Incompleteness Disclosure Duty Engineer A Incompleteness Concealment Prohibition

Should Engineer A treat an assumed future availability of federal funds as sufficient justification for withholding disclosure of the design's incompleteness, or should he disclose the deficiency regardless of funding expectations?

Options considered:
O1 Inform the client and reviewing agency of the missing design detail without relying on any private assumption that federal funds would later cover the shortfall. Board's choice
O2 Withhold disclosure of the incompleteness based on a private, unverified expectation that federal funds would be awarded to complete the work.
O3 Confirm with the federal agency whether additional funds are actually available before deciding whether disclosure of the incompleteness is necessary.
Argument structure (Toulmin):
Grounds

Engineer A admitted he expected Federal funds would be awarded to complete the work, and cited this expectation to explain why he did not disclose the incompleteness of the drawings he had already signed and sealed.

Warrant

Engineers must not excuse nondisclosure of known deficiencies by an unverified assumption about future funding (Engineer A Federal Funds Misrepresentation); the duty to disclose known incompleteness (Engineer A Incompleteness Disclosure Duty) is not discharged by a private, unconfirmed belief about financial outcomes.

Rebuttal

Would not apply if the federal funding expectation had been communicated to and verified with the client and reviewing agency at the time of submission, rather than used as an undisclosed private justification after the fact.

Engineer A Incompleteness Disclosure Duty Engineer A Federal Funds Misrepresentation

Should Engineer B have referred the review of the incomplete drawings to a more qualified engineer or supervisor, or approved the drawings himself despite the agency's lack of independent technical capacity?

Options considered:
O1 Inform a supervisor that the review exceeds his competence and request assignment of an engineer qualified to assess the missing design detail before any approval is given. Board's choice
O2 Approve the drawings and specifications for competitive bidding based on his own review, without independently verifying whether he possessed the specialized expertise to detect the missing design detail.
O3 Withhold approval and request that Engineer A supply additional design detail or clarification before proceeding, without formally escalating the review to a supervisor.
Argument structure (Toulmin):
Grounds

Engineer B approved the drawings and specifications on behalf of the federal government for competitive bidding; the Local Public Agency had no in-house technical resources, making Engineer B the sole reviewer standing between the incomplete drawings and public bidding.

Warrant

Engineers must perform reviews only within their area of competence (Engineer B Competence Duty); where competence is lacking, engineers must refer the matter to someone qualified rather than approve the work themselves (Engineer B Competence Referral Duty); the referral duty prevails when no independent backstop exists.

Rebuttal

Would not apply if Engineer B was fully competent and diligent in his review regardless of the agency's resources, or if the incompleteness was so subtle or specialized that no reasonably competent reviewer in his role could have detected it.

Engineer B Competence Referral Duty

Should Engineer C have identified the design's inadequacies and reflected them in his bid with appropriate additional-services items during the bidding phase, or submit a low bid and raise the 'unbuildable' concerns only at the pre-construction conference after contract award?

Options considered:
O1 Identify the missing design detail during bid preparation and include appropriate bid items for the additional services needed to complete the work, informing the agency of the risk. Board's choice
O2 Submit a competitive low bid without addressing the design's adequacy, then raise buildability concerns only at the pre-construction conference after the contract has been awarded.
O3 Refuse to submit a bid on the drawings and specifications until the local public agency provides more complete design documentation.
Argument structure (Toulmin):
Grounds

Engineer C, competent to evaluate the bid documents, submitted a low bid and was awarded the construction contract, then at the pre-construction conference stated that much of the design detail was lacking and that parts of the project were unbuildable without major changes.

Warrant

Engineers competent to assess bid documents must reflect known inadequacies in their bids for the owner's benefit (Engineer C Informed Bid Duty); this obligation arises at bid preparation, before competitive bidding integrity has been relied upon by the agency and other bidders, and prevails over the strategic advantage of raising concerns post-award.

Rebuttal

Would not apply if Engineer C lacked sufficient knowledge of the inadequacies until deeper engagement with the drawings during pre-construction planning, or if the deficiencies were latent and not reasonably discoverable through normal bid document review.

Engineer C Informed Bid Duty
Event Timeline (13)
13 sequenced 7 actions 6 events
Case timeline
A small local public agency issues a request for proposals for a new dam project financed in part by a federal grant.
State changes (1)
  • began: Federal Funding Coverage Assumption
Engineer A's firm responds to the RFP from the small local public agency and secures the design contract through its brochure and personal interview.
Causal-normative reasoning(confidence 0.60)
Contract Pursuit is normatively neutral on its own, but as the originating link that leads to Design Contract Award and eventually to the Incomplete Design Delivery, it establishes the causal foundation upon which the later violations become possible.
State changes (1)
  • began: Complete Design Delivery Requirement
Engineer A's firm is awarded the contract for the design, drawings, and specifications following its impressive brochure and personal interview.
State changes (2)
  • began: Complete Design Delivery Requirement
  • began: Engineer A Delivery Deadline Pressure
Engineer A, under deadline pressure, delivers signed and sealed drawings and specifications that lack much design detail, choosing to meet the specified date rather than complete the design or request more time.
Violates (2)
  • Obligation to provide a complete set of design drawings and specifications
  • Responsibility to complete plans in conformity with applicable engineering standards
Causal-normative reasoning(confidence 0.85)
Incomplete Design Delivery violates the obligation to provide complete design drawings and the responsibility to meet engineering standards, and this matters causally because the incomplete plans were what Engineer B approved, setting off Bid Advertisement, Low Bid Submission, and Construction Contract Award on a defective basis.
State changes (1)
  • began: Incomplete Dam Design Documents
Engineer A does not inform anyone that the drawings and specifications are incomplete, relying on his confidence that federal funds would cover any increased costs. The case treats this omission as his conduct.
Violates (2)
  • Duty to avoid deceptive acts
  • Responsibility to complete plans in conformity with applicable engineering standards
Causal-normative reasoning(confidence 0.80)
Nondisclosure of Incompleteness violates the duty to avoid deceptive acts and the responsibility to complete plans according to standards, and its downstream effect of causing the Design Deficiency to be Revealed shows how concealment let the flaw persist undetected until it surfaced later, increasing the harm and complicating accountability.
State changes (1)
  • began: Public Fund Expenditure Claim
Engineer B of the federal funding agency approves Engineer A's signed and sealed drawings and specifications despite their incompleteness, with the local agency lacking in-house resources to review them.
At stake (1)
  • Obligation to perform services within their area of competence
Violates (1)
  • Duty to recognize lack of competency and take appropriate action, such as informing a supervisor
Causal-normative reasoning(confidence 0.80)
Because Plan Approval was caused directly by the Incomplete Design Delivery, Engineer B's failure to recognize the limits of his own competency and flag the deficiency to a supervisor allowed a flawed design to move forward into Bid Advertisement, so the violation is significant precisely because it let an unrecognized problem propagate into public bidding and construction.
Following federal approval of the signed and sealed drawings and specifications, the project is duly advertised for bids under standard procurement procedure.
State changes (1)
  • began: Engineer C Bid Document Access
Engineer C, owner of Hi-Lo Construction, submits the low bid on the project after having the opportunity to review the bidding documents, presumably knowing the inadequacies of the documents and the risks involved.
Violates (1)
  • Responsibility to reflect document inadequacies in the bid or seek clarification before bidding
Causal-normative reasoning(confidence 0.75)
Because Engineer C's low bid was submitted directly on the strength of the approved but incomplete plans, failing to flag the document's inadequacies or seek clarification before bidding allowed a defective design to move forward into a binding construction contract, compounding the earlier nondisclosure rather than catching it.
The construction contract is awarded to Hi-Lo Construction as the low bidder under the low-bid selection rule.
The scheduled pre-construction conference convenes, providing the setting in which Engineer C discloses the design deficiencies and Engineer A admits the incompleteness.
At the pre-construction conference, Engineer C points out that much of the design detail is lacking and declares that certain parts of the project are unbuildable without major changes, rather than having raised the issues during bidding.
Causal-normative reasoning(confidence 0.65)
Deficiency Disclosure carries no violation because it represents the corrective moment, triggered by the Pre-Construction Conference, in which the previously concealed design problem is finally brought to light and leads to Engineer A's Admission With Justification.
State changes (2)
  • began: Engineer C Knowledge Of Inadequacies
  • ended: Concealed Incompleteness Of Deliverables
Engineer A generally agrees with Hi-Lo's characterization of the documents at the pre-construction conference, but defends his conduct by citing deadline pressure and his confidence that federal funds would cover increased costs.
Violates (1)
  • Duty to avoid deceptive acts
Causal-normative reasoning(confidence 0.75)
Since Engineer A's admission was triggered only after the deficiency was disclosed at the pre-construction conference, framing that admission with self-serving justification rather than forthright acknowledgment constitutes a deceptive act that undermines trust at the very point where the earlier concealment was finally being surfaced and needed honest correction.
State changes (1)
  • began: Engineer A Incompleteness Awareness
The incompleteness of the drawings and specifications becomes known to the project parties, with certain parts of the project declared unbuildable without major changes, ending the concealment of the deficiencies.
State changes (4)
  • began: Engineer A Incompleteness Awareness
  • began: Engineer C Knowledge Of Inadequacies
  • began: Unbuildable Dam Project Parts
  • ended: Concealed Incompleteness Of Deliverables
Narrative (4 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, having won a contract with a small local public agency to design a new dam project partially financed by a federal grant. Your firm's brochure and interview performance secured the award, and you prepared the signed and sealed drawings and specifications under a fixed delivery deadline. Engineer B, on the federal funding agency's engineering staff, reviewed and approved your drawings and specifications, after which the project was advertised for bids and awarded to the low bidder, Hi-Lo Construction, owned by Engineer C. The local public agency lacks in-house technical staff capable of independently reviewing your work. At the pre-construction conference, Engineer C states that much of the design detail is missing and that certain portions of the project are unbuildable without major changes, a characterization you do not dispute, while acknowledging you knew the documents were incomplete when submitted and expected federal funds to cover any resulting cost increases. You must now consider what obligations you and the other engineers involved bear regarding disclosure, review, and reliance on funding assumptions as the project moves forward.

Main characters (4)

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: Design Engineer

Guided by: Transparency in Incomplete Dam Design, Honesty in Federal Funds Assertion, Competence in Federal Agency Review

Tension between Engineer A Incompleteness Disclosure Duty and Engineer A Incompleteness Concealment Prohibition

Engineer A faces pressure to deliver a complete design on schedule to satisfy the client, but time or scope limitations mean the work is not actually finished, and sealing an incomplete design would violate the prohibition on certifying unfinished work. This creates a direct tension between the obligation to hand over a finished product and the constraint against affixing a professional seal to incomplete plans.

Engineer C has a duty to submit a bid based on full and accurate information about the project scope, but this depends entirely on Engineer A upholding the prohibition against concealing incompleteness. If Engineer A's disclosure is inadequate, Engineer C's ability to fulfill the informed bid duty is undermined by a failure that originates outside Engineer C's control, creating a cross role tension between one engineer's obligation and another's constraint.

Tension between Engineer A Incompleteness Disclosure Duty and Engineer A Federal Funds Misrepresentation

Engineer B Roles in this case: Federal Reviewing Engineer

Engineer B is obligated to competently evaluate the federally funded design, yet the review boundary constraint may limit the scope of what Engineer B is authorized or expected to examine. If the incompleteness lies outside that defined review boundary, Engineer B's competence duty to catch deficiencies conflicts with the formal limits placed on the review role, risking that incomplete work passes federal review undetected.

Engineer C Roles in this case: Contractor OwnerBidding Engineer

Engineer C has a duty to submit a bid based on full and accurate information about the project scope, but this depends entirely on Engineer A upholding the prohibition against concealing incompleteness. If Engineer A's disclosure is inadequate, Engineer C's ability to fulfill the informed bid duty is undermined by a failure that originates outside Engineer C's control, creating a cross role tension between one engineer's obligation and another's constraint.

Attaches to role: Contractor Owner
Hi-Lo Construction Roles in this case: Contractor

Engineer C has a duty to submit a bid based on full and accurate information about the project scope, but this depends entirely on Engineer A upholding the prohibition against concealing incompleteness. If Engineer A's disclosure is inadequate, Engineer C's ability to fulfill the informed bid duty is undermined by a failure that originates outside Engineer C's control, creating a cross role tension between one engineer's obligation and another's constraint.

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

Engineer A faces pressure to deliver a complete design on schedule to satisfy the client, but time or scope limitations mean the work is not actually finished, and sealing an incomplete design would violate the prohibition on certifying unfinished work. This creates a direct tension between the obligation to hand over a finished product and the constraint against affixing a professional seal to incomplete plans.

Engineer B is obligated to competently evaluate the federally funded design, yet the review boundary constraint may limit the scope of what Engineer B is authorized or expected to examine. If the incompleteness lies outside that defined review boundary, Engineer B's competence duty to catch deficiencies conflicts with the formal limits placed on the review role, risking that incomplete work passes federal review undetected.

The Board’s deliberation

How the Board of Ethical Review resolved the case, verbatim from its published conclusions.

It was not ethical for Engineer A to submit drawings and specifications for review and approval that he knew were incomplete.
It was not ethical for Engineer B to approve a set of incomplete drawings on behalf of the Federal government for competitive bidding.
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.
Opening States (10)
Incomplete Dam Design Documents Unbuildable Dam Project Parts Engineer A Delivery Deadline Pressure Concealed Incompleteness Of Deliverables Agency Review Capacity Shortage Federal Funding Coverage Assumption Engineer A Incompleteness Awareness Board Uncertainty On Approval Decision No Confidentiality Conflict Present Public Fund Expenditure Claim
Summary
  • Submitting incomplete drawings and specifications for formal review and approval is unethical regardless of schedule pressure or client demands, because completeness is a threshold requirement rather than something to be balanced against deadlines.
  • Disclosing that a design is incomplete does not cure the underlying violation of presenting that design for approval, since the act of submission itself implies a level of finality the work has not reached.
  • When federal funds are involved, submitting incomplete work for approval risks compounding a professional ethics violation with a misrepresentation to a funding authority, raising the stakes beyond ordinary client relations.

© Licensed under the GNU GPL v3