Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Competence To Perform Foundation Design
Step 4 of 5

148

Entities

5

Provisions

3

Precedents

15

Questions

18

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Responsibility for the footing-design competence issue moves in a linear chain: Engineer B's independent, non-delegable duty to self-assess competence (C7) exists first; upon Engineer A's discovery of doubts, the duty to raise concerns transfers to Engineer A (C2); once reported, the obligation to act transfers to the contractor (C5); and if the contractor ignores it, the obligation transfers again to external licensing/regulatory authorities (C6). Each stage represents a discrete handoff of who bears the operative ethical duty, consistent with the 'transfer' pattern rather than genuine paradox or repetition.
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.

II.2 board + analysis Engineers shall perform services only in the areas of their competence.
How this applies in the case (showing 3 of 19)
Obligation
Engineer B Footing Competence Duty
Requires Engineer B to perform footing design only within his area of competence
Action
Assignment Acceptance
Engineers must only accept assignments within their area of competence
State
Engineer B Foundation Competence Gap
Engineer B lacks competence in foundation design services being performed
Obligation (3)
  • Engineer B Footing Competence Duty
    Requires Engineer B to perform footing design only within his area of competence
  • Engineer A Competence Concern Report
    Relates to ensuring services are performed only by those competent in the specific field
  • Engineer A Peer Confrontation Duty
    Directly addresses the duty to act when a peer lacks competence in the required area
Action (2)
  • Assignment Acceptance
    Engineers must only accept assignments within their area of competence
  • Specialist Retention Decision
    Retaining a specialist ensures services are performed only within areas of competence
State (2)
  • Engineer B Foundation Competence Gap
    Engineer B lacks competence in foundation design services being performed
  • Engineer A Reservations About B
    Engineer A questions whether B is performing services within area of competence
Constraint (1)
  • Engineer B Footing Competence Boundary
    This provision establishes the general competence requirement that directly creates this constraint
Principle (1)
  • Competence Concern in Footing Design
    Directly addresses whether Engineer B is performing services outside their area of competence
Role (2)
  • Engineer B Footing Design Engineer
    Performed foundation design work outside his competence as a chemical engineer
  • Engineer A Project Engineer
    Must ensure work under project falls within areas of competence including that of consultants relied upon
Event (2)
  • Qualification Verification Failure
    This provision requires competence verification before undertaking services, directly relevant to the failure event.
  • Competence Concern Emergence
    The general competence requirement is the basis for the emerging concern about qualifications.
Resource (4)
  • NSPE Code of Ethics
    This provision is part of the NSPE Code of Ethics topic on competence
  • BER Case 71-2
    This case addresses retaining experts to ensure competence in specific fields
  • BER Case 78-5
    This case involves seeking work only in areas of competence
  • BER Case 85-3
    This case involves an engineer accepting a role lacking necessary competence
Capability (2)
  • Engineer A Competence Concern Recognition
    This provision underlies the concern that Engineer B may be performing services outside his area of competence
  • Engineer A Peer Competence Assessment
    This provision provides the standard by which Engineer A assesses whether Engineer B has sufficient competence
II.2.a board + analysis Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.
How this applies in the case (showing 3 of 15)
Obligation
Engineer B Footing Competence Duty
Specifies that Engineer B must have education or experience in structural footing design
Action
Assignment Acceptance
Assignments should only be undertaken when qualified by education or experience
State
Engineer B Foundation Competence Gap
Engineer B undertook foundation assignment without sufficient education or experience
Obligation (2)
  • Engineer B Footing Competence Duty
    Specifies that Engineer B must have education or experience in structural footing design
  • Engineer A Peer Confrontation Duty
    Basis for Engineer A determining whether Engineer B has qualifying education or experience
Action (2)
  • Assignment Acceptance
    Assignments should only be undertaken when qualified by education or experience
  • Qualification Investigation
    Investigating qualifications ensures the specific technical field requirement is met before accepting work
State (2)
  • Engineer B Foundation Competence Gap
    Engineer B undertook foundation assignment without sufficient education or experience
  • Specialist Retention Infeasible for Footings
    Lack of specialist retention means assignment proceeds without qualified expertise
Constraint (1)
  • Engineer B Footing Competence Boundary
    This provision requires qualification by education or experience which defines the boundary of this constraint
Principle (1)
  • Competence Concern in Footing Design
    Engineer B lacks education or experience in foundation design yet undertook the assignment
Role (1)
  • Engineer B Footing Design Engineer
    Undertook foundation design assignment without qualifying education or experience in structural or geotechnical engineering
Event (2)
  • Qualification Verification Failure
    This provision specifically requires verifying education or experience before accepting assignments, which failed here.
  • Competence Concern Emergence
    Lack of specific qualification triggers the competence concern described in this event.
Resource (2)
  • BER Case 85-3
    This case involves an engineer undertaking a position without adequate education or experience in surveying
  • BER Case 78-5
    This case involves misrepresenting qualifications to obtain work outside competence
Capability (2)
  • Engineer A Competence Concern Recognition
    This provision requires qualification by education or experience which Engineer A questions regarding Engineer B's chemical engineering background
  • Engineer A Peer Competence Assessment
    This provision sets the criteria of education and experience that Engineer A uses to evaluate Engineer B's qualifications
II.2.b board + analysis Engineers shall not affix their signatures to any plans or documents dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control.
How this applies in the case (showing 3 of 11)
Obligation
Engineer B Footing Competence Duty
Prohibits Engineer B from signing plans outside his competence
State
Engineer B Foundation Competence Gap
Engineer B may sign documents on footing design despite lacking competence
Constraint
Engineer B Footing Competence Boundary
This provision prohibits signing documents outside ones competence which reinforces this constraint
Obligation (2)
  • Engineer B Footing Competence Duty
    Prohibits Engineer B from signing plans outside his competence
  • Engineer A Conditional Withdrawal Duty
    Relates to Engineer A not certifying work not under his control or competence
State (2)
  • Engineer B Foundation Competence Gap
    Engineer B may sign documents on footing design despite lacking competence
  • Sole Purpose Footing Retention
    Footing design documents require signature only from someone competent in that area
Constraint (1)
  • Engineer B Footing Competence Boundary
    This provision prohibits signing documents outside ones competence which reinforces this constraint
Principle (1)
  • Competence Concern in Footing Design
    Engineer B may be signing foundation documents despite lacking competence in that subject matter
Role (1)
  • Engineer B Footing Design Engineer
    Risk of signing plans on foundation design subject matter in which he lacks competence
Event (2)
  • Qualification Verification Failure
    Signing documents without confirming competence directly relates to this verification failure.
  • Competence Concern Emergence
    The prohibition on signing without competence underlies the emergence of the competence concern.
Capability (2)
  • Engineer A Competence Concern Recognition
    This provision prohibits signing documents outside ones competence which relates directly to the concern about Engineer B
  • Engineer A Peer Competence Reporting
    Engineer A reports concerns partly because signing plans outside competence would violate this provision
II.2.c board + analysis Engineers may accept assignments and assume responsibility for coordination of an entire project and sign and seal the engineering documents for the entire project, provided that each technical segment is signed and sealed only by the qualified engineers who prepared the segment.
How this applies in the case (showing 3 of 11)
Obligation
Engineer B Footing Competence Duty
Allows Engineer B to sign only the segment he is qualified to prepare
Action
Specialist Retention Decision
Coordinating engineers may retain qualified specialists to sign and seal their own technical segments
State
Sole Purpose Footing Retention
Coordination of project requires qualified engineers to sign specific technical segments like footings
Obligation (2)
  • Engineer B Footing Competence Duty
    Allows Engineer B to sign only the segment he is qualified to prepare
  • Engineer A Client and Authority Reporting Duty
    Relates to coordination responsibility and ensuring qualified engineers sign their segments
Action (2)
  • Specialist Retention Decision
    Coordinating engineers may retain qualified specialists to sign and seal their own technical segments
  • Assignment Acceptance
    Accepting a coordination role requires ensuring qualified engineers handle specific segments
State (2)
  • Sole Purpose Footing Retention
    Coordination of project requires qualified engineers to sign specific technical segments like footings
  • Specialist Retention Infeasible for Footings
    Provision allows delegation to qualified specialists which is not feasible here
Principle (1)
  • Competence Concern in Footing Design
    Raises whether foundation design segment should be signed by a qualified geotechnical engineer rather than Engineer B
Role (2)
  • Engineer A Project Engineer
    Coordinates the entire design/build project and relies on qualified engineers to sign their own technical segments
  • Engineer B Consultant to Contractor
    Retained as a segment consultant expected to sign and seal only the footing design portion if qualified
Event (1)
  • Qualification Verification Failure
    This provision outlines proper procedure for verifying qualified engineers for each segment, which was not followed.
Resource (1)
  • BER Case 71-2
    This case discusses coordinating projects and retaining specialists for technical segments
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 12)
Obligation
Engineer A Client and Authority Reporting Duty
Requires notifying proper authorities if unprofessional conduct continues
Action
Concern Reporting
Engineers must notify proper authorities if standards are not being met and withdraw from service
State
Engineer B Foundation Competence Gap
Signing plans without competence may violate applicable engineering standards
Obligation (2)
  • Engineer A Client and Authority Reporting Duty
    Requires notifying proper authorities if unprofessional conduct continues
  • Engineer A Conditional Withdrawal Duty
    Mandates withdrawal from the project if nonconforming plans are insisted upon
Action (1)
  • Concern Reporting
    Engineers must notify proper authorities if standards are not being met and withdraw from service
State (3)
  • Engineer B Foundation Competence Gap
    Signing plans without competence may violate applicable engineering standards
  • Concerns Reported To Contractor
    Reporting concerns relates to notifying proper authorities about nonconforming work
  • Engineer A Reservations About B
    Engineer A must address concerns about nonconformity through proper notification
Principle (1)
  • Competence Concern in Footing Design
    Engineer B should not seal foundation plans that may not conform to applicable engineering standards given lack of expertise
Role (2)
  • Engineer A Project Engineer
    Must not allow completion or sealing of nonconforming plans and must address concerns with the client if standards are not met
  • Engineer B Footing Design Engineer
    Must not seal footing design plans that fail to conform to applicable engineering standards given his lack of competence
Event (2)
  • Qualification Verification Failure
    Signing nonconforming plans without proper competence verification violates this standard.
  • Competence Concern Emergence
    The concern about competence relates to ensuring conformity with engineering standards before signing.
Capability (1)
  • Engineer A Peer Competence Reporting
    This provision obligates reporting when plans may not conform to applicable engineering standards due to lack of competence
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 3 Lineage Graph

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

Principle Established:

An engineer must possess at least some substantive degree of background and experience relevant to the responsibilities of a position or assignment in order to ethically undertake it, even if the assignment does not require direct preparation of technical documents.

Citation Context:

Cited as the most closely analogous precedent, where an engineer with only chemical engineering background was deemed unqualified to serve as county surveyor because he lacked substantive background in surveying; the Board applies the same reasoning to conclude Engineer B lacks competence to design structural footings.

Relevant Excerpts
discussion: "More recently, in BER Case 85-3, a local county ordinance required that the position of county surveyor be filled by a P.E."
discussion: "As the Board noted in BER Case 85-3, obviously, there are important distinctions in applying the Code language to a consulting practice and applying the language in the context of an employment relationship."
discussion: "In contrast, in BER Case 85-3, the county surveyor's responsibilities did not include actual preparation or approval of engineering or surveying documents; however, the job responsibilities did include oversight of surveying reports and highway improvements."
discussion: "Nevertheless, The Board concluded in BER Case 85-3 that at a bare minimum, one who is serving in the role as a county surveyor must have at least some substantive degree of background and experience in order to accept such a position."
discussion: "In the present case, we follow the same reasoning and conclude that there is at least a reasonable basis for Engineer A to conclude that Engineer B does not possess the competence to perform the required task."

Principle Established:

Engineers have an ethical obligation to seek work only in areas where they possess educational background and experience, or to retain individuals with the necessary qualifications.

Citation Context:

Cited to reaffirm the principle from BER Case 71-2 that engineers must seek work only within their competence or retain qualified individuals, in the context of a firm altering its qualifications to secure a contract.

Relevant Excerpts
discussion: "Likewise, BER Case 78-5, involved an effort by a consulting firm under consideration to perform services to a public utility in which the firm sought to alter its qualifications following its interview with the public utility in order to improve its position to secure the contract."

Principle Established:

A prime professional is expected to retain or recommend the retention of experts and specialists in situations where substantial services are being performed, recognizing the value of specialists on a project.

Citation Context:

Cited to establish the principle that a prime professional should retain or recommend experts and specialists when performing substantial services on a project, and that engineers have an ethical obligation to work only in areas of their competence or retain those who do.

Relevant Excerpts
discussion: "In BER Case 71-2, a case involving the brokerage of engineering services by two firms competing for government work and the question of competence."
discussion: "The Board affirmed its decision rendered in BER Case 71-2 that in the field of consulting practice, engineers have an ethical obligation to seek work only in areas where they possess educational background and experience or to retain individuals who possess the necessary educational background and experience to perform the work."
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 56% Facts Similarity 46% Discussion Similarity 89% Provision Overlap 100% Outcome Alignment 100% Tag Overlap 60%
Shared provisions: II.2, II.2.a, II.2.b, II.2.c Same outcome unethical View Synthesis
Component Similarity 55% Facts Similarity 58% Discussion Similarity 67% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 60% Principle Overlap 62%
Shared provisions: II.2.a, II.2.b Same outcome unethical View Synthesis
Component Similarity 54% Facts Similarity 67% Discussion Similarity 52% Provision Overlap 75% Outcome Alignment 100% Tag Overlap 60%
Shared provisions: II.2.a, II.2.b, II.2.c Same outcome unethical View Synthesis
Component Similarity 62% Facts Similarity 57% Discussion Similarity 59% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 50% Principle Overlap 58%
Shared provisions: II.2 Same outcome unethical View Synthesis
Component Similarity 60% Facts Similarity 52% Discussion Similarity 55% Provision Overlap 12% Outcome Alignment 100% Tag Overlap 29% Principle Overlap 66%
Shared provisions: II.2 Same outcome unethical View Synthesis
Component Similarity 56% Facts Similarity 56% Discussion Similarity 58% Provision Overlap 20% Outcome Alignment 100% Tag Overlap 25% Principle Overlap 61%
Shared provisions: II.2.b Same outcome unethical View Synthesis
Component Similarity 61% Facts Similarity 65% Discussion Similarity 52% Provision Overlap 10% Outcome Alignment 100% Tag Overlap 20% Principle Overlap 59%
Shared provisions: II.2 Same outcome unethical View Synthesis
Component Similarity 54% Facts Similarity 59% Discussion Similarity 57% Outcome Alignment 100% Tag Overlap 50% Principle Overlap 60%
Same outcome unethical View Synthesis
Component Similarity 60% Facts Similarity 65% Discussion Similarity 60% Outcome Alignment 100% Tag Overlap 33% Principle Overlap 50%
Same outcome unethical View Synthesis
Component Similarity 55% Facts Similarity 54% Discussion Similarity 57% Outcome Alignment 100% Tag Overlap 22% Principle Overlap 62%
Same outcome unethical View Synthesis
Questions & Conclusions (2 board)
View Extraction
Board Board question 1

Would it be ethical for Engineer B to perform the design of the structural footings as part of the facility?

Board conclusion It would be unethical for Engineer B to perform the design of the structural footings as part of the facility.
Resolved by: The Board weighed the contractor's practical interest in retaining a single engineer for discrete tasks against the structural safety demands of footing design and found the competence requirement controlling. (confidence 0.85)
II.2. II.2.a. II.2.b. 2 principles 3 facts Conditions Narrative
Implicit (1)

Does Engineer B bear an independent ethical obligation to self-assess and decline the footing design assignment regardless of whether Engineer A ever raises concerns?

AnalyticalThe Board's conclusion implicitly places the primary duty of self-restraint on Engineer B himself, independent of Engineer A's intervention. Even if Engineer A had never raised concerns or reported them to the contractor, Engineer B would still bear an unmet obligation under II.2.a to decline an assignment outside his demonstrated competence. This means the ethical violation in Conclusion 1 exists prior to and independent of the reporting behavior addressed in Conclusion 2, making Engineer B's culpability the primary and freestanding issue, while Engineer A's conduct is a secondary, contingent question.
Resolved by: The Board prioritized Engineer B's freestanding duty of self-assessment over any dependency on Engineer A's conduct, treating the two engineers' obligations as separable rather than mutually conditioning. (confidence 0.70)
II.2. II.2.a. 2 principles 3 facts Conditions Narrative
AnalyticalIn response to Q102, Engineer B bears an independent, non-delegable ethical obligation under the Engineer B Footing Competence Duty to self-assess his own qualifications before accepting the footing design assignment. This obligation exists irrespective of whether Engineer A or anyone else raises concerns; the Code's competence provisions (II.2. and II.2.a.) place the primary duty of self-restraint on the engineer performing the work, not solely on third parties who might detect the deficiency.
Resolved by: The board weighed the possibility that third-party detection (by Engineer A or others) might substitute for self-restraint against the Code's placement of the competence duty primarily on the performing engineer, and concluded the latter controls. (confidence 0.85)
II.2. II.2.a. 2 principles 3 facts Conditions Narrative
Principle tension (1)

Does the contractor's practical interest in efficiently retaining specialists for discrete tasks (Specialist Retention Infeasible for Footings) conflict with the Competence Concern in Footing Design that demands rigorous qualification matching for structural safety work?

AnalyticalThe contractor's practical interest in efficiently retaining a specialist for a discrete task (reflected in Specialist Retention Infeasible for Footings) does not diminish or dilute the Competence Concern in Footing Design; the Board's reasoning implies that convenience-based staffing decisions in design/build arrangements cannot substitute for verified qualification matching when structural safety is at stake. Practical project-management considerations are subordinate to the core competence principle whenever public safety is implicated.
Resolved by: The contractor's convenience-driven staffing rationale was weighed against public-safety-grounded competence requirements and found insufficient to override them. (confidence 0.78)
II.2. II.2.a. 2 principles 3 facts Conditions Narrative
Also discussed in: C303
Theoretical (2)

From a deontological perspective, did Engineer B violate a duty of competence by accepting an assignment to design structural footings despite lacking demonstrated training in foundation engineering?

AnalyticalIn response to Q301, from a deontological perspective Engineer B violated a clear duty of competence by accepting the footing design assignment without demonstrated qualifications in foundation engineering. NSPE Code provisions II.2. and II.2.a. establish a categorical duty—not a consequence-dependent one—that engineers undertake assignments only within their area of competence; Engineer B's chemical engineering background and lack of subsequent training in foundation design place this assignment outside that duty's bounds regardless of whether harm ultimately resulted.
Resolved by: The board treated the competence duty as categorical rather than consequence-dependent, so no weighing against potential benefits or absence of harm was permitted to excuse the acceptance of the assignment. (confidence 0.85)
II.2. II.2.a. 2 principles 3 facts Conditions Narrative

Did Engineer B act with professional integrity, in the virtue-ethical sense, by accepting a structural footing design assignment outside a chemical engineering background without first disclosing the limits of his qualifications to the contractor?

AnalyticalIn response to Q303, viewed through a virtue-ethics lens, Engineer B failed to exhibit professional integrity by accepting the footing design assignment without first disclosing the limits of his chemical engineering background to the contractor. A virtuous engineer, oriented toward honesty and prudence, would have proactively disclosed the mismatch between his training and the assignment rather than allowing the contractor to assume competence that was never established.
Resolved by: The board weighed B's interest in securing the assignment against the virtue-based duty of honest self-disclosure, and found the latter controlling because accepting work silently let the contractor assume competence that was never established. (confidence 0.78)
II.2. II.2.a. 3 principles 3 facts Conditions Narrative
Counterfactual (2)

If Engineer B had in fact possessed subsequent formal training or certification in foundation design beyond his chemical engineering degree, would the Board still have concluded it was unethical for him to perform the footing design?

AnalyticalIn response to the counterfactual Q401, if Engineer B had possessed documented subsequent formal training or certification specifically in foundation design, the Board's conclusion would likely differ, since the Code's competence standard (II.2.a.) turns on demonstrated qualification by education or experience rather than on the engineer's original degree discipline alone. The unethical nature of the assignment in the actual case stems specifically from the Qualification Verification Failure and absence of any evidence of relevant training, not from the chemical engineering degree per se.
Resolved by: The board weighed the formalistic view (degree discipline determines competence) against the substantive Code standard (demonstrated qualification by education or experience), favoring the substantive standard. (confidence 0.80)
II.2.a. 3 principles 3 facts Conditions Narrative

If the construction contractor, rather than separately retaining Engineer B, had asked Engineer A to coordinate and approve the footing design as part of the overall design/build project, would the Board's conclusion about the unethical nature of Engineer B's independent retention still apply?

AnalyticalIn response to the counterfactual Q403, if the contractor had instead asked Engineer A to coordinate and approve Engineer B's footing design as part of an integrated design/build responsibility, the analysis would shift toward Code provision II.2.c., which permits an engineer to coordinate an entire project provided that each component is designed by a qualified specialist under appropriate signature and seal. In that scenario, Engineer A's approval role would create a more direct oversight duty, potentially making Engineer A more clearly accountable for verifying Engineer B's competence before allowing the design to proceed.
Resolved by: The board weighed Engineer A's peer autonomy against a heightened oversight duty created by an explicit coordination/approval role, finding the latter would dominate once such authority existed. (confidence 0.77)
II.2.c. 3 principles 3 facts Conditions Narrative
Also discussed in: C103
Board Board question 2

Did Engineer A have an ethical responsibility to question Engineer B's competency and report his concerns to the contractor?

Board conclusion Engineer A has an ethical responsibility to question Engineer B's competency and report his concerns to the contractor.
Resolved by: The Board balanced deference to a peer's professional autonomy against the public safety obligation to flag a visible competence gap, and found the reporting duty outweighed collegial restraint. (confidence 0.85)
II.2. II.2.a. III.2.b. 3 principles 3 facts Conditions Narrative
Implicit (2)

Once Engineer A reported concerns to the contractor, what further obligations, if any, does Engineer A have if the contractor ignores those concerns and proceeds to have Engineer B design the footings anyway?

AnalyticalThe Board's treatment of Engineer A's duty to question and report suggests a bounded obligation: Engineer A's ethical responsibility is satisfied by raising the concern to the party with authority to act (the contractor), and does not necessarily extend to policing the contractor's subsequent decision, verifying Engineer B's credentials independently, or refusing further cooperation on the project if the contractor disregards the warning. This reading leaves open whether Engineer A's duty is discharged entirely upon reporting, or whether continued participation in a project using an unqualified footing design would itself implicate Engineer A in a downstream ethical or public-safety failure under III.2.b if Engineer A is asked to coordinate or rely upon that design.
Resolved by: The Board weighed a broad ongoing policing duty against a narrower reporting-discharge duty and left the matter partly open, favoring the narrower reading while flagging potential re-engagement under III.2.b. (confidence 0.65)
II.2.c. III.2.b. 2 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101, once Engineer A has fulfilled the Engineer A Competence Concern Report by notifying the contractor, if the contractor disregards the concern and proceeds with Engineer B's design, Engineer A's obligations escalate under the Engineer A Client and Authority Reporting Duty. Because public safety is implicated by potentially inadequate structural footings, Engineer A cannot treat the initial report as discharging all ethical responsibility; further action may include escalating concerns to a state licensing board or other authority, consistent with the profession's paramount duty to protect public safety.
Resolved by: The board weighed Engineer A's interest in respecting the contractor's authority over hiring decisions against the paramount obligation to protect public safety, and found the latter controlling once initial reporting proved ineffective. (confidence 0.82)
2 principles 3 facts Conditions Narrative

Should Engineer A have gone beyond reporting concerns to actively investigate or verify Engineer B's credentials before forming a conclusion about his competence?

AnalyticalThe Board's finding that Engineer B's performance of the footing design would be unethical rests on a per se competence mismatch: a chemical engineering background does not, absent demonstrated subsequent training, establish qualification under II.2.a for structural foundation work. This suggests the Board's standard is not merely subjective doubt (as held by Engineer A) but an objective evidentiary gap—the absence of any established credential in foundation design is itself sufficient to trigger the ethical violation, independent of whether the resulting footing design would actually be deficient in practice.
Resolved by: The Board weighed a subjective-doubt standard against an objective evidentiary standard and adopted the objective standard, treating the credential gap itself as dispositive regardless of actual outcome quality. (confidence 0.75)
II.2.a. 2 principles 3 facts Conditions Narrative
Principle tension (1)

How should the principle of respecting professional autonomy and inter-firm boundaries be balanced against the Competence Concern in Footing Design when Engineer A, who is not Engineer B's supervisor, raises concerns about a peer's qualifications?

AnalyticalThe tension between respecting Engineer B's professional autonomy as an independently retained peer and the Competence Concern in Footing Design is resolved in favor of competence: an engineer's freedom to accept work from a client is not absolute but is bounded by the Code's competence requirements, so Engineer A's peer status did not excuse silence in the face of a credible competence gap. This shows that competence verification duties can override normal professional deference between engineers who are not in a supervisory relationship.
Resolved by: Professional autonomy and collegial non-interference were treated as real but subordinate interests, yielding to the Code's competence mandate once a credible qualification gap was identified. (confidence 0.82)
II.2. II.2.a. 3 principles 3 facts Conditions Narrative
AnalyticalTaken together, the case illustrates a general prioritization rule within the NSPE Code: competence-related obligations (II.2 and II.2.a) function as threshold constraints that take precedence over relational or operational principles such as collegial non-interference or contractor efficiency. Once a competence gap is identified, it activates downstream reporting duties (Engineer A Competence Concern Report) regardless of countervailing interests, indicating that public safety concerns embedded in competence provisions are treated as near-absolute rather than balanced case-by-case against convenience or autonomy interests.
Resolved by: The Board treated competence provisions as threshold constraints that automatically activate reporting duties, effectively foreclosing case-by-case balancing against collegiality or efficiency once a competence gap is recognized. (confidence 0.75)
II.2. II.2.a. III.2.b. 3 principles 3 facts Conditions Narrative
Theoretical (2)

From a consequentialist standpoint, did the potential public safety risk from an unqualified footing design justify Engineer A's decision to intervene by reporting concerns to the contractor, even absent certainty of actual harm?

AnalyticalRegarding Q302, from a consequentialist standpoint, Engineer A's decision to report concerns to the contractor was justified by the magnitude of potential harm from a structurally deficient footing design, even without certainty that Engineer B's work would in fact fail. Given that structural footings are safety-critical elements whose failure could endanger the public, the expected disutility of remaining silent outweighed the social costs of raising a peer's competence concerns, supporting Engineer A's intervention as ethically warranted.
Resolved by: The board weighed the social cost of raising a peer's competence concern (potential reputational harm, collegial friction) against the magnitude of potential harm from a structurally deficient footing design, concluding the latter outweighed the former. (confidence 0.80)
2 principles 3 facts Conditions Narrative

From a deontological perspective, did Engineer A fulfill an obligation of professional solidarity and public protection by questioning a peer's competence rather than remaining silent out of collegial deference?

AnalyticalAddressing Q304, from a deontological standpoint Engineer A fulfilled a duty that prioritizes public protection over collegial deference. The obligation to question a peer's competence, captured in the Engineer A Peer Confrontation Duty, reflects the Code's hierarchy of duties in which safeguarding public safety and welfare takes precedence over professional courtesy or reluctance to criticize a fellow engineer.
Resolved by: The board balanced the norm of collegial courtesy against the deontological duty to protect the public, concluding that public safety obligations override reluctance to criticize a peer. (confidence 0.75)
3 principles 3 facts Conditions Narrative
Counterfactual (1)

If Engineer A had not been able to confirm his own reservations about Engineer B's competence and instead had no doubts at all, would the Board still have found Engineer A ethically obligated to question Engineer B's competency and report concerns to the contractor?

AnalyticalRegarding the counterfactual Q402, even if Engineer A had harbored no personal doubts about Engineer B's competence, the Board would likely still find an ethical responsibility to investigate given the objective absence of verifiable qualifications (Qualification Verification Failure) and the safety-critical nature of structural footing design. The duty to question competence in such circumstances arises from the objective competence gap and role-based responsibility for project integrity, not merely from Engineer A's subjective reservations.
Resolved by: The board weighed subjective certainty against objective risk, concluding that the duty to investigate arises from the objective absence of verified qualifications rather than from Engineer A's personal suspicions. (confidence 0.75)
II.2. II.2.a. 3 principles 3 facts Conditions Narrative
Analytical questions (1)

Questions the analysis generates beyond the board’s explicit questions: implicit issues, principle tensions, theoretical framings, and counterfactuals. A question with an identified source board question appears nested under that question above.

Implicit (1)

What responsibility does the construction contractor bear for retaining Engineer B without verifying his qualifications in foundation design, given that the contractor controls the design/build process?

AnalyticalAddressing Q103, the construction contractor, as the party controlling the design/build process and the Specialist Retention Decision, bears a practical if not strictly codified ethical responsibility to exercise due diligence when retaining specialists such as Engineer B for safety-critical work like structural footing design. The contractor's failure to verify Engineer B's qualifications contributed to the Qualification Verification Failure and created the conditions for the competence gap identified in the case.
Resolved by: The board weighed the contractor's practical interest in efficiently retaining specialists against the need for rigorous qualification verification on safety-critical tasks, finding the contractor bears a practical, though not strictly codified, responsibility to verify qualifications. (confidence 0.75)
2 principles 3 facts Conditions Narrative
Decisions & Arguments (5)
View Extraction

Should Engineer B accept the assignment to design the structural footings given his lack of demonstrated qualification in foundation engineering?

Options considered:
O1 Engineer B accepts the contractor's assignment to design the structural footings despite his chemical engineering background and absence of demonstrated foundation design training.
O2 Engineer B declines the footing design assignment and recommends the contractor retain an engineer with demonstrated qualifications in foundation or structural engineering. Board's choice
Argument structure (Toulmin):
Grounds

Engineer B holds a chemical engineering background and has no established credential or subsequent training in foundation or structural engineering, yet was retained by the contractor to design structural footings.

Warrant

Engineers must undertake assignments only when qualified by education or experience, and must perform services only in their area of competence; this competence duty is categorical and does not depend on whether harm actually results.

Rebuttal

Would not apply if Engineer B had in fact obtained demonstrated subsequent training or experience in foundation design, or if the assignment were closely supervised and reviewed by a qualified structural engineer.

Undertake Assignments Only When Qualified by Education or Experience; Perform Services Only in Areas of Competence

Should Engineer A report his concerns about Engineer B's competency to the contractor?

Options considered:
O1 Engineer A raises his concerns about Engineer B's qualifications in foundation design directly with the contractor who controls the design/build process. Board's choice
O2 Engineer A refrains from raising the issue, treating Engineer B's qualifications as outside his purview since he is not Engineer B's supervisor.
Argument structure (Toulmin):
Grounds

Engineer A observed that Engineer B, a chemical engineer, was assigned to design safety-critical structural footings without demonstrated foundation design qualifications, and Engineer A was not Engineer B's supervisor but was aware of the assignment.

Warrant

Engineers must bring competence concerns to the attention of the client when public safety may be implicated, and this duty to protect the public can outweigh norms of professional deference between peer engineers who lack supervisory authority.

Rebuttal

Would not apply if Engineer A had no genuine basis for doubting Engineer B's qualifications, or if Engineer B's competence had already been independently verified by a qualified authority.

Obligation to Bring Competence Concerns to the Attention of the Client

Must Engineer A take further action, such as escalating to a licensing authority, if the contractor ignores his reported concerns and proceeds with Engineer B's design?

Options considered:
O1 Engineer A goes beyond his initial report and escalates the unresolved competence concern to a state licensing board or other appropriate authority given the public safety implications. Board's choice
O2 Engineer A considers his ethical obligation satisfied once he has reported to the contractor and takes no further action even though the contractor disregards the warning.
Argument structure (Toulmin):
Grounds

Engineer A reported his concerns about Engineer B's qualifications to the contractor, but the contractor disregarded the warning and continued to have Engineer B design the safety-critical footings.

Warrant

Engineers must hold paramount the safety of the public, and when reporting to a client or employer fails to resolve a threat to public safety, engineers must notify such other authority as may be appropriate.

Rebuttal

Would not apply if the contractor's disregard of the concern were later shown to rest on independent verification of Engineer B's qualifications, or if the footing design posed no genuine risk to public safety.

Client and Authority Reporting Duty

Should the construction contractor verify Engineer B's qualifications before retaining him to design the structural footings?

Options considered:
O1 The contractor conducts due diligence to confirm Engineer B's education, training, and experience in foundation design before assigning him the footing work. Board's choice
O2 The contractor retains Engineer B for the footing design based on convenience and prior working relationship, without confirming his qualifications in foundation engineering.
Argument structure (Toulmin):
Grounds

The contractor controlled the design/build process and retained Engineer B, a specialist with a chemical engineering background, for structural footing design without confirming his qualifications in that specific field.

Warrant

Parties controlling the assignment of safety-critical engineering work bear a practical responsibility to ensure that retained specialists possess demonstrated competence in the relevant technical field, given the paramount importance of public safety in structural work.

Rebuttal

Would not apply if the contractor reasonably relied on Engineer B's own representations of competence or on an established credentialing process that appeared to confirm his qualifications.

Due Diligence in Specialist Retention for Safety-Critical Work

Should Engineer A independently investigate or verify Engineer B's credentials before forming a conclusion about his competence, or is reporting the concern to the contractor sufficient?

Options considered:
O1 Engineer A raises his concern to the contractor based on his professional judgment, without independently investigating or verifying Engineer B's credentials himself. Board's choice
O2 Engineer A undertakes his own investigation of Engineer B's education and training records before deciding whether to raise or how to frame the concern.
Argument structure (Toulmin):
Grounds

Engineer A was not Engineer B's supervisor and had no formal access to Engineer B's education or training records, but he possessed sufficient professional judgment to identify a plausible competence gap and reported it to the contractor.

Warrant

Engineers must bring competence concerns to the attention of the client or other authority with power to act, but the Code does not impose an independent verification or investigative duty on a peer engineer lacking authority over another engineer's assignment.

Rebuttal

Would not apply if Engineer A had ready access to Engineer B's credentials or specialized authority to compel disclosure, in which case declining to verify before reporting could itself be a lapse.

Peer Confrontation Duty; Bounded Reporting Obligation
Event Timeline (6)
6 sequenced 4 actions 2 events
Case timeline
During construction, the contractor separately retained Engineer B, whose degree and background are in chemical engineering, to design structural footings for the industrial facility.
Causal-normative reasoning(confidence 0.70)
The Construction Contractor's decision to retain a specialist sets the causal chain in motion, leading directly to Engineer B's acceptance of the assignment, so although it carries no normative commitments itself, its significance lies in creating the conditions under which competence obligations become relevant.
State changes (1)
  • began: Sole Purpose Footing Retention
Engineer B accepted the assignment to design structural footings despite having education and background solely in chemical engineering, with no apparent training in foundation design.
Violates (2)
  • Undertake Assignments Only When Qualified by Education or Experience
  • Perform Services Only in Areas of Competence
Causal-normative reasoning(confidence 0.85)
Engineer B's acceptance of the assignment violates the duty to undertake work only when qualified and to perform services only within one's area of competence, and because this acceptance causally triggers the subsequent qualification investigation, the violation matters as the root failure that necessitates later scrutiny of B's credentials.
Engineer A attempted to establish whether Engineer B had any subsequent training in foundation design and was unable to do so, forming reservations about Engineer B's competence.
Fulfills (1)
  • Objectively Determine Whether Engineer B Has Sufficient Education, Experience and Training
Causal-normative reasoning(confidence 0.80)
The qualification investigation fulfills the obligation to objectively determine whether Engineer B has sufficient education, experience and training, and is guided by the competence standard, yet because it causally leads to a verification failure, its normative value is undermined by the outcome it produces, showing that even a proper process can expose an underlying competence gap.
State changes (1)
  • began: Engineer A Reservations About B
Engineer A's investigation fails to establish that Engineer B has any subsequent training in foundation design beyond a chemical engineering degree and background.
Engineer A develops reservations concerning Engineer B's competence to design the structural footings, a concern that grounds his subsequent reporting to the contractor and the duties the Board discusses.
Engineer A reported his reservations about Engineer B's competence to design the structural footings to the construction contractor.
Fulfills (1)
  • Obligation to Bring Competence Concerns to the Attention of the Client
Causal-normative reasoning(confidence 0.85)
Engineer A's concern reporting fulfills the obligation to bring competence concerns to the client's attention and is guided by the competence-based standard, and because it causally follows from the qualification verification failure and the resulting competence concern, it represents the corrective mechanism that addresses the earlier violation in the causal chain.
State changes (1)
  • began: Concerns Reported To 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 professional engineer retained by a construction contractor on a design/build project to construct an industrial facility. During construction, the contractor separately retains Engineer B, another professional engineer, to design the structural footings for the facility. Engineer B holds a degree and professional background in chemical engineering, and you have been unable to find any evidence that Engineer B has subsequent training or experience in foundation design. Based on this gap, you have formed reservations about whether Engineer B is competent to perform the structural footing design, and you have reported these concerns directly to the contractor. The contractor has not yet indicated how, or whether, it will act on your report. In the days ahead, you will need to decide how to proceed regarding Engineer B's assignment, your own responsibilities in raising and pursuing this matter, and what further steps, if any, the situation requires of you.

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

Guided by: Competence Concern in Footing Design

Engineer A faces a choice between first raising competence concerns directly with Engineer B as a matter of professional courtesy and collegial process, versus escalating immediately to the client and relevant authorities given the potential public safety implications of a deficient footing design. Prioritizing peer confrontation risks delay if Engineer B is uncooperative or dismissive, while immediate escalation risks bypassing due process and damaging professional relationships if the concern turns out to be unfounded.

If Engineer A's concerns are not resolved, there is an obligation to consider withdrawing from further association with the project, but withdrawal could remove Engineer A from a position to continue monitoring the situation and ensure the client and authorities remain properly informed. Staying engaged enough to fulfill reporting duties may conflict with the professional imperative to disengage from a project where competence concerns remain unaddressed.

Engineer B Roles in this case: Footing Design EngineerConsultant to Contractor

Engineer B is obligated to perform footing design competently, yet the competence boundary constraint suggests Engineer B may be operating at or beyond the edge of demonstrated expertise, particularly in the consultant role for the contractor. This creates tension between the duty to deliver a technically sound design and the practical limitation of possibly lacking sufficient specialized qualification for this specific geotechnical or structural challenge.

Attaches to role: Footing Design Engineer

Engineer A faces a choice between first raising competence concerns directly with Engineer B as a matter of professional courtesy and collegial process, versus escalating immediately to the client and relevant authorities given the potential public safety implications of a deficient footing design. Prioritizing peer confrontation risks delay if Engineer B is uncooperative or dismissive, while immediate escalation risks bypassing due process and damaging professional relationships if the concern turns out to be unfounded.

Attaches to role: Footing Design Engineer

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

Engineer B is obligated to perform footing design competently, yet the competence boundary constraint suggests Engineer B may be operating at or beyond the edge of demonstrated expertise, particularly in the consultant role for the contractor. This creates tension between the duty to deliver a technically sound design and the practical limitation of possibly lacking sufficient specialized qualification for this specific geotechnical or structural challenge.

Engineer A faces a choice between first raising competence concerns directly with Engineer B as a matter of professional courtesy and collegial process, versus escalating immediately to the client and relevant authorities given the potential public safety implications of a deficient footing design. Prioritizing peer confrontation risks delay if Engineer B is uncooperative or dismissive, while immediate escalation risks bypassing due process and damaging professional relationships if the concern turns out to be unfounded.

If Engineer A's concerns are not resolved, there is an obligation to consider withdrawing from further association with the project, but withdrawal could remove Engineer A from a position to continue monitoring the situation and ensure the client and authorities remain properly informed. Staying engaged enough to fulfill reporting duties may conflict with the professional imperative to disengage from a project where competence concerns remain unaddressed.

The Board’s deliberation

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

It would be unethical for Engineer B to perform the design of the structural footings as part of the facility.
Engineer A has an ethical responsibility to question Engineer B's competency and report his concerns to the contractor.
Opening States (5)
Engineer B Foundation Competence Gap Sole Purpose Footing Retention Engineer A Reservations About B Concerns Reported To Contractor Specialist Retention Infeasible for Footings
Summary
  • When public safety is potentially at risk due to a colleague's competence gap, the duty to protect the public can outweigh the norm of raising concerns privately with the peer first.
  • Engineers who accept work as consultants must have genuine demonstrated expertise in the specific technical area, such as footing design, rather than relying on general engineering credentials.
  • The obligation to withdraw from a project when competence concerns go unresolved exists in tension with the practical need to remain informed enough to alert the client or authorities if problems persist.

© Licensed under the GNU GPL v3