Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Pipeline Steps
Overview
1 Contextual Framework
2 Normative Requirements
3 Temporal Dynamics Reconcile
4 Whole-Case Synthesis
Extraction Review Full View
Provenance
Signing and Sealing Plans Not Prepared by Engineer
Step 4 of 5
Entity Review

267

Entities

3

Provisions

1

Precedents

17

Questions

23

Conclusions

Stalemate

Transformation
Stalemate Competing obligations remain in tension without clear resolution
Engineer A is caught between an irreducible set of simultaneously valid but mutually incompatible rule-sets: the professional sealing obligation demands document-level personal verification; the organizational reality of the large firm makes that verification structurally impossible at current scale; the coordinating engineer provision of Section II.2.c offers a partial resolution but only under conditions (subordinate seals, multi-engineer model) the firm has not implemented; and the competence-prerequisite obligation retroactively implicates the role-acceptance decision itself. The Board's conclusions multiply the obligation set — adding affirmative restructuring duties, threshold role-acceptance duties, and differentiated duties for registered versus non-registered subordinates — without resolving which path Engineer A can actually execute within the firm's existing structure. The stakeholders (Engineer A, the firm, registered subordinates, non-registered subordinates, the public) remain trapped in an architecture of rules that generates violation regardless of which single obligation Engineer A prioritizes, because fulfilling any one fully requires restructuring conditions that the firm controls, not Engineer A alone.
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 (3)
View Extraction
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 25)
Obligation
Engineer A Case 85-3 Analogy Oversight Role Competence Prerequisite
II.2.a requires qualification by education or experience, directly supporting the obligation that Engineer A must be competent to oversee technical segments before accepting the chief engineer role.
Action
Accepting Chief Engineer Role
This provision governs whether the engineer is qualified by education or experience to undertake the chief engineer assignment.
State
Case 85-3. Chemical Engineer Accepting County Surveyor Role
This provision directly addresses undertaking assignments only when qualified, which is the core issue of a chemical engineer accepting a surveyor role outside their competence.
Obligation (3)
  • Engineer A Case 85-3 Analogy Oversight Role Competence Prerequisite
    II.2.a requires qualification by education or experience, directly supporting the obligation that Engineer A must be competent to oversee technical segments before accepting the chief engineer role.
  • Engineer A Sections II.2.a II.2.b II.2.c Integrated Reading Application
    II.2.a is one of the three mutually dependent provisions the Board was obligated to read together in analyzing Engineer A's sealing practices.
  • Engineer A Seal Affixation Professional Judgment Certification Failure
    II.2.a requires engineers to be qualified before undertaking assignments, which underpins the obligation that sealing constitutes certification of professional judgment and competence.
Action (1)
  • Accepting Chief Engineer Role
    This provision governs whether the engineer is qualified by education or experience to undertake the chief engineer assignment.
State (2)
  • Case 85-3. Chemical Engineer Accepting County Surveyor Role
    This provision directly addresses undertaking assignments only when qualified, which is the core issue of a chemical engineer accepting a surveyor role outside their competence.
  • Engineer A Competence-Trust Substitution for Verification
    This provision requires qualification in the specific technical fields involved, which Engineer A's reliance on trust rather than verified competence potentially violates.
Constraint (5)
  • Engineer A Section II.2.a Qualification Prerequisite Work Acceptance Sealing
    II.2.a directly creates the qualification prerequisite that constrains Engineer A to accept and seal only work in areas where he is qualified.
  • Engineer A Case 85-3 Oversight Role Domain Competence Prerequisite Analogical Application
    II.2.a underlies the analogical application requiring Engineer A to possess substantive qualifications in each technical domain before sealing.
  • Engineer A Section II.2.b Cognizance Understanding Sealing Legal Responsibility
    II.2.a's qualification requirement is directly linked to the cognizance and understanding standard imposed on Engineer A before sealing.
  • Engineer A BER Case 85-3 Cross-Domain Analogical Sealing Competence Application
    II.2.a provides the qualification standard that the Board applied analogically from Case 85-3 to Engineer A's cross-domain sealing practices.
  • Engineer A Sections II.2.a II.2.b II.2.c Mutually Dependent Integrated Reading Sealing
    II.2.a is one of the three provisions that must be read together in the integrated analysis of Engineer A's sealing practices.
Principle (3)
  • Competence Prerequisite for Role Acceptance Applied via Case 85-3 Analogy
    II.2.a. directly requires engineers to only undertake assignments when qualified, which is the core competence prerequisite principle invoked via Case 85-3.
  • Mutually Dependent Code Provision Reading in Responsible Charge Analysis
    II.2.a. is one of the three provisions the Board read simultaneously in its responsible charge analysis.
  • Dual-Mode Seal Authorization Principle Applied to Engineer A Sealing of Non-Registered Graduate Engineers
    II.2.a. underpins the competence requirement that must be satisfied before sealing work in any technical field.
Role (2)
  • Engineer A Chief Engineer Sealing Supervisor
    Engineer A must only undertake assignments where he is qualified, directly relevant when he seals plans across technical fields he may not be competent in.
  • Engineer A Out-of-Competence County Surveyor
    This provision is directly violated when an engineer with only chemical engineering background accepts a county surveyor role requiring different technical expertise.
Event (2)
  • Ethics Violation Determination Reached
    The determination of an ethics violation is grounded in whether the engineer was qualified by education or experience for the assignment undertaken.
  • Precedent Standard Activated
    This provision establishes the competence standard that becomes the precedent for evaluating future engineer qualification cases.
Resource (3)
  • BER Case 85-3
    BER Case 85-3 is cited as precedent for the principle that an engineer must possess qualifications and experience to competently perform a role, directly supporting the qualification requirement in II.2.a.
  • NSPE Code of Ethics Sections II.2.a, II.2.b, II.2.c
    This entity explicitly lists II.2.a as primary normative authority governing engineer qualification to accept work.
  • Engineering_Licensure_Law_Sealing_Instance
    The legal framework defining responsible charge and supervision requirements directly relates to whether an engineer is qualified to undertake an assignment.
Capability (4)
  • Engineer A General Direction vs Responsible Charge Distinction Deficit
    II.2.a requires undertaking assignments only when qualified, directly relating to whether Engineer A's level of involvement constituted sufficient qualification for the assignments he sealed.
  • Engineer A Case 85-3 Oversight Role Competence Prerequisite Cross-Context Application
    II.2.a requires qualification by education or experience, which is the competence prerequisite that Engineer A failed to apply to his oversight role as chief engineer.
  • Engineer A Three-Provision Mutually Dependent Code Reading
    II.2.a is one of the three mutually dependent provisions Engineer A was required to read together when analyzing his sealing obligations.
  • Engineer A Sealed Document Completeness Pre-Certification Self-Assessment Deficit
    II.2.a requires qualification before undertaking assignments, which necessitates the pre-certification self-assessment Engineer A failed to conduct.
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 88)
Obligation
Engineer A Responsible Charge Detailed Review Before Sealing Violation
II.2.b prohibits affixing signatures to plans not prepared under the engineer's direction and control, directly requiring detailed review before sealing.
Action
Sealing Registered Engineers' Plans Without Their Seals
This provision directly prohibits affixing a signature or seal to plans not prepared under the engineer's direction and control.
State
Engineer A Non-Registered Engineer Seal Delegation
This provision directly prohibits affixing signatures to plans not prepared under the engineer's direction and control, which is exactly what Engineer A does when sealing plans from non-registered engineers.
Obligation (14)
  • Engineer A Responsible Charge Detailed Review Before Sealing Violation
    II.2.b prohibits affixing signatures to plans not prepared under the engineer's direction and control, directly requiring detailed review before sealing.
  • Engineer A Detailed Review Sufficiency Standard Violation
    II.2.b requires that plans be under the engineer's direction and control, establishing the standard that review must be substantive and detailed before sealing.
  • Engineer A Organizational Scale Non-Excuse Violation
    II.2.b's prohibition on sealing plans not under one's direction and control cannot be waived by organizational size or project volume.
  • Engineer A Subordinate Competence Confidence Non-Substitution Violation
    II.2.b requires direction and control, not merely confidence in subordinates, as the basis for affixing a signature.
  • Engineer A General Direction Non-Equivalence to Responsible Charge Violation
    II.2.b requires actual direction and control, meaning general direction and supervision alone does not satisfy the provision's standard.
  • Engineer A Professional Accountability Acceptance for Directed Work
    II.2.b ties the right to seal to direction and control, which implies full professional accountability for work prepared under that authority.
  • Engineer A Responsible Charge Active Review Obligation Violation
    II.2.b directly requires that plans be prepared under the engineer's direction and control, mandating active review as part of responsible charge.
  • Engineer A Responsible Charge Direct Control Non-Registered Subordinate Sealing
    II.2.b requires direction and control over all plans sealed, including those prepared by non-registered graduate engineers.
  • Engineer A Chief Engineer Minimum Engagement Responsible Charge Sealing
    II.2.b requires plans to be prepared under the engineer's direction and control, establishing minimum engagement obligations for the chief engineer before sealing.
  • Engineer A Subordinate Competence Confidence Non-Substitution Sealing Review
    II.2.b mandates direction and control rather than trust in subordinates as the prerequisite for sealing plans.
  • Engineer A Seal Affixation Professional Judgment Certification Failure
    II.2.b directly prohibits sealing plans not prepared under the engineer's direction and control, which is the basis for the certification obligation.
  • Engineer A Sections II.2.a II.2.b II.2.c Integrated Reading Application
    II.2.b is one of the three mutually dependent provisions the Board was obligated to read together in analyzing Engineer A's sealing practices.
  • Engineer A Responsible Charge Direction Control Definition Application
    II.2.b's requirement of direction and control is the provision against which Engineer A's self-described general direction must be measured.
  • Engineer A Organizational Scale Non-Excuse Responsible Charge Sealing
    II.2.b's sealing prohibition applies regardless of organizational scale or concurrent project volume.
Action (4)
  • Sealing Registered Engineers' Plans Without Their Seals
    This provision directly prohibits affixing a signature or seal to plans not prepared under the engineer's direction and control.
  • Sealing Non-Registered Engineers' Plans
    This provision prohibits sealing plans prepared by others not under the engineer's direction and control, especially where competence may be lacking.
  • Consciously Omitting Detailed Design Review
    This provision is violated when an engineer seals documents without exercising direction and control, which omitting detailed review undermines.
  • Defining General Supervision Standard
    This provision is relevant because defining supervision as merely general may fall short of the direction and control required before affixing a seal.
State (9)
  • Engineer A Non-Registered Engineer Seal Delegation
    This provision directly prohibits affixing signatures to plans not prepared under the engineer's direction and control, which is exactly what Engineer A does when sealing plans from non-registered engineers.
  • Engineer A Insufficient Responsible Charge
    This provision prohibits signing plans not prepared under the engineer's direction and control, directly addressing Engineer A's practice of sealing without detailed design review.
  • Engineer A General Supervision Without Detailed Design Review
    This provision requires that signed plans be prepared under the engineer's direction and control, which Engineer A's pattern of only conceptual oversight may not satisfy.
  • Engineer A Organizational Scale Preventing Adequate Review
    This provision's requirement for direction and control is directly implicated when project volume makes adequate review impossible for the sealing engineer.
  • Responsible Charge Standard Clarification. Direction and Control Definition
    This provision is the source text whose terms direction and control are the subject of the Board's active definitional work.
  • Engineer A Responsible Charge Standard Clarification Active
    This provision's language is the normative standard being interpreted when determining what responsible charge requires for a Chief Engineer in a large organization.
  • Chief Engineer Managerial Responsible Charge Model. Engineer A
    This provision directly governs whether a chief engineer's managerial role constitutes sufficient direction and control to justify sealing subordinates' documents.
  • General Supervision Without Detailed Design Review. Engineer A (Discussion Elaboration)
    This provision's direction and control requirement is directly tested by Engineer A's supervisory pattern of conceptual direction without detailed design verification.
  • Non-Licensed Subordinate Work Requiring Registered Engineer Direct Supervision. Firm Obligation
    This provision requires that signed plans be prepared under the engineer's direction and control, establishing the firm's obligation when non-licensed engineers perform technical work.
Constraint (20)
  • Engineer A Section II.2.b Cognizance Understanding Sealing Legal Responsibility
    II.2.b directly creates the constraint requiring Engineer A to possess genuine understanding before signing, sealing, and assuming legal responsibility.
  • Engineer A Responsible Charge Active Engagement Sealing Constraint
    II.2.b's direction and control requirement directly creates the constraint that Engineer A must be actively engaged in engineering decisions before sealing.
  • Engineer A CADD Supervisory Direction-and-Control Seal Authorization Constraint
    II.2.b's direction and control language directly constrains Engineer A to exercise genuine direction and control before sealing subordinate-prepared plans.
  • Engineer A CADD Supervisory Seal Detailed Review Sufficiency Constraint
    II.2.b's requirement that plans be prepared under direction and control creates the detailed review sufficiency constraint beyond general supervision.
  • Engineer A General Direction Non-Equivalence Sealing Authorization Constraint
    II.2.b's direction and control standard directly establishes that Engineer A's general direction practice does not meet the sealing authorization threshold.
  • Engineer A General Direction Non-Equivalence Responsible Charge Sealing Authorization
    II.2.b creates the responsible charge standard against which Engineer A's general direction practice is found insufficient for sealing authorization.
  • Engineer A Non-Registered Engineer Sealing Direct Supervision Prerequisite Constraint
    II.2.b's direction and control requirement directly constrains Engineer A from sealing plans by non-registered engineers without direct supervision.
  • Engineer A Direction-and-Control Plain-Language Completeness Standard Sealing
    II.2.b's plain-language direction and control requirement directly creates the completeness standard approaching performance of the work itself.
  • Engineer A Seal Affixation Professional Judgment Ethical Certification
    II.2.b directly underlies the constraint that affixing a seal certifies professional judgment and discharge of direction and control obligations.
  • Engineer A Full Professional Responsibility Assumption Upon Sealing Constraint
    II.2.b directly creates the constraint that sealing plans prepared by subordinates assumes full professional responsibility for those plans.
  • Engineer A Responsible Charge Verification Sealing Constraint
    II.2.b's direction and control requirement directly creates the constraint that Engineer A must verify responsible charge before sealing.
  • Engineer A Subordinate Competence Confidence Non-Substitution Sealing Constraint
    II.2.b's direction and control requirement directly establishes that confidence in subordinates cannot substitute for the required review and check.
  • Engineer A Subordinate Competence Confidence Non-Substitution Sealing Review Responsible Charge
    II.2.b creates the direction and control standard that Engineer A's confidence in subordinates fails to satisfy for responsible charge sealing.
  • Engineer A Organizational Scale Non-Excuse Responsible Charge Sealing Constraint
    II.2.b's direction and control requirement directly establishes that organizational scale cannot excuse failure to meet the sealing standard.
  • Engineering Firm Organizational Scale Non-Excuse Responsible Charge Review Sealing
    II.2.b's direction and control requirement creates the standard that firm size does not justify failure to conduct required review before sealing.
  • Engineer A NCEE Model Law Direct Control Personal Supervision Responsible Charge Standard
    II.2.b's direction and control language directly corresponds to and is reinforced by the NCEE Model Law responsible charge definition.
  • Engineer A Chief Engineer Minimum Engagement Sealing Authorization
    II.2.b's direction and control requirement directly creates the minimum engagement standard constraining Engineer A's sealing authorization.
  • Engineering Firm Non-Registered Graduate Engineer Work Direct Control Personal Supervision Sealing Obligation
    II.2.b's direction and control requirement directly creates the firm's obligation to ensure direct control over non-registered graduate engineer work.
  • Engineer A Sections II.2.a II.2.b II.2.c Mutually Dependent Integrated Reading Sealing
    II.2.b is one of the three provisions that must be read together in the integrated analysis of Engineer A's sealing practices.
  • Engineer A Resource Constraint. Organizational Scale Review Impossibility
    II.2.b's direction and control requirement creates the standard against which the practical impossibility of full review is measured.
Principle (13)
  • Detailed Review Sufficiency Standard Invoked Against Engineer A Sealing Practice
    II.2.b. directly prohibits affixing signatures to plans not prepared under the engineer's direction and control, which is the standard Engineer A fails by not conducting detailed reviews.
  • Responsible Charge Engagement Standard Applied to Engineer A General Supervision
    II.2.b. requires direction and control, and Engineer A's general supervision falls short of that standard.
  • Subordinate Competence Confidence Non-Substitution Principle Invoked by Engineer A Rationalization
    II.2.b. requires actual direction and control, which cannot be replaced by confidence in subordinates as Engineer A claims.
  • Responsible Charge Integrity and Seal Authority Applied to Engineer A Certification Act
    II.2.b. is the provision that makes affixing a seal a certification of direction and control, which Engineer A violates.
  • Professional Accountability Invoked for Engineer A Organizational Scale Rationalization
    II.2.b. imposes a non-delegable obligation of direction and control that organizational size cannot excuse.
  • Public Welfare Paramount Invoked by Engineer A Sealing Without Adequate Review
    II.2.b. protects the public by ensuring plans are only sealed when prepared under the engineer's direction and control.
  • Mutually Dependent Code Provision Reading in Responsible Charge Analysis
    II.2.b. is one of the three provisions the Board read simultaneously in its responsible charge analysis.
  • Responsible Charge Direction and Control Definition Applied to Chief Engineer Sealing
    II.2.b.'s direction and control language is the textual basis for the Board's analysis of responsible charge meaning.
  • Chief Engineer Managerial Responsible Charge Standard Applied to Engineer A
    II.2.b. sets the direction and control requirement that defines what the chief engineer must do to lawfully seal plans.
  • Direct Control and Personal Supervision Obligation for Non-Registered Subordinate Work
    II.2.b. requires that plans be prepared under the engineer's direction and control, which is the obligation at issue for non-registered subordinates.
  • Seal and Signature as Professional Judgment Certification Beyond Legal Formality
    II.2.b. is the provision whose violation makes the seal a false certification of professional judgment.
  • Subordinate Competence Confidence Non-Substitution for Review Obligation Applied to Engineer A
    II.2.b. imposes a direction and control requirement that confidence in subordinates cannot satisfy.
  • Dual-Mode Seal Authorization Principle Applied to Engineer A Sealing of Non-Registered Graduate Engineers
    II.2.b. is the provision that authorizes sealing only when plans are prepared under the engineer's direction and control, which is the supervisory mode applicable to non-registered engineers.
Role (3)
  • Engineer A Chief Engineer Sealing Supervisor
    Engineer A affixing his seal to plans not prepared under his direct control and in subject matter where he may lack competence directly implicates this provision.
  • Registered Engineer Subordinate Plan Preparers
    These engineers do not affix their own seals to their work, raising the question of whether unsealed plans they prepare are being improperly sealed by another engineer.
  • Engineer A Out-of-Competence County Surveyor
    This provision applies when the county surveyor signs documents in technical areas outside his chemical engineering competence.
Event (4)
  • Registered Engineers Relieved of Sealing
    This provision directly addresses the impropriety of engineers affixing signatures to plans not prepared under their direction and control, which is what occurs when registered engineers are relieved of sealing duties.
  • Non-Registered Work Enters Public Record
    This provision prohibits signing documents not prepared under the engineers direction and control, which is the mechanism by which unverified work enters the public record.
  • Ethics Violation Determination Reached
    The ethics violation determination is directly tied to this provisions prohibition on sealing plans not prepared under the engineers direction and control.
  • Supervision Standard Institutionalized
    This provision establishes the direction and control requirement that forms the basis of the supervision standard being institutionalized.
Resource (10)
  • NSPE_Code_of_Ethics_Sealing_Supervision
    This entity directly governs Engineer A's ethical obligations when affixing his seal to plans prepared by others, which is the core subject of II.2.b.
  • CADD_Document_Sealing_Practice_Standard_Instance
    This entity establishes professional obligations and required level of review when an engineer seals plans prepared by subordinates, directly relevant to II.2.b's prohibition on sealing work not under direction and control.
  • Engineer_Stamped_Document_Responsibility_Standard_Instance
    This entity establishes the ethical and legal weight of affixing a professional seal, directly corresponding to II.2.b's requirement that engineers not affix signatures to documents outside their competence or control.
  • Engineering_Licensure_Law_Sealing_Instance
    This entity provides the legal framework for when a PE may seal plans prepared by others, directly supporting the direction and control requirement in II.2.b.
  • NCEE Model Law - Responsible Charge Definition
    The authoritative definition of responsible charge as direct control and personal supervision directly informs the meaning of direction and control as used in II.2.b.
  • Webster's New Collegiate Dictionary (1981 ed.) - Direction and Control Definitions
    This resource is explicitly used to establish the plain-language meaning of direction and control as they appear in II.2.b.
  • CADD Document Sealing Practice - Responsible Charge Norms
    This entity applies norms governing when a chief engineer may ethically seal documents prepared by subordinates, directly addressing the direction and control standard in II.2.b.
  • Engineering Intern Supervision - Direct Control and Personal Supervision Norm
    This entity establishes the ethical obligation for direct control and personal supervision of non-licensed engineers whose work is sealed, directly relevant to II.2.b.
  • NSPE Code of Ethics Sections II.2.a, II.2.b, II.2.c
    This entity explicitly lists II.2.b as primary normative authority governing the obligation to sign and seal only work within the engineer's cognizance.
  • Engineering_Intern_Supervision_Standard_Instance
    This entity defines the required scope of supervision a PE must provide before sealing work by non-registered engineers, directly relevant to II.2.b's direction and control requirement.
Capability (11)
  • Engineer A General Direction vs Responsible Charge Distinction Deficit
    II.2.b prohibits signing plans not prepared under the engineer's direction and control, directly implicating Engineer A's failure to distinguish general direction from responsible charge.
  • Engineer A Responsible Charge Active Engagement Deficit
    II.2.b requires plans to be prepared under the engineer's direction and control, which Engineer A violated by limiting involvement to conceptual direction.
  • Engineer A Direction-and-Control Definitional Precision
    II.2.b explicitly requires direction and control as a prerequisite for signing, making precise application of that definition directly required by this provision.
  • Engineer A Sealed Document Completeness Pre-Certification Self-Assessment Deficit
    II.2.b prohibits affixing signatures to documents where competence or direction and control are lacking, requiring the self-assessment Engineer A failed to perform.
  • Engineer A Seal Professional Judgment Certification Scope Self-Recognition
    II.2.b prohibits signing plans not prepared under the engineer's direction and control, which is the certification scope Engineer A failed to recognize when affixing his seal.
  • Engineer A Non-Registered Subordinate Direct Control Personal Supervision Sealing Prerequisite
    II.2.b requires plans to be prepared under the engineer's direction and control, which Engineer A failed to ensure for work by non-registered graduate engineers.
  • Engineer A Three-Provision Mutually Dependent Code Reading
    II.2.b is one of the three mutually dependent provisions Engineer A was required to read together when analyzing his sealing obligations.
  • Engineer A Organizational Scale Non-Excuse Capability Deficit
    II.2.b requires direction and control regardless of organizational scale, making organizational size an invalid excuse for failing to meet this standard.
  • Engineer A Subordinate Competence Confidence Non-Substitution Capability Deficit
    II.2.b requires direction and control of plan preparation, which cannot be substituted by confidence in subordinates' abilities.
  • Engineer A Supervisory Sealing Authority Structural Redesign Capability Deficit
    II.2.b prohibits sealing plans not under the engineer's direction and control, requiring structural redesign when that control cannot be achieved.
  • Engineer A Chief Engineer Project Inception Involvement Responsible Charge
    II.2.b requires plans to be prepared under the engineer's direction and control, which necessitates involvement from project inception as the chief engineer.
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 38)
Obligation
Engineer A Technical Segment Sealing Without Qualified Preparer Attribution
II.2.c explicitly requires that each technical segment be signed and sealed only by the qualified engineers who prepared it, directly establishing this obligation.
Action
Accepting Chief Engineer Role
This provision sets the conditions under which an engineer may accept responsibility for an entire project and seal its documents.
State
Technical Segment Sealing Attribution Obligation. Multi-Engineer Firm Projects
This provision directly establishes that each technical segment must be sealed only by the qualified engineer who prepared it, defining the firm's obligation in multi-engineer projects.
Obligation (5)
  • Engineer A Technical Segment Sealing Without Qualified Preparer Attribution
    II.2.c explicitly requires that each technical segment be signed and sealed only by the qualified engineers who prepared it, directly establishing this obligation.
  • Engineer A Sections II.2.a II.2.b II.2.c Integrated Reading Application
    II.2.c is one of the three mutually dependent provisions the Board was obligated to read together in analyzing Engineer A's sealing practices.
  • Engineer A Chief Engineer Minimum Engagement Responsible Charge Sealing
    II.2.c permits a chief engineer to seal an entire project only when each technical segment is sealed by its qualified preparer, setting minimum engagement standards.
  • Engineer A Responsible Charge Direct Control Non-Registered Subordinate Sealing
    II.2.c's requirement that technical segments be sealed by qualified engineers who prepared them applies to work done by non-registered subordinates who cannot themselves seal.
  • Engineer A Professional Accountability Acceptance for Directed Work
    II.2.c conditions the chief engineer's authority to seal the entire project on proper attribution and qualification of each segment, implying full accountability for coordinated work.
Action (4)
  • Accepting Chief Engineer Role
    This provision sets the conditions under which an engineer may accept responsibility for an entire project and seal its documents.
  • Sealing Registered Engineers' Plans Without Their Seals
    This provision requires that each technical segment be signed and sealed by the qualified engineer who prepared it, making sealing others plans without their seals improper.
  • Sealing Non-Registered Engineers' Plans
    This provision requires each segment to be sealed only by qualified engineers who prepared it, which non-registered engineers cannot satisfy.
  • Defining General Supervision Standard
    This provision implies a higher standard of oversight than mere general supervision for legitimately coordinating and sealing an entire project.
State (5)
  • Technical Segment Sealing Attribution Obligation. Multi-Engineer Firm Projects
    This provision directly establishes that each technical segment must be sealed only by the qualified engineer who prepared it, defining the firm's obligation in multi-engineer projects.
  • Chief Engineer Managerial Responsible Charge Model. Engineer A
    This provision permits coordination responsibility and overall sealing by a chief engineer only when each technical segment is separately sealed by its qualified preparer, directly governing Engineer A's model.
  • Engineer A Non-Registered Engineer Seal Delegation
    This provision requires each technical segment to be sealed by the qualified engineer who prepared it, which is violated when non-registered engineers cannot independently seal their own segments.
  • Non-Licensed Subordinate Work Requiring Registered Engineer Direct Supervision. Firm Obligation
    This provision's requirement that each segment be sealed only by its qualified preparer directly creates the firm obligation when non-licensed engineers cannot seal their own work.
  • Engineer A Responsible Charge Standard Clarification Active
    This provision defines the permissible coordination model for a chief engineer, making it central to clarifying what responsible charge requires at the organizational level.
Constraint (3)
  • Engineering Firm Technical Segment Sealing Attribution Obligation Constraint
    II.2.c directly creates the obligation that each technical segment be sealed only by the qualified engineer who prepared it.
  • Engineer A Technical Segment Qualified Preparer Exclusive Sealing Section II.2.c
    II.2.c directly creates the constraint that each technical segment must be sealed exclusively by the qualified engineer who prepared that segment.
  • Engineer A Sections II.2.a II.2.b II.2.c Mutually Dependent Integrated Reading Sealing
    II.2.c is one of the three provisions that must be read together in the integrated analysis of Engineer A's sealing practices.
Principle (4)
  • Technical Segment Sealing by Qualified Preparers Applied in Large-Firm Context
    II.2.c. directly requires each technical segment to be signed and sealed only by the qualified engineer who prepared it, which is the principle the Board reiterated.
  • Mutually Dependent Code Provision Reading in Responsible Charge Analysis
    II.2.c. is one of the three provisions the Board read simultaneously in its responsible charge analysis.
  • Chief Engineer Managerial Responsible Charge Standard Applied to Engineer A
    II.2.c. defines the conditions under which a chief engineer may coordinate and seal an entire project, setting the standard applied to Engineer A.
  • Dual-Mode Seal Authorization Principle Applied to Engineer A Sealing of Non-Registered Graduate Engineers
    II.2.c. establishes the permissible framework for sealing entire projects while requiring qualified preparers to seal their own segments.
Role (3)
  • Engineer A Chief Engineer Sealing Supervisor
    This provision governs the conditions under which Engineer A may legitimately sign and seal an entire project, requiring each technical segment to be sealed by its qualified preparer.
  • Subordinate Registered Engineers Technical Segment Sealers
    This provision directly requires that these licensed engineers sign and seal the specific technical segments they prepare rather than having Engineer A seal all work.
  • Registered Engineer Subordinate Plan Preparers
    This provision implies these registered engineers should be sealing the segments they prepare rather than leaving all sealing to Engineer A.
Event (3)
  • Supervision Standard Institutionalized
    This provision defines the acceptable coordination and sealing standard that becomes institutionalized as the proper supervision framework for multi-segment projects.
  • Registered Engineers Relieved of Sealing
    This provision clarifies that each technical segment must be sealed only by the qualified engineer who prepared it, making it improper to relieve registered engineers of their sealing responsibilities.
  • Precedent Standard Activated
    This provision sets the precedent standard for how engineers may legitimately coordinate and seal entire projects while ensuring each segment is properly attributed.
Resource (4)
  • NSPE Code of Ethics Sections II.2.a, II.2.b, II.2.c
    This entity explicitly lists II.2.c as primary normative authority governing the hierarchy of responsibility when a coordinating engineer seals an entire project.
  • CADD_Document_Sealing_Practice_Standard_Instance
    This entity addresses professional obligations when an engineer seals plans prepared by subordinates under direct supervision, relevant to II.2.c's coordination and segment-sealing hierarchy.
  • CADD Document Sealing Practice - Responsible Charge Norms
    This entity governs when a chief engineer may seal documents prepared by subordinates, directly corresponding to II.2.c's provision for coordinating engineers sealing entire projects.
  • Engineering_Licensure_Law_Sealing_Instance
    The legal framework for responsible charge and general supervision directly informs the conditions under which II.2.c permits a coordinating engineer to seal an entire project.
Capability (7)
  • Subordinate Registered Engineers Technical Segment Sealing Capability
    II.2.c requires each technical segment to be sealed only by the qualified engineer who prepared it, directly invoking the subordinate registered engineers' sealing capability.
  • Subordinate Registered Engineers Technical Segment Attribution Sealing
    II.2.c explicitly requires subordinate engineers to affix their own seals to the technical segments they prepared, making this capability a direct requirement of the provision.
  • Engineer A Technical Segment Attribution and Exclusive Sealing Compliance
    II.2.c requires each technical segment to be signed and sealed only by the qualified engineer who prepared it, which Engineer A failed to implement.
  • Engineer A Registered vs Non-Registered Subordinate Sealing Differentiation
    II.2.c applies specifically to registered engineers sealing their own segments, requiring Engineer A to differentiate between registered and non-registered subordinates.
  • Engineer A Three-Provision Mutually Dependent Code Reading
    II.2.c is one of the three mutually dependent provisions Engineer A was required to read together when analyzing his sealing obligations.
  • Engineer A Supervisory Sealing Authority Structural Redesign Capability Deficit
    II.2.c provides the structural alternative of segment-by-segment sealing that Engineer A failed to recognize as the required redesign of his sealing authority approach.
  • Engineer A Non-Registered Subordinate Direct Control Personal Supervision Sealing Prerequisite
    II.2.c limits the coordination sealing model to segments sealed by qualified registered engineers, highlighting the distinct problem posed by non-registered subordinates.
Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1 Lineage Graph

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

Principle Established:

An engineer is unethical in accepting a position that requires oversight of engineering and surveying documents when the engineer lacks the qualifications and experience in the relevant field, regardless of whether the engineer personally prepares or approves the documents.

Citation Context:

The Board cited this case to illustrate that an engineer cannot ethically fulfill a role requiring oversight and approval of engineering documents in fields where they lack the necessary qualifications and experience, even if they are not personally preparing the documents.

Relevant Excerpts
discussion: "in the recent Case 85-3 where an engineer with experience and background solely in the field of chemical engineering accepted a position as a county surveyor, we noted that although the duties of the position included oversight of surveying reports and highway improvement but did not include actual preparation of engineering and surveying documents, nevertheless the engineer was unethical in accepting the position."
discussion: "Clearly, in Case 85-3 , the Board was faced with a situation in which an engineer was seeking to fulfill a role in which he possessed neither the qualifications nor the experience to perform in a competent manner."
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 51% Facts Similarity 48% Discussion Similarity 63% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 80%
Shared provisions: II.2.a, II.2.b Same outcome True View Synthesis
Component Similarity 56% Facts Similarity 62% Discussion Similarity 66% Provision Overlap 43% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: II.2.a, II.2.b, II.2.c Same outcome True View Synthesis
Component Similarity 48% Facts Similarity 49% Discussion Similarity 71% Provision Overlap 50% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: 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 56% Facts Similarity 57% Discussion Similarity 70% Provision Overlap 22% Outcome Alignment 100% Tag Overlap 83%
Shared provisions: II.2.a, II.2.b Same outcome True View Synthesis
Component Similarity 59% Facts Similarity 53% Discussion Similarity 75% Provision Overlap 30% Outcome Alignment 100% Tag Overlap 40%
Shared provisions: II.2.a, II.2.b, II.2.c Same outcome True View Synthesis
Component Similarity 60% Facts Similarity 57% Discussion Similarity 64% Provision Overlap 22% Outcome Alignment 100% Tag Overlap 50%
Shared provisions: II.2.b, II.2.c Same outcome True View Synthesis
Component Similarity 58% Facts Similarity 51% Discussion Similarity 51% Provision Overlap 20% Outcome Alignment 100% Tag Overlap 44%
Shared provisions: II.2.a, II.2.b Same outcome True View Synthesis
Component Similarity 51% Facts Similarity 42% Discussion Similarity 55% Provision Overlap 29% Outcome Alignment 100% Tag Overlap 43%
Shared provisions: II.2.a, II.2.b Same outcome True View Synthesis
Component Similarity 64% Facts Similarity 69% Discussion Similarity 60% Provision Overlap 8% Outcome Alignment 100% Tag Overlap 33%
Shared provisions: II.2.a Same outcome True View Synthesis
Questions & Conclusions (1 board)
View Extraction
Board Board question 1

Is it ethical for Engineer A to seal plans that have not been prepared by him, or which he has not checked and reviewed in detail?

Board conclusion It is unethical for Engineer A to seal plans that have not been prepared by him, or which he has not checked and reviewed in detail.
Implicit (4)

Does the ethical analysis change depending on whether the subordinate plan preparers are registered engineers versus non-registered graduate engineers, and if so, what distinct obligations does Engineer A bear in each case?

AnalyticalIn response to Q101: The ethical analysis does change materially depending on whether subordinate plan preparers are registered engineers or non-registered graduate engineers, and Engineer A bears distinct obligations in each case. When subordinates are registered engineers, Engineer A's failure to conduct detailed review is a serious ethical violation, but the registered subordinates themselves possess independent professional standing and licensure accountability that provides at least a structural floor of competence assurance. The ethical deficiency is Engineer A's abdication of responsible charge, not the absence of any licensed professional judgment in the work. By contrast, when subordinates are non-registered graduate engineers, the ethical violation is categorically more severe: no licensed professional judgment has been applied to the work at any stage prior to Engineer A's seal, meaning the seal itself becomes the sole professional certification of work that has received no professional-level verification whatsoever. The NCEE Model Law's requirement of 'direct control and personal supervision' for non-licensed subordinate work is not a procedural nicety but a substantive safeguard that compensates for the absence of the subordinate's own licensure accountability. Engineer A's practice of sealing non-registered engineers' plans under mere 'general supervision' therefore exposes the public to a categorically greater risk, and the Board's single unified finding of unethical conduct, while correct, understates the aggravated nature of the non-registered subordinate scenario. Engineer A's distinct obligation in the non-registered case is not merely to review more carefully but to exercise the kind of direct, granular, contemporaneous control that functionally substitutes for the absent licensure of the subordinate.

Should the engineering firm itself bear independent ethical responsibility for structuring its operations in a way that makes adequate responsible charge review impossible for Engineer A, rather than placing the entire ethical burden on Engineer A alone?

AnalyticalIn response to Q102: The engineering firm itself bears an independent and non-trivial ethical responsibility for structuring its operations in a way that makes adequate responsible charge review structurally impossible for Engineer A. The Board's analysis correctly identifies Engineer A's individual ethical violation, but the exclusive focus on Engineer A as the ethical actor obscures a systemic organizational failure. When a firm grows to a scale at which its designated chief engineer cannot physically conduct detailed reviews of the volume of plans being sealed, the firm has created an institutional arrangement that is structurally incompatible with the professional obligations that licensure law and the NSPE Code impose. The firm is not a passive backdrop to Engineer A's individual choices; it is an active participant in establishing the supervisory architecture, project volume, staffing ratios, and sealing protocols that make the violation possible and, indeed, nearly inevitable. Placing the entire ethical burden on Engineer A alone allows the organizational structure that generates the violation to escape scrutiny. A more complete ethical analysis would hold that the firm has an affirmative obligation to design its operations so that responsible charge is achievable - for example, by implementing multi-engineer sealing models, limiting project volume per sealing engineer, or requiring subordinate registered engineers to seal their own segments. The failure to do so is not merely a business decision but an ethical one, because the firm's operational model systematically degrades the public safety protections that the sealing requirement is designed to provide.

What affirmative restructuring steps is Engineer A ethically obligated to take - such as requiring subordinate registered engineers to affix their own seals to the segments they prepare - rather than simply refraining from sealing plans he has not reviewed in detail?

AnalyticalThe Board's conclusion implicitly treats Engineer A's ethical failure as a binary matter - he either reviews in detail or he does not - but a complete analysis reveals that Engineer A also bore affirmative restructuring obligations that he failed to discharge. Specifically, Engineer A was ethically required to pursue at least one of three corrective paths: (1) require registered engineer subordinates to affix their own seals to the technical segments they personally prepared, thereby invoking Section II.2.c's coordinating engineer model in a structurally sound way that distributes sealing accountability to the actual preparers; (2) reduce the firm's project volume to a scale at which detailed review was feasible; or (3) decline to seal any document he had not personally reviewed in sufficient detail. Engineer A's passive continuation of an inadequate supervisory model - justified only by confidence in subordinates - reflects not merely a failure to review but a failure of professional integrity in the virtue ethics sense: a conscientious engineer would have recognized that organizational scale is a structural problem demanding structural solutions, not an excuse that dissolves the responsible charge obligation. The firm itself bears independent ethical responsibility for institutionalizing an operating model that made adequate review impossible, but this shared institutional culpability does not diminish Engineer A's personal obligation to refuse to seal or to restructure before sealing.
AnalyticalIn response to Q103: The Board's conclusion that Engineer A must not seal plans he has not reviewed in detail implies, but does not articulate, a set of affirmative restructuring obligations. Engineer A is not merely required to stop an improper practice; he is ethically obligated to take positive steps to bring the firm's sealing architecture into compliance. The most structurally sound affirmative step is requiring subordinate registered engineers to affix their own seals to the technical segments they personally prepare, as expressly contemplated by Section II.2.c's coordinating engineer provision. This would distribute professional accountability to the engineers who actually possess direct knowledge of the work, while permitting Engineer A to seal the project as a whole in a coordination capacity - provided he has genuinely exercised responsible charge over the project's conceptual framework, design requirements, and integration. Additionally, Engineer A is obligated to refuse to seal plans prepared by non-registered graduate engineers unless he can demonstrate direct control and personal supervision of that work, and to advocate within the firm for staffing and workflow changes that make such supervision feasible. If the firm's scale makes these steps impossible, Engineer A's affirmative obligation extends to declining the chief engineer sealing role itself, or to restructuring the role so that sealing authority is distributed among multiple registered engineers each capable of exercising genuine responsible charge over their respective domains. Inaction in the face of a known structural impossibility is itself an ethical failure, not a neutral default.

Does Engineer A's act of sealing plans prepared by non-registered graduate engineers without direct control and personal supervision expose the public to a categorically greater risk than sealing plans prepared by registered subordinates, and does this distinction warrant a separate and more stringent ethical finding?

AnalyticalIn response to Q104: Engineer A's act of sealing plans prepared by non-registered graduate engineers without direct control and personal supervision does expose the public to a categorically greater risk than sealing plans prepared by registered subordinates, and this distinction warrants a separate and more stringent ethical finding that the Board's unified conclusion does not fully capture. When Engineer A seals plans prepared by registered engineer subordinates without detailed review, there exists at least a residual layer of professional accountability: the subordinate engineers are themselves licensed, have passed competency examinations, and are individually subject to professional discipline. The ethical failure is Engineer A's, but the work itself has passed through at least one professionally accountable mind. When Engineer A seals plans prepared by non-registered graduate engineers under only general supervision, no such residual layer exists. The graduate engineer's work has received no professional-level verification from any licensed engineer before the seal is affixed. The seal therefore misrepresents to the public, to regulators, and to clients that a licensed professional has exercised responsible charge over work that has in fact received none. This is not merely a procedural shortcut but a substantive misrepresentation of the professional oversight actually provided. The Dual-Mode Seal Authorization Principle recognizes this distinction by imposing the heightened standard of direct control and personal supervision specifically for non-licensed subordinate work, and a complete ethical analysis should treat the non-registered subordinate sealing scenario as an aggravated violation warranting independent emphasis beyond the general finding.
AnalyticalThe Board's conclusion, while correct, does not distinguish between two categorically different risk profiles embedded in Engineer A's practice. When Engineer A seals plans prepared by registered engineer subordinates who do not affix their own seals, the ethical deficiency is primarily one of inadequate personal review - the subordinate engineers possess licensure-validated competence, and the principal harm is the absence of Engineer A's own verification. However, when Engineer A seals plans prepared by non-registered graduate engineers under only general supervision, a compounded and categorically more serious violation occurs: the work has been produced by individuals whose professional judgment has not been independently validated by licensure, and Engineer A's general supervision falls short of the 'direct control and personal supervision' standard that the NCEE Model Law and engineering intern supervision norms require before a licensed engineer may take professional responsibility for non-licensed subordinate work. This distinction warrants a separate and more stringent ethical finding for the non-registered subordinate sealing practice, because the public is exposed not merely to unverified work but to work that has never been subjected to any independent professional quality gate other than Engineer A's cursory oversight.
Cross-cutting analytical questions (12)

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

Principle tension (4)

Does the Chief Engineer Managerial Responsible Charge Standard - which acknowledges that a chief engineer contributes through conceptual direction, design requirements, and consultative input - conflict with the Detailed Review Sufficiency Standard, which demands granular verification before sealing, and if so, how should the boundary between legitimate managerial oversight and insufficient review be drawn?

AnalyticalIn response to Q201: The Chief Engineer Managerial Responsible Charge Standard and the Detailed Review Sufficiency Standard do exist in genuine tension, and the Board's analysis resolves that tension by treating the managerial model as insufficient without fully articulating where the boundary lies. The resolution implicit in the Board's reasoning is that conceptual direction, design requirement setting, and consultative input on technical questions - the activities Engineer A actually performs - constitute a necessary but not sufficient component of responsible charge. They are the upstream conditions that make detailed review meaningful, not substitutes for it. The boundary between legitimate managerial oversight and insufficient review should be drawn at the point where the sealing engineer can form an independent professional judgment about whether the completed work conforms to the design intent, applicable standards, and public safety requirements. A chief engineer who sets design requirements and answers technical questions but never verifies that the resulting documents actually reflect those requirements and answers has exercised only half of responsible charge. The managerial contribution is the input side; the detailed review is the output verification side. Both are required. The practical implication is that a chief engineer in a large firm may legitimately rely on subordinates to execute design work, but must implement review checkpoints sufficient to form a genuine professional judgment about the completed product before sealing - not a rubber-stamp review, but one substantive enough to detect material errors or deviations from design intent.
AnalyticalThe tension between the Chief Engineer Managerial Responsible Charge Standard and the Detailed Review Sufficiency Standard was resolved decisively in favor of the latter, but the resolution was not a simple rejection of managerial oversight as a legitimate mode of engineering responsibility. Rather, the Board drew a threshold distinction: conceptual direction, design-requirement setting, and consultative input are necessary but not sufficient conditions for responsible charge. They constitute the floor of engagement, not the ceiling of obligation. A chief engineer who contributes at the conceptual and consultative level has done something professionally meaningful, but has not yet done enough to certify - through the act of sealing - that the resulting documents reflect his personal professional judgment. The case teaches that when two principles operate at different levels of abstraction (managerial oversight versus document-level verification), the more granular and document-specific principle governs the specific act of sealing, while the managerial principle governs the broader organizational role. Engineer A conflated the two levels, treating role-level engagement as document-level certification. The Board's resolution makes clear that the seal is a document-level act requiring document-level verification, regardless of how substantial the engineer's role-level contributions may be.

Does the Subordinate Competence Confidence Non-Substitution Principle - holding that trust in a subordinate's ability cannot replace the sealing engineer's own verification - conflict with the Technical Segment Sealing by Qualified Preparers principle, which implies that a registered subordinate's own professional judgment and accountability should be recognized and relied upon for the segments they prepare?

AnalyticalIn response to Q202: The tension between the Subordinate Competence Confidence Non-Substitution Principle and the Technical Segment Sealing by Qualified Preparers principle is real but resolvable, and its resolution actually points toward the affirmative restructuring obligation identified in Q103. The Non-Substitution Principle correctly holds that Engineer A's trust in subordinates cannot replace his own verification when he is the sole sealing engineer. However, the Technical Segment Sealing principle does not contradict this; rather, it offers a structural solution. If subordinate registered engineers affix their own seals to the segments they prepare, the professional judgment and accountability of those engineers is not merely trusted - it is formally certified and legally attributed to them. In that scenario, Engineer A's coordinating seal under Section II.2.c does not rest on unverified trust but on the documented professional certifications of the segment preparers, combined with Engineer A's own responsible charge over the project's integration and coordination. The two principles therefore operate at different levels: the Non-Substitution Principle prohibits Engineer A from treating trust as a substitute for verification when he alone seals; the Technical Segment Sealing principle provides a mechanism by which verification is formally distributed to those with direct knowledge, making Engineer A's coordinating role ethically sound. The conflict dissolves when the firm adopts the multi-seal model; it persists only when Engineer A insists on being the sole sealing engineer in a structure that makes his own verification impossible.
AnalyticalThe Subordinate Competence Confidence Non-Substitution Principle and the Technical Segment Sealing by Qualified Preparers principle, rather than genuinely conflicting, operate as complementary correctives that together point toward the same structural remedy. The Non-Substitution Principle establishes that Engineer A's confidence in his subordinates cannot replace his own verification when he is the sealing engineer. The Technical Segment Sealing principle establishes that registered subordinate engineers are themselves capable of bearing professional responsibility for the segments they prepare, and should affix their own seals accordingly. Read together, these principles do not create an irresolvable tension - they dissolve the false dilemma Engineer A constructed. Engineer A assumed that either he seals everything or nothing gets sealed. The principles jointly reveal a third path: registered subordinate engineers seal the segments they prepare, exercising their own professional judgment and accountability, while Engineer A seals only those elements he has personally reviewed in sufficient detail, or assumes the coordination role under Section II.2.c with a genuinely restructured review architecture. The case thus teaches that principle tensions in engineering ethics are often symptoms of a structural problem in practice design rather than genuine logical contradictions in the code, and that resolving the tension requires restructuring the practice rather than subordinating one principle to the other.

Does the Competence Prerequisite for Role Acceptance principle - applied by analogy from Case 85-3 - conflict with the Professional Accountability principle that holds Engineer A fully responsible for all work sealed under his authority, given that accepting a chief engineer role in a large firm may itself be the competence-prerequisite decision that then generates unavoidable sealing obligations he cannot practically fulfill?

AnalyticalIn response to Q203: The tension between the Competence Prerequisite for Role Acceptance principle drawn from BER Case 85-3 and the Professional Accountability principle is genuine and reveals a threshold ethical question the Board does not fully address. The Case 85-3 analogy holds that accepting a role one lacks the competence - or, by extension, the practical capacity - to fully discharge is itself an ethical violation. Applied to Engineer A, this suggests that if the organizational scale of the firm made detailed review structurally impossible from the outset, then Engineer A's acceptance of the chief engineer sealing role under those conditions was itself the threshold ethical act, not merely the downstream sealing of individual plans. The Professional Accountability principle then compounds this: having accepted the role, Engineer A is fully responsible for all work sealed under his authority, creating a situation in which the threshold violation generates an ongoing cascade of downstream violations. The resolution of this tension is not that Engineer A should have refused the chief engineer role categorically, but that he should have accepted it only on the condition that the firm's structure would be redesigned to make responsible charge achievable - whether through multi-engineer sealing, reduced project volume, or enhanced review protocols. The ethical failure is therefore both anterior (accepting an impossible role without restructuring conditions) and ongoing (continuing to seal without adequate review). The Board's finding addresses only the ongoing dimension; a complete analysis would also identify the anterior threshold violation.
AnalyticalThe most consequential principle interaction in this case is the collision between the Competence Prerequisite for Role Acceptance principle - drawn by analogy from BER Case 85-3 - and the Professional Accountability principle that holds Engineer A fully responsible for all work sealed under his authority. This tension is not merely theoretical: it reveals a structural ethical trap embedded in large-firm practice. If Engineer A accepts the chief engineer role knowing that organizational scale makes detailed review impossible, he has potentially committed a threshold ethical violation at the moment of role acceptance, not merely at the moment of sealing. Yet the Professional Accountability principle simultaneously holds him responsible for every document he seals, creating a compounding obligation that grows with each sealed document. The case teaches that these two principles are not in genuine conflict but are sequentially ordered: the Competence Prerequisite principle operates at the role-acceptance stage and is the primary preventive obligation, while the Professional Accountability principle operates at the document-certification stage and is the ongoing enforcement obligation. Engineer A's error was in treating the organizational scale problem as a background condition to be managed rather than as a threshold question about whether the role could be ethically accepted and discharged at all. The resolution implied by the Board's reasoning - though not made fully explicit - is that accepting a role one cannot discharge with integrity is itself an ethical violation, and that the downstream sealing violations are symptomatic of that foundational failure. This prioritization places role-acceptance competence assessment above document-level rationalization as the primary site of ethical responsibility.

Does the Seal and Signature as Professional Judgment Certification Beyond Legal Formality principle - which treats the seal as a substantive ethical act - conflict with the Mutually Dependent Code Provision Reading principle when applied to Section II.2.c, which expressly permits a coordinating engineer to accept responsibility for an entire project, potentially implying that the seal in a coordination role carries a different and less granular certification than the seal of the direct preparer?

AnalyticalIn response to Q204: The tension between the Seal and Signature as Professional Judgment Certification principle and the Mutually Dependent Code Provision Reading principle, when applied to Section II.2.c's coordinating engineer provision, is the most theoretically significant tension in this case. Section II.2.c does expressly contemplate that a coordinating engineer may accept responsibility for an entire project, which could be read to imply that the coordinating seal carries a different - and less granular - certification than the seal of the direct preparer. However, a careful reading of the mutually dependent provisions forecloses this interpretation. Section II.2.c does not create a lower standard of professional judgment for the coordinating engineer; it creates a different scope of responsibility. The coordinating engineer's seal certifies professional judgment about the project's integration, coherence, and conformity to overall design requirements - not necessarily about every computational detail in every technical segment. But this is only ethically sound when the technical segments themselves have been sealed by their qualified preparers, whose seals certify the segment-level professional judgment. When Engineer A is the sole sealing engineer and subordinates affix no seals, Section II.2.c's coordinating role cannot be invoked to justify a reduced certification standard, because there are no segment-level seals providing the underlying professional accountability on which the coordinating seal legitimately rests. The coordinating engineer provision therefore does not conflict with the Professional Judgment Certification principle when the multi-seal model is properly implemented; it conflicts only when it is misused as a justification for a single engineer to seal an entire large project without either detailed review or subordinate seals.
Theoretical (4)

From a deontological perspective, does Engineer A's act of affixing his seal constitute a categorical breach of professional duty, regardless of his confidence in subordinates' competence, because the seal functions as a formal certification of personal knowledge and judgment that cannot be delegated by definition?

AnalyticalIn response to Q301: From a deontological perspective, Engineer A's act of affixing his seal does constitute a categorical breach of professional duty, independent of his confidence in subordinates' competence, because the seal functions as a formal certification of personal professional knowledge and judgment that is non-delegable by its very nature. The deontological analysis proceeds from the nature of the act itself: a seal is not merely a bureaucratic marker of organizational affiliation but a first-person professional assertion - 'I, as a licensed engineer, certify that I have exercised responsible charge over this work.' This assertion is either true or false as a matter of fact, and its truth cannot be manufactured by confidence in others. Engineer A's rationalization - that trust in competent subordinates satisfies the sealing obligation - commits a categorical error by substituting a relational attitude (confidence) for a cognitive act (personal verification and judgment). From a Kantian perspective, universalizing Engineer A's maxim - 'a chief engineer may seal plans he has not reviewed in detail, provided he is confident in his subordinates' - would systematically destroy the institution of professional sealing, because the seal's social function depends entirely on its being a reliable signal of actual personal professional review. A world in which all chief engineers followed this maxim would be one in which seals conveyed no meaningful information about the quality of professional oversight, rendering the entire licensure and sealing system incoherent. The deontological verdict is therefore unambiguous: the breach is categorical, not contingent on outcomes.

From a consequentialist perspective, does the systemic risk to public safety created by Engineer A's practice of sealing unreviewed plans outweigh the organizational efficiency gains achieved by allowing a large firm to operate at scale without requiring detailed chief-engineer review of every design?

AnalyticalIn response to Q302: From a consequentialist perspective, the systemic risk to public safety created by Engineer A's practice of sealing unreviewed plans does outweigh the organizational efficiency gains, and the consequentialist analysis reveals an additional dimension the Board does not address: the systemic erosion of the professional sealing institution itself. The immediate consequentialist calculus is straightforward - the probability of undetected design errors multiplied by the severity of potential public harm (structural failures, safety hazards, infrastructure failures) substantially exceeds the efficiency gains from allowing a large firm to operate without chief-engineer review of every design. But the more significant consequentialist harm is systemic: if Engineer A's practice becomes normalized across large engineering firms, the professional seal loses its function as a reliable public safety signal. Clients, regulators, and the public rely on the seal as a proxy for professional oversight; if that proxy is systematically decoupled from actual oversight, the entire information architecture of professional licensure degrades. The efficiency gains are real but bounded - they accrue primarily to the firm and its clients in the form of faster project delivery and lower costs. The risks are unbounded in principle and are borne primarily by third parties and the public who have no contractual relationship with the firm and no ability to independently verify the quality of the professional oversight behind the seal. A consequentialist analysis that accounts for these systemic and distributional dimensions strongly supports the Board's conclusion and suggests that the efficiency rationale is not merely insufficient but affirmatively misleading as a justification.

From a virtue ethics perspective, does Engineer A's substitution of trust in subordinates for personal verification reflect a failure of the virtue of professional integrity, insofar as a truly conscientious engineer would recognize that organizational scale is a structural problem to be solved rather than an excuse that dissolves the obligation of responsible charge?

AnalyticalIn response to Q303: From a virtue ethics perspective, Engineer A's substitution of trust in subordinates for personal verification does reflect a failure of professional integrity, and the virtue ethics analysis adds a dimension that neither the deontological nor consequentialist frameworks fully capture: the question of what kind of professional Engineer A is becoming through the habituation of this practice. Virtue ethics evaluates not only discrete acts but the character dispositions that acts express and reinforce. Engineer A's rationalization - that organizational scale excuses him from detailed review - reflects a disposition to treat structural inconvenience as a moral exemption, which is precisely the disposition that a person of professional integrity would resist. A truly conscientious engineer, confronted with the recognition that organizational scale makes adequate review impossible, would experience this as a problem demanding a solution, not as a fact that dissolves the obligation. The virtue of professional integrity requires not only performing one's duties when convenient but actively restructuring one's circumstances to make duty performance possible. Engineer A's failure is therefore not merely a failure of a specific act but a failure of practical wisdom - the capacity to recognize what one's professional role genuinely requires and to take the steps necessary to fulfill it, even when those steps are organizationally costly. The habituation of the rationalization ('I trust my subordinates, therefore I need not review') further degrades the disposition over time, making future compliance progressively less likely and the character failure progressively more entrenched.

From a deontological perspective, do NSPE Code Sections II.2.a, II.2.b, and II.2.c, read as mutually dependent provisions, impose a unified and non-waivable duty on Engineer A such that accepting the chief engineer role without the capacity to exercise responsible charge over all sealed documents constitutes a threshold ethical violation independent of any downstream harm?

AnalyticalIn response to Q304: From a deontological perspective, NSPE Code Sections II.2.a, II.2.b, and II.2.c, read as mutually dependent provisions, do impose a unified and non-waivable duty on Engineer A such that accepting the chief engineer role without the capacity to exercise responsible charge over all sealed documents constitutes a threshold ethical violation independent of any downstream harm. Section II.2.a requires that engineers undertake assignments only when qualified by education or experience; read in the context of responsible charge, this extends to the practical capacity to discharge the role's obligations, not merely technical competence in the subject matter. Section II.2.b prohibits sealing documents dealing with subject matter in which the engineer lacks competence - and the Board's analysis makes clear that 'competence' in this context includes the practical ability to conduct adequate review, not merely abstract technical knowledge. Section II.2.c's coordinating engineer provision, read in conjunction with the other two, does not create an escape valve from these requirements but rather specifies the conditions under which a coordinating role is ethically permissible - conditions that include, implicitly, the ability to exercise genuine responsible charge over the coordination function. The integrated reading therefore generates a threshold obligation: before accepting the chief engineer sealing role, Engineer A was obligated to assess whether the organizational structure would permit him to fulfill the role's requirements, and to decline or restructure if it would not. This threshold obligation is non-waivable because it is grounded in the non-delegable nature of professional accountability, not in any contingent assessment of likely outcomes.
Counterfactual (4)

If Engineer A had restructured the firm's sealing practice so that each registered engineer subordinate affixed their own seal to the technical segments they personally prepared, would Engineer A's role as coordinating chief engineer have satisfied the responsible charge standard under Section II.2.c without requiring him to conduct detailed reviews of every design element?

AnalyticalIn response to Q401: If Engineer A had restructured the firm's sealing practice so that each registered engineer subordinate affixed their own seal to the technical segments they personally prepared, this restructuring would substantially - though not automatically - satisfy the responsible charge standard under Section II.2.c, provided that Engineer A's coordinating role was genuinely substantive. The key insight is that Section II.2.c's coordinating engineer provision is not a reduced-standard exception but a role-appropriate standard: the coordinating engineer's responsible charge is over the project's integration, coherence, and conformity to overall design requirements, while the segment preparers' responsible charge is over their respective technical domains. When both levels of sealing are present, the professional accountability structure is complete. Engineer A's conceptual direction, design requirement setting, and consultative input on technical questions - activities he actually performs - would constitute genuine responsible charge over the coordination function in this model, because the segment-level professional accountability would be formally attributed to the engineers with direct knowledge of the work. The counterfactual therefore reveals that the Board's finding does not condemn the chief engineer role as such, but rather the specific practice of a single engineer sealing an entire large project without either detailed review or subordinate seals. The multi-seal model is the ethically sound path, and Engineer A's failure to implement it - or to advocate for its implementation - is a significant dimension of his ethical failure.

If Engineer A had declined to seal plans prepared by non-registered graduate engineers unless he could exercise direct control and personal supervision over their work, would the firm's operational model have been ethically viable, or would the scale of the organization have made compliance with the responsible charge standard structurally impossible for non-licensed subordinate work?

AnalyticalIn response to Q402: If Engineer A had declined to seal plans prepared by non-registered graduate engineers unless he could exercise direct control and personal supervision over their work, the ethical viability of the firm's operational model would depend entirely on whether the firm was willing to restructure its use of non-registered engineers. The NCEE Model Law's direct control and personal supervision standard for non-licensed subordinate work is not aspirational but mandatory, and it reflects the structural reality that non-registered engineers cannot independently certify their own work. If the firm's scale made direct control and personal supervision of all non-registered engineer work impossible for Engineer A alone, the firm would face a binary choice: either assign non-registered engineer work only to projects where a registered engineer with sufficient capacity could exercise direct supervision, or limit the use of non-registered engineers to tasks that do not require professional sealing. The counterfactual therefore reveals that the firm's operational model, as structured, was not ethically viable for non-registered subordinate work at the scale described - not because large firms cannot ethically employ non-registered engineers, but because the firm had not distributed supervisory responsibility among enough registered engineers to make direct control and personal supervision achievable. The ethical implication is that organizational scale is a resource allocation problem, not a standard-reduction justification: the firm needed more registered engineers in supervisory roles, not a lower standard for the one it had.

If Engineer A had applied the same reasoning used in BER Case 85-3 - that accepting a role one lacks the competence to fully discharge is itself an ethical violation - and had refused to accept the chief engineer sealing role given the organizational scale that made detailed review impossible, would the firm have been compelled to adopt a structurally sound multi-engineer sealing model that better protected the public?

AnalyticalBeyond the Board's finding that sealing unreviewed plans is unethical, Engineer A's practice reveals a threshold violation that precedes any individual sealing act: by accepting and retaining the Chief Engineer role in an organization whose scale structurally prevents him from exercising responsible charge, Engineer A committed an antecedent ethical breach analogous to the one identified in BER Case 85-3. Just as the chemical engineer in that case erred by accepting a county surveyor role outside his domain competence, Engineer A erred by accepting - and continuing to hold - a sealing authority role whose organizational conditions made the discharge of that authority impossible. The ethical violation is therefore not merely episodic (each individual unsealed plan) but structural and ongoing: the firm's operating model itself is the source of the violation, and Engineer A's failure to either restructure that model or relinquish the sealing authority constitutes a sustained breach of the competence prerequisite for role acceptance.
AnalyticalIn response to Q403: If Engineer A had applied the Case 85-3 reasoning and refused to accept the chief engineer sealing role given the organizational scale that made detailed review impossible, the firm would have been compelled to confront the structural incompatibility between its operational model and the professional sealing requirements - and the most likely outcome would have been adoption of a multi-engineer sealing model that better protected the public. The Case 85-3 analogy is instructive precisely because it identifies role acceptance as the threshold ethical decision: a chemical engineer who accepts a county surveyor position without surveying competence does not merely commit a series of downstream errors but makes a single anterior decision that generates all subsequent violations. Similarly, Engineer A's acceptance of a chief engineer sealing role in an organization whose scale made responsible charge impossible was the threshold decision that generated the ongoing pattern of violations. Had Engineer A refused the role on these grounds, the firm's leadership would have faced a clear choice: restructure the sealing architecture to distribute responsible charge among multiple engineers, reduce project volume to a level manageable by a single chief engineer, or accept that the firm could not legally and ethically operate at its current scale without additional licensed engineering oversight. Any of these outcomes would have been more protective of the public than the status quo. The counterfactual therefore supports the conclusion that the threshold violation - accepting an impossible role - is not merely an academic point but a practically significant one, because refusing the role would have generated systemic corrective pressure that ongoing compliance failures do not.

If Engineer A had implemented a mandatory checkpoint system requiring him to conduct a detailed review of each project at a defined completion milestone before affixing his seal - even if this slowed the firm's output - would this have constituted sufficient responsible charge to satisfy both the NCEE Model Law definition and the NSPE Code's sealing provisions, and what does the answer reveal about whether the Board's standard is workable for large engineering organizations?

AnalyticalIn response to Q404: If Engineer A had implemented a mandatory checkpoint system requiring detailed review of each project at a defined completion milestone before affixing his seal - even at the cost of reduced firm output - this would likely have constituted sufficient responsible charge to satisfy both the NCEE Model Law definition and the NSPE Code's sealing provisions, provided the checkpoint review was genuinely substantive rather than perfunctory. The answer reveals something important about the workability of the Board's standard for large engineering organizations: the standard is demanding but not impossible, and its demands are calibrated to the nature of the professional certification being made, not to the operational convenience of the certifying engineer. A checkpoint system that required Engineer A to conduct a detailed review of completed plans - examining design calculations, specifications, and drawings for conformity to design intent, applicable standards, and public safety requirements - would satisfy the 'direction and control' standard because it would give Engineer A the personal knowledge necessary to make the professional judgment that the seal certifies. The organizational cost of such a system is real: it would slow project delivery and might require the firm to reduce its project volume or hire additional registered engineers to share the review burden. But this cost is precisely what the responsible charge standard is designed to impose - it is the cost of professional accountability, and it cannot be externalized onto the public by substituting organizational efficiency for professional verification. The counterfactual therefore confirms that the Board's standard is workable for large organizations, but only if those organizations are willing to bear the costs that genuine professional accountability requires.
Decisions & Arguments (8)
View Extraction

Should Engineer A continue sealing plans prepared by subordinates on the basis of general direction and confidence in their competence, or must he either conduct a detailed review of each plan before sealing or restructure sealing authority so that responsible charge is actually exercised?

Options considered:
O1 Engineer A institutes a mandatory, substantive review of each project's completed plans at a defined milestone before affixing his seal: examining design calculations, specifications, and drawings for conformity to design intent, applicable standards, and public safety requirements, accepting that this will slow firm output and may require reducing project volume or hiring additional registered engineers to share the review burden. Board's choice
O2 Engineer A continues his current practice of sealing plans prepared by subordinates on the basis of general direction, design-concept involvement, and confidence in subordinate competence, treating his managerial engagement as sufficient to constitute responsible charge given the organizational realities of a large firm.
O3 Engineer A requires each registered subordinate engineer to affix their own professional seal to the technical segments they personally prepared, invoking the Section II.2.c coordinating engineer model, so that Engineer A's coordinating seal rests on formally attributed segment-level professional accountability rather than on unverified trust, while Engineer A retains responsibility for project integration, coherence, and conformity to overall design requirements.
Argument structure:
Warrants

The Organizational Scale Non-Excuse Obligation holds that organizational size and workload volume are self-imposed conditions that do not diminish the responsible charge requirement. The General Direction Non-Equivalence Obligation distinguishes general supervision, setting concepts, reviewing design elements, answering questions, from the detailed review required as a prerequisite for sealing. The Subordinate Competence Confidence Non-Substitution Principle holds that trust in subordinates cannot replace the sealing engineer's own personal verification. The Chief Engineer Managerial Responsible Charge Standard acknowledges that a chief engineer need not personally prepare every element, but requires involvement in design concept, review of design elements as the project develops, and availability for technical consultation, a floor of engagement that is necessary but not sufficient for sealing. The Seal and Signature as Professional Judgment Certification principle treats the seal as a substantive first-person certification of personal professional knowledge, not a bureaucratic formality.

Rebuttals

Uncertainty arises if 'responsible charge' can be legitimately satisfied by managerial oversight in large organizations, such that Engineer A's conceptual direction and consultative input constitute sufficient personal engagement. The Chief Engineer Managerial Standard could be read to permit a reduced granularity of review commensurate with the coordination role. Additionally, if registered subordinate engineers are themselves competent and accountable, their presence may constitute a meaningful intermediate safeguard that partially discharges Engineer A's verification obligation.

Grounds

Engineer A is Chief Engineer of a large engineering firm. Because of the volume of concurrent projects, he finds it impossible to conduct a detailed review or check of the design for plans he seals. He seals plans prepared by registered engineer subordinates who do not affix their own seals, and also seals plans prepared by non-registered graduate engineers. He justifies this practice by his confidence in the ability of those he has hired and who work under his general direction and supervision. The NCEE Model Law defines responsible charge as 'direct control and personal supervision of engineering work.'

Organizational Scale Non-Excuse for Responsible Charge Review Obligation General Direction Non-Equivalence to Responsible Charge Sealing Prerequisite Obligation

Should Engineer A treat his sealing obligations identically for plans prepared by registered subordinates and plans prepared by non-registered graduate engineers, or must he recognize a categorically heightened duty of direct control and personal supervision before sealing non-registered engineers' work, and decline to seal that work unless such supervision has actually been exercised?

Options considered:
O1 Engineer A recognizes a categorical distinction between the two scenarios, declines to seal plans prepared by non-registered graduate engineers unless he has exercised direct control and personal supervision over that specific work, and advocates within the firm for restructuring, either by assigning a registered engineer with sufficient supervisory capacity to directly oversee each non-registered engineer's work, or by restricting non-registered engineers to tasks that do not require professional sealing. Board's choice
O2 Engineer A treats his general supervisory engagement as equally sufficient for both registered and non-registered subordinate work, reasoning that his involvement in design concept, design requirements, and technical consultation constitutes responsible charge regardless of the licensure status of the preparer, and that the firm's internal quality culture provides adequate assurance for all work product.
O3 Engineer A requires that every non-registered graduate engineer's work be co-supervised by a designated registered engineer subordinate who exercises direct control and personal supervision over that specific work product and who is identified as the responsible supervising engineer, while Engineer A retains coordinating oversight, thereby distributing the direct supervision obligation to engineers with sufficient capacity to discharge it without requiring Engineer A to personally supervise every non-registered engineer's task.
Argument structure:
Warrants

The Dual-Mode Seal Authorization Principle recognizes that sealing non-registered engineers' work requires direct control and personal supervision, a standard more demanding than general direction, because the non-registered engineer cannot independently certify their own work and has not passed any independent professional competency validation. The Residual Professional Accountability Floor principle holds that registered subordinate engineers, even when the chief engineer does not review in detail, retain independent licensure accountability that provides at least one professionally validated layer of quality assurance. When non-registered engineers prepare the work, no such floor exists: the seal becomes the sole professional certification of work that has received no professional-level verification. The firm bears an independent ethical obligation to structure work assignments so that non-registered personnel are never placed in a position where their work is sealed without the requisite direct control and personal supervision.

Rebuttals

Uncertainty arises if the NCEE Model Law's 'direct control and personal supervision' standard for non-registered work is read as establishing only a procedural rather than a substantive distinction from the standard applicable to registered subordinate work, in which case Engineer A's general supervision might be treated as a matter of degree rather than a categorical failure. Additionally, if registered subordinate engineers in the firm informally review non-registered engineers' work before it reaches Engineer A, a de facto intermediate quality gate may exist even without formal sealing attribution.

Grounds

Engineer A seals plans prepared by registered engineer subordinates who do not affix their own seals, and separately seals plans prepared by non-registered graduate engineers working under his general supervision. In neither case does he conduct a detailed review. For non-registered engineers' work, no licensed professional has reviewed or certified the work at any stage prior to Engineer A's seal. The NCEE Model Law requires 'direct control and personal supervision' of engineering work as the definition of responsible charge, and engineering intern supervision norms impose heightened oversight requirements for non-licensed subordinate work.

Responsible Charge Direct Control Personal Supervision Non-Registered Work Sealing Obligation Direct Control and Personal Supervision Obligation for Non-Registered Subordinate Work

Should Engineer A accept and retain the Chief Engineer sealing role while the firm's organizational scale makes detailed responsible charge review structurally impossible, or must he either restructure the firm's sealing architecture to make responsible charge achievable, for example by requiring subordinate registered engineers to seal their own segments, or relinquish the sealing authority he cannot properly discharge?

Options considered:
O1 Engineer A proactively redesigns the firm's sealing authority structure by requiring registered subordinate engineers to affix their own professional seals to the technical segments they personally prepared, assuming the Section II.2.c coordinating engineer role for project integration and coherence, and declining to seal any document for which neither he nor a qualified subordinate has exercised genuine responsible charge, accepting that this may require reducing project volume or advocating for additional registered engineering staff. Board's choice
O2 Engineer A retains the Chief Engineer sealing role and addresses the scale problem through enhanced internal quality control protocols: such as structured peer review among subordinate engineers, standardized design checklists, and documented sign-off procedures, treating these controls as a reasonable organizational substitute for his own detailed review given the firm's size and the demonstrated competence of his subordinates.
O3 Engineer A determines that the firm's leadership will not support the structural changes necessary to make responsible charge achievable at the current project volume, and therefore relinquishes the chief engineer sealing authority, formally notifying firm leadership that the sealing role cannot be ethically discharged under current organizational conditions and that sealing authority must be redistributed among multiple registered engineers each capable of exercising genuine responsible charge over their respective domains.
Argument structure:
Warrants

The Competence Prerequisite for Role Acceptance principle, applied by analogy from BER Case 85-3, holds that accepting a professional role whose obligations one lacks the practical capacity to discharge is itself an ethical violation, anterior to and generative of all downstream sealing violations. The Supervisory Sealing Authority Structural Redesign Capability establishes that a chief engineer who recognizes the structural impossibility of meeting the responsible charge standard must proactively redesign the supervisory and sealing authority structure, for example by delegating sealing authority to qualified registered subordinate engineers for specific technical segments, establishing tiered review protocols, or limiting concurrent projects, rather than continuing to seal under impossible conditions. The Technical Segment Qualified Preparer Exclusive Sealing Obligation requires that each technical segment be signed and sealed only by the qualified engineer who prepared it, providing a structurally sound alternative to single-engineer sealing of an entire large project. The Organizational Scale Non-Excuse Obligation confirms that organizational scale is a self-imposed condition that does not diminish the responsible charge requirement and that the engineer must either restructure workload, delegate sealing authority, or decline to seal.

Rebuttals

The Case 85-3 analogy is rebutted if the chief engineer role is distinguished from the county surveyor role on the grounds that cross-domain incompetence (chemical engineer as surveyor) does not map cleanly onto intra-domain scale incapacity (civil engineer as chief engineer of a large civil firm), because Engineer A may possess full technical competence in the subject matter even if organizational scale prevents granular review. Additionally, uncertainty arises as to whether the ethical code imposes affirmative structural remediation duties on individual engineers or only prohibitory standards, and whether Engineer A has the organizational authority to unilaterally restructure the firm's sealing architecture without firm leadership support.

Grounds

Engineer A is Chief Engineer of a large engineering firm. Because of the size of the organization and the large number of concurrent projects, he finds it impossible to give a detailed review or check of the design for plans he seals. He has accepted and continues to hold this role despite the structural impossibility of discharging its responsible charge obligations. BER Case 85-3 established that a chemical engineer who accepted a county surveyor position outside his domain competence was unethical in accepting the position, even if he was otherwise a competent engineer. Section II.2.c contemplates that a coordinating engineer may accept responsibility for an entire project when individual technical segment preparers are identified and each segment is sealed by its qualified preparer.

Supervisory Sealing Authority Structural Redesign Capability Engineer A Supervisory Sealing Authority Structural Redesign Capability Deficit

Should Engineer A continue to seal plans he has not personally prepared or checked and reviewed in detail, relying on his confidence in subordinates' competence, or must he refuse to seal any document he has not personally verified through substantive review?

Options considered:
O1 Decline to affix his seal to any plan he has not personally checked and reviewed in sufficient detail to form an independent professional judgment about its conformity to design intent, applicable standards, and public safety requirements, even if this slows firm output or requires reducing project volume. Board's choice
O2 Continue sealing plans based on his role-level contributions: setting design requirements, providing conceptual direction, and answering technical questions, treating these managerial inputs as constituting responsible charge sufficient for the chief engineer sealing function in a large organization.
O3 Implement a mandatory checkpoint system requiring Engineer A to conduct a substantive review of each project at a defined completion milestone before sealing, accepting reduced firm throughput as the cost of genuine professional accountability while preserving the chief engineer sealing role.
Argument structure:
Warrants

The Seal and Signature as Professional Judgment Certification principle holds that the seal is a substantive first-person assertion of personal professional knowledge, not a bureaucratic formality, making Engineer A's verification non-delegable. The Subordinate Competence Confidence Non-Substitution principle holds that trust in subordinates' ability cannot replace the sealing engineer's own verification. Competing against these, the Chief Engineer Managerial Responsible Charge Standard acknowledges that a chief engineer contributes through conceptual direction and consultative input, which could be read as satisfying responsible charge at the role level even without document-level granular review.

Rebuttals

Uncertainty arises because if 'responsible charge' can be legitimately satisfied by managerial oversight in large organizations, Engineer A's practice may be defensible under the Chief Engineer Managerial Standard. Additionally, when subordinates are registered engineers, their independent licensure accountability provides a residual professional quality floor that partially mitigates the absence of Engineer A's detailed review, weakening the case for treating all unsealed-plan scenarios identically. The organizational scale constraint is real: requiring detailed review of every document may be physically impossible for a single chief engineer at the firm's volume.

Grounds

Engineer A, as chief engineer of a large firm, seals plans prepared by both registered engineer subordinates and non-registered graduate engineers. He consciously omits detailed design review, relying instead on general supervisory direction: setting design requirements, answering technical questions, and providing conceptual input. The firm has institutionalized this general supervision standard. Non-registered engineers' work enters the public record bearing only Engineer A's seal, with no independent professional certification from the preparers.

Responsible Charge Active Review Obligation Before Sealing Organizational Scale Preventing Adequate Review

Should Engineer A restructure the firm's sealing practice, by requiring registered engineer subordinates to affix their own seals to segments they personally prepare and invoking the Section II.2.c coordinating engineer model, or should he continue as the sole sealing engineer while relying on general supervision, accepting the ethical and legal consequences of that role?

Options considered:
O1 Require each registered engineer subordinate to affix their own seal to the technical segments they personally prepare, restructuring Engineer A's role as a coordinating chief engineer under Section II.2.c, exercising responsible charge over project integration and coherence while segment-level professional accountability is formally attributed to the engineers with direct knowledge of the work. Board's choice
O2 Retain the current single-engineer sealing model, accepting full professional accountability for all sealed documents under the Professional Accountability principle, while advocating internally for enhanced review resources, additional staff, reduced project volume, or extended timelines, to make detailed review more feasible without restructuring the sealing architecture.
O3 Refuse to continue holding the chief engineer sealing authority under organizational conditions that make responsible charge structurally impossible, compelling the firm to either adopt a distributed multi-engineer sealing model, reduce project volume, or assign sealing authority to multiple registered engineers each capable of exercising genuine responsible charge over their respective domains.
Argument structure:
Warrants

The Technical Segment Sealing by Qualified Preparers principle holds that registered subordinate engineers are capable of bearing professional responsibility for segments they personally prepare and should affix their own seals accordingly, formally certifying their judgment rather than merely being trusted. The Subordinate Competence Confidence Non-Substitution principle holds that Engineer A's trust in subordinates cannot replace his own verification when he is the sole sealing engineer. The Affirmative Restructuring Obligation holds that cessation of improper practice is necessary but not sufficient. Engineer A must take positive steps to bring the sealing architecture into compliance. Competing against restructuring, the Professional Accountability principle holds Engineer A fully responsible for all work sealed under his authority regardless of organizational design, and the firm's operational efficiency rationale supports maintaining a single-engineer sealing model.

Rebuttals

Uncertainty arises because Engineer A may lack the organizational authority to unilaterally require subordinate registered engineers to affix their own seals, making the restructuring obligation contingent on firm leadership cooperation. Additionally, if Section II.2.c's coordinating engineer provision is read as creating a genuinely distinct and lesser certification standard for the coordinating role, Engineer A's current practice might be defensible as a coordination-level seal, though the board's integrated reading of II.2.a, II.2.b, and II.2.c forecloses this interpretation. The tension between the Non-Substitution Principle and the Technical Segment Sealing principle also creates uncertainty about whether distributed sealing fully resolves Engineer A's responsible charge obligation or merely redistributes it.

Grounds

Engineer A has institutionalized a practice in which registered engineer subordinates are relieved of affixing their own seals to the technical segments they personally prepare, with Engineer A serving as the sole sealing engineer across the entire firm's output. This practice makes adequate responsible charge review structurally impossible at the firm's scale. Section II.2.c expressly contemplates a coordinating engineer model in which a registered engineer accepts responsibility for an entire project while subordinate registered engineers seal their own segments. The firm's current architecture forecloses this distributed accountability structure.

Affirmative Restructuring Obligation for Sealing Architecture Subordinate Competence Confidence Non-Substitution Violation

Should Engineer A apply a categorically more stringent standard, direct control and personal supervision, before sealing plans prepared by non-registered graduate engineers, or should he apply the same general supervision standard he uses for registered engineer subordinates across all subordinate work regardless of licensure status?

Options considered:
O1 Refuse to seal any plans prepared by non-registered graduate engineers unless he can demonstrate direct control and personal supervision of that work: contemporaneous, granular oversight that functionally substitutes for the absent licensure of the subordinate, and advocate within the firm for staffing changes that make such supervision feasible at scale. Board's choice
O2 Apply the same general supervision standard, conceptual direction, design-requirement setting, and consultative input, to all subordinate work regardless of whether preparers are registered or non-registered, treating licensure status as a background credential rather than a factor that modifies the sealing engineer's review obligation.
O3 Limit non-registered graduate engineers to tasks that do not require professional sealing, preliminary calculations, drafting support, data collection, and assign all work requiring a professional seal exclusively to registered engineer subordinates who can bear independent professional accountability for their segments, thereby eliminating the compounded risk scenario entirely.
Argument structure:
Warrants

The Direct Control and Personal Supervision Obligation for Non-Registered Subordinate Work holds that the NCEE Model Law's heightened standard is not aspirational but mandatory, reflecting the structural reality that non-registered engineers cannot self-certify. The Dual-Mode Seal Authorization Principle recognizes that sealing non-registered subordinate work requires a categorically different and more demanding form of oversight than sealing registered subordinate work. The Public Welfare Paramount principle holds that when Engineer A's seal is the sole professional certification of work that has received no professional-level verification whatsoever, the public is exposed to a compounded and categorically greater risk. Competing against differentiation, the General Direction Non-Equivalence standard could be read as applying uniformly to all subordinate work regardless of licensure status, and the firm's operational model treats all subordinate engineers under a unified supervision framework.

Rebuttals

Uncertainty arises because if registered subordinate engineers are themselves capable of catching errors before plans reach Engineer A, their presence constitutes a meaningful intermediate safeguard that partially distinguishes the registered-subordinate scenario, but this intermediate safeguard is entirely absent for non-registered subordinate work, which arguably strengthens rather than weakens the differentiation. Additionally, whether the NCEE Model Law's 'direct control and personal supervision' language establishes a genuinely distinct and more demanding threshold, or merely a contextual application of the same general responsible charge standard: is contested, creating uncertainty about whether a separate and more stringent ethical finding is warranted or whether the board's unified finding adequately captures both scenarios.

Grounds

Engineer A seals plans prepared by non-registered graduate engineers under only general supervision, the same standard he applies to registered engineer subordinates. Non-registered graduate engineers have not passed licensure examinations and cannot independently certify their own work. Their plans enter the public record bearing only Engineer A's seal, with no intermediate professional quality gate from any licensed engineer. The NCEE Model Law imposes a 'direct control and personal supervision' standard specifically for work performed by non-licensed subordinates before a registered engineer may take professional responsibility for that work.

Direct Control and Personal Supervision Obligation for Non-Registered Subordinate Work Non-Registered Work Entering Public Record Without Independent Professional Certification

Should Engineer A apply a single uniform sealing standard to all subordinate work regardless of licensure status, or differentiate his practice by refusing to seal non-registered graduate engineers' plans unless he can exercise direct control and personal supervision over that work while applying a less stringent review standard to plans prepared by registered engineer subordinates?

Options considered:
O1 Engineer A declines to seal any plans prepared by non-registered graduate engineers unless he can demonstrate direct control and personal supervision of that specific work, while continuing to seal registered subordinates' plans subject to whatever review standard he can achieve, recognizing the categorical difference in public risk between the two scenarios and the NCEE Model Law's heightened standard for non-licensed subordinate work. Board's choice
O2 Engineer A applies the same general supervision standard: conceptual direction, design-requirement setting, and availability for technical consultation, uniformly to all subordinate work regardless of licensure status, treating demonstrated competence and internal quality controls as a sufficient professional basis for sealing in both cases and relying on the firm's institutionalized supervisory architecture.
O3 Engineer A restructures the firm's staffing model so that non-registered graduate engineers are assigned only to projects where a registered engineer with sufficient supervisory capacity, not necessarily Engineer A himself, can exercise direct control and personal supervision over their work, distributing supervisory responsibility among multiple registered engineers rather than concentrating it in the chief engineer role.
Argument structure:
Warrants

Competing obligations: (1) The Direct Control and Personal Supervision Obligation for Non-Registered Subordinate Work requires that Engineer A exercise granular, contemporaneous control over non-licensed subordinates' work, a standard that functionally substitutes for the absent licensure of the subordinate, before sealing. (2) The Dual-Mode Seal Authorization Principle recognizes that the sealing standard is categorically different for non-registered versus registered subordinate work, because registered subordinates retain independent licensure accountability that provides a residual professional quality floor. (3) The Subordinate Competence Confidence Non-Substitution Principle holds that trust in any subordinate's ability, registered or not, cannot replace the sealing engineer's own verification. (4) The Chief Engineer Managerial Responsible Charge Standard suggests that for registered subordinates, managerial oversight may provide a defensible, if insufficient, basis for sealing, whereas for non-registered subordinates no such argument is available.

Rebuttals

Uncertainty arises because if registered subordinate engineers are themselves capable of catching errors before plans reach Engineer A, their presence may constitute a meaningful intermediate safeguard that distinguishes the two scenarios in degree rather than kind. Additionally, the NCEE Model Law's 'direct control and personal supervision' language may admit of degree, meaning a rigorously structured supervisory protocol for non-registered engineers could satisfy the standard without requiring Engineer A's continuous personal presence on every design decision, potentially narrowing the categorical distinction between the two scenarios.

Grounds

Engineer A seals plans prepared both by registered engineer subordinates (who do not affix their own seals) and by non-registered graduate engineers working under only general supervision. Non-registered engineers' work enters the public record bearing only Engineer A's seal. The NCEE Model Law imposes a 'direct control and personal supervision' standard specifically for work performed by non-licensed subordinates before a registered engineer may take professional responsibility for that work. The firm has institutionalized a general supervision standard that applies uniformly across both categories of subordinate.

Engineer A Subordinate Competence Confidence Non-Substitution Sealing Review Sealing Non-Registered Engineers' Plans

Should Engineer A relinquish or restructure the Chief Engineer sealing role unless the firm redesigns its sealing architecture to make responsible charge achievable, for example through multi-engineer sealing or reduced project volume, or should he retain the role and discharge it through the managerial oversight activities he currently performs, treating those activities as constituting the responsible charge appropriate to a chief engineer's organizational position?

Options considered:
O1 Engineer A informs firm leadership that he will retain the chief engineer sealing role only if the firm restructures its sealing architecture to make responsible charge achievable, specifically by requiring registered engineer subordinates to affix their own seals to segments they prepare, reducing project volume, or distributing sealing authority among multiple registered engineers, and relinquishes the sealing role if the firm declines to restructure. Board's choice
O2 Engineer A retains the chief engineer sealing role and continues to discharge it through the managerial activities he currently performs, conceptual direction, design-requirement setting, and technical consultation, treating these contributions as constituting the form of responsible charge appropriate to a chief engineer's organizational position in a large firm, consistent with the view that the chief engineer role is a legitimate and recognized mode of professional oversight.
O3 Engineer A retains the chief engineer role in a coordination capacity under Section II.2.c but immediately requires all registered engineer subordinates to affix their own seals to the technical segments they personally prepare, limiting Engineer A's seal to the project's integration and coordination function, for which his conceptual direction and design-requirement activities constitute genuine responsible charge, without waiting for firm-wide structural redesign.
Argument structure:
Warrants

Competing obligations: (1) The Competence Prerequisite for Role Acceptance principle, applied by analogy from BER Case 85-3, holds that if organizational scale made detailed review structurally impossible from the outset, Engineer A's acceptance of the chief engineer sealing role under those conditions was itself the threshold ethical act generating all downstream violations. (2) The Professional Accountability principle holds Engineer A fully responsible for all work sealed under his authority, creating a compounding obligation that grows with each sealed document and cannot be dissolved by organizational scale. (3) The Chief Engineer Managerial Responsible Charge Standard holds that a chief engineer's conceptual direction and consultative contributions constitute a legitimate form of responsible charge appropriate to the managerial role, potentially distinguishing the chief engineer scenario from the cross-domain incompetence scenario in Case 85-3. (4) The Organizational Scale Non-Excuse for Responsible Charge Review Obligation holds that the size of the firm is a resource allocation problem, not a standard-reduction justification.

Rebuttals

Uncertainty arises because the Case 85-3 analogy may not map cleanly onto Engineer A's situation: the chemical engineer in that case accepted a role in a domain outside his professional competence entirely, whereas Engineer A is a qualified engineer accepting a managerial role within his own domain. The incapacity in Engineer A's case is one of scale and time, not subject-matter competence, which may support a less categorical application of the competence prerequisite principle. Additionally, if the chief engineer role is understood as a legitimate organizational form of responsible charge, with the seal certifying integration and coordination rather than granular segment-level detail, then the role may be ethically acceptable provided the firm implements subordinate sealing for technical segments.

Grounds

Engineer A accepted and continues to hold the Chief Engineer role in a large engineering firm. The firm's organizational scale is such that detailed review of every plan sealed by Engineer A is practically impossible for a single engineer. Engineer A has institutionalized a general supervision standard as a substitute for detailed review. BER Case 85-3 established that accepting a role one lacks the competence, or practical capacity, to fully discharge is itself an ethical violation. The NSPE Code Sections II.2.a, II.2.b, and II.2.c, read as mutually dependent provisions, impose a unified duty requiring that the sealing engineer possess the practical capacity to discharge responsible charge over all sealed documents.

Engineer A Chief Engineer Minimum Engagement Responsible Charge Sealing Accepting Chief Engineer Role
Event Timeline (10)
10 sequenced 5 actions 5 events
Case timeline
Engineer A accepts and maintains the role of Chief Engineer in a large firm with a high volume of concurrent projects, implicitly taking on responsibility for all sealed documents produced by the organization.
At stake (2)
  • Obligation to ensure that the scope of responsibility accepted does not exceed the engineer's capacity to exercise direct control and personal supervision (NCEE Model Law, Section II.2.b)
  • Obligation to ensure each technical segment is sealed only by the qualified engineer who prepared it (Section II.2.c)
Fulfills (1)
  • Accepting work within a domain where he possesses general engineering competence (Section II.2.a)
Engineer A deliberately defines 'general direction and supervision' as involvement in concept establishment, design requirements, periodic progress reviews, and answering technical questions, explicitly excluding detailed review or checking of designs as a component of his oversight model.
Fulfills (1)
  • Partial fulfillment of managerial guidance role recognized as legitimate for chief engineers (concept-setting, design requirements, progress review, technical consultation)
Violates (3)
  • Obligation to exercise direct control and personal supervision over all work bearing his seal (NCEE Model Law; Section II.2.b)
  • Obligation to possess understanding and cognizance of sealed documents (Section II.2.b)
  • Obligation to protect public safety by ensuring thorough review of engineering designs
Engineer A makes an explicit, ongoing decision not to perform detailed review or checking of designs before affixing his seal, rationalizing this omission as ethically and legally acceptable on the basis of his confidence in the competence of his staff.
Fulfills (1)
  • None identified with respect to the sealing obligation; general managerial involvement is fulfilled but does not satisfy the sealing standard
Violates (4)
  • Code Section II.2.b: engineer must sign and seal only documents in which he has understanding and cognizance, omitting detailed review undermines the basis for such cognizance
  • NCEE Model Law: 'direct control and personal supervision' cannot be satisfied without meaningful review of the work product
  • Obligation to protect public safety by ensuring engineering designs are personally verified by the responsible engineer before sealing
  • Obligation of professional honesty, affixing a seal implies a level of review that Engineer A acknowledges he is not performing
Engineer A's self-defined 'general supervision' standard becomes the de facto institutional practice within the firm, replacing the legally required 'direct control and personal supervision' standard. This normalization occurs gradually as the practice is repeated without challenge.
Engineer A affixes his own seal to plans prepared by registered engineers working under his general direction, while those registered engineers do not affix their own seals to the same plans, consolidating all sealing authority in Engineer A alone.
Fulfills (1)
  • Ensuring that a licensed professional engineer's seal appears on all submitted plans
Violates (3)
  • Code Section II.2.c: each technical segment shall be signed and sealed only by the qualified engineer who prepared that segment
  • Code Section II.2.b: the sealing engineer must have understanding and cognizance of the work sealed
  • Obligation to maintain transparent and accurate attribution of professional responsibility
As a direct outcome of Engineer A's sealing practice, registered engineers under his direction are effectively relieved of their individual professional sealing obligations, creating a structural gap in the chain of professional accountability required by engineering regulations.
Engineer A affixes his seal to plans prepared by non-registered graduate engineers working under his general supervision, assuming sole legal and ethical responsibility for work produced by unlicensed individuals without exercising direct control and personal supervision over that work.
Fulfills (2)
  • Ensuring a licensed engineer's seal appears on plans before public submission
  • Providing some level of technical guidance and consultation to non-registered staff
Violates (4)
  • Obligation that work by non-registered engineers be performed under direct control and personal supervision of a registered engineer who seals the document (Code Section II.2.b; NCEE Model Law)
  • Code Section II.2.b: the sealing engineer must possess understanding and cognizance of the sealed work
  • Obligation to protect public safety by ensuring unlicensed work receives rigorous licensed oversight
  • Code Section II.2.c: technical segments must be sealed by the qualified engineer who prepared them: non-registered engineers cannot seal, making direct control by the sealing engineer even more critical
Plans prepared by non-registered graduate engineers, sealed solely by Engineer A under general supervision, are completed and enter the public and professional record as if they carry the full weight of direct professional oversight, when in fact they do not.
The prior ethics ruling in Case 85-3 (1985) is applied as binding precedent to Engineer A's situation, automatically triggering the established interpretation of 'direct control and personal supervision' as the applicable standard against which Engineer A's conduct is measured.
Following analysis against applicable Code provisions and prior case precedent (Case 85-3, 1985), the reviewing body determines that Engineer A's level of oversight does not meet the ethical and legal standard of 'direct control and personal supervision' required for sealing documents, constituting a formal finding of ethical violation.
Narrative (1 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, the Chief Engineer at a large engineering firm. Your responsibilities include affixing your professional seal to plans produced by two categories of subordinates: registered engineers who do not affix their own seals, and non-registered graduate engineers working under your general supervision. Because of the firm's size and the volume of concurrent projects, you are not conducting detailed reviews or checks of the designs before sealing them. Your involvement consists of helping establish project concepts and design requirements, reviewing elements as work progresses, and responding to technical questions from your team. You believe this level of general direction and supervision, combined with your confidence in the people you have hired, satisfies your ethical and legal obligations. The decisions ahead concern what standard of review and oversight your sealing practice must meet, and whether your current role and the firm's structure can support that standard.

Main characters (1)

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

Engineer A Roles in this case: hover for definitions Chief Engineer Sealing SupervisorOut-of-Competence County Surveyor

Tension between Supervisory Sealing Authority Structural Redesign Capability and Engineer A Supervisory Sealing Authority Structural Redesign Capability Deficit

Attaches to role: Chief Engineer Sealing Supervisor

Tension between Engineer A Chief Engineer Minimum Engagement Responsible Charge Sealing and Accepting Chief Engineer Role

Attaches to role: Chief Engineer Sealing Supervisor

The code requires that each discrete technical segment of engineering work be sealed only by an engineer who is competent in and responsible for that specific segment. Simultaneously, Engineer A's role as supervisory sealer — directing CADD-based production work — does not satisfy the authorization threshold for sealing technical segments outside his domain competence. These two principles collide when Engineer A seals structural, survey, or other out-of-competence segments: the exclusive sealing obligation demands a qualified segment-specific engineer, but the firm's sealing architecture routes that authority through Engineer A regardless. Honoring the constraint means Engineer A cannot lawfully seal those segments; honoring the obligation means those segments must be re-attributed to qualified subordinate sealers — a structural change the firm has not implemented.

Attaches to role: Chief Engineer Sealing Supervisor

Tension between Engineer A Subordinate Competence Confidence Non-Substitution Sealing Review and Sealing Non-Registered Engineers' Plans

Attaches to role: Chief Engineer Sealing Supervisor

Tension between Engineer A Organizational Scale Non-Excuse Responsible Charge Sealing and Consciously Omitting Detailed Design Review

Attaches to role: Chief Engineer Sealing Supervisor

Engineer A, as Chief Engineer, bears an irreducible obligation to maintain meaningful responsible charge engagement with all work bearing his seal — including minimum substantive review — yet the organizational scale of the firm structurally prevents him from performing that review across the volume of plans produced. This is a genuine dilemma because the obligation cannot be delegated away or waived by operational necessity, yet the constraint is not self-imposed but systemic. Fulfilling the managerial role as constituted makes fulfilling the responsible charge obligation impossible; fulfilling the responsible charge obligation would require either refusing to seal most work or restructuring the organization, neither of which the firm's operational model accommodates.

Attaches to role: Chief Engineer Sealing Supervisor

Engineer A's reliance on the demonstrated competence and track record of his registered subordinate engineers as a practical substitute for his own detailed review creates a direct tension: the obligation categorically prohibits treating confidence in subordinate ability as equivalent to responsible charge review, while the constraint independently bars sealing authorization on that same basis. Both the obligation and the constraint point in the same direction normatively, but their simultaneous presence reveals that Engineer A's actual practice — sealing work he has not personally reviewed because he trusts his subordinates — violates both simultaneously and without mitigation. The ethical dilemma is that correcting this practice at organizational scale may be operationally impossible, forcing a choice between professional integrity and firm viability.

Attaches to role: Chief Engineer Sealing Supervisor

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

Tension between Engineer A Subordinate Competence Confidence Non-Substitution Sealing Review and Sealing Non-Registered Engineers' Plans

Engineer A, as Chief Engineer, bears an irreducible obligation to maintain meaningful responsible charge engagement with all work bearing his seal — including minimum substantive review — yet the organizational scale of the firm structurally prevents him from performing that review across the volume of plans produced. This is a genuine dilemma because the obligation cannot be delegated away or waived by operational necessity, yet the constraint is not self-imposed but systemic. Fulfilling the managerial role as constituted makes fulfilling the responsible charge obligation impossible; fulfilling the responsible charge obligation would require either refusing to seal most work or restructuring the organization, neither of which the firm's operational model accommodates.

Engineer A's reliance on the demonstrated competence and track record of his registered subordinate engineers as a practical substitute for his own detailed review creates a direct tension: the obligation categorically prohibits treating confidence in subordinate ability as equivalent to responsible charge review, while the constraint independently bars sealing authorization on that same basis. Both the obligation and the constraint point in the same direction normatively, but their simultaneous presence reveals that Engineer A's actual practice — sealing work he has not personally reviewed because he trusts his subordinates — violates both simultaneously and without mitigation. The ethical dilemma is that correcting this practice at organizational scale may be operationally impossible, forcing a choice between professional integrity and firm viability.

Engineer A, as Chief Engineer, bears an irreducible obligation to maintain meaningful responsible charge engagement with all work bearing his seal — including minimum substantive review — yet the organizational scale of the firm structurally prevents him from performing that review across the volume of plans produced. This is a genuine dilemma because the obligation cannot be delegated away or waived by operational necessity, yet the constraint is not self-imposed but systemic. Fulfilling the managerial role as constituted makes fulfilling the responsible charge obligation impossible; fulfilling the responsible charge obligation would require either refusing to seal most work or restructuring the organization, neither of which the firm's operational model accommodates.

The code requires that each discrete technical segment of engineering work be sealed only by an engineer who is competent in and responsible for that specific segment. Simultaneously, Engineer A's role as supervisory sealer — directing CADD-based production work — does not satisfy the authorization threshold for sealing technical segments outside his domain competence. These two principles collide when Engineer A seals structural, survey, or other out-of-competence segments: the exclusive sealing obligation demands a qualified segment-specific engineer, but the firm's sealing architecture routes that authority through Engineer A regardless. Honoring the constraint means Engineer A cannot lawfully seal those segments; honoring the obligation means those segments must be re-attributed to qualified subordinate sealers — a structural change the firm has not implemented.

These tensions did not map cleanly to a single character.

Tension between Responsible Charge Direct Control Personal Supervision Non-Registered Work Sealing Obligation and Direct Control and Personal Supervision Obligation for Non-Registered Subordinate Work

Tension between Responsible Charge Active Review Obligation Before Sealing and Organizational Scale Preventing Adequate Review

Tension between Direct Control and Personal Supervision Obligation for Non-Registered Subordinate Work and Non-Registered Work Entering Public Record Without Independent Professional Certification

Tension between Chief Engineer Managerial Role Responsible Charge Minimum Engagement Obligation and Consciously Omitting Detailed Design Review

Tension between Organizational Scale Non-Excuse for Responsible Charge Review Obligation and General Direction Non-Equivalence to Responsible Charge Sealing Prerequisite Obligation

Tension between Affirmative Restructuring Obligation for Sealing Architecture and Subordinate Competence Confidence Non-Substitution Violation

Opening States (10)
Responsible Charge Standard Clarification - Direction and Control Definition Chief Engineer Managerial Responsible Charge Model State Engineer A Non-Registered Engineer Seal Delegation General Supervision Without Detailed Design Review State Non-Registered Engineer Seal Delegation State Organizational Scale Preventing Adequate Supervisory Review State Competence-Trust Substitution for Verification State Engineer A Insufficient Responsible Charge Engineer A Responsible Charge Standard Clarification Active Engineer A Organizational Scale Preventing Adequate Review
Summary
  • Organizational scale and complexity do not excuse an engineering firm from ensuring that responsible charge review is structurally feasible for every project requiring a licensed engineer's seal.
  • General supervisory direction over non-registered subordinates is categorically insufficient to satisfy the direct control and personal supervision prerequisites for legitimate responsible charge sealing.
  • When a supervising engineer lacks the technical competency to redesign or critically evaluate structural work, their sealing authority is ethically void regardless of their formal organizational position.

© Licensed under the GNU GPL v3 | Report Issue