Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe 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.
Provisions (5)
View Extraction-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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 ExtractionExplicit 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.
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.
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.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions (2 board)
View ExtractionWould it be ethical 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?
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?
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?
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?
Did Engineer A have 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?
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?
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?
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?
Cross-cutting analytical questions (8)
These questions consider the case as a whole rather than a specific board question above.
Show 8 cross-cutting questionsTheoretical (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?
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?
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?
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?
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?
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?
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?
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?
Decisions & Arguments (6)
View ExtractionShould 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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
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?
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.
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.
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.
Event Timeline (13)
Case timeline
- Exercised contractual authority to retain specialists for specific project tasks
- 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
- Held a valid professional engineering license satisfying the legal threshold for practice
- 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
- 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
- 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
- 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
- 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
- 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
- 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 ExtractionOpening 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.
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
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)
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.