Step 4: Full View

Entities, provisions, decisions, and narrative

Competence To Perform Foundation Design
Step 4 of 5

266

Entities

5

Provisions

3

Precedents

18

Questions

26

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
A cascading multi-stage Transfer in which the primary ethical obligation to prevent an incompetent structural footing assignment originates with Engineer B (self-assessment and proactive disclosure duty), transfers to Engineer A upon Engineer B's failure to self-police (peer competence challenge and reporting obligation), transfers to the contractor upon Engineer A's notification (corrective action duty), and transfers finally to the state licensing board if the contractor fails to act — with each stage representing a clean handoff rather than a persistent shared tension or cyclical return of 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
II.2. Engineers shall perform services only in the areas of their competence.
How this applies in the case (showing 3 of 47)
Obligation
BER 85-3 County Surveyor Chemical Engineer Institutional Role Non-Expansion of Competence Obligation
The provision directly requires engineers to perform services only in areas of competence, which the county surveyor chemical engineer violated by assuming structural duties beyond their discipline.
Action
Engineer B Accepts Structural Assignment
This provision directly governs whether Engineer B should accept the assignment based on whether structural work falls within his competence.
State
Engineer B Chemical Engineer Structural Footing Assignment Incompetence
Engineer B is performing structural footing design services outside the area of chemical engineering competence.
Obligation (4)
  • BER 85-3 County Surveyor Chemical Engineer Institutional Role Non-Expansion of Competence Obligation
    The provision directly requires engineers to perform services only in areas of competence, which the county surveyor chemical engineer violated by assuming structural duties beyond their discipline.
  • Engineer B Cross-Discipline Structural Footing Assignment Acceptance Refusal Obligation
    The provision directly obligates Engineer B to refuse the structural footing assignment because it falls outside the area of competence established by a chemical engineering background.
  • Engineer B Domain-Specific Competence Verification Before Structural Footing Acceptance Obligation
    The provision requires engineers to limit services to areas of competence, directly grounding the obligation to verify domain-specific competence before accepting the structural footing assignment.
  • Engineering Firm Consulting Practice Subconsultant Engagement for Competence Gap Obligation
    The provision requires firms to perform services only within areas of competence, directly supporting the obligation to engage qualified subconsultants when a competence gap exists.
Action (2)
  • Engineer B Accepts Structural Assignment
    This provision directly governs whether Engineer B should accept the assignment based on whether structural work falls within his competence.
  • Engineer B Decides Whether to Withdraw
    This provision requires Engineer B to withdraw if he determines the structural assignment is outside his area of competence.
State (5)
  • Engineer B Chemical Engineer Structural Footing Assignment Incompetence
    Engineer B is performing structural footing design services outside the area of chemical engineering competence.
  • Engineer B Outside Area of Competence for Structural Footing Design
    This provision directly prohibits performing services outside one's competence, which is Engineer B's situation.
  • Engineer B Domain-Specific Incompetence in Structural Engineering
    Engineer B's lack of structural engineering competence directly violates the requirement to perform services only in areas of competence.
  • Public Safety at Risk from Incompetent Structural Footing Design
    The competence requirement exists to protect public safety, which is at risk when an unqualified engineer designs structural footings.
  • Consulting Context Competence Remediation Flexibility. General Principle
    The provision applies universally to competence requirements and forms the basis for distinguishing consulting versus employment contexts.
Constraint (11)
  • Engineer B General PE Licensure Non-Authorization for Structural Footing Design
    II.2 requires engineers to perform services only in areas of competence, directly creating the constraint that a general PE license does not authorize structural footing practice outside one's competence area.
  • Engineer B Education-Experience Competence Threshold Structural Footing Design
    II.2 establishes the competence standard that Engineer B fails to meet due to lacking relevant education and experience in structural footing design.
  • Engineer B Chemical Engineering Background Structural Footing Assignment Competence Boundary
    II.2 directly prohibits Engineer B from accepting the structural footing assignment given that chemical engineering background does not constitute competence in that domain.
  • Engineer B PE License Legal Minimum Ethics Code Higher Standard
    II.2 imposes an ethical competence standard higher than mere licensure, creating the constraint that a valid PE license alone is insufficient authorization.
  • Engineer B General PE License Non-Authorization for Structural Footing Practice
    II.2 is the provision that makes a general PE license insufficient when the engineer lacks competence in the specific technical field involved.
  • Engineer B Public Safety Paramount Structural Footing Incompetence
    II.2 underpins the prohibition on continuing work outside one's competence, which directly implicates public safety risk from incompetent structural footing design.
  • Public Safety at Risk from Engineer B Incompetent Structural Footing Design. Safety Constraint
    II.2 creates the foundational competence obligation whose violation generates the public safety constraint on Engineer B's structural footing work.
  • Consulting Firm Workforce Restructuring Permissibility. General Principle
    II.2 is the competence provision that consulting firms must satisfy, permitting remediation through subcontracting as an acceptable path to compliance.
  • Consulting vs. Employment Competence Flexibility Differential. BER Case 94-8 Application
    II.2 is the competence requirement whose satisfaction differs between consulting and sole-purpose retention contexts, creating the flexibility differential constraint.
  • Engineer B Sole-Purpose Structural Footing Sub-Delegation Circular Nullification
    II.2 requires competence for the services performed, and Engineer B's sole-purpose retention makes sub-delegation a nullification of the engagement rather than a remedy.
  • Engineer B Sole-Purpose Engagement Competence Delegation Non-Availability
    II.2 requires competence for services performed, and the sole-purpose retention structure eliminates the delegation flexibility that would otherwise allow compliance.
Principle (7)
  • Universal Competence Scope Limitation Invoked Against Engineer B Structural Footing Assignment
    This provision directly limits engineers to areas of competence, which Engineer B violated by accepting structural footing work outside chemical engineering expertise.
  • Universal Engineer Competence Scope Limitation Invoked Against Engineer B Chemical-to-Structural Practice
    This provision is the direct code basis for restricting Engineer B from practicing outside the chemical engineering field in which they were trained.
  • Employer and Client Pressure Non-Exemption from Competence Boundary Applied to Engineer B
    This provision establishes the competence boundary that applies regardless of contractor requests or pressure on Engineer B.
  • Ethics Code as Higher Standard Than Legal Minimum Applied to Engineer B PE Licensure Defense
    This provision sets an ethical competence standard that exceeds mere PE licensure, rejecting the defense that a license alone satisfies the obligation.
  • Institutional Role Non-Expansion of Technical Competence Scope Applied via BER 85-3 Analogy
    This provision underlies the principle that institutional roles or licenses do not expand an engineer's technical competence scope.
  • Degree-to-Task Alignment Verification Obligation Implicated in Contractor Retention of Engineer B
    This provision implies that competence must align with the specific task, which the contractor failed to verify when retaining Engineer B.
  • Degree-to-Task Alignment Verification Obligation Applied to Contractor Retention of Engineer B
    This provision requires competence in the specific area of service, directly implicating the contractor's failure to verify Engineer B's qualifications.
Role (2)
  • Engineer B Cross-Discipline Out-of-Competence Structural Design Engineer
    Engineer B is performing structural footing design outside his chemical engineering competence, directly violating the requirement to perform services only in areas of competence.
  • BER 85-3 County Surveyor Out-of-Competence Public Sector Appointee Engineer
    The county surveyor accepted a position requiring oversight outside his chemical engineering background, violating the requirement to perform services only in areas of competence.
Event (2)
  • Engineer B's Lack of Qualifications Confirmed
    This provision directly addresses the requirement to perform services only in areas of competence, which is violated when Engineer B's lack of qualifications is confirmed.
  • Project Construction Commences
    Construction proceeding despite competence concerns reflects a failure to ensure services are performed only within areas of competence.
Resource (6)
  • Professional-Competence-Standard-Structural-Footing-Design
    This provision directly establishes the competence standard that Engineer B violates by designing structural footings outside his chemical engineering background.
  • NSPE-Code-of-Ethics-Professional-Competence
    This resource directly governs the obligation under II.2 that engineers practice only within their areas of competence.
  • NSPE Code of Ethics Section II.2
    This resource is the direct codification of provision II.2 establishing the overarching competence obligation.
  • NSPE Code of Ethics – Professional Competence Standard
    This resource grounds the ethical obligation for engineers to practice only within areas of demonstrated competence as required by II.2.
  • BER Case 71-2
    This case established the ethical obligation to seek work only in areas of possessed competence, directly supporting II.2.
  • BER Case 85-3
    This case applied the competence standard to a chemical engineer practicing outside their field, directly illustrating II.2.
Capability (8)
  • Engineer A Cross-Discipline Structural Footing Competence Boundary Recognition
    II.2 requires engineers to perform only within their competence areas, directly relating to recognizing discipline boundaries.
  • Engineer B Structural Footing Foundation Design Competence Deficit
    II.2 is violated when an engineer performs services outside their competence, as Engineer B did with structural footing design.
  • Engineer B Pre-Acceptance Structural Footing Competence Self-Assessment Deficit
    II.2 requires engineers to assess their competence before performing services, which Engineer B failed to do.
  • Engineer A Domain-Specific Competence Boundary Recognition for Structural Footing
    II.2 requires recognizing competence limits in specific technical fields, which Engineer A was obligated to apply.
  • Engineer B PE License Legal Minimum vs Ethics Code Higher Standard Self-Recognition
    II.2 sets an ethical standard for competence that exceeds the mere possession of a PE license.
  • Engineer B Irreconcilable Sole-Purpose Competence Gap Declination
    II.2 requires declining assignments outside one's competence, which Engineer B failed to do.
  • BER 85-3 County Surveyor Irreconcilable Competence Gap Declination
    II.2 requires performing services only within competence areas, illustrated by the county surveyor precedent.
  • Engineer A BER Three-Precedent Consulting-Employment Competence Flexibility Spectrum Synthesis
    II.2 governs the overall competence requirement that the three BER precedents collectively interpret.
II.2.a. 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 50)
Obligation
Engineer B Cross-Discipline Structural Footing Assignment Acceptance Refusal Obligation
This provision directly states engineers shall only undertake assignments when qualified by education or experience, obligating Engineer B to refuse a structural assignment given only a chemical engineering background.
Action
Contractor Retains Engineer B
This provision governs whether Engineer B is qualified by education or experience to be retained for the structural assignment.
State
Engineer B Chemical Engineer Structural Footing Assignment Incompetence
Engineer B undertook a structural footing assignment without qualifying education or experience in structural or foundation engineering.
Obligation (5)
  • Engineer B Cross-Discipline Structural Footing Assignment Acceptance Refusal Obligation
    This provision directly states engineers shall only undertake assignments when qualified by education or experience, obligating Engineer B to refuse a structural assignment given only a chemical engineering background.
  • Engineer B Domain-Specific Competence Verification Before Structural Footing Acceptance Obligation
    This provision directly requires qualification by education or experience in the specific technical field before undertaking an assignment, grounding the verification obligation before acceptance.
  • BER 85-3 County Surveyor Chemical Engineer Institutional Role Non-Expansion of Competence Obligation
    This provision specifies that qualification by education or experience in the specific field is required, directly applying to the chemical engineer who lacked structural engineering qualifications.
  • Construction Contractor Degree-to-Task Alignment Verification Before Engineer B Retention Obligation
    This provision establishes that engineers must be qualified by education or experience for specific technical fields, informing the contractor's obligation to verify degree-to-task alignment before retention.
  • Engineer B PE License Non-Sufficiency Ethics Code Higher Standard Recognition Obligation
    This provision sets a higher standard than mere licensure by requiring qualification in the specific technical field involved, directly supporting the obligation to recognize that a PE license alone is insufficient.
Action (4)
  • Contractor Retains Engineer B
    This provision governs whether Engineer B is qualified by education or experience to be retained for the structural assignment.
  • Engineer B Accepts Structural Assignment
    This provision directly prohibits Engineer B from undertaking the structural assignment if he lacks the requisite education or experience.
  • Engineer A Investigates Engineer B's Qualifications
    Engineer A's investigation is aimed at determining whether Engineer B meets the qualification standard required by this provision.
  • Engineer B Decides Whether to Withdraw
    This provision obligates Engineer B to withdraw if he is not qualified by education or experience for the structural work.
State (5)
  • Engineer B Chemical Engineer Structural Footing Assignment Incompetence
    Engineer B undertook a structural footing assignment without qualifying education or experience in structural or foundation engineering.
  • Engineer B Outside Area of Competence for Structural Footing Design
    This provision directly requires qualification by education or experience before undertaking assignments, which Engineer B lacks for foundation design.
  • Engineer B Domain-Specific Incompetence in Structural Engineering
    Engineer B's chemical engineering background does not qualify them by education or experience for structural footing design assignments.
  • Engineer A Unverified Competence Concern About Engineer B
    Engineer A's concern stems from Engineer B's credential mismatch, which is precisely what this provision addresses regarding qualification requirements.
  • BER Case 85-3 Employment Context Competence Constraint. County Surveyor
    The county surveyor precedent similarly involved undertaking an assignment without qualifying credentials in the specific technical field.
Constraint (9)
  • Engineer B Education-Experience Competence Threshold Structural Footing Design
    II.2.a explicitly requires qualification by education or experience in the specific technical field, directly establishing the threshold Engineer B fails to meet.
  • Engineer B Chemical Engineering Background Structural Footing Assignment Competence Boundary
    II.2.a prohibits undertaking assignments without qualification by education or experience, directly constraining Engineer B from accepting the structural footing assignment.
  • Engineer B General PE Licensure Non-Authorization for Structural Footing Design
    II.2.a requires field-specific qualification beyond general licensure, creating the constraint that a chemical engineering background does not qualify Engineer B for structural footing design.
  • Engineer B General PE License Non-Authorization for Structural Footing Practice
    II.2.a mandates qualification in the specific technical field involved, making a general PE license insufficient for structural footing practice.
  • Contractor Competence Verification Duty Engineer B Structural Footing Retention
    II.2.a's requirement that engineers only undertake assignments when qualified implies a corresponding duty on the contractor to verify that qualification before retention.
  • BER Case 85-3 County Surveyor Oversight Role Substantive Background Minimum Threshold
    II.2.a requires qualification by education or experience, which the county surveyor analogy applies to show even an oversight role requires a minimum substantive background threshold.
  • Engineer B PE License Legal Minimum Ethics Code Higher Standard
    II.2.a sets an ethics standard of field-specific qualification that exceeds the legal minimum of holding a PE license, creating the higher standard constraint.
  • Public Safety at Risk from Engineer B Incompetent Structural Footing Design. Safety Constraint
    II.2.a's prohibition on undertaking unqualified assignments directly generates the public safety constraint by preventing incompetent structural footing design.
  • Engineer B Sole-Purpose Engagement Competence Delegation Non-Availability
    II.2.a requires Engineer B to be personally qualified for the assignment undertaken, constraining the ability to remedy incompetence through delegation in a sole-purpose engagement.
Principle (9)
  • Universal Competence Scope Limitation Invoked Against Engineer B Structural Footing Assignment
    This provision requires qualification by education or experience in the specific technical field, which Engineer B lacked for structural footing design.
  • Universal Engineer Competence Scope Limitation Invoked Against Engineer B Chemical-to-Structural Practice
    This provision explicitly ties qualification to education or experience in the specific field, directly applicable to Engineer B's chemical-only background.
  • Employer and Client Pressure Non-Exemption from Competence Boundary Applied to Engineer B
    This provision establishes that qualification requirements apply regardless of who assigns the work, negating the contractor-request defense.
  • Ethics Code as Higher Standard Than Legal Minimum Applied to Engineer B PE Licensure Defense
    This provision requires field-specific qualification beyond mere licensure, directly countering the argument that a PE license suffices.
  • Institutional Role Non-Expansion of Technical Competence Scope Applied via BER 85-3 Analogy
    This provision requires education or experience in the specific technical field, which an institutional role or general license cannot substitute for.
  • Degree-to-Task Alignment Verification Obligation Implicated in Contractor Retention of Engineer B
    This provision requires degree-to-task alignment, which the contractor was obligated to verify before retaining Engineer B.
  • Degree-to-Task Alignment Verification Obligation Applied to Contractor Retention of Engineer B
    This provision directly mandates that engineers undertake assignments only when qualified, making verification of Engineer B's credentials essential.
  • Peer Competence Challenge Obligation Invoked By Engineer A Based on Credential Inspection
    This provision is the basis for Engineer A's obligation to challenge Engineer B upon finding no structural engineering education or experience.
  • Peer Competence Challenge Obligation Upon Reasonable Doubt Applied to Engineer A Assessment of Engineer B
    This provision grounds the reasonable-doubt standard Engineer A applied when assessing whether Engineer B met field-specific qualification requirements.
Role (2)
  • Engineer B Cross-Discipline Out-of-Competence Structural Design Engineer
    Engineer B undertook a structural footing design assignment without being qualified by education or experience in structural engineering.
  • BER 85-3 County Surveyor Out-of-Competence Public Sector Appointee Engineer
    The county surveyor accepted an appointment requiring structural or civil oversight without being qualified by education or experience in those fields.
Event (2)
  • Engineer B's Lack of Qualifications Confirmed
    This provision directly applies as it requires engineers to undertake assignments only when qualified, and Engineer B's lack of qualifications is the central confirmed fact.
  • Project Construction Commences
    The commencement of construction under an unqualified engineer reflects a violation of the requirement to only undertake assignments when qualified.
Resource (5)
  • NSPE Code of Ethics Section II.2.a
    This resource is the direct codification of provision II.2.a specifying qualification by education or experience in the specific technical field.
  • Professional-Competence-Standard-Structural-Footing-Design
    This provision requires qualification by education or experience, directly implicated by Engineer B lacking structural engineering background.
  • BER Case 71-2
    This case affirmed the obligation to undertake assignments only when qualified by education or experience, consistent with II.2.a.
  • BER Case 85-3
    This case held a chemical engineer unethical for accepting work outside their qualified field, directly applying II.2.a.
  • NSPE-Code-of-Ethics-Professional-Competence
    This resource governs the competence obligation that II.2.a specifies in terms of required education or experience qualifications.
Capability (9)
  • Engineer B Structural Footing Foundation Design Competence Deficit
    II.2.a requires qualification by education or experience, which Engineer B lacked for structural footing design.
  • Engineer B Pre-Acceptance Structural Footing Competence Self-Assessment Deficit
    II.2.a requires self-assessment of qualification by education or experience before undertaking assignments.
  • Engineer A Peer Engineer Out-of-Discipline Competence Evidence Investigation
    II.2.a requires qualification by education or experience, making investigation of Engineer B's credentials directly relevant.
  • Engineer A Peer Competency Objective Basis Assessment
    II.2.a grounds competence in education and experience, which Engineer A was required to objectively assess for Engineer B.
  • Engineer B Irreconcilable Sole-Purpose Competence Gap Declination
    II.2.a requires declining assignments when not qualified by education or experience in the specific technical field.
  • BER 85-3 County Surveyor Irreconcilable Competence Gap Declination
    II.2.a is illustrated by the county surveyor who lacked the required education or experience for the role.
  • BER 85-3 County Surveyor Institutional Role Non-Expansion of Competence Self-Recognition
    II.2.a requires qualification by education or experience, not merely by institutional title or appointment.
  • Engineer B PE License Legal Minimum vs Ethics Code Higher Standard Self-Recognition
    II.2.a requires qualification by education or experience beyond what a PE license alone signifies.
  • Engineer A Employment vs Consulting Competence Flexibility Distinction Application
    II.2.a governs the qualification standard that differs in application between employment and consulting contexts.
II.2.b. 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 32)
Obligation
Engineer B Cross-Discipline Structural Footing Assignment Acceptance Refusal Obligation
This provision prohibits affixing signatures to documents in subject matter where competence is lacking, directly obligating Engineer B to refuse to sign structural footing design documents.
Action
Engineer B Accepts Structural Assignment
This provision prohibits Engineer B from signing or sealing structural documents if he lacks competence in that subject matter.
State
Engineer B Chemical Engineer Structural Footing Assignment Incompetence
Engineer B would be affixing a signature to structural footing plans in a subject matter where competence has not been established.
Obligation (3)
  • Engineer B Cross-Discipline Structural Footing Assignment Acceptance Refusal Obligation
    This provision prohibits affixing signatures to documents in subject matter where competence is lacking, directly obligating Engineer B to refuse to sign structural footing design documents.
  • Engineer B Sole-Purpose Structural Footing Sub-Delegation Infeasibility Recognition Obligation
    This provision prohibits signing documents not prepared under the engineer's direction and control, directly applying to the infeasibility of sub-delegating the sole-purpose structural footing design.
  • Engineer B PE License Non-Sufficiency Ethics Code Higher Standard Recognition Obligation
    This provision explicitly bars signing plans in subject matter where competence is lacking, directly establishing a standard beyond mere licensure that Engineer B was obligated to recognize.
Action (2)
  • Engineer B Accepts Structural Assignment
    This provision prohibits Engineer B from signing or sealing structural documents if he lacks competence in that subject matter.
  • Engineer B Decides Whether to Withdraw
    This provision requires Engineer B to refrain from affixing his signature to structural plans if he is not competent, effectively mandating withdrawal.
State (4)
  • Engineer B Chemical Engineer Structural Footing Assignment Incompetence
    Engineer B would be affixing a signature to structural footing plans in a subject matter where competence has not been established.
  • Engineer B Domain-Specific Incompetence in Structural Engineering
    This provision prohibits signing documents in subject matter where the engineer lacks competence, directly applicable to Engineer B's structural footing work.
  • Engineer B Sole-Purpose Structural Footing Engagement Precluding Delegation
    Engineer B's sole engagement is to design and presumably seal structural footing documents, which this provision prohibits without demonstrated competence.
  • Public Safety at Risk from Incompetent Structural Footing Design
    Prohibiting signature on plans outside one's competence is a safeguard directly protecting the public from unsafe structural designs.
Constraint (5)
  • Engineer B Domain-Specific Incompetence Seal Prohibition Structural Footings
    II.2.b directly prohibits affixing a signature or seal to documents in subject matter where the engineer lacks competence, creating this seal prohibition constraint.
  • Engineer B Domain-Specific Incompetence Structural Footing Seal Prohibition
    II.2.b is the direct source of the prohibition on Engineer B sealing structural footing design documents given demonstrated incompetence in that domain.
  • BER Case 85-3 County Surveyor Section II.2.b Inescapable Ethical Violation Recognition
    II.2.b is the specific provision the Board found the county surveyor could not comply with under any available course of action, making it the inescapable violation constraint.
  • Engineer B PE License Legal Minimum Ethics Code Higher Standard
    II.2.b imposes an ethical prohibition on sealing documents outside one's competence that goes beyond the legal minimum of holding a valid PE license.
  • Engineer B Public Safety Paramount Structural Footing Incompetence
    II.2.b's seal prohibition reinforces the public safety constraint by preventing Engineer B from certifying structural footing documents without requisite competence.
Principle (5)
  • Universal Competence Scope Limitation Invoked Against Engineer B Structural Footing Assignment
    This provision prohibits signing plans in subject matter where competence is lacking, directly applicable to Engineer B signing structural footing documents.
  • Universal Engineer Competence Scope Limitation Invoked Against Engineer B Chemical-to-Structural Practice
    This provision bars Engineer B from affixing a signature to structural footing plans given the absence of competence in that technical area.
  • Retained-Engineer Sub-Delegation Infeasibility Constraint Applied to Engineer B Structural Footing Sole-Purpose Retention
    This provision prevents Engineer B from signing documents outside their competence, making sub-delegation an insufficient workaround for the sole-purpose retention.
  • Employer and Client Pressure Non-Exemption from Competence Boundary Applied to Engineer B
    This provision makes clear that signing plans outside one's competence is prohibited regardless of client or employer direction.
  • Ethics Code as Higher Standard Than Legal Minimum Applied to Engineer B PE Licensure Defense
    This provision prohibits signing plans lacking competence even if the engineer holds a PE license, setting a higher standard than licensure alone.
Role (2)
  • Engineer B Cross-Discipline Out-of-Competence Structural Design Engineer
    Engineer B affixed his signature and seal to structural footing plans dealing with subject matter in which he lacked competence.
  • BER 85-3 County Surveyor Out-of-Competence Public Sector Appointee Engineer
    The county surveyor would be signing or sealing documents related to surveying and civil oversight in which he lacked competence.
Event (2)
  • Engineer B's Lack of Qualifications Confirmed
    This provision prohibits affixing signatures to documents in subject matter where competence is lacking, directly relevant when Engineer B's lack of qualifications is confirmed.
  • Project Construction Commences
    Construction commencing implies documents were signed and sealed, raising concern if Engineer B signed plans outside their competence.
Resource (3)
  • NSPE Code of Ethics Section II.2.b
    This resource is the direct codification of provision II.2.b prohibiting engineers from signing documents in subject matter where they lack competence.
  • BER Case 85-3
    This case explicitly applied II.2.b to conclude the chemical engineer could not comply with this provision regardless of the course of action taken.
  • Professional-Competence-Standard-Structural-Footing-Design
    This provision prohibits affixing signatures to plans in areas lacking competence, directly relevant to Engineer B signing structural footing designs.
Capability (6)
  • Engineer B Structural Footing Foundation Design Competence Deficit
    II.2.b prohibits signing documents in subject matter where competence is lacking, which Engineer B violated.
  • Engineer B Pre-Acceptance Structural Footing Competence Self-Assessment Deficit
    II.2.b requires engineers to refrain from signing plans in areas where they lack competence, necessitating prior self-assessment.
  • Engineer B Irreconcilable Sole-Purpose Competence Gap Declination
    II.2.b directly prohibits affixing signatures to documents in subject matter where the engineer lacks competence.
  • Engineer B Sole-Purpose Retention Sub-Delegation Infeasibility Recognition
    II.2.b prohibits signing documents not prepared under the engineer's direction and control, relevant to sub-delegation constraints.
  • Engineer A Cross-Discipline Structural Footing Competence Boundary Recognition
    II.2.b is implicated when Engineer A must recognize that Engineer B should not sign structural footing documents lacking competence.
  • BER 85-3 County Surveyor Irreconcilable Competence Gap Declination
    II.2.b prohibits signing plans in areas of lacking competence, directly illustrated by the county surveyor precedent.
II.2.c. 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 30)
Obligation
Engineering Firm Consulting Practice Subconsultant Engagement for Competence Gap Obligation
This provision explicitly allows coordination of an entire project with qualified engineers signing their respective segments, directly grounding the obligation to engage qualified subconsultants for competence gaps.
Action
Engineer B Accepts Structural Assignment
This provision clarifies the conditions under which Engineer B could legitimately accept coordination responsibility while ensuring qualified engineers seal each technical segment.
State
Engineer B Sole-Purpose Structural Footing Engagement Precluding Delegation
This provision allows coordination of entire projects with delegation to qualified engineers, but Engineer B's sole-purpose engagement leaves no room for such delegation.
Obligation (2)
  • Engineering Firm Consulting Practice Subconsultant Engagement for Competence Gap Obligation
    This provision explicitly allows coordination of an entire project with qualified engineers signing their respective segments, directly grounding the obligation to engage qualified subconsultants for competence gaps.
  • Engineer B Sole-Purpose Structural Footing Sub-Delegation Infeasibility Recognition Obligation
    This provision permits sub-delegation only when each technical segment is signed by the qualified engineer who prepared it, directly informing the recognition that sole-purpose sub-delegation by an unqualified engineer is infeasible.
Action (2)
  • Engineer B Accepts Structural Assignment
    This provision clarifies the conditions under which Engineer B could legitimately accept coordination responsibility while ensuring qualified engineers seal each technical segment.
  • Engineer A Investigates Engineer B's Qualifications
    Engineer A's investigation is relevant to determining whether the project structure complies with this provision's requirements for qualified engineers on each segment.
State (3)
  • Engineer B Sole-Purpose Structural Footing Engagement Precluding Delegation
    This provision allows coordination of entire projects with delegation to qualified engineers, but Engineer B's sole-purpose engagement leaves no room for such delegation.
  • Consulting Context Competence Remediation Flexibility. General Principle
    This provision outlines a consulting-context mechanism for managing competence across project segments, relevant to the Board's analysis of remediation options.
  • Engineer A Peer Competence Challenge Reporting Obligation Activated
    If Engineer A were coordinating the project, this provision would govern how qualified engineers must seal their respective segments, informing Engineer A's reporting obligation.
Constraint (6)
  • Consulting Firm Workforce Restructuring Permissibility. General Principle
    II.2.c permits coordination of an entire project with segment sealing by qualified engineers, directly authorizing the consulting firm workforce restructuring and subcontracting remedy.
  • Consulting vs. Employment Competence Flexibility Differential. BER Case 94-8 Application
    II.2.c provides the mechanism by which consulting firms can remedy competence gaps through qualified segment engineers, creating the flexibility differential relative to sole-purpose retention.
  • Engineer B Sole-Purpose Structural Footing Sub-Delegation Circular Nullification
    II.2.c allows project coordination with specialist sealing, but Engineer B's sole-purpose retention means sub-delegating the only assigned task nullifies rather than satisfies the engagement.
  • Engineer A Consulting Context Competence Flexibility Differential Awareness
    II.2.c is the provision that grants consulting context flexibility through specialist coordination, which Engineer A must recognize as inapplicable to Engineer B's sole-purpose retention.
  • Engineer B Sole-Purpose Engagement Competence Delegation Non-Availability
    II.2.c's coordination mechanism is unavailable to Engineer B because the sole-purpose retention leaves no broader project role within which to coordinate a competent specialist.
  • BER Cases 71-2 and 78-5 Cross-Domain Analogical Application to BER Case 85-3
    II.2.c underlies the consulting firm flexibility in BER Cases 71-2 and 78-5 that the Board had to distinguish from the sole-purpose employment context of BER Case 85-3.
Principle (2)
  • Retained-Engineer Sub-Delegation Infeasibility Constraint Applied to Engineer B Structural Footing Sole-Purpose Retention
    This provision allows coordination and overall signing only when qualified engineers sign each technical segment, which Engineer B could not satisfy for structural footings.
  • Universal Engineer Competence Scope Limitation Invoked Against Engineer B Chemical-to-Structural Practice
    This provision clarifies that overall project responsibility does not override the requirement that each technical segment be signed by a qualified engineer.
Role (3)
  • Engineer A Competency-Challenging Co-Project Engineer
    Engineer A as co-project engineer must ensure that technical segments like structural footing design are signed and sealed only by engineers qualified in that segment.
  • BER 71-2 Prime Professional Specialist-Retaining Prime Consulting Engineer
    The prime professional retaining specialists must ensure each technical segment is signed and sealed only by the qualified engineers who prepared it.
  • Construction Contractor Design-Build Project Retaining Contractor Client
    By separately retaining Engineer B for structural design, the contractor is involved in the coordination of project segments and must ensure qualified engineers seal each technical segment.
Event (2)
  • Engineer B's Lack of Qualifications Confirmed
    This provision outlines the conditions under which an engineer may coordinate and seal an entire project, relevant to assessing whether Engineer B's role was permissible given confirmed lack of qualifications.
  • Prior BER Precedents Established
    Prior BER precedents likely addressed coordination and sealing responsibilities under this provision, informing the ethical analysis of the case.
Resource (2)
  • NSPE Code of Ethics Section II.2.c
    This resource is the direct codification of provision II.2.c and was considered then rejected as an insufficient ethical avenue in this case.
  • BER Case 78-5
    This case affirmed obligations around qualifications and coordination responsibilities relevant to the II.2.c coordination and sealing framework.
Capability (8)
  • Engineer A Design-Build Separately Retained Engineer Competence Verification Duty Recognition
    II.2.c establishes that a prime engineer coordinating a project retains responsibility for verifying that each technical segment is handled by qualified engineers.
  • BER 71-2 Prime Professional Specialist Competence Verification
    II.2.c directly governs the prime professional's duty to ensure each technical segment is sealed only by qualified engineers.
  • BER 71-2 Prime Professional Specialist Retention Competence Gap Remediation
    II.2.c authorizes and requires the prime professional to retain qualified specialists for segments outside their own competence.
  • Engineer A Employment vs Consulting Competence Flexibility Distinction Application
    II.2.c provides the framework for how a coordinating engineer may accept overall responsibility while delegating segments to qualified specialists.
  • Construction Contractor Competence Gap Subconsultant Verification Responsibility
    II.2.c implies that parties retaining engineers for technical segments must ensure those engineers are qualified for the specific segment.
  • Construction Contractor Consulting Practice Workforce Structuring Competence Gap Remediation
    II.2.c permits project coordination with specialist segments, informing how contractors should structure engineering services.
  • Engineer A BER Three-Precedent Consulting-Employment Competence Flexibility Spectrum Synthesis
    II.2.c is a key provision synthesized across the three BER precedents regarding prime professional coordination and specialist qualification.
  • Engineer B Sole-Purpose Retention Sub-Delegation Infeasibility Recognition
    II.2.c requires each technical segment to be signed only by the qualified engineer who prepared it, making sub-delegation by a sole-purpose retainee problematic.
III.2.b. Engineers shall not complete, sign, or seal plans and/or specifications that are not in conformity with applicable engineering standards. If the client or employer insists on such unprofessional conduct, they shall notify the proper authorities and withdraw from further service on the project.
How this applies in the case (showing 3 of 36)
Obligation
Engineer A Direct Confrontation of Engineer B Recommending Withdrawal Obligation
This provision prohibits completing or sealing plans not in conformity with engineering standards and requires withdrawal from unprofessional conduct, directly supporting Engineer A's obligation to confront Engineer B and recommend withdrawal.
Action
Engineer B Accepts Structural Assignment
This provision prohibits Engineer B from completing or sealing plans that do not conform to applicable engineering standards, which is at risk if he lacks competence.
State
Engineer B Chemical Engineer Structural Footing Assignment Incompetence
Engineer B completing and sealing structural footing plans without competence would constitute signing plans not in conformity with applicable engineering standards.
Obligation (4)
  • Engineer A Direct Confrontation of Engineer B Recommending Withdrawal Obligation
    This provision prohibits completing or sealing plans not in conformity with engineering standards and requires withdrawal from unprofessional conduct, directly supporting Engineer A's obligation to confront Engineer B and recommend withdrawal.
  • Engineer A Client and Authority Escalation Upon Engineer B Refusal Obligation
    This provision requires notifying proper authorities when unprofessional conduct persists, directly grounding Engineer A's obligation to escalate to the client and authorities if Engineer B refuses to withdraw.
  • Engineer A Project Withdrawal If Competence Concerns Unmet Obligation
    This provision explicitly requires withdrawal from further service when unprofessional conduct is not corrected, directly applying to Engineer A's obligation to withdraw if competence concerns remain unresolved.
  • Engineer B Cross-Discipline Structural Footing Assignment Acceptance Refusal Obligation
    This provision prohibits completing or sealing plans not conforming to engineering standards, directly reinforcing Engineer B's obligation to refuse an assignment outside their competence.
Action (4)
  • Engineer B Accepts Structural Assignment
    This provision prohibits Engineer B from completing or sealing plans that do not conform to applicable engineering standards, which is at risk if he lacks competence.
  • Engineer A Reports Concerns to Contractor
    This provision supports Engineer A's obligation to report nonconforming conduct to the appropriate parties when engineering standards are not being met.
  • Engineer A Escalates to Client and Authorities
    This provision directly requires notifying proper authorities and withdrawing from the project when unprofessional conduct persists, governing Engineer A's escalation action.
  • Engineer B Decides Whether to Withdraw
    This provision obligates Engineer B to withdraw from further service if the plans he is being asked to seal do not conform to applicable engineering standards.
State (5)
  • Engineer B Chemical Engineer Structural Footing Assignment Incompetence
    Engineer B completing and sealing structural footing plans without competence would constitute signing plans not in conformity with applicable engineering standards.
  • Engineer B Domain-Specific Incompetence in Structural Engineering
    Sealing structural engineering documents without requisite competence violates applicable engineering standards addressed by this provision.
  • Engineer A Peer Competence Challenge Reporting Obligation Activated
    This provision supports Engineer A's obligation to notify proper authorities when nonconforming plans are being sealed by an unqualified engineer.
  • Engineer A Peer Competence Challenge Reporting Obligation
    This provision directly establishes the duty to notify proper authorities and withdraw from service when unprofessional conduct involving nonconforming plans is identified.
  • Public Safety at Risk from Incompetent Structural Footing Design
    The provision protects the public by requiring withdrawal and reporting when plans do not conform to engineering standards, directly addressing safety risks.
Constraint (6)
  • Engineer A Peer Competence Challenge Graduated Escalation Structural Footing Project
    III.2.b's requirement to notify proper authorities and withdraw from unprofessional conduct situations underpins the graduated escalation obligation Engineer A must follow.
  • Engineer A Non-Imminent Reporting Non-Compulsion Collegial First Step
    III.2.b implies escalation steps before formal reporting, supporting the constraint that Engineer A is not immediately compelled to file a formal complaint as a first step.
  • Engineer A Objective Basis Peer Competence Challenge Graduated Escalation
    III.2.b requires action when engineering standards are not met, creating the constraint that Engineer A must follow graduated escalation upon identifying an objective basis for concern.
  • Engineer A Project Withdrawal If Competence Concerns Unmet. Conditional Trigger
    III.2.b explicitly requires withdrawal from further service when unprofessional conduct persists, directly creating the conditional withdrawal obligation for Engineer A.
  • Engineer B Domain-Specific Incompetence Seal Prohibition Structural Footings
    III.2.b prohibits completing or sealing plans not in conformity with applicable engineering standards, reinforcing the seal prohibition on Engineer B's incompetent structural footing work.
  • Engineer B Public Safety Paramount Structural Footing Incompetence
    III.2.b's prohibition on sealing non-conforming plans and requirement to withdraw reinforces the absolute constraint on Engineer B continuing incompetent structural footing design work.
Principle (5)
  • Peer Competence Confrontation Before Authority Escalation Sequencing Applied to Engineer A Obligations
    This provision requires notifying proper authorities and withdrawing if unprofessional conduct persists, directly supporting the escalation sequence prescribed for Engineer A.
  • Engineering Self-Policing Obligation Invoked By Engineer A Reporting to Contractor
    This provision supports Engineer A's self-policing duty by requiring notification of proper authorities when non-conforming plans are being produced.
  • Project Withdrawal as Ethical Recourse Applied to Engineer A If Concerns Unmet
    This provision explicitly authorizes withdrawal from further service when unprofessional conduct is not corrected, directly grounding Engineer A's withdrawal option.
  • Public Welfare Paramount Invoked in Structural Footing Competence Context
    This provision protects public welfare by requiring engineers to refuse to complete non-conforming plans and to alert authorities, applicable to the structural safety risk.
  • Incomplete Situational Knowledge Restraint Balanced Against Reporting Obligation by Engineer A
    This provision creates the reporting obligation that Engineer A must balance against the restraint of incomplete knowledge about Engineer B's training.
Role (2)
  • Engineer B Cross-Discipline Out-of-Competence Structural Design Engineer
    Engineer B should not complete, sign, or seal structural plans that are not in conformity with applicable engineering standards given his lack of competence in that field.
  • Engineer A Competency-Challenging Co-Project Engineer
    Engineer A identified reservations about the structural design and is obligated not to approve or allow plans not in conformity with applicable engineering standards to proceed.
Event (3)
  • Contractor Receives Safety Concern
    This provision requires engineers to notify proper authorities when plans do not conform to standards, directly relevant when a safety concern is communicated to the contractor.
  • Engineer B Confrontation Outcome Determined
    The outcome of confronting Engineer B determines whether withdrawal or notification of authorities becomes necessary under this provision.
  • Escalation Necessity Triggered
    This provision mandates notifying proper authorities and withdrawing from the project when unprofessional conduct persists, directly triggering the need for escalation.
Resource (3)
  • Engineer-Public-Safety-Escalation-Standard-Competence-Context
    This provision requires notifying proper authorities if unprofessional conduct persists, directly governing Engineer A's duty to escalate beyond the contractor.
  • Engineer-Reporting-Obligation-to-State-Board-Competence-Violation
    This provision supports the duty to notify proper authorities such as the state licensing board when competence violations are not corrected.
  • Collegial-Notification-Before-Reporting-Standard-Engineer-B
    This provision implies a process of notification and potential withdrawal, relevant to whether Engineer A should first notify Engineer B before escalating.
Capability (4)
  • Engineer A Professional Withdrawal Decision Upon Unresolved Competence Concern
    III.2.b requires withdrawal from a project when unprofessional conduct cannot be resolved, directly governing Engineer A's withdrawal capability.
  • Engineer A Peer Competence Challenge Direct Confrontation Before Client-Authority Escalation Sequencing
    III.2.b requires notifying proper authorities when unprofessional conduct persists, informing the sequencing of Engineer A's escalation response.
  • Engineer B Structural Footing Foundation Design Competence Deficit
    III.2.b prohibits completing plans not in conformity with engineering standards, which is implicated when an incompetent engineer produces non-conforming work.
  • Engineer A Design-Build Separately Retained Engineer Competence Verification Duty Recognition
    III.2.b requires action including withdrawal when engineering standards are not met, reinforcing Engineer A's duty to act on competence concerns.
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 have at least some substantive degree of background and experience in the relevant field to accept a position requiring that expertise, even if they meet the legal requirements for the position; professional ethics requires going beyond what is legally permitted.

Citation Context:

Cited as the primary analogous precedent where a chemical engineer accepting a county surveyor position was deemed unethical due to lack of relevant background, establishing that engineers must have substantive background and experience to accept positions requiring specialized expertise.

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: "After considering the two earlier cases, the Board decided it was unethical for Engineer A to accept the position as county surveyor"
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"
discussion: "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"

Principle Established:

Prime professionals have an ethical obligation to retain or recommend experts and specialists when needed, and engineers should only seek work in areas where they possess the necessary educational background and experience.

Citation Context:

Cited to establish the propriety of retaining experts and specialists for projects, and that engineers have an ethical obligation to seek work only in areas where they possess educational background and experience 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"

Principle Established:

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 qualifications to perform the work.

Citation Context:

Cited to reinforce the principle from BER Case 71-2 that engineers must only seek work in areas where they possess the necessary educational background and experience, affirming the ethical obligation regarding competence.

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"
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"
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 55% Facts Similarity 57% Discussion Similarity 59% Provision Overlap 75% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: I.2, II.2, II.2.a, II.2.b, II.2.c, III.1.b Same outcome True View Synthesis
Component Similarity 57% Facts Similarity 58% Discussion Similarity 67% Provision Overlap 60% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: I.2, II.1.a, II.2, II.2.a, II.2.b, III.1.b Same outcome True View Synthesis
Component Similarity 62% Facts Similarity 65% Discussion Similarity 52% Provision Overlap 46% Outcome Alignment 100% Tag Overlap 62%
Shared provisions: I.2, II.1.f, II.2, II.2.b, II.2.c Same outcome True View Synthesis
Component Similarity 59% Facts Similarity 46% Discussion Similarity 89% Provision Overlap 56% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.2, II.2, II.2.a, II.2.b, III.1.b Same outcome True View Synthesis
Component Similarity 63% Facts Similarity 52% Discussion Similarity 55% Provision Overlap 38% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: II.2, II.2.a, II.2.b Same outcome True View Synthesis
Component Similarity 55% Facts Similarity 55% Discussion Similarity 51% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 38%
Shared provisions: I.2, II.2, II.2.a, II.2.b, II.2.c Same outcome True View Synthesis
Component Similarity 54% Facts Similarity 67% Discussion Similarity 52% Provision Overlap 38% Outcome Alignment 100% Tag Overlap 57%
Shared provisions: II.2.a, II.2.b, II.2.c Same outcome True View Synthesis
Component Similarity 50% Facts Similarity 48% Discussion Similarity 64% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 36%
Shared provisions: I.2, II.1.a, II.2.a, II.2.b, II.2.c, III.1.b Same outcome True View Synthesis
Component Similarity 52% Facts Similarity 65% Discussion Similarity 60% Provision Overlap 27% Outcome Alignment 100% Tag Overlap 44%
Shared provisions: I.2, II.1.f, II.2, II.2.a Same outcome True View Synthesis
Component Similarity 56% Facts Similarity 54% Discussion Similarity 65% Provision Overlap 18% Outcome Alignment 100% Tag Overlap 25%
Shared provisions: II.1.a, III.1.b Same outcome True 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.
Implicit (4)

Does Engineer B bear an independent ethical obligation to proactively disclose his chemical engineering background and lack of structural training to the contractor before accepting the structural footing assignment, rather than waiting for a peer to raise concerns?

AnalyticalBeyond the Board's finding that Engineer B's acceptance of the structural footing assignment is unethical, Engineer B bore an independent and antecedent ethical obligation to conduct a candid self-assessment of his own competence before accepting the engagement - not merely to decline if challenged by a peer. The chemical engineering background that defines Engineer B's training is substantively remote from the soil mechanics, load-path analysis, and foundation design principles required for structural footing work. Because Engineer B's sole-purpose retention was specifically and exclusively for structural footing design, there was no broader project role within which a competence gap could be absorbed, delegated, or remediated through collaboration with a qualified structural engineer. The circularity is decisive: Engineer B could not ethically seal work he lacked the competence to perform, and he could not ethically oversee a qualified structural engineer performing that work without himself possessing the substantive background necessary to evaluate it. Holding a general PE license does not dissolve this constraint; the ethics code imposes a higher standard than the legal minimum of licensure, and that higher standard required Engineer B to proactively disclose his disciplinary background to the contractor and decline the assignment before any peer raised concerns.
AnalyticalIn response to Q101: Engineer B bears an independent and primary ethical obligation to proactively disclose his chemical engineering background and lack of structural training to the contractor before accepting the structural footing assignment. This obligation flows directly from Section II.2.a, which requires engineers to undertake assignments only when qualified by education or experience in the specific technical field involved. The duty to disclose is not contingent on a peer raising concerns; it is self-executing and arises at the moment Engineer B evaluates whether to accept the engagement. Waiting for Engineer A or another party to surface the competence gap inverts the ethical architecture of the code, which places primary gatekeeping responsibility on the individual engineer. A fully ethical Engineer B would have declined the assignment outright or, at minimum, disclosed his background limitations to the contractor before any design work commenced, allowing the contractor to make an informed retention decision. The fact that Engineer B accepted the assignment without apparent disclosure compounds the ethical violation beyond mere incompetence into a failure of professional candor.

What ethical responsibility, if any, does the construction contractor bear for failing to verify Engineer B's qualifications before retaining him for structural footing design, and does the contractor's negligence in this regard diminish or amplify Engineer A's reporting obligations?

AnalyticalIn response to Q102: The construction contractor bears an independent ethical and practical responsibility to verify Engineer B's qualifications before retaining him for structural footing design, as implied by the degree-to-task alignment verification obligation. However, the contractor's failure to perform adequate pre-retention screening does not diminish Engineer A's reporting obligations - it amplifies them. The contractor's negligence creates a gap in the competence gatekeeping system that Engineer A's reporting obligation is specifically designed to fill. The engineering profession's self-policing norms, reflected in Section II.2 and the broader code structure, exist precisely because clients and contractors often lack the technical sophistication to independently assess cross-discipline competence deficiencies. Assigning primary responsibility to the contractor would dangerously dilute the profession's internal accountability norms and undermine the public trust that professional licensure is meant to guarantee. The contractor's failure is a contributing factor to the ethical problem, but it does not transfer or reduce Engineer A's independent duty to act upon reasonable knowledge of a competence violation that threatens public safety.
AnalyticalThe Board's conclusion that Engineer B's assignment is unethical carries an important but unaddressed implication for the construction contractor: the contractor's failure to verify Engineer B's disciplinary background and domain-specific qualifications before retention constitutes an independent ethical failure that neither diminishes nor displaces Engineer A's reporting obligation but does amplify the systemic risk to public safety. The contractor, operating in a design-build context, assumed a coordination and oversight role that included a duty to confirm that each retained engineer possessed qualifications aligned to the specific technical task assigned. Retaining a chemical engineer for structural footing design without investigating whether that engineer had subsequent training in foundation design represents a degree-to-task alignment verification failure. However, assigning primary responsibility for this failure to the contractor must not be permitted to dilute the engineering profession's internal self-policing norms: the contractor's negligence does not reduce Engineer A's obligation to report, nor does it excuse Engineer B's obligation to decline. Rather, the contractor's verification failure and the engineers' individual competence obligations operate in parallel, each independently required by the ethical framework governing their respective roles.

If Engineer A's concerns are reported to the contractor but the contractor takes no corrective action, at what point does Engineer A's ethical obligation escalate from internal reporting to notification of the state licensing board or other public authorities, and does the structural safety risk inherent in footing design accelerate that threshold?

AnalyticalThe Board's unresolved question about Engineer A's reporting obligation has a further dimension that the Board did not reach: if the contractor receives Engineer A's concerns and takes no corrective action, Engineer A's ethical obligation does not terminate at the contractor level. The structural footing context is particularly significant here because footing failures are catastrophic, irreversible, and capable of causing loss of life to building occupants who have no knowledge of and no ability to protect themselves from the competence deficiency. This asymmetry between the severity and irreversibility of potential harm and the relative ease of remediation - replacing Engineer B with a qualified structural engineer - means that the public welfare paramount principle accelerates the escalation threshold. Engineer A's obligation would progress from contractor notification to state licensing board notification if the contractor failed to act, and continued participation in the project alongside an unqualified Engineer B performing structural footing design could, under sufficiently unresponsive circumstances, constitute complicity requiring Engineer A's withdrawal from the project entirely.
AnalyticalIn response to Q103: If Engineer A reports concerns to the contractor and the contractor takes no corrective action, Engineer A's ethical obligation escalates progressively and does not terminate at the contractor notification step. The structural safety risk inherent in footing design - where failure can cause catastrophic, irreversible harm to building occupants - materially accelerates the escalation threshold. Under the public welfare paramount principle and the engineer's duty to hold public safety above client interests, Engineer A's next obligation would be to directly confront Engineer B and recommend withdrawal. If Engineer B also refuses to withdraw and the contractor continues to permit the incompetent design work, Engineer A's obligation escalates further to notification of the state licensing board or other relevant public authorities. The severity and irreversibility of potential structural footing failure means that the threshold for escalation beyond the contractor is lower in this context than it would be for a less safety-critical assignment. Continued silence after contractor inaction would risk making Engineer A complicit in a foreseeable public safety harm, which the code does not permit. At that stage, project withdrawal by Engineer A may also become ethically necessary.

Could Engineer B ethically cure the competence deficiency by collaborating with or directly supervising a qualified structural engineer, and if so, would that arrangement satisfy the ethical requirements of Section II.2.c, or does the sole-purpose nature of his engagement make such delegation structurally impossible?

AnalyticalIn response to Q104: Engineer B could theoretically cure the competence deficiency by engaging a qualified structural engineer to perform the actual footing design under proper supervision, as contemplated by Section II.2.c, which permits accepting coordination responsibility for an entire project while retaining specialists for components outside one's competence. However, the sole-purpose nature of Engineer B's engagement with the contractor makes this remedy structurally circular and ethically unavailable. Engineer B was retained specifically and exclusively to design the structural footings - that task is not a subsidiary component of a broader coordination role but the entirety of his engagement. If Engineer B sub-delegated the actual design to a qualified structural engineer, he would be providing no independent value to the engagement while retaining the ethical and legal responsibility of sealing work he cannot competently review. Furthermore, Engineer B's inability to competently oversee, evaluate, or seal the delegated structural work means the sub-delegation would not satisfy Section II.2.b's prohibition on affixing signatures to plans dealing with subject matter in which the engineer is not competent. The II.2.c remedy is designed for prime professionals with genuine coordination competence, not as a mechanism for incompetent engineers to launder out-of-discipline assignments through nominal delegation.
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.
Principle tension (4)

Does the principle requiring Engineer A to confront Engineer B directly before escalating to the contractor or authorities conflict with the principle that public welfare is paramount, particularly when structural footing failures could cause catastrophic and irreversible harm to building occupants?

AnalyticalIn response to Q201: The principle requiring Engineer A to confront Engineer B directly before escalating to the contractor or authorities does create a sequencing tension with the public welfare paramount principle, but this tension is resolvable rather than irreconcilable. The graduated escalation sequence - direct confrontation of Engineer B, then contractor notification, then authority escalation - is not merely a procedural courtesy; it reflects the profession's commitment to collegial self-regulation and gives Engineer B the opportunity to self-correct before external intervention. However, the structural footing context materially compresses the acceptable timeline for each escalation step. Because structural footing failures can cause catastrophic and irreversible harm, Engineer A cannot afford extended deliberation at any stage. The public welfare paramount principle does not eliminate the direct confrontation step but it does mean that Engineer A's tolerance for delay or non-response at each stage must be significantly shorter than it would be for a less safety-critical assignment. If direct confrontation of Engineer B produces no corrective action within a reasonable and compressed timeframe, the public welfare obligation overrides any residual collegial deference and compels immediate escalation.
AnalyticalThe most fundamental tension in this case - between the principle that public welfare is paramount and the principle of incomplete situational knowledge restraint - was resolved by the Board in favor of a graduated, sequenced response rather than immediate escalation. The Board did not treat public safety as a trump card that collapses all procedural steps into an immediate duty to report to authorities. Instead, it preserved the collegial-first sequencing: Engineer A should confront Engineer B directly before escalating to the contractor or beyond. This resolution implicitly teaches that 'public welfare is paramount' functions as a ceiling constraint on inaction, not as a lever that bypasses professional process. The principle only overrides procedural sequence when the risk is imminent and the process has already failed - not at the moment reasonable doubt first arises. In the structural footing context, where failures can be catastrophic, this sequencing remains intact precisely because early-stage intervention (direct confrontation, then contractor notification) is itself a public-safety-protective act, not a delay of it.

How should the principle of incomplete situational knowledge restraint - which cautions Engineer A against acting on unverified assumptions about Engineer B's competence - be reconciled with the peer competence challenge obligation that activates upon reasonable doubt, and where precisely does reasonable doubt become sufficient to override epistemic caution?

AnalyticalIn response to Q202: The tension between incomplete situational knowledge restraint and the peer competence challenge obligation resolves at the point where Engineer A has made a reasonable, good-faith investigation of Engineer B's credentials and background and has been unable to establish any qualifying education or experience in foundation design. The standard is not certainty of incompetence but reasonable doubt grounded in objective evidence - or the absence of evidence - following diligent inquiry. In this case, Engineer A investigated Engineer B's qualifications, found that his degree is in chemical engineering, and could not establish any subsequent training in foundation design. That combination of positive evidence of a non-structural background and absence of evidence of remedial qualification is sufficient to activate the peer competence challenge obligation. Engineer A is not required to prove Engineer B incompetent beyond doubt; the code's protective purpose for public safety means that reasonable, evidence-based doubt about competence in a safety-critical domain is sufficient to trigger the reporting obligation. Epistemic caution is appropriate before investigation but cannot serve as a perpetual shield against action once investigation has produced a reasonable basis for concern.

Does the principle that the ethics code sets a higher standard than mere PE licensure conflict with the principle that consulting contexts afford engineers greater competence flexibility than employment contexts, and if so, does that flexibility have any legitimate application to Engineer B's situation or is it entirely foreclosed by the sole-purpose nature of his engagement?

AnalyticalThe case reveals a decisive resolution of the tension between the ethics code as a higher standard than mere PE licensure and the principle that consulting contexts afford engineers greater competence flexibility than employment contexts. The Board's analysis makes clear that these two principles operate on different axes and do not cancel each other out: consulting flexibility is a real and recognized principle, but it applies to how competence gaps are remediated organizationally - through subconsultant retention, team structuring, or specialist delegation - not to whether a given engineer may personally seal work outside their domain. Because Engineer B was retained on a sole-purpose basis specifically to design structural footings, the consulting-context flexibility principle had no operative purchase: there was no organizational structure through which Engineer B could legitimately route the work to a qualified structural engineer while retaining meaningful oversight. The ethics code's higher standard therefore prevailed unconditionally in Engineer B's situation, and the consulting flexibility principle was effectively neutralized by the sole-purpose engagement constraint. This teaches that consulting flexibility is an organizational remedy, not a personal competence waiver.
AnalyticalIn response to Q203: The principle that the ethics code sets a higher standard than mere PE licensure and the principle that consulting contexts afford engineers greater competence flexibility than employment contexts do create a genuine tension, but that tension does not benefit Engineer B in this case. The consulting context flexibility principle, as illustrated in BER cases 71-2 and 78-5, applies to situations where a consulting firm or prime professional can restructure its workforce, retain specialists, or otherwise adapt its organizational capacity to address competence gaps. That flexibility is organizational and structural in nature - it permits a consulting firm to cure a competence gap through legitimate subconsultant arrangements. It does not permit an individual engineer to accept an assignment for which he personally lacks competence on the theory that consulting contexts are more permissive. Engineer B's sole-purpose engagement means there is no organizational flexibility to invoke; the consulting context flexibility principle simply has no application to his situation. Meanwhile, the ethics code higher standard principle directly forecloses any argument that Engineer B's general PE licensure authorizes structural footing design. The two principles are not in genuine conflict as applied to Engineer B - the consulting flexibility principle is inapplicable, and the higher standard principle is directly operative.

Does the degree-to-task alignment verification obligation - which implies the contractor should have screened Engineer B before retention - conflict with the engineering self-policing obligation that places the primary burden of competence gatekeeping on Engineer A and Engineer B themselves, and does assigning responsibility to the contractor risk diluting the profession's internal accountability norms?

AnalyticalIn response to Q204: The degree-to-task alignment verification obligation applicable to the contractor and the engineering self-policing obligation applicable to Engineer A and Engineer B are not fundamentally in conflict, but assigning meaningful responsibility to the contractor does carry a risk of diluting the profession's internal accountability norms if not carefully bounded. The contractor's verification duty is real but it is a secondary safeguard - it exists because contractors sometimes retain engineers without adequate credential scrutiny, and the profession's ethical framework anticipates this gap. The primary burden of competence gatekeeping remains on Engineer B himself, who must self-assess and decline out-of-competence assignments, and on Engineer A, who must challenge apparent competence violations when discovered. Treating the contractor's verification failure as a primary or co-equal responsibility risks creating a moral hazard where engineers assume that contractor screening will catch competence problems they themselves should have prevented. The correct framing is that the contractor's verification obligation and the engineers' self-policing obligations operate in parallel and are mutually reinforcing, but the engineers' obligations are primary and non-delegable, while the contractor's obligation is a secondary institutional check that does not substitute for professional self-regulation.
AnalyticalA subtler but important principle tension exists between the degree-to-task alignment verification obligation - which implies the contractor bore a duty to screen Engineer B before retention - and the engineering self-policing obligation that places primary competence gatekeeping on engineers themselves. The Board's analysis does not explicitly resolve this tension, but its structure implicitly prioritizes the internal professional obligation: the ethical conclusions are directed at Engineer B's acceptance decision and Engineer A's reporting duty, not at the contractor's screening failure. This prioritization carries a normative lesson: assigning primary responsibility to the contractor risks diluting the profession's internal accountability norms by suggesting that engineers may accept assignments unless externally screened out. The profession's ethical framework instead demands that Engineer B self-screen before acceptance and that Engineer A police the boundary when Engineer B fails to do so. The contractor's verification duty is real but secondary - a backstop, not the primary line of defense. Allowing contractor negligence to diminish Engineer A's reporting obligation would invert this hierarchy and undermine the self-regulating character of professional engineering ethics.
Cross-cutting analytical questions (8)

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

Theoretical (4)

From a deontological perspective, did Engineer B violate a categorical duty to practice only within competence by accepting the structural footing assignment, regardless of whether the resulting design might have turned out to be structurally sound?

AnalyticalThe Board's treatment of Engineer B's situation is further illuminated by the BER Case 85-3 analogy: just as the county surveyor's appointment to a public role did not expand the technical scope of that engineer's competence, Engineer B's retention by the contractor for a specific structural task did not confer structural engineering competence that Engineer B did not independently possess. The institutional or contractual framing of an assignment - whether a public appointment or a private consulting engagement - is ethically inert with respect to the competence boundary. This principle forecloses any argument that Engineer B's status as a retained PE, or the contractor's apparent confidence in retaining him, could serve as a substitute for substantive domain-specific qualification. From a deontological standpoint, Engineer B's categorical duty to practice only within competence was violated at the moment of acceptance, entirely independent of whether the resulting footing design might have proven structurally adequate. The outcome of the design is irrelevant to the ethical violation; the violation was complete upon acceptance of an assignment for which Engineer B lacked the requisite education or experience in the specific technical domain.
AnalyticalIn response to Q301: From a deontological perspective, Engineer B violated a categorical duty to practice only within competence by accepting the structural footing assignment, regardless of whether the resulting design might have turned out to be structurally sound. The deontological analysis under Section II.2.a is outcome-independent: the duty is to undertake assignments only when qualified by education or experience in the specific technical field, and that duty is violated at the moment of acceptance, not at the moment of failure. A fortuitously adequate design produced by an incompetent engineer does not retroactively cure the ethical violation, just as a lucky outcome does not transform a reckless act into a prudent one. The categorical nature of this duty reflects the code's recognition that competence cannot be reliably assessed after the fact by non-expert clients or the public, and that the profession's trustworthiness depends on engineers self-enforcing competence boundaries unconditionally. Engineer B's chemical engineering background and absence of established foundation design training place him categorically outside the competence boundary for structural footing design, making the acceptance of the assignment an unconditional ethical violation.

From a consequentialist perspective, does the potential harm to public safety from an incompetently designed structural footing outweigh any project efficiency or cost benefits gained by retaining Engineer B rather than a qualified structural engineer, and how should that calculus inform the contractor's retention decision?

AnalyticalIn response to Q302: From a consequentialist perspective, the potential harm to public safety from an incompetently designed structural footing vastly outweighs any project efficiency or cost benefits gained by retaining Engineer B rather than a qualified structural engineer. Structural footing failures can cause building collapse, loss of life, and severe injury to occupants and workers - harms that are catastrophic in magnitude, irreversible in nature, and potentially affect many people beyond the immediate parties to the contract. The cost savings or scheduling convenience of retaining an already-engaged chemical engineer for a structural task are marginal and speculative benefits by comparison. A rigorous consequentialist calculus, properly accounting for the probability of harm, the severity and irreversibility of potential outcomes, and the breadth of persons affected, would unambiguously favor retaining a qualified structural engineer. This analysis should directly inform the contractor's retention decision: the contractor's duty to verify Engineer B's qualifications before retention is not merely a procedural nicety but a consequentially critical safeguard against a foreseeable and preventable catastrophic outcome.

From a virtue ethics perspective, did Engineer A demonstrate the professional virtues of courage and integrity by reporting concerns about Engineer B's competence to the contractor, and would a fully virtuous engineer have gone further by directly confronting Engineer B before escalating to the contractor?

AnalyticalIn response to Q303: From a virtue ethics perspective, Engineer A demonstrated the professional virtues of courage and integrity by reporting concerns about Engineer B's competence to the contractor, particularly given the professional and social pressures that typically discourage engineers from challenging colleagues on a shared project. However, a fully virtuous engineer would also have directly confronted Engineer B before or alongside escalating to the contractor. Direct confrontation reflects the virtues of honesty, respect for professional peers, and commitment to collegial self-regulation - it gives Engineer B the opportunity to self-correct and preserves the dignity of the professional relationship. Bypassing direct confrontation in favor of immediate contractor notification, while not necessarily unethical, reflects a less complete expression of professional virtue. The virtuous sequence would be: investigate Engineer B's credentials thoroughly, confront Engineer B directly with the concern and recommend withdrawal, and then escalate to the contractor and authorities if Engineer B refuses to act. This sequence embodies both the courage to challenge a peer and the integrity to follow through with escalation when self-correction fails.

From a deontological perspective, does Engineer A's duty to protect public safety create an unconditional obligation to escalate concerns beyond the contractor to the state licensing board if the contractor fails to act, or does the duty remain conditional on the severity and imminence of the risk?

AnalyticalIn response to Q304: From a deontological perspective, Engineer A's duty to protect public safety creates a strong but not unconditional obligation to escalate concerns beyond the contractor to the state licensing board if the contractor fails to act. The duty is strong because structural footing design implicates irreversible public safety risks that cannot be adequately addressed by private contractual arrangements alone. However, the duty remains sensitive to the severity and imminence of the risk in determining the appropriate escalation pathway and timing. Where the risk is severe and imminent - as it is in structural footing design for an industrial facility under active construction - the threshold for escalating to the licensing board is materially lower than it would be for a speculative or remote risk. The structural safety context means that Engineer A cannot indefinitely defer licensing board notification while waiting for the contractor to act. If the contractor fails to take corrective action within a reasonable and compressed timeframe, the deontological duty to protect public safety becomes an unconditional obligation to escalate to the licensing board, because at that point Engineer A possesses knowledge of an ongoing competence violation that poses a direct threat to public welfare and no private remedy has been effective.
Counterfactual (4)

If Engineer B had substantial post-degree self-study and informal mentorship in foundation design but no formal credentials or documented training, would that be sufficient to satisfy the competence standard for structural footing design, and how should Engineer A or the contractor evaluate such informal experience?

AnalyticalIn response to Q401: Substantial post-degree self-study and informal mentorship in foundation design, without formal credentials or documented training, would not be sufficient to satisfy the competence standard for structural footing design under the code's requirements. Section II.2.a requires qualification by education or experience in the specific technical field, and the word 'experience' in this context implies documented, verifiable, and professionally supervised practice - not self-directed study or informal mentorship that cannot be independently assessed. The structural footing context is particularly demanding because the consequences of incompetence are catastrophic and irreversible, which means the competence threshold must be reliably verifiable rather than self-reported. Engineer A and the contractor evaluating such informal experience should apply a high degree of skepticism and require objective evidence: documented project history, references from supervising engineers, and ideally formal continuing education records. Absent such documentation, informal self-study claims should not override the reasonable doubt that Engineer B's chemical engineering background and absence of formal structural training creates. The burden of demonstrating competence rests on Engineer B, and unverifiable informal experience does not discharge that burden.

If Engineer B had accepted the structural footing assignment but immediately sub-delegated the actual design work to a qualified structural engineer while retaining overall coordination responsibility, would that arrangement have resolved the ethical problem, or would Engineer B's inability to competently oversee and seal the work still constitute an ethical violation?

AnalyticalIn response to Q402: If Engineer B had accepted the structural footing assignment but immediately sub-delegated the actual design work to a qualified structural engineer while retaining overall coordination responsibility, that arrangement would not have resolved the ethical problem. The core issue is not merely who performs the physical design calculations but who bears the professional responsibility for reviewing, evaluating, and sealing the work. Engineer B's inability to competently oversee and seal the structural footing design means that any sub-delegation would be nominal rather than substantive - Engineer B would be affixing his seal to plans dealing with subject matter in which he is not competent, which is directly prohibited by Section II.2.b. Furthermore, the sole-purpose nature of Engineer B's engagement means that his coordination role has no independent content beyond the structural footing design itself; there is no broader project coordination function that would justify invoking the Section II.2.c exception. The sub-delegation arrangement would create a false appearance of professional oversight while providing none of its substance, which is arguably more ethically problematic than straightforward incompetent practice because it actively misleads the contractor and the public about the quality of professional review.

If Engineer A had not reported concerns to the contractor and the structural footings subsequently failed causing injury, would Engineer A bear any ethical or professional responsibility for the harm, given that Engineer A possessed knowledge of Engineer B's apparent incompetence?

AnalyticalIn response to Q403: If Engineer A had not reported concerns to the contractor and the structural footings subsequently failed causing injury, Engineer A would bear significant ethical responsibility for the harm. Engineer A possessed knowledge - grounded in objective credential investigation - that Engineer B lacked apparent competence for the structural footing assignment. The engineering profession's self-policing obligation and the public welfare paramount principle together create an affirmative duty to act upon such knowledge. Silence in the face of a known, foreseeable public safety risk is not ethically neutral; it constitutes a failure of the professional duty to protect public welfare. The fact that Engineer A did not design the footings himself does not insulate him from ethical responsibility, because his knowledge of Engineer B's apparent incompetence created an independent obligation to intervene. This analysis reinforces the Board's implicit conclusion that Engineer A's reporting to the contractor was not merely permissible but ethically required. Failure to report would have transformed Engineer A from a bystander into a passive participant in the competence violation, with corresponding ethical culpability for foreseeable harms that his intervention could have prevented.

If the contractor had ignored Engineer A's reported concerns and directed Engineer A to continue working on the project alongside Engineer B, would Engineer A's ethical obligation require withdrawal from the project entirely, and at what point does continued participation become complicity in the competence violation?

AnalyticalIn response to Q404: If the contractor ignored Engineer A's reported concerns and directed Engineer A to continue working on the project alongside Engineer B, Engineer A's ethical obligation would require serious consideration of withdrawal from the project, and continued participation would risk becoming complicity in the competence violation. The threshold for required withdrawal is reached when Engineer A has exhausted available internal remedies - reporting to the contractor - and the contractor has not only failed to act but has affirmatively directed continuation of the problematic arrangement. At that point, Engineer A's continued participation lends professional credibility and implicit endorsement to a project in which a known competence violation is ongoing. The project withdrawal obligation is not triggered by mere disagreement with a client decision; it is triggered when continued participation would require Engineer A to act contrary to the code's requirements or to remain silent about an ongoing public safety threat. Before withdrawing, Engineer A should also escalate to the state licensing board, because withdrawal alone does not protect the public from the ongoing risk - it only removes Engineer A from personal complicity. The combination of licensing board notification and project withdrawal represents the full discharge of Engineer A's ethical obligations when contractor-level remedies have failed.
Decisions & Arguments (6)
View Extraction

Should Engineer B accept the structural footing design assignment based on holding a valid PE license, or decline the assignment and disclose his chemical engineering background to the contractor before any design work commences?

Options considered:
O1 Proactively inform the contractor of his chemical engineering background and absence of structural engineering training before any design work commences, and decline the structural footing assignment, allowing the contractor to retain a qualified structural engineer. Board's choice
O2 Accept the structural footing assignment on the basis that a valid PE license legally authorizes the work, treating licensure as sufficient qualification and proceeding with the design without disclosing the chemical engineering background.
O3 Accept the engagement but immediately retain a qualified structural engineer to perform the actual footing design, positioning Engineer B as the coordinating professional who reviews and seals the work, invoking the consulting-context flexibility available under II.2.c.
Argument structure:
Warrants

The ethics code (II.2.a) requires engineers to undertake assignments only when qualified by education or experience in the specific technical field, a higher standard than mere PE licensure. The sole-purpose nature of the retention forecloses any organizational remedy such as sub-delegation, because Engineer B was retained specifically to design the footings and cannot ethically seal work he lacks the competence to perform or oversee. The deontological duty is violated at the moment of acceptance, independent of whether the resulting design might prove adequate.

Rebuttals

Uncertainty arises if Engineer B possesses undisclosed post-degree training in foundation design, relevant cross-disciplinary experience, or informal mentorship that could satisfy a competence threshold not captured by formal credentials alone. Additionally, if the contractor's retention process included qualification representations that Engineer B reasonably believed satisfied disclosure, the proactive disclosure obligation may be partially mitigated, though not the underlying competence obligation.

Grounds

Engineer B holds a PE license but his academic degree and professional experience are confined to chemical engineering. He has no established subsequent training in foundation design. The contractor has retained him solely and exclusively for structural footing design on an industrial facility. Prior BER precedents establish that PE licensure alone does not satisfy the ethical competence requirement for cross-discipline structural work.

Engineer B Cross-Discipline Structural Footing Assignment Acceptance Refusal Obligation Consulting Practice Sole-Purpose Retention Competence Scope Non-Expandability Obligation

Should Engineer A first directly confront Engineer B and recommend withdrawal from the structural footing assignment before reporting concerns to the contractor, or should Engineer A report concerns directly to the contractor given the structural safety risk without first confronting Engineer B?

Options considered:
O1 Directly confront Engineer B with the credential findings, recommend that Engineer B withdraw from the structural footing assignment, and escalate to the contractor only if Engineer B refuses, honoring the collegial-first sequencing norm while preserving the escalation pathway. Board's choice
O2 Bypass direct confrontation with Engineer B and report competence concerns immediately to the contractor, on the basis that the structural safety stakes are too high to risk delay and that the contractor, as the retaining party, is the appropriate decision-maker.
O3 Defer both direct confrontation and contractor reporting pending further investigation to establish whether Engineer B has any undisclosed structural training or experience, applying incomplete situational knowledge restraint to avoid acting on potentially unverified assumptions.
Argument structure:
Warrants

The peer confrontation sequencing norm requires Engineer A to first directly confront Engineer B and recommend withdrawal before escalating to the contractor or authorities, reflecting the profession's commitment to collegial self-regulation and procedural fairness. However, the public welfare paramount principle and the structural safety context mean that Engineer A's tolerance for delay at each escalation stage must be significantly compressed. The peer competence challenge obligation activates upon reasonable doubt grounded in objective evidence, which Engineer A's credential investigation has produced. The engineering self-policing obligation and the public welfare paramount principle together create an affirmative duty to act.

Rebuttals

Uncertainty is created by the possibility that Engineer B has undisclosed structural competence that direct confrontation would reveal, making the sequencing norm particularly valuable here. Conversely, if construction is already underway and delay would allow irreversible harm, the public welfare principle may compress or override the confrontation-first sequence. The Board's silence on whether Engineer A actually confronted Engineer B before reporting to the contractor leaves open whether the sequencing obligation was fully discharged.

Grounds

Engineer A has investigated Engineer B's qualifications and confirmed that Engineer B's degree is in chemical engineering with no apparent subsequent training in foundation design. Engineer A has reservations concerning Engineer B's competence to design the structural footings. The structural footing design is safety-critical, failures can cause catastrophic and irreversible harm to building occupants. Engineer A has not yet confronted Engineer B directly or reported to the contractor.

Engineer A Direct Confrontation of Engineer B Recommending Withdrawal Obligation Peer Competence Challenge Direct Confrontation Before Authority Escalation Sequencing Obligation

If the contractor takes no corrective action after Engineer A reports concerns about Engineer B's competence, should Engineer A escalate to the state licensing board and withdraw from the project, or continue participation while deferring to the contractor's authority over the retention decision?

Options considered:
O1 Notify the state licensing board of the ongoing competence violation and withdraw from the project, recognizing that contractor inaction has exhausted internal remedies and that continued participation would constitute complicity in a foreseeable public safety harm. Board's choice
O2 Withdraw from the project to avoid personal complicity but refrain from notifying the state licensing board, treating withdrawal as a sufficient discharge of Engineer A's ethical obligations and leaving further action to the contractor's discretion.
O3 Continue working on the project under the contractor's direction while formally documenting Engineer A's objections in writing to the contractor, on the basis that the contractor bears primary responsibility for the retention decision and Engineer A's reporting obligation was discharged by the initial notification.
Argument structure:
Warrants

The progressive escalation norm establishes that Engineer A's ethical obligation does not terminate at contractor notification: if the contractor fails to act, the obligation advances to state licensing board notification. The public welfare paramount principle, combined with the catastrophic and irreversible nature of structural footing failure, materially lowers the escalation threshold beyond what would apply to a less safety-critical assignment. Continued participation after contractor refusal to act lends professional credibility and implicit endorsement to an ongoing competence violation, risking complicity. Withdrawal alone is insufficient because it does not protect the public from the ongoing risk, licensing board notification is independently required.

Rebuttals

Uncertainty is created by the absence of a defined BER standard specifying when contractor inaction crosses the threshold triggering mandatory external reporting, and by ambiguity about whether project withdrawal is required immediately upon contractor inaction or only after licensing board notification also fails to produce corrective action. The point at which continued participation becomes complicity is not fixed, it depends on whether Engineer A's role provides any meaningful ability to mitigate the risk from within the project.

Grounds

Engineer A has reported competence concerns to the contractor. The contractor has received the safety concern but has taken no corrective action and directed Engineer A to continue on the project. Engineer B has not withdrawn. Construction is underway or imminent. Structural footing failures can cause catastrophic, irreversible harm to building occupants who have no ability to protect themselves from the competence deficiency. Engineer A has exhausted the contractor-level internal remedy.

Engineer A Client and Authority Escalation Upon Engineer B Refusal Obligation Engineer A Project Withdrawal If Competence Concerns Unmet Obligation

Should Engineer B attempt to cure the structural footing competence deficiency by sub-delegating the actual design to a qualified structural engineer while retaining coordination responsibility, or must Engineer B recognize that the sole-purpose nature of his engagement makes sub-delegation an ethically unavailable remedy and decline the assignment entirely?

Options considered:
O1 Recognize that the sole-purpose nature of the engagement forecloses sub-delegation as an ethical remedy, decline the structural footing assignment entirely, and inform the contractor that a qualified structural engineer must be retained directly for the work. Board's choice
O2 Accept the engagement and immediately retain a qualified structural engineer to perform the actual footing design calculations, invoking the II.2.c consulting-practice flexibility that permits prime professionals to engage specialists for competence gaps, while retaining coordination and sealing responsibility.
O3 Accept the engagement but proactively disclose to the contractor that a qualified structural engineer will perform the design work under Engineer B's coordination, allowing the contractor to make an informed decision about whether this arrangement satisfies the project's technical and liability requirements.
Argument structure:
Warrants

The II.2.c coordination remedy applies to prime professionals with genuine coordination competence who can meaningfully oversee and evaluate specialist work, it is not a mechanism for incompetent engineers to launder out-of-discipline assignments through nominal delegation. Engineer B's inability to competently oversee, evaluate, or seal the delegated structural work means sub-delegation would be nominal rather than substantive, violating II.2.b's prohibition on affixing signatures to plans in subject matter where the engineer is not competent. The sole-purpose engagement eliminates the organizational structure through which consulting flexibility could legitimately route work to qualified specialists, the circularity is decisive. Sub-delegation that creates a false appearance of oversight is more ethically problematic than straightforward incompetent practice.

Rebuttals

Uncertainty arises because BER 71-2 permits prime professionals to retain specialists for competence gaps in multi-scope engagements, and it is unresolved whether that precedent's logic could extend to a sole-purpose engagement if Engineer B possessed sufficient substantive domain background to meaningfully oversee a qualified subconsultant's structural work. If Engineer B had cross-disciplinary exposure sufficient to evaluate the specialist's output, even without formal structural credentials, the circularity argument might be weakened.

Grounds

Engineer B was retained specifically and exclusively to design the structural footings. His degree and background are in chemical engineering with no apparent subsequent training in foundation design. The consulting-practice flexibility principle (BER 71-2, 78-5) permits prime professionals to retain specialists for competence gaps in multi-scope engagements. Engineer B's engagement has no broader project coordination scope beyond the structural footing design itself.

Engineer B Sole-Purpose Structural Footing Sub-Delegation Infeasibility Recognition Obligation Sole-Purpose Retained Engineer Cross-Discipline Sub-Delegation Infeasibility Recognition Obligation

Should the construction contractor independently verify Engineer B's structural engineering qualifications before retention, or rely on Engineer B's PE license as sufficient evidence of competence for the structural footing assignment?

Options considered:
O1 Independently investigate Engineer B's academic degree discipline and documented structural engineering experience before finalizing the retention, requiring evidence of domain-specific qualification beyond general PE licensure before assigning the structural footing task. Board's choice
O2 Treat Engineer B's valid PE license as sufficient evidence of competence for the structural footing assignment, on the basis that professional licensure is the established legal standard for engineering qualification and that the contractor is not positioned to second-guess the licensing board's determination.
O3 Require Engineer B to provide a written self-certification of competence for structural footing design before retention, placing the verification burden on Engineer B's professional representation rather than conducting an independent credential investigation, consistent with the profession's primary self-policing norm.
Argument structure:
Warrants

The contractor, operating in a design-build coordination role, assumed an oversight function that included a duty to confirm that each retained engineer possessed qualifications aligned to the specific technical task assigned, a degree-to-task alignment verification obligation. Retaining a chemical engineer for structural footing design without investigating subsequent structural training represents a verification failure that amplifies systemic public safety risk. However, the contractor's verification failure operates in parallel with, and does not diminish or displace, the individual engineers' competence obligations, the engineering profession's self-policing norms exist precisely because clients often lack the technical sophistication to independently assess cross-discipline competence deficiencies.

Rebuttals

Uncertainty arises from the risk that recognizing a robust contractor-screening obligation could dilute engineer self-policing norms: if contractors are expected to catch competence problems, engineers may assume external screening will substitute for professional self-assessment. The absence of clear BER precedent allocating shared responsibility between a negligent retaining contractor and the individual engineers' independent obligations also creates analytical uncertainty about the relative weight of the contractor's duty.

Grounds

The construction contractor retained Engineer B for the sole and exclusive purpose of structural footing design in a design-build project. Engineer B holds a PE license but his degree and experience are in chemical engineering. The contractor did not investigate whether Engineer B's academic degree and professional experience aligned with the structural engineering demands of the task before retention. Engineer A subsequently reported competence concerns to the contractor.

Construction Contractor Degree-to-Task Alignment Verification Before Engineer B Retention Obligation Contractor Competence Verification Duty Before Specialist Retention Constraint

Has Engineer A's credential investigation produced a sufficient objective basis to activate the peer competence challenge obligation and proceed with confronting Engineer B, or must Engineer A conduct further investigation before concluding that reasonable doubt about Engineer B's structural competence is warranted?

Options considered:
O1 Treat the combination of Engineer B's chemical engineering degree and absence of any apparent subsequent training in foundation design as a sufficient objective basis for reasonable doubt, and proceed to directly confront Engineer B and recommend withdrawal from the structural footing assignment. Board's choice
O2 Defer the peer competence challenge pending additional investigation, including direct inquiry to Engineer B about any post-degree structural training, review of Engineer B's project history, and consultation with the contractor about the basis for Engineer B's retention, before concluding that a reasonable basis for challenge exists.
O3 Rather than unilaterally concluding that reasonable doubt exists, formally request that Engineer B provide documentation of his structural engineering qualifications, including any post-degree training, relevant project experience, or continuing education, before deciding whether to activate the peer competence challenge obligation.
Argument structure:
Warrants

The peer competence challenge obligation activates upon reasonable doubt grounded in objective evidence, or the absence of evidence, following diligent inquiry. The combination of positive evidence of a non-structural background (chemical engineering degree) and absence of evidence of remedial qualification (no apparent subsequent training in foundation design) is sufficient to activate the obligation. The code's protective purpose for public safety means the standard is reasonable doubt, not certainty of incompetence. Epistemic caution is appropriate before investigation but cannot serve as a perpetual shield against action once investigation has produced a reasonable basis for concern. The burden of demonstrating competence rests on Engineer B, not on Engineer A to prove incompetence.

Rebuttals

Uncertainty is generated by the absence of a defined evidentiary threshold in the NSPE Code distinguishing sufficient from insufficient grounds for reasonable doubt, and by the possibility that Engineer B has informal experience or undisclosed training that Engineer A's investigation did not surface. The reasonable-doubt standard activates the obligation but does not specify what quantum of credential evidence is required, leaving open whether Engineer A's investigation was sufficiently thorough before concluding that a reasonable basis existed.

Grounds

Engineer A has investigated Engineer B's qualifications and established that Engineer B's degree is in chemical engineering. Engineer A has been unable to establish that Engineer B has any apparent subsequent training in foundation design. Engineer A has reservations concerning Engineer B's competence to design the structural footings. The structural footing assignment is safety-critical. No BER precedent specifies the precise quantum of credential evidence required to activate the peer competence challenge obligation.

Engineer A Objective Credential Investigation Before Peer Competence Challenge Obligation Incomplete Situational Knowledge Restraint Balanced Against Reporting Obligation by Engineer A
13 sequenced 7 actions 6 events
Case timeline
A historical sequence of prior Board of Ethical Review cases (71-2, 78-5, and 85-3) spanning 1971 to 1985 exists as established precedent, shaping the ethical framework applied to Engineer A's current obligations. These precedents are exogenous facts that constrain the analysis.
The design/build industrial facility project begins, establishing the collaborative working relationship between Engineer A and the construction contractor. This initiates the professional context within which all subsequent events unfold.
The construction contractor separately retained Engineer B, a chemical engineer, to design structural footings for the industrial facility without apparent consultation with Engineer A. This decision placed a potentially unqualified engineer in a safety-critical structural design role.
Fulfills (1)
  • Exercised contractual authority to retain specialists for specific project tasks
Violates (3)
  • Duty to ensure retained engineers are competent for the specific task assigned
  • Duty to protect public safety by engaging qualified professionals for safety-critical structural work
  • Implicit duty to coordinate specialist retention with the prime engineer on a design/build project
Engineer B, holding a chemical engineering degree with no apparent subsequent training in foundation design, accepted a commission specifically and solely to design structural footings for an industrial facility. This decision placed Engineer B in a role outside their established area of competence.
Fulfills (1)
  • Held a valid professional engineering license satisfying the legal threshold for practice
Violates (4)
  • NSPE Code Section II.2., obligation to perform services only in areas of competence
  • NSPE Code Section II.2.a., obligation to undertake assignments only when qualified by education or experience in the specific technical fields involved
  • Obligation to hold public safety paramount by declining work for which one is not competent
  • Professional obligation to self-assess and decline engagements outside one's expertise
Engineer A actively investigated Engineer B's educational background and professional experience to assess whether Engineer B possessed the competence necessary to design structural footings. Engineer A was unable to establish any apparent subsequent training in foundation design beyond Engineer B's chemical engineering degree.
Fulfills (3)
  • Obligation to form an objective, evidence-based judgment before reporting concerns about a colleague
  • Obligation to hold public safety paramount by proactively assessing whether structural design work is being performed by a competent engineer
  • Obligation to act on knowledge of potential Code violations by another engineer
Engineer A's investigation yields a finding: no evidence of training or competency in foundation design exists in Engineer B's background, despite Engineer B being a chemical engineer assigned to design structural footings. This is the evidentiary outcome of Engineer A's investigative action.
After investigating Engineer B's qualifications and finding no apparent foundation design training, Engineer A reported his competence concerns about Engineer B to the construction contractor. This was Engineer A's first formal escalation of the issue to a party with authority over the project.
Fulfills (4)
  • Obligation to report known or reasonably suspected competence deficiencies that endanger public safety
  • Obligation to notify the client/contractor of concerns affecting the project
  • Obligation to take action when aware of a potential Code violation by another engineer
  • Obligation to hold public safety paramount in all professional decisions
The contractor becomes formally aware of Engineer A's concerns about Engineer B's qualifications for foundation design, creating a documented moment of organizational knowledge about the potential competency risk. This is the outcome of Engineer A's reporting action.
As a prospective required action identified in the Discussion, Engineer A must directly confront Engineer B to communicate competence concerns and formally recommend that Engineer B withdraw from the structural footing design assignment. This is a peer-level professional intervention prior to further escalation.
Fulfills (4)
  • Obligation to directly notify the engineer whose conduct raises ethical concerns before escalating to third parties
  • Obligation to give Engineer B the opportunity to self-correct and withdraw voluntarily
  • Obligation to act affirmatively to protect public safety from potentially incompetent structural design
  • Obligation to uphold professional standards within the engineering community
Following Engineer A's direct confrontation and recommendation, Engineer B faces a prospective decision about whether to voluntarily withdraw from the structural footing design assignment. Acquiescence would resolve the ethical problem; refusal would trigger Engineer A's obligation to escalate to the client and authorities.
Fulfills (2)
  • If withdrawing: fulfills NSPE Code Section II.2. and II.2.a. obligations to perform only within areas of competence
  • If withdrawing: fulfills obligation to hold public safety above personal or financial interest
Violates (3)
  • If refusing: continues violation of NSPE Code Section II.2. and II.2.a.
  • If refusing: violates obligation to hold public safety paramount
  • If refusing: disregards a direct, Code-grounded recommendation from a peer engineer
Following Engineer A's direct confrontation of Engineer B, an outcome is produced: Engineer B either acknowledges the competency concern and agrees to withdraw, or resists and continues with the assignment. This outcome state determines the trajectory of subsequent escalation.
If Engineer B refuses to withdraw and the contractor fails to act, the conditions for mandatory escalation to the client and relevant authorities are automatically met, transforming Engineer A's optional escalation into a binding professional obligation. This is an automatic trigger event produced by the combined failure of prior resolution attempts.
If Engineer B refuses to withdraw, Engineer A is obligated to escalate the competence concern beyond the contractor to the client and to relevant professional or regulatory authorities. This prospective action represents a formal, institutional-level escalation of the ethical violation.
Fulfills (4)
  • NSPE Code obligation to bring known ethical violations and competence concerns to the attention of appropriate authorities
  • Obligation to hold public safety paramount above project continuity and client relationships
  • Obligation to take all available steps to prevent unqualified structural design from proceeding
  • Obligation to act when direct peer confrontation has failed to resolve the ethical problem
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 working alongside a construction contractor on a design/build project for an industrial facility. During construction, the contractor separately retained Engineer B to design structural footings for the facility. Engineer B holds a PE license, but his degree and professional background are in chemical engineering, and your review has not surfaced any subsequent training or experience in foundation design. This gap raises a genuine question about whether Engineer B has the competence required for this structural assignment. The decisions ahead will determine how you respond to that concern, and what obligations you carry toward the contractor, your colleague, and the public.

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: Competency-Challenging Co-Project Engineer

Tension between Engineer A Direct Confrontation of Engineer B Recommending Withdrawal Obligation and Peer Competence Challenge Direct Confrontation Before Authority Escalation Sequencing Obligation

Engineer A faces a sequencing dilemma between two legitimate obligations. The duty to objectively investigate Engineer B's credentials before mounting a competence challenge requires time, diligence, and epistemic caution. However, if structural footing design work is already underway or imminent, delay in direct confrontation may allow incompetent work to proceed and endanger public safety. Premature confrontation without credential verification risks being unfair to Engineer B and professionally unjustified. Waiting for full investigation may allow harm to materialize. These obligations pull in opposite temporal directions, forcing Engineer A to choose between procedural fairness and urgency of safety intervention.

Tension between Engineer A Client and Authority Escalation Upon Engineer B Refusal Obligation and Engineer A Project Withdrawal If Competence Concerns Unmet Obligation

Engineer A is obligated to escalate to the client and relevant authorities if Engineer B refuses to withdraw from the out-of-competence assignment. However, the constraint that non-imminent danger does not compel immediate reporting — and that collegial direct engagement must precede authority escalation — creates a genuine tension. If Engineer A escalates too quickly, they violate the graduated escalation norm and risk damaging professional collegiality and Engineer B's reputation unjustly. If Engineer A waits through the collegial process and Engineer B remains unresponsive, the window for preventing harm may close. The dilemma is whether the structural footing risk crosses the threshold of imminence that would justify bypassing the collegial constraint.

Tension between Engineer A Objective Credential Investigation Before Peer Competence Challenge Obligation and Incomplete Situational Knowledge Restraint Balanced Against Reporting Obligation by Engineer A

Engineer B Roles in this case: Cross-Discipline Out-of-Competence Structural Design Engineer

Tension between Engineer B Cross-Discipline Structural Footing Assignment Acceptance Refusal Obligation and Consulting Practice Sole-Purpose Retention Competence Scope Non-Expandability Obligation

Engineer B holds a valid PE license, which may create a surface-level appearance of professional authorization and social legitimacy for accepting the structural footing assignment. This creates a genuine dilemma: the obligation to refuse the assignment on competence grounds conflicts with the institutional signal of licensure that may lead Engineer B, the contractor, and other parties to rationalize acceptance. The PE license does not confer domain-specific structural competence, yet its existence exerts normative pressure that can undermine the refusal obligation. Fulfilling the refusal obligation requires Engineer B to actively override the implicit authorization signal of licensure, which is psychologically and institutionally difficult.

Tension between Engineer A Direct Confrontation of Engineer B Recommending Withdrawal Obligation and Peer Competence Challenge Direct Confrontation Before Authority Escalation Sequencing Obligation

Engineer A faces a sequencing dilemma between two legitimate obligations. The duty to objectively investigate Engineer B's credentials before mounting a competence challenge requires time, diligence, and epistemic caution. However, if structural footing design work is already underway or imminent, delay in direct confrontation may allow incompetent work to proceed and endanger public safety. Premature confrontation without credential verification risks being unfair to Engineer B and professionally unjustified. Waiting for full investigation may allow harm to materialize. These obligations pull in opposite temporal directions, forcing Engineer A to choose between procedural fairness and urgency of safety intervention.

Tension between Engineer B Sole-Purpose Structural Footing Sub-Delegation Infeasibility Recognition Obligation and Sole-Purpose Retained Engineer Cross-Discipline Sub-Delegation Infeasibility Recognition Obligation

Tension between Construction Contractor Degree-to-Task Alignment Verification Before Engineer B Retention Obligation and Contractor Competence Verification Duty Before Specialist Retention Constraint

Tension between Engineer A Client and Authority Escalation Upon Engineer B Refusal Obligation and Engineer A Project Withdrawal If Competence Concerns Unmet Obligation

Engineer A is obligated to escalate to the client and relevant authorities if Engineer B refuses to withdraw from the out-of-competence assignment. However, the constraint that non-imminent danger does not compel immediate reporting — and that collegial direct engagement must precede authority escalation — creates a genuine tension. If Engineer A escalates too quickly, they violate the graduated escalation norm and risk damaging professional collegiality and Engineer B's reputation unjustly. If Engineer A waits through the collegial process and Engineer B remains unresponsive, the window for preventing harm may close. The dilemma is whether the structural footing risk crosses the threshold of imminence that would justify bypassing the collegial constraint.

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

Engineer B holds a valid PE license, which may create a surface-level appearance of professional authorization and social legitimacy for accepting the structural footing assignment. This creates a genuine dilemma: the obligation to refuse the assignment on competence grounds conflicts with the institutional signal of licensure that may lead Engineer B, the contractor, and other parties to rationalize acceptance. The PE license does not confer domain-specific structural competence, yet its existence exerts normative pressure that can undermine the refusal obligation. Fulfilling the refusal obligation requires Engineer B to actively override the implicit authorization signal of licensure, which is psychologically and institutionally difficult.

Engineer A faces a sequencing dilemma between two legitimate obligations. The duty to objectively investigate Engineer B's credentials before mounting a competence challenge requires time, diligence, and epistemic caution. However, if structural footing design work is already underway or imminent, delay in direct confrontation may allow incompetent work to proceed and endanger public safety. Premature confrontation without credential verification risks being unfair to Engineer B and professionally unjustified. Waiting for full investigation may allow harm to materialize. These obligations pull in opposite temporal directions, forcing Engineer A to choose between procedural fairness and urgency of safety intervention.

Tension between Construction Contractor Degree-to-Task Alignment Verification Before Engineer B Retention Obligation and Contractor Competence Verification Duty Before Specialist Retention Constraint

Engineer A is obligated to escalate to the client and relevant authorities if Engineer B refuses to withdraw from the out-of-competence assignment. However, the constraint that non-imminent danger does not compel immediate reporting — and that collegial direct engagement must precede authority escalation — creates a genuine tension. If Engineer A escalates too quickly, they violate the graduated escalation norm and risk damaging professional collegiality and Engineer B's reputation unjustly. If Engineer A waits through the collegial process and Engineer B remains unresponsive, the window for preventing harm may close. The dilemma is whether the structural footing risk crosses the threshold of imminence that would justify bypassing the collegial constraint.

Opening States (10)
Engineer B Chemical Engineer Structural Footing Assignment Incompetence Engineer A Unverified Competence Concern About Engineer B Engineer A Peer Competence Challenge Reporting Obligation Activated Engineer B Outside Area of Competence for Structural Footing Design Sole-Purpose Engagement Precluding Competence Delegation State Consulting Context Competence Remediation Flexibility State Engineer B Domain-Specific Incompetence in Structural Engineering Engineer B Sole-Purpose Structural Footing Engagement Precluding Delegation Engineer A Peer Competence Challenge Reporting Obligation Consulting Context Competence Remediation Flexibility - General Principle
Summary
  • Engineers have an affirmative duty to challenge peer competency when public safety is at risk, even when doing so creates professional friction or disrupts project relationships.
  • The scope of a consulting engagement does not ethically permit an engineer to accept work outside their demonstrated competence simply because a client or contractor requests it.
  • When direct peer confrontation fails to resolve competency concerns, escalation to the contracting authority is not only permissible but obligatory under the NSPE Code's public safety mandate.